R
MappingIn the standard unit
- Source
- API, file export or ERP extension
- Model
- EN 16931
- Output
- UBL 2.1 · CII D16B · FA(3) · CIUS-RO · XRechnung 3.0
Collect
Representative invoices and every variant in scope.
Mapping
Your invoice, mapped field by field.
We start from the invoice data the ERP already produces, through its API, a file export or an ERP extension. We map it to the EU standard, EN 16931, and to the syntax the country’s route expects. Every decision on tax codes, exemptions and identifiers is written down.
Mapping
What mapping covers
- 01
Real invoices first
We read a representative set of your invoices, credit notes and awkward cases included, before we map a single field.
- 02
Tax logic
VAT categories, exemption reasons, reverse charge and rounding, set against each country's rules.
- 03
Identifiers with check digits
VAT numbers, company IDs and IBANs are checked before an invoice leaves: Polish NIP, Romanian CUI, Belgian enterprise number, German USt-IdNr. and French SIREN.
- 04
Credit notes and corrections
Each country corrects invoices its own way: a KOR in Poland, an FCN credit note in Romania, a type 381 document in CII. We map the one the route expects.
- 05
A mapping table you keep
Every field, its source and every decision go into one table. It stays with you after handover.
- 06
Your PDF
Where the route allows a readable copy, we can apply your logo and layout. The structured data underneath stays as the format requires.
Mapping
The format each route expects
| Country | Route | Format |
|---|---|---|
| Belgium | Peppol | Peppol BIS 3.0 (UBL 2.1) |
| Germany | Agreed channel | XRechnung 3.0 (UBL or CII), ZUGFeRD |
| France | Plateforme Agréée | UBL France, CII France, Factur-X |
| Poland | KSeF 2.0 | FA(3) |
| Romania | RO e-Factura | CIUS-RO (UBL 2.1) |
| Greece | myDATA provider | The provider's schema |
What we need from you
What we need from you
- A representative set of invoices covering every variant in scope
- Working access to the source: API, file handoff or extension
- Written decisions on tax codes, exemptions, payment data and identifiers
What you get back
- The mapping table, field by field
- A country-valid structured invoice, or a precise list of what is missing
- Mapping notes at handover
14 of 14 sample invoices pass our model check.
Eleven planted defects were rejected in the same run on 27 September 2026. Four sample invoices are on the evidence page.
See the evidenceSteps
How a mapping is built
Questions
Mapping
What if the ERP does not hold a field the country needs?
We name the field, the rule that needs it and where it would come from. Adding it on the ERP side is work for your ERP team or partner, and master-data repair is quoted separately.
Do we have to change the ERP?
Usually not. We start from the data the ERP already exports. Where the country needs a field the export does not carry, a small extension is often the cleanest way to add it.
Contact
Send us three representative invoices.
An ordinary invoice, a credit note and a reverse-charge invoice show most of what the mapping needs. Anonymised copies are fine.
- Your ERP and version
- The first country route and legal entity
- A representative invoice and where the credentials stand
E-mail
[email protected]30-minute call
Choose a time