If a transaction description on your Westpac 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 runs long and wraps across multiple lines inside the statement table, the engine tracks the row boundaries by their table geometry rather than by line breaks alone. A wrapped description is kept in its correct row; the amount and balance columns stay aligned. The export preserves the full, unwrapped description in a single cell, so no data is split or lost.
If your Westpac statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. For statements that run several pages long, the engine processes every page in sequence without breaking the table. It detects page headers and repeated column labels and strips them from the transaction stream, so the exported file contains one continuous list of rows. The closing balance from the final page is verified, and any discrepancy is flagged for review.