# How Far Back Can You Claim a Calibration Overcharge? > How far back a calibration billing error can be recovered, what limits the window, and what documentation makes a stale claim collectible. Read the full guide. Source: https://valuexpa.com/insights/how-far-back-can-you-claim-a-calibration-overcharge Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. Calibration and safety compliance spend is where that gap hides longest, because the invoices look routine and nobody revisits them once a certificate is filed. The question of how far back a calibration overcharge can be claimed has no single answer. It depends on the contract's own audit clause, the vendor's record retention, and the statute of limitations in the governing state. All three set a different clock, and the shortest one wins. ## Executive Summary A calibration overcharge, a wrong frequency billed, a device charged at the wrong tier, a certificate fee applied twice, sits on an invoice that nobody checks against the calibration schedule after it is paid. It survives because the review that would catch it, matching the invoice to the asset's actual calibration interval and contract tier, does not happen at the point of payment. It happens, if at all, only when someone audits the history. How far back that history can be reopened depends on three separate clocks running at once: the contract's audit or look-back clause, the vendor's own record retention period, and the statute of limitations that applies to a written contract in the relevant state. None of these is a ValueXPA figure or a fixed industry number. Each is written into a specific document the buyer already holds. What changes the outcome is not persistence but documentation. A claim that names the wrong device tier, the contract clause it violates, and the invoice dates is collectible years after the fact. A claim built from memory of "we've been overcharged for a while" is not, because the vendor has no obligation to reconstruct a period it can no longer support with its own records. ## 1. What actually sets the look-back window on a calibration claim? **Three separate clocks limit how far back a calibration overcharge can be claimed: the audit or reconciliation clause written into the calibration or MSA contract, the vendor's stated record retention period for certificates and invoices, and the state statute of limitations for a written contract claim. Each runs independently. The shortest of the three, not the longest, is the one that actually determines whether a specific invoice is still collectible.** The contract clause is the first place to look, and it is often the most restrictive. Many service agreements state a fixed audit window, commonly tied to the contract term itself, after which either party waives the right to reconcile past billing. If that clause reads 12 months, that number controls regardless of what else is true. Record retention is the second clock. A vendor that has purged certificates and calibration logs beyond a certain period cannot produce the documentation a claim needs to be verified, even if the contract's audit window is longer. This is a practical limit, not a legal one, but it functions the same way. The statute of limitations on a written contract varies by state, and it applies to the underlying billing dispute regardless of what the service contract says about audits. It is the longest of the three clocks in principle, and the least relevant in practice, because the other two typically close first. - **Contract audit clause:** Often the shortest window and the first to check; it can waive reconciliation rights entirely after a stated period. - **Vendor record retention:** Sets a practical ceiling: a claim needs a certificate or invoice the vendor can still produce. - **State statute of limitations:** Applies to the written contract itself and is usually the longest window, but rarely the binding one. ## 2. How do you find out what your own contract's audit window actually is? **Read the calibration or master service agreement for a clause labeled audit rights, billing reconciliation, or invoice dispute period, not just the termination or renewal terms. If no such clause exists, the contract defaults to whatever the general commercial terms say about billing disputes, which is often silent, leaving the state statute of limitations as the only real constraint on the claim.** The clause to search for rarely uses the word calibration. It sits in the general terms, under a heading like audit rights, invoice disputes, or billing reconciliation. Some contracts state a window explicitly, for example the right to dispute an invoice within a set number of days or months of receipt. Others are silent, which is not the same as unlimited. When the contract is silent, there is no contractual clock at all, and the claim falls back to the state statute of limitations for a written contract dispute. That is a legal question specific to the jurisdiction and the contract, and it is general information here, not legal advice; a claim near that boundary should be checked with counsel before it is pursued or dropped. A second thing worth checking in the same clause: whether it requires written notice within the window, or whether filing the dispute itself is enough. Some clauses distinguish between raising the issue and formally invoicing for the credit, and miss dates because of that distinction rather than the substance of the claim. ## 3. Does the type of calibration error change what can still be claimed? **The look-back window is set by the contract and retention limits, not by which error occurred, but the type of error determines whether enough evidence survives to prove it. A frequency error leaves a paper trail in the calibration schedule itself; a tier misclassification depends on the vendor's own device catalog, which may not be retained as long as the invoices are.** A frequency error, calibration billed more often than the equipment's schedule requires, is provable from the asset's own calibration history, which the buyer usually controls and retains independently of the vendor. This makes it one of the more durable claims even several years out. A device tier misclassification, where a simple gauge is billed at a complex-instrument rate, depends on the vendor's own service catalog and the device list attached to the contract. If that catalog changed over the period in question, proving the rate that should have applied requires the version in force on each invoice date, not the current one. A duplicate certificate fee is straightforward to document because it shows up as two line items for the same asset and date. It is also easy for a vendor to concede, because it requires no interpretation of contract terms, only a comparison of two invoices. ## 4. What documentation makes an older claim collectible? **A collectible claim names the specific invoice, the contract clause it violates, the correct rate or frequency, and the dollar difference, not a general sense that billing has been wrong. Strong documentation gives a vendor less reason to dispute a claim and more reason to verify and settle it, because the work of confirming it has already been done for them.** Start from the invoice, not the complaint. Pull the specific invoice number, date, device or asset ID, and the line item in question. Match it against the contract clause or rate schedule that governs that device or that calibration interval. State the correct value next to the billed value: the frequency the schedule actually calls for versus what was billed, or the tier rate the contract specifies versus what was charged. The dollar difference should follow directly from that comparison, not be estimated separately. Where the contract's audit clause requires written notice within a window, date-stamp the claim itself. A claim raised inside the window but not resolved before it closes is generally still valid, because the clock governs when the dispute is raised, not when it is settled. Confirm this reading against the specific clause language rather than assuming it; audit clauses vary on this point and the difference is a legal question, not a billing one. ## 5. Can a calibration overcharge claim be pursued if the vendor relationship is still active? **Yes. An active vendor relationship does not waive a documented billing claim, and raising it does not require ending the contract. It does mean the claim should be framed as a reconciliation request under the existing audit clause rather than a dispute, which keeps the conversation inside the contract's own mechanism instead of turning it adversarial.** Framing matters more than most buyers expect. A reconciliation request, invoking the audit clause and presenting the documentation directly, is a routine commercial exchange that calibration vendors have a process for. A dispute framed as an accusation invites a legal response instead of a billing one. The timing of the request relative to the contract's renewal cycle also matters. Raising it well before a renewal decision gives both sides room to resolve it on the merits. Raising it during a renewal negotiation ties the credit to negotiating room the buyer may not need, and can slow down a claim that would otherwise be straightforward. This is general information about how these claims are typically structured, not legal advice on a specific contract; a claim of meaningful size, or one the vendor disputes, should go through counsel before it is formally raised. ## 6. How do you stop the same calibration overcharge from recurring after it's recovered? **Recovering a past overcharge does not fix the control that let it happen. The invoice review that missed the error the first time will miss it again unless the calibration schedule, the device tier list, and the invoice are matched at each billing cycle, not just when a retrospective audit happens to run. The fix is a recurring check, not a one-time credit.** The root cause of a calibration billing error like this is a mismatch between two records that are rarely compared: the asset's actual calibration schedule and the invoice that bills against it. [Three-way matching against a purchase order](/guides/sub-hub-maintenance-and-msa-invoice-audit) checks that the invoice matches an authorized order. It does not check whether that order's frequency or tier still matches the equipment's current schedule. Closing that gap means someone, or some system, comparing the invoice line to the calibration schedule and the current device tier list at every billing cycle, not only when a periodic audit happens to catch it. That comparison is exactly what a [contract compliance audit](/answers/how-do-you-audit-calibration-and-safety-compliance-invoices) is built to run across a full spend category, calibration included, once, as part of establishing where the controls need to sit going forward, before handing the ongoing check to a [margin drift diagnostic](/margin-drift-diagnostic) engagement. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates). ## 7. Frequently Asked Questions (People Also Ask) ### Is there a fixed statute of limitations for calibration billing errors? No single fixed period applies everywhere; the statute of limitations for a written contract claim is set by state law and varies by jurisdiction. It is one of three clocks that can limit a claim, alongside the contract's own audit clause and the vendor's record retention period. Check the specific state law that governs your contract rather than assuming a standard window. ### What if the contract has no audit clause at all? If the contract is silent on billing disputes, there is no contractual clock limiting the claim, and the claim falls back to the state statute of limitations for a written contract. This is a legal question, not a billing one, and should be confirmed with counsel before a claim near that boundary is pursued. ### Can a vendor refuse to honor a claim just because it's old? A vendor can decline a claim that falls outside the contract's audit window, outside its own record retention, or outside the applicable statute of limitations. Inside those windows, a documented claim is a contractual reconciliation request, not a favor, though the vendor still has to be able to verify it against its own records. ### Does raising a calibration billing claim put the vendor relationship at risk? Framing it as a reconciliation request under the contract's own audit clause, rather than as an accusation, keeps the exchange routine. Vendors that provide calibration services under ongoing contracts generally have a process for this kind of request, since it is a mechanism the contract itself provides for. ### What records do I need before raising a calibration overcharge claim? You need the specific invoice number, date, device or asset ID, the contract clause or rate schedule that governs that device, and the correct frequency or tier compared against what was billed. The dollar difference should follow directly from that comparison rather than being estimated. ### Should a calibration overcharge claim go through legal counsel? For a claim of meaningful size, or one the vendor disputes, yes. This guide is general information about how these claims are typically structured, not legal advice on a specific contract, and questions about statute of limitations or clause interpretation are legal questions. ### Why do calibration overcharges often go unnoticed for years? The invoice is checked against a purchase order at the time of payment, not against the asset's calibration schedule or the contract's device tier list. That comparison only happens when someone runs a retrospective audit, which is why the error can persist across many billing cycles before it surfaces. ### Does fixing the overcharge automatically prevent it from happening again? No. Recovering the credit resolves the past invoices but does not change the review process that missed the error. Preventing recurrence requires matching the invoice against the calibration schedule and device tier list at every billing cycle going forward, not just once during an audit. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary A calibration overcharge, a wrong frequency billed, a device charged at the wrong tier, a certificate fee applied twice, sits on an invoice that nobody checks against the calibration schedule after it is paid. It survives because the review that would catch it, matching the invoice to the asset's actual calibration interval and contract tier, does not happen at the point of payment. It happens, if at all, only when someone audits the history. How far back that history can be reopened depends on three separate clocks running at once: the contract's audit or look-back clause, the vendor's own record retention period, and the statute of limitations that applies to a written contract in the relevant state. None of these is a ValueXPA figure or a fixed industry number. Each is written into a specific document the buyer already holds. What changes the outcome is not persistence but documentation. A claim that names the wrong device tier, the contract clause it violates, and the invoice dates is collectible years after the fact. A claim built from memory of "we've been overcharged for a while" is not, because the vendor has no obligation to reconstruct a period it can no longer support with its own records. ## 1. What actually sets the look-back window on a calibration claim? Three separate clocks limit how far back a calibration overcharge can be claimed: the audit or reconciliation clause written into the calibration or MSA contract, the vendor's stated record retention period for certificates and invoices, and the state statute of limitations for a written contract claim. Each runs independently. The shortest of the three, not the longest, is the one that actually determines whether a specific invoice is still collectible. The contract clause is the first place to look, and it is often the most restrictive. Many service agreements state a fixed audit window, commonly tied to the contract term itself, after which either party waives the right to reconcile past billing. If that clause reads 12 months, that number controls regardless of what else is true. Record retention is the second clock. A vendor that has purged certificates and calibration logs beyond a certain period cannot produce the documentation a claim needs to be verified, even if the contract's audit window is longer. This is a practical limit, not a legal one, but it functions the same way. The statute of limitations on a written contract varies by state, and it applies to the underlying billing dispute regardless of what the service contract says about audits. It is the longest of the three clocks in principle, and the least relevant in practice, because the other two typically close first. - Contract audit clause: Often the shortest window and the first to check; it can waive reconciliation rights entirely after a stated period. - Vendor record retention: Sets a practical ceiling: a claim needs a certificate or invoice the vendor can still produce. - State statute of limitations: Applies to the written contract itself and is usually the longest window, but rarely the binding one. ## 2. How do you find out what your own contract's audit window actually is? Read the calibration or master service agreement for a clause labeled audit rights, billing reconciliation, or invoice dispute period, not just the termination or renewal terms. If no such clause exists, the contract defaults to whatever the general commercial terms say about billing disputes, which is often silent, leaving the state statute of limitations as the only real constraint on the claim. The clause to search for rarely uses the word calibration. It sits in the general terms, under a heading like audit rights, invoice disputes, or billing reconciliation. Some contracts state a window explicitly, for example the right to dispute an invoice within a set number of days or months of receipt. Others are silent, which is not the same as unlimited. When the contract is silent, there is no contractual clock at all, and the claim falls back to the state statute of limitations for a written contract dispute. That is a legal question specific to the jurisdiction and the contract, and it is general information here, not legal advice; a claim near that boundary should be checked with counsel before it is pursued or dropped. A second thing worth checking in the same clause: whether it requires written notice within the window, or whether filing the dispute itself is enough. Some clauses distinguish between raising the issue and formally invoicing for the credit, and miss dates because of that distinction rather than the substance of the claim. ## 3. Does the type of calibration error change what can still be claimed? The look-back window is set by the contract and retention limits, not by which error occurred, but the type of error determines whether enough evidence survives to prove it. A frequency error leaves a paper trail in the calibration schedule itself; a tier misclassification depends on the vendor's own device catalog, which may not be retained as long as the invoices are. A frequency error, calibration billed more often than the equipment's schedule requires, is provable from the asset's own calibration history, which the buyer usually controls and retains independently of the vendor. This makes it one of the more durable claims even several years out. A device tier misclassification, where a simple gauge is billed at a complex-instrument rate, depends on the vendor's own service catalog and the device list attached to the contract. If that catalog changed over the period in question, proving the rate that should have applied requires the version in force on each invoice date, not the current one. A duplicate certificate fee is straightforward to document because it shows up as two line items for the same asset and date. It is also easy for a vendor to concede, because it requires no interpretation of contract terms, only a comparison of two invoices. ## 4. What documentation makes an older claim collectible? A collectible claim names the specific invoice, the contract clause it violates, the correct rate or frequency, and the dollar difference, not a general sense that billing has been wrong. Strong documentation gives a vendor less reason to dispute a claim and more reason to verify and settle it, because the work of confirming it has already been done for them. Start from the invoice, not the complaint. Pull the specific invoice number, date, device or asset ID, and the line item in question. Match it against the contract clause or rate schedule that governs that device or that calibration interval. State the correct value next to the billed value: the frequency the schedule actually calls for versus what was billed, or the tier rate the contract specifies versus what was charged. The dollar difference should follow directly from that comparison, not be estimated separately. Where the contract's audit clause requires written notice within a window, date-stamp the claim itself. A claim raised inside the window but not resolved before it closes is generally still valid, because the clock governs when the dispute is raised, not when it is settled. Confirm this reading against the specific clause language rather than assuming it; audit clauses vary on this point and the difference is a legal question, not a billing one. ## 5. Can a calibration overcharge claim be pursued if the vendor relationship is still active? Yes. An active vendor relationship does not waive a documented billing claim, and raising it does not require ending the contract. It does mean the claim should be framed as a reconciliation request under the existing audit clause rather than a dispute, which keeps the conversation inside the contract's own mechanism instead of turning it adversarial. Framing matters more than most buyers expect. A reconciliation request, invoking the audit clause and presenting the documentation directly, is a routine commercial exchange that calibration vendors have a process for. A dispute framed as an accusation invites a legal response instead of a billing one. The timing of the request relative to the contract's renewal cycle also matters. Raising it well before a renewal decision gives both sides room to resolve it on the merits. Raising it during a renewal negotiation ties the credit to negotiating room the buyer may not need, and can slow down a claim that would otherwise be straightforward. This is general information about how these claims are typically structured, not legal advice on a specific contract; a claim of meaningful size, or one the vendor disputes, should go through counsel before it is formally raised. ## 6. How do you stop the same calibration overcharge from recurring after it's recovered? Recovering a past overcharge does not fix the control that let it happen. The invoice review that missed the error the first time will miss it again unless the calibration schedule, the device tier list, and the invoice are matched at each billing cycle, not just when a retrospective audit happens to run. The fix is a recurring check, not a one-time credit. The root cause of a calibration billing error like this is a mismatch between two records that are rarely compared: the asset's actual calibration schedule and the invoice that bills against it. [Three-way matching against a purchase order](/guides/sub-hub-maintenance-and-msa-invoice-audit) checks that the invoice matches an authorized order. It does not check whether that order's frequency or tier still matches the equipment's current schedule. Closing that gap means someone, or some system, comparing the invoice line to the calibration schedule and the current device tier list at every billing cycle, not only when a periodic audit happens to catch it. That comparison is exactly what a [contract compliance audit](/answers/how-do-you-audit-calibration-and-safety-compliance-invoices) is built to run across a full spend category, calibration included, once, as part of establishing where the controls need to sit going forward, before handing the ongoing check to a [margin drift diagnostic](/margin-drift-diagnostic) engagement. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [the six categories drift hides in](/guides/indirect-spend-audit-categories) and [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates). ## Common questions ### Is there a fixed statute of limitations for calibration billing errors? No single fixed period applies everywhere; the statute of limitations for a written contract claim is set by state law and varies by jurisdiction. It is one of three clocks that can limit a claim, alongside the contract's own audit clause and the vendor's record retention period. Check the specific state law that governs your contract rather than assuming a standard window. ### What if the contract has no audit clause at all? If the contract is silent on billing disputes, there is no contractual clock limiting the claim, and the claim falls back to the state statute of limitations for a written contract. This is a legal question, not a billing one, and should be confirmed with counsel before a claim near that boundary is pursued. ### Can a vendor refuse to honor a claim just because it's old? A vendor can decline a claim that falls outside the contract's audit window, outside its own record retention, or outside the applicable statute of limitations. Inside those windows, a documented claim is a contractual reconciliation request, not a favor, though the vendor still has to be able to verify it against its own records. ### Does raising a calibration billing claim put the vendor relationship at risk? Framing it as a reconciliation request under the contract's own audit clause, rather than as an accusation, keeps the exchange routine. Vendors that provide calibration services under ongoing contracts generally have a process for this kind of request, since it is a mechanism the contract itself provides for. ### What records do I need before raising a calibration overcharge claim? You need the specific invoice number, date, device or asset ID, the contract clause or rate schedule that governs that device, and the correct frequency or tier compared against what was billed. The dollar difference should follow directly from that comparison rather than being estimated. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us