When a Targobank 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. Multi-page statements carry the same account number and a running balance that must be checked across every page. The engine collates all pages of a statement document into one continuous transaction table. The same row-level reconciliation that works on a single page extends naturally: each line's printed balance is compared to what the engine computes, page after page, and any break is flagged.
Once your Targobank statement is uploaded, what you get back depends on which export format you actually need next. Column mapping is configurable once and reused on every future conversion of the same layout. Tell the engine which source column becomes the date, the description, the amount, and the running balance; it remembers that mapping for every statement document that arrives later. The export step then writes whatever columns you need, in the order you need them, to the exact format you are working toward. Choose Excel for a clean ledger with colour-coded summary headers, CSV for a plain table ready to import into other systems, or QBO for a file mapped directly to QuickBooks fields. Nothing is hidden; the mapping screen shows every column the engine extracted, and you can include, exclude or relabel any of them before export.