Once your Banca di Cividale Società per Azioni - Società Benefit statement is uploaded, what you get back depends on which export format you actually need next. The file will reach your ledger in the exact format your workflow expects. CSV with a comma delimiter, Excel with consistent column types, or a QBO file mapped to your chart of accounts: you choose the target on export, not before.
Whichever order your Banca di Cividale Società per Azioni - Società Benefit statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export is the step that saves the most downstream work. The engine reads the statement's own column headers, so the date column, the description column, the debit and credit columns arrive sorted and identifiable. You can then map them to your preferred schema. Rename a column, reorder the fields, or drop columns you do not need before the file leaves the browser. The running balance column, if the statement printed one, stays with the transactions and can be included or excluded. No field is fused to its source position; every column goes where you direct it.
When your Banca di Cividale Società per Azioni - Società Benefit 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. A statement that was scanned or photographed introduces a different challenge: the engine must read numbers drawn on a page rather than data exported from a banking system. The layout engine handles this by identifying the transaction table visually and extracting its rows with OCR, then verifying the running balance against the statement's own printed closing figure. A single misread digit breaks the balance arithmetic, and the engine flags that row rather than rejecting the whole file. This means you can review the flagged line, correct the amount, and keep the rest of the work intact.