Once your Investitionsbank Sachsen-Anhalt statement is uploaded, what you get back depends on which export format you actually need next. The engine maps the extracted transaction table into a clean column structure, so what you see on the page becomes re-usable data. Date, description, debit and credit amounts, and the running balance are placed into separate columns without merged cells or fragmented rows. You choose the export format that matches your next step: a spreadsheet for manual review, a CSV for a bulk upload, or QBO (QuickBooks Online) for ledger-level reconciliation. The mapping is applied consistently across every statement from the same issuer, so the header order and field alignment stay predictable file after file.
If a transaction description on your Investitionsbank Sachsen-Anhalt 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 original document, a plain text extraction often splits it into separate, orphaned rows that break the table structure. The engine recognises continuation lines as belonging to the parent transaction by reading the statement’s row height and indentation patterns, not by guessing at word boundaries. It stitches those text fragments back onto the correct row so that the full description stays in one cell; the debit or credit amount and the running balance remain correctly aligned with it. Before the export is written, the closing balance printed on the statement is verified against the running balance the engine calculated line by line. Any row where the figures still do not add up is flagged for review, while the rest of the file remains ready for export.