Whichever order your Monzo statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. When the table layout is identified automatically, the columns are mapped individually so that each field lands in the right place in the export. The date stays a date, not a text string that Excel misreads. Inflows and outflows remain separate columns; a single balance column is not merged with the transaction amount. The description column keeps the full payee and reference text intact, without truncation or character corruption.
If your Monzo statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statement documents that run several pages long are stitched together into a single table. There is no need to split a multi-page file before uploading, and no transactions are lost at page breaks. The same running-balance check that guards single-page statements works end to end across the joined table, so a misread on page four is flagged just as readily as one on page one.
Whether you need your Monzo statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. The converted table can be saved as an Excel workbook, a CSV file, or a QBO file. Choose the format your workflow or software expects next; no extra conversion step is needed. The columns are ordered and labelled the same way regardless of which export you pick, so you get a clean, predictable file every time.