If a transaction description on your Morgan Stanley statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long and wrap across multiple lines, a generic extraction tool often breaks the entry apart: one row becomes two, or the narrative text bleeds into the column that should hold the amount. Convert·Into reads the full transaction block as a single record, preserving the complete description no matter how many lines it occupies on the page. The running balance is then checked against the statement's own printed closing figure, and any row where the split went wrong is flagged for review rather than silently accepted.
If your Morgan Stanley statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. A statement that runs several pages long introduces its own risks: a page break through the middle of a transaction can split a single entry in half, and a multi-page running total that is not re-anchored at each break can drift. The engine stitches consecutive pages together before extracting the transaction table, so a line that straddles the fold stays whole. The running balance is verified line by line, and a mismatch on any page stops the export only for that single row, not for the entire file, so you never have to restart the process from scratch.