Whichever order your Awash Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When you map the statement into the export, you decide where every column lands. The engine identifies the transaction table automatically; you then choose which columns to keep and the order they appear in. Rename any heading so it matches your ledger’s naming convention. Rows that cannot satisfy the running-balance check are flagged on screen, and you can correct a single misread amount before the file leaves, rather than starting over.
Should a description on your Awash Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Statements where transaction descriptions wrap across several lines are handled without losing the narrative detail that justifies an entry. The engine recognises when a cell spans multiple rows and keeps the full text together. Because the reconciliation relies on the numeric columns, a long description never interferes with the balance check: the amounts, dates and running totals are still verified line by line, and any row where the arithmetic does not hold is called out. You export the complete record to Excel, CSV or QBO, with every description intact and every figure confirmed against the printed closing balance.