Lesson 6 of 6
When the government is the partner
8 min
Listen to this lesson
Bilateral EDI is an agreement between two companies. E-invoicing mandates add a third party with no interest in negotiation: the tax authority. In a growing number of countries the invoice must be issued in a prescribed format, through a prescribed channel, and sometimes approved by the authority before it legally exists. That changes outbound invoicing from "send an 810 the customer can read" to "produce an electronic document the government accepts, then deliver it".
Three models
| Model | How it works | Examples | What changes in SAP |
|---|---|---|---|
| Clearance | The authority or an authorized provider validates and stamps each invoice before it is valid | Mexico (CFDI with an authorized certification provider, PAC) | Invoice is not final until the stamp returns; the stamp ID must be stored and printed |
| Platform or network exchange | Invoices travel in a structured format through registered platforms or a network such as Peppol | France from 1 September 2026 via registered platforms; Belgium Peppol B2B from 2026; Germany issuance phased in from 2027 | Format (UBL, CII, Factur-X) and access point or platform connectivity |
| Bilateral EDI without mandate | Partners agree formats; no authority in the flow | United States today | Classic IDoc and 810; voluntary frameworks only |
In SAP S/4HANA, the standard answer is SAP Document and Reporting Compliance. It creates an eDocument from a source document such as a billing document, converts it into the legally required format, sends it through the required channel (for example an authorized provider, a government platform, or a Peppol access point via SAP Business Network or SAP Integration Suite), and tracks the authority's response. The eDocument has its own status and monitor, separate from the billing document and from any IDoc.
Where this hits Contoso
Contoso's US business has no federal e-invoicing mandate, so the 810 to Great Lakes Fleet Services stays a bilateral EDI matter. Wave 2 changes that. When Contoso acquires Alternadores del Norte S.A. de C.V. and loads it as company code 1910 (MXN, plant 1910 Monterrey), every invoice from 1910 to Mexican customers such as Flotillas Monterrey S.A. de C.V. must be a CFDI: an XML document certified by an authorized provider (PAC) before it is valid. SAP S/4HANA 2025 supports this through Document and Reporting Compliance for Mexico, with eDocument processes for invoices and payments, and the CFDI's UUID flows into accounting reports.
For testers and integration teams, the shift is significant. The monitor that matters is the eDocument monitor, not only BD87. A billing document can post, its IDoc to a customer can succeed, and the invoice can still be legally invalid because the eDocument was rejected. Test cases need the authority's rejection codes, not just SAP statuses, and cutover plans for 1910 need the certification credentials and provider connectivity in place before the first invoice.
- Since 2023Mexico CFDI 4.0The current CFDI version is mandatory; invoices need certification by an authorized provider
- 2025Germany: receivingBusinesses established in Germany must be able to receive structured e-invoices
- 2026Belgium and FranceBelgium B2B e-invoicing via Peppol; France from 1 September 2026 through registered platforms, issuance phased by company size
- 2027–2028Germany: issuingMandatory issuance phased in, larger businesses first
- Wave 2Contoso 1910 MonterreyFirst Contoso company code under a clearance mandate
What testers change
- Add the eDocument to the expected result: billing document posted, eDocument created, sent, accepted, and the stamp or acceptance ID stored.
- Test rejections on purpose: an invalid tax ID, a missing postal code or a wrong tax regime for the receiver must come back as an authority rejection that someone can fix and resubmit.
- Test cancellations: under clearance models a cancelled invoice usually needs its own authority process, not just a reversal in SAP.
- Check what the customer receives: the certified document, not only the PDF or the 810.
- Keep the provider's test environment and credentials in the test plan; certification providers often have separate test endpoints.
None of this replaces bilateral EDI where customers want it. A Mexican fleet customer may still ask for an EDI message for its own matching, sent in addition to the certified CFDI. Keep the two flows apart in design and in monitoring: the legal document comes from the eDocument, the convenience copy from the IDoc.
What would you do?
Grace asks whether Contoso can simply extend its Process Orchestration 810 mapping to send Mexican invoices from company code 1910 to Flotillas Monterrey. What is the right answer?
- E-invoicing mandates add the tax authority to the invoice flow: clearance, platform exchange or none.
- SAP Document and Reporting Compliance creates and tracks eDocuments from billing documents, separate from IDocs.
- Contoso's US 810s stay bilateral; Wave 2 company code 1910 must issue certified CFDIs in Mexico.
- Test eDocument statuses and authority rejections, and verify mandate dates at the source when planning.
Check your understanding · not graded
Lesson check
1. What does a clearance model require before an invoice is valid?
2. Which SAP S/4HANA capability creates and tracks legally required electronic invoices?
3. Why does Contoso's Wave 2 change invoicing requirements?