How do you audit vendor invoices in Acumatica?

Executive Summary

Acumatica's three-way match confirms that an invoice, a purchase order, and a receipt agree on quantity and unit price. It does not confirm that the unit price on the PO is the price the contract actually authorizes, that a volume tier has been applied correctly, or that a surcharge expired on the date the vendor's own rate schedule says it should.

The mechanism is simple: three-way matching is an internal consistency check across documents already inside Acumatica. A contract rate card, a rebate clause, or a not-to-exceed cap usually lives in a PDF outside the system, so there is nothing in Acumatica to match the invoice against.

Closing that gap does not require new software layered onto Acumatica. It requires the contract terms encoded as rules and checked against invoice history: a project scoped to find what has already leaked, not to configure another system.

1. What does Acumatica's three-way match actually check?

Acumatica's three-way match compares the vendor invoice against the purchase order and the goods or service receipt: same vendor, same quantity, same unit price, within a configured tolerance. It confirms internal consistency across three documents already inside the system. It does not test whether the unit price on the purchase order is the price the underlying contract actually authorizes.

If the PO was cut at the wrong rate, the match clears an invoice that is already wrong.

The check runs at the line level. Acumatica pulls the PO line, the receipt line, and the invoice line, and flags a variance if quantity or price falls outside tolerance. That tolerance is usually set as a percentage or a flat dollar amount, configured once and rarely revisited.

The weakness is upstream of the match itself. Someone entered the unit price on the purchase order, often by copying the prior PO or a number from a quote. If that entry was wrong, or if the contract's rate changed and the PO was never updated, the three-way match has nothing to compare it against. It confirms the invoice matches the PO. It never asks whether the PO matches the contract.

2. Where does contract-to-invoice matching happen instead?

Contract-to-invoice matching happens outside Acumatica, because the contract terms it would need, rate cards, volume tiers, rebate triggers, surcharge schedules, and not-to-exceed caps, live in PDFs and signed agreements the ERP was never designed to read. Someone has to translate those terms into rules, then check every invoice against them. Acumatica has no field for a rebate clause or a surcharge expiration date, so nothing in the system runs that check automatically.

A rate card sets a price per unit, per hour, or per mile depending on category. A volume tier drops that price once spend crosses a threshold. A rebate clause returns a percentage of spend at the end of a quarter. A surcharge schedule adds a temporary charge tied to a fuel index or a labor shortage, with a stated end date.

None of these terms enter Acumatica as structured data. They sit in the contract file. Building a control that reads the invoice, finds the matching contract clause, and checks the calculation means someone has to do that translation first, manually, then maintain it as contracts renew.

3. Which drift types slip through Acumatica's AP workflow?

Three drift types recur in an Acumatica AP workflow: a surcharge that should have expired but keeps appearing, a rate that drifted from the contract's current schedule because the PO was never refreshed, and a rebate that was earned under a volume tier but never calculated or claimed. Each one clears the three-way match because the match tests internal consistency, not contract compliance. Each requires the contract terms to be checked separately.

These three patterns share a root cause: the control that exists tests documents against each other inside the ERP, while the term that was actually violated sits in a contract file the ERP never reads. Fixing each one starts with pulling the contract, not the PO.

A. Surcharge persistence

A fuel or labor surcharge gets added to an invoice with a start date and an end condition written into the contract. Acumatica's AP workflow has no field that tracks a surcharge's expiration trigger, so a charge that should have dropped off keeps appearing on invoices that otherwise pass the three-way match cleanly.

B. Rate schedule drift

A vendor's rate card updates, but the purchase order in Acumatica was built from an earlier price list. The invoice matches the PO. The PO no longer matches the contract. The three-way match has no way to see the second comparison.

C. Rebate and credit memo gaps

A rebate earned under a volume tier or a promotional clause requires someone to calculate it, request it, and apply it against a future invoice. Acumatica records the credit memo once issued. It does not calculate whether one was owed.

4. Can Acumatica's approval workflow catch a not-to-exceed overrun?

Acumatica's approval workflow routes an invoice to a manager based on dollar amount or GL account, not against a contract's not-to-exceed cap. An approver sees a total and a coding line, not the cumulative spend against a project's NTE ceiling stated in the contract. Unless someone builds and maintains a separate tracker outside the ERP, an NTE overrun on a service contract passes through the same approval path as any other invoice within its dollar threshold.

Not-to-exceed caps are common on contract labor, IT services, and maintenance work, where a vendor bills time and materials against a ceiling set in the statement of work. The cap is a cumulative figure across the life of the engagement, not a single invoice.

Approval routing in Acumatica evaluates one invoice at a time against a dollar threshold or a GL account rule. It has no concept of a running total against an external ceiling. An approver signing off on invoice six of eight has no visibility into whether the vendor already billed past the NTE on invoice five.

Catching that requires tracking cumulative spend against the contract separately and checking it before approval, not during it.

5. How do you find drift that already happened in Acumatica's invoice history?

Finding drift that already happened means pulling invoice history out of Acumatica and matching it line by line against the actual contract terms for that vendor and period, not against the PO that was open at the time. This is retrospective work: it covers 12 to 18 months of historical spend across ValueXPA diagnostics, and it surfaces duplicate payments, missed credit memos, and rate mismatches the three-way match already cleared.

The starting point is an AP export from Acumatica: vendor, invoice number, line items, unit price, quantity, GL coding, and payment date. That export gets matched against the contract file for each vendor, not the PO, since the PO can carry the same wrong rate as the invoice.

This is where duplicate payments and unapplied rebates usually surface. A duplicate can pass a three-way match twice if it was entered against two different PO numbers, or resubmitted under a slightly different invoice number. Acumatica's AP workflow was not built to catch a pattern across its own payment history; it processes one invoice against one PO at a time.

6. What should a manufacturer running Acumatica check first?

Start with the vendor categories where rates change independently of any PO update: freight and 3PL, contract labor, and maintenance contracts with surcharge or NTE clauses. These are the categories where a purchase order gets set once and left stale while the underlying contract term moves. Pull twelve months of invoice history for those vendors and compare it against the current signed contract, not the PO on file.

Freight and 3PL invoices carry accessorial charges and fuel surcharges that change on a schedule the PO never reflects. Contract labor and staffing invoices carry bill rates that can drift from a rate card or exceed a not-to-exceed cap across the life of an engagement. Maintenance and calibration contracts often include rebate or credit terms tied to volume that require someone to track and claim them.

A manufacturer that has not checked these categories against underlying contract terms in over a year is looking at drift that has already accumulated. Margin drift across a full diagnostic typically runs 1% to 3% of service vendor spend, and the diagnostic itself takes 2 to 4 weeks to produce a prioritized roadmap. The output tells you which vendors and which categories to fix first, without requiring a new system configuration before the first finding lands.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and what is margin erosion? causes and prevention for manufacturers.

7. Frequently Asked Questions (People Also Ask)

Does Acumatica's three-way match check contract compliance?

No. It checks that the invoice, purchase order, and receipt agree with each other on quantity and price within tolerance. It never checks whether the PO price matches what the underlying vendor contract authorizes, since contract terms are not data Acumatica holds.

Can Acumatica track a not-to-exceed cap on a service contract?

Acumatica's approval workflow evaluates each invoice against a dollar threshold or GL rule, not a cumulative NTE ceiling from a statement of work. Tracking spend against an NTE cap requires a separate process outside the standard AP workflow.

Why does a duplicate payment still get approved in Acumatica?

A duplicate invoice entered against a different PO number, or resubmitted with a slightly altered invoice number, can pass a three-way match twice because each match runs against one invoice and one PO in isolation, not against the full payment history for that vendor.

What is the difference between a PO price and a contract price?

A PO price is whatever was entered when the purchase order was created, often copied from a prior order or quote. A contract price is what the signed agreement, rate card, or rate schedule currently authorizes. The two can diverge when a contract renews or a rate changes and the PO is never updated.

Do I need to replace Acumatica to catch this kind of drift?

No. The gap is a missing check, not a missing ERP feature to replace. Retrospective invoice-to-contract matching runs against an export from Acumatica's existing AP data; it does not require reconfiguring or replacing the system.

How far back should a manufacturer look for drift in Acumatica invoice history?

Twelve to eighteen months is enough to cover a full contract cycle for most service vendor categories, including annual rate resets and rebate periods, per ValueXPA diagnostics.

Which vendor categories carry contract terms outside Acumatica?

Freight and 3PL, contract labor and staffing, and maintenance contracts with surcharge or rebate clauses tend to carry terms, rate schedules, NTE caps, volume tiers, that live in the contract file rather than any field in the ERP.

Can Acumatica calculate a rebate owed under a volume tier?

Acumatica records a credit memo once one is issued. It does not calculate whether a rebate was earned under a contract's volume tier; that calculation happens outside the system, against the contract terms.