When your Investitionsbank Berlin 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. A statement document that was scanned or photographed arrives as a flat image, not as a data file. The engine reads the image with OCR, identifies the transaction table and extracts every line. The running balance is then verified against the closing figure printed on the statement itself, line by line, so any character the scan misread is flagged for review before it reaches the ledger.
Whichever order your Investitionsbank Berlin statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. You control which columns appear in the export and where they land. The engine presents the extracted fields and you map them to your target layout: date to the date column, debit and credit to separate columns or a single amount column, and the narrative to the description. The same mapping is offered for Excel, CSV and QBO, so the file lands in your working format without further rearrangement.
If your Investitionsbank Berlin 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 table. The engine threads transaction rows across page breaks and carries the running-balance check straight through the final page. No header row, subtotal line or page number interrupts the extraction, so a statement that spans several pages still exports as a single transaction register.