What it means
ERP mapping connects source accounting fields to stable semantic invoice terms and then to one or more country profiles.
The canonical layer prevents every country adapter from depending directly on one ERP table layout.
Implementation method
- 1Inventory source fields, ownership and quality.
- 2Map to canonical document, party, line, tax, payment and reference domains.
- 3Create versioned profile transformations with explicit defaults and loss reports.
- 4Test semantic totals and edge cases using golden files.
Common mistakes
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Build an explicit control or test case for this condition.
Questions and answers
Should the canonical model copy EN 16931 exactly?
It can use EN 16931 concepts, but global implementations may need additional clearance, reporting, signature and lifecycle fields.
How should extensions be handled?
Keep namespaced extension domains and document which adapters consume or drop them.
Can EInvoiceLab officially certify ERP mapping?
No. EInvoiceLab can inspect, prepare and explain technical data, but official conformance, delivery or acceptance depends on the active authority, network, accredited provider and validation artefacts.
Should I keep the original structured file?
Yes. Preserve the original XML or JSON, its hash, every validation report and the final authority or network response. A readable PDF should not replace the source document.