Ask a corporate AP team why an invoice is on hold and you'll get one of two answers: the price doesn't match the PO, or the quantity doesn't match the receipt. Those are the holds AP automation was built around — the classic matching exceptions, tidy and quantitative.
Now ask a public-sector AP team the same question. You won't get two answers. You'll get a list that runs past a hundred, and almost none of them are about price or quantity. The invoice is fine. The documentation isn't there yet.
Why public money waits on paper, not numbers
When you spend public funds, the invoice is rarely the whole story. The cost has to be substantiated — and the substantiation is a document, a signature, a form, an attendance record. The dollar figure can be perfectly correct and the invoice still can't pay, because the file isn't complete enough to defend to an auditor or a grantor.
A few of the kinds of holds that have nothing to do with matching:
- A required signature is missing — a principal's, a program director's, a board-delegated approver's.
- A list of participants hasn't been attached to a professional-development or catered-event invoice.
- Transcripts, certificates, or attendance records that prove a service was actually delivered aren't on file.
- A grant-required form — the cost is allowable, but the documentation the funder mandates isn't attached.
- A contract or agreement reference needs to be linked before the spend is authorized.
- Tax-exempt or eligibility documentation has to be confirmed for the specific program paying.
There are dozens more, and they're organization-specific. The point isn't the exact list — it's the shape of the problem. These are documentation-driven holds, and a system that only understands price and quantity is blind to every one of them.
Why generic automation can't see these
Price and quantity holds are easy to automate because the system has both numbers and can compare them. Documentation holds are different: the system has to know that a human needs to attach or confirm something that isn't a number at all. There's no PO line to match against "the participant list," no receipt to reconcile with "the principal's signature."
So generic AP tools do one of two unhelpful things. Either they have no concept of the hold and the invoice flows through to payment missing its required documentation — a compliance problem. Or the invoice simply stalls with no reason recorded, while AP tries to remember why and emails around to chase it. Either way the knowledge of what this invoice is waiting on lives in a person's head, not in the system.
Make the hold a first-class, documented thing
The fix is to treat documentation holds as real, named, trackable states — not as the absence of progress. A well-designed AP layer lets the organization:
- Define its own hold reasons. The list of "why this can wait" is the customer's to maintain, because only the district or agency knows which documents its programs and grants require. The set should be open-ended — well past a hundred entries — and editable without a code change.
- Place a specific, named hold on an invoice. Not "stuck," but "waiting on participant list" or "principal signature required." The reason is recorded on the record, visible to anyone who opens it.
- Route the invoice to whoever can resolve it. A missing signature goes to the signer; a missing participant list goes to the program owner; a grant form goes to the grant administrator. The hold reason determines the destination.
- Track and report on holds. Finance can see, at any moment, how many invoices are waiting, on what, and for how long — which turns a pile of stuck paper into a managed queue.
- Clear the hold and resume cleanly. Once the documentation is attached, the invoice comes off hold and continues through approval and posting without re-keying.
The shift is from "the invoice mysteriously isn't moving" to "the invoice is on a named hold, owned by a named person, for a recorded reason." That's the difference between a chase and a workflow.
Route around the hold, don't let it stall everything
A documented hold also lets the rest of the work continue. An invoice waiting on a transcript shouldn't block the funding line that's already substantiated, and a hold on one document shouldn't hide the invoice from the person who can resolve it. The right model puts the held invoice in front of exactly the person who can clear it — with the reason attached — and keeps it out of everyone else's queue until it's ready.
It's the documentation cousin of confirming goods were actually received before an invoice pays — which we cover in in-workflow goods receiving on Oracle EBS. Receiving answers "did we get it?"; documentation holds answer "can we prove we're allowed to pay for it?" Public-sector AP needs both.
Where EZ Cloud fits
Modeling the hundred-plus reasons a public-sector invoice waits — and routing each held invoice to the person who can clear it — is exactly the kind of operational reality that years of real Oracle public-sector AP work teaches you to design for, well beyond the price-and-quantity holds generic tools stop at. EZ Cloud lets the customer define its own documentation-driven hold reasons, places named holds with a recorded reason, routes each to its owner, and resumes the invoice cleanly once the file is complete — all before it posts natively into Oracle. It's part of the Education on Oracle EBS solution and built on our Oracle EBS & Fusion integration; the broader picture of why public money breaks corporate AP assumptions is in AP automation for K-12 and public-sector finance.
If your AP team is chasing missing documents by email and keeping the reasons in their heads, the constraint isn't your ERP — it's that the holds that actually govern public-sector AP were never modeled. That's a fixable gap, and it's the one we built for.