When your Bank Saderat Iran 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. Statement documents that have been scanned or photographed, rather than exported as a clean digital file, introduce familiar pain points: skewed text, uneven lighting, and digits that blur together under compression. The engine reads these with OCR and applies the same running-balance verification it uses for every file. A 3 misread as an 8, or a currency symbol that bleeds into the amount field, breaks the running-balance chain; the engine flags that row for review rather than letting an incorrect figure land silently in the ledger. The extracted table keeps its original column order so you can cross-check any flagged line against the source image side by side.
When a Bank Saderat Iran statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. Statements that run several pages long often repeat the summary block or carry forward balances at page breaks, which can lead to accidental duplication if every page is treated as a self-contained file. The engine reads the document as a single continuous journal, stitching the transaction rows together and deduplicating any repeated header or summary rows. Column headings are matched once and applied across the full run, so a single export contains the complete period without gaps or overlapped entries.
If the running balance on your Bank Saderat Iran 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 the engine processes, regardless of length or source, is verified line by line against its own printed closing figure. The running balance is recalculated from the first transaction to the last and compared with the balance shown on the document. If the two figures diverge, the engine marks the row where the calculation broke rather than rejecting the whole file or quietly accepting the mismatch. The export columns are mapped into a clean table ready for Excel, CSV or QBO, so the data lands in your accounting software with the reconciliation already tested before you begin your own review.