GST reconciliation
GSTR-2B compared against the client's purchase register, invoice by invoice, on rules rather than a model.
₹86,000 vs ₹86,000 · nil
GST reconciliation for Indian CA firms
Close GST month-endwithout the spreadsheet chase.
Reconcile GSTR-2B against your clients’ books, understand why entries differ, see the input tax credit at risk, and know what to correct — before the 20th.
M
Aug 2026Meridian Packaging LLP
24AABFM8821K1Z7 · Maharashtra
Reconciliation
Search invoicesExceptions only
Invoices in 2B
1,248
Matched
1,204
Exceptions
44
ITC at risk
₹28,320
| Invoice | GSTR-2B | Books | Diff | ||
|---|---|---|---|---|---|
| MP-2608 | Freight Line Pvt Ltd27AACCF4321N1Z9 | ₹86,000 | ₹86,000 | Nil | Matched |
| MP-2609 | SafeTrans Logistics29AADCD7781H1Z8 | ₹15,480 | ₹15,336 | ₹144 | Review |
| MP-2611 | Shree Balaji Enterprises27AAKFS1108R1ZQ | ₹24,000 | — | ₹24,000 | Not in books |
MP-2609 · Why they differ₹144 in GST
Freight was booked on a separate voucher, so the books carry the tax on it in a different entry.
Evidence
Voucher MP-2609
Suggested
Split the voucher
Posts whenYou approve
Why CA firms trust it with their clients’ books
Built for Indian CA firms
GSTR-2B against a purchase register, the way the work is actually done. Not a generic ledger tool with GST bolted on.
Tally stays the system of record
We read from it and write back to it. Your books live where they have always lived, and nothing here replaces them.
Nothing posts without approval
An uncertain entry goes to a review queue, never to a guess. Suspense stays empty because we refuse to fill it.
The monthly grind
Six steps. Every client.
Every month.
None of it is difficult. All of it is slow, and none of it is the work a CA trained to do.
- 0130 min
Download GSTR-2B
One client, one period, from the portal.
- 0245 min
Export the books
Purchase register out of Tally, into a spreadsheet.
- 032 hr
Compare invoices
By eye, in Excel, line against line.
- 043 hr
Find the mismatches
Numbers typed three different ways, dates off by a month.
- 054 hr
Work out why
Open the voucher. Open the invoice. Read both.
- 061 hr
Post the corrections
Back into Tally, before the 20th.
01 / 06Swipe
Where the day goes
Per client, per month
- Download GSTR-2B30 min
- Export the books45 min
- Compare invoices2 hr
- Find the mismatches3 hr
- Work out why4 hr
- Post the corrections1 hr
Estimated total≈ 11.3 hr
Illustrative. Drawn from how firms describe the month, not from measured data.
With Ledger Orbit
- 1
Connect once
A small agent beside Tally. Set up in minutes, then never again.
- 2
Reconciliation runs itself
Every invoice, both sides, on a deterministic engine.
- 3
Only exceptions reach a person
With the reason, the evidence, and what to do about it.
Matched automaticallyYou look at these
Understand, not just find
Don’t just find the mismatch.
Understand it.
A difference of ₹144 takes a second to spot. Knowing it is freight on a separate voucher takes someone opening two documents. That second part is the job.
Exception · MP-2609
Needs reviewGST difference
₹144
- Why
- Freight of ₹800 was booked on a separate voucher, so the books carry ₹144 of tax on it in a different entry from the invoice.
- Evidence
- Voucher MP-2609·SafeTrans Logistics invoice, 14 Aug
- Suggested action
- Split the voucher so freight sits against the same invoice.
Posts to Tally whenA partner approves
NumberExplanationEvidenceAction
Everyone stops at the first one. The other three are the month.
The promise
No entry goes
to suspense.
A ledger is proposed only when the client’s own posting history supports it. When it doesn’t, the entry goes to a review queue instead of being guessed at — because a guess is exactly how something ends up in suspense.
So the queue shrinks on its own. Every decision a partner makes is one the engine does not have to ask about again.
Entries requiring review
One client
- 147Mar
- 121Apr
- 64May
- 31Jun
- 9Jul
- 2Aug
147 → 2
entries a person had to look at, over six months
Illustrative. A model of how the mapping history compounds, not a customer result.
Control
Your books remain
the source of truth.
Nothing is posted that a person has not seen. Nothing uncertain is posted at all. Tally is where the books live, before and after — we read from it and write back to it, and we never become the record.
- Human approval before posting
- Every decision keeps its reasoning
- Works with your existing workflow
- Deterministic matching, not a model
The path an entry takes
Tally stays the record- You
Client books
In Tally, where they already are
- LO
Reconciliation
GSTR-2B against the register
- LO
Exception
With the reason and the evidence
- You
Human review
A partner reads it and decides
- You
Posted back
Into Tally, with the trail attached
Back where it started. Two of these five steps are ours.
You decide. We assist.
What’s in the first release
Everything you need
to close with confidence.
GSTR-1 and 3B filing, TDS returns, notice replies and ITR are on the roadmap. They are not in this release, and we would rather say so than imply otherwise.
Exception reasoning
Why two records differ, in a sentence, with the voucher and the invoice it was read from.
Freight booked separately on MP-2609
ITC visibility
What is claimable and what is at risk this month, totalled as you work through the queue.
At risk ₹28,320 · claimable ₹4,81,220
Suggested corrections
What should change, named before anything is posted. A ledger is only ever one that exists in their books.
Suspense A/c → Freight Inward
Tally, both ways
Read the ledgers and the register, post the vouchers back. A small agent beside Tally, outbound only.
← ledgers, register · → approved vouchers
Audit trail
Every decision keeps the reasoning it was made on, append-only. CA firms are themselves audited.
14:06 · MP-2609 split, approved
Early access
Close the month
with fewer questions.
We’re taking on a small number of firms before opening this up more broadly. You get a direct line to the people building it, and your edge cases looked at first.
Request early access
Two questions. We reply from [email protected].