How to manage section 43B(h) interest penalties - Supplier payment guide

Delay in making payments to suppliers in India has transformed from being a more operational inconvenience into a compliance risk. Section 43B(h) of the Income Tax Act, incorporated via Finance Act 2023 and effective from April 1, 2024, has altered the way businesses should handle payments to Micro and Small Enterprises listed in the MSMED Act 2006. This amendment makes it clear that the ability to claim an expenditure as a tax deduction is dependent on the time frame for payments made. If the payment made by a business to a registered MSE supplier is made after 15 days from the date of receiving supplies without any written agreement or more than 45 days in case of any written agreement, the expense cannot be deducted in the current year. The deduction is postponed to the following year when payment was made.

What often gets missed is that the tax disallowance is only one side of the cost. Under Section 16 of the MSMED Act, any payment delay beyond the prescribed window also triggers compound interest, calculated at three times the RBI's notified bank rate. This interest is non-deductible under Section 23 of the MSMED Act read with Section 37(1) of the Income Tax Act, so it becomes a direct, non-recoverable cost on top of the lost deduction. Add to this the operational fallout of strained supplier relationships and disputes over acceptance dates, and the real cost of delayed payments extends well beyond a line item in the tax audit report.

Understanding section 43B(h)- A quick overview

What is section 43B(h)

Section 43B(h) is a clause added to Section 43B of the Income Tax Act, 1961, through the Finance Act 2023. Section 43B as a whole override’s normal accrual-based accounting by allowing certain expenses as deductions only when they are actually paid, not merely when they are recorded as payable. This actual-payment concept is expressly extended to sums owing to Micro and Small Enterprises under clause (h): if the payment is not made within the time frame specified under Section 15 of the MSMED Act, 2006, the deduction is disallowed for that financial year and can only be claimed in the year the payment is actually made. The provision took effect from April 1, 2024, and is applicable from Assessment Year 2024-25 onward, and it applies irrespective of whether the buyer follows the cash or mercantile method of accounting.

Why was it introduced

The MSMED Act, 2006, already required timely payment to MSE suppliers under Section 15, with interest liability under Section 16 for delays. These were civil remedies that businesses could and often did ignore, since enforcement depended on the supplier initiating action. Section 43B(h) was introduced to attach a direct tax consequence to non-compliance, giving buyers a financial reason to pay on time rather than treating the MSMED Act's payment timeline as a formality.

What are section 43B(h) interest penalties?

Section 43B(h) interest penalties refer to the interest liability that arises under Section 16 of the MSMED Act, 2006, when a buyer fails to pay a registered Micro or Small Enterprise supplier within the timeline prescribed under Section 15 of that Act, 15 days without a written agreement, or up to 45 days with one. This interest is calculated as compound interest at three times the bank rate notified by the RBI, and it accrues automatically from the day after the payment window lapses. It is separate from, and in addition to, the tax deduction disallowance imposed under Section 43B(h) of the Income Tax Act, and it cannot be claimed as a tax-deductible business expense under Section 37(1) of the Income Tax Act, read with Section 23 of the MSMED Act.

How delayed supplier payments increase business costs

1. Interest accumulation

Once a payment to a registered MSE supplier crosses the 15-day or 45-day window, compound interest under Section 16 of the MSMED Act begins accruing automatically, at three times the RBI's notified bank rate. Because this interest compounds and cannot be deducted for tax purposes under Section 37(1) read with Section 23 of the MSMED Act, the outstanding liability grows steadily the longer settlement is delayed, turning a single overdue invoice into a compounding cash outflow with no offsetting tax benefit.

2. Cash flow impact

Ironically, a provision designed to protect supplier cash flow also tightens the buyer's own cash flow discipline. Businesses that previously relied on extended credit periods with MSE vendors, 60, 90, or even 120 days, now need to release payments within a much narrower window to avoid both disallowance and interest. This compresses the working capital cycle and requires tighter coordination between procurement, accounts payable, and treasury functions to ensure funds are available when MSE dues fall due.

3. Reduced profitability

The combined effect of tax disallowance and non-deductible interest directly erodes profitability. A disallowed expense inflates taxable income for the year, increasing the tax outflow on money that has already been spent, while the accompanying interest is a pure cost with no corresponding deduction. Over a financial year with multiple delayed MSE payments, this double impact can meaningfully reduce net margins, particularly for businesses with thin operating margins or high dependence on MSE suppliers.

4. Audit observations

Section 43B(h) compliance is now a direct line item in the statutory audit process. The Tax Audit Report (Form 3CD) requires auditors to disclose the total amount payable to MSME vendors as of March 31, along with amounts paid within the prescribed timeline and amounts delayed and therefore disallowed. Statutory auditors are also expected to cross-verify these figures against a company's Form MSME-1 filings. This means delayed payments do not go unnoticed internally; they are flagged directly to the Income Tax Department through the audit report itself.

5. Vendor disputes

Disputes often arise around the date of "acceptance" of goods or services, since the 15-day or 45-day clock starts from acceptance or deemed acceptance, not from the invoice date. Disagreements over delivery timelines, quality objections, or documentation gaps can shift this reference date, creating friction between buyer and supplier over exactly when the payment window began, and consequently over whether a payment was actually late.

6. Compliance risks

Beyond the income tax exposure, non-compliance carries a wider set of risks. Inaccurate or incomplete Form MSME-1 filings can attract penalties under the Companies Act, adding a corporate compliance layer on top of the tax consequences. Since auditors are required to report MSME payment delays directly, businesses face limited room to manage or explain away non-compliance after the fact, making proactive tracking far more important than after-the-fact reconciliation.

7. Loss of supplier trust

Consistent delays, even where a business ultimately pays the compound interest, damage the buyer's standing with MSE suppliers. Given Section 43B(h)'s emphasis on payment discipline, MSE vendors are increasingly likely to track payment histories and factor them into future negotiations, pricing, and willingness to extend credit. A pattern of delayed settlements can make a business a less attractive customer relative to competitors who pay reliably within the prescribed timelines.

8. Procurement disruptions

Where supplier trust erodes, procurement teams may find MSE vendors less willing to prioritize orders, extend flexible terms, or accommodate urgent requirements. This can disrupt sourcing continuity, particularly for businesses dependent on a concentrated base of MSE suppliers for critical inputs, and may push procurement teams toward less favorable terms or alternate vendors to maintain supply chain reliability.

How to calculate section 43B(h) interest penalties

⇒  Formula

Section 16 of the MSMED Act mandates compound interest with monthly rests, at three times the RBI's notified bank rate. The standard compound interest formula applies:

A = P × (1 + r/12)?

Where:

♦  A = total amount payable (principal + interest)

♦  P = principal amount outstanding

♦  r = annual interest rate (3 × RBI bank rate)

♦  n = number of months (or part-months) the payment is overdue

Interest owed = A − P

⇒  Due date

The due date is governed by Section 15 of the MSMED Act, not by any commercial agreement that exceeds it. If there's a written agreement, the due date is whatever is specified in it, capped at 45 days from the date of acceptance (or deemed acceptance) of goods or services. If there's no written agreement, the due date is 15 days from acceptance. Interest begins accruing from the "appointed day," legally defined as the day immediately following the expiry of this period.

⇒  Actual payment date

This is simply the date the buyer actually settles the invoice. The gap between the appointed day and this date determines the number of months (n) used in the interest calculation. Even partial delays of a few days into a new month typically require prorating or rounding conventions that businesses should apply consistently.

⇒  Interest rate

The applicable rate is three times the bank rate notified by the RB. As of the RBI's April and June 2026 Monetary Policy Committee meetings, the Bank Rate stands at 5.50%, making the applicable annual rate approximately 16.5%, compounded monthly. This rate is not fixed for the life of the delay: if the RBI revises the Bank Rate partway through the overdue period, the applicable rate for each month is the rate in force during that month, not the rate on the appointed day.

⇒  Example calculation table

Assume an MSE supplier delivers goods on March 1, 2026, with a written agreement specifying 45-day payment terms. The appointed day is therefore April 15, 2026. The buyer actually pays on June 30, 2026, a delay of 76 days, or approximately 2.5 months.

This ?34,730 is a statutory liability, cannot be waived contractually, and is not deductible as a business expense under Section 23 of the MSMED Act read with Section 37(1) of the Income Tax Act.

Common mistakes while calculating interest

1. Using simple interest instead of compound interest. Many finance teams default to a straightforward P × r × t calculation, which understates the actual liability since Section 16 mandates compounding with monthly rests.

2.  Calculating from the invoice date instead of the date of acceptance. The clock starts from acceptance or deemed acceptance of goods or services, not the invoice date, and these can differ, especially where delivery and invoicing happen on different dates.

3.  Applying a fixed rate for the entire delay period. If the RBI revises the Bank Rate while a payment remains overdue, the rate applicable to each month should reflect the rate in force during that specific month, not the rate on day one of the delay.

4.  Ignoring the 45-day cap when a contract specifies a longer term. Even if the agreement states 60 or 90 days, interest calculations must use the statutory 45-day cap, since Section 15 overrides any contrary contractual term.

5.  Failing to prorate partial months correctly. Since compounding is monthly, businesses need a consistent convention for part-month delays (as used in the formula above via the exponent n), rather than rounding up or down arbitrarily, which can materially skew the result over longer delays.

6.  Assuming the interest can be offset against tax. Some finance teams initially factor the interest into taxable expense calculations; Section 23 of the MSMED Act explicitly disallows this deduction, so the full interest amount is a cash cost with no tax benefit.

Common reasons businesses miss supplier payment deadlines

⇒  Manual invoice approvals

Many businesses still route invoices through manual sign-offs, physical forms, email chains, or spreadsheet-based tracking, rather than a structured invoice to pay cycle. When approvals depend on someone remembering to check an inbox or physically sign a document, invoices sit idle well past their acceptance date, quietly eating into the 15-day or 45-day window before anyone notices.

⇒  Missing invoices

Invoices get lost between departments, misfiled, or never reach accounts payable at all, particularly when suppliers email invoices directly to a requester rather than a centralized intake point. Without a single point of entry into the procurement process, a valid invoice can go completely untracked until the supplier follows up, by which point the payment deadline has often already passed.

⇒  Long approval workflows

Multi-level approval chains, especially where sign-off is required from department heads, finance, and sometimes a second finance reviewer, add days to the invoice to pay cycle before payment can even be released. Each additional layer increases the chance of delay, particularly when approvers are unavailable, traveling, or simply slow to act on requests sitting in a queue.

⇒  PO mismatches

Discrepancies between the purchase order, the goods receipt note, and the invoice, whether in quantity, pricing, or line-item description, routinely stall payments while finance teams investigate the mismatch. This three-way matching step is meant to prevent overpayment, but when it triggers frequent exceptions, it becomes one of the most common bottlenecks in the procurement process.

⇒  Incorrect vendor data

Outdated bank details, incorrect GSTINs, mismatched vendor names, or incomplete Udyam registration information in the vendor master can cause payments to bounce, get flagged for review, or require manual correction before they can be processed. This is especially costly for MSE suppliers, since correcting the record often takes longer than the payment window itself allows.

⇒  Lack of payment visibility

Without a centralized dashboard or reporting tool that tracks invoice status, due dates, and ageing, finance teams often don't know an MSE payment is approaching its deadline until it's already overdue. This lack of real-time visibility into the accounts payable pipeline means payment prioritization happens reactively, based on which supplier calls or escalates, rather than on statutory due dates.

⇒  Decentralized finance processes

In organizations where different business units, regional offices, or departments manage their own procurement and payment approvals independently, there's often no single, standardized invoice-to-pay cycle across the company. This makes it difficult to consistently apply the same MSE payment discipline everywhere, and dues can slip through simply because one location's process is slower or less structured than another's.

⇒  Poor procurement coordination

Gaps between the procurement team, which places orders and confirms delivery, and the finance team, which processes payment, are a frequent source of delay. If procurement doesn't promptly confirm acceptance of goods or services, or doesn't flag a vendor's MSE status at the point of onboarding, finance has no reliable trigger to start the clock on the 15-day or 45-day window, and by the time the gap is caught, the deadline has already passed.

Best practices to avoid section 43B(h) interest penalties

1.  Verify MSME supplier status regularly

Vendor MSME classification can change year to year as a supplier's turnover or investment shifts, and a supplier who wasn't MSME-registered at onboarding may later obtain Udyam Registration. Businesses should periodically cross-check vendor master data against the Udyam portal rather than relying on a one-time verification done at the start of the relationship, since an outdated classification directly affects whether Section 43B(h) applies to that vendor's invoices.

2.  Maintain accurate payment due dates

Every MSE vendor invoice needs a due date calculated correctly from the date of acceptance, not the invoice date, and capped at 45 days even where a written agreement specifies a longer term. Building this calculation into the vendor master or invoice record at the point of entry, rather than leaving it to manual computation later, reduces the risk of a payment slipping past its statutory deadline unnoticed.

3.  Automate invoice approvals

Manual, email-based approval chains are one of the most common causes of missed MSME payment deadlines. AI-powered AP automation can route invoices automatically based on predefined approval hierarchies, flag MSE-registered vendor invoices for priority handling, and remove the dependency on someone manually forwarding a document at each stage of the invoice-to-pay cycle.

4.  Track invoice aging in real time

An aging report that segments MSE vendor invoices separately from standard payables and flags anything approaching the 15-day or 45-day threshold gives finance teams a clear, ongoing view of upcoming statutory deadlines rather than discovering overdue invoices at month-end or during audit preparation.

5.  Set payment reminders

Automated alerts triggered a set number of days before an MSE invoice reaches its due date give approvers and finance teams a buffer to act before the appointed day passes. This is particularly useful for invoices caught in longer approval chains, where a reminder can prompt escalation before the deadline is missed rather than after.

6.  Improve procurement-finance collaboration

Procurement typically confirms delivery and acceptance of goods or services, which is the trigger point for the 15-day or 45-day clock, while finance processes the actual payment. Establishing a clear handoff, where procurement promptly logs acceptance and flags MSE vendor status at the point of purchase order creation, gives finance an accurate and timely starting point for tracking each invoice's statutory deadline.

7.  Monitor vendor payment dashboards

A centralized dashboard showing payment status, aging, and MSE classification across all vendors and business units gives finance leadership visibility that individual invoice-level tracking can't provide. This is especially important in decentralized organizations, where payment processes may otherwise vary by department or location, making company-wide MSME compliance difficult to monitor consistently.

8.  Conduct periodic compliance reviews

Since Section 43B(h) compliance is now directly reported through the Tax Audit Report and cross-verified against Form MSME-1 filings, periodic internal reviews, ideally quarterly rather than only at year-end, help identify overdue MSE payments while there's still time to act, rather than discovering disallowances and interest liabilities only when the auditor flags them.

The role of AP and MSME automation

Much of what makes Section 43B(h) compliance difficult in practice, manual tracking, disconnected procurement and finance systems, and inconsistent processes across business units, is fundamentally a visibility and workflow problem. AI-powered AP automation and dedicated MSME payment tracking tools address this by automatically identifying MSE-registered vendors, calculating due dates from the correct acceptance trigger, flagging invoices nearing their statutory deadline, and consolidating payment status into a single view. For businesses managing MSE payments across multiple vendors, departments, or locations, this kind of automation reduces reliance on manual coordination and makes consistent, deadline-aware payment discipline far more achievable than spreadsheet-based tracking allows.

How AI-Powered AP automation & MSME Automation help reduce section 43B(h) risks

♦  Automated invoice capture

Invoices are captured automatically from multiple channels, email inbox, vendor portal submissions, PDFs, scanned documents, and API integrations, so nothing depends on a single person forwarding a document. This centralized intake, a core capability of AI-powered AP automation, removes the invoice leakage that often delays the payment clock before an invoice is even logged into the system.

♦  Intelligent approval workflows

Once captured, invoices are routed through rule-based approval workflows based on invoice value, hierarchy, department, cost center, and vendor or PO-based logic. With AI-driven AP automation, every action in the workflow is recorded, which keeps approvals moving without sacrificing the governance finance teams need over who signs off on what.

♦  Due-date alerts

Every MSME invoice is timestamped at the point of receipt, and the system automatically counts down the 45-day payment window, escalating as the deadline approaches. Delays are also tracked through SLA-based escalation triggers and automated reminders, so an invoice sitting in an approval queue doesn't quietly cross its statutory deadline unnoticed.

♦  Vendor classification

The system scans the vendor master and automatically tags registered MSME suppliers using Udyam registration data, removing the need for manual classification or periodic manual re-checks. This ensures the 45-day tracking is applied correctly and consistently across the vendor base.

♦  Payment prioritization

Invoices approaching the 45-day limit are automatically fast-tracked within the approval workflow, so payments closer to their statutory deadline get priority over lower-urgency invoices rather than being processed in whatever order they happen to reach a reviewer.

♦  Real-time dashboards

Finance teams get real-time visibility into invoice processing and approval status, accounts payable aging, vendor spend, and liabilities through centralized dashboards. For MSME compliance specifically, a live MSME payment tracker shows pending invoices, days used against the 45-day window, and flags invoices that are at risk, under review, or on track.

♦  ERP integration

Validated invoices are posted directly into the organization's ERP without manual data entry, keeping invoice data, approval status, and payment records synchronized. The platform integrates with major ERP and accounting systems, including SAP, Oracle, Microsoft Dynamics, NetSuite, Zoho, Tally, and others, so MSME due-date tracking works against the same records used for financial reporting.

♦  Audit trails

The applicable rate is three times the bank rate notified by the RBI. Each invoice is subjected to an automated validation system that covers 71 checkpoints, such as fraud and duplicate detection, vendor master and Udyam verification, three-way matching, and MSME Section 43B(h) payment deadline checks, with a complete audit trail logged for every workflow action. This creates a timestamped record supporting the disclosures required under the Tax Audit Report, without manual reconciliation at audit time.

♦  Compliance reporting

Because MSME vendor identification, 45-day tracking, and priority-based routing are built into the same workflow, finance teams get audit-ready, IT-return-ready documentation of payment timelines without assembling this data manually at year-end. This is where AI-powered AP automation moves beyond basic reminders, tying compliance reporting directly into the payment process itself rather than treating it as a separate exercise. The goal is a straightforward outcome full protection of the tax deduction entitlement under Section 43B(h), with no missed payment deadlines to explain during the audit.

Essential checklist for managing section 43B(h) compliance

⇒  Identify MSME suppliers 

Review your vendor base and flag which suppliers qualify as Micro or Small Enterprises under the MSMED Act, since only these vendors fall under Section 43B(h). Build this identification into the vendor onboarding process itself, rather than doing it as a separate exercise later. Medium enterprises and unregistered small businesses should be explicitly excluded from this classification, since only Micro and Small entities are covered.

⇒  Verify Udyam registration 

Confirm each MSME vendor's registration status directly against the Udyam portal, and re-verify periodically, since a supplier's classification can change as turnover or investment shifts. Avoid relying on self-declared MSME status or outdated Udyog Aadhaar certificates, since only current Udyam Registration is valid proof. Set a fixed cadence, such as annually or at contract renewal, for re-checking each vendor's status.

⇒  Record invoice receipt dates 

Log the date of acceptance or deemed acceptance of goods or services accurately for every MSME invoice, since this date, not the invoice date, is what starts the statutory payment clock. Ensure procurement and warehouse teams understand that the acceptance date, not the delivery challan date or invoice date, is the reference point. Any disputes over quality or documentation that delay formal acceptance should be resolved and recorded quickly to avoid ambiguity later.

⇒  Track statutory payment deadlines 

Calculate the due date correctly, 15 days without a written agreement, or up to 45 days with one, and apply the 45-day cap even if the agreement specifies a longer term. Build this calculation into the vendor master or invoice record automatically, rather than leaving it to manual computation by whoever processes the invoice. Flag any contracts that specify payment terms beyond 45 days so finance knows the statutory cap overrides the contractual term.

⇒  Monitor invoice aging 

Maintain a separate aging view for MSME vendor invoices so anything approaching the 15-day or 45-day threshold is visible well before the deadline passes. Segment this view by urgency, on track, at risk, overdue, so finance can prioritize action on the invoices closest to breach. Share this aging data with approvers directly, not just with the finance team, so bottlenecks in the approval chain get addressed early.

⇒  Automate approvals 

Reduce dependency on manual, email-based sign-offs by routing MSME invoices through defined approval workflows that move quickly and consistently. Set clear escalation rules so an invoice stuck with an unavailable approver doesn't sit idle past its deadline. Fast-track MSME invoices specifically within the workflow, rather than treating them the same as standard vendor payments.

 ⇒  Schedule timely payments 

Prioritize MSME invoices nearing their statutory deadline in payment runs, rather than processing payments in the order suppliers happen to follow up. Align payment run schedules with the MSME payment calendar rather than a fixed monthly or bi-weekly cycle alone. Keep a buffer of a few days before the statutory deadline to account for any last-minute banking or processing delays.

⇒  Maintain audit-ready records 

Keep a clear, timestamped trail of invoice receipt, approval, and payment for every MSME transaction, since this is what auditors cross-check against Form MSME-1 filings and the Tax Audit Report. Store supporting documents, purchase orders, GRNs, and approval logs alongside each invoice so the full payment history is easy to retrieve. Reconcile this trail against Form MSME-1 filings periodically, not only at year-end, to catch discrepancies early.

⇒  Review outstanding invoices monthly 

Don't wait for year-end or audit season; a monthly review of pending MSME dues gives finance teams time to act before disallowance or interest liability sets in. Involve both procurement and finance in this review, since delays often originate in acceptance confirmation or approval routing rather than payment processing itself. Track any recurring vendors or departments where delays keep showing up, and address the underlying process gap directly.

⇒  Monitor compliance reports 

Regularly check reports showing MSME dues outstanding, payments made within versus beyond the statutory window, and any accrued interest, so compliance status is known well ahead of the financial year close. Share these reports with finance leadership on a recurring basis so compliance risk stays visible beyond the AP team. Use these reports to estimate potential disallowance and interest exposure before the tax audit, rather than discovering the full impact only when the auditor reports it.

Conclusion

Section 43B(h) is more than a routine tax compliance requirement. It directly shapes working capital, supplier relationships, and overall financial health. A single delayed MSME payment carries a compounding cost, a deferred tax deduction on one hand and a non-deductible compound interest liability on the other, and its effects reach well beyond a line item in the tax audit report. Managing supplier payments proactively, rather than fixing missed deadlines after the fact, is what protects a business from these costs. Tracking MSME vendor status, calculating due dates correctly from the date of acceptance, and monitoring invoice aging on an ongoing basis stand between a business and unnecessary interest costs, tax disallowances, and strained supplier relationships.

Combining strong payment processes with the right automation is what makes this manageable at scale. AI-powered AP automation reduces the manual bottlenecks that most often cause delays, improves real-time visibility into upcoming deadlines, and turns Section 43B(h) compliance from a year-end scramble into a routine, well-controlled part of how accounts payable operates.