If the running balance on your BPM Bank 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 statement’s own printed closing figure is the source of truth. Every row of extracted data is checked against it; the running balance must tally from the first transaction to the last. If a single digit was misread, the check flags that row. You review the flagged item, correct it if needed, and proceed, rather than having the whole file rejected for a small scan artefact.
If a transaction description on your BPM Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions are long, they often wrap across two or three lines in the original document. The extraction engine reads these as a single entry, not as separate rows. It preserves the full narrative text and reconnects it to its transaction line. In the export, that combined description lands cleanly in one cell. The date, amount and balance stay aligned with it, so your ledger columns remain consistent all the way down, whether you export to Excel, CSV or QBO.