If a transaction description on your First City Monument Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. A statement document where transaction descriptions run long and wrap across multiple lines presents a genuine extraction challenge: what a human reads as one entry looks to a parser like several stray lines. The engine reconstructs the logical rows by recognising repeating column patterns and reassembling wrapped text into a single description field. Every transaction is kept whole, so nothing is lost or split into ghost rows during conversion.
When your First City Monument 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. A scanned or photographed statement begins as an image, not as a table of data. The engine reads these files with OCR that is tuned for the numeric columns and fixed labels in account statements. After optical recognition, the same running-balance check that applies to digital statements is run against the result, catching any digit the scan may have misread before it reaches the export.
When a First City Monument Bank 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. A statement that runs several pages long does not need to be split before upload. The engine processes the entire document as a single continuous ledger, stitching the transaction table across page breaks. The closing balance from each page is verified against the opening balance of the next, so the final reconciled figure reflects every entry without manual assembly.