When a Bank of Georgia 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 document runs several pages long, the engine treats it as one continuous record, not as a set of disconnected pages. It reads across page breaks and carries forward the running balance from the foot of one page to the head of the next. The extraction never splits a transaction that happens to straddle a page boundary. If the printed closing figure on the final page does not match the sum of all the rows, that mismatch is flagged. There is no extra step for a multi-page file; you upload it once and the whole ledger is extracted in a single pass.
However your Bank of Georgia statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Every column the engine extracts is available for mapping before export. You decide which source column feeds each destination field: the transaction date, the description, the debit and credit amounts, and the running balance. The mapping step uses the actual column headers found in the statement, so there is no guesswork. You can reorder columns, omit ones you do not need, and verify that the closing balance lands in the correct field. The same mapping logic applies whether you are exporting to Excel, CSV or QBO, and the choices you make are preserved for consistency across files.
Whatever the running balance looks like on your Bank of Georgia statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. The engine verifies the running balance line by line against the statement’s own printed closing figure, not against an independently calculated expectation. Every row is checked: its stated balance must equal the previous row’s balance plus or minus the transaction amount. If a single row does not add up, that row alone is flagged for review; the rest of the extraction remains intact. You see exactly where the arithmetic breaks, which lets you correct a misread figure without reprocessing the entire file. This verification runs on every statement, whether it is a native digital document or a scanned image read through OCR.