Receipt scanning for taxes: what the IRS actually requires

The IRS accepts scanned and photographed receipts. Digital images count as records under Internal Revenue Code § 6001 when your storage system meets Revenue Procedure 97-22, and you may destroy the paper originals once two conditions are met. The IRS is explicit that "all requirements that apply to hard copy books and records also apply to electronic records."

So receipt scanning for taxes is not a legal grey area. The real question is narrower: does your pile of phone photos meet the standard, or just look like it does? This walks through the actual requirements, what each receipt has to show, how long to keep it, and the specific gap where consumer scanning apps stop short.

This covers US federal rules and is general information, not tax advice — check with your accountant about your own situation. If you file outside the US, the principle that legible digital copies are acceptable is common, but the retention periods and specifics differ; check your own tax authority.

What the IRS requires of a scanned receipt

Rev. Proc. 97-22 section 4.01(2) lists what an electronic storage system must include. Stripped to what it means for receipts:

• An accurate and complete transfer from the paper to the stored image — nothing cropped off, nothing missing.
• Legibility and readability. The procedure defines these precisely: legibility means "the observer must be able to identify all letters and numerals positively and quickly," and readability means being able to "recognize a group of letters or numerals as words or complete numbers." A blurry photo where the total could be an 8 or a 3 fails this.
• An indexing system that lets you find a given receipt. Section 4.02 sets a forgiving bar: it's satisfied if the index is "functionally comparable to a reasonable hardcopy filing system."
• The ability to reproduce legible hardcopies on request — you must be able to print them.
• Reasonable controls for integrity and against unauthorized alteration or deletion.
• An inspection and quality assurance program with regular evaluations and periodic checks of the stored records.

Two things surprise people here. Nothing specifies a DPI, a file format, or a scanner — the standard is outcome-based, so a phone camera is fine if the result is legible. And section 3.03 states that using a third party for storage "does not relieve the taxpayer of the responsibilities" — your app vendor cannot be compliant on your behalf.

What each receipt has to show

A legible image of the wrong thing still fails. IRS guidance on what records to keep says supporting documents for expenses should show the payee, the amount paid, proof of payment, the date incurred, and a description of what was purchased.

It also notes that "a combination of supporting documents may be needed to substantiate all elements of the expense" — a card statement proves payment, the receipt proves what was bought, and neither alone does both.

For travel, meals, and gifts, Publication 463 adds a stricter test: your records must establish the amount, time, place, and business purpose. Business purpose is the element receipts never contain and people almost never capture — the receipt says $84 at a restaurant, not who you met or why.

The $75 exception, and the trap in it

Publication 463 states: "Documentary evidence, such as a receipt, isn't required if an expense is less than $75. However, a receipt is required for any lodging expense."

Read that carefully, because two mistakes follow from skimming it. The lodging carve-out has no dollar floor — a $40 roadside motel needs its receipt. And the exception drops the receipt, not the record: you still need something establishing amount, time, place, and business purpose for that sub-$75 expense.

This is the one place voice capture genuinely does something paper can't. Saying "lunch with Dana from Acme about the Q4 contract, thirty-one dollars" records the business purpose at the moment you remember it. A photographed receipt filed six weeks later does not.

How long to keep them

Retention runs from the period of limitations for the return the receipt supports, not from the purchase date:

The practical consequence: three years is the floor, not the answer. The six-year and indefinite rows depend on facts you may not know when you decide what to delete, which is why most accountants land on seven years for business records. Property records run longer still — until the limitations period expires for the year you dispose of the property.

Rev. Proc. 97-22 section 4.01(8) ties your digital copies to the same clock: retain them "so long as their contents may become material in the administration of the Internal Revenue laws."

Can you throw away the paper?

Yes. Section 7 permits destroying the original hardcopy records, but only after you have:

1. Completed your own testing of the storage system, establishing that records are being reproduced in compliance with the procedure; and
2. Instituted procedures that ensure continued compliance.

Both are things you do, not things your app does. In practice: scan a batch, print one back, confirm every character is readable, and write down the routine you'll follow and check.

There's also a safety net worth knowing. Section 6.02 says that even where a storage system fails the requirements, the penalties "may not apply if the taxpayer maintains its original books and records." Keeping the shoebox is what protects you while a digital system is untested — so digitize first, verify, and shred last.

Where receipt scanning apps stop short

Every app in this category — ours included — handles capture, extraction, storage, and export. Mapped against section 4.01, that covers the transfer, the legible image, the index, and the reproduction. It does not cover three requirements that are yours:

• The quality assurance program. Section 4.01(2)(c) wants regular evaluations and periodic checks. No app schedules this for you; it's a recurring task you own.
• The system description. Section 4.01(5) requires you to maintain, and produce on request, complete descriptions of the storage system and its indexing, including all procedures relating to its use. That's a short document you write once.
• The audit trail. Section 4.01(4) wants your stored images and your books cross-referenced so there's a trail between the general ledger and the source document. If your receipts live in one tool and your books in another with no shared reference, that trail is missing.

This is the honest answer that app roundups skip: no tool makes you compliant, because a third of the requirements are procedural. The useful question when choosing one is whether it makes your half easier — can you retrieve a single receipt from three years ago in seconds, and print it legibly?

A workflow that holds up

1. Capture the same day, especially thermal paper, which fades. Nothing downstream recovers a total you can no longer read.
2. Record the business purpose while you remember it. This is the element that goes missing, and the one Publication 463 requires for travel and meals.
3. Check the extraction, don't trust it. Spot-check new vendors — a misread total is a wrong deduction, and the image is your only proof of the right one.
4. Keep the image attached to the entry, not in a separate photo roll. Attachment is what makes the ledger row retrievable and reproducible together.
5. Test before you shred. Print a sample back and read every character. That test is literally condition one of section 7.
6. Export an annual archive and store a second copy somewhere else. Section 4.01(9) treats records as destroyed if you stop maintaining the means to read them — a vendor you leave, or an account you close, can put you there.

Troubleshooting the cases that break

Faded thermal receipts. Scan the day you get them. Section 4.03 lists retaining hardcopies of records "that are illegible or that cannot be accurately or completely transferred" among its recommended practices — if the image is marginal, keep the paper.

Long grocery or supply receipts split across categories. A single total hides a mixed purchase. Extract line items so each lands in the right category — see small business expense categories for how to structure those.

Cash spend with no receipt at all. The $75 exception often covers it, but you still need a contemporaneous record of amount, time, place, and purpose. Log it immediately rather than reconstructing it later.

Receipts in another currency or language. Keep the original image alongside the converted amount, and note the rate you used. See multilingual expense tracking.

Next step

Pick one pile — the current quarter — and run it through the workflow above, ending with the print-back test. That single pass tells you whether your setup actually satisfies section 7, or whether you should keep the paper another year.

Tapsayve captures receipts by photo and expenses by voice, keeps the image attached to each entry, and exports a tax bundle — a PDF report zipped together with your receipt images for a date range — which is the retrieve-and-reproduce half of the requirements in one file. The procedural half is still yours.

Related reading: how to organize receipts for the filing side, the best app to scan receipts for a comparison of tools, and how to track business expenses for the process around them.

Sources: IRS Revenue Procedure 97-22 (Internal Revenue Bulletin 1997-13), IRS Publication 463, and IRS small business recordkeeping guidance, all linked above and current as of September 2026. Rev. Proc. 97-22 predates the IRS reorganization that replaced District Directors, so some role names in it are historical; its requirements remain the operative guidance for electronic storage. Tax rules change — verify against the current text before relying on it.