Bring in the statement you already download
The file your bank gives you, without anyone retyping a line of it. This is the same statement your accountant has been working through by eye.
HomeRECONCILIATION
Bank statement import into Tally, from the file your bank already gives you.
Forty credits landed this week. Somebody has to work out which retailer sent each one and which bills it clears, and that somebody is usually you at nine at night.
Bank statement import takes the file your bank already gives you and turns each credit into a Tally entry. Takkada reads the narration and the account the money came from, suggests the party and the open bills it settles, and says why. You approve before anything posts, so nobody spends the evening matching credits to bills.
RECONCILIATION
From a bank file to a closed ledger
Each credit is read, not guessed at
The narration and the UTR are used to work out who sent the money. A credit with a reference in it is matched on that reference rather than on the amount alone.
The bills it clears are proposed for you
One payment covering three invoices is split across them rather than sitting on account. You see the proposed allocation before it becomes an entry.
Nothing posts until you say so
You approve the batch, and only then are the receipts written into Tally. A credit that cannot be attributed waits for you rather than being forced onto the nearest party.
The bank position stops being a mystery
Receipts and payments for the year in one view, so the gap between what the bank shows and what the books show is something you can look at rather than something you dread.
IN DETAIL
What the bank statement import actually does
What the app does today, read from the working build. The bold words are the point; the guide has the rest.
The file your bank gives you
- CSV, XLS or XLSX. Up to 10 MB, read by a spreadsheet reader rather than AI, so a statement is never misread.
- Most bank layouts known. Columns like Withdrawal Amt., Txn Date and Particulars are recognised by name, with a keyword fallback for the rest.
- Passwords and dates handled. Protected statements open after you type the password. Date order is worked out, or forced to day-first.
Each line is sorted before you see it
- Bank ledger found for you. From the account number on the statement.
- Receipt, payment or contra. Every line is sorted, and cash words such as ATM default to contra.
- The party is suggested. From a pick you made before, a remembered account-number tail, or a narration naming exactly one party. The reason is shown next to Confirm.
- Weak guesses wait. An exact account-number match is ready to post. Anything less waits for your tap.
What you can change on a line
- Type, narration, party. Any of the three, before it posts.
- Not applicable, remembered. Mark a line not applicable and it stays hidden on future statements from that bank.
- Settle specific bills. A receipt can be allocated to open bills, or left On Account. Over-allocation is blocked.
Nothing posts twice
- Re-imports are caught. An exact re-import of the same statement is blocked at posting, with a Post anyway if you mean it.
- Written after your yes. Only then are the receipts, payments and contras written into Tally against the right party.
- Own switch, own rights. Bank statement import has its own switch and needs create permission on receipts, payments or contras.
SIDE BY SIDE
What separates an import from a pile of entries
| What you need | Takkada | Other Tally mobile apps |
|---|---|---|
| Working out who sent the money | Narration and UTR read, party suggested | Matched by amount, or left to you |
| One payment against several bills | Split across the invoices it settles | Posted on account, allocated later by hand |
| Before it reaches your books | You approve the batch first | Varies, and some post directly |
| A credit nobody can attribute | Held for you rather than forced onto a party | Often dumped into a suspense entry |
| Where the entry ends up | A receipt in your Tally against the right bill | Sometimes only inside the app |
Checked on 8 August 2026 against the two Tally mobile apps distributors most often weigh against Takkada. We re-check this every fortnight, because their products move.
Bank statement import is part of the Copilot plan. It is no longer sold as a separate add-on.
Copilot ₹6,375/year + GST on a 3-year term
See what every plan includesQuestions distributors ask
Upload the statement file your bank already provides, and each credit is read and turned into a proposed receipt against a party and the invoices it settles. You review the batch and approve it, and the entries are then written into your Tally. Nothing is typed twice and nothing posts without you agreeing to it.
It reads the narration and the UTR on the credit rather than matching on the amount alone, which is what makes two retailers sending the same figure on the same day distinguishable. Where the reference is genuinely missing, the credit is held for you to attribute instead of being attached to whichever party looks closest.
It is split across the bills it settles rather than sitting on account against the party. This is the difference that matters at ageing time, because an unallocated credit leaves old invoices looking open when they have actually been paid, and your oldest slab reads worse than the truth.
No. The batch waits for your approval, and only the entries you approve are written into your books. This is deliberate. A reconciliation tool that posts on its own is one bad match away from a ledger you have to unpick by hand, which costs more than the reconciliation ever saved.
You still want the review, but the typing goes away. What used to be an evening of reading a statement line by line becomes a batch your accountant checks and approves. The exceptions, meaning the credits nobody can attribute, are surfaced separately so the work is spent where the judgement is actually needed.
See it in 15 minutes.
Decide with a full picture.
Book a demo. We walk through your setup, your Tally version, and exactly what changes for your business.