When an Ukrgasbank 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 runs several pages, the engine reads it as one continuous record. It follows the transaction table across page breaks, keeping rows aligned and the running balance intact. There is no need to split a multi-page file before upload, and no limit on the number of pages a single statement document can contain: the full statement is processed in one pass.
If the running balance on your Ukrgasbank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every conversion includes a line-by-line verification of the running balance against the printed closing figure on the statement. A row that does not add up is flagged for review rather than rejected outright, so you can inspect the discrepancy, correct it in the source, or re-export without losing the rest of the work. This check catches misread digits, skipped rows and layout shifts that would otherwise go unnoticed until reconciliation.