ERP Integrators
How do ERP integrators implement e-invoicing compliance modules?
ERP integrators adding e-invoicing compliance to ERP systems must handle format generation (Factur-X, UBL, CII), pre-transmission validation (schema, business rules, VAT), network connectivity (Peppol AP, PDP API, FTA ASP), and lifecycle status updates back into the ERP. The integration layer must be jurisdiction-aware and updatable as regulations change.
What does an e-invoicing integration architecture look like?
A typical ERP e-invoicing integration comprises four layers:
- Data extraction layer: Pull invoice data from ERP in structured format (ERP-native schema)
- Transformation layer: Convert ERP data model to target format (UBL, Factur-X, CII) with field mapping and code list translation
- Validation layer: Schema validation (XSD), business rule validation (Schematron), and VAT calculation check
- Transmission layer: Delivery to Peppol AP, PDP, PPF, or counterparty via certified channel
How frequently do e-invoicing specifications change?
E-invoicing specifications are updated on regular cycles. Integrators must plan for ongoing maintenance:
- Peppol BIS Billing: Major versions annually, minor releases quarterly
- Peppol PINT: Active development with frequent updates as new country extensions are ratified
- French DGFiP specifications: Updated as implementation dates approach and technical pilots provide feedback
- UAE FTA specifications: Active updates during pre-mandate period
Frequently Asked Questions
- Should ERP integrators build their own Peppol Access Point or use a third party?
- Building and certifying a Peppol Access Point requires significant technical investment and ongoing certification maintenance. Most ERP integrators connect to certified AP providers via API rather than operating their own AP. Only large platforms with sufficient volume and technical resources typically justify the cost of AP certification.
- How do ERP integrators handle invoice status callbacks?
- Peppol and PDPs provide Application Response documents (UBL ApplicationResponse or equivalent) to confirm delivery, acceptance, or rejection. ERP integrations must handle these responses and update invoice status in the ERP accordingly, triggering workflow actions (payment, dispute, resubmission) based on the response type.