If a transaction description on your Commercial Bank of Ethiopia statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Upload a statement document; the engine identifies the issuing bank and its layout automatically, so there is no template to configure. When transaction descriptions run long and wrap across multiple lines, a less careful parser can misread the wrapped text as a new row, splitting one transaction into two, or drag a value from the next column into the description field. Convert·Into scans the table geometry and the column edges to reassemble multi-line rows correctly, so a description that occupies two or three physical lines on the statement is kept as a single transaction record. The extracted data lands in a clean table: one row per transaction, each field in its own column, ready for review.
However your Commercial Bank of Ethiopia statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Once the table is extracted, you map each column to its matching field in the export. The engine proposes a default mapping based on the layout it detected, but you can adjust it: point the date column at the date field, the description at the memo, and the running balance at the balance field. This step takes only a moment to verify, and the same mapping is remembered for future statements of the same type. Export to Excel, CSV or QBO with the columns aligned exactly as your downstream system expects.