GSTR-2B Reconciliation: Books vs Portal

Quick View

Why It Matters

The reconciliation should begin with the purchase register and identify invoices present in both records, only in books, only in GSTR-2B, mismatched and legally ineligible.

Timing differences require ageing. A recent supplier delay is different from a six-month old invoice with no reporting. Vendor follow-up should record the owner and promised correction period.

Credit eligibility depends on the nature of supply and legal conditions, not only appearance in GSTR-2B. Conversely, an invoice in books may need to wait until the statutory conditions are met.

Control Framework

Action Checklist

1. Download and freeze the period data.
2. Normalise vendor and invoice identifiers.
3. Match at invoice and credit-note level.
4. Review legal eligibility separately.
5. Track vendor corrections by ageing.
6. Reconcile final GSTR-3B to the working.

Practical Example

Evidence to Keep

• Purchase register.
• GSTR-2B download.
• Invoices and receipt evidence.
• Eligibility and blocked-credit memo.
• Vendor follow-up tracker.
• GSTR-3B computation and sign-off.

Warning Signs

Management Decision

Report the ageing and value of unresolved credit to management. A growing balance can indicate poor vendor quality or procurement discipline.

Preserve the downloaded statement used for filing because later portal updates may change what a reviewer sees.

Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.

Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.

Monthly Review Test

Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?

The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.

Exception Review

The operating record should connect the control stages—matched eligible, books only, portal only, mismatch or blocked—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.

Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.

Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.

Tag every working with the legal entity, tax period and governing law. The filing date alone does not decide which Act, rate, form or limitation period applies, especially during the 2026 income-tax transition or where a notice covers earlier GST periods.

Portal data should be downloaded and preserved with the filing version. Later supplier corrections, updated statements or portal changes can otherwise make it difficult to prove what information management used when the return or response was approved.