Field Notes · 18 May 2026
Who should own an aged matching exception?
Ownership gaps keep invoices warm in the queue long after the matching rule has done its job.
An invoice matching application can classify a hold perfectly and still leave it untouched for ninety days. Classification without ownership is decoration.
Common ownership blanks
- Missing goods receipt — warehouse believes purchasing should cancel the PO; purchasing waits on the warehouse.
- Price dispute — buyer and supplier negotiate by email while AP remains the ticket owner inside the application.
- Vendor master mismatch — bank or tax details block payment after a technical match; master-data stewards are not in the exception workflow.
What healthy queues show
Reason codes map to named roles. Ageing reports are reviewed weekly with those roles present. Force-match is rare and logged. When Online Reason assesses exception queues, we spend as much time on the human path as on the rule that created the hold.
A small experiment
Pick the oldest twenty exceptions. For each, write one sentence naming the next human action and the person who can take it. If the sentence is vague, the application’s workflow — or your RACI — needs attention before more configuration work.