When an Absa Bank Kenya 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. Statements that run several pages long are handled as one continuous document. The engine reads across page breaks and stitches the transaction table into a single list, so no transaction is missed or duplicated. The running balance is verified across every page, and any break in the sequence is flagged for review.
When your Absa Bank Kenya 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. When a statement was scanned or photographed rather than exported as a clean file, the engine applies optical character recognition to pull out the numbers and text. Because the running-balance check compares every line against the statement’s own printed closing figure, a misread digit or merged character is caught rather than silently carried into the export. You review only the rows that did not add up, not the entire file.
If a transaction description on your Absa Bank Kenya statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across multiple lines are a common source of split rows and scrambled columns in a manual copy. The engine detects the table structure that underpins the statement and keeps each transaction in one row, even when its narrative text occupies two or three printed lines. You choose which columns appear in the export; the column mapping is flexible, so you can include the full description, a truncated memo, or both, depending on what your ledger needs. The converted file is delivered as Excel, CSV or QBO, ready for import.