Skip to content
Back to blog
IntegrationPublished 9 June 20266 min read

How to connect your ERP (SAP, Dynamics 365, Infor) to e-invoicing

A practical look at connecting ERP systems to e-invoicing using a push model — SAP IDoc, Dynamics 365 Business Central and F&O, Infor OAGIS, or any standard export.

Most companies already produce invoices in an ERP. The challenge is turning that internal data into a compliant, network-ready e-invoice. The cleanest pattern is a push model: your ERP or middleware sends its native invoice payload to an API, which maps, recomputes and validates it.

Why a push model

In a push model your systems call out to the conversion service with an API key. The service never stores your ERP credentials and never calls back in. That keeps the security surface small and the integration simple — no inbound connections into your ERP.

Ready-made connectors

MyInvoice ships connectors for the most common systems, so you send the payload your ERP already produces:

  • SAP — the classic IDoc INVOIC01/02 as XML; partners resolved by PARVW role.
  • Microsoft Dynamics 365 Business Central — a sales invoice JSON, e.g. from a Power Automate flow.
  • Dynamics 365 Finance & Operations — Electronic Reporting / data-entity JSON.
  • Infor — OAGIS Invoice BOD via ION (a BOD can carry several invoices).
  • Generic — any standard export (UBL, CSV, Excel, EDIFACT or legacy XML).

Totals are always recomputed

Whatever the source, the totals and VAT breakdown are recomputed from the line items rather than trusted from the payload, and all monetary maths uses arbitrary-precision decimals. That avoids rounding surprises and EN 16931 totals-rule failures.

The result

You POST to /v1/erp/:connector with your API key, pick an output profile, and get back compliant XML (per invoice) with validation results. One integration covers SAP, Dynamics, Infor and more — and a generic connector handles anything else you can export.