Whichever order your Itaú Unibanco statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The export process maps every column from the transaction table into its correct position so the output file matches your working format without manual re-ordering. Date, description, debit, credit, and balance columns are each identified and placed into the appropriate field; any column that the statement itself does not supply is left blank rather than guessed. The result is a clean ledger you can open in Excel or import straight into your accounting package, with every value in the column where your workflow expects it.
Should a description on your Itaú Unibanco statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions in statement documents sometimes wrap across two or even three rows, which makes a simple row-by-row copy produce broken, split records. Convert·Into detects these multi-line entries and reassembles them into a single row per transaction before the export is built, so a long narrative that runs onto the next line stays attached to its own date and amount rather than fragmenting into orphaned text. The running-balance check is applied after this reassembly: if the reconstructed row does not add up, the row is flagged for review while the rest of the file proceeds to export intact.