Why does ERP data quality matter for e-invoicing?
An e-invoice is assembled from the data in your ERP and checked against validation rules before it is exchanged. If a customer's VAT number is missing, an item has no tax category or a credit note does not reference its invoice, the document fails validation. Cleaning master data before go-live is usually the cheapest and fastest part of e-invoicing readiness.
Data quality decides how smoothly you go live
Most finance teams expect the hard part of e-invoicing to be the technology: formats, networks, connections. In practice, the format and the exchange are handled by your e-invoicing provider. What your provider cannot fix is the data your systems send. A PDF invoice could hide a missing field behind a nicely formatted page; a structured invoice cannot. Every gap becomes a validation error, and every validation error becomes a delayed invoice.
The good news is that data problems are knowable in advance. A focused review of four areas catches the large majority of them.
Party data: who you bill and who you buy from
Start with customers and suppliers. For each active party, check that the legal name is complete and consistent, that the VAT registration number is present where the party is registered and is in the right format, and that the address is structured into proper fields rather than typed into a single line. Duplicate records are a classic problem: the same customer created twice, once with a VAT number and once without, so half the invoices fail.
Item and tax data: what you sell
Every line of an e-invoice needs a tax treatment. Review your item master and service codes so that each one carries the right VAT category, with the standard 5% rate applied where it belongs and any other treatment explicitly assigned rather than left blank. Check units of measure too: ‘pcs’, ‘PCS’ and ‘each’ may mean the same thing to people, but a validation rule sees three different values.
Document references and numbering
Adjustments are where reference data matters most. A credit note or debit note must point to the invoice it adjusts, so make sure your ERP stores that link rather than relying on a note in a free-text field. Review your numbering too. Each document series should produce reliable, unique numbers without gaps caused by manual overrides, and each branch or system that issues invoices should have a clearly separated series.
Totals, rounding and currency
Structured invoices are checked arithmetically: line amounts, tax amounts and totals must reconcile. ERPs that round per line in one place and per document in another create small differences that a validator will reject. If you invoice in more than one currency, check how exchange rates and converted amounts are stored, and confirm the presentation requirements with your adviser.
Running a data audit without stopping the business
- Extract. Export active customers, suppliers and items, plus a sample of recent invoices and credit notes from every issuing system.
- Profile. Count blanks, duplicates and inconsistent values per field. A spreadsheet is enough to start.
- Prioritise. Fix the parties and items you invoice most often first; they drive most of your volume.
- Fix at source. Correct the ERP record, not the exported file, so the problem does not come back.
- Prevent. Add required fields and simple checks to the ERP's create screens so new records arrive clean.
How Invoice And Tax helps
Invoice And Tax checks every document against versioned, deterministic validation rules and Schematron conformance checks before transmission, and explains each error so it can be fixed at the source. The same input always produces the same result, which makes a data clean-up measurable. Data can arrive through the versioned REST API, through the connector framework, or through Excel and CSV import, and every route feeds one shared document composer, so the same checks apply whichever way the data comes in.
| Data area | Typical problem | What to check |
|---|---|---|
| Customers and suppliers | Missing or malformed VAT number; duplicates | One record per party, complete legal name, structured address |
| Items and services | No VAT category; inconsistent units | Tax category on every item; one code per unit of measure |
| Adjustments | Credit note without a link to the invoice | Original invoice reference stored in a field |
| Numbering | Gaps or reused numbers after manual edits | Separate, unique series per issuing system or branch |
| Totals | Rounding differences between lines and total | One consistent rounding rule |
Questions about ERP data
Do I need to replace my ERP for e-invoicing?
Usually not. Most ERPs can supply the data an e-invoice needs; the work is in making that data complete and consistent and connecting it to your provider.
How long does a data clean-up take?
It depends on the number of active parties and items and on how many systems issue invoices. Starting with the most-used records gives early results.
Can spreadsheets be part of the process?
Yes. Excel and CSV import are a legitimate route, provided the files carry the same complete data an ERP would.