Contents
Contents
Government contract fraud when work was completed can involve false prices, false eligibility or false certifications that influenced the award or payment. The bridge can be painted, the software delivered and the technical report finished while the contractor misrepresents something else the government bought. If you know who supplied the materials, which customers received the discounts or what an invoice originally said, you may know the part of the transaction the finished job cannot show.
The cases turn on different promises. A disadvantaged business enterprise was supposed to supply the paint. Commercial discounts were supposed to inform a government price. Technical advice was supposed to be independent. A progress payment was supposed to have truthful support when requested. Completion answers none of those questions.
A false certification misstates a fact or a promise the government relies on in buying or paying for work. It can concern the supplier’s eligibility, the independence of its advice, the price information it disclosed or the performance behind a payment request. The completed deliverable and the certification concern different parts of the purchase.
For a civil False Claims Act case, the connection runs through what was false, what the contractor knew and how the falsehood mattered to the government’s money.
That is why an employee’s account can reach beyond whether the customer seemed satisfied. The person accepting the finished work may see a different part of the transaction from the person negotiating the price or reviewing a supplier certification. The case takes shape where those accounts meet.
Completed construction work can still involve false DBE participation and wire fraud when the contractor obtains the award through a materially false promise about who will supply the project. The Supreme Court’s opinion in the criminal case involving Alpha Painting and Construction describes painting projects in Philadelphia whose work met expectations. The promise about the supplier was another matter.
Alpha represented that it would obtain approximately $6.4 million in painting supplies from Markias, a qualified disadvantaged business enterprise. The opinion describes how an Alpha manager negotiated directly with the actual suppliers and arranged for their purchase orders to be billed through Markias. Markias added a fee and forwarded the invoices. Checks covered its markup and the actual supplies, and Alpha reported qualifying payments to Markias as the projects progressed. Markias ultimately collected about $170,000 for its pass-through services.
Markias supplied the paperwork. The other businesses supplied the paint.
That arrangement gave the appearance of DBE participation while leaving the actual purchasing elsewhere. We see a fee for pretending to be the supplier. A good paint job does not make that participation real. The opinion describes a pass-through that performed no commercially useful function in that role.
The Third Circuit’s account of a separate criminal scheme involving Schuylkill Products and CDS Engineers shows how far the disguise could extend. Marikina appeared as the disadvantaged business enterprise while Schuylkill and CDS performed the work. Employees used Marikina stationery and email addresses. Magnetic placards covered the companies’ vehicle logos with Marikina’s logo.
For someone on the project, the useful distinction is who actually ordered, negotiated, supervised, transported and got paid. The company name on an invoice carries only part of that story.
There is a broader reason these promises exist. Transparency, Accountability, and Integrity of Public Procurement Systems, published by Transparency International in 2024, explains how supplier-selection criteria can advance public policy goals, including equality and environmental sustainability. In Alpha’s contracts, participation by a qualifying business was part of what the public purchase was intended to achieve.
GSA pricing fraud can concern the price the General Services Administration accepted for a real product. Commercial-sales disclosures and later discount obligations can affect that price before and after the first delivery.
Oracle agreed to a $199.5 million settlement over allegedly false commercial-pricing information and discounts the government did not receive. Its contract covered software licenses and technical support. In the Justice Department’s settlement announcement, the alleged harm was that incomplete disclosures led the government to accept lower discounts and pay too much. A former employee brought the whistleblower case. The Justice Department and the General Services Administration’s Office of Inspector General investigated the allegations and pursued the case.
NetApp agreed to a smaller settlement, $128 million, involving hardware, software and storage-management services. The government alleged the same pricing failures: incomplete commercial-sales disclosures and discounts withheld from government purchasers. The product’s presence in a government office did not answer what the government should have paid for it.
Symantec provides a judgment to compare with those settlements. The Justice Department reported that Gen Digital, formerly Symantec, paid $55.1 million to satisfy a judgment. The court found knowing false commercial-sales disclosures during negotiations and continuing false certifications during performance. It also found violations of the contract’s price-reduction promise. The whistleblower had administered the contract, and the government joined the case.
Inside a sales department, the revealing record can be an actual commercial invoice, rebate or concession that differs from the pricing practices disclosed to the General Services Administration. The traditional Schedule bargain used those disclosures to negotiate a price and identified a customer or customer category against which later discounts would be tracked. A published price list could miss the concessions customers actually received.
The December 2025 Schedule revision removed that discount-tracking promise as contracts adopted the new terms.
The government can receive technically useful advice while losing something it expressly required: independence from conflicting business interests. Science Applications International Corporation, known as SAIC, supplied technical advice to the Nuclear Regulatory Commission.
SAIC advised the commission about possible release or recycling of material with very low levels of radioactivity. The government alleged that SAIC repeatedly certified that it had no conflicting business relationships while working with entities financially interested in the rulemaking’s outcome. SAIC agreed to a $1.5 million False Claims Act settlement in October 2014. An earlier False Claims Act judgment had been set aside before the settlement.
The court’s earlier opinion describes the alleged overlap. The government argued that SAIC’s work for British Nuclear Fuels created a potential conflict because the project’s radioactive materials would become subject to the commission’s regulation. SAIC also performed consulting work for Bechtel Jacobs. The government alleged that an employee copied material from a report prepared for the commission into a report for Bechtel Jacobs.
SAIC argued that it had delivered high-quality, technically sound work. The court acknowledged evidence of that quality and of the commission’s continued use of the work. It also described the independent peer review the commission arranged after learning of the alleged conflicts. An agency employee testified that the alleged conflicts and resulting public distrust prevented the work from serving as the technical basis for the rulemaking as originally intended.
The useful report was only part of the purchase. The government had bought advice it could rely on as independent when setting public safety rules.
A false construction progress payment can release money before it is due even when the project involves real work. The support for the payment has its own history.
Young-Montenay’s Department of Veterans Affairs boiler-renovation case involved a supplier invoice altered from $104,000 to $153,000. The contractor used the altered document to support a progress-payment request. The Federal Circuit’s opinion identifies the harm as money paid before it was due. A later genuine invoice for the larger amount did not make the earlier alteration true.
The falsehood had already done its job: it moved the payment forward.
Construction payment records can carry several promises at once. The federal progress certificate addresses work performed according to the contract, payments already due to subcontractors and suppliers from earlier government payments, and the intended use of the next payment. The schedule of values, inspection record, supplier invoice and subcontractor ledger therefore describe different parts of the same request.
An employee who saw the original invoice can explain something a final inspection cannot. The amount requested, the document used to support it and the date the money became due belong together. That comparison is what makes the altered invoice consequential even after a later invoice reaches the larger amount.
No. The Supreme Court’s May 22, 2025 decision involving Alpha Painting addressed criminal wire fraud, not the amount recoverable in a civil False Claims Act case. It held that inducing a payment through a material falsehood can constitute wire fraud even when the defendant did not seek to cause a net economic loss.
SAIC supplies the civil comparison: the court asked how much the alleged conflicts reduced the advice’s value to the government. The false promise and the amount lost each need their own evidence.
The most useful government contract billing evidence connects the governing promise to the transaction that contradicts it. The solicitation or contract identifies the obligation. The certification shows what the contractor represented and when. Purchasing, sales, personnel or project records show what actually happened. The invoice and payment history show how the representation reached the government’s money.
Those records often sit with different people. Federal purchasing separates the office that needs the work from the officials who award, inspect and pay for it. An invoice, agency acceptance and Treasury disbursement are distinct records. A receiving office can confirm delivery while a commercial sales ledger explains an undisclosed discount.
The same separation helps explain bid rigging behind a completed job. A project file can show work performed while bidding communications show who arranged an intentionally losing offer. The payment for real work follows an award whose supposed competition was manufactured.
The question across these cases is specific: what did the contractor say the government was buying, and what did people inside the transaction know? In the painting case, supplier orders contradicted the participation claim. In the Oracle and NetApp cases, the government alleged that commercial transactions contradicted disclosures. In Symantec, the court found false commercial-sales disclosures. In SAIC, outside business relationships bore on promised independence. In Young-Montenay, the original invoice contradicted the payment support. Each gives an insider a concrete way to explain why the finished job leaves something unanswered.
A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. The opportunity starts with the knowledge behind that contradiction: the supplier, the discount, the relationship or the changed document.
If you know the promise was false despite the completed work, speak to one of our Whistleblower Experts about what you saw. We connect your knowledge of the business to the contract and payment, build your strongest government contract fraud whistleblower case, and bring in government procurement fraud whistleblower lawyers who understand the disputed promise. We stay beside you through the decisions that follow.