Once your African Bank Limited statement is uploaded, what you get back depends on which export format you actually need next. Upload a statement document; the engine identifies the issuing bank and its layout automatically, so there is no template to configure. The transaction table is extracted and the running balance is verified line by line against the statement's own printed closing figure. Every field stays in its own column through to export. Mapping the columns into the format your ledger or filing system expects is a single configuration step: choose Excel, CSV or QBO, and the file lands structured exactly as you need it.
If a transaction description on your African Bank Limited statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that run long and wrap across multiple lines are a known breakage point in manual copy-and-paste workflows: a single entry can split into two or three rows, throwing every subsequent column out of alignment. The extraction engine reads the statement's row structure, not just the line breaks, so a wrapped description stays in its own cell and the transaction remains a single row in the exported file.
If your African Bank Limited statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that run several pages long are handled in a single pass. The engine reads the full document sequentially, maintains the running-balance check across page breaks, and flags any row whose arithmetic does not tally rather than rejecting the whole file. The exported output is one continuous table: no page headers repeated mid-sheet, no missing rows, no need to stitch extracts together manually.