A federal contractor that stays quiet about credible evidence of fraud inside its own ranks isn't just skipping an ethics-program box — under FAR 52.203-13, that silence is itself a violation, one regulators can use to bar the company from all federal contracting regardless of how the underlying fraud plays out. The clause is written into solicitations and contracts expected to exceed $7.5 million with a performance period of 120 days or more, and it requires contractors to tell the government in writing — and fast — the moment they learn a principal, employee, agent, or subcontractor may have broken specific federal laws in connection with a government contract. Missing that window doesn't just look bad in a debrief; it opens a second, independent path to suspension or debarment that exists entirely apart from whatever crime triggered the disclosure duty in the first place.
Two Triggers: Title 18 Fraud and the Civil False Claims Act
FAR 52.203-13 doesn't ask contractors to report every internal suspicion or HR complaint. The disclosure duty attaches to two specific categories of conduct. The first is a violation of federal criminal law under Title 18 of the U.S. Code involving fraud, conflict of interest, bribery, or gratuity violations, committed by a principal, employee, agent, or subcontractor of the contractor in connection with the award, performance, or closeout of the contract or a subcontract under it. The second is a violation of the civil False Claims Act, 31 U.S.C. 3729-3733 — the statute the government uses to recover damages for false or fraudulent claims for payment. The clause states the obligation directly: "The Contractor shall timely disclose, in writing, to the agency Office of the Inspector General (OIG), with a copy to the Contracting Officer, whenever, in connection with the award, performance, or closeout of this contract or any subcontract thereunder, the Contractor has credible evidence that a principal... has committed a violation of Federal criminal law."
Two words carry the weight of the clause: "credible evidence." The rule doesn't require certainty, a completed internal investigation, or a referral from outside counsel — it requires disclosure once the evidence clears the credibility bar, a lower and earlier trigger than many contractors assume. And the clause doesn't route the disclosure to the contracting officer alone; the OIG gets the primary copy, with the CO copied, meaning a contractor cannot resolve the matter quietly through its usual contract-administration channel and consider the disclosure duty satisfied.
No Fixed Deadline, No Escape: The Clock Runs Three Years Past Final Payment
The FAR text notably avoids a bright-line day count. Where other compliance clauses specify 30, 60, or 90 days, 52.203-13 uses only the word "timely." That ambiguity is deliberate and unfavorable to contractors: it lets contracting officers and the OIG judge each case on its facts rather than letting a contractor run out a fixed clock before disclosing. In practice, "timely" is read to mean promptly after the evidence becomes credible — not after an internal investigation wraps, not after outside counsel signs off, and not after the contract closes out.
That last point matters because the disclosure duty itself doesn't end at contract closeout. It runs "until at least 3 years after final payment on the contract." A contractor that discovers, two years after final invoice, credible evidence that an employee falsified test data on a contract that's long since closed still owes the same written disclosure to the OIG and the CO. Treating a closed contract file as a closed compliance question is exactly the assumption this clause is built to defeat.
Silence Is Its Own Cause for Debarment Under FAR 9.406-2
The consequence for skipping disclosure isn't limited to whatever penalty attaches to the underlying fraud or false claim. FAR 9.406-2(b)(1)(vi) makes the failure to disclose a freestanding, independent cause for debarment — on top of, and separate from, the misconduct that should have been disclosed. The regulation defines the cause precisely: "Knowing failure by a principal, until 3 years after final payment on any Government contract awarded to the contractor, to timely disclose to the Government, in connection with the award, performance, or closeout of the contract or a subcontract thereunder, credible evidence of" a Title 18 violation, a False Claims Act violation, or a significant overpayment on the contract.
That structure means a contractor facing a fraud allegation can, in effect, face two separate debarment exposures from a single set of facts: one for the fraud itself if proven, and a second, independent one for knowingly sitting on credible evidence of it. The word "knowing" is the qualifier that matters for defense purposes — the debarment cause attaches to a principal's knowing failure to disclose, not to an honest failure to recognize evidence as credible. But once a principal has actually seen credible evidence and let it sit, the three-year clock measured from final payment gives the government a long window to bring the debarment case, well past the point most compliance teams consider a contract closed.
What It Means for Contractors
The practical takeaway is that mandatory disclosure has to be a live, standing process, not a closeout-triggered checklist. Ethics and compliance programs required under FAR 52.203-13 already obligate contractors to maintain an internal control system capable of detecting this kind of conduct; the disclosure clause turns detection into an affirmative reporting duty the moment evidence clears the credibility threshold, regardless of where the contract sits in its lifecycle. Contractors should route credible-evidence findings to the OIG and the CO in writing as soon as they surface — not after an internal investigation concludes, and not on the assumption that a matter tied to a closed contract is no longer reportable. Legal and compliance teams should also treat the three-year post-final-payment window as an active retention and monitoring period, since a principal's knowing failure to disclose during that window is enough on its own to support a debarment action, independent of how the underlying fraud or false-claims allegation is ultimately resolved. Contractors that build disclosure into a standing compliance workflow — rather than a step someone remembers only during an audit or a closeout review — are the ones least likely to face a debarment referral built entirely on their own silence rather than on the underlying conduct.
