Bank reconciliation without the busywork
Import any Indian bank statement, auto-match and categorise — so your cash position is always current.
Live product UI — sample data.
Smart statement import
A column-mapping wizard learns each bank’s format and remembers it; duplicate detection keeps re-imports clean.
Categorise on autopilot
Rule-based classification sorts lines into sales, purchases, expenses, transfers and tax — with suggested matches to open invoices and bills.
Always-current cash
Multiple bank accounts, a bank ledger and a cash-flow summary keep your real position one click away.
What this actually means in practice
Import is a CSV or XLSX upload with a column-mapping step: you point at the date, narration, debit, credit and balance columns once, and that mapping is saved against the bank's name for every later statement. Each line is fingerprinted on date, narration, amounts and its occurrence number among identical lines — so re-uploading an overlapping statement skips what is already there, while two genuine same-day, same-amount rows both survive. An import is one batch, and a batch can be undone whole.
Classification is keyword rules over the narration plus the direction of money, returning a category and a confidence: tax, salary, interest, bank charge, transfer, customer collection, vendor payment, expense, or uncategorised where nothing fits. That is a suggestion, not a posting. Matching is the separate act of linking a statement line to a voucher already in your books — a receipt, a vendor payment, an expense, a contra — and the link is what removes the line from the reconciliation gap.
The reconciliation statement is where this pays. It starts from your bank book closing balance as at a chosen date, adds cheques issued but not presented, subtracts cheques deposited but not credited, and then applies the net of statement lines you have not matched. Cheque timing is harmless. Unmatched lines are not: a debit you never booked is usually a charge, an EMI or a standing instruction; an unmatched credit is usually a customer payment nobody recorded.
| What is left unreconciled | What it usually means | What to do |
|---|---|---|
| Cheque issued, not presented | Pure timing — the payee has not banked it yet | Nothing; it clears itself |
| Cheque deposited, not credited | Timing again, or a cheque returned unpaid | Chase it if older than the clearing cycle |
| Unmatched debit line | A charge, EMI, standing instruction or fee never booked | Post an expense voucher, then match the line |
| Unmatched credit line | A customer paid directly and no receipt was entered | Enter the receipt, then match the line |
| Unmatched transfer | Money moved between your own accounts, booked once or not at all | Post a contra entry for both sides |
| Residual difference | An entry error, a wrong amount or a missing voucher | Compare the running balance line by line |
| Difference of zero | Only timing items remain — the account reconciles | Record the date and move on |
What’s included
- CSV / XLSX import (any Indian bank)
- Per-bank saved column mapping
- Duplicate detection
- Rule-based categorisation
- Multiple bank accounts
- Bank ledger & cash-flow summary
What it does not do
- · Statement import is a manual upload, not an automatic feed. There is no account-aggregator or bank-API connection today.
- · Categorisation is keyword rules, so an unusually worded narration lands in uncategorised rather than being guessed at. You correct it and the rule stands.
- · Matching a line to a voucher records the link — it does not create the voucher. A charge you never booked still needs an expense entry of its own.
- · The reconciliation statement uses the closing balance you type in, or the running balance from an imported statement. It cannot fetch a balance from your bank.
Frequently asked
Which banks are supported?
Any — the mapping wizard adapts to each bank’s CSV/XLSX layout and saves it for next time.
Are bank feeds automatic?
Today it’s a quick manual statement upload. Automatic account-aggregator feeds are on the roadmap.
I imported the same statement twice by mistake — what now?
Very likely nothing happened. Lines already present are skipped on their fingerprint, so an overlapping range simply does not duplicate. If something did land wrongly, each import is stored as a batch and undoing that batch removes only its own lines, leaving earlier imports and every voucher match intact.
Does a statement line become a ledger entry on its own?
No, and deliberately so. Imported lines are the bank's version of events, held beside your books rather than inside them. You post the voucher — a receipt, an expense, a contra — and then link the line to it. That keeps the ledger something you authored, and it keeps the reconciliation meaningful, since a statement that posts itself can never disagree with you.
What exactly is included in Banking?
CSV / XLSX import (any Indian bank), per-bank saved column mapping, duplicate detection, rule-based categorisation, multiple bank accounts and bank ledger & cash-flow summary. 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 banking handled differently here?
It rests on smart statement import, categorise on autopilot and always-current cash. 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 Banking work offline?
On the Desktop edition, yes — completely. CSV / XLSX import (any Indian bank) and per-bank saved column mapping 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 banking runs in the browser and needs a connection.
How does Banking 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 banking 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 Banking cost extra?
No. Banking is part of the accounting core rather than a paid add-on, so categorise on autopilot 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.
Reconciliation without the busywork
Drop in a statement; LekhaPro matches what it can, learns your categories, and leaves you only the exceptions.
- Import statementany Indian bank
- Matched to entriesauto, deduped
- Rest categorizedrules it remembers
- Reconciledbooks tie to the bank
Illustrative. Account-aggregator live feeds are on the roadmap.