When your Bulgarian Development 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 statement that was scanned or photographed brings its own set of risks. Lighting, angle, and page curvature can turn a 3 into an 8 or merge two adjacent cells into one. Convert·Into reads these documents with OCR, character by character, then runs a line‑by‑line audit of the running balance. If a misread digit breaks the arithmetic, that row is flagged. You do not have to reject the whole file or retype a year of transactions because of a single corner‑fold shadow.
Whatever the running balance looks like on your Bulgarian Development Bank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement is verified against its own printed closing figure. The engine recalculates the running balance from the first transaction to the last and compares the result with the closing balance shown on the document itself. A mismatch stops the review: you inspect the flagged row, correct the one figure that failed, and the check passes. The file is never accepted with a balance that does not add up.
If your Bulgarian Development Bank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. When a statement runs several pages, the engine stitches them into one continuous transaction table. Page breaks, repeated column headers, and carry‑forward subtotals are removed automatically, so the exported file behaves as if the bank had issued a single‑sheet ledger. The running‑balance check still runs end to end, including across page boundaries, so a carry‑forward error on page three is caught before it reaches your accounting package.