Does Global Shop Solutions check invoices against terms?

Executive Summary

Global Shop Solutions checks an invoice against a purchase order and a receipt. That confirms the vendor billed for what was ordered and received, at the unit price entered on the PO line. It does not confirm the unit price itself is still correct against a rate card, that a volume tier discount fired at the right threshold, that a fuel surcharge expired on schedule, or that an earned rebate was actually credited.

The mechanism causing this is structural, not a missing setting. Contract terms for service vendors, freight carriers, staffing agencies, MRO suppliers, calibration vendors, live as unstructured documents: PDFs, addenda, side letters. Global Shop Solutions has no field for a rebate trigger tied to cumulative spend or a surcharge that sunsets after 90 days.

Three-way matching was never designed to hold that kind of clause.

What changes this is not a system replacement. It is adding a layer that reads the contract terms Global Shop Solutions cannot, and tests every invoice line against them, either as a one-time diagnostic against 12 to 18 months of history or as an ongoing control on new invoices.

1. What does three-way matching in Global Shop Solutions actually verify?

Three-way matching in Global Shop Solutions confirms three things line by line: the invoice quantity matches the purchase order quantity, the receipt confirms the goods or service arrived, and the invoice unit price matches the price entered on the PO. It stops a vendor from billing for units never ordered or never received. It does not test whether the unit price on the PO itself is the correct contract price, because the PO price is manually entered rather than pulled.

The control is a comparison of three documents already inside the system: the PO, the receipt or service confirmation, and the invoice. All three exist as structured records with quantities and prices attached to fields.

That is exactly why it works reliably for what it does. A quantity mismatch or a missing receipt is a clean binary check. The system either has matching numbers or it does not.

The boundary is the PO price field itself. Someone typed that number in, whether correctly transcribed from a rate card or not. Three-way matching validates internal consistency between PO, receipt and invoice. It does not reach outside the ERP to the contract document that should have set the PO price in the first place.

2. Why can't Global Shop Solutions read a rate card or rebate clause?

Global Shop Solutions has no data structure for a rate card, a volume tier, or a rebate clause because those terms arrive as unstructured PDFs and contract addenda, not as importable records. The ERP's pricing fields hold whatever number a buyer or AP clerk typed into the PO. If that number was correct on day one but the vendor's rate card changed six months later, nothing in Global Shop Solutions knows the two have diverged, because the system never held.

A rate card lists a price per unit, per lane, or per service tier, and often changes on a schedule: quarterly for freight, annually for staffing, mid-contract for fuel-linked surcharges. A rebate clause sets a spend threshold that triggers a credit. A volume tier resets a per-unit price once cumulative spend crosses a line.

None of these are numeric fields Global Shop Solutions stores. They are clauses in a document a procurement or finance team negotiated, then filed away.

The PO price is a snapshot of that document at the moment someone entered it. Contracts are not static. A rate card renegotiated in March is only reflected in the ERP if someone manually updates every affected PO line, and nothing forces that update to happen.

3. What kinds of drift slip past Global Shop Solutions checks?

Four drift types pass three-way matching cleanly because none of them break the PO-to-receipt-to-invoice chain: a surcharge that should have expired but keeps billing, a volume discount tier that never triggered despite qualifying spend, a not-to-exceed cap the invoice quietly exceeds, and a rebate credit the vendor owes but never issues. Each produces an invoice that matches its PO in quantity and unit price. The defect sits in a contract term the PO was never built to encode.

A fuel or accessorial surcharge added to a freight invoice under a temporary clause has no expiration field in Global Shop Solutions. If the carrier keeps billing it past the contract's stated end date, the invoice still matches its PO line for that surcharge amount.

A not-to-exceed cap on a staffing or professional services contract limits total spend on an engagement. Three-way matching checks each invoice against its own PO, not against a running total compared to a contract ceiling.

A rebate clause obligates the vendor to issue a credit once spend crosses a threshold. That credit is the vendor's action to take. Nothing in an AP workflow flags its absence, because there is no invoice line to fail to match.

A. Surcharges and NTE caps

A surcharge with a sunset date and a not-to-exceed cap share the same failure mode inside Global Shop Solutions: both are conditions layered on top of a PO line, not properties of the line itself. The PO records a unit price and a quantity. It does not record that an add-on expires after a set period or that cumulative billing on this engagement stops at a stated ceiling.

An invoice that violates either condition still passes three-way matching, because matching only asks whether this invoice agrees with this PO, not whether the PO's underlying terms still hold.

B. Volume tiers and rebates

A volume tier lowers the unit price once cumulative purchases cross a threshold; a rebate clause issues a retroactive credit for the same reason. Both require tracking spend across many invoices against a contract term, then comparing that running total to a trigger point. Global Shop Solutions was built to process each PO and invoice as its own transaction.

Nothing in the system aggregates spend against an external threshold and flags when the vendor owes a lower price or a credit that never arrived.

4. How do you catch what three-way matching misses?

Catching these drift types requires a layer that holds the actual contract terms, rate cards, rebate clauses, surcharge sunset dates, NTE caps, as structured rules, then tests every invoice line against those rules rather than against the PO price alone. That layer can run retrospectively against 12 to 18 months of invoice history to quantify what already leaked, or continuously against new invoices as they arrive. Either way, the input is the contract document itself, not the PO field a.

The retrospective version is a diagnostic: pull the contract terms for each service vendor category, freight, contract labor, MRO, IT and professional services, maintenance, calibration, and test them against invoice history already sitting in Global Shop Solutions.

The forward version is a control: the same rules applied to each new invoice before or shortly after it posts, so a surcharge past its sunset date or a missed rebate threshold gets flagged before the AP team pays it rather than after.

Both versions need the same starting input: the contract terms extracted from the PDF and turned into a rule a system can test, which is exactly the step Global Shop Solutions was never built to perform.

5. Can you build this rule layer in a spreadsheet instead?

A spreadsheet can hold rate card values and rebate thresholds, and someone can manually compare invoice exports against them. That works at a small vendor count reviewed occasionally. It breaks down as the number of active contracts, surcharge sunset dates, and NTE caps grows, because each one requires a person to remember it exists and check it on every relevant invoice.

The spreadsheet does not fail technically; it fails because nobody re-runs the comparison consistently once the vendor list expands.

Building the comparison once, for one vendor's rate card against a quarter of invoices, is a reasonable weekend project for a finance analyst. The formulas are not complex: pull unit price, compare to a lookup table, flag mismatches.

The difficulty compounds with scale. A manufacturer running dozens of service vendor contracts across freight, staffing, MRO and IT services has dozens of rate cards, each with its own renewal date, each requiring the lookup table to be updated when terms change.

A spreadsheet has no alert when a contract renews with new terms and nobody updates the reference tab. It depends entirely on someone remembering to run it, and running it correctly, every cycle.

6. When does it make sense to check this manually versus get a diagnostic?

Checking manually makes sense when a company has few active service vendor contracts, stable terms that rarely change, and someone with time to review them line by line each cycle. A diagnostic makes more sense once the vendor count, contract complexity, or invoice volume outgrows what one person can track by hand, since a fixed-scope diagnostic is scoped to the reader's own vendor list rather than a general audit. The decision rests on how much contract complexity exists to track.

A company with three or four service vendor contracts, each renewed annually with terms that rarely change, can reasonably track them by hand inside a spreadsheet or even a shared document. The volume of invoices to check each cycle stays small enough for one person to manage.

Complexity grows independent of headcount. A manufacturer running freight contracts with multiple carriers, staffing agreements with NTE caps, and MRO rate cards that renew on different schedules accumulates more terms to track than any single AP reviewer can hold in memory.

At that point the question is not whether to check, but whether checking by hand still catches what it is supposed to catch.

For the wider pattern this sits inside, start with the margin drift guide. See also what is margin erosion? causes and prevention for manufacturers and margin drift vs. legitimate price increases: how to tell them apart.

7. Frequently Asked Questions (People Also Ask)

Does Global Shop Solutions do three-way matching?

Yes. It compares the purchase order, the receipt or service confirmation, and the invoice, checking that quantities and unit prices agree across all three. This confirms the vendor billed for what was ordered and received, but it does not confirm the price entered on the PO was the correct contract price to begin with.

Can Global Shop Solutions store a vendor rate card?

Not as a structured, comparable record. Rate cards typically arrive as PDFs or contract addenda. Global Shop Solutions has PO price fields that hold whatever number was manually entered, but no mechanism to import a rate card and test invoices against it directly.

Will Global Shop Solutions flag an expired surcharge?

No. A surcharge is billed as a line amount on the invoice, and as long as that amount matches what was entered on the PO, three-way matching passes it. The system has no field for a surcharge's sunset date, so nothing tests whether the surcharge should have stopped.

Does Global Shop Solutions track spend against a not-to-exceed cap?

Three-way matching evaluates each invoice against its own purchase order, not against a running total for the engagement. A not-to-exceed cap is a contract-level ceiling across many invoices, which is outside what a single PO-to-invoice comparison checks.

How do you find missed rebates if the ERP doesn't track them?

A rebate is owed by the vendor once spend crosses a threshold, and there is no invoice line for a credit that never arrived, so the ERP has nothing to flag. Finding it means comparing the rebate clause in the contract against cumulative spend by category, outside the ERP.

Is this a Global Shop Solutions configuration problem that can be fixed with a setting?

No. The gap is structural. Three-way matching compares documents already inside the ERP as structured records. Rate cards, rebate clauses and surcharge terms live outside it as unstructured contract documents, so no configuration change gives the ERP a field it was never built to hold.

What data does a margin drift diagnostic need from Global Shop Solutions?

It needs invoice history, typically 12 to 18 months, along with the associated purchase orders and vendor contract documents. The diagnostic pulls the contract terms out of the PDFs and tests them against the invoice data already sitting in the ERP.

Does adding a contract-terms layer replace Global Shop Solutions?

No. It sits alongside it. Global Shop Solutions keeps doing three-way matching on quantities and PO prices. The added layer handles the separate job of testing whether those PO prices and add-on charges still match the underlying contract terms.

How long does it take to find out how much margin drift exists?

A prioritized recovery and prevention roadmap is typically produced in 2 to 4 weeks, across ValueXPA diagnostics, once invoice history and contract documents are available for review.

Can a smaller manufacturer just track this in a spreadsheet?

It depends on contract complexity, not company size. A handful of stable, annually renewed contracts can be tracked by hand. Once the number of active rate cards, surcharge terms and NTE caps grows, a spreadsheet needs someone to remember to update and re-run it every cycle, which is where it tends to break down.