When a Laboral Kutxa 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 document that runs several pages long is not a problem. The engine reads the whole file as a single continuous table, stitching the pages together automatically. There is no need to split the document beforehand or to configure anything per page.
However your Laboral Kutxa statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. During the conversion, every column found in the statement table is mapped into a standard field in the export. You can review and adjust those assignments before you download: drag the date column, the description column, the debit and credit columns into the order that matches your ledger or software. If a statement presents debits and credits in a single signed column, the mapping can split that into two columns for the export. If the amounts arrive in separate columns, they stay separate. This mapping step takes nothing more than a drag to reorder or a click to reassign, and it saves manual reformatting after the file leaves the converter. The layout of the numbers on the original page does not constrain the shape of the exported data.
If the Laboral Kutxa 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. A statement that was scanned from paper or photographed on a phone is read with optical character recognition. The engine looks at the image, lifts the transaction table, and verifies the running balance against the printed closing figure, row by row. If a 5 is misread as a 6 or a column drifts because of a skew, the balance arithmetic will no longer add up, and that row is flagged for review. You correct the flagged values before export rather than discovering the discrepancy days later inside a reconciled ledger.