e-Invoice ERP integration: connectors, data mapping and exception handling
In short: Integrating e-invoicing with your ERP means invoices issued in the accounting system reach RO e-Factura automatically and their status returns to the ERP. EDIconnect ships connectors for 40+ ERPs, including SAP, Microsoft Dynamics, WinMENTOR, Charisma, Senior and Odoo.
Key capabilities
- 40+ ERP connectors: SAP, Microsoft Dynamics, WinMENTOR, Charisma, SeniorERP, Odoo, NexusERP and more, plus a generic API for proprietary systems.
- Master data mapping: Units of measure, VAT rates, exemption codes and country codes are aligned once, during implementation.
- Pre-submission validation: RO_CIUS rules run on the data before the invoice leaves, cutting rejections to near zero.
- Status write-back: The upload index and the final state are written back onto the ERP document.
- Inbound invoices in the ERP: Supplier documents arrive as purchase invoices, matched with orders and receipts.
- No major ERP rework: The integration uses existing interfaces, so the project does not block IT for months.
Where problems actually appear
The technical side of the integration is rarely the hard part. Blockers come from data: items without compliant units of measure, partners without a valid tax ID, inconsistent VAT rates, incomplete addresses on legacy customers.
A sound project therefore starts with a master data clean-up driven by a non-conformity report, not with writing code. With clean data, rejection rates fall below 1%.
Integration project stages
A typical project runs through four stages with a validation gate at the end of each, so go-live does not depend on one critical day.
- Analysis: inventory of documents and master data
- Connection: connector setup and field mapping
- Testing: submission in the test environment and error fixing
- Go-live: parallel run, then full cut-over
Frequently asked questions
How long does ERP integration take?
For an ERP with an existing connector, typically 1-3 weeks including master data mapping and tests on real data.
What if my ERP has no connector?
The generic API or structured file exchange is used instead. The flow stays automated; only the retrieval method differs.
Do I have to modify the ERP?
Usually not. Existing export and import interfaces are used, with extra fields only where a document status must be stored.
How are mapping errors handled?
Documents with incomplete data are stopped before submission and appear in an exception queue naming the exact problematic field.
Can e-Transport be part of the same project?
Yes. The same delivery data from the ERP feeds e-transport declarations and UIT code generation.