A customer who deregisters from VAT after you have built their treatment into a recurring billing run will break every invoice you send them — and you will find out from a transmission rejection, not from the customer.
Counterparty readiness verification is usually built as a one-time gate: confirm a customer's registration status before invoicing, confirm a supplier can transmit before onboarding, then move on. Real-time exchange makes that gate insufficient, because a counterparty's readiness does not hold stable once established. It changes, and the enterprise's own compliance is exposed every time it does. The practical response is to treat counterparty readiness as an ongoing governance relationship rather than a one-time check performed once and filed away.
Two Directions of Exposure
The exposure runs both ways across a transaction. On the customer side, a business whose registration status changes — deregistering, or moving between registration categories — after the enterprise has already built that customer's tax treatment into a recurring billing arrangement will cause every subsequent invoice to transmit against a status the authority no longer recognises. The enterprise typically discovers this only when a transmission that used to clear cleanly starts rejecting for a reason that has nothing to do with anything it changed on its own side.
On the supplier side, the same exposure appears in reverse. A supplier whose own ASP relationship lapses, or whose internal process for generating electronic invoices degrades without any external sign of it, produces a procure-to-pay process that depends on invoices meeting a standard the supplier has quietly stopped meeting. The first indication is usually a spike in exception volume — a diagnostic signal worth reading rather than absorbing as noise, distinct from the input-tax risk AP teams already carry on inbound invoices, because here the exposure sits in the counterparty's capability, not in what a single transmitted invoice states.
Proportionate, Not Continuous
Ecosystem governance means applying the same proportionality principle that governs real-time connectivity investment to counterparty monitoring: concentrating attention on the small number of counterparties whose transaction volume or transaction complexity means their own readiness materially affects the enterprise's compliance position, rather than spreading a fixed monitoring effort evenly across a long tail of low-volume relationships where the exposure was never significant. A counterparty responsible for a handful of invoices a year does not need the same standing scrutiny as one driving a recurring billing arrangement worth a material share of transmitted volume.
This is where exception data earns its keep as a governance instrument rather than a queue to clear. A rising rejection rate concentrated on one customer, or a supplier whose invoices increasingly need correction before they can be processed, is the signal that a counterparty's readiness has moved since onboarding — and it arrives faster through a monitored exception pattern than through any periodic re-verification exercise.
The Walls the Process Doesn't Stop At
An order-to-cash process rebuilt correctly still depends on customers who can receive and act on a structured electronic invoice. A procure-to-pay process rebuilt correctly still depends on suppliers who can generate one correctly in the first place. Neither redesign is complete on its own terms, because the enterprise's own process transformation is incomplete if it stops at its own walls. A proportionate, standing process for monitoring material counterparties is what closes that gap. The alternative is discovering the dependency transaction by transaction, as exceptions accumulate into a pattern nobody was watching for.