What if our signed contract with an MSME vendor explicitly states 90-day payment terms?

Section 15 of the MSMED Act contains a statutory cap: in no case shall the period agreed upon between the supplier and the buyer in writing exceed 45 days from the day of acceptance. Any 60-day or 90-day clause is legally reduced to 45 days.

Is the Section 16 late-payment interest deductible as a business expense for Income Tax?

No. Section 23 of the MSMED Act explicitly overrides the Income Tax Act and prohibits any buyer from claiming interest paid or payable under Section 16 as an allowable deduction while computing taxable income.

When is an invoice purchased in March allowed in the same FY under Section 43B(h)?

If goods are accepted on March 10 under a 45-day written agreement, the statutory due date falls on April 24. Provided the buyer pays the invoice on or before April 24, the expense is allowed in the March financial year itself.

Do Micro/Small overdue balances have to be disclosed in company financial statements?

Yes. Both Section 22 of the MSMED Act and Schedule III of the Companies Act, 2013 require audited financial statements to disclose unpaid principal and accrued Section 16 interest due to Micro and Small suppliers separately.

Calculate MSME 45-Day Late Interest & Sec 43B(h)

Section 15 credit limits: 15 days (no written agreement) vs max 45 days

Every file format and statutory compliance rule has a deterministic structure underneath the user interface. When teams rely on manual spreadsheet edits or generic cloud converters, subtle structural details get lost: page coordinate boxes reset, check digits go unverified, or rounding rules drift by several hundred rupees across a financial year. Understanding the exact specification behind MSME Interest lets you verify every output before it enters an audit file or government portal.

The reference table below summarizes the core technical and statutory parameters enforced by the local engine:

Parameter / Rule	Specification / Formula	Practical Audit Impact
No Written Credit Terms	`Statutory Due Date = Day of Acceptance + 15 Days`	Even if an invoice prints a unilateral note without a buyer-supplier agreement
Written Agreement Exists	`Statutory Due Date = MIN(Agreed Credit Days, 45 Days)`	Any contract clause granting 60 or 90 days is overridden down to 45 days by Sec 15
Interest Formula (Sec 16)	`Rate = 3 × RBI Bank Rate (e.g. 3 × 6.75% = 20.25% p.a.) compounded monthly`	Notwithstanding any zero-interest waiver in the purchase order
Tax Treatment (Sec 23 & 43B(h))	`MSME interest is 100% disallowed as tax expense u/s 23; principal disallowed u/s 43B(h) if unpaid across FY end beyond limit`	Applies to Udyam-registered Micro and Small manufacturers/service providers

Because each rule above is evaluated directly in your browser tab using typed JavaScript arrays and WebAssembly workers, there is no server queue, no file-count cap, and zero external data retention. Every byte of the source document or ledger table is parsed inside volatile browser memory and released as soon as the tab closes.

Section 16 compound interest math: 3 × RBI Bank Rate with monthly rests

Running this workflow in MSME Late Payment Interest Calculator (45-Day Rule) takes four deterministic steps from raw input to verified output:

Open MSME Late Payment Interest Calculator and enter the Invoice Amount, Date of Acceptance (delivery/service completion), and Actual Settlement Date.
Select whether a written credit agreement exists and enter the agreed credit days (the tool automatically caps credit at 45 days, or 15 days if no agreement exists).
Confirm the prevailing RBI Bank Rate (default 6.75% → 20.25% statutory penal rate).
Inspect the Appointed Day (statutory due date), overdue days, month-by-month compound interest schedule, and Section 43B(h) fiscal year boundary check.

Note: All inputs, uploaded files, and intermediate calculations remain in volatile browser RAM. Closing or refreshing the tab clears the memory buffer immediately.

When you process recurring monthly batches, keeping the input schema consistent across runs ensures that downstream checks in related guides such as calculate tds under section 194c 194j 194h 194i, compare act 365 act 360 and 30 360 day count interest, verify gstin checksum and state codes modulo 36 match to the exact rupee or byte. Before starting a large batch, verify that your source file is not locked by an unknown password and that column headers or page indices match the expected range.

Step-by-step: auditing MSME overdue invoices in ShiftTools

Computing Section 16 Compound Interest on ₹8,00,000 Paid After 95 Days (45-Day Contract)

A buyer accepts goods worth ₹8,00,000 from a Udyam-registered Small manufacturer on January 10, 2026 under a written 45-day PO, and settles the invoice on April 15, 2026 (95 days after acceptance). The Appointed Day (45-day cutoff) is February 24, 2026, leaving 50 overdue days (1 full month + 20 days). At 3 × 6.75% = 20.25% p.a. (1.6875% per monthly rest): Month 1 interest = ₹8,00,000 × 0.016875 = ₹13,500 (New principal base = ₹8,13,500). Remaining 20 days interest on ₹8,13,500 = ₹8,13,500 × 0.2025 × (20 ÷ 365) = ₹9,026.51. Total Section 16 interest = ₹22,526.51 (which is non-deductible for income tax under Section 23). Furthermore, because the invoice crossed March 31 unpaid past its February 24 due date, the ₹8,00,000 expense is disallowed in FY 2025-26 under Section 43B(h) and allowed only in FY 2026-27 upon actual payment.

TEXT

Principal: ₹8,00,000 | Acceptance: 2026-01-10 | Written Terms: 45 Days
Appointed Day (Due Date): 2026-02-24 | Settlement: 2026-04-15 (50 days overdue)
Statutory Rate: 3 × 6.75% (RBI Bank Rate) = 20.25% p.a. (Monthly Rests)
  - Rest 1 (30 days): ₹8,00,000.00 × (20.25% / 12)     = ₹13,500.00
  - Rest 2 (20 days): ₹8,13,500.00 × 20.25% × (20/365) =  ₹9,026.51
Total Sec 16 Compound Interest Payable:                  ₹22,526.51

You can reproduce this exact calculation at any time by pasting the sample values above into MSME Interest and comparing the generated summary row against your internal workpaper. Recording the input parameters alongside the output file creates a self-contained audit trail for statutory or peer review.

Worked example: ₹8,00,000 Micro vendor invoice settled 95 days after acceptance

In production accounting and document engineering workflows, edge cases appear when inputs combine multiple conventions in a single batch. For example, a merged PDF bundle may mix portrait A4 text pages (/MediaBox 595.28 × 841.89 pt) with wide environment annexures, or a quarterly ledger export may combine April-to-September transactions with October-to-March entries after a mid-year threshold revision.

To prevent silent errors across those boundaries, always inspect the per-item diagnostic status before exporting the final file:

Verify unit consistency: Confirm whether input figures represent monthly vs annual amounts, GST-exclusive vs GST-inclusive values, or 1-based physical page indices vs printed document numbers.
Check boundary conditions: Pay close attention to exact threshold cutoffs, leap-year day counts, and page rotation multiples (0, 90, 180, 270 degrees) where off-by-one errors commonly occur in manual spreadsheets.
Preserve audit trails: Save the exported summary CSV or processed PDF alongside the raw source file so any reviewer can trace the transformation step by step without re-keying data.
Cross-check neighbour utilities: Pair MSME Interest with companion tools in the Accounting & Finance suite (calculate tds under section 194c 194j 194h 194i, compare act 365 act 360 and 30 360 day count interest, verify gstin checksum and state codes modulo 36) when a task spans multiple stages.

Section 23 non-deductibility of interest and Section 43B(h) year-end cliff

Section 43B(h) of the Income Tax Act applies strictly to Udyam-registered Micro and Small enterprises that manufacture goods or render services; it does not apply to Medium enterprises or pure retail/wholesale traders (whose Udyam registration is limited to priority-sector lending). Always verify the supplier's Udyam enterprise class and major activity before booking year-end disallowances.

Limit: Client-side browser execution verifies mathematical formulas, statutory rules, and binary file structures offline. Where a regulation requires live portal authentication (such as checking active GST registration status on the GSTN portal or verifying operative PAN-Aadhaar linkage on TRACES), perform that portal check alongside your local calculation.

By separating deterministic local computation from external portal lookups, your team eliminates manual formatting and calculation errors while keeping sensitive client files off third-party cloud servers.