A UAE e-invoicing dashboard showing 100% delivery success confirms one thing only: documents moved through the network correctly. Whether the books are right is a separate question entirely, answered by a different instrument.
The PEPPOL five-corner architecture means every covered transaction exists in five distinct positions at once: the enterprise's ERP, the enterprise's ASP, the exchange network itself, the buyer's ASP, and the FTA's structured data holding. A transmission dashboard tracks whether a document moved cleanly between those points — whether Corner 2 sent it, whether Corner 4 acknowledged it, whether the ASP logged a green status. A full five-corner reconciliation asks a different and much harder question: do all five positions agree, and where they differ, can every difference be explained?
Perfect agreement across all five positions is not the standard to design toward. A reconciliation built to flag every discrepancy as an error drowns in false positives — timing differences in network acknowledgement, an ASP document sitting in a pending-acceptance state, a Corner 4 confirmation that has not yet arrived. Explainability is the standard. Every difference needs an attributable cause. A difference with no known cause is a governance gap, regardless of how small it looks against total transaction volume.
The mechanics of where this goes wrong sit in four internal layers most businesses never connect to the five-corner picture. The IT architecture layer has to reconcile what the legacy systems, the middleware and the ASP each independently hold as the record of a transaction — three systems, potentially three slightly different versions of the same event. The process layer has to trace that same population from subsidiary registers through the general ledger, the trial balance and the financial statements, confirming the population that transmitted is the population the books report. The people layer has to confirm that whoever is actually running the reconciliation — often a shared service centre, executing on behalf of functional owners who carry the accountability — is escalating exceptions to the right people rather than absorbing them silently. And the data layer has to reconcile the transmission codes the ASP sent against the interpretive codes Tax originally determined, confirming the meaning the ERP assigned survived the trip through the network unchanged.
A concrete version of the gap: an invoice transmits, the ASP confirms receipt, the buyer's Corner 4 acknowledges it, and the dashboard shows green across every stage. Weeks later, when the ledger is reconciled against the ASP's transmission log, the VAT amount posted to the general ledger does not match the VAT amount the transmitted document carried — a rounding difference introduced by a middleware transformation, or a manual adjustment made in the ledger after transmission that was never reflected back into the exchange record. None of the five corners flagged anything. The document was structurally valid at every hop. The accounting position and the transmitted position had already diverged, and the dashboard had no way of knowing, because dashboard monitoring and ledger reconciliation are answering different questions.
India's GST e-invoicing experience — the largest implementation of this model anywhere — puts a number on what happens when this distinction is not designed for. The ClearTax State of Tax Assurance Report 2026 records a median mismatch-to-detection lag of roughly 200 days across the Indian population, and an input tax credit gap of around 18 percentage points between businesses running basic reconciliation and those running continuous, AI-assisted reconciliation. That gap is a cadence and ownership problem before it is a technology problem: a monthly reconciliation on a high transaction volume accepts up to a month's accumulation of exactly this kind of unexplained difference before anyone looks.
The reconciliation cadence has to be set against transaction velocity, not administrative convenience. A business processing hundreds of invoices a day that reconciles once a month is choosing to discover a gap weeks after it opened — not because the dashboard failed, but because the dashboard was never built to answer the question the reconciliation exists to ask.