When a Hellenic 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. A statement that spans several pages is handled as one continuous record. The engine collates all pages of the uploaded document, stitches the transaction table across page breaks, and verifies the running balance from the first row to the final closing figure printed on the statement. A break in pagination does not create duplicate header rows or orphaned entries in the output.
However your Hellenic Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. During export, every column extracted from the transaction table is mapped to a standard field: the date column lands in one field, the description in another, the debit and credit amounts in their own columns, and the running balance in its own column. This mapping is applied automatically, so the resulting file matches the structure expected by your accounting package without rearranging columns by hand. The mapping is consistent across every statement from the same issuing layout, which means you review it once and every subsequent statement from that same source lands identically.
Whether you need your Hellenic Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. The file you receive is built for the next step in your workflow. You can download the converted data as an Excel workbook for analysis or manual review, as a clean CSV for bulk import into a ledger or data tool, or as a QBO file formatted for direct ingestion into QuickBooks Online. There is no intermediate clean-up step inside the tool: the exported file reflects the verified transaction table, with the column mapping you confirmed, ready to be moved into your books.