Whichever order your First Abu Dhabi Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine lets you choose which columns land where in the export. Credit and debit amounts can stay in separate columns, or you can map them into a single signed-amount column that flows straight into your ledger. Every field that the statement prints is available to map: posting date, value date, running balance, and the transaction narrative itself. You set the mapping once for a layout; the same column arrangement is then applied to every statement document that shares that structure, so you do not have to re-configure the export each time.
If your First Abu Dhabi Bank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. A statement document that spans several pages is read as a single continuous transaction feed. The table header is identified on the first page and carried forward, so columns remain aligned all the way to the closing balance on the final sheet. Subtotal lines and repeated page headers are stripped from the output automatically: the exported file contains only the transactions, with one clean row per entry. The running-balance check spans the full document, not each page in isolation, which catches any carry-over error at a page break before the file reaches your reconciliation step.
If a transaction description on your First Abu Dhabi 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 transaction description wraps across two or three lines inside the statement table, the engine reads all the wrapped text and joins it into a single cell in the export. The line breaks that served only the printed layout are removed, and the full narrative is preserved in one field. If the description column in the statement sits unusually wide and occasionally overlaps the column beside it, the extraction still recovers the complete text; anything that cannot be resolved cleanly is flagged at the row level, so you can review it rather than discover a truncated narrative later.