Contents
Contents
Government IT contractor fraud uses false claims about software, staffing, prices or performance to obtain public money. The government buys a working system, qualified people or a specified assessment method. The contractor represents that it supplied them. Inside the business, someone knows which employees actually did the work, which functions worked and how the invoice was calculated. That gap between the promise and the work is where a whistleblower’s knowledge matters.
Civilian IT cases reach federal agencies, state systems bought with federal grants, and city technology projects.
A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.
A false functionality claim tells the government that a system works as required while concealing the gap between that claim and the delivered software. The specific requirement matters: medical-record functionality, eligibility calculations or system integration.
Computer Sciences Corporation agreed to a $389,355 settlement in 2018 over its electronic medical-records system at Hanford. The Justice Department alleged that the company represented the system as functional and compliant with its contract and Department of Energy requirements. The software was part of an occupational-health contract. Former employees brought the whistleblower case.
For someone working on a medical record system billed as functional, the useful comparison is the required capability, what the system actually did and what the company told its customer. We connect those facts to the claim for payment.
IBM and Cúram faced allegations about software readiness, eligibility calculations, life events, tax credits and integration in Maryland’s health-benefit exchange. Federal health grants helped pay for the state’s IT purchase. IBM agreed to a $14.8 million settlement in 2019.
After its October 2013 launch, Maryland terminated and replaced the platform. Taxpayers helped pay for a system the state then replaced. A readiness representation reaches the people who know whether eligibility calculations and integration worked when the representation was made.
Government IT contractor staffing fraud can conceal who performed the work or bill people as meeting qualifications they lacked. The contract can buy a particular level of skill and restrict who may have access to the work.
The Justice Department alleged that Global Computer Enterprises concealed prohibited personnel on software contracts. At the Department of Labor and Equal Employment Opportunity Commission, the allegations concerned citizenship or immigration conditions. The account also identified clearance, qualification or overseas-location restrictions on work for the General Services Administration and Secret Service.
For the people assigning staff, those promises have names attached to them: the employee assigned, the qualification required and the location from which the work was performed. We compare the staffing representation with the people actually supplied and the work billed.
Hourly contracts make that comparison especially concrete. The federal hourly-payment clause ties payment to specified labor qualifications, subject to the contracting officer’s authorization. Timekeeping, labor categories and that authorization belong together. A person may have worked the hours while lacking the qualification the government purchased.
A false certification can tell the government that a contractor used the method it was paid to use when it used something else. The Foresee Results case shows that difference in a website assessment.
Foresee Results and Verint Americas agreed to a $7 million settlement in 2023 over website assessments for the Interior Department’s Federal Consulting Group. The government alleged that the companies promised the American Customer Satisfaction Index methodology and used a different method while representing that they used the promised one.
The buyer had selected how the assessment would be done. The alleged substitution changed that purchased service, even though an assessment was supplied. Someone who worked on the assessment could understand the difference that the customer-facing description concealed.
CFI Group USA and American Customer Satisfaction Index brought the Foresee whistleblower case. A business that understands the promised method can recognize a contradiction from another side of the sale.
IT overbilling can begin in the scope approval, the pricing proposal or the discount information that determines what the agency pays. Those records can explain an inflated bill even when people worked and software was delivered.
Hill Associates agreed in 2025 to pay at least $14.75 million to resolve allegations involving GSA Schedule IT services.
The government alleged that Hill supplied unqualified labor and performed cybersecurity work without a required technical evaluation. It also alleged out-of-scope services, unapproved fees, omitted prompt-payment discount information and unallowable incentive compensation in a proposal.
On a federal purchase, the contracting officer’s authority and the written modifications establish who could change the bargain. The program office asking for work, the office approving a contract change and the office paying an invoice have different roles. We examine what each approved and when.
The contract’s pricing history matters too. For a Schedule purchase, we compare the original pricing agreement with its modifications and their effective dates. That identifies the pricing promise in force for the transactions in question, including any required commercial-discount comparison.
Taleo’s human-resources software pricing case shows how the counting method can become the alleged overcharge. The Justice Department alleged that Taleo charged a higher employee-count-based rate for Transportation Security Administration software than its normal commercial method supported. Its subcontract promised commercial list rates with specified discounts. The government alleged that the pricing caused the prime contractor to submit false claims.
An insider who knew how Taleo counted employees and priced its commercial sales could explain the alleged overcharge. The supplier can control the price input while another company sends the government the invoice. A former Taleo employee brought the case.
Steering and kickbacks can inflate an IT purchase through the choice of who gets the work. In its June 2013 CityTime criminal-case release, the Justice Department alleged that corrupt work steering and kickbacks inflated New York City’s payroll-system costs. Its account of the alleged scheme identified participants in program management, systems engineering, consulting and subcontracting.
The useful question for an insider is who influenced the subcontract award and who benefited. Subcontract decisions and money flows can explain the price of a technology project alongside the work performed.
Control over the work also matters when a contract is reserved for eligible small businesses. In a civilian security-services parallel, the Justice Department alleged that former Paragon Systems executives controlled purportedly eligible companies to obtain Homeland Security contracts, then subcontracted substantially all the work to Paragon. Payments allegedly concealed as consulting payments formed part of that scheme. A whistleblower brought the case.
The company named on the contract and the company controlling performance can be different. Bids, management instructions, payroll and subcontract payments help explain that relationship. The staffing story includes who directs the work as well as who appears on the invoice.
The useful proof connects the contract’s promise, the contradictory work or business record, the payment and who knew about the difference. Our whistleblower experts help you make those connections, whether your knowledge comes from developing the software, assigning staff or setting the price.
An invoice, acceptance of the work and payment are separate records. We connect what the company told the buyer to what the agency accepted and paid for, and to the people who knew how the work was actually performed.
Electronic procurement puts requisitions, purchase orders, invoices and requests for proposals into systems that can make those records easier to compare. Transparency International’s 2024 paper, Transparency, Accountability, and Integrity of Public Procurement Systems, explains that online procurement can widen access to purchasing information and improve supervision. It also makes a point familiar to anyone who has implemented an agency system:
Overall, it transpires that introducing e-procurement systems in any public administration requires far more than a simple purchase of a software, it almost always requires amending administrative procedures, shifting duties and controls within public organisations.
The purchase includes a change in how people work. That is why the people handling approvals and performance have knowledge beyond the invoice stored in the system.
A 2022 review published in CEUR Workshop Proceedings, Public Procurement Fraud Detection and Artificial Intelligence Techniques: A Literature Review, describes methods that examine tender text and relationships among procurement participants to identify suspicious patterns and prioritize investigation.
Those comparisons give investigators places to look. The person who knows which staff worked, which method was used or how the price was calculated can explain the transaction behind the pattern. That is the knowledge we build a case around.
If you worked on the system, assigned its staff or priced the contract, talk with our whistleblower experts about what the government was told and what your team delivered. We work beside you to build your strongest case around that difference and bring in government contract fraud whistleblower lawyers who understand software performance, staffing and pricing. We stay with you from the first assessment through the case.