Section 43B(h): The Clause That Reprices Your Client's March

Most of the provisions a tax auditor deals with are settled. You know the limit, you test against it, you report. Section 43B(h) is not like that, and three audit seasons in, it is still producing arguments in conference rooms.

The clause itself is one sentence. The trouble is that almost every part of applying it depends on a fact about your client's supplier that your client does not have written down.

The rule, precisely

Section 43B(h) says that any sum payable to a micro or small enterprise beyond the time limit in section 15 of the MSMED Act is deductible only in the year it is actually paid.

Section 15 sets that time limit at 45 days where there is a written agreement, and 15 days where there is not. Not 45 days always, which is the version that circulates.

Then comes the part that catches people. Section 43B carries a proviso allowing a deduction if the amount is paid by the return filing due date under section 139(1). Clauses (a) to (g) get that relief. Clause (h) does not. An amount outside its section 15 window at year end is not rescued by paying it in September. It moves to the next year, and there is nothing to argue about.

There is one piece of good news buried in the timing, and it gets missed in the other direction:

An invoice that is still inside its 15 or 45-day window on 31 March, and is then paid in April within that window, was never disallowable at all.

It is not a late payment. It is a payment made on time that happens to straddle a year end. Treating the whole March creditor balance as an add-back is as wrong as ignoring the clause, and it is the more common error in practice because it feels conservative.

Three facts you need per supplier, not per invoice

This is where the clause stops being a computation and starts being a data problem.

One: is the supplier micro or small? The clause reaches micro and small enterprises. Medium enterprises are outside it. A supplier can hold a perfectly valid Udyam registration and still be a medium enterprise, in which case 43B(h) simply does not apply to what you owe them.

Two: is the supplier a trader at all? This one is worth stopping on, because it goes the other way from what most people assume. Wholesale and retail traders were brought into Udyam registration for the purpose of priority sector lending. They were not brought inside section 15. A trading supplier with a Udyam number is outside section 15, and therefore outside both 43B(h) and clause 22 of Form 3CD.

That single distinction moves large numbers. A firm that treats every Udyam-registered creditor as an MSME under 43B(h) will over-disallow, and the client will be paying tax on a sum that was never disallowable.

Three: is there a written agreement? Because that is what decides whether the supplier's clock ran for 15 days or 45. In the absence of an agreement the window is the shorter one, and a payment on day 30 — comfortably early under the number everyone remembers — is late.

Why this is hard to do by hand

The computation is per invoice, per day, across the whole creditor population. You need, for every unpaid or late-paid invoice: the invoice date, the payment date, the applicable window, and the supplier's status.

A creditor ledger with four hundred invoices across sixty parties is not a sampling problem. Every invoice either sat inside its window or it did not, and the answer is different for each one. There is no representative invoice.

Then, having computed it, you have to be able to defend it. When the client asks why ₹4,20,000 was added back for a particular vendor, "our workings show it" is not the answer that ends the discussion. The answer that ends it is the invoice, the payment, the number of days between them, and the registration certificate that establishes the supplier's status.

How Audcrix runs it

Audcrix reads the ledgers and vouchers straight from Tally, then computes 43B(h) invoice by invoice rather than on the closing balance.

• The window is applied per invoice, 15 or 45 days according to what the engagement records about the agreement, not a single blanket figure across the ledger.
• Supplier status is read from the Udyam certificate where one has been provided, so micro, small and medium are distinguished on evidence rather than on the vendor's letterhead.
• Traders are carved out of section 15, and therefore out of 43B(h) and clause 22, instead of being swept in because they hold a registration.
• Next-year payments are read from the following financial year's books where that year has been synced, so an invoice paid inside its window in April is correctly not disallowed, and one paid beyond it lands in the right year.
• Every add-back opens onto its own vouchers. The row carries the party, the amount, the days elapsed and the section that triggered it.

Where the evidence is not there — no certificate, no agreement on file — the row is flagged and stated as unresolved. It is not quietly assumed one way. A blank is not assurance, and an add-back computed on a guess is a number you cannot defend in the meeting where it matters.

Audcrix is audit and compliance intelligence for Indian CA firms. It reads a client's books once, straight from Tally, and runs the statutory tests across the whole population. See how it works.