If a transaction description on your Banca Popolare di Puglia e Basilicata statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description wraps across multiple lines on a statement document, the row count no longer matches the data count. Pasting that into a spreadsheet produces split rows, merged columns and figures that land in the wrong cell. The engine reads each statement page as a whole and reassembles wrapped text into a single row per transaction, so the table holds together before any balance verification begins.
If the running balance on your Banca Popolare di Puglia e Basilicata 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. Every statement carries a printed closing balance. That figure is the truth source for the file. The engine extracts the running balance column line by line and checks it against the statement’s own closing number. A row whose arithmetic does not add up is flagged clearly for review: the rest of the file remains intact. When you export to Excel, CSV or QBO, only rows that have survived that verification go into the export file, with columns mapped directly into your target format.