Bank reconciliation is how you check your books agree with your bank: upload your bank statement — as a spreadsheet, a CSV or a PDF — and Finocket lines each statement entry up against the payments and expenses you've already recorded — you confirm the matches and catch anything you forgot to enter.
What is a bank reconciliation statement (BRS)?
A BRS is the working that explains any difference between your bank balance and your books — entries in one but not yet the other. In Finocket, reconciling is doing that working live: every statement line ends up either matched to a recorded entry or standing out as a gap to fix.
Import a bank statement
- Download a statement from your bank in whatever it offers — an Excel sheet (either .xlsx or the older .xls), a CSV or a PDF all work. You don't need to convert it first.
- Open Banking → Bank reconciliation and upload it.
- Give it a label you'll recognise later, like HDFC ****1234 — Jun 2026.
Finocket reads each row into a date, a signed amount (positive for money in, negative for money out) and the narration — and copes with the different column orders and headings banks use, so you don't reformat the file first.
It works out what kind of file you gave it by reading the file itself rather than trusting its name, so a sheet saved with the wrong extension still imports.
Excel statements and the preview
Excel workbooks (.xlsx and .xls) import the same way as CSV. Real bank exports carry a title block above the column headers — account name, period, a logo row — and that block is skipped: the header row is found wherever it sits, on whichever sheet holds the statement, and the bank is recognised from the headers just as it is for a CSV. If no bank format fits, a generic date / narration / debit / credit mapping is offered.
Nothing is saved when you pick the file. You see the rows first — how many were read, the date range, the debit and credit totals, and any lines that were skipped with the reason — and confirm before anything is written. A file that yields no rows tells you why: which sheet was read, where the header was looked for, and the closest formats that were tried.
Re-importing a range you already imported
Pulling overlapping ranges is the normal way this gets used — June, then mid-June to mid-July for the rest. Finocket recognises the lines it already holds and skips them, so nothing doubles up, and it tells you how many it skipped.
You can see which ones. Open show which ones beside that message and every skipped line is listed with its date, narration and amount — so you can confirm they really are the rows you already had rather than taking the number on trust. If more than fifty were skipped the list is shortened, but the count beside it is always exact.
A line is recognised by its date, its amount and its narration together, so two genuinely identical transactions on the same day are both kept — a pair of ₹500 UPI payments to the same shop is ordinary, and losing one of them would be worse than skipping neither.
Every upload gets its own tab
Each statement you import stays on screen as its own tab, showing the file's name, the day you imported it and which bank format read it. Importing a second statement opens it and leaves the first one exactly where it was — click its tab to go back. Nothing you import replaces anything you imported before.
Card statements carry a card icon and bank statements a bank icon, because a card payoff is matched across the two: the debit on your bank statement and the credit on your card statement are one event, and Finocket links them as a pair.
Recording several lines at once
Statement lines that have no match yet don't have to be entered one at a time. Tick the ones you want — or use the checkbox in the header to take everything on screen — and choose Review and record.
The review shows exactly what would be created before anything is written: each line as an expense or a receipt, its category, and every customer or supplier that does not exist yet. Finocket reads the payee out of the narration, so UPI-NARMADA RESTAURANTS -PAYTMQR1IBR3NDGD9 is proposed as Narmada Restaurants rather than left as it is. A name is created once however many lines mention it.
Untick a line to leave it for later, or mark it as not a business transaction — an owner's personal transfer, say — and it stops appearing every time you reconcile.
Choosing who a line belongs to
Reading the payee out of the narration is a guess, and it fails on plenty of real statements. On every line in the review you can choose the client or supplier yourself and add a note in your own words.
The picker knows which way the money went: a payment out offers your suppliers first, money in offers your customers, and the other side is still there under a heading because a supplier does occasionally refund you. Search by name, GSTIN or phone.
Choosing somebody does more than fill a box. Finocket then stops guessing entirely for that line — it will not read a name from the narration and it cannot create a second record for a firm you already have. It is also how a receipt that names nobody becomes recordable: pick the customer and the warning clears in front of you.
Your note is added after the bank's own narration rather than replacing it, so the statement text you will reconcile against later is still on the record.
Two things the review will tell you rather than guess at. A line dated inside a period you have locked is shown and left alone, so reconciling an earlier year never rewrites books you have already filed; the owner can move the lock date in Profile → Business if that is what they want. And a receipt whose narration names nobody needs a customer chosen before it can be recorded, because a receipt in Finocket always belongs to someone.
Cash taken from an ATM is recorded as a transfer to Cash, not an expense — it has not been spent, it has moved between two of your own accounts.
How matching works
For every statement line, Finocket suggests the closest entry already in your books — a customer payment for a credit, an expense for a debit — looking a few days either side of the statement date for the same amount. If the suggestion is right, Confirm match in one tap and the line marks reconciled. Matched wrongly? Unmatch and pick again.
Lines with nothing to match stand out — and that's the point. An unmatched credit usually means a receipt you haven't recorded yet; an unmatched debit, a bill still to enter. Record the missing entry (press ⌥P/Alt+Shift+P or ⌥E/Alt+Shift+E), come back, and match it.
Bank rules — auto-categorise recurring lines
For lines that repeat every month — a Swiggy spend, your office rent, a recurring subscription — set up a bank rule so Finocket recognises them for you. A rule watches for narration text (case-insensitive, e.g. SWIGGY), an optional amount range, and a direction (money in or money out), and when a line matches every condition it suggests an expense category, a specific match, or the client or supplier the line belongs to.
The party a rule chooses behaves differently from the other two, on purpose. A bank line has no record yet, so there is nothing to attach a customer to — instead the review sheet opens with that party already chosen on every matching line, and you change it or leave it before anything is written. So a rule for SWIGGY can say both “this is a food expense” and “it is owed to Bundl Technologies”, and you stop re-typing the second one every month.
Crucially, a rule only suggests. It shows a chip on the line with one-tap Accept — which books the categorised expense or links the match through the normal path, fully audited — or Dismiss. Nothing is ever posted silently, and a rule with no conditions matches nothing (so it can never fire on every line). Build a rule in two taps from any unmatched line with ＋ Rule, or manage them on the Workflows screen, which is the AI workflows icon in the system dock on a tablet or computer rather than a menu row.
Recording UPI transactions
Record UPI receipts as payments with mode UPI and UPI outgoings as expenses paid by UPI. On the statement they appear as ordinary credits/debits and match the same way — the Cashbook's UPI tab then agrees with your bank.
Access & control
Statements and matches are owner-scoped: the owner imports and confirms. An invited accountant or teammate can open the reconciliation and see where things stand, read-only. Banking is a module — turn it on under Settings → Modules & features if the screen isn't visible.
Related: Day Book, Cashbook & Outstanding, Payments & TDS.