If a transaction description on your DZ Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Statements that wrap transaction descriptions across multiple lines are handled by the engine’s layout parser. It reads the column structure pixel by pixel, recognising when a single transaction entry spans more than one row. The text from the continuation lines is joined to the correct transaction record automatically, so a narrative description that runs to three or four lines is reassembled cleanly before export. This avoids the split-row errors that appear when a generic converter treats every line as a new transaction and breaks the running balance.
Once your DZ Bank statement is uploaded, what you get back depends on which export format you actually need next. The export stage maps the extracted columns into your target format. Choose Excel, CSV or QBO. Every transaction field is assigned to the matching column header: date, description, debit, credit, balance. The closing balance that was verified against the statement’s own printed figure is carried across unchanged, so the exported file is ready to import into your ledger or reconciliation tool.
If the DZ Bank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements are read with OCR. The running-balance check then verifies every row against the expected arithmetic, flagging any line where a character was misread. Because the verification works row by row, a single misread does not force you to re-export the entire file. Correct the flagged entry and confirm the balance; the rest of the statement stays intact.