GSTR-2B Reconciliation in TallyPrime: Find ITC Differences Before Filing

Separate matching records from deciding credit eligibility

GSTR-2B reconciliation compares purchase information in the books with the portal statement. Its first purpose is to explain differences, not to turn every matching invoice into an automatic credit claim. The GST portal FAQ says taxpayers must assess eligibility, including circumstances the statement may not identify.

This guide uses fictional records to practise a review workflow in TallyPrime. Keep the accounting correction, supplier follow-up, portal action and tax decision as separate outcomes. A reconciled status supports the investigation; it does not replace the applicable GST rules or the reviewer’s conclusion.

Core concepts to learn

Build a practice scenario

1. Step 1: Select the intended GST registration, return period and a saved version of the downloaded statement.
2. Step 2: Compare individual documents and tax components; assign each difference a specific reason.
3. Step 3: Check supporting invoices before proposing a books correction, supplier follow-up or portal action.
4. Step 4: Reconcile the exception totals and obtain the responsible reviewer’s decision before filing work proceeds.

Use sample, authorised or fictional data. Do not publish credentials, business data, account numbers or customer information in a portfolio. If a task has financial, security or production impact, include a review or approval step before any change.

What good work looks like

Start with a reliable statement and report scope

Record the company, GST registration, return period and download date before comparing values. A business with several registrations can produce misleading results if one registration’s statement is compared with consolidated books. Keep the original downloaded file and an export of the books used in the exercise so another person can reproduce the comparison.

TallyHelp documents both downloading portal data and importing a GSTR-2B file. Its import summary distinguishes processed, imported and failed transactions. Review those counts first: a missing record caused by a failed import is not yet evidence that the supplier omitted it. Use the instructions appropriate to the installed release and supported file format.

Open the GSTR-2B Reconciliation report and inspect the applicable categories, including mismatched records, records only in books, records only on the portal and return-period differences. Start with a small group of known documents. Confirm the report filters before assuming a category contains every unresolved item.

Worked example: reconcile tax differences without hiding them

Use three fictional supplier invoices. Record A has taxable value Rs 20,000 and total tax Rs 3,600 in both sources. Record B has taxable value Rs 10,000 and tax Rs 1,800 in the books, but tax Rs 1,700 in the statement. Record C has taxable value Rs 5,000 and tax Rs 900 in the books and is absent from the selected statement. These numbers are arithmetic examples, not a recommendation of a tax rate for any product.

The books show Rs 6,300 of tax across A, B and C. The statement shows Rs 5,300 for A and B. Explain the Rs 1,000 difference as Rs 100 on B plus Rs 900 on C. Do not simply describe it as “extra ITC” or “credit to reverse”: the reconciliation alone has not established the tax treatment.

For B, inspect the actual supplier invoice, individual tax components and any amendment or credit note. If the source invoice supports Rs 1,800, supplier follow-up may be required. If the books contain a typing error, document the proposed correction. For C, check the selected period, registration and supporting documents before assigning responsibility.

Now add record D, present only on the portal with tax Rs 450. The statement total becomes Rs 5,750, and the net difference falls to Rs 550. There are still three exceptions: B Rs 100, C Rs 900 and D Rs 450 in the opposite direction. Net totals can conceal unresolved records, so retain the gross exception amounts and document counts.

Potential matches need document evidence

Matching amounts do not establish that two entries describe the same supply. Two invoices from the same supplier might both total Rs 11,800. Compare the supplier GSTIN, document type, invoice reference, date, taxable value and tax components together. Preserve meaningful prefixes, suffixes and leading characters when comparing document numbers.

TallyPrime can identify potential matches where particular details differ. Treat that result as a lead to investigate. If one source shows AB/104 and the other AB/140, check the original invoice rather than copying whichever value makes the status turn green. Distinguish a genuine credit note from an invoice with a negative value or incorrectly selected voucher type.

Also inspect the reconciliation configuration. TallyHelp describes options that can ignore configured differences between books and portal values. Document any tolerance used in the exercise. A tolerance is a matching rule, not permission to disregard an incorrect invoice or a statutory condition.

Timing, IMS actions and changing statement versions

Keep the invoice date, books posting date and selected return period as separate fields in the tracker. A period difference may explain why a document appears in one comparison and not another. Do not change a books date merely to remove an exception without establishing the correct accounting and GST treatment.

Where the applicable IMS workflow and GSTR-2B recomputation are used, retain the action history and download the latest statement after the authorised process completes. Tally’s IMS guidance describes how invoice actions can affect the statement. Label each reconciliation with its statement version so a later review does not compare a refreshed portal total with an old spreadsheet.

For every unresolved item, record the reason, supporting invoice, responsible person, requested supplier clarification and next review date. Separate “waiting for evidence” from “reviewed with a decision.” Close the exception only when the decision and any resulting correction can be traced.

Does a matched invoice guarantee ITC entitlement?

No. Matching is one control. Applicable eligibility conditions and required adjustments still need assessment by the responsible tax reviewer.

Should a portal-only invoice always be entered into purchases?

No. Verify that it belongs to the business and is supported by the underlying transaction. A supplier may have reported an incorrect recipient GSTIN.

What should a beginner submit?

Provide the fictional four-record comparison, the Rs 550 net bridge, the three separate exceptions and a proposed evidence request for each. State that no return was filed and no credit decision was made in the exercise.

Official documentation for further checks

• TallyHelp: GSTR-2B reconciliation
• GST portal: GSTR-2B FAQ and eligibility
• TallyHelp: reconciliation configuration
• TallyHelp: IMS inward workflow

Frequently asked question

What should a beginner practise after learning GSTR-2B reconciliation in TallyPrime?

Build one small, documented exercise that uses the concepts safely, validate the result, and explain the decisions and limitations. Repeating this cycle makes learning more reliable than collecting disconnected tutorials.