What to Do in an Audit Without Receipts

When receipts are missing, start by identifying what each deduction legally requires and what reliable records still exist. Reconstruct transactions from bank and card statements, canceled checks, vendor duplicates, invoices, emails, calendars, contracts, mileage records, property documents, and accounting history. Explain how the reconstruction was made and preserve both the source and calculation. The IRS may consider credible evidence, but a bank charge alone may prove payment without proving what was purchased or why it was business-related. Some categories, including travel, gifts, and listed-property expenses, have strict substantiation rules that a general estimate may not satisfy.

This guide is part of Steady’s Business Taxes & the IRS library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

The burden is issue-specific

A deduction can require proof of amount, date, payee, business relationship, business purpose, and allocation between business and personal use.

Payment is only one element

A bank or card statement shows money moved but may not establish the item, recipient, or business purpose.

Third-party duplicates are valuable

Vendors, landlords, utilities, processors, and financial institutions may reproduce invoices, statements, or canceled checks.

Contemporaneous records are stronger

Calendars, mileage logs, job files, emails, and work orders created near the event can connect the cost to business activity.

Reconstruction should be transparent

Label estimated or reconstructed schedules, explain the method, and do not present a later document as an original receipt.

Strict substantiation can limit estimates

Travel, meals, gifts, vehicles, and other listed property can require specific records beyond a reasonable general estimate.

Personal portions must be removed

Mixed telephone, vehicle, home, subscription, and card activity needs a supported allocation.

Records must also support income

An audit reconstruction should reconcile deposits and gross receipts, not focus only on deductions.

Step-by-step workflow

1. Read the exact request. List each return line, period, amount, evidentiary element, response date, and delivery method.
2. Freeze existing data. Save bank feeds, ledger detail, emails, calendars, cloud files, texts, project systems, and device exports before retention periods expire.
3. Request duplicates. Contact vendors, banks, processors, landlords, insurers, utilities, and payroll providers for replacement records.
4. Build a transaction schedule. For each item, record date, vendor, amount, account, category, business purpose, job or client, source, and confidence.
5. Link payment and purpose. Pair the financial record with invoices, correspondence, contracts, event agendas, mileage logs, or work product.
6. Apply category rules. Review the specific federal instructions and strict substantiation requirements before using an estimate.
7. Remove unsupported amounts. Separate personal activity, duplicates, capital items, wrong-year costs, and expenses that lack a credible business connection.
8. Reconcile totals. Tie the reconstructed schedule to the ledger, return, bank activity, and any audit adjustment.
9. Submit with an explanation. Describe missing records, recovery steps, calculation method, limitations, and indexed exhibits without overstating certainty.
10. Repair the system. Use receipt capture, separate accounts, monthly close, backups, and a retention calendar for future years.

Worked example

A contractor lacks several fuel and supply receipts after a phone failure. The bank statements identify vendors and amounts, job calendars show work locations, vendor portals reproduce most invoices, and a mileage app export supports trip dates. The contractor creates an indexed schedule linking each expense to these sources, removes personal purchases, and clearly labels the small reconstructed portion. The contractor does not fabricate receipts or treat every fuel charge as deductible mileage.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Inventing replacement receipts. Fabrication creates credibility and potential penalty problems.
• Sending only bank statements. Add evidence of item and business purpose.
• Estimating strict-substantiation expenses casually. Review the category’s exact record requirements.
• Deducting every mixed-account charge. Allocate or remove personal use.
• Ignoring gross receipts. Reconcile income and deposits too.
• Rebuilding from memory alone. Seek contemporaneous and third-party evidence.
• Overwriting the original books. Preserve the filed-return ledger and show reconstruction adjustments separately.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Practical implementation notes

Evidence matrix

Show each evidentiary element and the source that supports it.

Recovery log

Record vendor requests, dates, responses, and unavailable items.

Reconstruction memo

Explain method, assumptions, exclusions, and reviewer.

Future control

Adopt separate accounts, receipt capture, monthly reconciliation, and tested backups.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.