Tally Prime & Excel Workflows

How to Reconcile GSTR-2B with Tally Prime Purchase Register in Excel (Without Broken Headers)

By gstr2bmatch.in Editorial Team • Updated: September 2026 • 7 min read

Direct Answer: To reconcile GSTR-2B with Tally Prime in Excel without corrupted headers, navigate to Display More Reports > Statutory Reports > GST Reports > GSTR-2B (or Purchase Register), press Ctrl + E, configure Export format to Excel (Spreadsheet), and set "Export with Merged Cells" to NO while toggling "Detailed / Columnar View (F8)" to ensure GSTIN, Voucher No, and Tax amounts populate on single rows. Then compare your cleaned register with the government portal's GSTR-2B Excel directly in your browser without uploading proprietary purchase ledgers to remote servers.

Prefer a spreadsheet? Our GSTR-2B reconciliation in Excel guide includes a free template. This page is part of our GSTR-2B reconciliation in Tally Prime series.

If you have ever tried running a VLOOKUP or uploading a raw Tally Prime purchase export into a generic spreadsheet macro, you know the frustration: row 1 to 5 contain company names and blank headers, supplier GSTINs sit two rows below the voucher number, and merged total cells break standard sorting routines.

This breakdown explains the exact keyboard shortcuts in Tally Prime 3.x/4.x to extract a clean, single-row purchase dataset, how to resolve invoice formatting mismatches, and how to verify eligible Input Tax Credit (ITC) before filing GSTR-3B.

Why Standard Tally Prime Excel Exports Break Reconciliation

By default, Tally Prime formats spreadsheet exports for visual printing rather than relational database matching. When you press standard Export on a columnar register, Tally injects:

  • Multi-line Title Headers: Rows 1 through 6 carry metadata ("Company Name", "Address", "Purchase Register from 01-Apr to 30-Apr") which prevents automated tools from identifying column headers.
  • Merged Cells: Voucher dates and supplier ledgers span multiple merged columns, causing lookup formulas to return #N/A or copy values across unrelated rows.
  • Original Invoice Number vs. Tally Voucher Number: Tally maintains an internal "Voucher No." (e.g., PUR/042) while your supplier billed you under "Supplier Invoice No." (e.g., INV-2026-9812). If your columnar view pulls the internal voucher number instead of the supplier reference, your GSTR-2B matching rate drops to zero.

Step-by-Step: Exporting a Clean Columnar Purchase Register from Tally Prime

Follow these exact configuration steps inside Tally Prime to obtain a flat tabular file:

Step 1: Open the Columnar Purchase Register

Go to Gateway of Tally > Display More Reports (D) > Account Books (A) > Purchase Register (P). Select the required tax month and press Enter.

Press F8 (Columnar). Configure the display options:

  • Party's GSTIN/UIN: Set to Yes.
  • Supplier Invoice No. & Date: Set to Yes (Important: do not rely only on Tally Voucher Number).
  • Quantity / Rate Details: Set to No (Keeps register lightweight).
  • Tax Ledgers (CGST, SGST, IGST): Set to Yes (Separates tax components into distinct columns).

Step 2: Apply Clean Export Configurations (Ctrl + E)

Press Ctrl + E to open the Export dialog. Click C (Configure) and set:

  • File Format: Excel (Spreadsheet).
  • Show Company Name & Period: Set to No (if available in your Tally release) or prepare to delete the top 4 title rows.
  • Export with Merged Cells: NO.

Press Ctrl + A to save settings, then click E (Send) to generate the Excel workbook.

Field Mapping: Tally Columnar Register vs. GSTR-2B B2B Table

Before running reconciliation, ensure your exported columns align logically with the official GSTR-2B schema downloaded from gst.gov.in:

Data Point Tally Prime Column Header Official GSTR-2B Table (B2B) Matching Rule & Common Trap
Supplier GSTIN GSTIN/UIN GSTIN of Supplier Exact 15-character alphanumeric match. Watch for trailing spaces.
Invoice Number Supplier Invoice No Invoice number Strip prefixes/slashes. Suppliers often log 0045 while Tally logs 45.
Invoice Date Supplier Invoice Date Invoice date Standardize DD-MM-YYYY format. Watch for month/day inversions.
Taxable Value Gross Total / Purchase Value Taxable value (₹) Ensure discount deductions match post-tax vs pre-tax values.
IGST / CGST / SGST Integrated Tax, Central Tax, State Tax Integrated Tax (₹), Central Tax (₹), State/UT Tax (₹) Round-off differences (±₹1 to ₹2) are routine and must be tolerated.

Worked Example: Catching Missing ITC in Real Life

Consider an engineering workshop in Vadodara with 450 vendor vouchers for the month:

  • Tally Purchase Books ITC: ₹18,40,500 across 450 bills.
  • GSTR-2B Auto-Populated ITC: ₹16,95,000 across 418 bills.
  • Gross Difference: ₹1,45,500 missing credit.

Running a manual cross-check revealed 12 invoices where the supplier had billed under INV/24-25/089 but Tally had recorded it as 089. A rigid formula tagged all 12 as "Missing in 2B". Once normalized, ₹95,000 was successfully matched. The remaining ₹50,500 belonged to two vendors who had filed late in GSTR-1, landing the invoices in IMS Pending.

Why Client-Side In-Browser Reconciliation Beats Cloud Uploads

Many tax consultants paste proprietary Tally purchase ledgers into cloud-based reconciliation platforms. This creates substantial compliance and confidentiality risks:

  • Commercial Sensitivity: Purchase registers disclose vendor names, negotiated raw material pricing, payment terms, and turnover metrics.
  • Data Privacy: Uploading accounting books to third-party databases exposes client information to data retention and scraping policies.

With gstr2bmatch.in, reconciliation runs 100% locally in your browser memory via WebAssembly and SheetJS. Your vendor registers, GST numbers, and tax figures never touch an external server or API.

Common Tally-to-2B Reconciliation Errors and Fixes

  1. Voucher Date vs. Invoice Date: If your accountant logs the date goods arrived (e.g., 2nd May) rather than the invoice date (28th April), date-based formulas will misalign the accounting periods. Always match on the supplier's original billing date.
  2. Branch Transfers (Same PAN): Ensure internal branch invoices between distinct GSTINs are categorized under separate accounts so inter-unit stock transfers don't distort external vendor reconciliations.
  3. Multi-Rate Vouchers: If a single vendor invoice contains both 12% and 18% items, Tally generates multiple lines or combined tax columns. Consolidate total taxable and tax values per invoice before matching against GSTR-2B B2B rows.

Match Your Cleaned Tally Register in 30 Seconds

Drop your exported Tally Excel file and government GSTR-2B sheet directly into our private matching tool. No sign-up, no software installation, and zero data leaves your browser.

Start Free Reconciliation →

Frequently Asked Questions

Can I directly upload Tally Prime GSTR-2B JSON to GSTR2BMatch?

You can export your purchase register from Tally as an Excel (.xlsx) file and download your official GSTR-2B Excel directly from the GST Portal. Both files can be dropped into the tool without altering column structures.

What should I do if Tally shows an invoice that is missing from GSTR-2B?

Check the Invoice Management System (IMS) on the GST Portal first. If the supplier filed their GSTR-1 after the 11th/13th cutoff or if the invoice is sitting in IMS Pending, it will not appear in the current 2B. If not filed at all, escalate to the vendor for an amendment in GSTR-1A.

Does GSTR2BMatch store our Tally purchase data?

No. The matching engine operates entirely within your local browser runtime. Open your browser Developer Tools (Network tab) during reconciliation to verify that zero bytes of ledger data are transmitted externally.

Related guides