How to Convert a Nedbank Statement to Excel or CSV

Nedbank's online banking platform lets you export statements in OFX and OFC format via Enquiries → Statements → Export, but it does not offer a native CSV or Excel download. If you use the Nedbank Money App, your only option is a PDF statement. To convert a Nedbank statement to Excel, you either import the OFX file into accounting software that supports it, or you convert the PDF using an AI extraction tool that can parse Nedbank's specific column layout and output a structured .xlsx or .csv file.

Nedbank, one of South Africa's Big Five banks regulated by SARB, saw its total client base reach 8 million for the first time in 2025, with active Money App users climbing 14% to 3 million and digital transaction values rising 16% year-on-year, according to TechAfrica News reporting on Nedbank's 2025 annual results. A significant share of those clients are accountants, bookkeepers, and SME owners who need their Nedbank bank statement data in spreadsheet format for reconciliation, VAT returns, or import into packages like Sage Pastel.

This guide covers every available path: native OFX/OFC exports from online banking, handling Nedbank's encrypted .emc files, converting PDF statements to Excel or CSV, and importing the result into South African accounting software. If you also work with FNB accounts, we have a separate walkthrough for converting FNB statements to Excel.

Nedbank Statement Export Options: Online Banking vs Money App

The export options differ significantly depending on whether you use Nedbank Online Banking, the Nedbank Money App, or NetBank Business. Here is what each platform offers and where each one falls short.

Nedbank Online Banking (Personal)

The desktop online banking platform offers the most export flexibility. Navigate to Enquiries → Statements, select your account and date range, and open the Export dropdown. You'll find two structured format options:

OFX (Open Financial Exchange) — a standardised data format built for importing transaction data into accounting and personal finance software. It carries structured fields (date, amount, description, reference) but is not a spreadsheet file.
OFC (Open Financial Connectivity) — an older predecessor to OFX, supported by some legacy accounting packages. Functionally similar but less widely compatible.

Both formats give you machine-readable transaction data. Neither produces an Excel or CSV file. If your goal is a spreadsheet you can manipulate, filter, or share, OFX and OFC won't get you there directly.

Where OFX is useful: You can import OFX files straight into Sage Pastel, Xero, and several other SA-focused accounting packages for bank reconciliation. That makes OFX the fastest native path for getting Nedbank data into your accounting system. But if you need the data in Excel for VAT working papers, custom analysis, or sending a transaction summary to a client, OFX alone is not enough. You still need to convert Nedbank statement data to a spreadsheet format.

Nedbank Money App

The Money App supports PDF statement downloads only. There is no OFX, OFC, or any other structured export option. If you do most of your banking through the app, your only native output is a PDF file, which means you have no direct path to spreadsheet data without a conversion step.

A Nedbank Money App statement download gives you a formatted document, not usable data.

NetBank Business

Business clients access statements through NetBank Business, a separate interface with its own reporting tools. The core limitation persists: no native CSV or Excel export. Business users handling high transaction volumes across multiple accounts face the same conversion requirement.

Historical Statement Fees

Nedbank charges R11 per statement for any statement older than three months. For bookkeepers and accountants pulling several months of historical data for reconciliation or audit preparation, these fees accumulate quickly across multiple client accounts. The practical advice: download recent statements promptly each month before they cross the three-month threshold.

The e-Confirm Stamp

Every Nedbank PDF statement carries an official e-confirm verification stamp, giving the document evidentiary value for legal, audit, and formal compliance purposes. When you convert a Nedbank statement to Excel or CSV, the converted file does not carry this authentication. Always retain the original PDF as your verified source record alongside any spreadsheet versions you create.

Nedbank PDF Statement Format and Encrypted .emc Files

Nedbank PDF statements have structural quirks that explain why your copy-paste attempt probably produced a mess of misaligned columns and broken rows.

The Nedbank PDF Column Structure

A standard Nedbank PDF statement follows a five-column layout: Date, Description, Debit, Credit, and Balance (running). On the surface, this looks straightforward. The problem is the Description field.

Nedbank packs transaction details into the description column, including beneficiary names, branch codes, reference numbers, and payment identifiers. This text frequently wraps across two or three lines within a single transaction entry. When you copy and paste into Excel, or run the PDF through a basic converter, each of those wrapped lines registers as a separate row. A single debit order becomes three rows, only one of which contains the amount. The other two look like orphaned text fragments with empty debit, credit, and balance cells.

Why Generic PDF-to-Excel Tools Struggle

The parsing failures are predictable once you know the Nedbank PDF statement format:

Multi-line descriptions split one transaction across multiple rows. Tools that map one PDF line to one spreadsheet row cannot reassemble these.
Embedded reference numbers within descriptions (card numbers, payment references, Nedbank Universal Branch codes) create inconsistent line lengths that confuse pattern-based parsers.
Page-break continuations are particularly destructive. When a transaction starts at the bottom of one page and its description continues at the top of the next, most converters treat the continuation as a new, incomplete transaction. You end up with two broken rows instead of one clean one.
Running balance alignment drifts once any row-splitting occurs, making the entire column unreliable downstream.

These are not edge cases. On a typical 30-day current account statement, any card transaction, batch payment, or debit order will usually have a multi-line description.

The .emc Encrypted File Problem

Some Nedbank statements never arrive as PDFs at all. Statements delivered via email or downloaded from certain Nedbank channels come as .emc encrypted files. If you have tried to open one of these and got nothing useful, that is expected. The .emc format is a proprietary encrypted container that requires Striata Reader software to decrypt and view.

The workflow to get from .emc to usable data is:

Download and install Striata Reader (free, available for Windows and Mac).
Open the .emc file in Striata Reader using the password provided by Nedbank (typically your ID number or a pre-agreed passphrase).
Save or print to PDF from within Striata Reader.
Convert the resulting PDF to Excel or CSV using a capable converter.

This extra decryption step catches people off guard, especially bookkeepers and creditors clerks managing statements for multiple Nedbank accounts. You cannot skip it. No PDF converter, no matter how capable, can read an .emc file directly.

Scanned Statements Add Another Layer

Firms that handle banking documents for multiple clients often end up with printed-then-rescanned Nedbank statements. These introduce OCR challenges on top of the structural issues described above. A scanned Nedbank statement is no longer a text-based PDF; it is an image. The converter must first recognise the characters (OCR), then parse the Nedbank-specific layout, then handle the multi-line descriptions. Each stage introduces potential errors, particularly with low-resolution scans or statements that have been photocopied multiple times.

How to Convert a Nedbank PDF Statement to Excel or CSV

Manual Copy-Paste: Quick but Unreliable

The most obvious approach is opening your Nedbank PDF in a viewer, selecting the transaction table, and pasting into Excel. In practice, this rarely produces usable output. Nedbank's multi-line descriptions collapse into a single cell or scatter across adjacent columns. Debit and credit amounts misalign with their corresponding rows, and the running balance column frequently merges with the credit field. Some users have made this work by spending 20 to 30 minutes per page on manual cleanup, but for an accountant processing statements across a dozen Nedbank client accounts every month, it does not scale.

OFX Import Route

If you downloaded OFX files from Nedbank Online Banking, you can convert these to spreadsheet format. Excel's Power Query can import OFX data directly: go to Data > Get Data > From File, select the OFX file, and transform the resulting table. Alternatively, third-party OFX converter utilities will output CSV or XLSX. This method produces clean, structured data because OFX is already machine-readable.

The limitations are significant, though. OFX exports are only available through Nedbank Online Banking (not the Money App), only cover your current statement periods, and do not help with historical PDF statements you have on file. If your source document is a PDF, you need a different approach.

AI-Powered Extraction for Nedbank PDFs

The method that handles Nedbank's specific PDF format without manual cleanup is AI-powered extraction. Instead of parsing the visual layout through copy-paste, AI reads the document structure, identifies column boundaries, and maps each transaction to the correct fields regardless of multi-line descriptions or page breaks.

With Invoice Data Extraction, the workflow is:

Upload your Nedbank PDF statement (or batch-upload multiple months at once, up to 6,000 files in a single job).
Prompt the AI with what you need extracted and how you want it structured.
Download a formatted Excel (.xlsx) or CSV (.csv) file, typically within minutes.

The AI interprets Nedbank's column layout, keeps multi-line transaction descriptions intact, correctly separates debit and credit amounts, and handles page-break continuations where a transaction starts at the bottom of one page and finishes at the top of the next. Scanned statements and mobile phone photos of printed statements are also supported.

Prompting for Nedbank Statements

The prompt-based approach lets you control exactly what gets extracted and how it appears in your output. For a standard Nedbank cheque account statement, a practical prompt looks like this:

"Extract date, description, debit, credit, and balance from my Nedbank statement. Standardize dates to YYYY-MM-DD format. Keep the full transaction description including reference numbers on a single row."

You can adapt this to your specific needs. If you only need debits for expense analysis, say so. If you want a column for transaction type (EFT, debit order, card purchase), the AI will classify based on Nedbank's description text. If you process the same statement format monthly, save your prompt to the Prompt Library and reuse it, ensuring consistent output structure across every period.

For bookkeepers and accountants handling multiple Nedbank clients, the ability to extract data from Nedbank statements with AI across batch uploads eliminates the per-statement processing overhead entirely. Upload an entire year of statements, run a single prompt, and receive one consolidated spreadsheet with every transaction correctly parsed and formatted.

Importing Nedbank Statement Data into SA Accounting Software

Getting Nedbank transactions into a spreadsheet is only half the job. The end goal is reconciled books, which means importing that data into whatever accounting package your practice or business runs. The three platforms that dominate the SA market each handle bank statement imports slightly differently.

Sage Pastel

Sage Pastel remains the most widely used accounting software in South Africa, and its bank reconciliation module accepts CSV imports. The catch is column ordering: Pastel typically expects date, reference, description, and amount (some versions require separate debit and credit columns rather than a single signed amount). If your columns don't match, the import will either fail silently or map data to the wrong fields.

When extracting your Nedbank statement data, structure the output to match Pastel's expected layout from the start. This is far more efficient than exporting a generic CSV and manually rearranging columns afterward. If you're using an AI-powered extraction tool, configure your prompt to output the Nedbank statement to Sage Pastel format directly: date in yyyy/MM/dd or dd/MM/yyyy (matching your Pastel date setting), Nedbank's transaction reference, the full description line, and the amount split into debit/credit if your version requires it.

Xero South Africa

If you already downloaded an OFX file from Nedbank Online Banking, Xero is your fastest path: upload it directly to the bank feed without any conversion or column mapping.

For PDF-sourced Nedbank data, CSV is the route. Xero's CSV import requires at minimum three columns: date, amount, and description, with optional payee and reference fields. Xero prompts you to map columns during upload, so exact header names are flexible. Keeping your extraction output consistent with Xero's template (date, amount, payee, description) eliminates the mapping step on repeated imports.

QuickBooks South Africa

QuickBooks Online accepts CSV or QBO (QuickBooks format) for bank transaction imports. The CSV requirements are similar: date, description, and amount at minimum. QuickBooks lets you map columns during import, so the exact header names are flexible, but the data types must be clean. Dates should be in a consistent format, amounts should be numeric without currency symbols, and descriptions should not contain line breaks that could split a single transaction across multiple rows.

Scaling Across Multiple Clients

For accountants and creditors clerks processing Nedbank statements for multiple clients, standardise one extraction prompt per accounting platform. Extract once in the right format, import without rearranging. The same principle of streamlining document processing for SA creditors clerks applies whether you are handling bank statements, supplier invoices, or other source documents: consistent extraction templates matched to your downstream system.