A dinner receipt uploaded to an expense app doesn’t look like the start of a federal case. It looks like a chore. The employee snaps a photo, taps a category, adds a note about who was there, and moves on. But that little bundle of data, timestamps, GPS coordinates, merchant codes, card swipe, receipt image, approver ID, cost center, is exactly the kind of clean, structured record federal prosecutors love.
Corporate card platforms and reimbursement software were built to speed up the month-end close. They also happen to produce, at scale, the tidiest fraud evidence a grand jury has ever seen. Routine spend leaves a trail that outlives memory, outlives employment, and increasingly, outlives the company’s own retention policies.
How Small Line Items Become Federal Charges
Federal prosecutors rarely charge a single padded dinner. What they charge is the pattern, and the wires that carried it. The Justice Manual‘s guidance on credit card fraud walks through how the general fraud statutes, wire fraud in particular, reach conduct that starts as a card swipe and ends as an interstate electronic transaction. When a corporate card is involved, almost every relevant act, submission, approval, and reimbursement crosses a wire.
The exposure grows sharply when federal money is anywhere in the chain. If the employer bills the government, receives grant funding, or contracts with a federal agency, an inflated expense that gets folded into an invoice or an indirect cost pool can pull the conduct under the false claims framework the DOJ describes in its policy on fraud against the government. A single padded dinner is not a federal case. That same dinner billed through to a federal contract, repeated across a year, with a Slack message telling a subordinate to “just code it to the project,” is a very different document.
What Investigators Actually Pull From the Software
The value of these platforms to an investigator is that everything is already normalized. There is no reconstruction. A few queries produce a spreadsheet that a jury can follow.
- Card-level transaction data. Merchant name, merchant category code, city, amount, and the exact timestamp of authorization. Duplicate charges, weekend hotel spend, and out-of-policy vendors surface with a filter.
- Receipt metadata. The image itself, plus EXIF data showing when and where the photo was taken. A receipt “from Tuesday’s client dinner” photographed on a Saturday afternoon at the employee’s home is its own small confession.
- Submission and approval logs. Who submitted, who approved, when, from what IP address, and whether the report was edited after approval. Rubber-stamp patterns show up clearly, as do managers who approved everything a subordinate sent in ninety seconds flat.
- Policy and coding history. Every time a category was changed, a project code reassigned, or a note edited, the system usually keeps a version. Reclassifying a personal trip as “business development” three weeks later is a discoverable event, not a private correction.
The Patterns Investigators Look For First
Expense reimbursement fraud is unusually durable. Insurance-industry analysis of these schemes points out that the underlying conduct usually runs for a long stretch before anyone notices, because each transaction is small and the review is cursory. Once someone does look, the same signatures appear again and again: round-number receipts, sequential vendor invoices from the same printer, mileage claims that overlap with card charges in another city, per-diems drawn on days the calendar shows the employee was on vacation.
None of those, by themselves, prove intent. Together, across a year, they build the narrative prosecutors need. And the platform holds the raw material in a form that can be exported without an interview.
What This Means If You’re the One in the File
Someone who learns their expense history is being reviewed, by an auditor, by outside counsel, by a federal agent at the door, is often tempted to log in and “clean up” a few entries, or to explain the pattern in a friendly interview. Both instincts are dangerous. Edits to records after notice of an investigation raise obstruction questions that can be worse than the underlying spend. And an interview without counsel, in a matter where the documents are already assembled, rarely helps.
The better move is early, quiet advice from a lawyer who handles federal financial crimes defense, before talking to the company’s investigators, before responding to a preservation request, and certainly before touching the platform. The receipts are not going anywhere. The strategy for how to explain them is what still has room to move.
The expense report used to be paperwork. It is now a recording. Treating it like one, on the front end when policies are written and on the back end when questions start, is the only version of this that ends well.
