Requirement
Jcurve solutions would like to create a BPAY Payment File Format Template in TXT format in NetSuite.
Solution
The requirement can be achieved by creating an EFT template using the TXT format for only Australian Dollars (AUD) based on the client’s requirement. Also need to create company bank details and entity bank details for the new Payment file templates for testing purposes. Then that template needs to be tested by creating the vendor bills for the test vendor and need to do the bill processing for verification.
Field Mapping
File Header Record
| Index | Field | Type | Notes | Length | Validation | Mandatory/ Optional |
| 1 to 2 | Record Type | Numeric | 00 (Static Value) A code ‘00’ indicating the Header record | 2 | Mandatory | |
| 3 to 5 | Payer Institution Code | Alphanumeric | company bank. Payer Institution Code (The Institution Code that is to receive the file. For example, ANZ, 114, C02, etc.) | 3 | Minimum length – 3 Maximum length – 3 | Mandatory |
| 6 to 13 | File Creation Date | Numeric | Format YYYYMMDD. The date of file creation. | 8 | Mandatory | |
| 14 to 19 | File Creation Time | Numeric | Format HHMMSS. The time of file creation. | 6 | Mandatory | |
| 20 to 22 | File Number | Numeric | Payment file administration.ID (last 3 digits) The unique file number for the file creation date. | 3 | Mandatory | |
| 23 to 201 | Filler | Alpha | Spaces | 179 | Mandatory |
Payment Instruction Record
| Index | Field | Type | Notes | Length | Validation | Mandatory/ Optional |
| 1 to 2 | Record Type | Numeric | 50 (Static Value) A code ‘50’ indicates a Payment Instruction record. | 2 | Mandatory | |
| 3 to 5 | Payer Institution Code | Alphanumeric | company bank. Payer Institution Code (The Code representing the Payer Institution. For example, ANZ, 114, C02, etc) | 3 | Minimum length – 3 Maximum length – 3 | Mandatory |
| 6 to 25 | Payment Account Detail | Alphanumeric | company bank. Account Number The relevant account number of the payer (BSB and account number), left justified with trailing spaces | 20 | Minimum length – 1 Maximum length -20 | Mandatory |
| 26 to 28 | Country of Payment | Alpha | AU (static value) The ISO alphabetic country code in which the Payer’s Account resides. This will be the code for Australia. | 3 | ||
| 29 to 31 | State of Payment | Alpha | company bank.State of Payment The alphanumeric state in which the Payer’s account resides if the country has state codes. | 3 | Optional | |
| 32 to 34 | Currency Code of Payment | Alpha | AUD (Static Value) The ISO alphabetic code denoting the currency of Payment. This should be the code for Australian Dollars (AUD). | 3 | Mandatory | |
| 35 to 44 | Biller Code | Numeric | Entity bank details. Biller Code The CIP assigned number denoting the Biller | 10 | Minimum length – 1 Maximum length -10 | Mandatory |
| 45 to 51 | Service Code | Numeric | Entity bank details. Service Code 0000000(Default Value) Reserved for future use. Currently zero filled. e.g., “0000000” | 7 | Minimum length –1 Maximum length – 7 | Mandatory |
| 52 to 71 | Customer Reference Number | Alphanumeric | Entity bank details.Customer Reference Number The number by which the Biller identifies the account that is being paid. Left Justified, filled with trailing spaces. The leading non-space part must be all numeric. | 20 | Minimum length – 1 Maximum length -20 | Mandatory |
| 72 to 83 | Amount | Numeric | Payment file administration. Amount The amount of the Payment, 2 digits of cents implied | 12 | Mandatory | |
| 84 to 91 | BPAY Settlement Date | Numeric | Payment file administration.Process Date The date is used for forward dating files, in YYYYMMDD format. If left blank, the date will default to the current business day. | 8 | Optional | |
| 92 to 131 | Payer Name | Alphanumeric | Payment file administration.Process User The name of the Batch Payer | 40 | Optional | |
| 132 to 151 | Additional Reference Code | Alphanumeric | Not required | 20 | Optional | |
| 152 to 201 | Discretionary Data | Alphanumeric | Not required | 50 | Optional |
File Trailer Record
| Index | Field | Type | Notes | Length | Validation | Mandatory/ Optional |
| 1 to 2 | Record Type | Numeric | 99 (Static value) A code ‘99’ indicates the Trailer record. | 2 | Mandatory | |
| 3 to 5 | Payer Institution Code | Alphanumeric | company bank.Payer Institution Code (The Institution Code that is to receive the file. For example, ANZ, 114, C02, etc.) | 3 | Minimum length –3 Maximum length – 3 | Mandatory |
| 6 to 13 | File Creation Date | Numeric | Format YYYYMMDD. The local date of file creation. | 8 | Mandatory | |
| 14 to 19 | File Creation Time | Numeric | Format HHMMSS. The local time of file creation. | 6 | Mandatory | |
| 20 to 22 | File Number | Numeric | Payment file administration.ID (last 3 digits) The unique file number for the file creation date. | 3 | Mandatory | |
| 23 to 31 | Number of Payments | Numeric | Payment file administration. Paid Transactions The total number of Payment Instructions in the file. | 9 | Mandatory | |
| 32 to 46 | Amount of Payments | Numeric | Payment file administration. Total Amount Paid The total amount of Payment Instructions in the file, 2 digits of cents implied | 15 | Mandatory | |
| 47 to 201 | Filler | Alpha | Spaces | 155 | Mandatory |
The following character set is allowed in a BPAY file:
- Fields that are marked ‘Alpha’ (Alphanumeric) in the ‘Type’ column are limited to:
- Letters: A-Z, a-z o Numbers: 0-9
- The following Characters: spaces ( ) , ampersands (&), apostrophes (‘), commas (,), hyphens (-), full stops (.), forward slashes (/), plus sign (+), dollar sign ($), exclamation mark (!), percentage sign (%), left parenthesis ((), right parenthesis ()), asterisk (*), number sign (#), equal sign (=), colon (:), question mark (?), left square bracket ([), right square bracket (]), underscore (_), circumflex (^) and the at symbol (@)
- ‘Optional’ Alphanumeric fields must be filled with spaces if no data exists
- Fields that are marked ‘Numeric’ in the ‘Type’ column are limited to:
- Numbers: 0-9
- ‘Optional’ Numeric fields must be filled with zeros if no data exists
- Unless otherwise indicated, numeric fields should be right justified and blank filled
Assumptions
- We have added the field mapping of a Payment file template based on the FRD Document.
- We will create a payment template only for Australian Dollars (AUD) in TXT format based on field mapping. So, the template will not work for multi-currency payments and payments in other currencies.
- We will not provide any validation for fields other than the mentioned validations.
Risk
- J&J will not create the actual company bank details and vendor bank details in this scope. Jcurve has to create company bank details and vendor bank details with Actual details.
- J&J created the field mapping based on FRD file. If the bank rejects this template due to incorrect field mapping after the development, J&J might have to revise the template. That is not considered in this scope. So that additional effort will be billed as support hours.