If a transaction description on your Bank Gutmann statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. A statement document is uploaded as it arrives. Transaction descriptions that run long and wrap across multiple lines are common in layout‑driven formats, where a single entry can occupy two or three printed rows. The engine reconstructs each transaction as one logical row, re‑joining the wrapped text and aligning it with the correct date, amount and balance columns. The process runs without a template: the engine identifies where each description begins and ends by reading the column boundaries in the document itself, so a split memo is reassembled automatically and the full narrative stays with the right line item.
However your Bank Gutmann statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Once the transaction table is rebuilt, map each column into the right place in the export. The engine presents a clean table with standardised headers; you assign which source column feeds the date, description, debit, credit and balance fields in the output. The mapping is a direct column‑to‑column assignment, no formula required, and every row carries the complete reconciled running balance. The result is a flat, sortable ledger ready for your existing workflow, whether the destination is Excel, CSV or QBO.
When a Bank Gutmann 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 run several pages long are handled in a single pass. The engine reads the document end to end, pulling every transaction row across all pages into one continuous table. The running balance is verified line by line against the statement’s own printed closing figure, and anything that does not add up is flagged on that specific row so you can review it without rejecting the rest of the file.