How to Check E-Invoice Status in Bulk

Before you shop for a bulk e-invoice status tool, separate the two jobs hiding under that phrase. Screening a list of counterparties to find out which ones are enabled for e-invoicing is a bulk GSTIN verification job, cheap and easy to run over a supplier master. Checking IRN status for a list of your own invoices is an operation on your own registration, performed against an Invoice Registration Portal directly or through a GSP.

SMEs almost always need the first and often think they are being quoted for it when they are being quoted for the second — which is why the prices look wrong. This page sizes both.

Which bulk check do you actually need?

If your worry is "am I paying suppliers against non-compliant invoices", you want the left column. If your worry is "did all of yesterday's sales invoices actually register", you want the right column — and the architecture for that is in e-invoice status and IRN tracking.

Bulk screening suppliers by e-invoicing status

This is a straightforward bulk verification run with one extra column read out of the response. The steps:

1. Export supplier GSTINs from your accounting system — Tally, Zoho Books, Busy or a spreadsheet. One column is enough.
2. Deduplicate and format-check locally. Free, and it removes the blanks, the typos and the PAN numbers that always appear in a real export. See GSTIN format explained.
3. Run the batch through the verification API, reading three fields from each response: status, einvoiceStatus and filing_data.
4. Sort into three buckets — compliant, needs a conversation, and blocked — using the rules in the next section.
5. Act on the middle bucket before the next payment run, which is the only step that turns a report into a control.

The second row is worth dwelling on, because it is where teams create work for themselves: a supplier below the e-invoicing threshold is not doing anything wrong by sending a plain invoice, and chasing them for an IRN wastes everyone's time. The screen exists to find row one suppliers who are behaving like row two suppliers.

Bulk checking IRNs for your own invoices

For your own outbound invoices, "bulk status check" should mostly be unnecessary — if your billing system records the IRN, acknowledgement number and acknowledgement date at generation time, you already know the status of every document without asking anyone.

The batch job that is worth running is a gap check rather than a status fetch: every document issued in the period, minus every document with a confirmed IRN stored, equals the set that needs resolving. Resolve those individually with a Get IRN by Document Details call. That is a handful of calls a day rather than one per invoice, and it catches the real failure — the timeout where the IRP registered the invoice but your system never recorded it.

What the two checks cost an SME

Set those against a single disputed input tax credit claim and the screening pays for itself many times over. Full pricing detail is in GST API pricing explained.

A monthly workflow that fits in one job

• Week 1, after the previous month closes: export supplier GSTINs touched by any invoice in the period. This is a much shorter list than the full master and is the one that matters.
• Deduplicate, format-check, verify. Ten minutes of runtime for most SMEs.
• Report three lines only: cancelled or suspended suppliers, suppliers enabled for e-invoicing whose documents this month had no IRN, and new suppliers seen for the first time.
• Route the exceptions to whoever owns the supplier relationship, with a deadline before the next payment run.
• Quarterly, run the full master to catch changes among suppliers you did not transact with this month.

If you want this daily rather than monthly, the same machinery scales — see automated daily vendor GSTIN monitoring. For the spreadsheet-first version, see bulk verification from a CSV or GST verification in Google Sheets.

Where bulk e-invoice checks go wrong

1. Chasing IRNs from suppliers below the threshold. Read einvoiceStatus before you send the email.
2. Screening the full master when only the transacting subset matters. More cost, more noise, same signal.
3. Producing a report nobody acts on. A screen that does not gate a payment run is a spreadsheet, not a control.
4. Ignoring the status field. A cancelled registration is a bigger problem than a missing IRN, and it comes back in the same response.
5. Running it right before the filing deadline, when the upstream systems are at their busiest and everything is slower.

Frequently asked questions