What We Fix Automatically

Categories of Auto-Fixes

1. Date Format Corrections

We normalize dates to ISO 8601 format (YYYY-MM-DD):

• 15-01-2026 → 2026-01-15
• 01/15/2026 → 2026-01-15
• 15 Jan 2026 → 2026-01-15

2. Scheme Identifier Fixes

We add or correct scheme identifiers for party identifiers:

• Missing schemeID → Derived from country/context
• EAN → 0088 (standard GLN scheme)
• GLN → 0088

3. Code Value Mapping

We map human-readable codes to standard values:

• Invoice → 380 (UNTDID 1001)
• EUR currency codes normalized
• Unit codes mapped to UN/ECE Rec 20

4. XML Structure Fixes

We correct structural issues:

• Missing required empty elements
• Namespace corrections
• Element ordering issues

Why These Fixes Are Safe

Auto-fixes only change the technical representation of your data, not the data itself:

• Date formats: "15-01-2026" and "2026-01-15" mean the same date
• Scheme codes: "EAN" and "0088" both mean "GLN number"
• Document types: "Invoice" and "380" both mean "commercial invoice"

Confidence Levels

Each fix has a confidence score:

• High (>90%): Applied automatically, shown in summary
• Medium (70-90%): Applied with notice for review
• Low (<70%): Shown for explicit approval

How to Use Auto-Fix

1. Go to the Fixer tool
2. Upload your invoice
3. Auto-fixes are applied during the "We Fix Them" step
4. Review the change log showing all auto-fixes
5. Download your fixed invoice

What If Auto-Fix Isn't Enough?

Some errors need information we can't derive from the invoice:

• Missing buyer reference → We ask you
• Missing payment terms → We ask you
• Calculation errors → Needs source system fix

See Quick Start Guide for the full workflow.