When your Bank of Communications 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. Statement documents that were scanned or photographed on a phone are read with optical character recognition. A smudge, a fold or uneven lighting can cause a character to be read incorrectly. The engine does not reject the file for that; it extracts what it can and then checks every row. The built-in running-balance verification compares the arithmetic line by line against the printed closing figure on the statement itself, so a misread digit is caught where it would break the sum.
Whether you need your Bank of Communications statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. The extracted transaction table can be exported to the exact format the next step requires. Choose Excel for a clean set of columns ready for pivot tables and lookups, CSV for a plain import into most accounting platforms, or QBO for a direct upload into QuickBooks Online. The column mapping between the statement layout and the export is preserved in the same order every time, so a routine month-end close produces a predictable file structure with no manual reordering.
Should a description on your Bank of Communications statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description is long enough to wrap across several lines on the page, a naive extraction can split a single transaction into multiple phantom rows. The engine recognises wrapped text by the pattern of blank cells in the date or amount columns that follow, and it re-joins the description into one row. The export file shows one transaction per line with a complete description, while the running-balance check confirms that nothing was lost or duplicated during the reassembly.