Status
All services operational.
Three of these are somebody else's uptime and are marked as such. A status page that lists only its own components is a status page that will be green on the morning nothing works.
Forwarded invoices, panel uploads and the mobile capture endpoint.
Google Document AI. Their uptime, not ours — when it degrades, documents fall back to a single reader and the interface says so.
Azure AI Document Intelligence. The independence between the two is the mechanism, so both are listed separately.
Arithmetic, check digits, known values and template memory. Runs in-process; no external dependency.
Duplicate, bank account, delivery match, price drift, arithmetic, identifiers, due dates.
Posting, corrections and the period close.
Structured invoices in and out. Documents that arrive this way skip both readers entirely.
CSV, Excel and UBL. Refuses while the period has blocking items.
Everything documented on /docs/api.
Incident history
Elevated latency, 41 minutes
First reader
Extraction queued rather than failed. Documents processed with the second reader alone and were marked single-source; 63 fields were re-settled automatically once the first reader recovered.
Delivery delays, 3 hours
e-Invoice network
Inbound structured invoices arrived late across the network. Nothing was lost; the affected documents carry their original issue dates rather than their arrival times.