If a transaction description on your Unity Trust Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Some transaction descriptions run long, wrapping across several lines inside the statement document. The engine reads these layouts as they are printed, preserving the full memo field across the line breaks instead of splitting one entry into two fragments. When the description is reconstructed, every part of the original text stays attached to its row, so exports do not contain dangling partial lines that have to be stitched back together by hand.
If the running balance on your Unity Trust 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. The converted data is measured against the statement’s own printed closing figure, row by row. Every line that makes up the running balance is checked: if an individual entry does not add up, that row is flagged for review while the rest of the file remains intact. You see exactly where the arithmetic breaks, correct the item in the review panel, and move on without re-processing everything else.