False Claims Act Conspiracy: When Someone Else Sends the Bill

False Claims Act conspiracy involves an agreement to commit a False Claims Act violation. Causing a false claim reaches a business that knowingly causes another company to submit one. The company sending the bill may be only the last stop. A supplier may provide the false certification, a manufacturer the defective diagnostic kit, or a provider the diagnosis that changes a health plan’s payment. If you know where the false information entered that chain, what you know can reach the company behind the invoice.

A qui tam case allows a private whistleblower to pursue the government’s claim. A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.

What Does It Mean to Cause Another Company to Bill?

Causing another company to bill means that a business’s knowing conduct leads another business to submit a false claim. The False Claims Act reaches both the party submitting the claim and the party causing its submission. It separately reaches someone who knowingly makes or uses a false record or statement that matters to a false claim.

That distinction matters in businesses where production, certification and billing sit in different hands. The quality department may know whether a product passed the required inspection. A contractor’s pricing team may supply the cost information used to negotiate government payment. A laboratory may use a manufacturer’s diagnostic kit and submit the resulting reimbursement claim.

A bill sent to a contractor or grant recipient can also fall under the law when it seeks money for government work or a government program and the government funds or reimburses at least part of the request.

Knowledge includes knowing the information is false, deliberately avoiding the truth, or recklessly disregarding it. The false information must be capable of influencing payment. We connect what the business knew to the statement it supplied and the claim that followed.

What Makes a False Claims Act Conspiracy?

False Claims Act conspiracy centers on an agreement to commit a violation covered by the Act. The agreement may concern causing false claims, using false records, or improperly keeping money owed to the government.

The practical question is what the participants agreed to do. Who supplied the false information? Who understood what was wrong with it? What did each participant do to put the shared plan into effect? Instructions, certifications and the claims they supported let us examine those questions together.

When companies take similar steps, we look for the shared plan behind them. We examine each company’s role and knowledge, including what information passed between them.

That is why a person working upstream can have such valuable evidence. Someone who saw the inspection skipped, the pricing information changed or the instruction passed along may know how the payment request became false before billing ever saw it.

A Supplier’s Certification Can Reach a Shipyard’s Bill

The Navy generator-set dispute involving Allison Engine shows how a government contract can pass through several businesses before a bill reaches the government. The Supreme Court’s 2008 opinion describes shipyards hiring Allison Engine to build generator sets for destroyers. Allison Engine hired General Tool Company to assemble them, and General Tool hired Southern Ohio Fabricators to make the bases and enclosures.

The subcontracts carried the Navy’s specifications. Each delivered generator set required a certificate stating that it met those requirements. Former employees alleged that gearboxes leaked, required final inspections had been skipped and welders failed to meet military standards. They alleged that the suppliers nevertheless issued certificates saying the work complied.

That dispute put each handoff in view: the manufacture of the parts, their assembly, the certificate and the invoice sent to the shipyard. For someone inspecting the equipment, the disputed fact was whether the work met the specification. For someone preparing the certification, it was what the certificate represented. The same generator set connected them.

Congress changed the law the following year through the Fraud Enforcement and Recovery Act. The Congressional Research Service’s 2009 report, Qui Tam: The False Claims Act and Related Federal Statutes, explains the change: the claim need not go directly to the government, and false supporting information matters when it can influence payment.

The report also explains why the conspiracy amendment mattered. It extended conspiracy to the Act’s other violations, including schemes to keep money owed to the government. The supplier’s part in the transaction deserves attention even when another company handles the government-facing bill.

The Evidence Trail Runs Backward From the Payment

The useful evidence connects the false information, the claim or unpaid obligation, the government money and what the participants knew when they acted. A conspiracy allegation adds the agreement connecting their roles. We work through that chain with the insider who understands the business.

Product qualification records can connect a failed specification to a certificate. Pricing disclosures connect the cost information supplied by a contractor to the government’s bargain. Diagnosis records connect clinical information to a health plan’s payment. Experimental results connect work in a laboratory to a grant application or progress report.

The timing belongs in that picture. What did the company know when it supplied the information? In a 2023 decision involving pharmacy pricing, the Supreme Court focused on the businesses’ knowledge and beliefs at the time. An explanation developed afterward does not erase a contemporaneous belief that a claim was false.

For someone considering reporting fraud under the False Claims Act, the starting point may be the handoff they witnessed. We connect that knowledge to the payment records and the other participants’ decisions. A product inspector, coding employee or pricing specialist can explain a discrepancy that a finished invoice conceals.

A Rubber Stamp Became a Diagnosis Code

The whistleblower complaint against Kaiser Foundation Health Plan alleged a particularly concrete handoff. According to the complaint, a dietician stamped a Medicare Advantage enrollee’s medical record with an opinion of malnutrition or severe malnutrition, and physicians countersigned the stamp. The complaint then described the coding decision:

To examine responsibility across that chain, we connect each participant’s action and knowledge to the payment information. The conspiracy question concerns what they agreed to do with it.

The Same Question Reaches Different Industries

False information can enter through a product, a price, a research result or an import declaration. These cases show where to look in the business relationship and how the alleged conduct connected to government money.

Healthcare Manufacturers and Downstream Claims

Quest Diagnostics agreed to a $262 million federal civil settlement in 2009, with approximately $45 million for the whistleblower. The Department of Justice alleged that inaccurate diagnostic kits caused downstream reimbursement and unnecessary treatment claims.

The government alleged that the defect reached payment through laboratories and health care providers using the kit and submitting reimbursement claims. That puts product knowledge upstream of the billing record at the center of the inquiry.

Government Contractors and Pricing Information

Raytheon agreed to a $428 million False Claims Act settlement in 2024 over allegations involving untruthful certified cost and pricing disclosures. The Justice Department’s account connects the disclosures to government contract negotiations. The whistleblower’s share was $4.2 million.

The relevant information entered when the price was being established. A pricing employee may understand the discrepancy in the cost data long before the negotiated price appears on an invoice. We examine the information used to secure that price and who knew what the disclosures left wrong.

Research Grants and Fabricated Results

Duke University agreed to a $112.5 million settlement in 2019 after a whistleblower alleged that fabricated research supported applications and progress reports for National Institutes of Health and EPA grants. The Justice Department’s settlement announcement concerned the connection between research evidence and federal funding. The whistleblower’s share was $33.75 million.

The whistleblower pursued the case after the government declined to take it over. The laboratory results and the grant documents supplied different parts of the alleged mechanism. For a research insider, the important handoff can be the movement of an experimental result into the account given to a funding agency.

Customs Duties Owed to the Government

Linde’s 2020 settlement resolved allegations of misstating imported goods’ classification, nature, value and eligibility for favorable trade treatment. Those allegations concerned duties owed to the government.

The money moved in the opposite direction from an ordinary reimbursement claim. The false information allegedly reduced what the importer paid. The conspiracy provision’s coverage of reverse false claims makes the agreement question relevant to that kind of obligation too: what did the participants agree to do about money the government was owed?

You Know Where the False Information Started

If you saw a false certification leave your company, a product problem reach a customer’s claims or businesses coordinate the story behind a payment, you may know how the false claim began. We build the case around those connections, bring in False Claims Act whistleblower lawyers who understand your industry and stay beside you throughout the case. Speak with our whistleblower experts about building your strongest whistleblower case from the connections you saw.