When a Banque Raiffeisen 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. When a statement runs several pages, the layout often repeats with a header on each page, a running subtotal that carries forward, and a final closing balance on the last sheet. The conversion engine reads the document as a continuous table, not as isolated pages. It recognises repeating headers and strips them automatically, so the export contains one clean transaction list without broken rows or duplicated column titles. The running balance is tracked across page breaks; if a carry-forward figure does not tie to the next page, the row is flagged for review. The full closing balance printed on the statement is verified against the reconstructed ledger, so the converted file matches the original document exactly, even when it spans ten or twenty pages.
However your Banque Raiffeisen statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping places every extracted field in the right slot before export. The engine identifies the standard columns (date, description, debit, credit, balance) from the statement's layout and presents them in a preview grid. You can adjust the mapping for any column with a single click, for example moving a reference code into a dedicated notes field or reordering columns to match a template. The mapping persists for future uploads from the same layout, so repeat conversions follow the same structure without reconfiguration.
If a transaction description on your Banque Raiffeisen statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across multiple lines are a common cause of split rows in a naive extraction. The engine reads the full block of text that belongs to a single transaction, not just the first line. It recognises when a description continues onto a second or third line and merges the text into one cell, keeping the amount, date and balance on the same row. The running-balance check confirms that nothing was lost or duplicated when the lines were joined, so wrapped descriptions do not fracture the ledger.