Home / Reconciler AI
Reconciler AI · In development · Early access

The last stop before filing.

An independent verification pass over bank, ledger, GST and TDS records before a return leaves your office. Upload only, read-only, and nothing kept when the session closes.

Reconciler AI is in development and not yet available for production use. Everything described on this page is the design the product is being built to — it is a statement of intent, not of shipped functionality. Early-access places are being taken now.

AccessUpload only — no integration
WritesRead-only by design
RetentionNo retention by design
Why it matters

A verification gap with a real cost.

Verification today is manual, spreadsheet-based, and does not scale with data volume. Nothing independently checks a filing against the records behind it.

₹55,000 Cr

in fake invoice fraud identified in a single year.

GST Council, 2024
50–70%

of a Chartered Accountant’s time lost to manual reconciliation.

Industry estimates
27%

of GST notices trace back to spreadsheet errors.

CBIC / GST Council, 2024

“Technology intervention is urgently needed in MSME compliance.”

National Financial Reporting Authority, 2024

Accounting software records a transaction. Filing software submits a return. Between the two sits the gap where errors are most costly — and where Reconciler AI is built to sit.

The pass

Six steps, from upload to nothing kept.

The whole pass runs in one session. This is what happens inside it.

01

You upload

You supply the documents you already produce at period close: the bank statement, the ledger export, and the returns data. PDF, Excel, CSV, or a Tally or Zoho export.

There is no integration step by design: no API keys, no credentials for your accounting system, and no plug-in installed against your books. If your firm's policy forbids third-party access to the accounting system, that policy is not in the way here.

02

Extraction

Each document is designed to be parsed into rows: date, particulars, amount, and where in the source it came from. Scanned statements are read too, and anything the parser cannot read confidently is flagged as unread rather than guessed at.

That distinction matters more than it sounds. A reconciliation tool that silently guesses a number is worse than one that admits it could not read it.

03

Matching

Entries are matched on amount, date proximity and reference. Exact pairs settle first, then near matches within a tolerance you set — a payment cleared two days later, a reference typed with a different spacing.

Split and merged entries are handled: one bank credit against three ledger lines, or one ledger entry against a batched settlement. These are the cases where manual reconciliation actually loses time.

04

Statutory cross-check

The ledger is checked against GSTR-2B for input credit and Form 26AS for tax deducted — from files you supply, not through a portal connection. Where a supplier appears in one and not the other, or an amount differs, it is raised as an exception rather than netted off.

This is the check that most often catches something before filing rather than after a notice, because it compares what you are about to claim against what the department already holds.

05

Review

Every exception is presented with both amounts, both sources, and the date each was drawn from. You decide what each one is. Reconciler AI does not resolve exceptions and does not post corrections — it cannot write to anything.

The output is designed to be read by a reviewer who was not present for the work, which is what a working paper has to survive.

06

Close

The product is being built so that when a session ends, the files and everything derived from them are discarded. Nothing is written to a database, nothing is retained for training, and there is no copy for us to produce later on request — because there is no copy.

If you need the output, you export it before you close. That is deliberate: the alternative is a permanent archive of client financial records held by a vendor, which is a liability neither of us needs.

What an exception is

Every exception carries both figures and both sources.

An exception is never a count. It names the two amounts, the two documents they came from, and the date each was drawn from — so the person reviewing it can decide what it is without going back to the source themselves.

Reconciler AI does not resolve it, net it off, or post a correction. That judgement belongs to the professional signing the return.

Bank Ledger GST / TDS Exceptions Verified
Pass output · June3 need a human
₹ 48,200NEFT · 12 Jun Matched
₹ 84,000RTGS · 18 Jun Matched
Three of five need a human. Nothing here is resolved for you.
What it reads

Documents you already produce.

Statements

Bank PDFs and Excel exports, including multi-page scanned statements.

Books

Tally and Zoho exports, or any ledger you can produce as CSV.

Returns

GSTR-2B and Form 26AS, read against what the ledger says.

These commitments describe Reconciler AI, the product. Our services hold client data under contract when an engagement requires it; that is set out separately in the Privacy Policy.

Take an early-access place.

Join Early Access