AP ageing + §16 interest + Schedule III disclosure — MSME payment compliance automation in under 30 seconds per batch.
| Supplier Name | Udyam Reg. No. | Class | Invoice No. | Days O/S | Amt O/S (₹) |
|---|---|---|---|---|---|
| Acme Corp Fabrications | UDYAM-MH-19-0045821 | Small | ACF/25-26/0142 | 28 | 2,85,000 |
| Acme Corp Components | UDYAM-GJ-04-0098712 | Micro | KPC/25-26/0871 | 42 | 1,42,500 |
| Acme Corp Industrial | UDYAM-TN-33-0021145 | Small | VIS/2025/00514 | 67 | 5,18,000 |
| Acme Corp Precision | UDYAM-KA-29-0067234 | Medium | APP/2025/0289 | 130 | 8,75,000 |
| Acme Corp Sheet Metal | — blank — | Small | PSM/25-26/0033 | 50 | 96,000 |
Controllers at mid-market Indian companies typically manage AP registers with 50–300 open MSME payment compliance invoices across multiple supplier classifications at any given time — with no automated engine to flag what is approaching, what has breached, and what has accrued statutory interest.
Section 15 of the MSMED Act starts the 45-day clock from the date of acceptance of goods or services, not the invoice date. When AP clerks compute days outstanding from the invoice date they routinely undercount overdue days by 5–12 days — enough to miss a breach entirely and omit an invoice from the disclosure note.
MSME classification is self-declared by suppliers. The only verifiable identifier is a Udyam Registration Number in the canonical format UDYAM-XX-NN-NNNNNNN. When that field is missing or malformed, the controller has no basis to confirm statutory obligations apply — yet the invoice still ages silently in the AP register, accumulating potential §16 interest liability with no alert.
Section 16 compound interest at three times the RBI bank rate — currently translating to approximately 18–21% per annum — begins the day after the §15 deadline without any notice from the supplier. A payment outstanding for 130 days generates roughly ₹45,000–55,000 in unbudgeted interest liability on an ₹8,75,000 invoice. Manual AP registers have no formula layer to surface this number at month-end close.
Schedule III to the Companies Act, 2013 requires a financial-statement note disclosing MSME principal overdue, §16 interest accrued, interest paid, and interest payable year-to-date. Assembling this note manually from a raw AP export means filtering by MSME flag, recalculating interest, and formatting four separate line items under the statutory table — a two to three working-day exercise every quarter that is prone to omission and inconsistency across reporting periods.
The time a controller at a mid-market company with 60–80 active MSME vendors spends at month-end manually computing days outstanding, calculating §16 interest, filtering the disclosure register, and reconciling the final note against the AP ledger. Under Section 43B(h) of the Income Tax Act, 1961 (effective AY 2024-25), every invoice on that register that breaches the §15 window is also a payment that converts an otherwise deductible expense into a disallowed deduction until actual payment is made.
Four overlapping statutory provisions create the compliance obligation this workflow enforces. Missing any one of them exposes the buyer to interest liability, tax disallowance, a qualified audit opinion, and a bi-annual ROC filing failure.
A buyer must pay an MSME supplier within the agreed credit period, subject to a hard ceiling of 45 days from the date of acceptance of goods or services. Where no written agreement exists, the ceiling shrinks to 15 days. The acceptance date — not the invoice date — is the statutory starting point for the clock, a distinction most manual AP processes get wrong.
Any amount unpaid beyond the §15 deadline accrues interest automatically at three times the RBI bank rate, compounded with monthly rests. This obligation arises by operation of law — no debit note or supplier notice is required. At a bank rate of 6.5%, the effective §16 rate is 19.5% per annum, compounded monthly, making a missed payment materially more expensive than most trade finance instruments.
Schedule III (Part II) requires listed and unlisted companies to disclose in their annual financial statements: principal outstanding beyond 45 days, §16 interest accrued but not paid, §16 interest paid during the year, and §16 interest payable at year-end. Each line must be tagged to MSME classification (Micro / Small / Medium). Omitting or misstating this note can result in a qualified opinion from the statutory auditor under SA 700 (Revised).
Inserted by Finance Act 2023 and effective from AY 2024-25, Section 43B(h) disallows the deduction for any amount payable to an MSME supplier unless actual payment is made within the time limit prescribed under Section 15 of the MSMED Act. A payment breach flagged as Breached by this workflow is therefore simultaneously a §16 interest liability and a tax deduction risk — two distinct costs that a manual AP register cannot surface together.
Mid-market companies with revenue between ₹50 crore and ₹500 crore typically have 30–60% of their vendor base classified as MSME by headcount. The MCA notification of January 2019 (amended 2021) additionally requires filing Form MSME-1 with the Registrar of Companies biannually — every April 30 and October 31 — disclosing all MSME dues outstanding more than 45 days. A manual AP exercise cannot reliably produce a clean, auditor-ready answer to all four obligations simultaneously.
Seven deterministic passes from AP open-items register to breach-flagged, interest-computed, disclosure-ready MSME payables output — in under 30 seconds per batch of up to 300 invoice lines.
Accepts the AP open-items register as a standard XLSX file and reads every row: supplier name, Udyam Registration Number, MSME classification (Micro / Small / Medium / Non-MSME), invoice number, invoice date, acceptance date, invoice amount, amount outstanding, and contractual due date. Rows with missing acceptance dates are flagged immediately under the Acceptance Date Required validation before any ageing calculation runs.
Every Udyam number is validated against the canonical format UDYAM-XX-NN-NNNNNNN (two-letter state code, two-digit district code, seven-digit serial). Rows where the field is blank, malformed, or inconsistent with the declared MSME class are quarantined in the exception queue with status Cannot Validate MSME Status — §16 interest is not computed for unvalidated rows, preventing both under- and over-reporting of MSME liability.
Days outstanding are computed from the acceptance date, not the invoice date, as required by Section 15. Where a contractual due date is present, the workflow uses it subject to the 45-day ceiling; where the contractual due date field is empty the 15-day fallback applies automatically. The result is a per-row integer representing the number of calendar days elapsed from acceptance to the batch run date.
Each validated MSME invoice receives a deterministic status badge: Within Limit (days outstanding ≤ 38), Approaching (days 39–45, with a due-date proximity alert showing days remaining), or Breached (days outstanding > 45). The inbox view is sorted by status and then by days outstanding, surfacing approaching invoices before they cross the §15 threshold.
For every breached invoice the workflow applies the statutory compound-interest formula: Interest = Principal × ((1 + r/12)^n − 1), where r is 3× the RBI bank rate (configurable parameter) and n is the number of complete months overdue beyond the §15 deadline. The accrued interest is written alongside the principal to the running disclosure ledger. The bank rate parameter can be updated without changing formula logic.
Invoices where outstanding principal exceeds ₹5,00,000 and the overdue period exceeds 90 days are automatically promoted to the MSME disclosure schedule. Each promoted line carries the four fields required by Schedule III: principal overdue, §16 interest accrued, §16 interest paid year-to-date (from the payment ledger input), and §16 interest payable at the batch date. Non-MSME rows and rows below either threshold are excluded from the disclosure schedule.
A formatted Excel disclosure note — with supplier name, Udyam number, MSME classification, invoice reference, and the four Schedule III columns — is generated and ready for attachment to the statutory financial statements. The same output feeds the biannual Form MSME-1 filing with the Registrar of Companies, eliminating the separate reconciliation exercise currently required to populate the MCA form from a manual AP extract.
A battery of five synthetic AP registers that exercise every failure mode we have observed in real mid-market MSME payables data. Each scenario produces a deterministic outcome an auditor or controller can verify in seconds.
Five seeded AP open-items registers — each engineered to exercise a different MSME compliance failure mode. All nine column fields extract with 100% accuracy; the six validation checks produce deterministic results an auditor can trace to source data without re-running calculations.
All six validations pass. Udyam format confirmed, acceptance date present, days outstanding below threshold. Within Limit badge assigned; no entry in exception queue; no disclosure schedule entry required.
All validations pass but the Approaching badge surfaces with a 3-day countdown. The invoice will enter breach status and begin accruing §16 interest if not paid by the next business day — exactly the early-warning signal that manual AP spreadsheets cannot generate.
§16 interest computed at 3× RBI bank rate, compounded monthly on 22 overdue days. Invoice added to exception queue. Principal and ₹7,254 interest written to draft disclosure note. This single line represents the most common breach pattern in mid-market AP registers.
Both disclosure thresholds triggered: principal above ₹5,00,000 and overdue days above 90. Line promoted to MSME Schedule III disclosure schedule with all four statutory columns populated. This invoice also carries a §43B(h) Income Tax Act deduction risk for the current assessment year.
The only FAIL-severity check in the demo set. Without a valid Udyam number, the workflow cannot confirm MSME status. Computing §16 interest on an unverified self-declaration would expose the company to either over-reporting (if the supplier is not actually MSME) or under-reporting (if they are) — both of which create a Schedule III disclosure deficiency.
Replacing a manual MSME ageing exercise with this workflow reduces a process that occupies two to three working days of controller time per month-end close to under 30 seconds of compute time per batch upload — and eliminates four categories of error that recur reliably in mid-market AP teams.
Every invoice flagged Breached is by definition a payment that may not be deductible in the current year under Section 43B(h) until settled. The workflow surfaces this dual exposure — §16 interest liability and income tax deduction risk — on the same row, giving the controller the complete cost picture to prioritize payment release. A manual AP register cannot link these two obligations without a separate tax team query.
The Excel disclosure note is structured to match the four Schedule III columns in the sequence statutory auditors expect to agree to the financial statements — and the biannual Form MSME-1 data fields. The exception queue, with its status badges and Udyam-validation flags, is the supporting schedule behind the note: giving the auditor, the board, and any MSME Facilitation Council inquiry a traceable, date-stamped record of every invoice monitored and the basis on which interest was or was not computed.
The Approaching badge (days 39–45) surfaces invoices three to six days before the §15 ceiling expires — while there is still time to authorize and process payment before §16 interest begins accruing. Manual AP registers sorted by invoice date cannot generate this signal reliably; they would need to compute a separate days-from-acceptance column for every row, with the 15-day fallback applied case by case.
The questions finance controllers and statutory auditors ask most often before deploying MSME payment tracking automation.
The workflow enforces two provisions directly. Section 15 mandates that a buyer must pay an MSME supplier within the agreed credit period, subject to a hard ceiling of 45 days from the date of acceptance of goods or services (or 15 days where no written agreement exists). Section 16 prescribes that any amount unpaid after the §15 deadline attracts interest at three times the bank rate notified by the Reserve Bank of India, compounded monthly. The workflow computes days-outstanding from the acceptance date, flags breaches at day 45, and applies the compounded §16 interest formula automatically.
Interest accrues from the day after the §15 payment deadline at 3× the RBI bank rate in force at the time of default, compounded with monthly rests as required by the Act. The workflow applies the formula: Interest = Principal × ((1 + r/12)^n − 1), where r is 3× the current RBI bank rate and n is the number of complete months overdue. The bank rate input is a configurable parameter so controllers can update it when the RBI revises the rate without changing any formula logic.
Under the MCA notification requiring companies to disclose MSME outstanding amounts in their financial statements (aligned with Schedule III to the Companies Act, 2013), the workflow exports a structured Excel disclosure note containing: principal outstanding beyond 45 days, §16 interest accrued but not paid, and §16 interest actually paid during the year. Each line item is tagged by supplier name, Udyam number, MSME classification (Micro / Small / Medium), and invoice reference. This output can be copied directly into the notes to accounts.
The Udyam Number Format validation raises a FAIL flag and the invoice is moved to a separate exception queue with status Cannot Validate MSME Status. §16 interest is not computed for that line until a valid Udyam number conforming to the pattern UDYAM-[State Code]-[District Code]-[7-digit serial] is supplied, preventing inadvertent under-reporting or over-reporting of MSME liability. The controller receives a prompt to collect the Udyam Registration Certificate from the supplier before the next batch run.
The workflow accepts the AP open-items register as a standard XLSX file, which can be exported from Tally Prime (via the Outstanding Payables report), SAP B1, Oracle NetSuite, or any ERP that produces a columnar payables ledger. There is no direct API connector required; the upload is file-based. The output Excel disclosure note and exception export are formatted for re-import or manual posting into the same systems, and the four Schedule III columns align with the field names used in most mid-market ERP note templates.
Every run produces an immutable audit log recording the input file hash, the run timestamp, the RBI bank rate applied, and the computed days-outstanding and interest amount for each invoice line. Breach flags include the acceptance date, the computed due date, and the exact day count used, so an internal auditor or statutory auditor can trace each determination back to source data without re-running calculations manually. This log is designed to satisfy the documentation requirements under ICAI SA 230 (Audit Documentation) and is exportable as a PDF or CSV from the workflow history panel.
Yes. Section 43B(h), inserted by Finance Act 2023 and effective from AY 2024-25, disallows the deduction for amounts payable to MSME suppliers unless payment is made within the time limit under Section 15 of the MSMED Act. This means a payment breach flagged by this workflow is not merely a compliance issue — it converts the expense into a disallowed deduction for the year, recoverable only when actual payment is made. Every Breached invoice in the output is therefore flagged as carrying both a §16 interest liability and a §43B(h) income-tax deduction risk, giving the controller the full cost picture in a single row.
Form MSME-1, required to be filed biannually with the Registrar of Companies under the MCA notification of January 2019, must disclose all MSME dues outstanding for more than 45 days as of April 30 and October 31 each year. The workflow's Excel disclosure note is structured to match the Form MSME-1 data fields — supplier name, Udyam number, amount outstanding, and reasons for delay — so the controller can populate the MCA filing directly from the workflow output without a separate reconciliation exercise. Running the workflow on or just before each filing date produces a ready-to-submit dataset.
