If a transaction description on your Access Bank Group statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long and wraps across multiple lines, the statement document can split a single entry into what looks like two or three rows. Convert·Into reads the full record, not just the first line of text. It joins the wrapped lines back into the single transaction they belong to, so the export contains one row per entry with the complete description intact. Nothing is truncated, and no ghost rows appear in the output.
When your Access 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. Scanned and photographed statements introduce their own kind of noise: skew, uneven lighting, or a 3 misread as an 8. Convert·Into applies OCR to lift the transaction table from the image, then runs the same line-by-line running-balance check it uses on every statement. Any row whose lifted numbers do not add up to the printed closing figure is flagged for review. The full file is never rejected; only the suspect row is set apart. You review the flagged item, correct or confirm it, and proceed. Once verified, the mapped columns export cleanly to Excel, CSV or QBO, with every transaction in its proper place and the reconciliation already proven.