When a Steiermärkische Sparkasse statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. For statements that run several pages long, the engine processes the entire document as one continuous ledger rather than treating each page in isolation. It recognises repeated column headers as continuations of the same table, not as the start of a new one, so a single account period that spans five pages is stitched into one clean transaction list. The running balance check runs across the full document: if a carry-forward figure on page three does not match the closing balance of page two, the row is flagged for review.
Should a description on your Steiermärkische Sparkasse statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that are long enough to wrap across multiple lines are a known source of false table rows in simpler converters, where each wrapped line is interpreted as a new transaction and the column structure falls apart. The engine reads these multi-line description blocks as a single row by tracking the alignment of the other columns: a date or amount cell that spans one line vertically confirms that the description beneath it belongs to the same entry. This keeps a single purchase note that fills three lines in the statement as one row in the exported file, with no phantom transactions and no split amounts.