If the running balance on your Diamond Trust Bank Group 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. The engine unlocks the statement’s own printed closing figure and uses it as a control total. Every transaction row is tested: the running balance must match what the statement itself declares, line by line. When a row does not add up, the engine flags that specific entry for review instead of rejecting the whole file. This means you can trust the export while still inspecting the one or two items that need a second look, which keeps the reconciliation tight without blocking the workflow.
If the Diamond Trust Bank Group 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 documents are read with the same rigour as a clean digital file. OCR reconstructs the transaction table, and then the running-balance check pressure-tests the result against the printed closing figure. If the scan is sharp enough for a human to read, the engine can usually pull the data reliably; when a digit is too blurred, the verification catches the mismatch so you are not left guessing. No separate scanning step is required, and the same export options to Excel, CSV or QBO are available once the extraction completes.