False Claims Act
For government contractors responsible for tracking time records under government procurement contracts—and for federal grantees responsible for submitting time and effort documentation to their federal funding agencies accurate timekeeping records are crucial.
False Claims Act Settlement
Falsifying Timesheets for DEI Requirements
The Hierarchy submits the worker’s timesheets to the Urban Affairs Coalition omitting the Caucasian laborer’s name so it is recorded on federal grants as the Black “The Hierarchy’s” labor. This loophole for meeting DEI goals also results in the worker not receiving 1099s.
Inflating Hours for Unjust Enrichment
The victim reported to UAC C-Suite management that The Hierarchy was inflating its timesheet hours. The one scheme involves Mr. Latoison rounding hours worked up to the highest full hour where the minutes worked are greater than seven minutes. It is estimated this resulted in $81,000 in unjust enrichment. In addition, The Hierarchy bills for overtime hours not previously approved by UAC and keeps the overtime to bootstrap his company. A rough estimate of this angle is $104,000. Then, of course, the missing payroll of $35,406 + the labor hours stolen.
The programmer also found the construction contracts were reporting the gross pay as a freeform number; not [Hours] * [PayRate]. This is compounded by a former Hierarchy programmer creating an SQL view with the same name as the Timesheet table and changing the front-end ODBC to display the view that obscures data used in reporting labor on contracts instead of the actual table.
The programmer was blasted in an email for finding what he believed to be fraud. The programmer was told that this intentional inflating of hours was necessary DUE TO DIVERSITY.
Here is an excerpt of the eMail from Latoison that he said he sent to UAC EDP C-Suite management and his wife’s Gmail account: (using personal email on government contracts is forbidden).
I’m going to send an email out to EDP concerning the changes you’ve made to their RDB’s.
When you were rather forcefully explaining to me why you believed their reports to be wrong, I was trying to convey that you’re thinking was incorrect.
EDP’s reports for many clients get checked against the client’s own reporting (some clients have done their own work with the payrolls separate of EDP) and they tend to match. This is in part, due to the very valid reasons why the RDB’s were stopped from doing the math for the gross pay versus allowing Data Entry people to hand type it.
You are not mistaken concerning the general rule that data entry mistakes can happen as human beings tend to be less than perfect, but part of the RDB’s design, which has worked for over a decade is that some reports in the main RDB help to flag issues with other reports in the same system.
What is needed here is a more open mind about how things can be designed.
The reason developers still have and will always have work is due to the diversity of how IT needs to be wrapped around various clients, in different and diverse ways, to meet the business requirements.
… You are being directly disrespectful…
…make sure its doing what they actually need it to do, versus ANY standard.
Is Latoison admitting that DOL timesheets on construction projects and UAC reports to the government use special math for minorities where 1+1 does not equal 2? Is it a coincidence that every deviation results in getting paid more? For ten years dollars have been inflated?