FICO India e-Invoicing Part 2: SAP Document and Reporting Compliance and the eDocument Cockpit

📌 KEY POINTS
✅ SAP Document and Reporting Compliance creates an eDocument for each in-scope source document and tracks its status.
✅ The eDocument Cockpit (transaction EDOC_COCKPIT) shows submitted, pending, rejected and cancelled documents with their IRP responses.
✅ Connection to the IRP runs through SAP's cloud integration content or a GSP/ASP partner, depending on the architecture chosen.
✅ IRN, acknowledgment number and QR data are stored against the eDocument and used for invoice output.
⚠️ An eDocument stuck in 'pending' is a customer invoice that cannot be sent — monitor it like a failed payment.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 explained the legal model. Part 2 shows how SAP implements it and where you look when something fails.

━━━━━━━━━━━━━━━━━━━━
▶ 1. EDOCUMENTS
When a billing document or FI invoice of an in-scope type is posted, SAP Document and Reporting Compliance creates an eDocument linked to it. The eDocument holds the mapped data, the submission status and the response from the authority. Each country has its own eDocument types; for India these cover e-invoices and e-way bills. The source document is unchanged; the eDocument is its compliance companion.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SUBMISSION ARCHITECTURE
Companies either use SAP's integration content on SAP BTP Integration Suite to connect to the IRP, or connect SAP to a GST Suvidha Provider or Application Service Provider who submits on their behalf. Either way, credentials and certificates are managed outside the billing process, and the interface must handle timeouts and retries without creating duplicate registrations.

━━━━━━━━━━━━━━━━━━━━
▶ 3. THE EDOCUMENT COCKPIT
EDOC_COCKPIT lists eDocuments by company code, country and status. From there users submit or resubmit, see error messages returned by the IRP, display the IRN and QR data, and trigger cancellation where allowed. It is the daily workplace of whoever owns e-invoice exceptions.

━━━━━━━━━━━━━━━━━━━━
▶ 4. OUTPUT AND DATA STORAGE
Once the IRN is received, the invoice form reads the IRN, acknowledgment details and QR content stored with the eDocument and prints the QR code. Output determination should check that the eDocument is in a successful status before sending to the customer. The signed data should be retained per statutory record-keeping rules.

━━━━━━━━━━━━━━━━━━━━
▶ 5. WHAT TO MONITOR
Monitor counts of pending, rejected and cancelled documents per business place every day, the age of the oldest pending document, and interface errors such as certificate expiry or authentication failures. Most rejections are data errors — invalid GSTIN, missing HSN, wrong pin code — which should be fixed in master data, not only on the single document.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Post an in-scope billing document and find its eDocument in the cockpit.
2. Inspect the mapped data and the IRP response.
3. Simulate a rejection (e.g. invalid buyer GSTIN in test) and resubmit after correction.
4. Set up a daily monitoring report by status and business place.

✅ CHECKPOINT: you can find any invoice's eDocument, read its status and IRP response, and resolve a rejection.

Monday morning, 600 eDocuments were pending since Saturday. The integration's digital certificate had expired over the weekend and every submission failed authentication. After renewing the certificate and resubmitting from the cockpit, all invoices registered. Certificate expiry dates now sit in the operations calendar with 30-day alerts.

• Fixing rejected documents one by one without fixing master data.
• No monitoring of pending documents.
• Certificates and credentials without expiry tracking.
• Output sent regardless of eDocument status.

• Daily cockpit review with named owners.
• Root-cause rejections back to master data.
• Idempotent retries that check for existing IRNs.
• Expiry alerts for certificates and credentials.

Interviewers expect you to know where e-invoice status lives in SAP (eDocument and EDOC_COCKPIT), how rejections are handled, and how to avoid duplicate IRNs on retry.