When a VTB Capital 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. Upload a statement document that runs several pages; the engine handles it as a single continuous record. There is no page limit and no need to split files before you start. The transaction table is stitched across page breaks, so the running balance that appears at the foot of one page is checked against the opening balance at the top of the next.
Should a description on your VTB Capital statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions that wrap across multiple lines are a common source of split rows in manual copy-paste workflows. Convert·Into reads the full layout and groups wrapped text back into the correct row before extraction. The result is one clean line per transaction, with the description field intact and no stray fragments in neighbouring columns.
Whether you need your VTB Capital statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. When the file is clean, you map the columns you see to the export fields your next step requires: date, amount, description, reference, running balance. The engine suggests a mapping based on the layout it detected; you can adjust it before you export. Choose Excel, CSV or QBO, and the output lands arranged exactly as you mapped it. Every balance figure is verified against the statement's own printed closing figure line by line while the conversion runs, so a row that fails the check is flagged for review rather than being written into the export silently.