Whichever order your Banco Montepio statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is handled for you: every extracted field is placed into the correct column in the export layout automatically, so there is no manual drag-and-drop step to perform. Transaction descriptions, dates, amounts and running balances each land where they belong. The export formats present the data in clean columns ready for your ledger or reconciliation workflow, with no merged cells or hidden characters that would trip up an import routine. You can review the mapping once and rely on it for every subsequent statement that follows the same layout.
Should a description on your Banco Montepio statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a statement contains transaction descriptions that run long and wrap across multiple physical lines, the engine reads the continuation as part of that transaction rather than as a separate new row. A payment reference split over three lines stays a single transaction in the output; a concatenated memo or payee field that a copy-and-paste job would scatter across neighbouring cells stays in one column. The running-balance check confirms the accounting row by row, so a split line mistaken for two transactions would break the tally and is caught before you ever see the file.