If the running balance on your FCM Bank Limited 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 extracted row is checked against the statement’s own printed closing figure before the file ever reaches your machine. The engine reads the running-balance column and recalculates it from the first transaction to the last, comparing the result with the figure the bank printed at the foot of the statement. A mismatch raises a flag on the suspect row rather than rejecting the whole file, so you can review one line instead of starting over from a fresh upload.
When an FCM Bank Limited 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 long the engine treats it as a single dataset, not as a collection of disconnected pages. It reassembles the transaction register across page breaks, keeping the running balance continuous and catching any carry-forward error a page boundary may introduce. The result is one clean table rather than a set of tables you would need to stitch together by hand.
Once your FCM Bank Limited statement is uploaded, what you get back depends on which export format you actually need next. Once the reconciliation is clean the file can be exported in the format your downstream workflow actually needs. Choose Excel for analysis in a spreadsheet, CSV for ingestion into another system, or QBO for direct import into QuickBooks Online. The column mapping adjusts accordingly, so the export lands with the right headers and the right data types the first time.