When your Western Alliance Bancorporation 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 printed out and then scanned or photographed adds a layer of optical interpretation before the numbers can be read. The engine applies OCR to these image-based documents and then runs the extracted figures through the same line-by-line running-balance check that it uses for every other file. Any character that the scan misread and that throws the balance out of alignment is flagged on that specific row, so a single smudge does not force you to rekey the entire month.
If a transaction description on your Western Alliance Bancorporation statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across two, three or four lines inside a table cell often break a naive extraction into separate, orphaned rows. The engine reads a statement document as a whole and recognises multi-line descriptions as a single transaction entry before it maps the columns. The result is one clean row per transaction, with the full payee or narrative text kept together, ready for export to Excel, CSV or QBO without manual splicing.