Why invoices became regulated messages

For most of EDI's history an electronic invoice was a private arrangement. Contoso sends Great Lakes Fleet Services an X12 810 because Great Lakes asked for it in its supplier requirements; the tax authority never sees the file, and a PDF would be just as legal. Government e-invoicing mandates change that. In more and more countries the electronic invoice is the legal invoice, it must follow a prescribed format and route, and in many cases a tax authority or a licensed platform has to see it before or as it reaches the buyer.

That turns invoicing into a regulated B2B message with a new trading partner: the state. For an SAP team it means a new kind of interface, new statuses on every billing document, new master data, and a go-live date set by law rather than by the project.

EDI with a customer versus e-invoicing with a tax authority

Both can coexist. A German customer may keep receiving EDI invoices from a supplier that is also subject to the German e-invoicing rules, as long as the EDI invoice meets the legal requirements. Treat the two as separate requirements and test both.

Four models you will meet

• Post-audit (exchange model). Seller and buyer exchange structured invoices directly or through providers; the authority sees them only in an audit. Germany's B2B rules work this way today.
• Centralized clearance. The invoice becomes valid only after a government system or a licensed intermediary validates it. Mexico's CFDI is the classic case: a certification provider (PAC) validates and stamps each invoice with a unique ID (UUID) on behalf of the tax authority, the SAT. Poland's national e-invoice system, KSeF, is another centralized platform.
• Decentralized continuous transaction controls. Invoices travel between certified platforms, which also report data to the authority in near real time. France's reform, with approved platforms (plateformes agréées) and a public portal, follows this pattern.
• Peppol network exchange. Invoices travel over Peppol, an open network where each party connects through an accredited access point. Belgium uses Peppol as the default channel for its B2B mandate, and many countries use it for invoices to government.

The European semantic standard

Inside the EU most mandates point to EN 16931, the European standard that defines the core content of an electronic invoice (a semantic model) and allows a small set of syntaxes, mainly UBL and UN/CEFACT Cross Industry Invoice (CII). National formats build on it: Germany's XRechnung, the hybrid PDF-plus-XML formats ZUGFeRD and Factur-X, and Peppol BIS Billing 3.0. Knowing that they share one semantic model helps testers: the same fields (seller VAT ID, buyer reference, line net amount, VAT category) appear in every format, under different tags.

For the SAP team the change shows up in concrete places. Master data gains new fields that must be right before the first invoice: tax registration numbers, network identifiers, routing codes, and sometimes the customer's own invoicing channel. Billing documents gain a second life as eDocuments with their own statuses, so finance needs a daily view of what was sent, accepted and rejected. Cancellations and credit memos follow legal rules, not just accounting ones. And the test plan gains an external dependency: the authority's or provider's test environment, with its own availability and rules.

Why Contoso cares

Contoso Motor Co. sells mainly in the United States, which has no federal B2B e-invoicing mandate. But the Wave 2 acquisition of Alternadores del Norte S.A. de C.V. (company code 1910, Monterrey) brings a company that must issue CFDI invoices in Mexico from day one in SAP S/4HANA. Dan, the finance process owner, also wants to understand Europe because sales is considering a French distribution entity for aftermarket customers; in this course that is a clearly labeled what-if, since Contoso has no European subsidiary.