GST reconciliation software (2B vs books)
Match your purchases against GSTR-2B and your sales against GSTR-1/3B — surface mismatches and ITC at risk — on an offline app.
Live product UI — sample data.
2B vs your books
Reconcile GSTR-2B against your purchase register to protect input tax credit.
1 vs 3B checks
Cross-check GSTR-1 and 3B and your books so returns agree.
ITC protected
ITC-at-risk flags credit you might lose from missing GSTINs or unfiled vendors.
What this actually means in practice
GSTR-2B and GSTR-2A are not two names for one thing. 2B is a static statement, generated once for a period and then frozen — what it says on generation day is what it says a year later, which is precisely why it is the document to reconcile against and to defend with. 2A is dynamic and keeps shifting as suppliers file late. Reconcile to 2B; use 2A to see who has filed since.
Matching happens at line level, never on a total. LekhaPro pairs each purchase against a 2B row on supplier GSTIN, document number, document date and value, normalising the ways an invoice number gets typed — leading zeros, slashes, a prefix dropped. Near-misses are scored rather than thrown away, so a number written one way in your books and another way on the portal surfaces as one probable pair with a confidence figure, not two orphans.
The output is four buckets, and each is a different conversation. Matched needs nothing. A value mismatch is a query to the supplier, or a correction in your own entry. In-books-not-in-2B is credit you are carrying but cannot yet claim, usually because the supplier has not filed. In-2B-not-in-books is a purchase you never recorded. Supplier credit notes count too — a CDNR row reduces the credit available, so ignoring notes overstates your ITC.
| Bucket | What it means | The action it calls for |
|---|---|---|
| Matched | Book row and 2B row agree on party, document and value | Claim the credit; nothing further is needed |
| Value mismatch | Same document, a different taxable or tax figure | Query the supplier, or correct the purchase entry |
| In books, not in 2B | You recorded a purchase the supplier has not reported | Chase the supplier; hold the credit until it appears |
| In 2B, not in books | The portal shows an invoice you never entered | Book it, or reject it if it is not your purchase |
| Matched but ineligible | Paired cleanly, yet the portal flags the credit as blocked | Leave it unclaimed and record the blocking reason |
| Supplier credit note | A CDNR row that nets down credit already taken | Reverse the corresponding credit in the same period |
What’s included
- GSTR-2B vs purchase books
- GSTR-1 vs 3B checks
- Mismatch & exception reports
- ITC-at-risk radar
- HSN summary
- Filing-ready pack
- Offline-first
What it does not do
- · Reconciliation runs on the 2B JSON or Excel you download from the portal, or on a 2A pulled through your own GST Suvidha Provider credentials — LekhaPro does not sign in to the GST portal on your behalf.
- · Vendor follow-up is a list and a reminder. The app does not chase suppliers for you, nor take actions on the portal on your behalf; those remain your calls to make.
- · The Desktop edition is Windows-only; the Cloud edition runs the same reconciliation in a browser on any platform.
Frequently asked
Does it reconcile GSTR-2B?
Yes — match GSTR-2B against your purchase register and surface mismatches and ITC at risk.
Does it check GSTR-1 vs 3B?
Yes — cross-checks so your returns and books agree before filing.
Is it offline?
Yes — reconciliation runs on your machine.
Should I reconcile against 2A or 2B?
Against 2B, for the period you are claiming. Because 2B is generated once and then stays fixed, it is auditable — you can show exactly what credit was available to you when you filed. 2A keeps moving as suppliers file late, which makes it useful for tracking who has since reported, but a poor basis for a claim you may have to defend.
Why did my ITC fall after a supplier issued a credit note?
Because a credit note reduces the credit that was made available to you. The supplier's CDNR entry in 2B nets down the tax you may claim, so a purchase matched last month can be partly withdrawn this month. LekhaPro reads CDNR rows alongside invoices, so the eligible figure reflects the notes rather than the gross.
What exactly is included in GST · 2B reconciliation?
GSTR-2B vs purchase books, GSTR-1 vs 3B checks, mismatch & exception reports, ITC-at-risk radar, HSN summary and filing-ready pack, and 1 more. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is gst · 2b reconciliation handled differently here?
It rests on 2B vs your books, 1 vs 3B checks and ITC protected. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
Does GST · 2B reconciliation post to the real books?
Yes, and that is the whole reason it lives in this product rather than beside it. What 2B vs your books records lands in the same posted double-entry ledger the Trial Balance, P&L and GST returns are built from — so there is no second set of gst · 2b reconciliation numbers to reconcile against the first.
Does GST · 2B reconciliation cost extra?
No. GST · 2B reconciliation is part of the accounting core rather than a paid add-on, so 1 vs 3B checks is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.
Can I try GST · 2B reconciliation before committing?
Yes — 14 days, no card. Test gst · 2b reconciliation against your own masters and your own transactions rather than sample data: the questions worth answering here are about your business's edge cases, and a demo dataset is built not to have any.