When a Bordier & Cie statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. When a statement runs several pages, the same format continues throughout. The engine reads across page breaks without losing the transaction table. Running balances picked up mid-page stay in sequence, so the full period arrives in one continuous export.
If the running balance on your Bordier & Cie statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The engine verifies the running balance against the statement's own printed closing figure, line by line. A row that does not add up is flagged for review rather than discarding the file: you see the exact line and the mismatch, and the rest of the data remains intact. This check repeats for every page, so a single misread partway through a multi-page statement cannot hide.
If the Bordier & Cie statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements are read with OCR, then subjected to the same running-balance verification as any other document. If the scan misread a 3 as an 8, the balance will not add up; the flagged row lets you correct it without redoing the whole file. When the statement is clear enough to pass verification, the columns are mapped into the export automatically. You download the file as Excel, CSV or QBO, with every column placed for your ledger. No template to configure, no column to name, and no layout to describe: the engine identifies the issuing bank's layout on its own and organises the extracted table accordingly.