If a transaction description on your GLS Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a statement document contains transaction descriptions that wrap across multiple lines, the engine does not mistake each line for a separate record. It groups the continued text with its parent transaction, so a long memo or reference line stays whole in the output instead of spilling into the next row.
When your GLS Bank 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 scanned or photographed statement passes through optical character recognition before extraction begins. The running-balance check then verifies every figure the OCR returned, flagging any row where the numbers do not add up while leaving the rest of the file intact. That means you can rely on the converted data without rekeying from the original image.
When a GLS Bank 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. Statements that span several pages are read in full with no practical page limit. The engine identifies the transaction table across page breaks, removes the headers and footers that repeat mid-document, and maps every column into your chosen export layout. You choose Excel, CSV or QBO as the output; the columns populate directly, so the file drops into your workflow without reformatting, and the closing balance matches the printed figure on the last page before you hand it off.