How these numbers are computed
ITC composition
Eligible (reconciled) vs provisional (booked, awaiting supplier) vs in-2B-not-booked, by tax value
Unmatched in 2B — why?
The actionable breakdown — turns the “in 2B, not booked” number into work
Data
—
Upload a file
Auto-detects type & period, previews it, and on commit re-matches the entire open pool — so earlier months’ timing differences clear automatically.
Bulk upload (.zip)
Drop a .zip of monthly 2B / 6A / PR / vendor workbooks. Each is detected, validated and previewed; commit the ready ones in one click.
Upload formats & templates
The accepted files, each in a fixed format. Download a template or follow the steps, then upload above.
Data coverage loading…
Every loaded period and which statements are present in each. The reconciliation runs across all loaded periods, so timing differences clear automatically as later months arrive.
Upload history
Individual files uploaded through the tool, newest first. (Months loaded by the initial bulk seed won’t appear here — see Data coverage above for those.)
Duplicate check
The same invoice loaded more than once (PR keyed on vendor + invoice no, 2B on supplier GSTIN + invoice no) — usually a cumulative file committed under a different month. Review and retract the extra copies; the kept one stays. reviewer/admin
What each bucket & section means
Suggested matches review & confirm
Open 2B and PR documents from the same supplier PAN with tax agreeing within ₹1 but a different invoice number — likely the same invoice typed differently. Ranked by similarity. These are never auto-matched: confirm each one yourself (logged as a manual action).
View findings by section, or download document packs
Reconciliation explorer
Findings on screen — by bucket and by section. Each view downloads as CSV.
Overview — documents by bucket × section
Click any cell to open that slice in the explorer above.
Document packs
Formatted deliverables for filing, audit and the board.
Month-over-month — ITC, at-risk & ISD
Eligible ITC (net of credit notes), ITC at risk, and ISD credit across the year.
Reconciliation match-rate %
Share of each month's documents reconciled — the health trend.
Other GSTIN registrations
2B sitting under TBEA's other state registrations (Gujarat is the main reconciled GSTIN). These are 2B-only — no Purchase Register has been loaded for them yet — so they're shown as an ITC-exposure view, kept entirely out of the main reconciliation. Upload the all-states workbook on the Upload tab to refresh.
Vendor risk — highest ITC exposure
Suppliers ranked by ITC at risk + filing reliability. HIGH = low match rate (likely won't file).
Vendor purchase trend
How much you purchased from a vendor over the year (invoice value + tax, by month).
Manual reconciliation — match by hand
Pick a vendor to see their booked-but-not-in-2B and in-2B-but-not-booked invoices side by side. Select one from each side and match with a reason — for the cases auto-match won't touch (number typed differently, split/clubbed invoices, amount differences). Logged as an audited manual action.
Enter a vendor to begin.
Add or correct a vendor and the PR re-bridges immediately (a newly-bridged invoice clears on the spot). Or download the Excel above, fill new rows, and re-upload it on the Upload tab. reviewer/admin
| Source | Vendor code | Vendor name | PAN | GSTIN |
|---|
What this screen does
- Bank / CHA / Airline / Insurance / Courier → Credit via JV — eligible, still counted in ITC.
- Hotel (out-of-state) and Cab / Taxi → Ineligible — correctly not claimed.
- Normal supplier → stays in Missing in PR to follow up.
| Supplier (2B name) | PAN | GSTINs | 2B docs | Tax · missing in PR | Vendor type | Treatment |
|---|
What this screen does
Audit pack
One workbook: Summary · GSTR-2B vs Purchase · one sheet per check · Evidence register (any section whose source isn't uploaded is marked as a scope limitation) · covering-email draft with the headline figures.
About this log
| When | Event | User | Document / detail | IP |
|---|---|---|---|---|
| loading… | ||||
Roles & what each can do
- Viewer — read-only: dashboard, findings, reports.
- Preparer — viewer + upload & commit files and confirm suggested matches.
- Reviewer — viewer + confirm/override matches and see the full activity log (no uploads).
- Admin — everything, plus manage users here and reset the ledger.
Add a user
They sign in with this email & password; they can change their own password later.
| Name | Role | Last sign-in | Actions | |
|---|---|---|---|---|
| loading… | ||||
GST 2B vs Purchase Register — how this tool works
This is a continuous reconciliation ledger: each month you upload the supplier-filed GSTR-2B (from the GST portal) and your Purchase Register (PR), and the tool matches them so you can claim the right Input Tax Credit (ITC) and chase the gaps. Every document keeps its status across months, so timing differences clear themselves over time.
1 · The data it uses
- GSTR-2B — the supplier-filed statement, only the Excel generated from the GST portal. All sections are read: B2B, B2BA (amendments), CDNR (credit/debit notes), IMPG (import IGST), ECO and ISD.
- Purchase Register — your Oracle AP export, line-item level, no manual working. The PR has no GSTIN; it carries a vendor code.
- Vendor master — the bridge. Vendor GST Details (VG) is the primary vendor-code → PAN/GSTIN source; Vendor Master (VM) is a PAN-only fallback.
2 · How matching works — the exact method
Matching is deterministic (rule-based), not AI/fuzzy guesswork. The identity of an invoice is reduced to one key:
PAN = characters 3–12 of the GSTIN (2B side); the PR side is bridged to a PAN via the vendor master.
normalised number = upper-cased, spaces & punctuation removed (INV-001 = inv 001 = INV/001).
A pair is a full match only when every tax head agrees within a ₹1 tolerance:
It runs in ordered passes, most-confident first; a document is consumed once matched:
Credit/debit notes are compared on absolute values. There is no tax-only pass — it caused false matches and was removed.
3 · Cross-period auto-clearing
On every commit the matcher runs against the entire open pool across all months. A December invoice the supplier reports only in January clears automatically when January is loaded — no manual carry-forward. The open list is a true aging worklist.
4 · Buckets & sections
Findings split into five buckets (Missing in 2B, Missing in PR, Differences, Matched, Out of scope) and you can view each by section — B2B invoices, Credit notes, Debit notes, Import (IMPG) and Other (ECO/ISD) — combined or separately, on the Findings and Reports tabs. Out of scope = zero-GST and RCM (reverse charge), tracked but excluded from “missing” follow-ups.
5 · Why a 2B row is unmatched
- Trailing edge — recently filed; the matching PR will likely arrive next month.
- Likely same invoice (no. differs) — same PAN & tax, different number → see Suggested matches.
- Not booked / follow-up — no corresponding PR entry.
- No PR from this supplier — the PAN never appears in your PR.
- Prior period — origin before the ledger start.
6 · Reports & the as-on date
Reports rebuild live from the ledger. The workbook carries 14 tabs; the CFO PDF is a one-page summary; the as-on-date report reproduces a point in time (only periods up to the chosen date, matched only if both sides were in scope by then).
7 · Roles, activity log & security
Access is by role — viewer / preparer / reviewer / admin — enforced on the server. The Activity log records sign-ins, uploads, commits, exports, user/role changes and manual decisions in a tamper-evident chain. Sign-in is per user, rate-limited, over HTTPS; change your own password any time from the top bar.
Prepared for TBEA Energy (India) Pvt Ltd · GSTIN 24AADCT5210F1ZU · by CA Siddharth Shah, Chartered Accountants.