Bank statement PDFs, turned into Tally-ready entries.

Built for chartered accountants. Upload the client’s statement, check the balance chain, and download a Tally XML voucher file with the ledger masters already inside — ready to import into the client’s books.

Sign in with your WhatsApp number — no password, and no separate sign-up step.

Speed

Most statements are converted in under 20 seconds.

Sounds unbelievable? That’s what our data shows.

How it works

Four steps from PDF to Tally.

A month of bank activity, posted to the client’s books in the time it used to take to key in the first page.

  1. Step 1

    Upload the statement

    Pick the client’s bank, drop in the PDF. Leepik reads it in seconds — no manual data entry.

  2. Step 2

    Leepik reads the table

    Text extraction pulls the real column layout out of the PDF — narration, cheque number, value date, debit, credit, balance. No OCR guesswork, no AI service in the loop.

  3. Step 3

    Review and reconcile

    Every row is editable, and each one gets a ledger automatically — and Leepik remembers your pick for next time. Leepik walks the running balance and flags anything that doesn’t tally before you sign off.

  4. Step 4

    Import into Tally

    Download a Tally XML voucher file with the ledger masters included, so Tally creates whatever is missing on import. Or take a plain CSV if you’d rather work in Excel.

Ledgers · Mapping rules

Every row gets a ledger, and Leepik remembers your choice.

Leepik matches each transaction's counterparty against the client's own ledger master and suggests a ledger the moment a statement opens. Confirm one, and that pick becomes a rule for that client — the same counterparty maps itself on every statement after.

  • A suggested ledger on every row as soon as the statement is parsed
  • Confirm a pick once — Leepik saves it as a mapping rule automatically
  • The next statement from that party maps itself, no re-selecting
  • Anything still unresolved falls to Suspense, never silently guessed
  • Rules stay scoped to their own client — never mixed with another client's ledger master

Ledger suggestions

UPI/RAJESH TRADERS

Rajesh Traders

Learned

NEFT/AXIS/SALARY

Salary Payable

Learned

IMPS/KIRAN TEXTILES

Kiran Textiles

Suggested

CHQ 004182

Suspense

Unmapped

Tally · Voucher import

It lands in Tally as vouchers, not as a CSV to re-key.

The export is a Tally XML voucher file that carries its own <LEDGER> masters, so Tally creates any ledger that is missing at import time instead of failing on it. Amount signs follow Tally's convention — negative is the debit leg — so the vouchers post the right way round.

  • Tally XML with a <LEDGER> master emitted for every ledger used
  • Per-row ledger dropdown, drawn from that client’s own ledger master
  • Anything unmapped falls to Suspense, so no row silently disappears
  • Set the bank ledger name exactly as it reads in the client’s Tally company
  • Date-range filter applied at export, for part-period postings

Reconciliation · Balance chain

If the balance doesn’t tally, you hear about it.

Leepik compares the closing balance printed on the statement against the last row it parsed, and tells you the moment the two disagree. You sign off on a reconciled month, not on a hopeful one.

  • Closing balance cross-checked against the statement’s own summary
  • Debit / credit direction verified against the balance movement
  • Any row whose balance can’t be derived is flagged, not quietly dropped
  • Inline-editable cells — fix a narration or an amount without re-uploading
  • Rows always returned oldest to newest, whatever order the bank printed

Engine · Every bank your clients use

Written per bank, not guessed.

Every supported bank has its own parser built against real statements. Column positions are read from the PDF's own header row at runtime, so a branch template with slightly different margins still lands in the right columns.

  • A dedicated parser per bank, plus a generic reader for everything else
  • Public sector, private, small finance, payments and co-operative banks
  • Opening / brought-forward rows kept, so the ledger starts where the bank did
  • Value date, cheque number and narration preserved exactly as printed
DateNarrationWithdrawalDepositBalance
02-04UPI/DR/40213…4,500.00—1,86,220.40
04-04NEFT/AXIS/SAL—92,000.002,78,220.40
09-04CHQ 00418218,750.00—2,59,470.40
15-04IMPS/CR/8821—6,300.002,65,770.40

Practice · One login, every client

Built for a client list, not a single company.

A practice juggles a dozen entities at once. Each client gets its own workspace, its own ledger master and its own statement history — switched from the header, not from a second login.

  • Separate workspaces per client company under one account
  • Ledger masters kept per client, never shared across books
  • Full statement history — reopen and re-export any past month
  • Team logins created and deactivated by your own admin
  • New bank formats are handled automatically

Active client

Sharma & Associates
Nexa Traders Pvt Ltd
Kiran Textiles
Vardhman Agro Exports
Deshmukh Logistics LLP
Anand Pharma Distributors

Confidentiality

Your clients’ statements never reach a third party.

You hold other people’s bank data under a professional duty of confidence. So the parsing engine was built with no third-party calls in it — not as a setting you switch on, but as the only way it works.

No third-party AI ever sees it
No OCR service, no LLM, no cloud vision API anywhere in the parsing path. Leepik and its own ledger-mapping engine are the only ones that touch the file.
Read, not guessed
Plain text extraction against the PDF’s own layout. A scanned, image-only PDF is reported unparseable, not sent out to be guessed at.
Client data stays walled off
Every statement is scoped to one client workspace. Ledger masters, history and exports never cross between clients.
Honest about what we keep
The PDF and its parsed result are retained, so you can reopen and re-export any past statement.
Accounts under your control
JWT sessions, bcrypt-hashed passwords, and staff logins your own admin creates and deactivates.
Illustration: a practitioner resting her hand on a sealed vault door that holds her client's bank statement, with the link to an outside cloud service crossed out

Who it’s for

Built for the people who actually post the entries.

  • Chartered accountants

    Close a client’s books without keying 400 rows off a PDF. Map ledgers once, then push the whole month into Tally as vouchers.

  • Accounting & bookkeeping firms

    Every client is its own workspace with its own ledger master, all under one team login — and the article clerks can run it unsupervised.

  • In-house finance teams

    Get a month of bank activity into Tally or a spreadsheet in minutes, with the balance chain already reconciled against the statement.

Pricing

Free while Leepik is in beta.

No plans to compare, no card, no seat count. Beta accounts get the whole product — we would rather you put real client statements through it and tell us where it hurts.

Beta access

Open now

₹0

For the whole beta period

  • Every supported bank and statement format
  • Tally XML + CSV export
  • Full statement history and re-export
  • Review and edit every transaction before you export
  • New bank formats as they ship, at no extra cost
  • Support straight from the people who built it
Try one statement

Paid plans come after beta, priced by statement pages rather than per seat. We will publish the numbers well before anything switches on, and beta users hear it first — nothing on this page charges you today.

Questions

Straight answers.

How does the Tally import actually work?

You download a Tally XML voucher file and import it into the client’s company in Tally. The file carries a <LEDGER> master for every ledger it uses, so Tally creates anything that is missing instead of rejecting the import. Amount signs follow Tally’s convention, so debits and credits post the right way round.

What if a transaction has no ledger mapped?

It posts to Suspense rather than vanishing. You reconcile it inside Tally exactly as you would a manually keyed entry — nothing is silently dropped from the voucher file.

Which banks and statement formats are supported?

Every bank in the upload list is supported. The banks your clients are most likely to use — public sector, private, small finance, payments, and the district and urban co-operative banks a lot of tools skip — have a dedicated parser written and verified against real statements, including banks that print several different layouts. Any other bank still parses through Leepik's generic statement reader, and new bank formats are handled automatically.

Is my client’s statement sent to any AI service?

No. There is no OCR service, no LLM and no cloud vision API in the parsing path at all. The file is uploaded to Leepik and read there with plain text extraction — it is never forwarded to OpenAI, Google or any other third party.

What about scanned or photographed statements?

An image-only PDF has no text layer to read, so Leepik reports it as unparseable instead of guessing. There is no OCR fallback, and that is deliberate — adding one would mean handing your client’s statement to an outside service. Ask the bank for the digital PDF and it will parse.

Can I handle several clients from one login?

Yes — each client company is its own workspace, with its own ledger master and its own statement history, switched from the header. Staff logins are created and deactivated by your admin.

How do I get an account?

Hit Try one statement and enter the WhatsApp number you want to use. We send a 6-digit code, you enter it, and you are in — the same step whether it is your first visit or your fiftieth. There is no password, and online billing is not switched on yet.

Stop typing bank statements into Tally.

Upload the client’s PDF, check the balance chain, import the vouchers. That is the whole job — and it should take minutes, not an afternoon of data entry.

Try one statementTakes a WhatsApp number.