If the running balance on your SozialBank 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. Every converted transaction row is checked against the running balance printed on the statement. The closing figure from the original document becomes the reference point: if a single row does not add up, it is flagged for review rather than silently accepted. The rest of the file proceeds as normal, so one misread character does not halt the entire reconciliation.
If a transaction description on your SozialBank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description is long enough to wrap across multiple lines, the engine recognises the continuation as part of the same record. It reassembles the split text into a single description field, so the payee, reference or narrative remains whole in the exported table and nothing is dropped or duplicated.
If your SozialBank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Multi-page statements are read as one continuous ledger. All pages are processed together, the running balance is tracked across page breaks, and the final export gives you a single table covering every line. You can map the extracted columns to the headings your accounting software expects, then export the result as Excel, CSV or QBO in one step.