Whichever order your Nederlandse Waterschapsbank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the engine identifies a statement table, it captures every column the document presents: date, description, debit, credit and balance. During export you map those source columns into your target format so the output matches your ledger structure exactly. Rename a field, reorder columns, or drop the ones you do not need; the extraction itself stays intact. The export step produces a clean file where every transaction sits in the right column, ready for import with no manual relabelling.
Should a description on your Nederlandse Waterschapsbank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Long transaction descriptions can wrap across several lines inside a statement document, making a single entry look like two or three separate rows to a naive parser. The engine reconstitutes these wrapped lines back into a single transaction before extraction. The date, amounts and running balance anchor the reconstruction, so a merchant name split across multiple lines stays with its figures and no stray text fragments into the next record.
Whatever the running balance looks like on your Nederlandse Waterschapsbank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every conversion includes a row-by-row verification of the running balance against the statement's own printed closing figure. The engine recalculates the balance from the extracted amounts and compares it to what the document declares. A mismatch flags the row that does not add up, instead of rejecting the whole file. You review the flagged entry, correct the single misread, and the rest of the batch proceeds.