Whichever order your APS Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The columns the engine extracts are mapped into a clean, consistent structure so every transaction lands where your workflow expects it. You confirm the mapping once: the date goes to the date column, the debit and credit amounts are separated, the narrative or reference field populates the description, and the running balance is preserved. After that, every subsequent statement from the same layout is mapped the same way automatically. There is no template to build and no column header to retype. If a statement introduces a new column you have not seen before, the engine surfaces it so you can assign it before export. The output is a flat table with no merged cells, no split rows, and no formatting artefacts that would break an import or a lookup formula. You export to Excel, to CSV, or directly to QBO.
When your APS Bank statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. A statement that arrives as a scan or a photograph goes through the same pipeline as a native digital file, with one additional layer: the image is read with OCR before the extraction runs. The running-balance check is the safeguard. Every line's closing figure is verified against the arithmetic of the prior balance plus deposits minus withdrawals; a row where the scan misread a 3 as an 8, an O as a 0, or a smudged decimal point will not add up, and that row is flagged for your review. You retype one number, not the whole statement. The rest of the table, where the figures do verify, flows straight through to the export without interruption.
When an APS 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. Long statements that run across several pages are treated as a single continuous record. The engine detects the page breaks, strips the repeated headers and any page-level summary rows, and stitches the transaction table together end to end. You upload one document, even if it scans to a dozen pages, and you download one reconciled file with no duplicate header rows, no mid-table page markers, and a single running balance that remains continuous from the opening figure on page one through the closing figure on the final page.