# Who is responsible for catching surcharge persistence? > Surcharge persistence sits between AP, procurement and contract owners. Here is who actually owns catching it, and why the gap forms. Read the full guide. Source: https://valuexpa.com/insights/who-is-responsible-for-catching-surcharge-persistence Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. Surcharge persistence, a fuel or peak surcharge that keeps billing after its trigger condition ends, is one shape that gap takes. The honest answer to who catches it is nobody, by default. It falls between three job functions, each of which has a good reason to assume someone else is watching the surcharge line. ## Executive Summary Surcharge persistence survives because it is nobody's single job to catch. AP pays against the purchase order and the invoice total, not against the surcharge's own expiration condition. Procurement negotiates the trigger clause and then moves to the next contract. The contract owner in the business unit rarely sees the invoice at all. Each function does its assigned job correctly, and the surcharge still keeps billing. The mechanism is a handoff failure, not a competence failure. A surcharge clause lives in a contract PDF. The invoice line that charges it lives in the ERP. Three-way matching checks the invoice against the PO and the receipt; it does not read the contract PDF and does not test whether the fuel index or the peak-season window that triggered the surcharge is still active. What changes it is assigning the check explicitly, to a role or a control, rather than assuming it falls out of the existing process. That means someone owns reconciling active surcharge clauses against the invoices billing them, on a schedule, with the contract terms as the reference document. ## 1. Why does surcharge persistence fall through the cracks? **Surcharge persistence falls through because the three functions closest to it each have a narrower job. AP validates that an invoice matches a purchase order and a received quantity. Procurement negotiates the surcharge clause once, at contract signing, then moves on. The business unit that ordered the freight or service sees a total cost, not a line-item trigger condition. None of the three has 'confirm this surcharge is still owed' written into their job.** Three-way matching is built to catch quantity and price errors against a PO. It was never designed to test a time-based or condition-based clause sitting in a separate contract document. A surcharge that matches its own invoice history perfectly, the same rate, the same line description, passes every automated check AP runs. Procurement's incentive structure reinforces the gap. A negotiated rate card is treated as done once signed. Nobody schedules a return visit to the fuel index or the peak-season calendar that justified the surcharge in the first place. The business unit is furthest from the contract language and closest to the invoice total. A manager approving a freight bill sees whether the number looks reasonable against last month, not whether a named trigger condition in a rate schedule has actually lapsed. ## 2. What does AP actually check on a surcharge line? **AP checks that a surcharge line matches the purchase order, the unit price on file, and the receipt or delivery record. It does not check the underlying condition that made the surcharge legitimate in the first place, because that condition lives in a contract, not in the ERP fields AP's matching logic reads. A surcharge can pass every field-level check AP runs and still be billing after its trigger has ended.** AP's control surface is the ERP: the PO, the goods receipt, the invoice. A three-way match confirms these three documents agree with each other. That is a real control, and it catches quantity errors, duplicate invoices, and price mismatches against the rate loaded in the system. What it cannot do is reach outside the ERP into the contract PDF where the surcharge's actual trigger, a fuel index threshold, a named peak season window, a capacity shortage clause, is defined. If that trigger has lapsed but the vendor's billing system has not been updated, the invoice still matches the PO on file. Nothing in AP's normal workflow flags it. This is a scope boundary, not a lapse. Extending AP's mandate to include contract-condition testing means giving them the contract terms in a form their matching process can actually use, not asking them to read PDFs on top of an already high invoice volume. ## 3. Does procurement own this after the contract is signed? **Procurement owns negotiating the surcharge clause, but ownership of monitoring whether the clause still applies typically ends at signature unless a renewal or review cadence is written into the process itself. Once a contract is executed and loaded, procurement's attention moves to the next negotiation. A surcharge condition change six months into a two-year contract has no natural point where anyone in procurement is looking at it again.** A rate card negotiation is a project with a defined end: signature. Procurement teams are measured on rates secured, contracts closed, and the next sourcing event, not on ongoing surveillance of clauses inside contracts already signed. That structure makes sense for most contract terms, which do not change mid-term. Surcharges are the exception: their entire premise is a condition that moves, a fuel price, a seasonal window, a capacity constraint, and the contract is only correct for as long as that condition holds. Without an explicit review point built into the contract calendar, a surcharge clause gets the same one-time attention as a fixed rate that actually stays fixed. See how this differs from a legitimate price increase in margin drift vs. legitimate price increases: how to tell them apart. ## 4. Who should own catching it, in practice? **In practice, catching surcharge persistence needs an owner independent of both AP's transactional workflow and procurement's negotiation cycle: someone or some control tasked specifically with reconciling active surcharge clauses against what is currently billing, on a recurring schedule, using the contract as the reference document rather than the invoice history. Without that explicit assignment, the check does not happen anywhere.** The role does not need a new headcount. It needs an explicit mandate given to an existing one: a controller, a contract compliance function, or a periodic audit, whichever already has both invoice access and contract access. The defining feature of this role is that it starts from the contract and asks whether the invoice still matches it, rather than starting from the invoice and asking whether it matches the PO. That is the reverse direction from what AP's matching process runs. Where this responsibility sits organizationally matters less than whether it exists at all and runs on a schedule tied to when surcharge conditions actually change, not to the AP close calendar. ## 5. How is surcharge persistence different from other drift types to catch? **Surcharge persistence is a condition problem, not a document-matching problem, which is what makes it harder to assign than most drift types. A duplicate payment or a missed credit memo shows up by comparing documents that already exist. Surcharge persistence requires knowing a real-world or contractual condition has changed and then checking that the billing changed with it, which needs someone actively watching a clause, not just reconciling paperwork.** A [duplicate payment](/glossary/duplicate-payment) is caught by comparing two invoices against each other. A [missed credit memo](/glossary/missed-credit-memo) is caught by comparing a return or a rebate entitlement against what was actually credited. Both are static comparisons between records that already exist in the ERP. Surcharge persistence needs a third input: knowledge that the triggering condition, external or contractual, has actually changed. That input does not live in AP's systems at all. It lives in a fuel index, a seasonal calendar, or a capacity report. That structural difference is why assigning this one is harder than assigning most drift types, and why it needs a deliberate answer rather than an assumption that the existing AP and procurement processes will surface it on their own. Compare this against [accessorial charge creep](/glossary/accessorial-charge-creep), which follows a similar shape but drifts through added line items rather than a stale condition. ## 6. What does a working reconciliation process look like? **A working reconciliation process pulls every active surcharge clause from current contracts into one list, checks each clause's trigger condition against current external data or contract terms, and compares the result against what is actually billing on recent invoices. It runs on a set schedule, independent of when a contract renews or an invoice happens to look unusual, and produces a short list of surcharges to challenge with the vendor.** The list of active surcharge clauses is the starting document, built from the contract, not the invoice history. Each clause states its trigger condition explicitly: a fuel price threshold, a named date range, a capacity constraint. Checking the condition means going to the source: the fuel index the contract references, the calendar the peak-season clause names, or the capacity report if that is the trigger. This step happens outside the ERP entirely. Only after the condition is confirmed lapsed or still active does the process compare it against the invoice. A mismatch, condition lapsed but surcharge still billing, becomes a specific, documentable challenge to send back to the vendor with the contract clause attached. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. ## 7. Frequently Asked Questions (People Also Ask) ### Is catching surcharge persistence AP's job? Not under a normal three-way match. AP's matching process checks the invoice against the purchase order and receipt, which confirms the surcharge matches what was previously billed, not whether the underlying trigger condition still applies. Catching persistence needs someone comparing the invoice against the contract clause directly, a different check than AP's workflow runs. ### Should procurement monitor surcharges after signing the contract? Procurement negotiates the clause but is typically measured on contracts closed, not on ongoing monitoring after signature. Unless a review cadence is written into the contract calendar explicitly, nobody in procurement revisits a surcharge clause mid-term, which is exactly when a fuel index or seasonal trigger is most likely to have changed. ### Can accounts payable software catch a surcharge that should have expired? Standard AP matching software checks invoices against purchase orders and receipts already loaded in the ERP. It does not read contract PDFs or external condition data like a fuel index, so a surcharge that matches its own billing history passes automated checks even after its trigger condition has lapsed. ### What information does someone need to catch surcharge persistence? They need the contract's exact surcharge clause and trigger condition, the external or contractual data that determines whether the trigger is still active, and the recent invoice history for that vendor. Comparing all three is what surfaces a surcharge still billing after its condition has ended. ### Does a periodic audit catch surcharge persistence that ongoing AP review misses? A periodic audit starts from the contract and checks whether current billing still matches it, which is the reverse direction from AP's invoice-to-PO matching. That reversal is what lets it find a surcharge condition that lapsed months ago but never stopped being billed. ### Is surcharge persistence the same issue as accessorial charge creep? No. Both are freight-related drift types but they work differently: accessorial charge creep adds new fees over time, while surcharge persistence keeps an existing fee running past the condition that justified it. See accessorial charge creep for how that mechanism differs. ### How often should surcharge clauses be reconciled against invoices? The right cadence is tied to how often the underlying trigger condition can change, a fuel index moves weekly, a seasonal window has fixed dates, rather than to the AP close calendar. A quarterly reconciliation against the contract is a reasonable baseline for most surcharge types. ### Who has both the contract access and invoice access needed to do this? Usually a controller function, a dedicated contract compliance role, or an external diagnostic has access to both. AP typically has invoice access without contract-level detail, and procurement typically has contract access without visibility into ongoing invoice activity, which is exactly the gap that lets persistence continue. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary Surcharge persistence survives because it is nobody's single job to catch. AP pays against the purchase order and the invoice total, not against the surcharge's own expiration condition. Procurement negotiates the trigger clause and then moves to the next contract. The contract owner in the business unit rarely sees the invoice at all. Each function does its assigned job correctly, and the surcharge still keeps billing. The mechanism is a handoff failure, not a competence failure. A surcharge clause lives in a contract PDF. The invoice line that charges it lives in the ERP. Three-way matching checks the invoice against the PO and the receipt; it does not read the contract PDF and does not test whether the fuel index or the peak-season window that triggered the surcharge is still active. What changes it is assigning the check explicitly, to a role or a control, rather than assuming it falls out of the existing process. That means someone owns reconciling active surcharge clauses against the invoices billing them, on a schedule, with the contract terms as the reference document. ## 1. Why does surcharge persistence fall through the cracks? Surcharge persistence falls through because the three functions closest to it each have a narrower job. AP validates that an invoice matches a purchase order and a received quantity. Procurement negotiates the surcharge clause once, at contract signing, then moves on. The business unit that ordered the freight or service sees a total cost, not a line-item trigger condition. None of the three has 'confirm this surcharge is still owed' written into their job. Three-way matching is built to catch quantity and price errors against a PO. It was never designed to test a time-based or condition-based clause sitting in a separate contract document. A surcharge that matches its own invoice history perfectly, the same rate, the same line description, passes every automated check AP runs. Procurement's incentive structure reinforces the gap. A negotiated rate card is treated as done once signed. Nobody schedules a return visit to the fuel index or the peak-season calendar that justified the surcharge in the first place. The business unit is furthest from the contract language and closest to the invoice total. A manager approving a freight bill sees whether the number looks reasonable against last month, not whether a named trigger condition in a rate schedule has actually lapsed. ## 2. What does AP actually check on a surcharge line? AP checks that a surcharge line matches the purchase order, the unit price on file, and the receipt or delivery record. It does not check the underlying condition that made the surcharge legitimate in the first place, because that condition lives in a contract, not in the ERP fields AP's matching logic reads. A surcharge can pass every field-level check AP runs and still be billing after its trigger has ended. AP's control surface is the ERP: the PO, the goods receipt, the invoice. A three-way match confirms these three documents agree with each other. That is a real control, and it catches quantity errors, duplicate invoices, and price mismatches against the rate loaded in the system. What it cannot do is reach outside the ERP into the contract PDF where the surcharge's actual trigger, a fuel index threshold, a named peak season window, a capacity shortage clause, is defined. If that trigger has lapsed but the vendor's billing system has not been updated, the invoice still matches the PO on file. Nothing in AP's normal workflow flags it. This is a scope boundary, not a lapse. Extending AP's mandate to include contract-condition testing means giving them the contract terms in a form their matching process can actually use, not asking them to read PDFs on top of an already high invoice volume. ## 3. Does procurement own this after the contract is signed? Procurement owns negotiating the surcharge clause, but ownership of monitoring whether the clause still applies typically ends at signature unless a renewal or review cadence is written into the process itself. Once a contract is executed and loaded, procurement's attention moves to the next negotiation. A surcharge condition change six months into a two-year contract has no natural point where anyone in procurement is looking at it again. A rate card negotiation is a project with a defined end: signature. Procurement teams are measured on rates secured, contracts closed, and the next sourcing event, not on ongoing surveillance of clauses inside contracts already signed. That structure makes sense for most contract terms, which do not change mid-term. Surcharges are the exception: their entire premise is a condition that moves, a fuel price, a seasonal window, a capacity constraint, and the contract is only correct for as long as that condition holds. Without an explicit review point built into the contract calendar, a surcharge clause gets the same one-time attention as a fixed rate that actually stays fixed. See how this differs from a legitimate price increase in margin drift vs. legitimate price increases: how to tell them apart. ## 4. Who should own catching it, in practice? In practice, catching surcharge persistence needs an owner independent of both AP's transactional workflow and procurement's negotiation cycle: someone or some control tasked specifically with reconciling active surcharge clauses against what is currently billing, on a recurring schedule, using the contract as the reference document rather than the invoice history. Without that explicit assignment, the check does not happen anywhere. The role does not need a new headcount. It needs an explicit mandate given to an existing one: a controller, a contract compliance function, or a periodic audit, whichever already has both invoice access and contract access. The defining feature of this role is that it starts from the contract and asks whether the invoice still matches it, rather than starting from the invoice and asking whether it matches the PO. That is the reverse direction from what AP's matching process runs. Where this responsibility sits organizationally matters less than whether it exists at all and runs on a schedule tied to when surcharge conditions actually change, not to the AP close calendar. ## 5. How is surcharge persistence different from other drift types to catch? Surcharge persistence is a condition problem, not a document-matching problem, which is what makes it harder to assign than most drift types. A duplicate payment or a missed credit memo shows up by comparing documents that already exist. Surcharge persistence requires knowing a real-world or contractual condition has changed and then checking that the billing changed with it, which needs someone actively watching a clause, not just reconciling paperwork. A [duplicate payment](/glossary/duplicate-payment) is caught by comparing two invoices against each other. A [missed credit memo](/glossary/missed-credit-memo) is caught by comparing a return or a rebate entitlement against what was actually credited. Both are static comparisons between records that already exist in the ERP. Surcharge persistence needs a third input: knowledge that the triggering condition, external or contractual, has actually changed. That input does not live in AP's systems at all. It lives in a fuel index, a seasonal calendar, or a capacity report. That structural difference is why assigning this one is harder than assigning most drift types, and why it needs a deliberate answer rather than an assumption that the existing AP and procurement processes will surface it on their own. Compare this against [accessorial charge creep](/glossary/accessorial-charge-creep), which follows a similar shape but drifts through added line items rather than a stale condition. ## 6. What does a working reconciliation process look like? A working reconciliation process pulls every active surcharge clause from current contracts into one list, checks each clause's trigger condition against current external data or contract terms, and compares the result against what is actually billing on recent invoices. It runs on a set schedule, independent of when a contract renews or an invoice happens to look unusual, and produces a short list of surcharges to challenge with the vendor. The list of active surcharge clauses is the starting document, built from the contract, not the invoice history. Each clause states its trigger condition explicitly: a fuel price threshold, a named date range, a capacity constraint. Checking the condition means going to the source: the fuel index the contract references, the calendar the peak-season clause names, or the capacity report if that is the trigger. This step happens outside the ERP entirely. Only after the condition is confirmed lapsed or still active does the process compare it against the invoice. A mismatch, condition lapsed but surcharge still billing, becomes a specific, documentable challenge to send back to the vendor with the contract clause attached. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. ## Common questions ### Is catching surcharge persistence AP's job? Not under a normal three-way match. AP's matching process checks the invoice against the purchase order and receipt, which confirms the surcharge matches what was previously billed, not whether the underlying trigger condition still applies. Catching persistence needs someone comparing the invoice against the contract clause directly, a different check than AP's workflow runs. ### Should procurement monitor surcharges after signing the contract? Procurement negotiates the clause but is typically measured on contracts closed, not on ongoing monitoring after signature. Unless a review cadence is written into the contract calendar explicitly, nobody in procurement revisits a surcharge clause mid-term, which is exactly when a fuel index or seasonal trigger is most likely to have changed. ### Can accounts payable software catch a surcharge that should have expired? Standard AP matching software checks invoices against purchase orders and receipts already loaded in the ERP. It does not read contract PDFs or external condition data like a fuel index, so a surcharge that matches its own billing history passes automated checks even after its trigger condition has lapsed. ### What information does someone need to catch surcharge persistence? They need the contract's exact surcharge clause and trigger condition, the external or contractual data that determines whether the trigger is still active, and the recent invoice history for that vendor. Comparing all three is what surfaces a surcharge still billing after its condition has ended. ### Does a periodic audit catch surcharge persistence that ongoing AP review misses? A periodic audit starts from the contract and checks whether current billing still matches it, which is the reverse direction from AP's invoice-to-PO matching. That reversal is what lets it find a surcharge condition that lapsed months ago but never stopped being billed. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us