Tracking the MSME 45-Day Payment Deadline for Indian Suppliers
The MSME 45-day rule under Section 15 of the MSMED Act, 2006 says a buyer must pay a micro or small supplier on or before the date agreed in writing, and that date cannot be more than 45 days after goods or services are accepted. Without a written agreement, the default is 15 days. To track it, you need three things for every bill: the acceptance date, proof that the supplier holds a valid Udyam registration, and a due date that updates itself. A tracker in Tally or Zoho Books can flag bills nearing the limit. The one step a machine should not finish alone is deciding that goods were accepted, because that is a business judgement.
In short
- The 45-day clock starts at acceptance, not at the invoice date, and no contract can extend it for micro or small suppliers.
- Check every supplier's Udyam number on the official portal on a schedule, not once at onboarding.
- Late payments carry compound interest at three times the RBI bank rate, and Section 43B(h) can disallow the expense for tax.
- Automate the data work: acceptance records, due dates, alerts and payment run drafts. Keep the acceptance judgement and payment approval with a person.
What the rule asks you to do
The rule is simple to state and easy to miss in practice. Section 15 of the Micro, Small and Medium Enterprises Development Act, 2006 requires you to pay a registered micro or small enterprise on the date you agreed in writing. That agreed period cannot exceed 45 days from the day of acceptance or deemed acceptance. If there is no written credit term, payment falls due within 15 days. A purchase order that says 60 or 90 days does not override the statute for these suppliers.
Two details trip up most buyers. The first is the starting point. The clock runs from acceptance of the goods or services, which is not always the invoice date. A supplier can send an invoice a week before delivery, or a month after it. The second is the supplier's status. The protection only covers suppliers that are micro or small enterprises with a valid Udyam registration. Medium enterprises fall outside the rule. Wholesale and retail traders are generally excluded too, based on a July 2021 Ministry of MSME office memorandum that a tax-compliance article cites. Confirm this with your CA for any supplier that is a trader.
The consequence of missing the date is not only a legal issue. Under Sections 15 and 16, late amounts carry compound interest with monthly rests at three times the RBI bank rate. A worked example published in 2026 assumed a 6.5 per cent bank rate, which gives a 19.5 per cent annual statutory rate. On an unpaid invoice of ₹5,00,000, that example puts interest at about ₹24,773 after three months of delay, and about ₹50,774 after six months. The exact rate depends on the RBI bank rate in force in each period, so use the official figure from the RBI when you calculate a real claim.
Why this costs money even when the supplier never complains
Most buyers only hear about the rule when a supplier writes a stern letter. The bigger cost is quieter. Income-tax treatment is the second layer. Section 43B(h) of the Income-tax Act, 1961 was inserted by the Finance Act 2023 and applies from assessment year 2024-25. Under it, an amount payable to a micro or small enterprise is deductible only in the year you actually pay it, if payment goes beyond the Section 15 limit. A bill that is unpaid at 31 March can therefore be added back to your taxable income for that year, even if you pay it a few weeks later.
Some commentators report that this clause moves into section 37 of the Income-tax Act, 2025, which took effect on 1 April 2026. Treat that as something to confirm with your chartered accountant before you rely on a section number in your own working papers.
Put plainly, your cost has three parts. The first is the interest exposure on late bills. The second is the tax you pay on profit that you could not deduct in the year of the expense. The third is staff time, because someone has to chase bills, check Udyam numbers and prepare reports every half year. The first two are money. The third depends on your team. For a business with a few dozen supplier invoices a month, the time cost is usually the one that hurts first. Your own numbers will decide which part dominates, so pull one quarter of payables before you decide how much to spend on the fix.
Manual tracking versus an automated tracker
| Task | Manual way | Automated way |
|---|---|---|
| Recording acceptance | Someone types a date into a spreadsheet, often from memory or a delivery slip | Goods receipt or service sign-off is captured as a dated record, and the due date is calculated from it |
| Checking Udyam status | A buyer looks up each supplier once, when onboarding, and rarely again | Each URN is checked against the official portal on a schedule and changes are flagged |
| Spotting bills near the limit | Someone filters the payables sheet every few weeks, or at year end | Alerts go out at fixed points, such as day 30, day 40 and day 45 of each bill |
| Preparing a payment run | Accounts builds a list by hand and forwards it to the owner by email | A draft run is prepared with amounts, bank details and due dates, and waits for approval |
| Half-year reporting | Accounts rebuilds the ageing report from scratch | The report is generated from the same records used for daily tracking |
The table shows where the time goes. Most of the manual work is data gathering, not decision making. That is where automation pays back. The decision points stay with a person.
How to build the tracker, step by step
Start with the vendor master. Add a field for Udyam registration number, classification (micro, small, medium or trader) and whether the supplier is covered. In TallyPrime, the ledger alteration screen has an MSME registration setting where you can enter the Udyam number and classification. Zoho Books can hold the same details in its vendor record. Pick one system of record and stop keeping the list in a side spreadsheet.
Check every Udyam number against the official portal. The URN follows a fixed pattern, starting with UDYAM and a 19-character format, and it can be verified on udyamregistration.gov.in using the Verify Udyam Registration option. The certificate also carries a QR code that links to the live record. Run this check when the supplier is onboarded, then again on a schedule. A registration that was valid last year is not proof that it is valid today.
Record the written credit term for each supplier. Store the signed purchase order, supplier agreement or the terms on the accepted quotation as a file attached to the vendor. The tracker should show whether a 15-day or a 45-day window applies, and the 45-day figure should never be entered if the agreed term is longer. Set the default in your accounting software to the statutory maximum rather than to 30 or 60 days.
Capture the acceptance date as its own event. This is the step most buyers skip. Your warehouse or site team confirms receipt in a simple form, a WhatsApp message to a shared group, or a signed delivery note that is scanned. For services, the manager who signs off the work records the date. Use an OCR tool such as Google Document AI or the open-source Tesseract to read dates and amounts from scanned delivery notes and supplier invoices, then have a person confirm the values that feed the due date.
Let the system calculate the due date and the alert dates. Due date equals acceptance date plus the agreed term, capped at 45 days, or 15 days if there is no written term. Send internal alerts at set points. A simple pattern is a notice to the approver at day 30, a reminder at day 40, and a flag on the owner's dashboard at day 45. Tally's MSME bills payable report can age bills into intervals of 0 to 15, 15 to 45 and beyond, which lines up with the statutory windows.
Connect the supplier's communication channel. Many Indian suppliers send invoices and chase payment on WhatsApp. The WhatsApp Business Platform Cloud API from Meta lets your system receive supplier messages and send approved template messages, such as a payment status update. Business-initiated messages need pre-approved templates, and you should check current messaging rules on Meta's developer documentation before you go live. Email works the same way through the Gmail API or a shared mailbox, and an LLM can read incoming messages to tag them as invoice, delivery confirmation, dispute or query.
Prepare the payment run, then stop. The system builds a list of bills due in the next cycle, with supplier name, Udyam number, amount, due date and bank details. Bank details should be checked against the vendor master, not against the invoice, because invoice bank changes are a common fraud route. The list goes to an approver. Once approved, the file is uploaded to your bank for NEFT, RTGS or a bulk payment, or paid through the bank's UPI channel for smaller amounts. The system should never release money on its own.
Keep the audit trail. Every acceptance record, Udyam check, alert and approval should carry a date and a user name. This is the evidence you will need if a supplier files a complaint on the MSME Samadhaan portal, and it is the evidence a tax auditor will ask for when you report delayed MSME payments.
What breaks, and how to stop it
The most common failure is a supplier who changes status. A registered micro enterprise can grow into a medium enterprise, or a Udyam registration can be cancelled. The tracker needs a scheduled check, not a one-time check, and the owner should review changes each quarter.
The second failure is a wrong acceptance date. If the warehouse signs a delivery note on Monday but the stock is rejected on Wednesday, the clock may have started on the wrong day. Make rejections a separate event in the system, with a written reason, and link them to the bill so the due date can be recalculated or the dispute recorded.
The third is OCR misreading a figure. A 5 read as a 6 in an invoice total will flow into the payment run. Put a rule in place: any amount or bank detail that the OCR reads with low confidence goes to a person for review before it reaches the approval list. Compare the invoice total against the purchase order as a second check.
The fourth is that the supplier messages through a personal phone rather than the shared channel. Then the acceptance and chase history sits in one person's inbox. Set a rule that all supplier chases go through the shared number or mailbox. Personal data in supplier messages also falls under the Digital Personal Data Protection Act, 2023, so limit who can see that data and keep only what the tracker needs.
The fifth is the rule itself changing. The MSME Amendment Bill discussed in 2026 is a source of uncertainty for buyers, and the text needs to be checked when it is passed. Keep the 45-day and 15-day values in one settings table so you can change them in one place.
When not to automate this
Automation is not worth it for every business. If you buy from fewer than a handful of suppliers, and most of them are medium or large companies, the MSME rule may barely touch your payables. A quarterly manual review of the vendor list, done by your accountant, is cheaper and good enough.
It is also a poor fit when acceptance is genuinely disputed as a routine matter. Construction, custom manufacturing and project services often have milestones, retention money and quality sign-offs that cannot be reduced to a single date. Automation can record the milestone and the sign-off, but a person must decide whether the work was accepted and whether the amount is payable. The AI can show you the date and the document. It cannot tell you that a pipe joint was accepted despite a leak, or that a consultant's report meets the brief.
Finally, do not automate a payment without an approval step, even when the list is correct. The tracker can say what is due. A named person should say what to pay, and when.
What setup typically takes
The time depends on how many suppliers you have, how clean your vendor records are, and whether your accounting system already holds bill dates. As a planning estimate, not a benchmark from a published study, a first working version usually takes a few weeks of part-time effort from one accounts person and one operations person. The longest task is usually cleaning the vendor master and collecting written credit terms, not building the alerts. Budget more time for the first half-year report, because it is the first time the records are tested against a real audit question.
Start with one quarter of payables. Check every supplier's Udyam number, classify each bill, and see how many fall outside the window. That exposure figure will tell you whether the full build is worth the time.
Sources
- MSME 45-Day Payment Rule: How Micro and Small Suppliers Can Recover Delayed Payments
- MSME Payment Rule: 45-Day Deadline & Tax Compliance Guide
- [FAQs] Liability of Buyer u/s 15 of MSMED Act to Make Timely Payments to MSE Suppliers
- MSME Interest Calculator — Section 16 Delayed Payment 3x Bank Rate (2026)
- MSME 45-Day Payment Rule: Section 15 Explained
How AiStaffo would automate this
AiStaffo would connect your accounting records, your goods receipt or sign-off inbox, and the shared WhatsApp or email channel where suppliers send invoices. The system would hold each supplier's Udyam number and written credit term, calculate the 15-day or 45-day due date from the recorded acceptance date, and send internal alerts at set points before the deadline. It would also draft a payment run each cycle with amounts and verified bank details. Your team still confirms acceptance, rejects or disputes bills, and approves every payment. To see how this would fit your own supplier list, Book a free automation audit.
Questions people ask
Does the 45-day MSME rule apply to every supplier?
What is the difference between the 15-day and 45-day deadline?
How do I check whether a supplier has a valid Udyam number?
What happens if I pay an MSME supplier late?
Can accounting software like Tally or Zoho Books track this automatically?
Book a free automation audit
Thirty minutes. We look at one process you run every week and tell you exactly what an AI worker would take off your desk, and what it would not.
