Schedule III Trade Payables Ageing: Due Date, MSME Rows, Unbilled Dues and Reconciliation

Trade-payables ageing under Schedule III looks simple until the accounts team has to decide which date starts the clock, how to separate MSME and disputed balances, what to do with unbilled dues, and why the final table does not reconcile to the balance sheet. The disclosure is not just an ageing report exported from the ERP. It is a financial-statement note built around the specific categories and ageing basis prescribed by Schedule III.

The authoritative text is available in the official India Code compilation of the Companies Act, 2013 and Schedule III. India Code also maintains the Companies Act, 2013 page with Schedule III and related subordinate legislation. The compiled Schedule III records the trade-payables ageing requirement inserted by G.S.R. 207(E) dated 24 March 2021 with effect from 1 April 2021.

Start with the right population: what is a trade payable?

Schedule III describes a trade payable as an amount due for goods purchased or services received in the normal course of business. That definition matters before ageing begins. Borrowings, deposits, statutory liabilities, employee-related balances and other liabilities should not be pushed into the trade-payables table merely because they appear in the same general-ledger liability group.

A good year-end process therefore starts by reconciling the accounts-payable subledger and relevant accrual accounts to the trade-payables balance presented in the financial statements. The team should document any mapping judgment where a general-ledger account contains both trade and non-trade items.

What columns and rows does Schedule III require?

For trade payables due for payment, Schedule III prescribes ageing from the due date of payment across four time bands: less than one year, one to two years, two to three years, and more than three years, together with a total column.

The table is split into four categories:

• MSME
• Others
• Disputed dues - MSME
• Disputed dues - Others

This means a single vendor ageing report that only shows supplier name and days outstanding is not enough. The financial-statement process must also identify whether a balance belongs in the MSME or other category and whether the amount is disputed.

The key rule: age from due date, not automatically from invoice date

The most important data point is the payment due date. Where a due date exists, the ageing period runs from that due date. If no due date of payment is specified, Schedule III says similar information is to be given from the date of the transaction.

This distinction can materially change the bucket. Many ERP reports calculate ageing from invoice date by default. That may be useful operationally, but it does not automatically produce the Schedule III disclosure. The finance team should identify the contractual or otherwise supportable due date and configure the reporting logic accordingly.

Worked example

Assume a supplier invoice for ₹12 lakh is dated 1 November 2025 and the agreed payment due date is 31 January 2026. At a 31 March 2026 reporting date, the Schedule III ageing period is measured from 31 January 2026, so the balance falls in the less-than-one-year bucket. If there were no specified due date, the disclosure would instead be aged from the relevant transaction date.

Now assume a separate disputed MSME payable of ₹3 lakh had a due date of 15 January 2024 and remained outstanding at 31 March 2026. It would be presented in the disputed-dues MSME row and, based on that due date, in the two-to-three-years bucket. The illustration shows why both the date logic and category tagging must be correct before totals are calculated.

Unbilled dues should not be forced into an ageing bucket

Schedule III specifically states that unbilled dues are to be disclosed separately. This is important because an amount for goods or services received may be recognised before a supplier invoice creates the normal billing and due-date trail.

Finance teams should therefore identify unbilled amounts included within the trade-payables population and keep a separate reconciliation for them. Assigning an artificial invoice date merely to make the ERP ageing report balance can distort the required disclosure.

MSME ageing is not the whole MSME disclosure

Schedule III contains separate MSME-related note requirements in addition to the ageing matrix, including specified disclosures around amounts remaining unpaid and interest-related information under the Micro, Small and Medium Enterprises Development Act framework. The ageing table should therefore be reconciled with the entity's separate MSME disclosure work rather than treated as a replacement for it.

Practically, the vendor master should have support for the classification used in the financial statements, and changes or uncertainty in vendor status should be resolved consistently with the entity's accounting policy and the applicable statutory definitions. The objective is not merely to populate an “MSME” column but to make the ageing note and the separate MSME disclosures internally consistent.

A practical year-end workflow

1. Freeze the reporting-date population. Reconcile the accounts-payable subledger, relevant accruals and general ledger to the financial-statement trade-payables balance.
2. Remove non-trade liabilities. Review mapped accounts and reclassify items that do not arise from goods purchased or services received in the normal course of business.
3. Establish the ageing date. Use the payment due date where specified. Where no due date exists, use the transaction date as required by Schedule III.
4. Tag the category. Separate MSME from others and disputed from undisputed balances using documented support.
5. Separate unbilled dues. Identify them independently instead of inventing a due date to place them in a bucket.
6. Run the four ageing bands. Less than one year, one to two years, two to three years and more than three years.
7. Reconcile every total. The ageing output, separately disclosed unbilled dues and any presentation adjustments should bridge clearly to the trade-payables figure in the financial statements.
8. Cross-check MSME notes. Compare the ageing classifications with the separate MSME-related disclosures and investigate inconsistencies before finalisation.

Common mistakes to avoid

• Using invoice date for every balance even when a payment due date is specified.
• Copying the ERP's operational ageing report without testing whether its date logic matches Schedule III.
• Combining disputed and undisputed balances in the same row.
• Forcing unbilled dues into an ageing bucket simply to make totals agree.
• Including borrowings, statutory dues or other non-trade liabilities because they sit in a generic payable account.
• Preparing the ageing matrix independently from the separate MSME disclosure work.
• Leaving an unexplained difference between the note and the financial-statement trade-payables balance.

Practical takeaway

A defensible Schedule III trade-payables ageing note starts with classification and source data, not with formatting a table. Confirm the trade-payable population, age each billed balance from the correct due date, use transaction date only where no due date is specified, separate MSME and disputed categories, keep unbilled dues outside the ageing buckets, and reconcile the result to both the balance sheet and the separate MSME disclosures. That workflow turns the ageing note from a year-end spreadsheet exercise into a controlled financial-reporting process.