Testing and signing off a country

An e-invoicing go-live has a hard edge that ordinary releases don't: the first invoice after go-live is a legal document. If it's wrong, the customer can't deduct VAT, the company may be fined, and in clearance countries the invoice may not exist at all in the authority's eyes. Testing must therefore prove the legal path end to end, the failure paths, and the reconciliation that shows nothing slipped through.

Contoso's real case: Alternadores del Norte goes live with CFDI

In Wave 2, Alternadores del Norte's data is loaded into SAP S/4HANA as company code 1910 and its first invoices will be posted there. The largest customer is Flotillas Monterrey S.A. de C.V., and the main product is ADN-200. Priya is the test lead, Lucía (the Monterrey order-to-cash key user) owns order-to-cash testing, Dan signs off finance, and a Mexican tax adviser confirms legal content. The PAC provides a test environment; nothing in testing is sent to the PAC's production service.

The reconciliation that matters most

The single most valuable check is completeness: every invoice-relevant source document in the period has an eDocument, and every eDocument has reached a final status. Count billing documents and accounting documents for company code 1910 by day, count eDocuments by process and status, and investigate every difference. An invoice without an eDocument is an invoice the tax authority never saw; an eDocument stuck in error is a customer who can't book its purchase. Repeat this daily during hypercare.

What-if: the same discipline for France

If Contoso's what-if French entity went live, the test set would look different but the discipline would be the same. Receiving comes first, because every company must be able to receive from 1 September 2026: test that supplier invoices arrive through the platform and create eDocuments for Domestic Supplier Invoice processing. Then test issuing through the Domestic Customer Invoice process (eDocument types such as France eInvoice and France Credit Memo), validation of customers against the public directory with the online validation feature, the e-reporting lists in the Run Statutory Reports app, and payment data for services. Each needs its own evidence.

Hypercare: the daily routine

Go-live is the start of the riskiest month. During hypercare Contoso runs a short routine every morning for company code 1910: count yesterday's billing documents and eDocuments and explain differences; work every eDocument in error with the owner named in the runbook; check that background jobs for submission and status updates ran; look for cancellations waiting for a customer's answer; and confirm the PAC certificate and credentials are not close to expiry. Lucía's team in Monterrey owns the business errors, Theo's team the technical ones, and Dan reviews the summary weekly until the error rate is stable.

Evidence and sign-off

• The legal requirements list from the tax adviser, with each requirement mapped to a test case.
• For each test case: the source document number, the eDocument status history, the XML sent and received, and the provider's response or UUID.
• The daily reconciliation of source documents to eDocuments for the final test cycle, with zero unexplained differences.
• Proof of the failure paths: a rejection corrected and resubmitted, a cancellation, an outage recovered.
• Background jobs scheduled in production, with an owner and a monitoring routine.
• Production master data checks: company tax registration, customer tax IDs, and network or directory registrations.