This is a composite, illustrative scenario, not an account of a named client. A GST liability of roughly ₹6 lakh had remained unpaid and crossed the six-month-overdue mark four days before the financial year end — a threshold directly relevant to CARO clause 3(vii), which requires reporting statutory dues outstanding for more than six months from the date they became payable. The liability was paid two days after the balance sheet date, and management's initial position was that since it had since been cleared, it did not need to be reported as outstanding — a position that confuses when the balance sheet date position is assessed with what happened afterward.
Why the subsequent payment did not change the reporting position
CARO clause 3(vii)(b) asks what statutory dues were outstanding for more than six months as at the balance sheet date, not as at the date the audit report is signed. A liability that had already crossed the six-month line by the balance sheet date is reportable on that basis regardless of what happened in the days or weeks after year end — paying it off before the report is signed does not retroactively change its age as at the balance sheet date, any more than paying off an overdue loan the week after year end would change whether it was overdue at year end.
What the ageing test actually calculated
- 01Computed the exact due date and the exact number of days overdue as at the balance sheet date, not the payment dateThe liability's original due date made it 184 days overdue as at the balance sheet date — four days past the six-month line, by this computation.
- 02Checked whether 'six months' was being computed on a calendar-month or day-count basis, since the gap was this close to the lineUsing a straightforward calendar computation, the due date clearly fell more than six months before the balance sheet date, leaving no reasonable room to classify it as just under the threshold.
- 03Confirmed the actual payment date from the bank statementPaid two days after the balance sheet date — consistent with management's account, and irrelevant to the clause 3(vii) assessment itself, but still worth confirming the full facts for the file.
- 04Discussed the reporting position directly with managementOnce the distinction between balance sheet date position and subsequent settlement was explained, management agreed the amount needed to be reported under clause 3(vii).
| Date / status | |
|---|---|
| Original due date | roughly 184 days before the balance sheet date |
| Balance sheet date | liability still outstanding, 184 days overdue |
| Actual payment date | 2 days after the balance sheet date |
| CARO clause 3(vii) reporting position | Reportable — overdue status is assessed as at the balance sheet date |
What went into the file
- The precise day-count computation showing the liability had crossed six months overdue before the balance sheet date, with the calculation shown rather than just the conclusion.
- The bank statement confirming the actual settlement date, documented separately from the reporting conclusion.
- The discussion with management and the final agreed CARO disclosure.
- A note on why a liability this close to the six-month line deserves an explicit day-count calculation rather than a rounded estimate, given how easily a few days either way changes the reporting outcome.
Regulatory requirement
CARO 2020 clause 3(vii)(b) requires disclosure of statutory dues outstanding for more than six months from the date they became payable, assessed as at the balance sheet date. Settlement after the balance sheet date, even shortly after, does not change the reporting position for that date — it only affects what the subsequent-events note, if any, says about it.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- CARO & Companies ActCARO statutory dues clause: testing approachHow to test timely deposit of statutory dues for CARO reporting, handle disputed dues disclosure, and avoid redoing work already done in the GST and payroll sections.
- CARO & Companies ActWhy statutory dues cross the six-month-overdue line without anyone noticing in real timeThe six-month line gets checked once a year, at close. It gets crossed, if it's going to be crossed, on an ordinary Tuesday in between.
- CARO & Companies ActCARO clause 3(ix)(a)-(f): the six-part default and diversion testA walkthrough of each of the six sub-parts of CARO clause 3(ix), from default in repayment to fund diversion to subsidiaries, with what the auditor tests for each.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.