Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
During a GST audit, an officer requests the purchase register and GSTR-2B for a 12-month period and asks the finance team to show how ITC was reconciled before each GSTR-3B filing. If the reconciliation happened in a spreadsheet, the finance team will produce a PDF printout with no version history, no indication of who made changes, and no log of exceptions that were overridden.
That is not an audit trail. That is a snapshot.
What a Complete Audit Trail Contains
A complete reconciliation audit trail has five mandatory components:
1. Match log: Every transaction matched during the reconciliation run — source record, target record, matching criterion used, match confidence, and timestamp of the match.
2. Exception log: Every item that did not match automatically — exception type (classification), the data that was available, the classification rationale, and who reviewed and resolved it.
3. Override log: Every instance where a human overrode an automatic match or exception classification — the original classification, the override, the reason stated, and the approving user.
4. Source data log: Every input file ingested — filename, source, date of download, row count, hash verification. This proves the reconciliation was run against the correct data.
5. Sign-off log: Every approval event — who signed off on the month-end close, with timestamp, and what exceptions were outstanding at sign-off with their materiality classification.
CBDT and GST Authority Requirements
| Regulatory authority | Primary interest | Documentation required | Retention period |
|---|---|---|---|
| CBDT (Income Tax) | TDS receivable vs Form 26AS | Assessment year-wise TDS reconciliation + mismatch log | 8 years from end of assessment year |
| GST authority | ITC claimed vs GSTR-2B | Month-wise GSTR-2B vs purchase register reconciliation | 6 years from GSTR-9 filing date |
| Statutory auditor (Companies Act) | All reconciliation types | Bank BRS, TDS schedule, ITC schedule, AR/AP confirmation | 8 years from financial year end |
| RBI (if NBFC or payment aggregator) | Bank and nodal account | Daily bank reconciliation statements | As per specific RBI direction |
Maintaining Queryable Match History
A queryable audit trail is one where a specific transaction can be traced in seconds — not hours. Given a UTR number, the auditor should be able to retrieve: the original bank credit, the invoice or settlement it was matched against, the matching criterion applied, the confidence score, and the team member who reviewed any exceptions.
How Long to Retain Reconciliation Records
The practical answer for Indian organisations is 8 years — the maximum retention requirement across all applicable laws. Organising retention by financial year makes retrieval straightforward: a single folder or archive per FY, containing all reconciliation run logs, input files, and sign-off records for that year.
Digital vs Paper Audit Trails
A paper audit trail fails for three reasons:
- No version history: A printed spreadsheet shows the final state, not the changes made during the reconciliation process
- Not queryable: Finding a specific transaction in a printed report requires manual page-by-page review
- Tamper risk: Paper records can be altered without detection; digital records with hash verification cannot
Passing a Reconciliation Audit
The most common failure in a reconciliation audit is not that the reconciliation was wrong — it is that the organisation cannot demonstrate the reconciliation was done correctly. The absence of an audit trail is treated by regulators as absence of the reconciliation itself.
Reconciliation software India that generates system-level audit trails — immutable, timestamped, user-attributed — meets the regulatory expectations of CBDT, GST authorities, and statutory auditors without requiring additional documentation overhead.
TDS reconciliation software that maintains a queryable log of every Form 26AS match and every exception raised reduces audit response time from days to hours — the difference between a routine inquiry and an extended scrutiny.
The Income Tax India portal publishes Section 44AB audit requirements and the CBDT guidance on record retention that governs what documentation the tax auditor will request.