If the running balance on your NatWest Group statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. A statement's closing balance is the one fixed number both the bank and the accountant trust. The engine reads that printed figure and then works through every transaction row, recalculating the running balance step by step. Any row where the numbers no longer add up is flagged for review, so a single misread never propagates silently into the ledger.
Whether you need your NatWest Group statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. When the statement is clean, the engine maps its columns into the export fields a bookkeeper or accountant actually needs: date, description, debit, credit, balance. You choose the target format, Excel, CSV or QBO, and the output arrives ready for import. No column header needs to be renamed and no stray merged cell needs to be split before the file can be used.
If your NatWest Group statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. The engine works the same way whether a statement is one page or forty. A multi-page document threads its transaction table across page breaks without losing a row, and the final closing balance is verified from the statement's own last page. Every transaction is captured, so a long statement takes more time to review but no more time to set up.