If a transaction description on your Webster Bank 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 inside a statement document, the extraction engine reads the full narrative as a single entry. It does not split a wrapped line into two separate transactions, and it does not merge two adjacent rows just because both contain text overflow. The running-balance check still applies: every row’s arithmetic must stay consistent with the statement’s own closing figure, no matter how tall any single description block grows.
If your Webster Bank 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 is handled as one continuous ledger. The engine reads across page breaks without restarting column detection or reinterpreting headers that repeat mid-document. The transaction table is assembled in full before the running balance is verified end to end, so a mismatch on page four will be flagged as clearly as one on page one. Once the file is verified, you choose the export format: Excel, CSV or QBO. The column mapping preserves the original structure, placing dates, descriptions, debits, credits and the running balance into the same columns you would expect from a single-page statement, ready for import into your ledger or reconciliation tool.