Books, GSTR-1 and 3B that triangulate
GST Reconciliation in LekhaPro compares your books-computed figures against your as-filed GSTR-1 and GSTR-3B, showing live ₹ deltas and an internal GSTR-1-vs-3B tie-out — so what you filed matches what you booked, and you catch differences before the department does.
The single most common notice trigger is a 1-vs-3B mismatch; this catches it for you.
Three-way tie-out
Books vs GSTR-1 vs GSTR-3B, with the deltas spelled out in rupees.
Catch mismatches early
The 1-vs-3B difference — the classic notice trigger — is surfaced before filing.
Persisted
Reconciliations are saved so you have an audit trail of what tied out when.
What’s included
- Books vs GSTR-1
- GSTR-1 vs GSTR-3B
- Live ₹ deltas
- Internal tie-out
- Persisted reconciliations
- Drill-down to documents
Frequently asked
Why does 1-vs-3B matter?
A mismatch between GSTR-1 and 3B is one of the most common reasons for a GST notice — this keeps them aligned.
Is it just for the current month?
You can reconcile per period and the results are persisted for an audit trail.
What exactly is included in Reconciliation · Tie-out?
books vs GSTR-1, GSTR-1 vs GSTR-3B, live ₹ deltas, internal tie-out, persisted reconciliations and drill-down to documents. 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 reconciliation · tie-out handled differently here?
It rests on three-way tie-out, catch mismatches early and persisted. 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 Reconciliation · Tie-out work offline?
On the Desktop edition, yes — completely. books vs GSTR-1 and GSTR-1 vs GSTR-3B run against a local database on your own machine, so the screens behave the same with the network unplugged as with it connected. AI and billing are the only two things that reach out. On the Cloud edition reconciliation · tie-out runs in the browser and needs a connection.
Where does Reconciliation · Tie-out get its data from?
From your own posted books, not a separate register you maintain twice. three-way tie-out is built from the invoices, masters and rates already entered, so there is nothing to re-key before filing and nothing that can quietly disagree with the ledger it was drawn from.
How does Reconciliation · Tie-out affect my GST?
It feeds it directly rather than sitting alongside it. CGST/SGST and IGST are split from HSN or SAC and place of supply as each document is raised, so whatever reconciliation · tie-out produces is already correct when GSTR-1, 3B and 2B reconciliation are drawn off the same books. The return matches the accounts because it was never a separate exercise.
Does Reconciliation · Tie-out cost extra?
No. Reconciliation · Tie-out is part of the accounting core rather than a paid add-on, so catch mismatches early 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 Reconciliation · Tie-out before committing?
Yes — 14 days, no card. Test reconciliation · tie-out 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.
Is anything in Reconciliation · Tie-out generated by AI?
None of the figures. Everything three-way tie-out produces is computed by tested engines and would be identical with the model switched off — what AI contributes is the sentence around a number and the routing that brings the right one to your attention. Nothing it writes posts to your books without your approval.