Once your Reichmuth & Co statement is uploaded, what you get back depends on which export format you actually need next. The export step maps every extracted column into the format your downstream system expects next. Choose Excel for spreadsheet reconciliation, CSV for a lightweight data interchange format, or QBO for direct import into QuickBooks Online. The file you receive mirrors the original transaction table with no summary rows, no header graphics, and no blank spacer columns; only the data you selected, in the order you requested.
When a Reichmuth & Co 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. A statement that runs several pages long is read as one continuous transaction register. The engine follows the running balance from the top of the first page to the closing figure on the last, so no transaction gets lost or duplicated across page breaks. If any row does not add up, that single row is flagged; the rest of the file remains fully usable while you check the flagged line.
Should a description on your Reichmuth & Co statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that wrap across multiple lines are reconstructed into a single cell per record. The engine recognises that a continuation line belongs to the transaction above it rather than starting a new one, using the column alignment and the statement’s own printed structure to guide that decision. A split narrative that would otherwise fragment a CSV row stays intact as one description field.