Procure to pay: requisitions, encumbrances, and three-way match

Reference article · 6 min read

Procure to pay is the chain that connects a department's request to buy something to the payment that eventually leaves the treasury. In government that chain carries a requirement commercial systems often treat as optional: the money should be committed against an appropriation before the obligation is made, and the system should be able to show, at any moment in the fiscal year, how much of each appropriation is spent, how much is committed, and how much remains available.

That single requirement explains most of what makes government procure to pay distinctive, and most of where it goes wrong. Trouble concentrates in three places: approval routing that takes longer than the business needs, encumbrances that do not liquidate the way people expect, and match exceptions that accumulate in a queue nobody owns. What follows walks the cycle in order and explains where the controls belong.

The cycle in order

Requisition. A department states what it needs, an estimated cost, and the accounts to charge. The requisition is an internal request, not a commitment to a vendor.
Pre-encumbrance. On approval, the estimated amount reserves budget so two departments cannot spend the same dollars while sourcing is underway.
Sourcing and award. Purchasing applies the applicable method: an existing contract or cooperative agreement, quotes, or a formal solicitation, depending on dollar thresholds and the entity's procurement code.
Purchase order. The PO is the obligating document sent to the vendor. Issuing it liquidates the pre-encumbrance and creates an encumbrance for the PO amount.
Receiving. Someone other than the requester confirms what arrived, in what quantity, and in what condition.
Invoice entry. Accounts payable enters the vendor invoice and references the PO.
Match and approval. The system compares PO, receipt, and invoice, and routes anything outside tolerance.
Payment. Payment relieves the accrued liability and liquidates the remaining encumbrance for that line.

What encumbrances actually do

An encumbrance is not an expenditure and not a liability. It is a reservation of budget authority recording that the government has committed to spend. Under governmental fund accounting it reduces available balance for budgetary purposes without hitting the operating statement as expense. Reporting and disclosure conventions for encumbrances are set out in the applicable accounting standards, and practice varies by state law and local policy, so confirm treatment with your finance office and external auditor rather than assuming the software default is correct.

Three practical points matter more than the theory:

Liquidation must follow the same line it encumbered. If receiving or invoicing posts to a different account, fund, or PO line than the encumbrance, the original reservation stays open. This is the single most common cause of stale encumbrances.
Partial receipts create partial liquidations. A PO for a quantity delivered in stages should relieve proportionally, and the remainder should stay encumbered until closed.
Closing is an action, not an assumption. Someone must close short-shipped or abandoned POs. Systems do not know that a vendor stopped shipping.

Where budget checking should stop and where it should warn

Budget checking runs at several points, and the correct behavior differs at each. A reasonable default is to warn early and stop late.

Requisition. Warn. The estimate is soft, and a hard stop here trains staff to understate requests.
Purchase order. Stop. This is the obligating moment, and most jurisdictions expect appropriation to exist before obligation.
Invoice or voucher. Stop when the invoice exceeds tolerance and no budget remains. Warn when budget is available but the encumbrance has been exhausted, because the funding question is different from the match question.
Grant and project funds. Stop against the award or project budget rather than only the fiscal year appropriation, since grant periods and spending conditions rarely align with the fiscal calendar.

Define the control level explicitly: fund, department, object, or project. Checking at too fine a level produces constant overrides. Checking too loosely defeats the purpose. Log every override with a user, a timestamp, and a reason, and review the log.

Three-way match and its exceptions

Three-way match compares the purchase order, the receiving record, and the invoice on quantity and price. Where no physical receipt exists, such as many professional services, a two-way match against the PO plus a documented approval of service delivery is the practical equivalent. Some agencies add inspection or asset tagging as a fourth point for capital items.

Tolerances decide how much work the process creates. Set them by dollar and percentage together, so a small percentage on a large PO does not pass unexamined. Then design for the exceptions that actually recur:

Price variance. Invoice unit price exceeds the PO price. Route to the buyer, not to accounts payable, because only the buyer can decide whether to amend the PO.
Quantity variance. More invoiced than received. Usually a timing problem, and it resolves when receiving catches up. Hold, do not reject.
No receipt on file. Frequently a training issue in the department rather than a vendor problem.
Invoice with no PO. Track these separately and report the volume by department. Recurring after the fact purchases are a policy problem that a match rule cannot fix.
Freight, tax, and fees. Decide in advance whether these are encumbered on the PO or allowed outside tolerance, and configure accordingly.

Approval routing and thresholds

Routing rules should reflect delegated authority as it is written, not as it has accumulated. Map the thresholds in your procurement code and administrative policy, then build routing to match, including commodity or category exceptions such as technology, professional services, and anything involving personally identifiable information.

Keep the number of approval steps small. Each additional approver adds delay and rarely adds control if the earlier approvers already reviewed funding and compliance. Set out of office delegation, automatic escalation after a defined period, and a queue view so no approval depends on one person's inbox. Measure cycle time by step so you can see where requisitions actually wait.

Year end and how to start

Before year end, run an aging report of open encumbrances and force a decision on each: receive, close, or roll forward. Confirm with your finance office which encumbrances may lapse and which carry forward, since that depends on state law, local ordinance, and fund type. Reconcile encumbrance detail to the general ledger control before rolling, because rolling a balance that does not tie forward carries the discrepancy into the new year.

When configuring or replacing a system, ask vendors to demonstrate with your data rather than describe: partial receipt and partial liquidation, a PO amendment that increases an encumbrance and re-runs the budget check, a match exception routed to a buyer and resolved, a budget override with its audit record, and the year-end roll with its reconciliation report. Require in the contract that configuration of thresholds and tolerances belongs to the agency without a change order, and that encumbrance and match data be exportable in full.

HQT works with state and local agencies on enterprise financial and procurement systems, including workflow configuration, integration, and reporting.

Frequently asked questions

What is the difference between a pre-encumbrance and an encumbrance?

A pre-encumbrance is created when an approved requisition reserves estimated budget while purchasing is still sourcing the goods or services. An encumbrance is created when the purchase order is issued and the government is actually committed to a vendor. Issuing the PO normally liquidates the pre-encumbrance and replaces it with the encumbrance at the PO amount.

Why do purchase order encumbrances not liquidate correctly at year end?

The most common cause is that receiving or invoicing posted to a different account, fund, or purchase order line than the one that was encumbered, so the original reservation stays open. Short shipments and abandoned orders also leave balances that nobody closes, because a system cannot know a vendor stopped delivering. Run an aging report of open encumbrances before year end and force a receive, close, or roll decision on each one.

When should budget checking block a transaction instead of just warning?

A reasonable default is to warn at the requisition, where the estimate is soft, and to stop at the purchase order, which is the obligating moment. Stop again at invoice entry when the amount exceeds tolerance and no budget remains. Grant and project funds should be checked against the award or project budget rather than only the annual appropriation, since grant periods rarely match the fiscal year.

Is a three-way match required for services where nothing is physically received?

No. For professional services and similar purchases, a two-way match against the purchase order combined with a documented approval that the service was delivered serves the same control purpose. The key is that someone other than the person who requested the purchase confirms performance before payment. Configure the system so those purchase orders are flagged as service type and do not sit in an exception queue waiting for a receipt that will never exist.

How should we set match tolerances so accounts payable is not buried in exceptions?

Set tolerances using a dollar amount and a percentage together, so a small percentage variance on a large purchase order still gets reviewed. Decide in advance whether freight, tax, and fees are encumbered on the purchase order or allowed to pass outside tolerance. Then route each exception type to whoever can actually resolve it: price variances to the buyer, quantity timing differences to receiving, rather than all of them to accounts payable.