If a transaction description on your Banque du Caire 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 run long and wrap across multiple lines can break a simple copy-paste extraction; the text splits into fragments that end up in the wrong cells downstream. The engine reads the statement’s table structure as it was laid out, so a multi-line description stays in its own column as a single cell, preserving the narrative detail accountants rely on. The line-by-line running-balance check still applies: every debit and credit is tallied against the printed closing figure, and if a wrapped description caused a misread, that row is flagged for review rather than silently corrupting the reconciliation.
When your Banque du Caire 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 or photographed statements add another layer of risk because the source is a raster image, not a character stream. The engine applies OCR to lift the transaction table from the image, then immediately verifies the extracted numbers against the statement’s own balance column. A misread digit that breaks the arithmetic produces a flag on that row, giving you a prompt to correct it before you export. Once the data is clean, you map the columns into the export layout and download the file as Excel, CSV or QBO.