EDOC_COCKPIT — eDocument Cockpit

Legal e-invoicing and e-reporting require that each relevant business document is sent to an authority or provider and that the response is stored. The eDocument framework creates an eDocument per source document and tracks its lifecycle. The cockpit gives users one place to see which documents were accepted, which are pending and which failed, and to trigger the next action.

Billing and compliance teams use it daily wherever e-invoicing applies, for example in India for invoice registration and e-way bills. It is especially important around go-live of a new country requirement, at month end and whenever invoice output to customers depends on a registration number.

Filter by country, company code, process and status. Open failed documents to read the error returned, correct the source document or master data, and resend. Use the cancellation actions where allowed, within the time limits of the regulation. Keep monitoring the cockpit after configuration changes, because errors often appear in groups.

For a billing document subject to e-invoicing, the cockpit should show one eDocument with an accepted status and the registration data returned, such as the IRN in India. The invoice output sent to the customer should carry the same data. Counting accepted, failed and pending documents per day gives a simple control that nothing was missed.

SAP Document and Reporting Compliance is the S/4HANA solution for e-documents; scope and integration options depend on country, release and whether a provider or SAP's own connectivity is used.

Most cockpit work is caused by master data and timing.

Owned jointly by billing operations, who process daily rejections, and the tax or compliance team, who decide on corrections and cancellations. IT supports connectivity, certificates and configuration, and should be alerted when many documents fail at once.