If a transaction description on your BRD - Société Générale statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Upload a statement document. The engine reads the transaction table automatically, identifying each column and row without any manual template setup. When a transaction description runs long, it often occupies several lines on the statement page; the layout engine reconstructs these wrapped descriptions into a single, complete transaction record rather than splitting the detail across multiple exported rows. The result is a clean table where each line in the export represents exactly one entry from the original, no matter how many printed lines it needed.
If the running balance on your BRD - Société Générale 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 then verifies every row mathematically. It recalculates the running balance line by line against the statement's own printed closing figure, so a single misread digit surfaces immediately. If a row does not add up, it is flagged for review rather than silently accepted; the rest of the file remains available, and you can correct just that one entry before finalising the export.
If the BRD - Société Générale 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. For a statement that was scanned or photographed, the engine applies OCR to extract the transaction table from the image. That same running-balance check then catches anything the scan misread: a 3 mistaken for an 8 breaks the arithmetic, marks the row, and preserves the integrity of the rest of the output. Export the verified data to Excel, CSV or QBO when you are satisfied, with columns mapped consistently into the format your ledger expects.