When your Kenya Commercial Bank Group 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. Upload the statement document. The engine will handle it whether the file was exported directly from a banking portal or scanned on a desktop machine. Scanned and photographed statements are read with OCR, and every extracted figure is then checked against the statement's own printed closing balance line by line. If a crease, a shadow or an imperfect scan misreads a digit, the running balance sum will not match and the row is flagged for review. The file is never rejected wholesale because of a single unclear number. You keep every transaction; you just know where to double-check.
Whether you need your Kenya Commercial Bank Group statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. During export, the extracted transaction table is mapped into a clean ledger format. Choose Excel, CSV or QBO, and the columns are arranged exactly as your downstream workflow expects. Date, description, debit, credit and balance each land in a dedicated field. There is no template to configure and no manual column assignment. The mapping stage is designed so the exported file drops straight into your reconciliation process without further reshaping.
If your Kenya Commercial Bank Group statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Multi-page statements are handled in the same pass. The engine follows a statement across page breaks, carrying forward the running balance so that no mid-document reset or header row disrupts the verification. Rows continue to be ordered as they appeared on the page, and the closing figure at the end of page thirty carries the same scrutiny as the one on page one.