GSTR-2B vs Purchase Register: Practical ITC Reconciliation Guide for GST

GSTR-2B is one of the most important controls in a GST input-tax-credit close, but it is not a substitute for the purchase register or for legal ITC eligibility checks. The GST Portal's official GSTR-2B Advisory describes GSTR-2B as an auto-drafted ITC statement based on information furnished by suppliers and other specified sources. It also expressly advises taxpayers to reconcile GSTR-2B with their own records and books of account.

What GSTR-2B tells you

GSTR-2B organises document-level information that can affect the recipient's ITC review. The advisory explains that supplier-filed information from forms such as GSTR-1 or IFF, along with specified other sources, feeds the statement. It also includes import-of-goods information received from ICEGATE, including specified inward supplies from SEZ units or developers.

The statement separates information into ITC-available and ITC-not-available sections. However, the portal itself warns that the system's “ITC not available” identification covers specified scenarios only. Other legal restrictions can still make a credit ineligible even if the system does not flag it. That is why a finance team should never use “appears in GSTR-2B” as the sole approval test.

Why the purchase register is still essential

The purchase register answers questions that GSTR-2B cannot answer on its own: Was the invoice actually booked? Were the goods or services received? Is the expense business-related? Is the GSTIN correct? Is the credit blocked or partly attributable to exempt activity? Has the invoice already been claimed in another period?

A useful reconciliation therefore compares portal data with the entity's books and then applies the GST-law eligibility tests. The objective is not merely to make two totals equal. It is to explain every material document-level difference and decide the correct treatment.

A practical four-bucket reconciliation

1. In books and in GSTR-2B: match GSTIN, invoice number, invoice date, taxable value and tax amount. Then perform the legal eligibility review before claiming credit.
2. In books but not in GSTR-2B: investigate whether the supplier has not filed or has reported the invoice incorrectly, whether the document falls into a different statement period, or whether another data-flow issue exists. Do not force-match the item by changing the books without evidence.
3. In GSTR-2B but not in books: check for unrecorded invoices, wrong recipient GSTIN used by a supplier, duplicate documents, goods or services not received, or documents belonging to another entity or location.
4. Amount or master-data mismatch: investigate differences in GSTIN, invoice number, taxable value, tax rate, tax amount, place of supply, debit note or credit note treatment.

Worked example

Assume the April purchase register shows eligible-looking input GST of ₹8,40,000, while the GSTR-2B review shows ₹8,65,000. A weak control would simply claim the portal total or restrict the claim to the lower book total. A proper reconciliation explains the ₹25,000 difference.

Suppose ₹18,000 relates to an invoice visible in GSTR-2B but not yet recorded because the service invoice is still under internal approval, while ₹7,000 relates to a supplier document that does not belong to the recipient's business. The team should investigate and book the genuine liability only when appropriate, while separately following up the incorrectly reported document. The reconciliation becomes an evidence trail, not just a spreadsheet total.

GSTR-2B timing differences need careful handling

The GST Portal advisory explains that a document furnished by a supplier appears in the next open GSTR-2B according to the applicable filing cycle, irrespective of the original invoice date. This can create legitimate timing differences between the purchase register and the statement.

For example, an invoice may be dated in one month but reported by the supplier later. The recipient's reconciliation should preserve the original invoice information and track the statement period in which it appears rather than rewriting the accounting date simply to make the monthly reports align.

Do not double-claim a late-appearing invoice

The advisory specifically tells taxpayers to ensure that no credit is availed twice for any document. This is a major risk where an invoice is handled manually because it was missing from an earlier statement and later appears in GSTR-2B. A strong reconciliation file therefore needs a claim-status field showing whether the document was claimed, reversed, deferred or re-availed and in which tax period.

Reverse charge and imports need separate attention

Not every credit follows the ordinary supplier-invoice pattern. The advisory notes that reverse-charge credit on import of services is not part of GSTR-2B and continues to require taxpayer-side reporting. For inward supplies liable to reverse charge that are reflected in the statement, payment of the tax and the applicable credit treatment must still be handled through the relevant GSTR-3B tables.

Import-of-goods information is sourced from ICEGATE. Finance teams should therefore reconcile bills of entry and customs records separately instead of expecting the domestic purchase-register matching process to explain every import difference.

Monthly reconciliation checklist

• Freeze the books extract: download a controlled purchase-register version for the tax period with GSTIN, invoice number, date, taxable value and tax components.
• Download document-level GSTR-2B: preserve the source file used for the close rather than working only from a summary.
• Standardise matching fields: clean invoice-number formats and GSTINs without altering the underlying source data.
• Run exact and exception matching: separate full matches, amount mismatches, book-only documents and 2B-only documents.
• Apply eligibility checks: test blocked credits, business use, receipt conditions, time limits and other relevant restrictions independently of portal visibility.
• Track claim status: record claimed, deferred, reversed and re-availed amounts by document and tax period.
• Follow up vendors: use a controlled exception list for missing or incorrectly reported invoices.
• Reconcile to GSTR-3B: the final eligible-credit working should explain the amount actually taken in the return.

Common mistakes to avoid

• Claiming every item shown as available in GSTR-2B without testing legal eligibility.
• Assuming every book-only invoice is permanently ineligible instead of investigating timing or supplier reporting.
• Ignoring 2B-only invoices because they are not in the ledger.
• Matching only total IGST, CGST and SGST rather than document-level data.
• Failing to maintain a prior-period claim history, creating duplicate-credit risk.
• Expecting GSTR-2B to contain every reverse-charge or import-service credit item.

Practical takeaway

GSTR-2B reconciliation should answer three questions for every material invoice: does the document exist in the books, does the portal data agree, and is the credit legally eligible? Build the monthly close around those three tests, keep document-level claim history, investigate timing and vendor-reporting exceptions, and reconcile the final eligible amount to GSTR-3B. That produces a much stronger ITC control than simply matching two monthly totals.