Electronic invoicing is the structured electronic exchange of invoice data between a supplier and a buyer. Under the definition used in EU Directive 2014/55/EU, an electronic invoice is issued, transmitted and received in a structured data format that allows automatic electronic processing. A PDF may be an electronic document, but a PDF or scan without structured invoice data is not an e-invoice under that definition.
What is e-invoicing?
E-invoicing is the structured electronic exchange of invoice data between suppliers, buyers and, where required, tax authorities. It differs from emailing a PDF because the invoice is machine-readable and may pass through a clearance platform or regulated network. Requirements vary by country, transaction type and implementation model.
This distinction explains why e-invoicing projects are more than “stop printing invoices.” They combine business data, legal rules, technical validation, transmission, status responses and operational controls.
Explainer scope: This page defines e-invoicing formats, networks and clearance models. For the SAP delivery sequence from mandate scope through cutover, use the E-Invoicing in SAP implementation guide.
Five layers that should not be confused
- Semantic model: the business meaning of fields such as seller, buyer, invoice line, tax category, amount and payment terms. EN 16931 is a European semantic model for the core elements of an electronic invoice.
- Syntax or format: the technical representation of that data. UBL and UN/CEFACT CII are examples of XML syntaxes used in European-standard implementations; national formats may differ.
- Platform: software that creates, validates, transforms, monitors or stores electronic documents. A platform is not itself the legal format.
- Network or channel: how a document moves between parties or to an authority. Peppol, a national portal and a direct authority API are different channel models. A network is not the same thing as the invoice syntax it transports.
- Regulatory model: whether the transaction is exchanged directly, reported to an authority, or submitted for validation or clearance before or around issuance. Timing and legal effect are jurisdiction-specific.
“XML-ready,” “Peppol-connected” or “using an e-invoicing platform” therefore does not by itself establish compliance. The invoice must satisfy the applicable business rules, syntax, identifiers, transmission process and lifecycle requirements.
A typical e-invoice lifecycle
- The source system creates the commercial and accounting document.
- Required data is mapped to the applicable semantic model and syntax.
- Technical and business rules are validated before transmission.
- The document is sent through the prescribed network, provider, portal or API.
- Authority and recipient responses are captured and matched to the source document.
- Accepted, rejected, cancelled or corrected states are reflected in operations and retained as evidence.
The response can be as important as the outbound document. A successful HTTP call, for example, may only prove technical delivery; it does not necessarily mean legal acceptance. Teams need to model each status and decide what releases billing, posting, payment collection or correction work.
What e-invoicing means for SAP
In an SAP landscape, invoice data may originate in billing, financial accounting, procurement or an external application. The implementation must preserve a controlled relationship between the source business document, the electronic payload and every authority or recipient response.
SAP Document and Reporting Compliance offers capabilities for electronic documents, monitoring, corrections and statutory reporting. Depending on the SAP product and release, users may work with the eDocument Framework and eDocument Cockpit or with applications such as Manage Electronic Documents. SAP Document and Reporting Compliance, cloud edition can participate in supported scenarios. Exact country coverage, prerequisites and supported source systems must be confirmed in current SAP documentation.
SAP Integration Suite is an integration platform as a service that can connect applications, APIs, events and B2B processes. It may be part of an approved e-invoicing architecture, but it is separate from SAP Document and Reporting Compliance and should not be described as a universal compliance engine or ABAP add-on runtime.
Readiness questions before selecting a solution
- Which legal entities, transaction types and counterparties are in scope?
- Is the obligation B2G, B2B, B2C or a combination, and when does each phase apply?
- Which semantic model, syntax, local extension, identifiers and code lists are mandatory?
- Which channel is prescribed, and are certified or accredited service providers required?
- Does the authority clear, validate, report, or merely receive the invoice?
- Which SAP product, release and source process owns the invoice and its corrections?
- How will acknowledgements, rejection, cancellation, contingency and archive evidence be controlled?
A useful fit assessment answers these questions with citations to current law, authority specifications and product documentation. It avoids treating a format, network or product name as a substitute for the complete compliance process.
Sources
- EUR-Lex — Directive 2014/55/EU on electronic invoicing in public procurement
- European Commission — What is eInvoicing
- European Commission — European standard on eInvoicing
- OpenPeppol — eDelivery specifications
- SAP — SAP Document and Reporting Compliance
Verified on: 10 July 2026. Scope, dates, formats and channels are jurisdiction-specific and may change.
Need to turn a mandate into an SAP design? Contact S4FN for a country-, process- and release-specific readiness review.