Import a bank statement

Bring your bank activity in from a statement file:

1. Go to Ledger › Banking › Statements.
2. Optionally set the currency (it defaults to Auto-detect Currency).
3. If you're uploading a CSV, OFX or QFX, pick the account it belongs to from the CSV/OFX account dropdown. A PDF statement names its own account, so you can leave this alone for one.
4. Click Upload Statement and pick a PDF, CSV, OFX, or QFX file: you can select several at once.

A PDF is read in the background: the row shows Processing, then flips to completed once TALISK_HQ has pulled out the transactions and checked them against the statement's own balances. CSV and OFX files import right away.

Extracted transactions land on the Transactions tab ready to categorize and match. Everything belonging to one account sits in one list in date order, whether it came from a statement, a connected bank feed, a file import or your own typing: under each date is a small note saying which. Each statement row lets you rename its account, Move it to another account, open it to fix any rows that don't tie, or delete it.

If a connected bank feed already delivered some of a statement's transactions, TALISK_HQ links those existing lines to the statement instead of importing them a second time. The statement still accounts for every line it lists, and any work already done on the feed's copy (a category, a match, a reconciliation) is left exactly as it was. On a line nobody has worked yet, the statement's own transaction date wins over the feed's posted date, which usually runs a day or three later.

Move really does move the transactions, not just the name on them, so use it when a statement was filed under the wrong account. TALISK_HQ refuses the move once any of those transactions has been categorized or matched: their entries are already recorded against the account they are on now, and shifting them would leave your books saying one thing and the transaction another. Clear the categories or unmatch first, then move. A line that actually came from your connected bank feed stays on its own account either way: the move releases its link to the statement instead of carrying it along.

If you skip the account dropdown on a CSV, its rows still import: they sit in their own CSV Import group instead of joining an account.

If the statement's currency isn't your book's, its transactions still import, but TALISK_HQ doesn't create a bank account for them: those lines would post at face value with no conversion. A health card on your dashboard lists them so they aren't missed. If the currency was detected wrongly, correct it on the statement and the account is created as usual.