When your Powszechna Kasa Oszczędności Bank Polski 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. A statement document that was scanned or photographed is read with OCR as soon as it lands. The engine identifies the transaction table automatically, so the paper original’s layout does not need to match any preset template. The running-balance check catches digits the scan may have misread: if a row does not add up, it is flagged rather than accepted silently.
Whether you need your Powszechna Kasa Oszczędności Bank Polski statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Mapping columns into the exact export format you need is a deliberate step with no hidden decisions. Each column the engine extracted, whether date, description, debit, credit or balance, is listed plainly for review before export. You confirm which column goes where in the output; the engine does not guess on your behalf. Exports are delivered as Excel, CSV or QBO, with one file per format and no merged cells or split rows to unpick afterwards.
If the running balance on your Powszechna Kasa Oszczędności Bank Polski 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’s running balance is verified line by line against the printed closing figure that appears on the document itself. The engine recomputes the balance from the first transaction to the last: anything that breaks the arithmetic is flagged for your attention. No statement passes through without this check, and no row is silently changed to make the numbers fit.