Lesson 3 of 5
eDocuments in SAP
10 min
Listen to this lesson
SAP's answer to e-invoicing mandates is SAP Document and Reporting Compliance. In SAP S/4HANA it lives in the application as a set of features you activate per country and process; for many scenarios it works together with a BTP service, SAP Document and Reporting Compliance, cloud edition, which talks to networks, platforms and authorities.
What an eDocument is
When you post a supported source document, such as a billing document from sales or an accounting document from finance, the system extracts the data that must be transmitted and saves it as an entry in a database table. That entry is the eDocument. It has its own process (for example Mexico eInvoice, or France's Domestic Customer Invoice), its own status, its own history and logs, and the XML files it produces and receives. The billing document and the eDocument are linked but separate: a billing document can be correct while its eDocument is in error.
Where you work with eDocuments
Two tools show eDocuments in SAP S/4HANA 2025. The eDocument Cockpit (transaction EDOC_COCKPIT; on SAP Easy Access under Cross-Application Components > Document and Reporting Compliance) displays eDocuments created from source documents, submits them, creates those that couldn't be created automatically, and monitors their status with follow-up actions. The SAP Fiori app Manage Electronic Documents offers a similar function with a newer interface: a landing page with counts by completion status (In Process, Error, Completed), a flow chart of process statuses, an error analysis page that groups errors by category and code, and document details with history, logs and attachments. SAP notes that some country-specific tasks are available in the cockpit before the app supports them, so check the supported tasks for your country.
| Need | eDocument Cockpit (EDOC_COCKPIT) | Manage Electronic Documents app |
|---|---|---|
| See all eDocuments for a process | Yes, in an ALV list per process | Yes, with counts by status |
| Group errors by category and code | Interface and application logs per document | Error Analysis page, where enabled for the country |
| Status flow overview | Not available | Flow chart of process statuses |
| Manual creation in special cases | Inside the cockpit | Create Electronic Documents Manually - Special Cases app |
| Country coverage | Broader in some countries | Growing; check supported tasks |
Processes and statuses: the Mexico example
Each country has processes with their own statuses and actions. In Mexico, you use the Mexico eInvoice process in the eDocument Cockpit. When Alternadores del Norte posts an invoice, the system creates an eDocument; you submit it, and SAP Integration Suite applies the digital signature and sends it to the PAC. The PAC validates it and forwards it to the SAT; if approved, the response carries the stamp, certificate data and UUID, the eDocument status is updated, and you can send the CFDI to the customer from the cockpit. If the PAC rejects it, you correct the error and resubmit, or cancel the eDocument.
Cancellation is its own path. If the eDocument is still in a status such as eDocument Created, Sending Requested or Rejected by Tax Authorities, the system can cancel it directly. For an approved invoice you choose Cancel eDocument with a reason code; reason code 01 requires the UUID of the substitute invoice, and some cancellations need the customer's acceptance, during which the eDocument shows Awaiting Cancellation Response. When you cancel an eDocument, cancel the source document too to keep the books consistent.
Setting it up: the main configuration steps
- Activate the features for the country, following SAP's requirements for enabling Document and Reporting Compliance features; keep the SAP Notes for the eDocument framework current.
- Technical settings: assign interface versions and mapping classes that turn source documents into the legal XML; define process step determination and interface determination for each step.
- Accounting documents: activate the business transaction event and register function modules so FI postings create eDocuments.
- Communication: integrate with the cloud edition or SAP Integration Suite, depending on the country process, and set up company and business partner master data such as tax numbers, Peppol participant IDs or French routing codes.
- Jobs: schedule background processing so creation, submission and status updates don't depend on someone pressing buttons.
The cloud edition
SAP Document and Reporting Compliance, cloud edition is a BTP service, available in the Cloud Foundry and Kyma environments with an enterprise global account. You activate a process per compliance task in its Activate Process app. Two matter most here. Peppol Exchange makes the cloud edition your Peppol access point; SAP lists it for SAP S/4HANA and SAP S/4HANA Cloud Private Edition for customer and supplier invoices in countries including Austria, Belgium, Denmark, Finland, France, Germany, Ireland, Luxembourg, the Netherlands, Norway and Sweden, among others. E-Invoices and E-Reports (France) lets the cloud edition act as your approved platform (PA) for France; SAP notes it is available only for subaccounts in the Europe (Rotterdam, cf-eu02) region. SAP also states clearly that customers remain responsible for their own compliance and for registering in networks and directories.
What would you do?
Lucía reports that billing document 90002113 for Flotillas Monterrey was posted correctly, but the customer says it has no valid invoice. What should she check first?
- An eDocument is a separate record created from a source document; it carries the legal XML, status and logs.
- Work in the eDocument Cockpit (EDOC_COCKPIT) or the Manage Electronic Documents app; check country support for each.
- In Mexico, the Mexico eInvoice process sends signed XML to the PAC and stores the SAT's UUID; cancellations need reason codes.
- The cloud edition on BTP provides Peppol Exchange and, for France, the approved platform process (cf-eu02 region only).
Check your understanding · not graded
Lesson check
1. What is an eDocument in SAP Document and Reporting Compliance?
2. Which transaction opens the eDocument Cockpit?
3. A Mexican invoice is cancelled with reason code 01. What must the cancellation include?
4. In which BTP region does SAP offer the E-Invoices and E-Reports (France) process of the cloud edition?