Many Indian businesses and accounting firms continue to operate on Tally.ERP 9. While the software handles day to day billing and bookkeeping reliably, it was developed before the Goods and Services Tax Network introduced auto-generated GSTR-2B statements. When the 14th of the month arrives, accountants using legacy Tally face a manual bottleneck: GSTR-2B arrives as an Excel or JSON download from the GST portal, but Tally ERP 9 provides no direct import button for it.
Why Tally ERP 9 cannot import GSTR-2B JSON directly
Under Section 16(2)(aa) of the CGST Act, input tax credit can only be claimed if the supplier has furnished invoice details in Form GSTR-1 and those details are communicated to the recipient in Form GSTR-2B. When the government introduced this requirement alongside Notification No. 40/2021-Central Tax, the portal began generating static monthly GSTR-2B statements on the 14th of each month.
Tally Solutions incorporated native GSTR-2B JSON import and reconciliation only in TallyPrime, particularly Release 3.0 and later versions. Tally.ERP 9 (including Release 6.6.3) was built around the older GSTR-2 return architecture that was suspended early in the GST regime. Consequently, Tally ERP 9 lacks the schema parsers required to open modern GSTR-2B JSON files. If you attempt to load a GSTR-2B JSON file into Tally ERP 9, the program does not recognize the file structure. Businesses on legacy Tally must therefore export their book data and perform the comparison externally.
Common mistake: Attempting to edit Tally.ERP 9 configuration files to force JSON imports. Tally ERP 9 cannot parse GSTR-2B JSON without third-party custom TDL add-ons, which often fail when GSTN updates its return schema. Exporting clean Excel data is faster and safer.
Step 1: export the purchase register from Tally ERP 9
To prepare your books for matching, export a clean purchase register containing all required GST fields. Follow these steps in Tally ERP 9:
- From the Gateway of Tally, press D (Display), then A (Account Books), and select Purchase Register.
- Select the relevant month (for example, 1 September 2026 to 30 September 2026) and press Enter to view the voucher list.
- Press F12 (Configure) to display detailed invoice columns. Set the following options to Yes:
- Show Supplier GSTIN: Yes
- Show Voucher Number: Yes
- Show Supplier Invoice No: Yes
- Show Taxable Value: Yes
- Show Separate Tax Values (CGST, SGST, IGST): Yes
- Press Alt + E to open the Export screen.
- Set Format to Excel (Spreadsheet), choose your destination folder, and name the file (for example, Purchase_Register_Sep2026.xlsx).
- Accept the screen to export the file.
Alternatively, accountants who maintain disciplined tax classifications can navigate to Gateway of Tally → Display → Statutory Reports → GST → GSTR-2. Before exporting from this screen, check the top row for Incomplete/Mismatch in Information. If any vouchers appear under Uncertain Transactions, resolve them first so that all valid inward invoices appear in the B2B Invoices table.
Three common formatting pitfalls in Tally ERP 9 exports
Raw files exported from Tally ERP 9 frequently create false mismatches when compared against portal data. Watch out for these three issues:
- Voucher number versus supplier bill number: Tally ERP 9 stores two distinct document numbers: the internal serial voucher number (e.g. 104) and the actual vendor bill number (e.g. INV/26/890). If your export maps the internal voucher number instead of the vendor invoice number, your matching tool will report every single invoice as missing.
- Multi-item row splitting: When an invoice includes items with different GST rates, Tally ERP 9 exports a separate row for each inventory item or ledger line. If matched directly, standard spreadsheet lookup formulas read only the first row and miss the remaining tax amounts.
- Punctuation differences: Suppliers often format invoice numbers with dashes while your data entry operator entered slashes, such as AB-101 versus AB/101. In accordance with Rule 46(b) of the CGST Rules, invoice numbers can contain alphabets, numerals, hyphens, and slashes. Punctuation variations cause exact match formulas to fail.
How to reconcile Tally ERP 9 data with GSTR-2B
Once you download your official GSTR-2B statement from the GST portal in Excel or JSON format, you have two practical methods to complete your reconciliation:
Method A: manual spreadsheet reconciliation
If you prefer using spreadsheets, open both the Tally purchase register and the GSTR-2B Excel file. Create a helper column combining the supplier GSTIN and cleaned invoice number (using SUBSTITUTE to remove slashes and hyphens). Then apply XLOOKUP or INDEX and MATCH to pull tax amounts from GSTR-2B into your purchase register. To review formula structures and download a pre-built sheet, see our guide on GSTR-2B reconciliation in Excel format free download.
Method B: free browser matching with gstr2bmatch.in
Instead of building complex Excel macros, you can upload your exported Tally purchase register and the portal GSTR-2B file directly to gstr2bmatch.in. The tool normalises invoice punctuation automatically, consolidates multi-rate rows, and categorises every invoice into five clear groups: matched, value mismatch, only in books, only in GSTR-2B, and likely IMS Pending. To understand how this compares with newer software versions, read our comparison on Tally GSTR-2B reconciliation vs a free browser tool, as well as our guide for users upgrading to Tally Prime GSTR-2B reconciliation.
Worked example: reconciling a monthly Tally ERP 9 purchase register
Consider Radhika Industrial Supplies, an engineering trading firm in Rajkot operating on Tally.ERP 9. For the month of September 2026, the accountant exports five purchase vouchers totaling ₹1,44,000 in input tax credit. On 14 October 2026, the firm downloads Form GSTR-2B from the portal and performs reconciliation before filing Form GSTR-3B due on 20 October 2026.
| Voucher | Supplier & bill number | Tax in books | Tax in GSTR-2B | Discrepancy type | Status |
|---|---|---|---|---|---|
| Vch 101 | Apex Tools (AT/26/088) | ₹45,000 | ₹45,000 | None | Fully matched |
| Vch 102 | Bharat Steel (BS/0412 in books, BS-0412 in 2B) | ₹18,000 | ₹18,000 | Punctuation difference | Matched (normalised) |
| Vch 103 | Chola Bearings (CB-902) | ₹27,000 | ₹0 | Missing from GSTR-2B | ITC at risk (₹27,000) |
| Vch 104 | Delta Fasteners (DF-551) | ₹18,000 | ₹18,000 | Tax head mismatch (CGST+SGST vs IGST) | Tax head mismatch |
| Vch 105 | Eastern Valves (EV-104) | ₹36,000 | ₹32,400 | Tax value mismatch (gap of ₹3,600) | Partial match (₹3,600 gap) |
| Total | 5 purchase vouchers | ₹1,44,000 | ₹1,13,400 | Net gap: ₹30,600 |
Here is how the numbers break down:
- Total input tax credit recorded in Tally ERP 9: ₹1,44,000 (calculated as 45,000 + 18,000 + 27,000 + 18,000 + 36,000).
- Total credit reflected on the portal in GSTR-2B: ₹1,13,400 (calculated as 45,000 + 18,000 + 0 + 18,000 + 32,400).
- Cleanly matched credit: ₹63,000 (Apex Tools ₹45,000 and Bharat Steel ₹18,000).
- Tax head mismatch: ₹18,000 for Delta Fasteners. In Tally ERP 9, the entry was booked under CGST and SGST (₹9,000 each), but the supplier filed it as inter-state supply with IGST of ₹18,000. This requires correcting the tax ledger in Tally before filing.
- Value mismatch: Eastern Valves reported taxable value of ₹1,80,000 with IGST of ₹32,400 in GSTR-1, whereas the purchase voucher was recorded at ₹2,00,000 with IGST of ₹36,000. Only ₹32,400 is eligible in the current tax period, leaving an unverified difference of ₹3,600.
- Missing invoice: Chola Bearings failed to file GSTR-1 by the due date. The entire ₹27,000 cannot be claimed in GSTR-3B for this period.
- Total credit withheld to avoid mismatch notices: ₹30,600 (comprising ₹27,000 missing plus the ₹3,600 excess value).
Statutory rules under Section 16(2)(aa) and notice risk under Rule 88D
If an accountant claims the entire ₹1,44,000 from Tally ERP 9 in Table 4(A)(5) of Form GSTR-3B, the claim exceeds the GSTR-2B auto-populated amount of ₹1,13,400 by ₹30,600. Under Rule 88D of the CGST Rules and GSTN Form DRC-01C guidelines, any taxpayer whose ITC claim exceeds GSTR-2B by a pre-defined threshold receives an automated notice in Part A of Form GST DRC-01C.
The taxpayer is granted seven days to either deposit the differential amount through Form GST DRC-03 or submit an explanation on the portal. In addition, under Section 50(3) of the CGST Act, wrongly availed and utilized credit attracts interest at 18% per annum. Performing monthly reconciliation between Tally ERP 9 and GSTR-2B ensures that you claim only verified credits in Table 4(A)(5) as guided by GSTN GSTR-3B filing rules.
Notice risk: Filing GSTR-3B based purely on Tally ERP 9 ledger balances without reconciling GSTR-2B frequently leads to DRC-01C notices and 18% annual interest under Section 50(3) on differential amounts.
Summary checklist for Tally ERP 9 users
- Export purchase registers using actual supplier invoice numbers, not internal voucher numbers.
- Group multi-rate invoice items to compare total tax per invoice against GSTR-2B lines.
- Resolve punctuation mismatches in invoice numbers before flagging records as missing.
- Check vendor filing status on missing invoices and follow up before the subsequent tax period.
- Adjust Tally vouchers for place of supply and tax head errors before finalizing GSTR-3B.
Related guides
- What kinds of GSTR-2B reconciliation software exist, and which fits me
- How to use a GSTR-2B reconciliation tool
- Busy ERP to GSTR-2B Reconciliation: step-by-Step Guide
- How accountants can automate GSTR-2B reconciliation
Frequently asked questions
Can Tally ERP 9 directly import GSTR-2B JSON files?
No. Tally ERP 9 does not support native GSTR-2B JSON import. The software was architected around the older GSTR-2 format, whereas direct JSON download and automated reconciliation were introduced only in TallyPrime Release 3.0 and later editions.
How do I export the purchase register from Tally ERP 9 for reconciliation?
Go to Gateway of Tally, select Display, then Account Books, and open Purchase Register. Select the month, press F12 to enable supplier GSTIN and bill reference numbers, and press Alt+E to export the data to an Excel spreadsheet.
Why do invoice numbers exported from Tally ERP 9 fail to match GSTR-2B?
By default, Tally ERP 9 exports the internal voucher number rather than the supplier bill number if column settings are unconfigured. Differences in punctuation like slashes or dashes between your ledger entry and the supplier filing also cause exact text lookups to fail.
Are my accounting files uploaded when using gstr2bmatch.in?
Your GSTR-2B and purchase register files are read in your browser and never uploaded to any server.
Reconcile your Tally ERP 9 purchase register in seconds
Export your monthly register from Tally ERP 9 to Excel, drop it into gstr2bmatch.in alongside your GSTR-2B file, and immediately see matched records, value gaps, and missing invoices with exact rupee figures. Your GSTR-2B and purchase register files are read in your browser and never uploaded to any server.
Last checked: 14 October 2026. Sources: Section 16(2)(aa), CGST Act, CBIC Notification No. 40/2021-Central Tax, GSTN DRC-01C guidance, GSTN GSTR-3B user manual.