Invoices and purchase orders can live in one system or two, and the interesting risk in both arrangements is the same: the connection between them failing without anybody noticing. In two systems it is an integration going stale. In one system it is orders or receipts not being entered. Both produce matching against incomplete data, and both are silent.
Two systems: the integration
Orders and receipts feed into payables on a schedule. When that fails, matching continues against whatever arrived last, so invoices that should match do not and somebody investigates them one at a time without realising there is a common cause. Ask what a failed sync looks like operationally and whether anybody is alerted.
One system: the missing entry
No integration to fail, and the same outcome when orders are not raised or receipts are not recorded. The system cannot tell the difference between a purchase with no order and an order somebody forgot to enter, so the exception looks identical. Only counting exception reasons by department reveals the pattern.
What to monitor either way
The share of invoices arriving with both an order and a recorded receipt, tracked weekly. A sudden fall is either an integration problem or a behaviour change upstream, and either way it is worth knowing within days rather than discovering through a growing exception queue a month later.
Questions people ask about invoice and purchase order software
Which architecture is safer?
Neither inherently. One system removes an integration; two systems make each side replaceable. Both need the same monitoring.
How often should the feed run?
Often enough that a receipt recorded this morning is available when this afternoon's invoice arrives. Daily is usually the minimum.
What is the single best warning signal?
A fall in the share of invoices arriving matchable. It catches both failure modes.