If a transaction description on your Alfa-Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long, it wraps across two or three rows in the statement table. A naive extraction sees each wrapped line as a separate row and splits the record apart. The engine reads the layout structure, not the visual line breaks, so a multi-line narrative entry stays together as one transaction. The running-balance check confirms that the joined row still sits in the correct sequence and that nothing was dropped when the lines were recombined.
When your Alfa-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. Scanned and photographed statements add a different layer of risk: a speck of dust misread as a decimal point, a crease mistaken for a digit. The engine applies OCR to bitmap images and then runs the same verification it uses on born-digital documents. Every row is checked against the statement's own printed closing figure; a misread that pushes the running balance out by even one cent is flagged for review. When you export the cleared file, columns are mapped cleanly into Excel, CSV or QBO, so you get a working ledger without rekeying a single figure.