When your March Bank statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. When the source is a scan or a photograph rather than a clean digital file, the engine applies optical character recognition to pull out the figures and text. It then runs the extracted numbers through the same running-balance check it uses on every statement: each row's printed running total is verified line by line against the one the maths produces, so a misread digit that breaks the balance is caught before the data reaches your ledger. No extra step is needed from you; the same upload path handles both camera shots and machine-generated files.
Whichever order your March Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Once the transaction table is extracted and verified, the engine maps each column into the export's own structure so dates land in date columns, amounts in amount columns, and descriptions in memo fields without manual dragging or reordering. If the statement splits debits and credits into separate columns, the export can combine them into a single signed-amount column, and vice versa. The final file arrives ready for import into your accounting package as Excel, CSV or QBO, with no stray characters or shifted fields left to fix.