Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Section 43B(h) disallows deduction for any MSME payable unpaid beyond 15 days (no written agreement) or 45 days (with agreement). A company with 150 MSME vendors and 450–1,200 invoices per month cannot track compliance reliably in spreadsheets, risking year-end disallowance on every breached invoice.
Tag every vendor with MSME status and agreement type at invoice entry, calculate due date as acceptance date + 15 or 45 days, and age each invoice against that date. Match the NEFT/RTGS UTR bank debit back to the invoice to confirm payment date. Alert AP at 10 and 35 days outstanding to prevent breach and calculate year-end disallowance at invoice level.
Vendor master MSME flag plus agreement-type tag, invoice-level age bucket linked to 15/45-day rule, UTR-keyed bank match, and automated 10-day/35-day alerts.
Complete Section 43B(h) compliance trail, zero avoidable disallowance at year-end, evidence-backed dispute pack for MSME Samadhaan, and an AP workflow that protects deductibility every invoice cycle.
For a company with 150 active MSME vendors, each generating 3 to 8 invoices per month, tracking compliance with Section 43B(h) requires monitoring roughly 450 to 1,200 invoices per month against two different payment windows (15 days without an agreement, 45 days with one). Each invoice requires four data points: acceptance date, agreement type, due date, and actual payment date. At this volume, the compliance function cannot run on spreadsheets reliably — particularly when the 15-day window leaves almost no buffer for manual review cycles.
The challenge is further complicated by the vendor master problem: MSME status is not always known at invoice time, payment date attribution requires matching to bank records, and year-end provisioning requires calculating disallowance across an entire year’s payables history.
What a Section 43B(h) Payment Tracker Must Capture
The minimum required fields for each MSME vendor transaction:
| Field | Data source | Why it matters |
|---|---|---|
| Vendor PAN | Vendor master | Required for Form MSME-1 filing |
| Udyam Registration Number | Vendor onboarding | Confirms Micro/Small classification |
| MSME category (Micro or Small) | Udyam certificate | Medium enterprises are excluded from 43B(h) |
| Invoice number | AP ledger | Transaction identifier |
| Invoice date | AP ledger | Starting reference |
| Acceptance date | Goods receipt / service confirmation | The actual clock start |
| Agreement type | Vendor contract register | Determines 15 or 45-day rule |
| Due date (calculated) | System-derived | Acceptance date + 15 or 45 days |
| Actual payment date | Bank statement debit date | The compliance measurement point |
| UTR / transaction reference | Bank statement | Links payment to bank record |
| Days outstanding at payment | Calculated | Due date minus payment date |
| Compliance status | Calculated | Within window / Breach / Still outstanding |
| Disallowance amount | Calculated at year-end | Outstanding balance at breach date |
The most error-prone fields in manual trackers are acceptance date (often substituted with invoice date, which understates elapsed time) and actual payment date (often taken from cheque issue date rather than bank debit date). Both errors reduce apparent days outstanding and mask real compliance breaches.
The Vendor Master Verification Problem
Most companies have a vendor master that records basic supplier information — PAN, GSTIN, bank details, payment terms. Section 43B(h) adds a new requirement: MSME classification must be verified and maintained for every active vendor.
The systematic challenge is that vendors do not proactively communicate MSME status, and Udyam registrations can lapse or change classification when a company’s turnover crosses a threshold. A vendor who was classified as Small in FY 2023-24 may have crossed the ₹50 crore turnover threshold and no longer qualifies as Small in FY 2024-25.
A workable collection process:
- Add Udyam certificate upload as a mandatory field in the vendor onboarding form
- Send annual recertification requests to all vendors flagged as Micro or Small in the master
- For existing vendors where certificates are missing, flag the vendor as “MSME-unverified” and default payment terms to the 15-day conservative rule until confirmed
- Maintain a document store linking each vendor record to their current Udyam certificate with effective date
The Ministry of MSME maintains the Udyam database, and Udyam registration numbers can be verified online. For high-volume AP teams, building an API or manual check into the vendor onboarding workflow eliminates the risk of accepting unverified MSME status claims.
Building the Reconciliation Logic
The core reconciliation logic for 43B(h) compliance operates at two levels:
Invoice-level compliance check: For each invoice from a Micro or Small vendor, calculate days outstanding = payment date minus acceptance date. Compare against the applicable window (15 or 45 days). Flag as compliant, breach, or still outstanding.
Year-end disallowance calculation: For all MSME invoices where compliance status is “breach” or “still outstanding” at March 31, sum the outstanding balance. This is the Section 43B(h) disallowance for the year. Split by vendor for Form MSME-1 preparation.
The reconciliation must also handle partial payments correctly. A ₹10 lakh invoice paid ₹4 lakh within the window and ₹6 lakh after — only the ₹6 lakh portion is disallowed, and the disallowance date is determined by when the ₹6 lakh became overdue, not when the partial payment was made.
Mapping MSME Payments to Bank Credits
The accounts payable ledger records a payment instruction. The bank records the actual debit. For Section 43B(h), the relevant date is the bank debit date — confirmed by the UTR generated at the time of NEFT, RTGS, or IMPS transfer.
This means every MSME payable record must be reconciled to a bank statement entry. For NEFT and RTGS payments, this is a UTR match. For IMPS, it is similarly UTR-based. For payments by cheque, the relevant date is the cheque clearance date (when the CTS clearing cycle debits the account), not the cheque issue date.
The reconciliation step between the AP record and the bank statement is where most manual trackers fail. A payment entered in the AP system on March 30 may not debit the bank until April 1 — making the payment fall in the next financial year for 43B(h) purposes. Without UTR-level bank matching, this timing risk is invisible.
Year-End Provision Calculation for Section 43B(h)
Before the books close for March 31, run a full age analysis of MSME payables:
- Extract all open MSME invoices as of March 31 where payment date is blank
- For each, calculate days since acceptance date
- Flag any invoice where days since acceptance exceeds the applicable window (15 or 45 days)
- Sum flagged invoice balances — this is the provisional disallowance
- For invoices paid but outside the window, include those in the disallowance calculation too (they are not paid within the financial year within the required window)
- Book the disallowance provision in the current year P&L; recognise the deferred tax asset (since the deduction will be available when payment is made in a future year)
- Prepare the disclosure schedule for Form 3CD (Tax Audit) Clause 8A and Form MSME-1
Integration with Accounts Payable Systems
For companies using Tally, SAP, Oracle, or similar ERP systems, the 43B(h) tracker should be built as a report layer or supplemental module rather than a standalone spreadsheet. The data already exists in the system — vendor master, invoice records, payment entries — but the system typically does not calculate MSME-specific age analysis or produce Form MSME-1 output.
The integration requirement is:
- Vendor master extended with MSME flag and Udyam number
- Invoice record extended with acceptance date and agreement type
- Payment record linked to bank statement UTR (not just payment voucher date)
- Age analysis report configured to apply 15 or 45-day rules by vendor
What Automated Reconciliation Does That Manual Tracking Cannot
Manual MSME payment trackers typically fail in three ways at scale: acceptance date is taken from invoice date (understating elapsed time), payment date is taken from AP voucher date rather than bank debit date (understating actual payment delay), and year-end provisioning misses invoices where payment occurred after year-end despite being booked before it.
An automated reconciliation layer that connects the accounts payable ledger to bank statement records using UTR matching resolves all three. The bank debit date is unambiguous. For companies already using reconciliation software India for bank statement matching, extending the same matching infrastructure to MSME payment tracking requires only the vendor master MSME flags and acceptance date fields — the UTR matching logic and bank feed processing are already in place.
The output a structured system produces — invoice-level compliance status, days outstanding, disallowance calculation, Form MSME-1 data extract — cannot be replicated reliably at volume with spreadsheets. The same logic applies here as with TDS reconciliation software: the reconciliation burden is not the complexity of any single transaction, but the volume of transactions that must all be correct simultaneously.