India·7 min read·16 days ago

Tally Prime 1.25 GSTR-3B Filing Error: Step-by-Step Fix 2026

Fresh B.Com graduate staring at a red error screen at 11 PM before the GSTR-3B deadline? This step-by-step guide walks you through every known Tally Prime 1.25 filing error in the July 2026 window — with exact menu paths, root causes, and fixes.

By the SuperAccountant Editorial Team

Tally Prime 1.25 GSTR-3B Filing Error: Step-by-Step Fix 2026 · tally prime 1.25 gstr-3b filing error fix 2026 — SuperAccountant Journal illustration

You just landed your first accounts-executive role, your senior has handed you the GST login credentials, and Tally Prime 1.25 is throwing an error you have never seen before — two days before the GSTR-3B due date. Welcome to the real B.Com curriculum. This guide gives you the exact fix, step by step, no padding.

Why Tally Prime 1.25 Trips Up Freshers on GSTR-3B

Tally Prime version 1.25 introduced a revised GST data-export engine to align with GSTN's updated JSON schema released via CBIC notification. That is good news for compliance accuracy, but it also means any data entry habit carried over from older Tally ERP 9 or Tally Prime 1.x behaviour will now throw a mismatch error at the point of upload on the GST portal (gstin.gov.in or the official filing interface at gst.gov.in).

The three most common error families freshers hit in the July 2026 filing window are:

  1. JSON upload failure — the exported file is rejected by the GSTN portal with "Invalid JSON structure."
  2. Mismatch in Table 3.1 — outward supply figures in Tally do not match auto-populated data from GSTR-1.
  3. ITC reversal not captured — Section 17(5) of the CGST Act blocked credits are sitting in your books but not being reversed in Table 4(B)(2) of GSTR-3B, triggering a portal validation alert.

Understanding which family your error belongs to is step zero. Every fix flows from that diagnosis.

Step 0 — Confirm Your Tally Prime Version and Release Update

Before troubleshooting, verify you are actually on Tally Prime 1.25 and not an intermediate patch release that may have already addressed the bug.

Menu path: Help → About → Product & License

If the Release field shows anything below Tally Prime Release 1.25, go to Help → Check for Updates and install the latest statutory update. Tally Solutions releases GST-specific statutory patches (separate from the main version) several times a year; missing a patch is the single most common reason freshers get errors their seniors do not.

Restart Tally Prime after any update before retrying the export.

Step 1 — Run the Pre-Export GSTR-3B Reconciliation

This step alone resolves roughly 60 % of filing errors. Do not skip it.

  1. Go to Gateway of Tally → Display More Reports → GST Reports → GSTR-3B.
  2. Set the period to the month you are filing (e.g., June 2026, return due 20 July 2026 for monthly filers under QRMP quarterly category not applicable here).
  3. Press F5: Reconcile (or use the button on the right-hand action panel).
  4. Tally will compare its computed values against the auto-drafted GSTR-3B figures pulled from GSTN. Any cell highlighted in red signals a mismatch you must resolve before exporting.

Common red-cell root causes:

  • A sales invoice was recorded with the wrong Place of Supply, causing CGST/SGST to be computed instead of IGST (or vice versa). Fix in the original voucher: Alter → Voucher → change Place of Supply.
  • A purchase voucher is missing the supplier's GSTIN. Under Sec 16(2)(c) of the CGST Act, ITC eligibility is partly linked to the supplier filing their GSTR-1; a blank GSTIN field prevents Tally from mapping the credit correctly.
  • Advance receipts under RCM (Reverse Charge Mechanism, applicable under Sec 9(3) of the CGST Act) were not tagged. Tally Prime 1.25 now mandates a separate RCM ledger group for these; older voucher entries may not carry that tag.

Step 2 — Fix the JSON Export for GSTN Upload

Once reconciliation is clean, export the GSTR-3B JSON:

GSTR-3B Report → E-Return → Export

Settings to verify in the Export screen:

SettingRequired Value
FormatJSON
Return TypeGSTR-3B
VersionGSTN v3.1 (select from dropdown)
GSTINAuto-populated; verify it matches portal
PeriodCorrect month/year
File PathA local folder with no special characters in the path (avoid paths like C:\Client's Files\)

A folder path containing an apostrophe or ampersand is a silent killer — Tally writes the file correctly but the Windows file system truncates the name, producing a corrupt JSON the portal rejects. Save to C:\GST_Returns\ or similar.

After export, open the JSON in Notepad and do a quick sanity check: search for your GSTIN string to confirm it appears correctly, and check that "ret_period" matches the filing month (e.g., "062026" for June 2026). If either field is blank or malformed, the issue is in your company master: Gateway of Tally → F11: Features → Statutory & Taxation → GST Details.

Step 3 — Resolve the Three Most Frequent Error Codes at the GSTN Portal

After uploading the JSON at gst.gov.in, the portal may still return error codes. Here is what each means and how to fix it in Tally before re-uploading:

Error: "RET191012 — GSTIN not registered for the tax period" Your company's GST registration may be suspended or the return period is outside the registration date. Check registration status at gst.gov.in → Search Taxpayer. If the registration is active, the issue is usually a wrong financial year in Tally's company master.

Error: "RET191023 — Values in Table 3.1 do not match GSTR-1 auto-populated data" The GSTR-1 filed for the same period has different outward supply figures. You cannot change the already-filed GSTR-1 now. In Tally, manually override Table 3.1 figures in the GSTR-3B screen to match GSTR-1 exactly; the difference, if any, can be explained in the next period's amendment. Do NOT leave the 3B unfiled waiting for a GSTR-1 amendment — interest under Sec 50(1) of the CGST Act accrues from the due date.

Error: "RET13001 — Invalid JSON / Schema mismatch" Almost always a Tally version issue. Confirm you are on the latest statutory release (Step 0), then re-export. If the error persists, open the JSON in jsonlint.com — a free validator — and look for the line number flagged. The most common structural fault in Tally Prime 1.25 JSON is a null value in the "itc_elg" object when no ITC was claimed; set all nil ITC fields to 0 instead of null directly in the JSON, then re-upload.

Step 4 — File or Save as Draft on the GST Portal

Once the JSON uploads without error:

  1. Navigate to Services → Returns → Returns Dashboard.
  2. Select the GSTR-3B tile for the relevant period.
  3. Choose Proceed to File and verify the auto-computed tax payable figures.
  4. If there is tax payable, create a challan under Services → Payments → Create Challan and complete payment via net banking or NEFT before submitting. An unfunded challan is the most avoidable last-minute mistake.
  5. Submit using EVC (OTP on registered mobile) or DSC (Director's digital signature) as applicable.

Save the ARN (Acknowledgement Reference Number) and attach it to the client file immediately. Your senior will ask for it.

Quick Pre-Filing Checklist for Fresh Graduates

Use this before every GSTR-3B filing cycle:

  • Tally Prime statutory release updated (Help → About confirms latest patch)
  • All sales and purchase vouchers entered and approved for the period
  • GSTIN present on every purchase voucher where ITC is claimed
  • Place of Supply verified on inter-state invoices (IGST vs CGST+SGST)
  • RCM liability vouchers created and tagged under correct ledger group
  • Sec 17(5) blocked credits (motor vehicles, personal expenses) manually reversed in Table 4(B)(2)
  • GSTR-3B reconciliation run (F5: Reconcile) — zero red cells
  • JSON export path contains no special characters
  • JSON validated at portal — no error codes
  • Tax liability funded via challan before submission
  • ARN saved and filed in client folder

Building the Skill That Gets You Hired

Error-free GSTR-3B filing is not just a compliance task — it is the single most-tested competency in accounting-executive interviews at firms ranging from regional CA offices to mid-market companies like STC India and Lulu Group's India retail entities. Interviewers at Big 4 firms (Deloitte, KPMG, EY, PwC) assessing freshers for indirect-tax associate roles routinely ask candidates to walk through a GST filing workflow.

If you want to benchmark your current GST and Tally knowledge before your next interview, take the SuperAccountant skills quiz — it flags exactly which areas a hiring manager would probe you on, and gives you a personalised study list. Candidates who complete the quiz before applying to roles listed on the platform report feeling significantly more confident in technical rounds.

For structured, mentor-guided practice with real Tally Prime datasets and mock interview scenarios, the SuperAccountant cohort programme runs monthly batches designed specifically for B.Com and M.Com graduates with less than one year of work experience.


Browse current openings curated for new accounting graduates at https://app.superaccountant.in/en/jobs — we list both India and KSA roles, with filters by location and required skills, so you can apply where you actually fit.