Whichever order your American Express statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When you open the converted file, every column from the statement is already present; the mapping step lets you choose which columns land where in the export. You can rename a column heading, drop a column you do not need, or reorder fields so the export matches your existing chart of accounts. The mapping is persistent for later statements from the same issuing layout, so you set it once and every subsequent upload inherits the same structure. The engine never hard-codes column positions by bank: it reads the actual headers on the page and maps them to your chosen export fields, so a column labelled "Amount" does not end up in the "Description" column of your Excel file.
If your American Express statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Multi-page statement documents are handled as one continuous record. The engine walks every page, detects page breaks, and stitches the transaction rows together so no entry is dropped or duplicated at a page boundary. Running subtotals or repeated headers that appear on each new page are identified and suppressed, leaving a single clean table that runs from the first transaction through to the last without interruption. The closing balance and statement date are pulled once from the final page, and the whole file is verified as a unit.
Whatever the running balance looks like on your American Express statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement that Convert·Into processes is checked against its own printed closing figure. The engine recomputes the running balance line by line, starting from the opening balance and applying each transaction in sequence. Any row where the recomputed balance does not match the figure printed beside it on the statement is flagged for review, while all rows that do add up remain intact. The check catches transposed digits, misread characters from a scanned document and column misalignment, and it surfaces the exact row that failed so you can correct that transaction without rechecking the entire file. When the final recomputed balance agrees with the statement's own closing number, the whole table is confirmed.