Whichever order your B2B Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. To start, upload a statement document. The engine detects the issuing bank and its layout automatically, so no template is required. Every column found in the transaction table is then available to map: date, description, debit, credit, balance, and any custom fields present in the original. You choose the column order and labels, and your choices are saved, so the next statement from the same source maps the same way without rework. The remapping step catches columns that shift between statement formats, keeping every figure in its proper place for export.
Should a description on your B2B Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Transaction descriptions that span several lines inside the original document are reassembled into a single cell. The engine reads multi-line text as one record, preventing split rows that would break the running total. The result is a flat table where each transaction occupies exactly one row, with its full description intact and ready for categorisation.
If the B2B Bank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned or photographed statements are read with OCR, and the running-balance check on every row catches any digit the scan may have misread. A row that does not add up is flagged in the review view; you correct the figure once and the balance rolls forward, so a single scanning error does not force you to abandon the file. The verified table exports cleanly to Excel, CSV or QBO.