If a transaction description on your CIH 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 wraps across several lines, the extraction engine reads the full text as one continuous field. It does not stop at the first line break or treat a continuation as a new row. The result is a clean transaction record that keeps the complete narrative together, so nothing is cut short or split into a phantom row when you export.
When your CIH 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 page brings its own risks: a smudge, a skewed angle, or a shadow across a number can all defeat a simpler reader. The OCR layer here is paired with a line-by-line balance check. If a misread digit throws the tally off, that row is flagged. You can correct the single value and move on, without losing the rest of the file or having to rekey everything from scratch.
Whichever order your CIH Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Before you export, the engine maps each extracted column to its destination automatically. You can review and adjust those mappings yourself: drag the date field into the correct slot, confirm which column holds the debit versus the credit, and set the running balance to land where your ledger expects it. The final export respects every mapping you set, so the file arrives in Excel, CSV or QBO with the structure you chose.