Skip to content

Accounts Payable | GSTR-2B Bill Reconciliation

GSTR-2B reconciled overnight. ITC at risk surfaced before payment.

Your purchase register is matched against GSTR-2B every night, automatically. Mismatches, vendor non-filers and tolerance gaps are flagged before a payment is scheduled, so the ITC you book is the ITC you actually claim.

Start free trialBook a demo
Gstr 2B Bill Recon

How Indian finance teams do this today

GSTR-2B recon, the way most teams still do it.

It's the second week of the month. Someone downloads GSTR-2B from the GSTN portal, exports the purchase register from the books, and starts the VLOOKUP. Then the gaps show up:

  • Vendor names don't match between 2B and your books. Pvt vs Private, & vs and, trailing 'India' or 'Industries'.
  • Invoice numbers carry stray hyphens, prefixes or leading zeros. Same invoice, no match.
  • Half the GSTINs are last month's. The supplier filed late, and the matching window has already moved on.
  • Mismatches age while next month's bills are already piling up, and vendor follow-up gets pushed to next quarter.

ITC gets reversed at year-end, not because the team didn't try, but because a manual three-way match across 800 bills, 1,200 vendors and 28 GSTINs is not a job a spreadsheet was built for.

How it works

From GSTN portal to ITC sign-off, every night.

Five steps, one of them yours. The system pulls 2B, runs the match, surfaces what needs attention, drives the vendor follow-up. Your team reviews and signs off.

Step 01

GSTR-2B pulled nightly

An authorised GSP connection pulls 2B for every GSTIN you operate, the moment it's available on the GSTN portal. No portal login, no Excel export.

Step 02

Three-way match runs

Each line of 2B is matched against your bill register and your books on PAN, GSTIN, invoice number, date, taxable value and tax components, with tolerance you control.

Step 03

Mismatches classified, not just flagged

Matches, near-matches (within tolerance), missing-in-2B, missing-in-books, vendor-non-filer and amended-by-supplier are separate buckets, each with its own resolution path.

Step 04

Vendors followed up automatically

Suppliers with non-filed or mismatched invoices receive a templated email or WhatsApp nudge from the vendor portal, with a link to confirm the right invoice number, date and value.

Step 05

ITC at risk gates the payment

Bills with unresolved mismatches surface in the payment scheduler with the ITC-at-risk amount visible. Your team chooses to hold, override with a reason, or release.

What the system does

Capability, input, output.

  • Nightly GSTR-2B pull

    Input
    Authorised GSP connection per GSTIN
    Output
    Latest 2B + IFF data, per state, per period

  • Three-way match engine

    Input
    2B line + purchase bill + GL posting
    Output
    Match status: matched, near-match, missing-2B, missing-books

  • Tolerance configuration

    Input
    Rupee or % thresholds on taxable value, IGST, CGST, SGST
    Output
    Auto-clear within tolerance; flag above

  • Vendor non-filer detection

    Input
    Filing status from GSTN per supplier GSTIN
    Output
    Risk score per vendor + bill-level non-filer flag

  • ITC eligibility tag

    Input
    GST law rules: Section 16, blocked credits, RCM
    Output
    Eligible / ineligible / RCM / blocked, per bill line

  • Rule 42/43 reversal computation

    Input
    Exempt + taxable turnover, common ITC pool
    Output
    Drafted reversal entry posted to GSTR-3B Table 4(B)

  • Vendor follow-up workflow

    Input
    Mismatch list + vendor contact master
    Output
    Email / WhatsApp nudge + portal task with audit trail

  • Payment-gate integration

    Input
    Bill match status + scheduled payment run
    Output
    ITC-at-risk visible at scheduling; CFO override logged

  • FY drill + audit pack

    Input
    All 2B periods + match decisions + overrides
    Output
    Hash-verified evidence pack for GST audit

Compliance + integrations

Built around the regulation, not bolted on.

GSTR-2B reconciliation isn't a bolt-on workflow. Every match runs against the standards your auditor will check, and the data lives where your team already posts.

Regulations we work within

  • Section 16, CGST Act

    ITC eligibility tagged per bill line: eligible, ineligible, RCM or blocked.

  • Rule 36(4)

    ITC capped to the GSTR-2B amount per period; over-claims surfaced before 3B is filed.

  • Section 38

    Drafted reversal auto-populated to GSTR-3B Table 4(B), cross-referenced to source bills.

  • Rule 42 / 43

    Common-credit reversal computed on actual exempt + taxable turnover and posted to the books.

  • Section 36 + Rule 56

    Hash-verified recon evidence retained for the full 6-year statutory period.

  • RCM (Sec 9(3) / 9(4))

    Reverse-charge bills tagged at capture and excluded from the 2B match.

Connects to

  • GSTN Authorised GSP, every GSTIN
  • Tally Prime Bidirectional sync
  • Zoho Books Native connector
  • SAP Business One Native connector
  • NetSuite Native connector

GSTR-2B Bill Reconciliation FAQ

What buyers ask.

How is this different from GSTR-2A reconciliation?

GSTR-2A is dynamic. It changes as suppliers file, amend or upload late. GSTR-2B is the static, locked snapshot used for ITC eligibility from the period it was issued. We reconcile against 2B by default, because that is what the GST law (post-2022 amendments) and the GSTN portal use as the system of record for ITC. 2A is available as a secondary view when you need to investigate an amendment trail.

What tolerance should we set, and can it differ by vendor?

Tolerance is configured at three levels (global, vendor group and individual vendor), with both rupee thresholds (typically ₹1–10 per tax component) and percentage thresholds (typically 0.1%–1%). Strategic vendors with high volume often get tighter tolerance; long-tail vendors get looser. Defaults are seeded from Indian audit practice; you tune from there.

A supplier filed late and the bill now appears in next month's 2B. What happens?

Once the bill appears in any subsequent 2B period within the FY, it auto-reconciles and the ITC-at-risk flag clears. The system doesn't need a manual nudge. The original month's 3B isn't restated; the ITC is claimed in the period the supplier's 2B carries it, which is what Section 16(4) requires.

How does this play with the new Invoice Management System (IMS)?

IMS-actioned invoices (accepted, rejected, pending) are read from the GSTN alongside 2B. The recon engine treats an IMS-rejected invoice as missing-in-2B for the period and an IMS-pending invoice as held, so your books, your IMS state and your 2B stay aligned. Full IMS workflow (accept, reject, pend, reset) runs from inside the recon screen.

Our CA reviews ITC posture before we file 3B. Can they sign off here?

Yes. CA reviewer access is read-only across bills, the match status, tolerance overrides, and the drafted Rule 42/43 reversal. Comments and sign-off are captured per period with timestamp and DSC where used. The 3B is filed only after the period is signed off. The system enforces that gate.

We run six GSTINs across four states. Does it scale?

Recon runs per GSTIN, in parallel, every night. The CFO dashboard rolls up ITC-at-risk and non-filer exposure across all GSTINs; the controller can drill into any one state's match queue. Multi-GSTIN, multi-entity and multi-state are first-class. There is no separate setup for them.

More in Accounts Payable

Related features

Pull tonight's 2B. See the mismatches by morning.

Connect one GSTIN to your books, free. The first three-way match runs tonight. ITC at risk surfaces before your next payment run. Not at year-end.

Start free trialBook a demo