Schedule III Trade Receivables Ageing: Due Date, Unbilled Dues and Reconciliation Guide

Schedule III trade receivables ageing is not a simple “invoice-date ageing” report copied from the ERP. The disclosure is built around the due date of payment, and the format also requires separate handling where no due date is specified and for unbilled dues. That makes the note a reconciliation exercise between contracts, customer ledgers, dispute records and the financial statements rather than a mechanical export from the receivables module.

The current Companies Act text on India Code includes the Schedule III ageing requirements and can be checked in the official Companies Act, 2013 compilation. The ageing disclosure was inserted through the 24 March 2021 Schedule III amendment with effect from 1 April 2021.

What ageing buckets does Schedule III use for trade receivables?

For trade receivables outstanding, the Schedule III format uses these time buckets measured from the due date of payment:

• less than 6 months;
• 6 months to 1 year;
• 1 to 2 years;
• 2 to 3 years; and
• more than 3 years.

The total across those buckets forms the ageing matrix. The exact row labels depend on the Schedule III division applicable to the company. In formats for companies following Accounting Standards, the matrix distinguishes disputed and undisputed balances and considered-good or doubtful balances. Ind AS-oriented formats include categories such as significant increase in credit risk and credit-impaired receivables. Finance teams should therefore first identify the reporting division that applies instead of copying a template from another company.

The most important rule: age from the due date, not automatically from the invoice date

Schedule III states that the ageing period runs from the due date of payment. This is different from many internal ageing reports, which calculate days from invoice date by default.

Consider an invoice of Rs. 10 lakh dated 1 May 2025. The contract allows six months of credit, so payment is due on 1 November 2025. At 31 March 2026, the receivable has been outstanding for about five months from its due date and therefore belongs in the less-than-6-month bucket. If the team aged it from invoice date, it would appear to be about eleven months old and could be placed in the 6-month-to-1-year bucket. The same receivable would therefore land in a different disclosure bucket merely because the ageing base was wrong.

A robust year-end process should therefore carry the contractual due date at invoice level wherever possible. Where payment terms differ by customer, project, milestone or invoice, a generic “30 days” assumption can create material classification errors.

What if no due date of payment is specified?

Schedule III expressly addresses this situation. Where no due date is specified, similar ageing information is to be given from the date of the transaction. The finance team should not invent a contractual due date just to make the ageing report work.

For older customer balances, this rule makes documentation particularly important. If the underlying contract or purchase order does contain a payment term but the ERP due-date field is blank, the correct control is to repair the master or invoice data using the actual term. The transaction-date fallback is for cases where no due date is specified, not for cases where the accounting system simply failed to capture an existing due date.

Unbilled dues must be shown separately

The Schedule III text states that unbilled dues shall be disclosed separately. This means a company should not force unbilled revenue or contract-based receivable amounts into a normal invoice-ageing bucket merely by assigning an artificial due date.

Practically, the close file should identify which amounts are invoiced trade receivables and which amounts are unbilled dues under the applicable accounting framework. The unbilled balance should then reconcile separately to the note and the underlying revenue recognition working.

Disputed and undisputed balances need a documented classification

The ageing format does more than split balances by time. It also separates disputed from undisputed receivables. A “disputed” tag should therefore be supported by evidence such as customer correspondence, debit notes, legal notices, quality claims, rate disagreements or other documented challenges to the amount.

A common control failure is to mark an entire customer account as disputed because one invoice is under challenge. Where the records support it, the ageing working should distinguish the disputed portion from the undisputed portion so that the disclosure reflects the actual status of the balances rather than the customer name alone.

Good, doubtful and credit-risk categories are not interchangeable

The category structure changes with the applicable Schedule III division. Companies should align the ageing matrix with the same impairment or doubtful-debt assessment used elsewhere in the financial statements. A balance should not be labelled “good” in the ageing note while the impairment working treats the same amount as seriously credit impaired without a documented explanation.

For companies applying an expected-credit-loss framework, the ageing schedule and the impairment model are related but they are not the same calculation. Age is an important risk input, but credit risk can also be affected by customer-specific information, defaults, restructuring, litigation, sector stress and other forward-looking factors. The disclosure working should therefore reconcile to, rather than replace, the impairment assessment.

How to build a reliable Schedule III receivables ageing working

1. Freeze the receivables population. Reconcile the customer ledger to the general ledger and the trade receivables note before ageing.
2. Separate unbilled dues. Keep them outside the normal invoice-ageing grid and reconcile them independently.
3. Capture the real due date. Use contract, purchase order or invoice terms rather than default ERP assumptions.
4. Apply the transaction-date fallback only where no due date is specified.
5. Calculate bucket age as at the reporting date. Map each invoice or balance to the prescribed less-than-6-month, 6-month-to-1-year, 1-to-2-year, 2-to-3-year or more-than-3-year bucket.
6. Classify dispute status. Tie disputed amounts to documentary evidence and review partial disputes separately.
7. Map credit-quality categories. Use the row structure required by the applicable Schedule III division and reconcile it to the doubtful-debt or impairment working.
8. Reconcile totals. The ageing matrix, separately disclosed unbilled dues and applicable allowance or impairment presentation should tie back to the trade receivables disclosure without unexplained differences.
9. Review comparatives consistently. Apply the same methodology to the comparative period so that movement between ageing buckets is understandable.

Common mistakes to avoid

• Ageing every invoice from invoice date even when a contractual due date exists.
• Using a default credit period because the ERP due-date field is incomplete.
• Putting unbilled dues into an invoice-ageing bucket.
• Treating all balances of one customer as disputed because only one item is under dispute.
• Using a Division I-style row structure for an Ind AS reporter, or vice versa.
• Netting or reclassifying impairment amounts without reconciling the ageing note to the applicable financial statement presentation.
• Preparing the disclosure only at year-end without retaining invoice-level support for due dates, disputes and bucket movements.

Practical takeaway

The strongest Schedule III receivables ageing file starts with the contract, not the spreadsheet. Determine the real due date, use transaction date only when no due date exists, keep unbilled dues separate, document disputed balances, apply the correct row structure for the company’s reporting framework and reconcile the final matrix to the financial statements. That approach turns the ageing note from a formatting exercise into a reliable financial-reporting control.