How do you audit vendor invoices in Sage Intacct?

Executive Summary

Sage Intacct's dimensional structure and approval workflows confirm that an invoice matches a purchase order and that the purchase was authorized. That is a procurement control. It answers "did we approve this spend," not "does this invoice charge what the contract says it should."

The mechanism behind the gap is simple. Contract terms for freight, contract labor, maintenance, and professional services live in PDFs and vendor portals, not in Sage Intacct's data model. A surcharge that should have expired, a volume tier that should have dropped the rate, a rebate that should have been credited: none of these show up as a mismatch between PO and invoice, because the PO was correct when issued and the contract term changed afterward.

What changes it is a periodic pass that reads the invoice against the actual contract clause, not against the PO. That is retrospective work for the audit and forward-looking work for prevention. Sage Intacct can host the resulting credit memos and corrected coding. It cannot generate the finding on its own.

1. What does Sage Intacct actually check on a vendor invoice?

Sage Intacct checks that an invoice ties to an approved purchase order and receipt, that the general ledger coding follows your dimension structure, and that the approval workflow was followed before payment. These are three-way match and procurement controls. They confirm the invoice matches what was ordered and that someone signed off.

They do not test whether the price on the invoice matches a rate card, whether a volume tier should have applied, or whether a surcharge is still contractually.

Three-way matching in Sage Intacct compares the invoice, the purchase order, and the receiving record. If the quantities and the PO price line up, the invoice clears. That check is built around what was ordered, not around what the contract permits the vendor to charge.

A vendor can raise a rate mid-term, apply an accessorial charge outside the tariff on file, or continue billing a fuel surcharge past its trigger condition, and the three-way match will still pass. The PO price and the invoice price agree with each other. Neither one is being checked against the contract clause that actually governs the charge.

Dimension-based reporting in Sage Intacct is a strength for spend visibility: you can see freight spend by vendor, by location, by department. It tells you how much you spent. It does not tell you whether the rate applied to get there was the rate you contracted for.

2. Where does margin drift hide in a Sage Intacct AP workflow?

Drift hides in the space between the purchase order and the underlying contract clause. A PO carries a price at the time it is cut. If a rate card changes, a rebate threshold is crossed, or a surcharge should expire, the PO does not update itself and the invoice can still match it exactly.

The invoice looks clean in the ERP because the control being applied was never designed to test the contract term that actually moved.

Freight and 3PL invoices are a common example. A carrier's fuel surcharge is tied to a published index and a trigger condition in the contract. Three-way matching checks the invoice against the PO and receipt; it does not test a surcharge's expiration condition or recompute it against the index.

Contract labor and staffing invoices carry a similar exposure. A not-to-exceed cap or a rate escalation clause sits in the master services agreement, not in the PO line item, so an invoice can clear the match and still exceed the cap.

Maintenance and calibration contracts often include volume-based rebate clauses that require someone to track cumulative spend against a threshold across the year. Sage Intacct will total the spend by vendor. It will not flag that the threshold was crossed and a rebate is now owed.

3. Can Sage Intacct's approval workflow catch these on its own?

No. An approval workflow routes an invoice to a person based on amount, department, or vendor, and that person decides whether to approve it. The workflow enforces who must sign off.

It supplies no reference to the contract's rate card, rebate clause, or surcharge terms, so the approver is deciding from the same limited information the system gives them: the PO price and the invoice price, not the governing contract language.

An approver reviewing an invoice in Sage Intacct sees the invoice, the PO it matches, and any attached documents. Unless someone has attached the actual contract and the approver reads it against the specific line item, the approval is a check that the number matches what was expected, not that the number is contractually correct.

This is not a flaw in the approver's judgment. It is a scope limitation in what the workflow puts in front of them. A rate card with volume tiers, a rebate clause with a cumulative threshold, or a surcharge schedule tied to an external index is unstructured information sitting in a PDF outside the ERP.

Building that reference into the approval step means someone has already done the work of translating the contract into a rule an approver, or a system, can check against. That translation work is the audit.

4. How does a contract compliance audit work alongside Sage Intacct?

A contract compliance audit pulls invoice history and vendor contracts, matches each invoice line against the specific clause that governs it, rate card, volume tier, rebate trigger, surcharge schedule, or NTE cap, and produces findings independent of Sage Intacct's own controls. Sage Intacct remains the system of record for the transaction. The audit adds a layer that reads the contract, which the ERP was never built to parse or enforce.

The audit starts with an export of AP invoice detail from Sage Intacct by vendor and category, alongside the underlying contracts, rate cards, and amendments for those vendors. Line-by-line matching then checks invoice price and terms against the contract clause, not against the PO.

Findings fall into two buckets. Recovery items: overbilling, unapplied rebates, and duplicate payments already posted, which become credit memo requests. Prevention items: rules that should be checked on every future invoice, such as a rate cap or a rebate threshold, so the next invoice does not repeat the pattern.

Sage Intacct's dimension and attachment fields are useful here. Once a rule is identified, the corrected coding and any supporting documentation can be attached to future invoices in Sage Intacct itself, without adding a separate system.

A. Recovery findings

These are invoices already paid where the contract was not followed. A duplicate payment, an overbilled rate, a rebate that should have posted as a credit. Each becomes a specific request back to the vendor, supported by the invoice and the contract clause, not a general dispute.

B. Prevention findings

These are the rules the invoice should be checked against going forward: a rate ceiling, a surcharge expiration date, a rebate threshold. Documenting the rule is what lets the same drift get caught on the next invoice instead of the one after that.

5. Is Sage Intacct's ERP data enough to run this audit alone?

Sage Intacct's invoice and payment history is necessary but not sufficient. It supplies the transaction record: what was billed, when, by whom, and how it was coded. What it does not supply is the contract itself.

The audit needs both the ERP export and the actual vendor agreements, rate cards, and amendments, because the finding only exists where the two are compared against each other, not from either one read alone.

An AP team with strong Sage Intacct hygiene, clean dimension coding, consistent vendor records, and complete attachments, still cannot answer whether the rates charged match the contract, because that answer is not encoded anywhere in the transaction data. It requires the contract document.

This is why the audit is a distinct engagement rather than a report run inside Sage Intacct. The report can tell you what you spent. It cannot tell you what you should have spent under the terms you signed.

Organizing the invoice export by vendor and category before the audit starts saves time: Sage Intacct's dimension structure, if used consistently, makes this extraction straightforward, which is one place the ERP's design does help the audit even though it cannot run the audit itself.

6. What should an AP team change in Sage Intacct after an audit?

After a diagnostic identifies specific drift, the fix is usually a documented rule attached to the vendor or contract record in Sage Intacct: a rate ceiling noted on the vendor, a surcharge expiration date tracked outside the automatic match, a rebate threshold flagged for review at a set spend level. None of this requires new software. It requires the contract terms to be written down somewhere the AP team checks before approving, not after.

The simplest change is documentation: attaching the current rate card and any amendments to the vendor record in Sage Intacct, so the approver has the reference in front of them instead of relying on memory or a filing cabinet.

A second change is a manual checkpoint for the specific vendors and categories where drift was found. This is not a system-wide policy change. It is targeted to the contracts where a rate card, rebate clause, or surcharge schedule actually governs a meaningful share of spend.

Where regulatory or contractual obligations are part of the discussion, such as a rebate clause with legal notice requirements, this is general information, not legal advice, and the underlying agreement should be reviewed with counsel before a dispute is raised with a vendor.

For the wider pattern this sits inside, start with the margin drift guide. See also the Margin Drift Diagnostic and our insights.

7. Frequently Asked Questions (People Also Ask)

Does Sage Intacct do three-way matching?

Yes. Sage Intacct compares the invoice, the purchase order, and the receiving record, and flags a mismatch in quantity or PO price. This confirms the invoice matches what was ordered and received. It does not check the PO price itself against a contract rate card, so a PO issued at a stale or incorrect rate will still clear the match.

Can Sage Intacct flag a duplicate payment automatically?

Sage Intacct's duplicate invoice detection typically checks invoice number, vendor, and amount at entry. It can catch an exact resubmission. It is less reliable against a duplicate billed under a slightly different invoice number or a different amount for the same underlying charge, which is where a manual audit adds coverage.

What is a rate card, and why doesn't the ERP check it?

A rate card is the pricing table in a vendor contract: base rates, volume tiers, accessorial charges. It typically exists as a PDF or spreadsheet attachment, not as structured data Sage Intacct can read line by line, so the ERP has nothing to compare the invoice price against beyond the PO.

How often should a contract compliance audit be done if we use Sage Intacct?

There is no fixed interval that applies to every company. A reasonable trigger is a set spend threshold per vendor category, a contract renewal, or after a period of known billing errors. The diagnostic itself takes 2 to 4 weeks across ValueXPA engagements, once it starts.

Does this audit require replacing Sage Intacct?

No. The audit works from an export of Sage Intacct's invoice and payment data alongside the vendor contracts. Findings and corrected coding get attached back into Sage Intacct's existing vendor and dimension structure. No new system is required to run the audit or to act on its findings.

What size of company does this apply to?

The diagnostic is built for manufacturers and distributors above $100M in revenue, where service vendor spend across freight, labor, maintenance, and professional services is large enough that a 1% to 3% drift rate, across ValueXPA diagnostics, represents a material dollar figure.

Who should own this inside the finance team?

Typically the Controller or AP lead owns the invoice-side data and the vendor relationships, while a CFO or procurement lead owns the contract negotiation. Both perspectives matter because the audit compares what was negotiated against what was billed and coded.

What happens to findings after the audit?

Findings split into recovery items, credit memo requests for already-paid overbilling or missed rebates, and prevention items, rules documented so future invoices in Sage Intacct are checked against them before payment rather than after.

Is this the same as AP automation software?

No. AP automation prevents forward-looking errors at the point of invoice receipt inside systems like Sage Intacct. It does not quantify leakage already embedded in 12 to 18 months of historical spend or interpret unstructured contract terms living in PDFs outside the ERP. The two are complementary, not substitutes.