UK bank statement formats, and where they trip people up.

Seven have a dedicated parser: Barclays, HSBC, Lloyds, NatWest, Monzo, Starling and Mettle. Beyond those a generic reader matches columns by name, which covers Santander, Tide, Nationwide, Halifax, Co-operative and most others. A named parser mainly buys a correct bank badge and protection from format changes, not new capability. So the answer to “which banks are unsupported” is: very few.

Yes, from Barclays, Chase, Lloyds, Mettle, Monzo and Revolut, but only when every row agrees with the balances printed on the statement. A PDF that doesn’t add up to the penny imports nothing and says which row disagreed, because guessing at a layout is how wrong figures reach a trial balance. Scans and photos are refused. Bank not listed? When Entrio refuses its PDF, send it to us in one click and we’ll usually add the bank within two working days. CSV and Excel remain the most direct route.

Yes. .xlsx is converted on upload. Legacy .xls is refused at the form rather than half-read, which is the safer failure: an error you can see beats a file that imports with the wrong columns.

05/01/2025 is read as 5 January, the UK interpretation. It is the right default here and the wrong one for a US-formatted file, so a file exported with American dates needs checking before import.

They are detected and flagged, never converted. A EUR line read as sterling puts €1,200 into the books as £1,200, the journal still balances, and nothing looks wrong. So Entrio names the currencies it found on the face of the report and in the export checks instead of guessing an exchange rate.

Separate fee columns. Revolut Business and Wise put the transaction in one column and the charge in another, and that fee is a real allowable expense that does not currently enter the books. Starling and Tide do the same on FX. It is on the list; until then those rows want a manual look.