Calibration Compliance Controls in Sage Intacct

Executive Summary

Sage Intacct enforces coding accuracy, purchase order matching and approval routing on calibration invoices. Its dimension structure (Vendor, Department, Location, Project, Class, Item) lets a controller isolate calibration spend by lab, plant or asset class, and its Purchasing module supports matching a bill against a purchase order and a receipt before payment releases.

None of that checks a calibration invoice against the calibration contract itself. Sage Intacct has no field for a certificate expiration date, no rule that flags a recalibration billed ahead of its stated interval, and no comparison between a line-item rate and a rate card that lives outside the system. The platform verifies that a bill matches what was ordered and received.

It does not verify that what was ordered was priced correctly to begin with.

The result is a control gap that sits precisely where calibration and safety compliance spend goes wrong: not in a phantom invoice, but in a real one paid at the wrong rate, off the correct cycle, or without a credit that a missed service window earned.

1. What does Sage Intacct actually enforce on a calibration invoice?

Sage Intacct enforces three things on a calibration invoice: general ledger coding through its dimension structure, quantity and price matching against an open purchase order, and approval routing before a bill posts for payment. Vendor, Department, Location, Project, Class and Item dimensions let a controller report calibration spend by plant, lab or asset category. None of these checks whether the calibration price or interval matches what the service contract actually says.

Sage Intacct's Purchasing module supports a purchase order to receipt to bill workflow. When a calibration vendor bill arrives, the system can match its quantity and unit price against the originating purchase order line and flag a variance for review before the bill posts. This catches a price typed incorrectly at entry, or a quantity that does not match what was received.

Approval workflows route the bill to the right cost center owner based on dimension values, so a calibration invoice coded to the wrong department gets caught by someone who would notice.

What this workflow cannot do is compare the purchase order price itself against the calibration contract's rate schedule. If the PO was cut at the wrong rate, the three-way match confirms the invoice against a wrong number and clears it.

2. Can Sage Intacct catch a recalibration billed before it was due?

No. Sage Intacct has no field that stores a calibration certificate's expiration date or a recertification interval, and no rule engine that compares an invoice date against either. The platform tracks when a bill was entered and when a purchase order was issued, not when an asset's calibration cycle is scheduled to run again.

A vendor billing a 12-month cycle at 9 months posts and pays like any other correctly coded invoice.

Calibration contracts typically state a recertification interval tied to an asset or instrument, sometimes annual, sometimes tied to usage hours. That interval lives in the vendor's service agreement, not in any Sage Intacct data structure.

A Fixed Assets module can track an asset's acquisition date and depreciation schedule, but it has no concept of a calibration due date or a linked service contract term. Nothing in the platform flags an invoice date against a prior calibration date for the same asset.

An AP team relying on Sage Intacct alone to prevent early recalibration billing is relying on a control that does not exist in the system. The check has to happen against the contract, outside the ERP, by someone who tracks calibration schedules separately.

3. Does Sage Intacct validate calibration and safety compliance rate cards?

Sage Intacct validates that an invoice price matches the price on its own purchase order. It does not validate that the purchase order price matches a rate card, tiered pricing schedule or contracted discount the vendor agreed to. A calibration vendor can raise its rate on a renewal and the new number flows through PO, receipt and bill matching cleanly, because nothing in the platform holds the original contracted rate as a reference point.

A calibration and safety compliance contract commonly sets per-instrument or per-visit rates, sometimes with volume tiers for facilities running multiple labs or plants. None of that rate structure has a home in Sage Intacct beyond the price typed onto a purchase order line at the time it is cut.

If the person creating the PO enters last year's rate, or a rate the vendor already increased, the three-way match confirms the bill against that number without ever comparing it to the signed contract.

This is a rate card and pricing schedule problem, not a data entry problem the system is built to catch. Sage Intacct's matching logic is internally consistent: PO, receipt and bill agree with each other. It has no external reference to the contract that would tell it whether that agreed number was ever correct.

4. What do dimensions actually give a controller here?

Dimensions give a controller visibility, not enforcement. Tagging every calibration bill with Vendor, Location, Department and Item dimensions makes it possible to run a report showing total calibration spend by plant or by vendor across a period. That visibility is real and useful for spotting a vendor whose spend jumped.

It is not a control that stops an incorrect invoice from posting in the first place.

A controller who sets up dimension values consistently across calibration vendors can pull a report showing spend trends by location or by asset class over a quarter or a year. That report can surface a vendor whose total billing rose without a corresponding increase in instrument count, which is a legitimate first signal that something changed.

But a dimension report is retrospective. It shows what already posted, not what was wrong before it posted. Finding the increase does not tell the controller whether it came from a legitimate rate escalation clause, a billing error, or a vendor charging outside the contract.

Dimensions are a reporting layer built on top of transactions that already cleared whatever matching rules applied. They answer where the money went, not whether the amount was right.

5. Where does the gap between Sage Intacct and the calibration contract actually sit?

The gap sits between the purchase order and the contract that should have priced it. Sage Intacct's matching logic starts at the PO and checks everything downstream of it: receipt, bill, approval. It has no upstream check comparing the PO itself to the calibration agreement's rate schedule, service interval, or any credit clause tied to a missed or late service visit.

Three distinct mechanisms sit outside what Sage Intacct's Purchasing module checks. A rate schedule comparison, verifying a PO price against the contracted rate at the time it was cut. A service interval comparison, verifying an invoice date against the contract's recertification cycle for that specific asset.

And a credit or penalty clause comparison, verifying whether a missed service window should have triggered a credit the vendor never issued.

Each of these requires reading the calibration contract as a document and holding its terms as a reference point independent of whatever price was typed onto a purchase order. Sage Intacct was not built to ingest and interpret an unstructured contract PDF, and no configuration inside the platform changes that.

This is not a criticism specific to Sage Intacct. Every ERP's purchasing module checks internal consistency between the documents it generates. None of them holds the vendor's contract as ground truth against the purchase order a buyer created.

6. What should a calibration AP control actually check?

A calibration invoice control worth the name checks three things a Sage Intacct workflow does not: the invoiced rate against the contracted rate schedule, the invoice date against the contract's recertification interval for that asset, and any missed-service credit the contract entitles the buyer to. All three require reading the contract once and holding its terms somewhere the AP team can compare against every future invoice.

Building this inside Sage Intacct means creating a reference table, outside the transactional system, that holds each calibration contract's rate schedule and service interval by asset or vendor. Someone then has to compare every invoice against that table before it posts, because the platform will not do the comparison natively.

For a facility running a handful of calibration vendors this is manageable in a spreadsheet. For a manufacturer running calibration and safety compliance programs across multiple plants, with vendors on different renewal cycles and rate structures, the spreadsheet becomes the largest source of missed drift rather than the fix for it.

The practical question is not whether Sage Intacct should add this. It is whether the reference table gets built and checked consistently, and by whom. A margin drift diagnostic answers that question by testing a period of actual calibration invoices against the underlying contracts once, and showing exactly where the gap cost money.

For the wider pattern this sits inside, start with the margin drift guide. See also diagnostic or software: what to buy first and build vs. buy: can you do contract-to-invoice matching in excel?.

7. Frequently Asked Questions (People Also Ask)

Does Sage Intacct do three-way matching on calibration invoices?

Yes. Sage Intacct's Purchasing module supports matching a bill's quantity and price against the originating purchase order and the recorded receipt before the bill posts for payment. This catches data entry errors and quantity mismatches. It does not check whether the purchase order price itself matches the vendor's contracted rate.

Can I track calibration due dates inside Sage Intacct?

Not natively. Sage Intacct's Fixed Assets module tracks acquisition and depreciation data, not calibration certificate expiration or recertification intervals. Tracking calibration due dates requires a separate system or spreadsheet maintained alongside Sage Intacct, with no built-in link between the two.

Will Sage Intacct flag a calibration vendor's rate increase?

Only if the rate change is visible against the purchase order it was entered on. If a rate increase is entered directly into a new purchase order without comparison to the prior contracted rate, the three-way match will clear it, because the system checks internal consistency between its own documents, not against the contract.

What can dimensions in Sage Intacct show me about calibration spend?

Dimensions like Vendor, Location, Department and Item let you report total calibration spend by plant, lab or asset category over any period. This is useful for spotting a vendor whose billing changed. It is retrospective reporting, not a control that stops an incorrect invoice from posting.

Is this an issue specific to Sage Intacct?

No. Every ERP's purchasing workflow checks that a bill matches the purchase order and receipt it was generated from. None of them, Sage Intacct included, holds an external vendor contract's rate schedule or service interval as a reference point to check purchase orders against.

Should I build a calibration rate and interval tracker outside Sage Intacct?

It is one workable option: a reference table holding each contract's rate schedule and recertification interval by asset or vendor, checked manually against invoices before they post. Whether that is worth building depends on how many calibration vendors and assets you run and how often rates or intervals change.

Does Sage Intacct handle credit memos for missed calibration service windows?

Sage Intacct can record and apply a credit memo once a vendor issues one. It has no mechanism to detect that a credit should have been issued because a service window in the contract was missed. That determination has to be made by comparing the service history against the contract.

What is margin drift in the context of calibration spend?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In calibration and safety compliance spend it commonly shows up as a stale rate carried forward on a purchase order, or a service interval billed ahead of its contracted schedule.

Can Sage Intacct's approval workflow catch a wrong calibration rate?

Only if the approver happens to know the contracted rate and checks it manually during review. The workflow itself routes the bill based on dimension values and amount thresholds. It does not compare the invoiced rate against any stored contract figure, because Sage Intacct has no field for that comparison.