Once your Nationwide Building Society statement is uploaded, what you get back depends on which export format you actually need next. Upload a statement document. The engine identifies the layout on its own, so there is no template to set up. It pulls out every transaction row, including the date, the description, the paid-in and paid-out amounts, and the running balance that was printed on the page.
Whichever order your Nationwide Building Society statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Once the table is extracted, you decide which columns map to which fields in the export. Drag the statement's paid-out column to the debit field, the paid-in column to the credit field, or rename a field if the statement labelled it differently. The same control lets you drop an unused column entirely, so the export carries only the data your ledger or software expects. You can save that mapping and reuse it on the next statement from the same source, and the engine remembers it.
When your Nationwide Building Society 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. After the mapping is set, pick the format the next step requires: an Excel workbook, a CSV file, or a QBO file ready for import. The export preserves the structure you defined, with every transaction row verified against its own running balance. If a single line's printed balance does not add up, that line is flagged, but the rest of the file exports cleanly. Scanned or photographed statements are read with OCR before the same verification runs; the running-balance check catches any figure the scan misread, so you can review that row, correct it, and finish the export without redoing the whole file.