Before you start
Please download the suggested API integration process flow document and use it as a reference when developing.
Kindly adhere to the Netcash brand guidelines when developing.
Programmers Guide
Refer to our Programmers guide for more detail on how to apply the required methodology in this document.
Ensure that the settings for developers are adhered to before you proceed with your implementation.
Web Service Methods
The list of Netcash web service methods can be found here.
Quick Start Guides
Quick Start Guides will help you understand this service and get you started.
Introduction
The Netcash Bulk Statement Download is a consolidated file of daily client statements.
The client elects to have the Netcash statement downloaded to a central point for integration into a software product.
The Netcash system determines all the client accounts to be included in the bulk statement, extracts the daily statement, and concatenates all the statements into a single file which is zipped and transferred to a pre-defined location
Statement format
The file is a tab-delimited text file that is zipped and sent via sFTP to the relevant external location.
The file contains a daily statement for each client configured for the download. This is set up on the Netcash web front-end under the Sage Connect client profile.
Each client statement is defined by a statement header and footer. The file is bound by a statement header and footer.
File header
Occurs once at the start of the file
| Field | Name | Type | Value |
| 1 | Record identifier | A | FH |
| 2 | File date | N | CCYYMMDD (same date as the transactions in the file) |
| 3 | Software vendor key | AN | The GUID key associated with the transactions in the file |
Statement header
Occurs multiple times at the start of each client statement
| Field | Name | Type | Value |
| 1 | Record identifier | A | SH |
| 2 | Statement date | N | CCYYMMDD (same date as the transactions in the file) |
| 3 | Account number | N | The Netcash account number for the client |
| 4 | Account service key | AN | The GUID key associated with the client’s Account service |
Statement detail
| Field | Name | Type | Value |
| 1 | Transaction date | AN | CCYYMMDD |
| 2 | Transaction type | A | See appendix 1 |
| 3 | Transaction id | N | Unique Netcash reference |
| 4 | Description | AN | Short description of the transaction |
| 5 | Amount | N | Transaction amount in cents |
| 6 | Symbol | AN | Positive/Negative |
| 7 | VAT | N | VAT amount |
| 8 | Extra 1 | AN | User-defined data received in upload file |
| 9 | Extra 2 | AN | User-defined data received in upload file |
| 10 | Extra 3 | AN | User-defined data received in upload file |
Statement footer
Occurs multiple times at the end of each client statement
| Field | Name | Type | Value |
| 1 | Record identifier | A | SF |
| 2 | End of statement indicator | AN | 9999 |
File footer
Occurs once at the end of the file
| Field | Name | Type | Value |
| 1 | Record identifier | A | FF |
| 2 | End of file indicator | AN | #END# |
Table 1
Click here for a list -and explanation of unpaid transaction codes.
Netcash brand guidelines
Please refer to the Netcash brand guidelines here when using any logos, images, icons, labels, descriptions, and references to Netcash in your software.
Testing
See Testing section for more details. If you require any integration assistance contact our technical support team