We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Free tool

Check MSME payment delays for free, right now.

Drop in a vendor/purchase register CSV. See every MSME-flagged invoice paid — or still unpaid — more than 45 days after the invoice date, the trigger behind Section 22 of the MSMED Act and the related disclosure requirement.

Drop your vendor/purchase register CSV here, or choose a file.

Needs a vendor name and invoice date column; payment date, amount and an MSME flag make the check complete.

What this does and doesn't do

  • Your file is read entirely in your browser and never uploaded anywhere.
  • It only reads what the MSME/MSME-registered flag column actually says — it does not guess which vendors are Udyam-registered, and a blank flag is reported as "can't determine," not as a pass.

How to use this

  1. Export the vendor or purchase register as CSV

    Needs a vendor name and invoice date column; payment date, amount and an MSME flag column make the check complete.

  2. Drop it in above

    The tool matches common header variations automatically.

  3. Pull the flagged invoices and confirm Udyam registration

    A blank MSME flag is not a "not MSME" — it's a gap in the export that needs a manual check.

  4. Quantify the disallowance and disclosure separately

    This tool finds the delayed invoices; computing the section 23 disallowance and drafting the disclosure is a separate step.

This free tool, and where it stops

This free tool checks

  • MSME-flagged invoices beyond the 45-day payment window, from invoice date to payment date or today
  • Rows where the MSME flag column is blank, flagged as needing a manual check

A full engagement in Lekhya also checks

  • Udyam registration status checked against the actual vendor master, not a self-reported flag
  • The section 23 interest/disallowance computation run against the ledger
  • The MSME disclosure note drafted and linked to the underlying invoices
  • Full-population checks every period, not a one-time scan

One run, one file, four or five rules — versus every procedure a real engagement needs, run continuously against the full population, with every exception linked to its source document.

See it run on a full engagementRead how it works