Whichever order your Münchener Hypothekenbank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Every column the engine extracts is mapped to a corresponding field in the export. Date, description, debit, credit and balance columns are placed into the standard ledger structure without manual rearrangement. If the original statement uses a different column order or names them in a way specific to the issuer, the engine normalises them into a consistent format before the file is written. You review the mapping once and then reuse it for every subsequent statement document from the same source.
If your Münchener Hypothekenbank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. A statement that runs several pages long is treated as a single continuous ledger. The engine stitches the pages together, reassembles any transaction row that was split by a page break, and carries the running balance forward from one page to the next to confirm it ties out at the final closing figure. When a mismatch appears on any page, that row is flagged: the rest of the file remains intact and usable, so a single discrepancy does not block the full export.