Tax Audit Trigger: When Business or Professional Income Needs Extra Review

Tax audit is not determined by turnover alone. Activity type, cash ratio, presumptive history and declared profit can change the answer.

What the taxpayer should understand

• The Income-tax Act, 2025 took effect on 1 April 2026. FY 2025–26 and AY 2026–27 remain governed by the Income-tax Act, 1961, including the notified AY 2026–27 ITR forms. Tax year 2026–27 beginning 1 April 2026 is governed by the 2025 Act and the Income-tax Rules, 2026. Legacy section numbers and forms should therefore be used only for the period to which they legally apply.
• For FY 2025–26, the familiar old-Act tax-audit framework remains applicable.
• The ordinary business threshold is ₹1 crore, increased to ₹10 crore where both cash receipts and cash payments do not exceed the specified five-per-cent conditions.
• The professional gross-receipt threshold is ₹50 lakh under the old-Act framework.
• Presumptive lower-profit or opt-out cases can trigger audit under separate conditions even below the headline turnover threshold.
• Turnover calculation for F&O, intraday, agency, reimbursement and multiple businesses needs activity-specific analysis.

Use the Income-tax Rules, 2026 — Rule 1 to 333 Repository to apply these points to your figures or facts.

The five-point review

Practical example

How to apply the framework

Prepare an audit-trigger memo before the audit due date, not after filing the return.

Where several activities exist, reconcile turnover consistently across books, GST, broker reports and AIS.

Filing-control workflow

Fix the tax period and statutory route

Identify the financial year, assessment year or tax year before using any threshold, form or section. Review activity, scale and cash together. A form filed in June 2026 for AY 2026–27 remains an old-Act filing, while an event occurring after 1 April 2026 can fall under the new Act.

Reconcile the commercial evidence

Start from contracts, invoices, bank statements, payroll, broker records, property documents and statutory certificates. Then reconcile AIS, TIS, Form 26AS, ITR schedules, tax payments and prior returns. Portal information can contain gross values, timing differences or reporting errors and should not replace primary evidence.

Test the live filing result

Review validation messages, selected regime, form acknowledgements, loss schedules, tax-credit matching and processed intimation. Preserve the filed JSON or form, computation, supporting schedules, transaction IDs and any correction request. A saved draft or payment debit is not proof that the statutory task is complete.

Implementation checkpoint

Before treating the filing step as complete, verify the live portal or processed outcome. Confirm the form and regime, taxable income, losses, tax credit, payment mapping, deduction schedule and acknowledgement. Record any remaining mismatch, responsible person and correction deadline. This check prevents a technically submitted return from preserving the wrong tax result.

Action checklist

• Classify every activity.
• Compute turnover correctly.
• Test both cash ratios.
• Review presumptive history.
• Confirm audit form and deadline.
• Appoint auditor and preserve working.

Evidence to keep

• Turnover computation
• Cash receipt/payment analysis
• Prior presumptive returns
• Books/GST/broker records
• Audit engagement and report

Warning signs

Finin2min takeaway