Convert BNZ Bank Statements to OFX

To convert a BNZ bank statement to OFX, upload your PDF statement to BankStmtConverter. The system extracts transaction dates, payee details, particulars, codes, references, debits, credits, and running balances, then compiles them into a structured Open Financial Exchange (.ofx) file ready for import into your accounting software.

How to convert BNZ bank statements to OFX

1. Upload your BNZ PDF: Select your BNZ checking, savings, or credit card statement from your computer or cloud storage. Scanned paper statements and digital e-statements are both supported.
2. Automated extraction: The parser identifies the statement header, account metadata, and transaction tables. It separates deposits, withdrawals, and balance checkpoints without altering negative or positive signs.
3. Review and verify: Check the preview table to confirm that line items match your BNZ statement's opening and closing balances.
4. Download the OFX file: Export the result directly as a .ofx file and import it into your financial application.

If you prefer tabular spreadsheets for manual audits rather than structured bank feeds, you can also convert your statement using our BNZ to Excel converter or export to BNZ to CSV.

Data fields extracted from BNZ statements

BNZ statements use distinct transaction fields common across New Zealand financial institutions. The conversion engine captures and structures these fields into standardized OFX XML/SGML tags:

• Transaction Date: Formatted in standard YYYYMMDDHHMMSS within the OFX container from the statement's original DD/MM/YYYY layout.
• Particulars, Code, and Reference: Extracted from the statement narration and mapped into the <MEMO> or <NAME> tags so reference tracking remains intact.
• Transaction Type: Categorized automatically as debits (DEBIT) or credits (CREDIT) to populate <TRNTYPE> accurately.
• Amount: Stored under <TRNAMT> using precise decimals (e.g., -145.50 or 2500.00).
• Financial Institution Transaction ID (FITID): Generated deterministically for each transaction to prevent duplicate imports on subsequent uploads.
• Ledger Balance: Calculated and written to <LEDGERBAL> matching the closing balance printed on the statement.

Working with OFX files in accounting software

The OFX (Open Financial Exchange) format is the standard data container for financial institutions and desktop accounting platforms. Unlike plain text files, OFX contains rigid structural tags that prevent misaligned columns, corrupted date formats, and duplicate records.

Why choose OFX over standard spreadsheets?

When you import an OFX file into tools like MYOB, Xero, Reckon, or desktop systems such as GNUCash and Moneydance, the software reads the embedded <FITID> tag. If you accidentally upload the same BNZ statement twice, the accounting software recognizes the existing transaction IDs and ignores the duplicates. This saves significant clean-up time during month-end or year-end reconciliation.

Importing BNZ OFX files into your system

Most accounting platforms accept OFX bank feed imports through a standard file upload workflow:

• MYOB: Go to your Banking menu, select Bank Feeds or Import Bank Statement, choose Open Financial Exchange (.ofx), and assign the file to your BNZ account.
• Xero: Open the relevant BNZ bank account, click Manage Account > Import a Statement, and upload the generated OFX file. For a dedicated Xero workflow, you can also use our BNZ to Xero converter.
• Moneydance & GNUCash: Select File > Import > OFX/QFX. The software will match the transactions directly against your local account register.

Comparison of statement processing methods

Example conversion: BNZ statement to OFX structure

Below is an example of realistic BNZ business account transactions and the corresponding structured OFX output generated by the parser.

Original BNZ statement records

Generated OFX data snippet

<STMTTRN>
<TRNTYPE>DEBIT</TRNTYPE>
<DTPOSTED>20231012120000</DTPOSTED>
<TRNAMT>-149.99</TRNAMT>
<FITID>20231012BNZ1499901</FITID>
<NAME>Spark NZ Ltd</NAME>
<MEMO>Direct Debit / Internet / ACC-9482</MEMO>
</STMTTRN>
<STMTTRN>
<TRNTYPE>DEBIT</TRNTYPE>
<DTPOSTED>20231014120000</DTPOSTED>
<TRNAMT>-820.50</TRNAMT>
<FITID>20231014BNZ8205002</FITID>
<NAME>Mainfreight NZ</NAME>
<MEMO>Bill Payment / Freight / INV-8812</MEMO>
</STMTTRN>
<STMTTRN>
<TRNTYPE>CREDIT</TRNTYPE>
<DTPOSTED>20231015120000</DTPOSTED>
<TRNAMT>3450.00</TRNAMT>
<FITID>20231015BNZ34500003</FITID>
<NAME>Customer Payment</NAME>
<MEMO>Direct Credit / Apex Retail / INV-1044</MEMO>
</STMTTRN>

Handling scanned and image-based BNZ statements

If you have physical BNZ statements received by post or archived scans, the optical character recognition (OCR) engine reads the document layout, separates table columns, and reconstructs the data. The tool verifies that the sum of all debits and credits equals the difference between the starting and ending balance shown on the printed page, identifying any potential scanning distortions before you export the file.

Security and file privacy

Your financial data is protected with 256-bit encryption during transfer. Uploaded PDF files and generated OFX files are processed automatically and deleted from the servers shortly after conversion. Your records are never stored long-term, shared with third parties, or used to train artificial intelligence models.