Using Pennyweight in the UK and Europe
On this page
If you bank in the UK or elsewhere in Europe, you can keep each account in Pennyweight in its own currency and fill it from the files your bank already gives you. Your AI reads the file and adds the transactions after you approve a preview. The general path is in use Pennyweight without a bank link.
Why there's no bank link
Pennyweight links banks in the US only. A UK or European account is a manual account that you fill from statements and exports.
What your bank gives you
Download options differ from bank to bank, so check your own. Some examples from banks' own help pages:
- Monzo exports transactions from its app as a PDF, CSV or QIF file. For QIF, see import QIF files.
- HSBC UK offers statements as PDFs going back up to 6 years. Its Excel and CSV downloads come from the transaction list.
- Commerzbank exports your online-banking transactions as PDF or CSV. It notes that these are not complete account statements.
- ING offers MT940 end-of-day statements for download in InsideBusiness Payments. Its camt.053 guide describes camt.053 as the ISO 20022 message for end-of-day statements. See import MT940 or camt.053 statements.
Your AI opens the file and sends Pennyweight the transactions as rows. Pennyweight has no reader of its own for PDFs, QIF, MT940 or camt.053. Whether your AI can open a particular file depends on your AI app. For PDFs, see import a PDF statement.
Decimal commas, semicolons and day-first dates
Handelsbanken's CSV format, for example, separates columns with semicolons and writes amounts with a decimal comma. When your AI sends the rows itself, Pennyweight takes each date as YYYY-MM-DD and each amount as a plain number, so your AI converts them first: 2.150,00 becomes 2150.00, and 31.01.2026 becomes 2026-01-31.
Pennyweight can also read a CSV file directly. It detects semicolons and decimal commas, and it converts dates written DD.MM.YYYY or DD/MM/YYYY once your AI names that order. It never guesses the order, and a date it can't convert blocks the whole file. The details are in bank CSVs with decimal commas, semicolons and day-first dates.
Pounds, euros and other currencies
Give each account its currency when you add it, such as GBP or EUR. If you don't, the account takes its ledger's currency, then the workspace's. Each amount is stored in its own currency and is never converted. Totals that combine your ledgers, such as your net worth, keep the figures per currency and add one figure in your display currency; see choose the currency for totals across ledgers. When your AI sends rows in a currency other than the account's, the preview flags them before anything is saved. See accounts and totals in more than one currency.
How to do it
- Ask your AI to add the account with its currency, or add it in Settings under Accounts. See add a manual account.
- Share your bank's file with your AI and name the account it belongs to.
- For a new account, give the balance at the start of the statement. A manual account needs an opening balance before its first import saves. See set or correct an opening balance.
- Check the preview. It lists the rows, flags likely duplicates and shows the account's balance after the import.
- Say yes. Your AI reports how many rows were saved and the account's new balance.
Import eu-semicolon.csv into my Euro Account. It uses day-first dates and decimal commas. Show me the preview, then ask me once before importing.
My studio's euro business account isn't in Pennyweight yet. Add it as a EUR checking account called Atelier EUR in my Studio ledger, import statement.mt940 into it with the statement's opening balance, and ask me once before importing. Afterwards, tell me whether the account's balance matches the statement's closing balance.
What you'll see
For the first prompt, your AI either converts the rows itself or uploads the file with the day-first order named. Either way, it previews the transactions for your Euro Account. After you confirm, it reports how many rows were saved.
For the second, your AI adds the euro account and previews the statement's transactions. After you confirm, it reports the rows saved. It also reports the account's new balance, which you can compare with the closing balance on the statement.
Good to know
- Accounts added in Settings. The form's starting balance isn't recorded as an opening balance, so the account still needs one before its first import.
- Wrong direction? If the amounts went in with the wrong sign, your AI can remove the whole import and run it again. See undo an import. See balance looks wrong after an import.
- Your rules run on import. Your active rules categorize matching rows when the import is saved. To skip them, ask your AI to import without applying your rules. See who wins: you, your rules, or the bank.