If the running balance on your Pax-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. When you upload a statement document the engine does not trust the totals it extracts on sight. It recalculates the running balance line by line from the first transaction through to the last, then compares its own computed closing balance against the closing balance printed on the statement. A mismatch on any row points to an extraction issue: a digit that OCR misread, a split row that landed in the wrong column, or an unrecognised fee line that shifted the total. The engine flags that specific row for review rather than rejecting the whole file, so you correct a single anomaly and move on. This check catches problems that a visual scan would miss, giving you a converted file whose figures tie out to the statement’s own printed summary.
If the Pax-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. Scanned and photographed statements go through the same reconciliation logic as clean digital files. OCR reads the text from every pixel, and the running-balance verification catches anything the scan misread, a 3 taken as an 8 or a decimal point swallowed by a crease, at the row where the arithmetic breaks. You do not need to pre-process the image or separate facing pages; the engine handles rotation, skew and multi-page scans on its own. Once the balance checks out, the transaction table exports to Excel, CSV or QBO just as a clean digital statement would.