Whichever order your CIMB statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The structure of the export is built around the columns your accounting workflow actually needs. You decide where the date, description, money in, money out and balance columns land, and you can reorder or rename them before the file is created. The mapping screen shows you the columns that were found in the statement alongside a preview of the export layout. Drag a column into a different slot, give it a label your ledger recognises and leave out anything you do not need. Every transaction row keeps the fields aligned exactly as you set them, so the file opens in your accounts package with no reformatting required.
When your CIMB statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. A scanned or photographed document is read with optical character recognition before extraction begins, and the same verification logic that runs against a clean digital file is applied to the result. The engine checks the running balance figure at every row against the previous balance and the transaction amount. If a character was misread, the tally breaks at that specific row rather than somewhere downstream. A flag is raised and the row is held for your review; every other transaction proceeds to the export normally. This means a single unclear scan does not hold up the whole batch.
When a CIMB 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. Long statements that span several pages are treated as one continuous ledger. The engine detects page breaks, picks up the columns where they left off and stitches the running balance across the divide without resetting it. The verification logic runs front to back, so a mismatch on page three of six is caught at its source. You upload the whole document at once and receive a single export file with every transaction in sequence and the closing balance matched to the statement's printed figure.