Who approves calibration and safety compliance invoices?

Executive Summary

Calibration and safety compliance invoices need two approvers, not one, because they carry two separate claims: that a technician performed a specific procedure on a specific asset, and that the price charged matches the contracted rate for that procedure. A single AP approver checking a PO total verifies neither claim. A quality or EHS lead can confirm the certificate exists and the interval was met, but has no reason to check the rate card.

A plant or maintenance manager can confirm the technician was on site, but rarely holds the master service agreement.

The mechanism that produces drift here is not fraud. It is that the calibration certificate, the purchase order, and the contract rate schedule live in three different systems, held by three different people, and none of them is asked to reconcile the other two. An invoice can be technically compliant (certificate attached, asset tagged correctly) and still be priced wrong, or priced correctly and attached to an asset that was never due for calibration.

The fix is a defined split: a technical approver who owns compliance evidence, and a commercial approver who owns contract terms, with AP responsible only for matching the two sign-offs to the invoice before payment. Neither approver should be asked to do the other's job, and the routing should say so explicitly rather than leaving it to whoever opens the invoice first.

1. Who should approve calibration and safety compliance invoices?

Two people, not one: a technical approver, usually a quality manager, EHS lead, or maintenance supervisor, who confirms the calibration or inspection actually occurred on the correct asset and interval; and a commercial approver, usually a controller or procurement lead, who checks the invoiced rate against the master service agreement. AP matches both sign-offs to the invoice before release. No single approver should be asked to confirm both the technical event and the contracted price.

The technical approver's job is narrow: did this asset need calibration on this date, and did a qualified technician perform the documented procedure. That person reads certificates and interval schedules, not rate cards.

The commercial approver's job is equally narrow: does the line-item price match what the contract specifies for that procedure, that asset class, and that service tier. That person reads the master service agreement, not calibration logs.

When one person is asked to do both, the review defaults to whichever skill they actually have. A quality lead signs off on price because the certificate looks right. A controller signs off on compliance because the total looks reasonable. Splitting the approval forces each check to actually happen.

2. Why can't AP approve these invoices alone?

AP can confirm a purchase order exists and a vendor is approved, but it cannot confirm a calibration interval was due or that a technician-hour rate matches the contract's tiered pricing for that equipment class. Those checks require documents AP does not hold: the calibration schedule and the master service agreement's rate table. Routing the invoice through AP as the only approver means neither document gets checked before the invoice is paid.

AP teams work from the purchase order and the invoice. Neither document states whether the underlying calibration was actually due, or whether the vendor applied the correct tier for that asset's criticality class.

A purchase order for calibration services looks identical whether the rate is correct or inflated, and whether the asset was due this quarter or not due until next year. AP has no independent way to tell.

This is not a staffing gap AP can close by working harder. It is a structural mismatch between what AP sees and what the two real questions require. See how do you audit calibration and safety compliance invoices for the full checklist AP can run once the technical and commercial approvals are in hand.

3. What does the technical approver actually check?

The technical approver confirms three things: the asset was actually due for calibration or inspection on the schedule that governs it, the technician who performed the work held the required certification, and the documentation attached to the invoice (certificate number, as-found and as-left readings, next-due date) matches the asset's own record. None of these three checks touches price.

This role sits with whoever owns the calibration or safety compliance schedule, usually a quality manager or EHS lead, sometimes a maintenance supervisor for shop-floor equipment.

The check is a match: does the certificate on the invoice correspond to a real, due event on this specific asset. An invoice for an asset not due for another four months, or for a certificate number that does not appear in the calibration log, fails this check regardless of price.

This approver should never be asked to confirm the rate is correct. That is a different document, held by a different person, and asking one approver to hold both invites a rubber stamp on whichever half they cannot actually verify.

4. What does the commercial approver actually check?

The commercial approver checks the invoiced line items against the master service agreement's rate schedule: the per-asset or per-procedure rate, any travel or minimum charge terms, and whether volume-based discounts applied when the contracted threshold was met. This is the same discipline used for labor rate deviations against master service agreements, applied to calibration line items instead of staffing timesheets.

Calibration contracts commonly price by equipment class, procedure type, or a flat per-visit rate with itemized exceptions for travel or after-hours work. The commercial approver holds that rate table and checks the invoice line by line against it.

This is where drift concentrates. A vendor may bill the standard rate for a procedure that qualifies for a lower contracted tier, or add a travel charge the agreement already bundles into the base fee.

The commercial approver does not need to know whether the calibration happened. That confirmation belongs to the technical approver. Asking one person to check both invites errors on whichever side is outside their training.

5. How should the two approvals be routed together?

Route the invoice to the technical approver first, since a calibration event that did not happen or does not match the asset record makes the price question moot. Once technical approval clears, route to the commercial approver for the rate check. AP releases payment only when both sign-offs are attached, and a missing signature from either approver holds the invoice regardless of how close the due date is.

Sequencing matters because the two checks answer different questions in a natural order: did this happen, then was it priced correctly. Running them in parallel risks a commercial approval on an invoice that later fails the technical check, which then requires unwinding a payment already queued.

The hold rule matters more than the sequence. A vendor payment term approaching does not justify skipping either signature. An invoice with only a technical sign-off, or only a commercial one, is incomplete, not lower-risk.

Smaller finance teams sometimes combine the roles under time pressure. Where that happens, it should be a stated, temporary exception, not a permanent default, and the two checks should still be performed as two distinct passes rather than one glance at the total.

1. Technical sign-off first: Confirm the calibration event was due, performed, and documented against the asset's own record.
2. Commercial sign-off second: Match the invoiced rate to the master service agreement's rate table for that procedure and equipment class.
3. AP holds without both: Payment does not release on a single approval, regardless of how close the due date is.

6. What happens when this split doesn't exist?

Without a defined split, invoices get approved by whoever is available, usually the person managing the vendor relationship day to day, who checks that the visit happened and treats the price as a given. Rate errors persist across renewal cycles because no one holds the contract terms during the actual approval step, only during negotiation. The category becomes recurring, easy-to-miss drift precisely because the approval step that should catch it was never assigned to someone who could.

A single-approver process tends to concentrate around whoever manages the vendor relationship operationally, often a maintenance or facilities lead. That person's incentive is to keep the vendor performing on schedule, not to interrogate the invoice against a contract they did not negotiate and may not have access to.

The result is not a single bad invoice. It is a rate that was wrong once, approved once, and then approved again on every subsequent invoice because the approval step never compares the current invoice back to the contract, only to the previous invoice.

Defining the split does not require new headcount in most finance organizations. It requires naming, in writing, which existing role owns the technical check and which owns the commercial check, and refusing to let AP release payment until both are visible on the invoice record.

For the wider pattern this sits inside, start with the margin drift guide. See also accessorial charge audit: the surcharges nobody validates and rate card enforcement: why approved timesheets still produce wrong invoices.

7. Frequently Asked Questions (People Also Ask)

Can the same person be both the technical and commercial approver?

It happens under time pressure, but it defeats the purpose of the split. One person checking both tends to verify whichever half matches their training and skim the other. If roles must combine temporarily, treat it as a stated exception and still run the technical and commercial checks as two separate passes, not one glance at the total.

Who holds the master service agreement rate table?

Usually a controller or procurement lead, since that is the group that negotiated it. If no one is named as the holder of the current rate table, the commercial check has no reference document to check against, and the invoice gets approved on the total alone.

What if the technical approver is not available before payment is due?

The invoice holds. A missing technical sign-off is not a reason to approve on the commercial check alone, since a wrong or unnecessary calibration event makes the price question irrelevant regardless of how correct that price is.

Does this approval split apply to every vendor invoice or just calibration?

The two-approver logic, a technical check and a separate commercial check, applies wherever a compliance event and a contracted price are verified by different documents. Calibration and safety compliance is a clear case because the certificate and the rate card are always held separately.

How do we know if our current process already has this split?

Check who actually signs each invoice today. If one name appears on both the compliance confirmation and the price approval, or if AP releases payment without a named technical sign-off at all, the split does not exist yet even if two roles are listed on paper.

What document should the commercial approver ask for if the rate table is unclear?

The master service agreement itself, including any amendment schedules, rather than a summary sheet or the previous invoice. Approving against the last invoice instead of the contract is how a wrong rate persists across renewal cycles.

Should the technical approver ever see the price?

There is no need for them to review it as part of their sign-off. Their job is confirming the event and the documentation, not the dollar amount, and keeping the price out of their review reduces the chance they approve based on a total that looks reasonable rather than the compliance record.

What happens to an invoice if only the commercial approval is attached?

It is incomplete and should not be paid. A commercial sign-off confirms the rate matches the contract, but says nothing about whether the underlying calibration event actually occurred or was even due.