Whichever order your Mitsubishi UFJ Financial Group statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping works without a template. The extraction engine identifies transaction tables, recognises columns by their headers and positions, and places each field in the correct slot in the export layout. Date, description, debit, credit and balance are aligned automatically, exactly as they appear on the statement. If a column in the statement uses an unconventional label, the engine matches it by its data pattern rather than by exact text; a column full of running-balance figures, for example, is placed into the balance column regardless of what the header reads. The mapping is reversible: before you export, you can override a column assignment with a single click, and the engine remembers the correction across the rest of the file.
If your Mitsubishi UFJ Financial Group statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that span several pages are handled as one continuous file. The engine reads across page breaks, stitching rows that are split by a page footer or header into a single transaction. The running-balance check holds across the full document: if a balance printed at the top of a new page does not follow from the last entry on the previous page, the row is flagged. Multi-page handling applies equally to statements uploaded as a single file and to scans where each page arrives as a separate image; the engine groups matching page sizes and layouts together automatically, so a twenty-page file is processed as one statement, not twenty fragments.