If a transaction description on your Starling Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. A statement document whose transaction descriptions run long and wrap across multiple lines is not a problem. The engine reads the full transaction row, not one line at a time, so a description that wraps does not get split into two phantom entries. If the bank prints a continuation indent or repeats a date on the wrapped line, the layout is recognised for what it is: one transaction, not several. The extracted table keeps the description intact in its own cell.
If your Starling Bank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Long statements spanning many pages are handled the same way as a one-page extract. The engine does not process a page and reset; it follows the transaction table to the end of the file. The running balance is verified across page breaks, and the closing figure on the final page is the one that must match. Any mismatch is flagged on the specific row where the break occurred, not buried in a bulk report.