Bulk E-Invoice QR Verifier for Purchase Invoices (India)

About the Bulk E-Invoice QR Verifier for Purchase Invoices (India)

Before you claim input tax credit on a month of purchase invoices, check that each one is a real e-invoice. Drop the invoice PDFs, photos or a ZIP of them — as many as you have — and every signed QR code is found, decoded and its IRP signature checked with the public keys the Invoice Registration Portals publish, exactly as the e-invoice QR code verifier does for one invoice.

The result is one sheet for the batch: file, supplier GSTIN, document number and date, value, IRN, IRN date and the signature result. Add your GSTR-2B or your purchase register and every invoice is matched by supplier GSTIN, document number and value, with the problems flagged: no signed QR code, invalid signature, duplicate IRN, value or date differences, invoices missing from GSTR-2B, and invoices issued to another GSTIN. Files are checked one after another on your device with progress, and you can pause and resume; nothing is uploaded.

Without a pass the result is a free preview: the first files of the batch are checked in full and the rest are counted; the workbook, the CSV and the summary unlock with a Premium pass.

Common uses

• An accounts team checking the month’s supplier e-invoices before GSTR-3B.
• A CA testing a client’s purchase invoices during the annual return or an audit.
• Finding duplicate or edited invoices in a vendor’s bundle of PDFs.
• Listing GSTR-2B documents whose invoice copy is missing from the file.

What is checked

• The signature: each QR code is a JSON Web Token signed by an IRP with RS256; the page checks it with the published key for the period, so a changed character shows as invalid signature. A QR code no bundled key verifies shows as no bundled key; NIC sandbox (test) QR codes as test e-invoice.
• The IRN: it must be the SHA-256 hash of the supplier GSTIN, financial year, type and number signed with it.
• Duplicates: the same IRN in two files is one e-invoice counted twice.
• The recipient: with your GSTIN entered, an invoice addressed to another GSTIN is flagged — its credit is not yours.
• The match: with GSTR-2B or a register, by supplier GSTIN and document number (spaces, punctuation and leading zeros ignored), then the value (within ₹1) and the date. GSTR-2B documents with no QR code in the batch are listed too.

Why check purchase invoices

Input tax credit rests on a genuine invoice from a registered supplier that also appears in GSTR-2B. A forged or edited e-invoice, a copy of one invoice billed twice, or an invoice issued to another business all look ordinary on paper; their signed QR codes do not. The check needs no login, no OTP and no upload, so it can run on a client’s whole month in one go. The official alternatives are the IRP’s Verify Signed Invoice (one signed JSON at a time, with a mobile OTP) and the QR code verification app for phones.

Sources

• NIC, Signed QR Code in E-invoicing system and the e-invoice FAQs
• IRP public keys: NIC, GSTN, for every IRP and Cygnet’s IRP
• GSTN, GSTR-2B FAQs: the statement credit is taken from

Limitations

• A signature cannot show whether an IRN was cancelled after it was generated: search the IRN on the IRP portal for invoices that matter.
• Pictures must show the QR code sharply; a faint scan or a tiny QR code may not be readable, and a protected PDF has to be saved without its password first.
• Very large batches take time, as every page of every PDF is searched on this device; pausing and resuming keeps what is done.
• Matching relies on the supplier GSTIN and the document number as signed; a number written differently in the register still needs a look.
• For information, not tax advice.

Privacy

The invoices, the GSTR-2B and the register are read in this browser and are never uploaded or stored; closing the page discards them.