Peppol Integration with ERP and Accounting Systems: 2026 Connector Guide

Choosing a Peppol Access Point looks simple until you read the integration brief from your ERP team. SAP, Odoo, Dynamics 365, Exact, Yuki and Billit all expose invoice data differently. The real question is not which Access Point is cheapest. It is which one connects cleanly to the system your finance team already uses. This guide compares 6 Peppol Access Points by ERP and accounting connector coverage, then walks through a generic integration in 5 steps with a working API example.

TL;DR

If you need Peppol delivery without switching ERP, pick e-invoice.be. It exposes a REST API with SDKs in 5 languages (Python, Node.js, PHP, C#, Java), accepts flat JSON or PDF/Word/Excel input, and delivers inbound invoices to any ERP via webhook or batch upload. Native connectors inside Billit, Yuki and Odoo are the fastest path if you are already on one of those platforms. Basware, Unifiedpost, Comarch and Pagero target large SAP and Oracle estates with deeper AP automation.

Why ERP integration is the hard part of Peppol

Sending a Peppol invoice involves three layers that most integration guides skip. The first is the SMP (Service Metadata Publisher) lookup. Before any invoice can leave your network, the Access Point queries the recipient's SMP record to find their endpoint URL, supported document types and trust certificates. If the lookup fails, the invoice never gets routed.

The second layer is UBL conversion against EN 16931 and Peppol BIS 3.0. Your ERP exports invoice data in a proprietary model. SAP uses IDoc INVOIC02, Odoo emits a JSON model close to its account.move entity, Dynamics 365 BC exposes SalesInvoice through AL events. Each has different field names, VAT category codes, and unit handling. The Access Point must transform every export into UBL 2.1 XML that passes the EN 16931 schematron and the additional Peppol BIS 3.0 rules. Read more about the UBL invoice format.

The third layer is MLR (Message Level Response) handling. When a recipient's Access Point rejects a document (invalid tax calculation, unknown buyer reference, schematron error) you get an MLR back. That MLR has to surface in your ERP so the AR team can fix and resend. Most native ERP connectors do this badly. A good API integration owns it.

Three integration patterns

There are exactly three ways to connect an ERP to Peppol. Pick the one that matches how your invoicing flow works today.

1. Native connector inside the ERP. The accounting platform embeds a Peppol Access Point. You enable a setting and invoices flow to Peppol without any custom code. Best for SME-focused suites: Billit, Yuki, Odoo, Exact Online, Dynamics 365 BC. Limitation: you are locked to the platform's built-in AP, with its pricing and feature set.
2. REST API integration. Your ERP middleware (SAP PI/PO/CPI, Odoo automation, Boomi, Workato, custom .NET) posts invoices to a Peppol Access Point API. Webhooks bring inbound invoices back. Best for any ERP, any volume, any customisation. This is what e-invoice.be is built for.
3. Batch CSV or SFTP upload. The ERP exports a daily file of invoices. The Access Point picks it up, sends each one, and posts a result file back. Best for legacy ERPs without a modern integration layer, or for parallel runs during migration.

Connector matrix: 6 Access Points × 10 ERP and accounting systems

Native = first-party plug-in maintained by the AP or the ERP vendor. API = standard REST integration via middleware. Partner = available through a third-party integrator. None = no documented integration path in 2026.

Matrix as of May 2026. Vendor connectors change frequently. Verify the current state on the provider's integration directory before committing.

Integration walkthrough: 5 steps from ERP to Peppol

This is the same flow every API-based integration follows, whether you are on SAP, Odoo, Dynamics 365 BC, NetSuite or QuickBooks. The code example below uses the e-invoice.be Peppol API.

1. Register your Peppol ID. Register the business entity in the Peppol SMP using your KBO/BCE enterprise number for Belgium (scheme 0208) or the equivalent national identifier. With e-invoice.be this is included and takes half a day after KYC.
2. Export the invoice from your ERP. Trigger an export when the invoice is posted: IDoc INVOIC02 for SAP, account.move JSON for Odoo, SalesInvoice entity for Dynamics 365 Business Central, or the standard report from Exact, Yuki or Billit.
3. POST the document to the Access Point API. Send the invoice as flat JSON to POST /v1/documents using vendor_name, customer_name, customer_peppol_id, invoice_id, items and totals. The Access Point converts to UBL, validates against EN 16931 and Peppol BIS 3.0, and routes to the recipient.
4. Handle delivery confirmations via webhook. Subscribe to the delivery webhook so your ERP can mark the invoice as sent, store the Peppol message ID, and surface MLR (Message Level Response) errors back to the AR team.
5. Receive inbound invoices and book them. Configure the inbound webhook to push received Peppol invoices into your AP module. e-invoice.be returns the same flat-field JSON for inbound, so the mapping is symmetric with sending.

// POST /v1/documents
// Authorization: Bearer YOUR_API_KEY
{
  "document_type": "INVOICE",
  "invoice_id": "INV-2026-00042",
  "invoice_date": "2026-05-15",
  "due_date": "2026-06-14",
  "currency": "EUR",
  "vendor_name": "Your Company BV",
  "vendor_tax_id": "BE0123456789",
  "vendor_address": "Kerkstraat 1, 1000 Brussels, BE",
  "vendor_peppol_id": "0208:0123456789",
  "customer_name": "Acme NV",
  "customer_tax_id": "BE0987654321",
  "customer_address": "Lange Lozanastraat 250, 2018 Antwerp, BE",
  "customer_peppol_id": "0208:0987654321",
  "items": [
    {
      "description": "ERP integration consultancy",
      "quantity": 8,
      "unit": "HUR",
      "unit_price": 125.00,
      "tax_rate": 21
    }
  ]
}

The Access Point converts this JSON to UBL 2.1, validates it against EN 16931 and Peppol BIS Billing 3.0, looks up the recipient's SMP record using customer_peppol_id, and routes the document. The response contains the Peppol message ID, which your ERP should store against the invoice for reconciliation. See the full API integration guide for authentication, retries and webhook signatures.

"The teams that ship Peppol fastest are the ones that treat it as a plain REST integration, not a tax project. If your Access Point makes you think in UBL, switch."

When to pick which integration pattern

• You are on Billit, Yuki, Odoo or Exact Online. Use the native connector. It activates in minutes and is maintained by the platform vendor.
• You are on SAP, Dynamics 365, NetSuite, Sage or QuickBooks. Build a REST API integration against e-invoice.be using the SDK for your middleware language. Symmetric flat-field JSON keeps the mapping trivial.
• You have a legacy ERP with no modern integration layer. Use batch CSV or SFTP upload as a stepping stone, then revisit the API once the rest of the stack is modernised.
• You have multinational AR or AP at SAP/Oracle scale. Evaluate Basware, Pagero, Comarch or Unifiedpost for their supplier onboarding programmes and global compliance footprint. The Access Point fee is a small line item next to the AP automation savings.

For accounts receivable specifically, the same pattern applies. Compare options in our guide to the best Peppol Access Points and our walkthrough on automated incoming invoice processing for larger companies.

Frequently Asked Questions