Reconciling GSTR-3B Tax Liability Breakup in Tally Prime

The Goods and Services Tax Network (GSTN) has introduced a mandatory Tax Liability Breakup Table inside Form GSTR-3B return preparation dashboard. This feature requires taxpayers to declare the specific tax periods to which their paid liabilities belong.

While this update ensures that interest calculations under Rule 88B are correct, it has introduced significant reconciliation friction for businesses using Tally Prime. Often, the generated GSTR-3B JSON files throw error logs upon upload, indicating mismatches between Tally's internal indexes and the portal's auto-populated tables. This detailed static guide provides a step-by-step tutorial to resolve these breakup discrepancies.

1. The Source of the Breakup Mismatch

A tax liability breakup discrepancy occurs when the document dates of sales or purchase returns recorded in your Tally database do not align with the tax periods in which the tax is actually declared.

For example, if you issue a Credit Note in April but only record it in Tally during your May reconciliation, Tally will include this credit note in the May GSTR-3B return. If you do not manually adjust the GST Details statutory flags on the transaction voucher, Tally will attempt to export the credit note as a May liability reduction. However, the GST portal expects this to be mapped to the original April tax period, causing a JSON validation rejection.

2. Handling E-Commerce Operators under Section 9(5)

Many businesses selling goods or services through e-commerce operators (such as Amazon, Flipkart, Swiggy, or Zomato) fail to reconcile **Table 3.1.1** of their GSTR-3B.

Under Section 9(5) of the CGST Act, e-commerce operators are liable to pay tax on specific services. In Tally Prime, these sales must be recorded using the tax class *'Sales Liable to E-commerce Operator'*. If the sales are entered as regular taxable sales, Tally will export them into Table 3.1(a) instead of Table 3.1.1, leading to severe discrepancies when matching with your GSTR-1 filings.

3. Rule 88C System Flags: GSTR-1 vs. GSTR-3B Differences

Under **Rule 88C of the CGST Rules**, if the tax liability declared in your GSTR-1 exceeds the tax paid in GSTR-3B by a specified percentage or amount (currently 20% or ₹25,000), the portal generates an automated system notice in **Form GST DRC-01B**.

Taxpayers must either pay the differential tax along with interest or explain the reasons for the mismatch within 7 days. If a taxpayer fails to respond, the portal blocks the generation of their subsequent GSTR-1 return. Correcting tax breakup allocations in Tally Prime prevents these DRC-01B blocks.

4. Finding and Fixing 'Uncertain Transactions' in Tally Prime

Before exporting your GSTR-3B return, you must clean up your transaction list. Follow these steps:

1. Go to Gateway of Tally > Display More Reports > Statutory Reports > GST Reports > GSTR-3B.
2. Scroll to the top section and check the count of **Uncertain Transactions (Correction Needed)**. If this count is greater than zero, your JSON export will contain structural errors.
3. Press Enter on the line to see the detailed list of errors. Look for exceptions marked with:
   • Information required for tax calculation is missing.
   • Mismatched tax rate assigned to item master.
   • GST registration details of the party are incomplete.
   • UQC (Unit Quantity Code) mismatch.
4. Open each transaction, press **Alt + W (GST Details)**, and ensure the state, tax rates, and transaction nature are defined. Re-save the voucher.

5. Reconciling Credit and Debit Notes (Table 4.B & 4.D)

When credit or debit notes are issued, they often cross tax periods. In Tally Prime, you must link each credit note to the original invoice using the *'Original Invoice Number'* and *'Original Invoice Date'* fields.

Failing to map these relationships prevents Tally from generating a clean GSTR-3B Table 4.B ITC reversal list, causing errors during the upload to the GST Portal.

6. Mapping Previous Period Liabilities Discharged in Current Month

If you are paying outstanding taxes from previous periods (e.g. discharging an unrecorded March sale in your May return), you must specify this breakup details inside Tally Prime:

1. While in the GSTR-3B report screen, click on **F5: Land/Liability Details** (or press Alt + L).
2. Navigate to the section for **Tax Liability Breakup**.
3. Select the specific months to which the delayed tax payments relate (e.g. CGST and SGST amounts belonging to March 2026).
4. Ensure these values match your GSTR-1 Table 12 HSN summaries for those periods, allowing Tally to generate a clean, validated JSON export.

7. GST Auditor Reconciliations (GSTR-9C Table 5)

Under **Form GSTR-9C (Reconciliation Statement)**, GST auditors must certify and reconcile any differences between the turnovers declared in your audited financial statements and the turnovers reported in GSTR-9.

Table 5 of GSTR-9C highlights these discrepancies. By aligning your Tally Prime previous period adjustments with the tax liability breakup fields, you eliminate audit exceptions in Table 5, ensuring smooth tax assessments.

8. Reconciling Consolidated vs. Multi-GSTIN Turnovers

For businesses operating across multiple states, consolidating tax liability breakup tables is a major compliance hurdle. If you run multiple GSTIN branches mapped to a single Tally Prime corporate license, you must split sales journals and allocate turnovers state-wise.

If your billing software does not tag state codes correctly in transaction metadata, GSTR-3B exports will merge state tax liabilities, triggering validation failures during the upload process. Establishing separate state-specific duties ledger hierarchies (such as creating separate child ledgers for Maharashtra CGST and Gujarat CGST under Duties & Taxes) in your Chart of Accounts resolves this consolidation issue, keeping your multi-state branch reporting perfectly auditable.

9. Manual vs. Automated Reconciliations: The Audit Trial

Manually verifying hundreds of tax rate percentages and document dates is prone to errors, leading to audit warnings. To maintain clean books, audit departments recommend using automated validation connectors.

With automation, your system can check party GSTINs, calculate tax rates based on HSN directories, and verify state-code prefixes before vouchers are generated, keeping your database clean and error-free.