GSTR-2B Reconciliation: Match Purchase Invoices Without Retyping Them
Dynamite Docs Team — 2026-08-13
Reconciliation compares two lists; one of them is PDFs
Input tax credit reconciliation starts with two lists: the GSTR-2B statement, which the GST portal auto-drafts from what your suppliers report, and your own purchase invoices and receipts. Matching them means comparing supplier GSTINs, invoice numbers and dates, taxable values, and the CGST/SGST/IGST split across both.
The GSTR-2B side is structured data. The purchase side is a stack of PDFs, and the comparison still starts with retyping the numbers out of them. The mismatches are where the work hides: an invoice in your records but not in the statement, a GSTIN that does not match, a tax amount that does not tie.
- GSTR-2B is auto-drafted from what your suppliers report
- The purchase side of the match is almost always manual
- Mismatches have to be traced back to the original document
Purchase documents to comparable rows
Dynamite Docs extracts supplier GSTIN, invoice number and date, HSN/SAC, taxable value, CGST, SGST, IGST, and totals from purchase invoices and receipts into confidence-scored rows. Clean digital PDFs, including most billing-software exports, parse deterministically for free, identical results every run. Vendor scans and photos are read by the vision model you pick.
The tax split is where the reconciliation actually bites. CGST and SGST apply to intra-state supplies and IGST to inter-state supplies, and a row that should have carried IGST but was keyed as state tax surfaces as a mismatch. Because the split is extracted as separate fields and checked against the total, the review shrinks to the handful of rows that genuinely do not tie.
- Supplier GSTIN, invoice number and date, value, and split come out as separate fields
- The CGST/SGST versus IGST regime is visible on every row
- Corrections per vendor are remembered, so repeat suppliers extract cleanly
The match runs on rows; the decisions stay with your team
Export the purchase side to Excel, CSV, or JSON, or push it to Google Sheets, so the comparison against your GSTR-2B data runs on rows you can filter, sort, and reconcile. Batch processing turns a month of purchase documents into one review session.
Whether a credit is claimable, how a mismatch should be resolved, and when to follow up with a supplier are decisions for your CA and your team, and the rules change; consult the GST portal and your tax advisor for current requirements. Dynamite Docs is a document-processing and data-preparation layer. What extraction removes is the keystrokes, not the judgment.
Keep purchase data off models you didn’t choose
Purchase documents are not content for a model you did not approve. Bring your own keys on every plan and pay your provider’s rate with zero markup; on Pro and Ultra that BYOK processing is unlimited and never counts against your monthly allowance. Documents are encrypted at rest, never used to train foundation models, and sensitive processing can be locked to no-training providers or run fully local with Ollama.
Related workflow: GSTR-2B reconciliation document processing.
Try it yourself. Upload a PDF, scan, or image and let Dynamite Docs infer the schema.