Contents
Contents
Government contract refund fraud keeps refunds, rebates or credits that the government is owed, or leaves prohibited charges on its bills. The missing money can sit behind a delivery exception code, an expired training package or a commercial rebate that never reaches the government account. If you work in accounts receivable, delivery operations or finance, you may see the event that should have changed the bill and the decision that kept it unchanged. The invoice tells the government what to pay. The records behind it can tell a different story.
Government contract refunds, rebates and credits become fraud when a contractor knowingly hides or keeps money the government is owed. The contract or order supplies the right to repayment, and the transaction supplies the event that activates it: a late delivery, an unused course, a qualifying rebate or a charge the contract excludes.
The refund can disappear at different points: the performance report, the unused balance, the invoice component or the pricing adjustment. The cases show why the contract term and the company’s treatment of the money belong in the same conversation.
UPS allegedly used false delivery times, invalid exception codes and inaccurate performance reports to prevent government customers from receiving late-delivery refunds. The Justice Department’s 2015 settlement announcement described a case brought by a former employee involving Next Day Air service, including General Services Administration contracts.
The alleged conduct ran from 2004 through 2014. The package’s arrival time was a financial fact: it determined whether the customer received the service promised or became entitled to money back. An exception code could change what the billing process did with that fact.
For someone inside delivery operations, the important comparison is the actual delivery against the scan, the exception assigned to it and the report given to the customer. For someone in finance, it is the same shipment’s charge and refund history. The alleged scheme connected those records by changing the account of performance on which the refund depended.
The package could arrive and the government could still be shortchanged. Delivery completed the shipment. It did not erase the promise about when it would arrive.
Learning Tree International agreed to pay $4.5 million in 2010 to resolve allegations involving advance billing and retained money for unused training. Its General Services Administration contract required billing after service, according to the Justice Department’s announcement.
The company allegedly billed multi-course vouchers and training passports in advance. When packages expired with courses unused, it allegedly kept the money instead of refunding or crediting it. Federal agencies had paid for training their employees never took, and the company allegedly kept the unused balance too.
When unused federal training credits are retained after package expiration, the question is where the balance went. In Learning Tree, the event described by the government was package expiration. The package terms, course-use records and billing terms connect the unused training to the money retained.
Verizon paid $93.5 million in 2011 to resolve allegations that it billed property taxes, common-carrier recovery charges and other surcharges contrary to its government contracts or applicable regulations. The Justice Department identified the FTS2001 and bridge contracts and MCI Communications Services as the invoicing entity. The settlement resolved a whistleblower case.
A bill could contain the contracted service alongside a surcharge the government had not agreed to pay. Looking only at the main service price would leave the alleged overcharge untouched.
We examine those invoice components with the employee who knows how they were applied, connecting the disputed charges to the contract and the money collected.
VWR allegedly withheld rebates and incentives that should have affected government prices, imposed increases on government customers alone and failed to make required reductions or refunds. The 2024 Justice Department announcement concerning Avantor described conduct under General Services Administration contracts and purchasing arrangements with the National Institutes of Health and the Department of Veterans Affairs.
The allegations covered 2008 through 2017. A former VWR employee brought the whistleblower case. The government’s account included commercial pricing changes that VWR allegedly failed to report, leaving government customers paying more than their agreements required.
A rebate changes the economics of a sale even when the printed price stays the same. The useful records therefore extend beyond the price list: commercial invoices, rebate arrangements, the contract’s designated comparison customer and the government’s own invoices belong together.
Bottini Fuel illustrates the state and local version of the problem. In its 2018 guilty plea to falsifying business records, reported by New York’s comptroller, the company admitted diverting customer credit balances. Government customers included schools, prisons, towns and state agencies.
The account already reflected money belonging to a customer. The scheme diverted that balance instead of returning it.
If you have seen supplier credits not returned to state purchasing customers, that is the pattern we examine with you. Bottini supplies a specific New York example, with state and local customers at its center.
Yes. Government pricing agreements can require reductions or refunds even when the goods arrived. The VWR allegations concerned what government customers paid under their agreements, including omitted rebates and incentives.
Traditional General Services Administration Schedule pricing used commercial-sales disclosures and a negotiated comparison customer or customer category. Under the Price Reductions Clause, a covered change in that pricing relationship could require a corresponding government reduction. The commercial transaction, the agreed comparison and the effective dates determined which adjustment the government was owed.
Under the newer Transactional Data Reporting model, that customer-tracking promise ends when the relevant contract modification takes effect.
We examine the agreement that governed the transaction, including the modifications in effect when the sale occurred. That connects a rebate in the commercial ledger to the government price or refund it should have changed.
The useful proof connects the contract’s promise, the event that changed what the government was owed, the bill and the money retained.
Which records matter depends on how the contract pays. We work through that with you, connecting the operational records you understand to the money the government paid.
Under the cost-reimbursement payment clause, the final accounting must include refunds, rebates and credits attributable to the government contract. A credit received after the government paid the original cost still belongs in that accounting. We connect it to the earlier charge and the amount ultimately kept.
A credit memo and a payment ledger also answer different questions. One records the adjustment. The other shows whether it reached the government account. We follow the adjustment to the government account and identify any balance that remained with the contractor. In a delivery case, we also connect that financial trail to the original performance records.
Management’s ability to override accounting controls matters alongside the records themselves. Unique Characteristics of Management Override Fraud Cases, published in the Journal of Forensic and Investigative Accounting in 2019, compared occupational fraud cases involving management override with cases involving missing controls. The study found management-override fraud in organizations that had internal audits, independent financial audits and anti-fraud policies.
For a retained-credit inquiry, that points us toward who could approve, change or bypass an adjustment. We connect your understanding of those decisions to the entries themselves. The employee who knows why a credit disappeared can explain something a ledger alone cannot.
The False Claims Act reaches knowingly false payment requests, false records that matter to payment and knowing concealment or avoidance of money owed to the government. Keeping an overpayment is a reverse false claim when the money is owed back to the government and the contractor knowingly conceals or avoids that obligation.
We examine what the company knew about the obligation, how its records affected payment or repayment, and who decided to keep the money. That connects the contract terms to the conduct of the people operating the account.
A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.
If you know why a government refund never left the business, speak with our whistleblower experts about the account and the decision behind it. We work beside you to build a case connecting the contract, the missing credit and the people who controlled the money, and bring in government contract fraud whistleblower lawyers who understand pricing and repayment cases. We stay with you through the case.