Blogs / Tax Audit

Tax Audit

Cash Payments in Tax Audit: Identifying Transactions That Need Further Review

A cash-payment review should test payment modes, daily aggregation and exceptions. Learn how to identify relevant transactions without treating every cash entry as a tax disallowance.

By Team assureOffice
Published 2026-10-11
AI SummaryQuick overview

AI Summary

A cash-payment review should test payment modes, daily aggregation and exceptions. Learn how to identify relevant transactions without treating every cash entry as a tax disallowance. • Aggregate relevant payments by person and day. • Check statutory exceptions using actual evidence. • Separate expense payments, loans and large receipts.

Scope: FY 2025-26 / AY 2026-27 under the Income-tax Act, 1961 and applicable Income-tax Rules, 1962; do not reuse section/form references unchanged for Tax Year 2026-27. Verification date: 11 October 2026.

Do more than filter amounts above ₹10,000

Checking individual vouchers above a limit can miss several smaller payments to the same person on the same day. It can also produce false positives by treating withdrawals, transfers and amounts already reviewed elsewhere as ordinary expenditure.

For the relevant old-Act framework, Section 40A(3) generally tests expenditure payments aggregating more than ₹10,000 to a person in a day through non-permitted modes. The goods-carriage payment ceiling is ₹35,000. Prescribed exceptions and payment modes must be assessed; the ledger's word “cash” is only a starting point.

Build the transaction population

Extract cash-book payments, relevant bank entries, expense settlements and creditor payments. Keep voucher date, payee identity, amount, payment mode, expense reference and source document. Include earlier-year liabilities paid during the current year for the separate Section 40A(3A) review.

Normalise the payee using a code, PAN or verified identity. “ABC Stores”, “A.B.C. Stores” and an employee paying ABC on behalf of the business may need investigation. Name cleaning helps find transactions, but do not merge different people solely because their names look similar.

A daily-aggregation example

A fictional company makes two cash expenditure payments to the same supplier on one day: ₹7,000 in the morning and ₹6,000 later. The daily total is ₹13,000. A voucher-by-voucher test would miss the issue because neither payment individually exceeds ₹10,000.

The preparer should flag ₹13,000 for the statutory review. Assuming no applicable exception and all other conditions are met, the relevant expenditure is examined for disallowance; the exercise is not simply to disallow the ₹3,000 excess. Keep the underlying invoices and evidence.

Screening resultNext step
Multiple payments to one payee/dayAggregate and examine the complete facts
Payment relating to goods carriageVerify nature and the specific ceiling
Claimed exceptionRecord the relevant Rule 6DD basis and supporting documents
Earlier-year expense liability paid nowReview Section 40A(3A) separately

Evidence matters for exceptions

Do not accept a statement such as “supplier insisted on cash” as sufficient by itself. Identify the relevant prescribed exception and obtain the facts needed to support it. Keep the preparer's analysis and review conclusion with the transaction listing.

Similarly, do not classify a bank transaction as permitted merely because it passed through a bank account. Check whether the actual mode meets the statutory requirement. The source document may reveal a bearer or other instrument requiring further assessment.

Keep other cash provisions separate

Loans/deposits and certain property-related advances require their own receipt/repayment review. Large receipts have a different set of tests. An expenditure-payment working cannot replace those analyses. Use a common transaction extract with separate rule-specific conclusions.

Maintain a final register showing flagged amount, provision, explanation, exception evidence, accepted conclusion and reporting/computation treatment. This avoids reporting a raw software exception list as if every row were a confirmed violation.

Final checklist

  • Confirm period, payee identity and payment mode.
  • Aggregate relevant amounts by person and day.
  • Review special ceilings and prescribed exceptions.
  • Trace conclusions to Form 3CD and the tax computation.
  • Prevent the same amount being disallowed twice.

Use approved financials from assureOffice as part of the reporting pack, while retaining this transaction-level tax working. A balanced P&L does not demonstrate that payment-mode conditions have been satisfied.

Document the full review outcome

Use an exception sheet with payee, date, daily aggregate, expenditure reference, payment mode, potentially relevant rule and evidence status. Distinguish an item flagged by the extraction from a concluded disallowance. A missing document should remain an unresolved exception until the position is assessed.

Reconcile the screened population to the source ledger so cash entries have not been lost through filters or narration searches. Test a few transactions below the individual threshold where several payments occur on the same day. This addresses the common weakness of reviewing only the largest vouchers and overlooking smaller payments that aggregate to a relevant amount.

Related articles

Sources and references