When a Danske Bank 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. A statement document that runs several pages long is treated as a single continuous record. The upload accepts the whole file at once, and the extraction engine threads the transaction table across page breaks automatically. Headers that repeat on every page are discarded, so the export contains one clean run of data from the first row to the last. There is no cap on page count, and no step where you need to split or stitch files together before conversion begins.
If the running balance on your Danske Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The running balance is verified line by line against the statement's own printed closing figure. The engine reads every debit and credit, recalculates the cumulative total, and compares the result to the balance printed at the end of the statement. A row that does not add up is surfaced with a flag; the rest of the file remains intact, and the mismatch is shown plainly so you can decide whether a single misread digit needs attention before export.
If the Danske 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. A statement document that was scanned or photographed, instead of exported as a clean electronic file, is read with OCR. The same running-balance check applies: if the scan misreads a 3 as an 8, the balance will not tie, and the affected row is flagged. Because the check works across every line, you can trust the numbers that do tie without needing to retrace the entire document. The engine still identifies the layout automatically, so no template configuration changes for a photographed document.