If the running balance on your Banca Monte dei Paschi di Siena 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 extracts the closing balance printed on the statement document, then recalculates the running balance line by line, following every credit and debit in sequence. That independent recalculation is compared against the statement’s own closing figure. If the two match, the extraction is arithmetically sound: no transaction has been split, shifted, or misread in a way that changes the total. If they do not match, the file is not rejected wholesale. The row where the numbers diverge is flagged for review, so you can open that point in the statement, correct the discrepancy, and release a clean export without rechecking every line above it.
If a transaction description on your Banca Monte dei Paschi di Siena 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 several printed lines, extraction tools often treat each line as a separate row, splitting one entry into fragmented pieces that break the column alignment. Convert·Into follows the full text block to its end, recombining wrapped lines into a single transaction record before mapping the row. Amount, date and description stay in their correct columns, and the running-balance check confirms that no value was read from the wrong row.
If your Banca Monte dei Paschi di Siena statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Long statements turn a manual conversion into hours of scrolling and pasting. The engine handles every page in sequence, reading to the end without needing the file split or prepped. The final export preserves the same sort order as the source, so a year-end ledger reconstitutes cleanly, however many pages the original statement spans.