Workflow Routing

1. What does workflow routing actually control?

Workflow routing controls the path an invoice takes through human reviewers before payment: which approver sees it first, which cost center owner signs off, and what threshold triggers a second or third signature. It is a sequencing and authorization control, built to stop unauthorized spend, not a pricing control, and it does not compare invoice line items to any contract.

A typical rule set escalates by dollar amount: a small invoice needs one approver, a large one needs several signatures in sequence. Category-based rules route freight invoices to logistics and IT invoices to the technology owner.

None of these steps recompute the invoice against a rate schedule. The rule engine reads the invoice total and the category field, matches it to a threshold, and assigns an approver. It never opens the underlying contract to check whether that total is the correct one.

That is by design. Routing exists to enforce authorization, not pricing accuracy, and building both into the same rule set would require the routing engine to hold the entire contract library it currently has no access to.

2. Why does an invoice with a rate error still get approved?

An invoice with a rate schedule violation clears routing because the approver's task is to confirm budget, authorization, and a valid purchase order, not to recompute the invoice against the rate card or volume tier. Routing rules have no field for the contracted rate, so nothing in the approval step compares the billed amount to what the contract permits.

The approver sees a total and a cost center, not the underlying agreement. See margin drift vs. legitimate price increases for how that gap is diagnosed after the fact, once the invoice is already paid and archived.

The approver's screen shows a vendor name, an amount, and a cost center code. It does not show the rate card, the volume tier the account should be sitting in, or the surcharge schedule the vendor agreed to. Approval confirms the spend was authorized, not that the price was correct.

3. How is workflow routing different from a contract compliance check?

Workflow routing governs sequence and sign-off. A contract compliance check governs correctness: it matches each invoice line against the rate card, volume tier, or not-to-exceed cap the contract specifies. The two run at different layers, and a company can have mature routing with zero contract-level validation, which is exactly where drift accumulates undetected.

The routing layer decides who approves an invoice and in what order, based on amount or category. The compliance layer decides whether the billed rate matches the rate card, volume tier, or NTE cap on file. A well-built approval chain says nothing about whether the number inside it is correct.

A company can invest years into refining its routing logic, adding thresholds, escalation paths, and delegation rules, without ever adding a step that checks a rate against a contract. The two projects do not compete for budget or attention because they solve different problems, which is part of why the gap persists quietly.

4. Where does workflow routing fit in a broader AP control set?

Workflow routing sits alongside, not inside, three-way matching and contract compliance review. Each control catches a different failure: routing catches an unauthorized approver, three-way matching catches a quantity or PO mismatch, and contract compliance catches a rate, tier, or accessorial charge that departs from the agreement. None of the three substitutes for another.

Routing confirms the right person authorized the payment. Three-way matching confirms the invoice, PO, and receipt agree on quantity and price. Contract compliance confirms the billed rate matches the rate card or volume tier, the check applied by category audits like freight and 3PL audit.

An AP department can run all three controls well and still miss drift if the contract compliance layer only checks a subset of vendors or categories. Coverage matters as much as the existence of the control itself.

For the wider pattern this sits inside, start with the margin drift guide.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

Does adding more approval steps catch pricing errors?

No. More approval steps add more people confirming budget and authorization, not more checks against the contract. A rate error that clears the first approver clears every subsequent one for the same reason: none of them are checking the rate card.

Can routing rules be extended to check contract terms?

A routing engine could theoretically hold contract data, but that is a different system than most AP platforms ship with. It requires structured rate cards, tier logic, and NTE caps as inputs, which is the function of a contract compliance check, not a routing rule.

Who is responsible for catching a rate schedule violation if not the approver?

That responsibility sits with whoever owns contract compliance review, a function separate from approval routing. In many companies no one owns it explicitly, which is why a periodic audit or a dedicated compliance layer is what surfaces these errors.

Does three-way matching catch rate errors that routing misses?

Three-way matching checks that the invoice, purchase order, and receipt agree on quantity and price against what was ordered. It does not test whether the ordered price itself matches the contracted rate card, volume tier, or surcharge schedule.

Is workflow routing worth improving if it does not catch drift?

Yes. Routing solves authorization risk, which is a real and separate problem from pricing accuracy. Improving it reduces unauthorized spend; it should not be relied on to also reduce margin drift.

What is the fastest way to tell if contract compliance is missing from the AP process?

Ask whether any step between invoice receipt and payment opens the vendor contract itself, rather than the purchase order. If the answer is no, contract compliance is not part of the current control set.

Does ERP-native approval workflow differ from third-party AP automation routing?

Both are built the same way: rules keyed on amount, vendor, cost center, and category, executed before payment. Neither type stores or checks contract-level rate data as part of the approval decision.

Where should a company start if it wants to close this gap?

Start by identifying which vendor categories and contracts currently have no compliance check at all, then build or buy a matching process for those first rather than trying to cover every vendor at once.