When your Persia International 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. A scanned or photographed statement often arrives as an image, not as a structured data file. The engine reads these images with optical character recognition and then lays the numbers out into rows and columns, the same way it handles a clean digital document. Smudges, skew, and uneven lighting are common when a phone camera is used, so the extracted table is checked for consistency after the scan. A printed statement that has been folded or scanned at a slight angle may still produce a complete transaction list, but each line is only kept when the numbers add up correctly.
Whatever the running balance looks like on your Persia International Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. After the transaction table is built, the running balance is verified against the closing figure printed on the statement. The engine recalculates the balance from the first transaction to the last, comparing every intermediate total to the amount shown alongside it. If a single digit was misread, that row is flagged for review. The rest of the file remains intact and ready to export; the check isolates the problem without blocking the whole batch.
Once your Persia International Bank statement is uploaded, what you get back depends on which export format you actually need next. Once the statement passes verification, it is mapped into the export format you choose: Excel, CSV, or QBO. Columns are ordered to match the target layout, and the date and number formats are normalised so they import without adjustment. You download one clean file and move on.