IRS Audit Triggers: 10 Risks to Review

An IRS audit is an examination of a return and its support, not proof that a taxpayer did something wrong. The IRS explains that selection can arise from random or statistical sampling, computer scoring against norms, information-return mismatches, or issues found while examining another taxpayer. For a small business, the useful question is not how to hide a red flag. It is whether revenue, deductions, payroll, owners, and filed forms reconcile to reliable records.

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

1. Information-return mismatches

Forms W-2, 1099, K-1, 1098, and payment reports can be compared with a filed return. A missing or duplicated amount deserves a written reconciliation.

2. Gross receipts that do not reconcile

Bank deposits, merchant reports, invoices, cash logs, and the tax return should connect, with transfers, loans, refunds, and owner contributions identified.

3. Large or unusual deductions

A deduction is not wrong merely because it is large, but unusual amounts need invoices, business purpose, payment evidence, and correct capitalization or limitation treatment.

4. Repeated losses

Losses can be legitimate, but the file should establish a real profit-seeking activity and distinguish business expenses from personal consumption.

5. Cash-intensive operations

Strong daily sales records, deposits, void reports, discounts, tips, inventory, and owner-withdrawal controls help explain cash that otherwise leaves little third-party evidence.

6. Worker classification and payroll gaps

Payments to workers should agree with the relationship, payroll returns, W-2s, 1099s, deposits, and state accounts.

7. Owner transactions

Loans, distributions, draws, reimbursements, wages, basis, and personal expenses need separate accounts and consistent return treatment.

8. Vehicle, travel, meals, and home-office claims

These areas mix business and personal use and therefore need contemporaneous logs, business purpose, allocation, and any stricter substantiation required.

9. Entity and shareholder inconsistencies

An S corporation return, shareholder payroll, K-1s, distributions, basis records, and personal returns should tell the same story.

10. Late, incomplete, or changing filings

Late returns, unsupported amendments, missing schedules, and unexplained changes can create questions even when a refund claim or amendment alone is not an automatic trigger.

Step-by-step workflow

1. Reconcile all income sources. Tie books to bank, cards, processors, cash, invoices, and every third-party form.
2. Build a return bridge. Explain each movement from book income to taxable income, including depreciation, meals, owner items, accruals, and elections.
3. Test high-risk accounts. Sample travel, meals, vehicle, contractor, payroll, home-office, and owner transactions for required evidence.
4. Review entity consistency. Compare formation, elections, payroll, returns, K-1s, basis, distributions, and owner reporting.
5. Preserve versions. Keep the filed return, workpapers, source reports, adjustments, approvals, and e-file acceptance.
6. Respond only to the notice. If contacted, confirm authenticity, scope, deadline, requested records, response channel, and representative authorization.
7. Organize evidence by issue. Provide a clean schedule and supporting documents instead of an unstructured data dump.
8. Protect appeal rights. Track deadlines and understand examination, protest, appeals, and court options before agreeing to changes.

Worked example

A consulting S corporation reports $420,000 of receipts. Merchant reports show $65,000 and bank deposits show $500,000. The preparer does not force either total into the return. The reconciliation identifies $355,000 of ACH customer receipts, $65,000 of card receipts, a $50,000 shareholder loan, $20,000 of transfers between accounts, and $10,000 of returned customer funds. The supported business receipts total $420,000, and the owner transactions are documented separately.

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

• Treating a list as a prediction. No checklist can guarantee selection or nonselection.
• Changing valid numbers to look ordinary. Report the supported result, even when it differs from an industry average.
• Using bank deposits as revenue without analysis. Separate transfers, loans, contributions, refunds, and timing differences.
• Sending every record immediately. Answer the authenticated request in an organized, issue-specific way.
• Creating receipts after the fact. Use genuine records and clearly label lawful reconstruction.
• Ignoring deadlines. Late responses can reduce options and increase proposed adjustments.

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

Audit-ready index

List each return line, workpaper, source report, evidence folder, preparer, and reviewer.

Notice log

Track letter number, tax period, issue, deadline, response, delivery, and next action.

Legal hold

Pause routine destruction when an examination, notice, claim, or dispute is pending.

Security

Send only through an authenticated channel and redact unrelated sensitive data when permitted.

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.