SalonLogic ← Help Centre
Banking
Overview Step 1 — Upload CSV Step 2 — Review Matches New expenses — categorisation
Other Guides
Bills & suppliers → Finance Dashboard →
SalonLogic Pro

Banking

Import a bank statement, match transactions to unpaid bills, and categorise anything new.

Overview

Import Bank Statement

This is currently the only Banking feature built — there's no separate reconciliation screen or expenditure categorisation area beyond what this wizard itself does. Owner's Drawings is built, but lives on the Finance Dashboard alongside VAT and Tax Accruals, not here — see Finance Dashboard.

The wizard has three steps: Upload CSV, Review Matches, and Complete Import.

🔴
Known issue — Cancel doesn't work, and refreshing duplicates the import. Clicking the page-level Cancel button on Step 2 does not clear the import. Refreshing the page afterwards doesn't reset it either — it re-runs the import on top of what's already there, so the transaction count keeps climbing. Right now there is no reliable way to back out of an import once you've reached Step 2. Be cautious with a real bank statement until this is fixed — consider testing with a small file first, and avoid refreshing or navigating away mid-import.
Banking

Step 1 — Upload CSV

Go to Banking → Import Bank Statement. Choose your bank from the dropdown, then drop your statement CSV into the upload area or click to browse for it.

Import Bank Statement — Step 1, Upload CSV, bank selector and drag-and-drop area

Step 1 — Upload CSV, with a bank selector (Starling Bank shown) and drag-and-drop upload area

Click Upload & Process once a file is selected to move to Step 2.

Banking

Step 2 — Review Matches

Every transaction in the file is sorted into one of three groups, each shown as a count card at the top of the screen:

GroupWhat it means
Auto-MatchedThe transaction amount matches an unpaid bill exactly, and the payee name matches the supplier closely enough to confirm automatically
Need ReviewThe amount matches an unpaid bill, but the payee name doesn't match the supplier closely enough to confirm on its own — a human needs to say yes or no
UnmatchedNo unpaid bill matches this transaction at all — it's treated as a new expense (see Categorisation, below)

Auto-Matched Transactions

Each row shows the transaction date, payee, the bill it was matched to, the amount, and a confirmation that it's matched.

Auto-Matched Transactions panel — date, payee, bill invoice number, amount, matched confirmation

Auto-Matched Transactions — exact amount and a clearly matching supplier name, confirmed without input

Suggested Matches — Please Review

Where the amount matches a bill but the payee name is close rather than identical — for example a transaction from "ABD Ltd" against a bill owed to "ABC Ltd" — the system flags it for review rather than guessing. Each row shows a Bill Amount / Transaction / Difference comparison, with Confirm Match and Not a Match buttons.

Suggested Matches - Please Review panel — bill amount, transaction amount, difference, confirm match and not a match buttons

Suggested Matches — a close-but-not-exact supplier name match, with the amount comparison shown for you to judge

💡
This is a sensible safety net — matching only on amount could easily pair the wrong supplier's payment to a bill if two suppliers happen to charge the same amount. Reviewing the name mismatch before confirming avoids that.
Banking

New Expenses — Categorisation

Every Unmatched transaction is treated as a new expense rather than a bill payment, and needs a category assigned before the import can complete. These are listed under New Expenses - Need Categorization, with a count badge showing how many are waiting.

New Expenses - Need Categorization panel — date, payee, amount, category dropdown, remember category checkbox

New Expenses — each row needs a category before the import can finish; "Other" is the default

Each row shows the transaction date, payee, and amount, with a Category dropdown defaulted to "Other." Below it, a Remember "[Payee]" = this category checkbox saves that payee-to-category mapping, so future imports from the same payee are categorised automatically rather than asking again every time.

💡
Ticking "Remember" for recurring payees — a card processor, a regular software subscription — means you only categorise that payee once. Worth doing this consistently from the start to save time on every import after the first.