If a transaction description on your Secure Trust 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 more than one line in a statement document, the raw text can look split and fragmented. The engine treats these wrapped lines as a single logical record, so each transaction stays whole and nothing is lost in the conversion.
However your Secure Trust Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping is handled automatically: dates go to the date field, amounts to the debit and credit columns, and descriptions to the memo or narration field. Every mapped column appears in a review table before export, so you can confirm the alignment is correct and reorder or rename fields to match your ledger structure. For exports that require a specific column layout, the mapping can be adjusted without rebuilding anything from scratch.
When a Secure Trust 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. Multi-page statements are read as one continuous file, not as a stack of disconnected pages. The running-balance check carries forward across page breaks, and the converted output preserves the full transaction sequence. When a statement spans several pages, the closing balance of the first page must equal the opening balance of the next, and the engine verifies that chain step by step before the file is ready for export.