When an AikBank 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. Statement documents that run across several pages are handled as one continuous transaction list. The engine reads every page in sequence, stitches the tables together, and maintains a single running-balance check from the first row of page one to the closing figure printed on the final page. Nothing is split into separate exports, and no manual joining of partial CSVs is required. The verification logic crosses page breaks transparently; a discrepancy that spans pages is flagged exactly once, at the row where the arithmetic first fails.
However your AikBank 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 statement is mapped into the output file according to its function: dates stay in a date column, debits and credits are separated if the statement presents them that way, and the running balance is placed alongside its matching transaction line. Numeric values are normalised so that Excel and CSV totals sum correctly, and currency symbols and thousand separators are stripped during conversion. The mapping is applied automatically once the engine identifies the statement's layout; there is no column-picker to configure or field-order to memorise.
If the AikBank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statement documents are read with OCR before extraction begins. The OCR engine turns a page image into machine-readable text and numbers, and then the same running-balance verification that runs on clean digital statements is applied to the scanned result. If a stray mark or a low-resolution photo causes a digit to be misread, the arithmetic no longer adds up and that specific row is flagged for review. The rest of the statement is preserved, and there is no file-level rejection when a single row fails verification.