How to Reconcile GSTR-2B with Tally Data (Step-by-Step, No VLOOKUP)

Reading time: 9 min

Quick summary: Reconciling GSTR-2B with your Tally purchase register means matching every purchase invoice recorded in Tally against the invoices your suppliers have actually filed on the GST portal — checking GSTIN, invoice number, invoice date, and tax amounts line by line. Done manually, it usually means exporting two files and running VLOOKUP or INDEX-MATCH formulas between them. This guide walks through the full manual process, explains exactly where VLOOKUP breaks down, and shows what a faster, error-free workflow looks like.

Every month, thousands of Chartered Accountants sit down with two spreadsheets — a Tally purchase register export and a GSTR-2B JSON-to-Excel conversion — and try to make them agree. On paper it sounds like a simple lookup problem. In practice, it's one of the most error-prone parts of the GST filing cycle, and it's the single biggest reason firms end up under-claiming or over-claiming Input Tax Credit (ITC).

This guide breaks the process down step by step, exactly as a practicing CA would do it in Tally Prime — including the specific places where VLOOKUP formulas silently fail and you don't find out until a DRC-01C notice lands in your inbox.

<a name="why-it-matters"></a>

Why This Reconciliation Matters

Under Rule 36(4) and the current GSTN enforcement framework, ITC claimed in GSTR-3B is validated against GSTR-2B. Since FY2025, the GST department has significantly increased automated DRC-01C notices — issued the moment your claimed ITC exceeds what's reflected in GSTR-2B beyond the permitted threshold. Once issued, you have 7 days to explain the mismatch or pay the differential with Section 50 interest.

That means this isn't a bookkeeping formality — it's a compliance control. Get it wrong and your client either loses eligible credit (money left on the table) or claims ineligible credit (a notice waiting to happen).

<a name="prerequisites"></a>

What You'll Need Before You Start

• GSTR-2B JSON file or Excel download for the relevant return period, from the GST portal or your GSP (Sandbox.co.in, MasterGST, etc.)

• Purchase Register export from Tally Prime — Gateway of Tally → Display More Reports → Statutory Reports → GST Reports → GSTR-2, or a raw Day Book export filtered to purchase vouchers

• A common reference key on both sides: Supplier GSTIN + Invoice Number + Invoice Date

• Roughly 30–90 minutes per client GSTIN if done manually (more if the client has 500+ monthly purchase entries)

<a name="step-1"></a>

Step 1: Download GSTR-2B from the GST Portal

1. Log in to the GST portal → Returns Dashboard → select the return period → GSTR-2B → Download.

2. Choose Excel (not just JSON) so you get a readable table. If your GSP is integrated, this can be pulled via API instead of the portal UI.

3. Note that GSTR-2B is generated on the 14th of the following month and is static for that period — it won't update mid-cycle even if a supplier files late (that invoice will appear in the next period's GSTR-2B instead).

<a name="step-2"></a>

Step 2: Export the Purchase Register from Tally

1. In Tally Prime, go to Gateway of Tally → Display More Reports → Account Books → Purchase Register.

2. Set the period to match your GSTR-2B return period exactly (not the invoice date — the filing period, which can differ for late-received invoices).

3. Export as Excel (Alt+E → Excel format).

4. If you're on Tally's native GST reports, cross-check against GSTR-2 (Reconciliation) inside Tally itself first — it gives you a partial head start, but it only compares against what's already been entered, not against the live GSTR-2B feed.

<a name="step-3"></a>

Step 3: Standardize Both Files

This is the step most people skip — and the one that causes 80% of "false mismatches." Before matching anything:

• Strip extra spaces from GSTIN and invoice number fields (TRIM() in Excel)

• Convert both invoice number columns to the same case and remove leading zeros/special characters inconsistently applied by different accounting software

• Standardize date formats — Tally often exports DD-MM-YYYY while the GST portal Excel uses YYYY-MM-DD

• Separate combined "Taxable Value + Tax" columns into individual IGST/CGST/SGST columns if Tally has exported them merged

<a name="step-4"></a>

Step 4: Match on GSTIN + Invoice Number + Period

The technically correct match key is a composite of three fields: Supplier GSTIN, Invoice Number, and Tax Period. Using invoice number alone is not reliable — many small suppliers reuse invoice number series across financial years.

In Excel, this typically means:

=IFERROR(VLOOKUP(A2&B2, 'GSTR2B'!$A:$A&'GSTR2B'!$B:$B, 1, 0), "NOT FOUND")

...run as an array formula, or more commonly done today with INDEX/MATCH combined with a helper "concat key" column on both sheets. Either way, you now have a binary "found / not found" result — which only answers half the question.

<a name="step-5"></a>

Step 5: Reconcile Tax Values (IGST vs CGST/SGST)

Finding a matching invoice number doesn't mean the invoice is actually matched. You still need to compare:

• Taxable value in Tally vs GSTR-2B

• IGST vs the sum of CGST+SGST (place-of-supply errors are extremely common here)

• Total tax amount, with a tolerance band (most firms use ±₹1 for rounding, not more)

Any variance beyond your tolerance gets flagged as a "Diff Found" record, separate from a full match.

<a name="step-6"></a>

Step 6: Bucket the Results Into 4 Categories

Every invoice should land in exactly one bucket:

<a name="step-7"></a>

Step 7: Prepare GSTR-3B Table 4 Entries

Once buckets are finalized, your eligible ITC for Table 4(A) is the sum of Matched + Diff-Found-and-resolved entries. Missing-in-2B invoices are held back to the period they actually appear in GSTR-2B, to avoid triggering a DRC-01C for over-claiming. Document your workpaper — auditors and GST officers both expect a clear audit trail showing why each figure was included or excluded.

<a name="why-vlookup-breaks"></a>

Why VLOOKUP Breaks (Every Single Time)

If you've done this even twice, you already know the pain points. Here's why they happen:

• Trailing spaces and invisible characters in GSTIN/invoice number fields — VLOOKUP treats "Apex Steel" and "Apex Steel " as different values

• Inconsistent invoice number formatting — INV-001 vs INV-0001 vs INV/001/25-26

• Merged or split tax columns — Tally exports can combine CGST+SGST into one field depending on voucher configuration

• Cross-period invoices — a supplier files late, and the invoice shows up in next month's GSTR-2B, not this month's, breaking your straight VLOOKUP entirely

• Duplicate invoice numbers across different suppliers or financial years, which VLOOKUP will happily match incorrectly to the first result it finds

• File size — beyond roughly 5,000–10,000 rows, most Excel files with heavy VLOOKUP/array formulas start to lag or crash, especially on shared/network drives

None of these are Excel's fault exactly — they're data-quality problems that a rigid lookup formula simply isn't built to handle. Fuzzy matching (comparing "Apex Steel Industries" to "Apex Steel Ltd" as the same vendor) requires logic VLOOKUP cannot do at all.

<a name="comparison"></a>

Manual Excel vs Automated Reconciliation

For a single client with under a few hundred monthly invoices, a careful manual process works fine. Once a firm is managing 15–20+ client GSTINs with 30-day filing cycles, the manual process is usually what's eating the "120 billable hours a year" figure that shows up in most CA-firm time studies — which is the exact gap tools like TaxSolver's GSTR-2B reconciliation engine are built to close, by connecting directly to your GSP and ingesting Tally exports without manual column mapping.

About the Author

Abhishek leads product at TaxSolver and has spent over 6 years building GST compliance workflows for Chartered Accountant firms across India, working directly with CAs managing multi-GSTIN portfolios.

Reviewed by CA Priyanka Shah, a practicing Chartered Accountant specializing in indirect tax compliance.

This article reflects the compliance framework and thresholds in effect as of August 2026. GST rules, DRC-01C thresholds, and CBIC notifications are subject to change — always verify current rules against the latest CBIC circulars or consult a qualified tax professional before filing.

Tired of doing this by hand every month? Try TaxSolver's GSTR-2B reconciliation engine free for 14 days — it connects directly to your GSP, ingests Tally exports with zero manual column mapping, and auto-drafts supplier follow-ups for anything missing.