When your Belagroprombank 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. When a statement document is a photograph or a scan, the text is lifted by optical character recognition before parsing begins. The extracted characters are fed through the same running balance check as any clean digital file. A smudge that turns a 7 into a 1 will misalign the balance, so the row is flagged for review rather than allowed to pass silently. This way, the data you export reflects exactly what is on the page, or it stops and asks for a correction.
When a Belagroprombank 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 span several pages are handled as one continuous table, with any repeated column headers stripped automatically. The running balance carries across page breaks and is verified against the printed closing figure on the final page. You receive a single output with no gaps at the page boundaries, ready for the whole period to be exported to Excel, CSV or QBO at once.
Should a description on your Belagroprombank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions that wrap onto a second or third line are reassembled into a single row during extraction. The table is rebuilt by column position rather than line count, so a wrapped memo is correctly paired with its debit, credit and balance values instead of splitting into phantom extra rows. The running balance check confirms every line still adds up before the export is written.