Whichever order your Zempler Bank Ltd statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Once a statement document lands, the engine maps each column from the statement into the export automatically. The date column, the description field, the debit amount, the credit amount and the closing balance are each identified and placed in the right slot so you do not have to match headers by hand. If the statement format wraps a long transaction description across two or three lines, those lines are gathered back into a single record before the columns are assigned. The export preserves the logical grouping: a multi-line narrative stays with its own date and amount, never splitting across rows or leaking into the next transaction. You choose the output (Excel, CSV or QBO) and the structure is ready for the ledger, with every column in its expected place.
Should a description on your Zempler Bank Ltd statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. The running balance remains the final check. The engine reads the printed closing figure from the statement and verifies that the sum of the listed transactions leads exactly to it. If a wrapped description line was misread and threw the line count off, the numbers will not reconcile, and that row is flagged. The rest of the statement stays intact; only the line that does not add up is set aside for review. That way you fix the one problem row rather than scrub the whole file, and the export always carries what passed.