Extended CSV statement format
The Extended CSV format supports all New Payments Platform (NPP) transaction information.
Format overview
Field delimiters
The Extended CSV file is a comma delimited file (CSV).
Record termination
Each record is terminated by a CR/LF end-of-line pair.
Leading zeros
All leading zeros within file extracts will be provided, including the following leading zeros:
- Transaction Codes (e.g.
001
,009
etc). - Customer Account Number (e.g.
032000
,000007
,032000000016
).
File specification
Line 1 of each CSV file will contain a header record as follows:
Transaction date,Account number,Account name,Currency code,Closing balance,Transaction amount,Transaction code,Narrative,Serial number,Segment account number,Payment Information ID,Instruction ID,Transaction ID,Value Date,Transaction Date/Time,Debtor Name,Creditor Name,End To End Id,Remittance Information/Unstructured 1,Remittance Information/Unstructured 2,PayId Type,PayId Value,Reversal Reason Code,Original Transaction Id
Following the header line, each transaction for the account will be included as follows:
Field | Field Name | Field Length (max) | Description |
---|---|---|---|
1 | Transaction Date | 8 | Format is YYYYMMDD , e.g: 17th March 2017 will display as 20170317 . |
2 | Account Number | 12 | BSB Number + Account Number, e.g: 032000123456 . |
3 | Account Name | 25 | Account Name. |
4 | Currency Code | 3 | The currency of the account, e.g: AUD = Australian Dollars. |
5 | Closing Balance | 17 | Account closing balance, signed for negative amounts, e.g: 1234.56 or -1234.56 . |
6 | Transaction Amount | 17 | Transaction amount, signed for negative amounts, e.g: 1234.56 or -1234.56 . |
7 | Transaction Code | 3 | Three digit bank transaction code, e.g: 050 . |
8 | Narrative | 240 | Transaction narrative. |
9 | Serial Number | 7 | Transaction serial number, e,g: 1234567 . |
10 | Segment Account Number | 12 | BSB Number + Account Number of the segment account the transaction was processed against. Blank if not processed against a segment account. |
Note: The following fields will only be populated when the information is available. | |||
11 | Payment Information Id | 35 | Customer supplied reference for batch files. Present for debits only, blank otherwise. |
12 | Instruction Id | 35 | Customer supplied reference for individual ISO payments, blank otherwise. |
13 | Transaction Id | 35 | Unique reference for the transaction for both internal (WBC to WBC) and external (WBC to Other Bank or Other Bank to WBC) transactions. This is used by the industry to ensure uniqueness of transactions within the NPP clearing process. |
14 | Value Date | 8 | Format is YYYYMMDD , e.g: 17th March 2017 will display as 20170317 . |
15 | Transaction Date/Time | 20 | Posted date and time of the transaction. Format is UTC DateTime. e.g 5pm, 17th March 2017 will display as 2017-03-17T17:00:00Z |
16 | Debtor Name | 140 | The name of the payer of the transaction. |
17 | Creditor Name | 140 | The name of the payee of the transaction. |
18 | End To End Id | 35 | The End To End Id of the transaction. Blank if not present. |
19 | Remittance Information/Unstructured 1 | 140 | The first 140 characters of the transaction description. |
20 | Remittance Information/Unstructured 2 | 140 | The next 140 characters of the transaction description. |
21 | PayId Type | 4 | The type of PayId used for this transaction. Will be one of the following values:
|
22 | PayId Value | 256 | The PayId used for this transaction. This is the PayId to which the payment was directed. Blank if a PayId was not used for this transaction. |
23 | Reversal Reason Code | 4 | Four character code indicating why the transaction was reversed. Blank if this transaction is not a reversal or refund. |
24 | Original Transaction Id | 35 | Transaction Id of the transaction being reversed. Blank if this transaction is not a reversal or refund. |
If there are no transactions for an account, one record will be included containing the account details and closing balance, and blanks for the remaining fields.
Enrichment support
If you receive a data-enriched (bulked, reconciled, debulked or enriched) statement, there will be some modifications to the transaction lines.
Bulked/reconciled enrichment
For bulked and reconciled enrichment, the following modifications will be performed to the transaction lines:
Payment Information Id
: This field will be populated with theBatch Payment Reference Code
.Transaction Id
: This field will be populated with a unique, BankRec-generated transaction identifier.End To End Id
: This field will be populated with theBatch Payment Code
.Payment Information Id
: This field will be populated with thePayment Information Id
from the Payment Batch if available, otherwise blank.Creditor Name
: This field will be populated if available, otherwise blank.
Debulked receivables enrichment
For debulked receivables enrichment, the following modifications will be performed to the transaction lines:
- Each transaction line that previously represented a bulk settlement record will be replaced with multiple transaction lines that represent multiple individual payments that formed part of the bulk settlement.
Transaction Id
: This field will be populated with a unique, BankRec-generated transaction identifier.Payment Information Id
: This field will be populated if available, otherwise blank.Creditor Name
: This field will be populated if available, otherwise blank.Debtor Name
: This field will be populated if available, otherwise blank.Instruction Id
: This field will be populated if available, otherwise blank.End To End Id
: This field will be populated if available, otherwise it will be populated with theBatch Payment Reference Code
.
Debulked payables enrichment
For debulked payables enrichment, the following modifications will be performed to the transaction lines:
- Each transaction line that previously represented a bulk settlement record will be replaced with multiple transaction lines that represent multiple individual payments that formed part of the bulk settlement.
Transaction Id
: This field will be populated with a unique, BankRec-generated transaction identifier.Payment Information Id
: This field will be populated if available, otherwise blank.Creditor Name
: This field will be populated if available, otherwise blank.Instruction Id
: This field will be populated if available, otherwise blank.End To End Id
: This field will be populated if available, otherwise it will be populated with theBatch Payment Reference Code
.
External entry enrichment
For external entry enrichment (i.e, transactions enriched with information from an external EFT feed), the following modifications will be performed to the transaction lines:
Transaction Id
: This field will be populated with a unique, BankRec-generated external transaction identifier.Creditor Name
: This field will be populated if the transaction is a debit on your statement.Debtor Name
: This field will be populated if the transaction is a credit on your statement.End To End Id
: This field will be populated with thePayment Reference
sourced from the external feed if available, otherwise blank.
For RTGS/OTT transactions, the following modifications will also be performed to the transaction lines:
Remittance Information/Unstructured 1
: This field will be populated with thePayment Detail
from the RTGS/OTT transaction.
If you require further enrichment, you should discuss this during your implementation.
Difference between Extended CSV and Corporate Online CSV statement formats
In other CSV formats, all transactions will be included in the file, however NPP transaction narratives may be truncated, and any additional NPP transaction data will not be included. The Extended CSV format will include complete NPP transaction details for NPP transactions. For non-NPP transactions, all available data will be included, however the additional NPP fields (Payment Information Id
onwards) will be blank.
Sample files
The following files are intended to be examples only.
NPP sample transactions
Download the NPP sample Extended CSV file.
This file contains examples of all NPP transaction codes, and how they will appear in a standard Extended CSV statement.