Skip to content
OHMby YantrAI
Log in Book a demo Start free
OHM · The AI team · MSME Agent
Invoice entry

MSME Agent

Section 15 of the MSMED Act sets the window: the date agreed in writing, never beyond 45 days from acceptance — and just 15 days where nothing was agreed in writing. Section 43B(h) then makes a late payment to a registered micro or small enterprise non-deductible until it is actually paid. Two different consequences, one clock, and nobody with the time to track it per vendor.

A registered small vendor is paid inside the statutory window — 45 days, or 15 where nothing was agreed in writing.The clock runs from acceptance or deemed acceptance, not from the invoice date, and which window applies depends on whether there is a written agreement. Both are resolved per vendor and turned into a constraint on the payment run.

What it checks

On every invoice, not a sample.

  • Udyam registration and enterprise category against the vendor, not against memory
  • Which window applies — 45 days on a written agreement, 15 days without one
  • The day the clock actually started: acceptance or deemed acceptance, not the invoice date
  • Whether written objection was raised inside 15 days, since that changes the computation
  • Days remaining on every open invoice, and whether the scheduled run lands inside the window

What it reads, what it writes

Reads

Vendor master and Udyam registration · Purchase terms, and whether they are agreed in writing · Acceptance and delivery dates · The scheduled payment run

Writes

Days remaining against every open invoice for a registered vendor · The window applied and why, so the computation can be re-read · A scheduling constraint on the run, and a flag where the window cannot be met

Where it sits in the team

Agents do not work alone. Each one hands its result to the next, so a finding raised here shows up as context downstream rather than being re-derived.

Hands to it

TDS Agent

It triggers

DOA Agent

When it isn't sure

Registration status changes, and a vendor can register after invoicing. Where status or the agreed-in-writing question is unclear, the shorter window is applied and the case is named — assuming the longer one is the expensive direction, because the consequence is both interest and a disallowed deduction.

Why this matters more than the accuracy number

Any check that runs on every transaction will meet cases it cannot settle. What makes a control trustworthy is not that it never hesitates — it is that hesitation produces a named question for a person, rather than a silent pass or a silent block.

See what this one finds in your last 90 days.

One export. No connector. We come back within a working day.

$Check your savings→