If a transaction description on your Coris 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 statement document prints transaction descriptions that run long and wrap across multiple rows, the extraction engine reads the full block of text and reassembles it into a single field. It does not split a wrapped description into two separate lines, and it does not leave the overflow floating beside an unrelated transaction. The engine identifies where the narration ends and the next amount begins, so even entries that span three or four printed lines stay whole. That single description flows into your export as one clean cell, with no fragments to repair by hand.
If the running balance on your Coris Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every file that leaves the conversion step is checked against the closing balance printed on the statement itself. The engine recalculates the running balance line by line, and if any row does not add up, that row is flagged for review rather than discarding the entire file. You can inspect the discrepancy, correct it, and proceed; the rest of the ledger stays intact. Because the verification uses the statement's own printed closing figure, not an inferred one, a mismatch is a concrete signal that a figure needs attention before the file goes into your books.
Whichever order your Coris Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. During export, each extracted column can be mapped into the slot your accounting system expects: the date column into the date field, the debit and credit columns into their matching fields, the narration into the description line. The default mapping handles the most common layouts without changes, and you can adjust a single field without rebuilding the whole template. The same column mapping applies whether the output is Excel, CSV or QBO, so a statement that was mapped once exports cleanly across all three formats on the next run.