If the running balance on your Ulster Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The engine reads the printed closing figure shown on the statement and then verifies the running balance line by line. If any row does not add up to the next, it is flagged for review. The file is never rejected wholesale: a single discrepancy leaves the rest of the data intact.
Whether you need your Ulster Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Once the statement is verified, the next task is mapping its columns into the exact export format your workflow requires. Convert·Into identifies transaction dates, descriptions, amounts and balance columns automatically, then writes them into clean, predictable fields. You can choose Excel, CSV or QBO as the output, and standard fields such as debits and credits are placed in separate columns so they slot straight into your reconciliation template or accounting package without further reshaping. The export respects British-neutral number formatting that downstream tools expect, preventing locale mismatches from silently corrupting figures.
Should a description on your Ulster 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 run long and wrap across multiple lines, which makes a simple copy-and-paste into a spreadsheet unreliable: pieces of one transaction can scatter into unrelated rows. Convert·Into reassembles wrapped text back into a single description field so every transaction lands in its own row. The mapped output preserves the full narrative detail of each entry while keeping the column structure rigid, giving you a flat table ready for filtering and categorisation.