ERP integration checklist for e-invoicing rollout teams
Official references
Use these sources to verify dates, formats, and official rule changes.
Related Technical Wiki
Explore deep-dive developer documentation and regulatory guidelines matching this article.
Practical guides for validating DATEV, Lexware, SAP Business One, Odoo, and Microsoft Dynamics invoice exports.
Common integration error codes explained for non-technical users.
Common e-invoicing code lists: VAT category codes, payment means codes, unit codes, and invoice type codes.
This checklist is for ERP owners, finance operations teams, and implementation leads introducing e-invoicing into an existing accounting system or custom billing platform.
The common mistake is to treat e-invoicing as an export-format problem. In practice, the work covers master-data quality, country and recipient routing, XML generation, validation, exception handling, and a clear handoff to finance operations.
1. Define the target scope first
- List which countries, recipient types, and channels are in scope for phase one.
- Define the target formats per workflow: XRechnung, ZUGFeRD/Factur-X, UBL, or CII.
- Decide whether the ERP will generate the final XML or whether a conversion service will act as the integration layer.
2. Clean the source data before mapping
- Review seller and buyer master data, tax identifiers, addresses, IBANs, and payment terms.
- Check that line items, discounts, allowances, charges, and VAT categories are stored consistently.
- Mark fields that need enrichment outside the ERP, such as a buyer reference or Leitweg-ID.
3. Design the mapping and validation path together
Design mapping and validation together. Missing required fields and code-list mismatches are easiest to catch while the ERP-to-XML mapping is being defined.
- Map every required field to a known ERP source or an explicit fallback workflow.
- Confirm the code lists for VAT categories, payment means, currencies, and country codes.
- Decide which validation reports to retain and who is responsible for correcting rejected invoices.
4. Build an exception workflow before go-live
- Define who reviews uncertain extracted data and missing identifiers.
- Document when to regenerate an invoice from source data instead of editing the XML.
- Set response times for validation failures so finance teams know what blocks transmission.
5. Test with realistic invoice samples
- Test simple domestic invoices first.
- Then test discounts, mixed VAT rates, exemptions, credit notes, and recipient-specific identifiers.
- Run end-to-end tests through the target delivery channel and any downstream import or portal.
6. Involve operational owners before go-live
- Train finance users on what to review before sending.
- Expose validation status and correction ownership clearly in the daily workflow.
- Keep a manual handling path for invoices that cannot yet pass automatically during the first rollout wave.
Ready to convert your invoices?
Start converting PDF invoices to XRechnung, ZUGFeRD, and other formats today with credits or a paid plan.