AWS Builder Center

Indian MSMEs Are Owed ₹8.1 Lakh Crore. I Built the Interest Calculator Nobody Had.

The MSMED Act already guarantees Indian small businesses 16.5% compound interest on late payments. Almost nobody collects it, because almost nobody can compute it. How I built a deterministic statutory interest engine on serverless AWS in a weekend.

Most hackathon projects start with a technology and hunt for a problem. I spent the first several hours of this one doing the opposite, and I nearly talked myself out of the idea three times before I started writing code.
The number that stopped me was this: roughly ₹8.1 lakh crore is locked up in delayed payments to Indian micro and small enterprises, according to the Economic Survey 2025-26. That is not a market sizing estimate invented for a pitch deck. It is a government figure describing money that has been earned, invoiced, and simply not paid.
What made it interesting was the second fact. These businesses are already legally entitled to compound interest on that money, and almost none of them collect it.

The law nobody uses

Section 15 of the MSMED Act 2006 says a buyer must pay a registered micro or small supplier within the agreed period, and in no case later than 45 days from acceptance. Section 16 says that if they do not, interest accrues at three times the RBI Bank Rate, compounded with monthly rests. Section 24 makes this override any contract clause to the contrary, so a buyer cannot write their way out of it in the purchase order.
The RBI Bank Rate is currently 5.50 percent. Three times that is 16.5 percent, compounding monthly. On a ₹5 lakh invoice sitting unpaid for two hundred days, that is over ₹47,000 the supplier is legally owed and almost certainly will never ask for.
So why does nobody claim it?
I went looking for the answer in the filing data rather than guessing. The MSME Samadhaan portal had received around 2.57 lakh applications worth roughly ₹55,244 crore as of June 2026. Against an ₹8.1 lakh crore problem, under seven percent of the money ever reaches a portal at all. And of what does arrive, the disposal rate has fallen from about 33 percent in FY21 to just 4.07 percent by FY26.
Then I read the filing guidance itself, and found the detail that turned this from an observation into a product. Advisory sources repeatedly warn that MSMEs forget to include the statutory interest calculation in their claim, and recover less as a result.
That is the actual bottleneck. Not awareness. Not the law. Arithmetic.

Why the arithmetic is genuinely hard

I assumed this would be a compound interest formula and a text field. It is not.
To compute a Section 16 claim correctly you need to derive the appointed day, which is the acceptance date plus the agreed credit period, clamped to a maximum of 45 days. Then you compound from the day after that, with monthly rests anchored to the appointed day rather than to calendar months, which means you need end of month clamping so that the 31st of January plus one month lands on the 28th or 29th of February and does not then drift for the rest of the schedule. Interest accrues on a day count basis within each rest period and capitalises only at completed period boundaries, so the final partial period accrues simple and is not capitalised. And if the RBI Bank Rate changed while the invoice was outstanding, you have to split that period at the change date and apply each rate to its own day segment.
Every one of those is a place to be quietly wrong by a few thousand rupees.
This is exactly the kind of problem where the instinct is to reach for a language model, and it is exactly where that instinct is worst. I made one architectural decision early and it shaped everything after it.
No model touches any number.
The interest engine is pure Python. Decimal throughout, no floats anywhere, no I/O, no dependencies. It returns a month by month breakdown where every row exposes its accrual basis, the rate applied, the day count, the interest for that period, and the closing balance. Fifteen unit tests cover leap year February, mid period rate changes, partial payments, credit terms above and below the 45 day clamp, and the non capitalised final period.
Before I wrote a single line of AWS infrastructure, I ran one worked example and checked the first rest period by hand on paper. ₹5,00,000 accepted on 15 January, appointed day 1 March, first period 31 days at 16.5 percent. That is ₹7,006.85. The engine agreed. Only then did I start building around it.
That ordering mattered more than anything
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article