When a Citadele banka 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 spans several pages, the engine first detects the repeating row structure that signals a table of transactions. It follows that structure across page breaks so a single long account run is not split into separate chunks. Column alignment is tracked independently per page, and any line where the printed running balance fails basic arithmetic is marked in the output rather than rejected silently. You always end up with one uninterrupted table, whether the original came as a two-page export or a ten-page scanned bundle, and you can trust that the figures were verified as they were read.
However your Citadele banka statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. The exported file does not force a single layout on you. Before you download, you choose which source columns to include and where each one maps in the final Excel, CSV or QBO file. Dates stay recognisable dates; amounts keep the decimal precision shown on the statement. You are not fixing a global template after the fact: you align the columns once for this batch, and that mapping applies cleanly to every row in the extracted table.
If the Citadele banka 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 statements are routed through the same extraction and verification pipeline as a born-digital file. The engine applies optical character recognition to locate the transaction grid, then runs the running-balance check line by line. A 3 misread as an 8 breaks the balance and gets flagged, so you know exactly which row needs attention, while every other row stays intact and ready for export.