If the running balance on your Fürstlich Castell'sche Bank 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 running balance printed on the statement is verified line by line against the extracted data. Each transaction row is checked to confirm that the previous balance plus the transaction amount equals the new balance shown. If a row fails this check because of a misread digit or a shifted column break, that row is flagged for review. The rest of the file remains intact; a single anomaly never blocks the entire conversion.
If the Fürstlich Castell'sche Bank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Statement documents that arrive as a scan or a photograph are read with optical character recognition before any extraction begins. The same running-balance verification then tests every row the OCR produced, catching any character the scan misread. This means a photographed statement receives the same structural audit as a clean digital file, and no row enters the export without passing the arithmetic check.
However your Fürstlich Castell'sche Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. After the verification pass, the extracted columns are ready for export. You map the statement fields, such as the date, description, debit, credit and balance columns, to the matching columns in your chosen format. The mapping is a one-time step that remembers your layout choice, so the next statement from the same layout can flow straight into Excel, CSV or QBO without further configuration.