Editing or "Fixing" a Receipt for Taxes: The IRS Fraud Line

Published: August 24, 2026 · Reading time: 9 min

TL;DR: Digitizing a receipt — cropping it, adjusting contrast, running it through an AI scanner that reads the vendor, date, and amount — is exactly what Rev. Proc. 97-22 expects and requires. Changing a number, a date, or a line item, or letting a tool "reconstruct" an illegible figure and presenting the result as the original, is a different act entirely. There are two separate penalty tracks: a noncompliant storage system risks the civil 20% accuracy-related penalty (§6662) or a misdemeanor recordkeeping charge (§7203); a fabricated document risks the civil 75% fraud penalty (§6663), potential criminal charges under §7206 or §7201, and — critically — no statute-of-limitations cap at all under §6501(c)(1). In the worked example below, a single $1,000 fabricated figure turns a $345.76 tax adjustment into a $605.08 one, plus exposure the dollar amount alone doesn't capture.

AI receipt scanners have made digitizing records faster than ever — snap a photo, and a tool reads the vendor, date, and total in seconds. That convenience creates a genuinely new question freelancers didn't have to think about with a shoebox of paper receipts: what happens when the photo is blurry, the thermal paper has faded, or the tool's best guess at a smudged number is wrong? The line between fixing a bad scan and fabricating a record matters more than it looks, and the IRS treats the two very differently.

Two Very Different Kinds of "Digital Receipt"

Reading a receipt — OCR extraction, AI categorization, a searchable index built from the image — leaves the source document untouched. Rewriting a receipt — changing what the image itself shows, or generating a "corrected" version and treating it as the original — does not. Both can look identical in a receipt-tracking app: a clean, legible entry with a vendor, date, and amount. Only one of them is what the IRS's own recordkeeping rules describe.

What the IRS Actually Requires: Rev. Proc. 97-22

Rev. Proc. 97-22, the IRS's governing guidance on electronic storage systems, sets the bar plainly. Under §4.01(1), an electronic storage system "must ensure an accurate and complete transfer" of the original record. §4.01(2)(b) goes further, requiring "reasonable controls to prevent and detect the unauthorized creation of, addition to, alteration of, deletion of, or deterioration of" electronically stored books and records. §4.01(4) adds an audit-trail requirement — the system needs to be able to trace an entry back to its source document.

The underlying substantiation standard those digital records have to satisfy is Treas. Reg. §1.274-5(c): documentary evidence needs to show "the amount, date, place, and the essential character of the expenditure." A $75 documentary-evidence exception (Treas. Reg. §1.274-5(c)(2)(iii)) means a receipt isn't strictly required for expenses under that amount — except lodging — but that exception is about not needing a receipt at all, not a license to invent one for a larger purchase.

Where Legitimate Digitization Ends

Auto-crop, contrast adjustment, deskewing a photo taken at an angle, converting to a searchable PDF — all of this is squarely inside what Rev. Proc. 97-22 contemplates. None of it changes what the receipt says; it changes only how legible or searchable the record is.

An AI tool "reconstructing" an illegible number and presenting the result as the receipt's actual figure is a different act. So is manually cropping out a line item, changing a total, or altering a date. The Cohan rule — a court's authority to estimate a deductible amount when records are genuinely missing — belongs to the court, not to the taxpayer or an app. It applies only outside the strict-substantiation categories §274(d) locks down: travel, meals, gifts, and vehicle or other listed property get no Cohan estimate at all, from anyone, under any circumstances. Filling in a plausible number yourself and calling it the record isn't an estimate — it's a fabrication with an estimate's dollar value.

Two Penalty Tracks: a Bad System vs. a Bad Document

Track 1 — a Noncompliant Storage System (Civil, Capped)

If your record-storage setup simply doesn't meet Rev. Proc. 97-22's requirements — no audit trail, no controls against accidental alteration, records that degrade or go missing — the exposure is a Notice of Inadequate Records under Treas. Reg. §1.6001-1(d), the 20% accuracy-related penalty under §6662(a) for the resulting understatement, or in a willful case, the §7203 misdemeanor for failing to keep required records (fine up to $25,000, or $100,000 for a corporation, up to one year). Serious, but bounded, and treated as a systems failure rather than an intent-to-deceive finding.

Track 2 — a Fabricated Document (Criminal Exposure, Uncapped Audit Window)

Altering what a receipt actually says, or generating a replacement and presenting it as the original, opens a different door entirely:

• §7206(1)/(2) — willfully subscribing to or presenting a document not believed true as to a material matter: a fine up to $100,000 ($500,000 for a corporation), up to 3 years imprisonment, or both.
• §7201 — tax evasion: a fine up to $100,000 ($500,000 for a corporation), up to 5 years imprisonment, a felony.
• §6663 — the civil fraud penalty: 75% of the underpayment attributable to fraud, versus 20% for ordinary negligence under §6662(a). Once any portion of an underpayment is shown fraudulent, the entire underpayment is presumed fraudulent unless the taxpayer proves otherwise.

The Statute of Limitations That Never Closes

This is the part that makes the two tracks not just different in severity, but different in kind. §6501(a) and (e) cap a normal audit window at 3 years from filing (6 years if omitted gross income exceeds 25% of what was reported). §6501(c)(1) removes that cap entirely for "a false or fraudulent return... with the intent to evade tax" — the IRS "may be assessed... at any time." A single fabricated document doesn't just risk that one deduction; it can keep the entire return open to audit indefinitely, long after every other year would have closed on its own.

Worked Example: A $1,000 Overstatement, Three Ways

A freelance photographer's actual computer receipt shows $1,400. Before an audit, they use an editing tool to change the total on the stored image to $2,400 — matching what they'd already claimed as a deduction. The IRS discovers the discrepancy at examination: a $1,000 overstated deduction. At a 22% marginal ordinary rate, with self-employment tax computed on 92.35% of net earnings and the standard above-the-line half-SE-tax deduction applied:

The dollar gap between the negligence scenario and the fraud scenario — $190.17 — understates the real difference. The fraud finding also carries potential criminal referral and removes the statute of limitations on the entire return, exposure that scales with nothing about the original $1,000 figure.

The Safer Move When a Receipt Is Missing or Illegible

Altering a document is never the fix for a bad or missing receipt — reconstruction from secondary evidence is. CentSense's guides on faded thermal receipts, the Cohan rule for lost receipts, and reconstructing a mileage log after the fact all cover legitimate paths: bank and card statements, calendar entries, contemporaneous notes, and — where the law actually allows it — a court's own estimate under Cohan. None of them require inventing what a document says.

A Practical Checklist for Using AI/OCR Receipt Tools Safely

1. Confirm the tool preserves the original image alongside any extracted data — the source file, unaltered, should always be retrievable.
2. Treat "enhance" and "auto-correct" features with caution if they change pixel values in the amount, date, or vendor-name region rather than just sharpening legibility elsewhere on the page.
3. If a figure is genuinely illegible, don't let a tool guess for you. Pull the transaction from a bank or card statement instead, and keep both records together.
4. Never overwrite the stored original once it's been categorized — the audit trail Rev. Proc. 97-22 requires depends on being able to trace an entry back to an unaltered source.
5. When in doubt about a specific figure, use the actual amount from your statement, even if it's slightly different from what you remember charging — a statement-backed number is real evidence; a remembered or "cleaned up" one isn't.

Frequently Asked Questions

Can I edit or "clean up" a receipt before saving it for taxes?

You can crop, deskew, or adjust contrast/brightness — Rev. Proc. 97-22 only requires the storage system be legible and accurately, completely reproduce the original. You cannot change any number, date, vendor, or line item, or use an AI tool to "reconstruct" an illegible figure and present the result as the original — that crosses from digitizing into fabricating.

What happens if the IRS discovers an altered or fabricated receipt?

It's treated very differently from an honest mistake. Beyond the additional tax, a fabricated document risks the 75% civil fraud penalty under §6663 (versus 20% for ordinary negligence), potential criminal referral under §7206 (up to 3 years/$100,000) or §7201 (up to 5 years/$100,000), and it opens the entire return, not just that item, to audit with no time limit under §6501(c)(1).

Is using an AI receipt scanner different from altering a receipt?

Yes, if it's reading, not rewriting. A compliant tool extracts vendor, date, and amount into a searchable index while preserving the original image untouched, which is exactly what Rev. Proc. 97-22 requires. It becomes a problem only if the tool, or you, overwrites or "corrects" the stored image itself based on a guess.

Does the Cohan rule let me estimate an amount instead of altering a receipt?

Only a court applies Cohan, and only for expenses outside the strict-substantiation categories of §274(d) — travel, meals, gifts, and vehicle/listed property get no Cohan estimate at all. You can't self-apply it by filling in a number on a document and presenting that as the record; that's fabrication, not estimation.

How long can the IRS audit a return with a fabricated receipt?

Indefinitely. The normal window is 3 years from filing (6 years for a substantial income omission), but §6501(c)(1) removes any time limit for a false or fraudulent return filed with intent to evade tax — a single altered document can keep the whole return open forever, not just the item in question.

Authoritative References

• IRS — Rev. Proc. 97-22: Retention of books and records / electronic storage systems
• 26 CFR §1.274-5 — Substantiation requirements
• 26 U.S.C. §7206 — Fraud and false statements
• 26 U.S.C. §7201 — Attempt to evade or defeat tax
• 26 U.S.C. §6663 — Imposition of fraud penalty
• 26 U.S.C. §6501 — Limitations on assessment and collection

Related reading: Faded thermal receipts and the IRS · The Cohan rule for lost receipts · Reconstructing a mileage log after the fact · What to do when the IRS requests documents in an audit

Keep Every Original Receipt Exactly as It Was Scanned

The safest way to stay on the right side of this line is to never need to "fix" a receipt in the first place. CentSense's AI scanner reads and categorizes each receipt automatically while preserving the original image untouched, with a full audit trail back to the source — so your records satisfy Rev. Proc. 97-22 without you having to think about the distinction. Free tier includes 10 AI scans per month; Solo is $5/month for unlimited scanning and mileage logging.

Start free →

This guide is general education for U.S. freelancers and small-business owners covering the 2026 tax year. It is not personalized tax advice or legal advice. If you believe a past filing contains an inaccuracy, consult a CPA, EA, or tax attorney before taking any action — including before amending a return.