If the running balance on your Azerigasbank 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. Upload a statement document. The engine reads the bank’s layout automatically, no template or column mapping required. It extracts the full transaction table and then verifies the running balance line by line. Each row’s computed balance is checked against the printed closing figure on the statement itself. If they ever diverge, that row is flagged for review without rejecting the rest of the file, so one OCR slip on a cheque number does not force you to start over.
If a transaction description on your Azerigasbank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long, they often wrap onto a second line and break a naive table parser. The engine recognises these wrapped rows and reconstructs a single, complete description cell before extraction. Column alignment is preserved, keeping the date, amount, and balance columns clean. The exported file lands in Excel, CSV, or QBO with one transaction per row and all its details intact, ready for import.