When your Banca Popolare del Frusinate 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. Statements arrive in many forms: electronic files downloaded from a portal, and paper pages that were scanned or photographed. When a statement is a photograph, the numerals the reader needs are pixels of varying brightness and contrast, not crisp digital characters. The conversion engine reads these images using optical character recognition built for bank layouts, and every extracted figure is checked against the statement's own printed closing balance. A row that does not add up is flagged for review, so a grainy photo of a column of numbers never becomes a silent error in the general ledger.
If a transaction description on your Banca Popolare del Frusinate statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions in statement documents often carry payee names, reference codes and narrative text that run well past the edge of a single cell. When a scanner interprets that wrapped line as a new row, the table structure breaks: a single payment splits into two ghost entries, and the imported data no longer matches the physical statement. The converter reads the full transaction block as one logical record, not as consecutive lines, and reassembles the description field before mapping it to the export. The running-balance verification then catches any case where a misread line break has shifted the figures, so the issue is visible the moment the file is processed.
However your Banca Popolare del Frusinate statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Mapping the extracted columns into the export is the step that turns a bank's layout into a working import file for your accounting software. The converter recognises the standard columns, date, description, debit, credit, balance, and aligns them into the same schema every export uses. When the statement presents a combined debit-and-credit column with signs or an amount column that prepends a currency symbol, the engine normalises the values into separate numeric fields before the export is written. The result is a clean Excel workbook, a CSV file ready for bulk processing, or a QBO file that drops straight into the ledger, with the column map preserved and the closing balance verified.