When your Patria Bank 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. Scanned and photographed documents are treated the same as born-digital files. Upload an image of a paper statement; the engine reads every line with OCR, then verifies the result field by field. No manual setup is required.
Whether you need your Patria Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Export mapping fits the output to your workflow, not the other way around. The extracted table is presented with every column clear: date, description, debit, credit, and the printed running balance. You choose which columns to keep and in what order, then export to Excel, CSV or QBO. The file lands ready for import into your ledger or accounting package, with no stray merged cells or split rows to clean up.
If the running balance on your Patria 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. Every statement is checked against its own printed closing figure. The engine tests the arithmetic line by line. If a row does not add up, it is flagged for review rather than rejected. You spot the discrepancy yourself before the file enters your books, and the rest of the transaction table stays intact.