Wrapped descriptions
How Do I Fix PDF Bank Transactions Split Across Multiple Excel Rows?
Reviewed 12 September 2026
Short answer
Short answer
Treat a line as a new transaction only when it has the fields required by that statement layout, not merely because it begins with date-like text. Mark valid transaction rows, fill their row identifier down through continuation lines, group by that identifier, and combine the description text in its original order. Then verify that each grouped row has one transaction amount and the expected balance.
Wrapped descriptions are normal in Australian statement PDFs. The risk is attaching a reference to the wrong payment or turning it into a fake transaction.
Give continuation lines a transaction owner
In Power Query, a useful pattern is to create an identifier only on confirmed transaction rows, fill it down, then group the lines by that identifier. The exact confirmation rule must match the bank's layout.
Keep the description parts in source order. Account numbers, receipt references and timestamps can matter later when a business owner or accountant needs to identify the transaction.
Step by step
- 01
Define a complete transaction row
Require the date and the expected amount or balance fields for that statement layout.
- 02
Assign row identifiers
Number confirmed transactions and fill each identifier down through its continuation lines.
- 03
Group the lines
Combine description fragments in their original order without summing repeated amount text.
- 04
Check ambiguous rows
Compare date-looking references and page-boundary lines directly with the PDF.
Checks before you rely on the spreadsheet
- Continuation text belongs to the correct transaction.
- Each grouped row contains one transaction amount.
- Description order matches the PDF.
- Transaction counts and balances still reconcile.
Questions people ask
Why do descriptions create extra Excel rows?
The PDF often stores each visible line as separate positioned text even though a person reads the lines as one transaction.
Can I delete the extra rows?
Not safely. They may contain receipt numbers, merchant locations or other useful description details. Join them to the correct row instead.
Can a bank-specific parser handle wrapped descriptions?
Yes, when the parser has rules for that bank's transaction and continuation-line structure.