If the running balance on your Bank of Sardinia 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 verifies the running balance against the statement's own printed closing figure. Every line is checked, and any mismatch is flagged for review so a single misread digit does not corrupt the ledger.
Whichever order your Bank of Sardinia statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is handled automatically. The engine identifies the transaction table, inspects its headers, and assigns each column to the correct field in the export. If the statement prints debits and credits in a single column with an in-cell sign indicator, the sign is parsed and the values are split cleanly into two columns. Date formats, decimal separators and currency symbols are recognised and normalised so the output fits your system without manual rekeying.
Should a description on your Bank of Sardinia 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 can split a single entry into fragments during conversion. The engine detects wrapped rows by analysing the table's column edges and joining orphaned lines back to their parent transaction. The original row order is preserved, and the full description is assembled into one cell in the export.