Whichever order your Ecobank Ghana statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The statement rows are mapped into an output table automatically. The engine identifies the columns that hold dates, descriptions, amounts and the running balance, then places each one into the correct field in the export. You can review the mapping before export and adjust any column assignment. When a statement prints debits and credits in separate columns, both are brought into a single signed amount field. The mapping step ensures the export columns match your ledger's structure without manual reordering.
If your Ecobank Ghana statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that span several pages are handled as one continuous record. The header row is identified once; repeating page headers, continuation lines and summary banners are stripped, not duplicated. Every transaction row across all pages is verified against the last printed closing balance. A misread on page four does not go unnoticed: the same line-by-line arithmetic check ties every entry back to the statement's own end-of-period figure.
If the Ecobank Ghana statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned or photographed statements are read with OCR before extraction begins. The engine lifts the transaction table from the image and runs the identical reconciliation check used on native files. A row that does not add up is flagged individually, so one unclear figure from a creased scan does not block the rest of the file. You can correct a flagged amount directly in the review step and export the clean table to Excel, CSV or a QBO-ready format.