Most mid-market companies know Section 43B(h) exists but have not calculated what it costs them. The gap between awareness and quantification is a vendor master data problem, not a payment process problem - and that distinction matters for how you fix it.
Section 43B(h) disallows the tax deduction on payments to MSME vendors if those payments are not made within 45 days of the invoice date (or the agreed credit period, whichever is shorter). For most mid-market companies, the real exposure is not slow payment - it is not knowing which vendors in their master are MSME-registered. An unverified vendor master means the exposure cannot be calculated, let alone managed.
What 43B(h) actually costs you
If your company pays an MSME vendor after the 45-day window (or beyond the agreed period, if shorter), the payment amount is added back to your taxable income for that financial year. You recover the deduction only in the FY when the payment is eventually made.
The financial impact compounds quickly. Take a mid-market manufacturer with INR 60L in outstanding payments to MSME vendors at year-end, all overdue by more than 45 days. At a 25% effective corporate tax rate, that is INR 15L in additional tax liability for the year, a cash outflow that disappears from the balance sheet only when the underlying payments clear.
The 43B(h) disallowance is only part of the exposure. Under Section 16 of the MSMED Act 2006, as typically interpreted, delayed payments to MSME vendors attract compound interest at three times the RBI bank rate. This interest is not tax-deductible. Unlike the original payment, you cannot recover it in a later FY. Two separate liabilities run simultaneously on the same overdue invoice. The 43B(h) disallowance reverses when you eventually pay. The MSMED Act interest does not. Most AP teams track one or neither.
Why most companies do not know their exposure
The standard response when auditors raise 43B(h) is to pull a list of MSME vendors from the ERP and check payment dates. This works only if the vendor master is accurate, and in most mid-market companies, it is not.
MSME registration status is self-declared by vendors. It is not automatically verified at onboarding, not updated when a vendor’s Udyam registration changes, and not flagged when a vendor’s status shifts mid-year. A typical vendor master carries four distinct failure modes on MSME status:
- Vendor onboarded before obtaining Udyam registration - ERP shows non-MSME, reality is MSME, liability understated
- Vendor’s MSME registration lapsed or was cancelled - ERP shows MSME, 43B(h) no longer applies, liability overstated
- Vendor onboarded with no MSME verification at all - status unknown, calculation impossible
- Vendor graduated from Micro or Small to Medium enterprise due to increased turnover - no longer covered under 43B(h), but AP team continues treating them as MSME
The fourth failure mode is the least visible. A vendor that crosses the Udyam turnover threshold mid-year stops attracting 43B(h) liability from that point. If your vendor master still shows them as MSME, your AP team is tracking phantom exposure while potentially missing real exposure elsewhere.
In mid-market vendor masters, 15-20% of records typically carry unverified or outdated MSME status. Year-end compliance exercises, where the AP team manually chases Udyam certificates, are both too late and unreliable. The disallowance crystallises during the year, not at year-end. And certificates are point-in-time documents that do not capture status changes occurring after issue.
What an accurate exposure calculation requires
A defensible 43B(h) exposure calculation has three steps, each dependent on the previous one.
Step 1: Verify current MSME status against the live Udyam portal. Certificates held on file go stale; portal data does not. For a vendor master with 400-600 active vendors, this is not a one-time exercise - Udyam status changes, and your records need to reflect current status, not onboarding status.
Step 2: Cross-reference payment dates against invoice dates for verified MSME vendors. For every invoice raised by a confirmed MSME vendor in the FY, you need the invoice date, the agreed credit period if any, and the actual payment date. The exposure is the sum of invoice values where payment cleared outside the 45-day window.
Step 3: Calculate the tax disallowance and interest liability separately, and maintain a timestamped log. The 43B(h) disallowance applies to outstanding amounts at year-end. The MSMED Act interest accrues from the due date on each invoice. These require different data cuts and produce different liability figures. The log needs to capture Udyam status as it was on the invoice date, not just the payment date, so the calculation holds up under scrutiny.
The dependency is hard to overstate. With 15-20% of vendor records carrying unverified or outdated MSME status, the exposure number your AP team produces at year-end is not reliable, regardless of how carefully they ran the payment date analysis.
This is what a Finance Operations Diagnostic surfaces in the vendor master. Not just duplicate records or inactive GSTINs, but the compliance data gaps that make year-end calculations guesswork. The companies that close their 43B(h) exposure cleanly treat vendor MSME status as a live data field, not an annual certificate collection exercise.
If you have not mapped your MSME vendor base, a Diagnostic is the fastest way to find out your actual exposure and close it before year-end.
Key observations
- Section 43B(h) creates two simultaneous liabilities on overdue MSME payments: a tax deduction disallowance and compound interest under the MSMED Act; the interest is not tax-deductible.
- The root cause of most 43B(h) exposure is a vendor master data gap, not a payment process failure.
- Mid-market vendor masters typically carry 15-20% of records with unverified or outdated MSME status, making year-end exposure calculations unreliable.
- Vendor graduation from Micro/Small to Medium, removing 43B(h) applicability, is the least visible failure mode and the most likely to cause overstated liability.
- An accurate exposure calculation requires vendor MSME status as a maintained live data field with a timestamped log per invoice, not a year-end certificate collection.