Once your Alexbank statement is uploaded, what you get back depends on which export format you actually need next. The conversion engine maps the extracted data into columns that suit your workflow, so the formatting step is already done when the file lands. The default layout places dates, descriptions, amounts and the running balance into separate fields; you can reorder or rename those columns before exporting, using a single click to pick the sequence that matches your ledger. Once the columns are arranged, the file exports to Excel, CSV or QBO. Each row arrives as a discrete transaction, clean of merged cells or split lines, ready to import without manual reshaping.
Whatever the running balance looks like on your Alexbank statement, Convert·Into checks it against the statement's own printed closing figure before you export anything. Every statement is verified against its own printed closing figure, line by line, before the download is ready. The engine reads the balance printed on the statement and checks that the running total in the extracted table adds up to that number exactly. If a single row does not reconcile, that row is flagged for review rather than silently accepted. You can inspect the mismatch, correct the figure, and re-run the check, keeping the rest of the file intact.
If your Alexbank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Multi-page statements are handled as a single continuous run, not as separate batches you must stitch together. When you upload a document that spans several pages, the engine reads across the page breaks and builds one transaction table from start to finish. The running-balance check then validates the full account of activity, so a split at a page boundary never causes a false break in the reconciliation. The export you receive reflects the whole statement period, not one page at a time.