How to Match Purchase Invoices for GSTR-2B Reconciliation

Dynamite Docs, 2026-08-13

Build the purchase-side dataset before matching GSTR-2B

GSTR-2B reconciliation starts with two datasets: the downloaded GSTR-2B statement and a complete purchase register supported by vendor documents. Purchase evidence may be spread across digital PDFs, scans, email attachments and phone photos. Put those documents into one consistent table before comparing them with portal data.

Keep the tax period, recipient GSTIN and source file attached to every row. If an invoice is unreadable, duplicated or missing from the collection, record that problem before matching. A tidy result built from an incomplete document set gives the reviewer false confidence.

  • Confirm the GSTIN and tax period on both datasets
  • Record every source invoice, credit note and debit note once
  • Keep missing, duplicate and unreadable documents in the control sheet

Extract the fields that support a defensible match

Capture supplier GSTIN, document type, invoice number, invoice date, taxable value, CGST, SGST, IGST and cess when present. Keep credit notes and amendments distinct from ordinary invoices. Preserve the printed invoice number and add a separate normalized helper value for comparisons.

Use the strongest identifiers first. Supplier GSTIN plus invoice number and date is more useful than amount alone. Compare taxable value and each tax component after the identity fields agree. An amount-only match should remain a suggestion because different invoices can share the same value.

Classify exceptions before asking the reviewer to decide

Separate exact matches from partial and missing matches. Useful exception labels include missing in GSTR-2B, missing in books, invoice number mismatch, date mismatch, taxable value mismatch, tax mismatch, duplicate, credit note, and period difference. Each label should lead to a specific check rather than a generic red cell.

Assign each open item to the accounts team, vendor follow-up, or tax reviewer. Record the evidence and final decision without changing the source values. The reconciliation file should explain the difference even when the decision is to leave it open for a later period.

Keep invoice matching separate from the ITC decision

Dynamite Docs can extract purchase invoices into structured rows for the matching sheet. A match shows that selected document fields agree. It does not by itself establish input tax credit eligibility, filing treatment, or the action required for an unmatched item.

Use current GST Portal guidance for the tax period and have the taxpayer or qualified tax adviser review eligibility, reversals and return treatment. Preserve the GSTR-2B download, source documents, matching rules, exceptions and reviewer decisions as one period file.

Build the matching sheet before reviewing exceptions

A useful GSTR-2B reconciliation starts with one normalized row per invoice or debit note. Keep supplier GSTIN, document number, document date, taxable value, tax components, place of supply, and source file reference in separate columns. Normalize spaces, punctuation, and date formats in helper columns, but retain the values exactly as they appear on the source document for review.

Match in layers. Start with the strongest key available, usually supplier GSTIN plus invoice number and date. Then compare taxable value and CGST, SGST, IGST, and cess. A near match should remain an exception rather than being forced into the matched set. Credit notes, amended documents, duplicate uploads, and invoices recorded in a different tax period need their own statuses.

The working paper should explain why each row is open. Labels such as missing in books, missing in 2B, value mismatch, tax mismatch, duplicate, and period difference give the reviewer a real queue. A single red cell does not tell the accounts team what to do next.

Use a close checklist before handing the file to your tax reviewer

Reconcile totals only after row-level matching. Compare the number and value of matched documents, unmatched book entries, unmatched GSTR-2B entries, credit notes, and duplicates. Recalculate the tax columns instead of trusting formatted totals copied from a PDF. Keep a control total for the imported source and another for the final review table so dropped rows are visible.

Document preparation does not decide whether input tax credit is eligible. The GST Portal advises taxpayers to review system-generated information and assess the credit they report. Keep the source invoice, the GSTR-2B row, the matching reason, and the reviewer decision together. That makes the spreadsheet useful for month-end review without presenting an extraction result as a filing decision.

  • Confirm the tax period and GSTIN before comparing files.
  • Check invoice counts as well as taxable value and tax totals.
  • Separate exact matches, suggested matches, and unmatched rows.
  • Record the reviewer, decision date, and reason for every manual override.

Frequently asked questions about GSTR-2B reconciliation

  • Should invoice numbers be changed before matching? Keep the original value, then create a normalized helper value for comparison so the evidence is not lost.
  • Can a value-only match be accepted automatically? It is risky because two invoices can share the same amount. Use supplier identity and document references, then review any partial match.
  • Does matched data prove ITC eligibility? No. Matching prepares evidence. Eligibility and filing treatment require the taxpayer or qualified tax reviewer to apply current rules.

Test the matching rules on one tax period

Use one closed period with known exceptions. Preserve the source invoice values, compare document counts and tax totals, and ask the responsible tax reviewer to inspect exact matches, suggested matches, and unmatched rows. Reuse the rules only when the working paper explains every exception without hiding the original evidence.

Sources checked for this note

  1. GST Portal, Form GSTR-2B frequently asked questions

Related workflow: GSTR-2B reconciliation document processing.

Keep reading

Try it yourself. Upload a PDF, scan, or image and let Dynamite Docs infer the schema.

Loading Dynamite Docs… This page is taking longer than expected. Reload page.