Whichever order your ChiantiBanca statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping organises the extracted data for export. The engine identifies the statement's own headers and aligns the rows beneath them, preserving the original structure. Any column that does not map cleanly is flagged for manual review before the export runs, so the final file matches the intended layout from the statement.
When your ChiantiBanca statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. Scanned and photographed statements are read with optical character recognition before extraction begins. The same transaction table is rebuilt from the recognised text, and the running balance is verified line by line against the printed closing figure. A misread digit that breaks the balance is flagged for review without discarding the rest of the file.
Whether you need your ChiantiBanca statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. The converted data is exported directly to the format the next workflow requires, with Excel, CSV and QBO all available in one step. Column mapping and balance checks are preserved through the export, so the numbers in the output file match the verified figures from the statement exactly.