If a transaction description on your Luminor 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 transaction description wraps across several lines inside a cell, the engine keeps the whole entry together as one record. It recognises that the text belongs to a single row even when a line break makes the raw data look split. No fragments end up as orphaned lines, and every transaction stays complete in the export.
When your Luminor 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 arrives as an image, not a data table. Optical character recognition reads the printed figures and text, then the running-balance check verifies every line against the statement's own closing total. If a smudge or a fold causes a misread, the discrepancy is flagged on that row. The file still converts; only the problem line needs a second look, so you are not forced to retype the entire document by hand.
When a Luminor 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 as a single continuous ledger. The engine aligns columns across page breaks and stitches the transaction table end to end, preserving the sort order and running balance without introducing gaps or duplicate header rows. When the extraction is complete, the mapped columns move into the chosen export format. You pick the output: Excel with one transaction per row and every column broken out, a plain CSV for ingestion into another system, or a QBO file structured for import. Column headers are assigned to the fields your workflow expects, and the same reconciliation check runs on the finished file, so the exported closing balance matches the final figure on the last page of the statement.