If a transaction description on your Abu Dhabi Islamic Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a statement’s transaction descriptions run long, a single entry can break across several lines in the document. The engine reads the table structure, not the visual line breaks, so multi-line descriptions stay together in one row. No line of text gets orphaned into its own cell, and every transaction keeps its full, original description in the converted file.
When your Abu Dhabi Islamic Bank 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 are read with OCR, and the running balance is verified line by line against the document’s own printed closing figure. If a misread digit anywhere in the table would cause the balance to drift, that row is flagged for review: the rest of the file remains intact, and the reconciliation check tells you exactly which transaction needs attention. The recognised table is mapped into columns you name, and you export the full set of transactions to Excel, CSV, or QBO in a single step.