Whichever order your Russtroybank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the transaction table has been isolated, the engine maps each column into the right place in the export. Date, description, debit, credit and balance are recognised by their content and header labels, not by a fixed position, so the same logic works regardless of the statement’s column order. You can review and reorder the mapped columns before the export leaves the tool. Every column the statement provides is carried through; nothing that appears in the original table is silently dropped. The mapping is deterministic: if a column header reads “Value date” while the posting date sits elsewhere, the engine keeps both, labels them separately, and lets you decide which one flows into the date field of your output.
If the running balance on your Russtroybank 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 converted file is verified against the statement’s own printed closing figure. The engine reads the running balance column line by line and checks that each row’s balance equals the previous balance plus the row’s own credit less its debit. If a single row does not add up, that row is flagged for review; the rest of the file stays intact and ready to use. You see exactly which transaction failed the check, so you can correct a misread digit or a stray character without retouching hundreds of clean rows. The closing-balance check is the same arithmetic a reviewer would do by hand, applied to every row, every time.
When a Russtroybank 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. Statements that run several pages long are handled in one pass. The tool reads across page breaks, removes repeated headers and running totals printed mid-statement, and reassembles the full transaction list into a single continuous table. You get one clean export covering the whole statement period, not one file per page. A multi-page document takes no more manual steps than a single-page one: upload the file, check the flagged rows, and export.