Whichever order your Saman Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before the data is exported, every column the engine has extracted is mapped to its correct export field. The transaction date, the description, the debit and credit amounts, and the running balance are each placed into their own column. If the source layout ordered its columns differently or split fields across separate table sections, the mapping step aligns them into a single, consistent row structure. The result is a flat table with no merged cells, no offset values, and no misaligned columns.
Should a description on your Saman Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Some statement documents print transaction descriptions that wrap across two or three lines, with the second line indented or left-aligned under the first. The engine reads these multi-line rows as a single transaction, merging the wrapped text into one description field without breaking the row or creating phantom blank entries. When a wrap also shifts a numeric column on screen, the extraction still anchors each amount to the correct row by following the table's column boundaries, so a long description does not pull the wrong figure into the running-balance sequence.