If a transaction description on your Hypo Noe Landesbank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions can wrap across several lines, splitting one record into what looks like two. The engine recognises the layout pattern that anchors each entry, typically a date or amount column, and reassembles the full description before extraction begins. The result is a single row per transaction, with the complete narrative in the description field.
If your Hypo Noe Landesbank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. When a statement spans multiple pages, the engine processes every page in sequence without treating a page break as a file boundary. The running balance is verified line by line across the entire document. A mismatch on page four is caught with the same rigour as a mismatch on page one, and the specific row is flagged rather than the whole file being rejected.
If the Hypo Noe Landesbank 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. Scanned and photographed statements are read with optical character recognition. The engine then runs the same verification: the running balance is recalculated from the extracted figures and checked against the closing balance printed on the document. Any character the scan misread, a 3 taken for an 8 or a decimal point lost in a shadow, is surfaced as a flagged row for review before export to Excel, CSV or QBO.