Whichever order your National Bank of Pakistan statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before exporting, the engine maps each extracted column into the corresponding field in your chosen format. The date column becomes the transaction date, the narration column becomes the description, and debits and credits are placed into separate amount columns. You can review this mapping on screen and adjust it: for example, drag a reference number into the memo field or reorder columns to match your ledger’s import template. Once the mapping is correct, the export populates every row consistently, so you do not need to realign fields afterwards.
When your National Bank of Pakistan 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. Scanned and photographed statements are read with OCR as soon as the file is uploaded. The engine processes the image, locates the transaction table, and extracts the rows the same way it handles a clean digital file. A running-balance check then verifies every line against the statement’s own closing figure, flagging any row where a misread digit has caused the totals to break. This lets you spot an extraction error on a specific transaction instead of rechecking the whole statement.
When a National Bank of Pakistan 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 conversion handles the full document without splitting it into separate jobs. The engine follows the table across page breaks, keeping columns aligned and suppressing repeated headers. You receive one complete transaction history, with the running balance carried forward from each page to the next, and the final closing balance checked against the printed figure on the last page.