Client Data Files is a suite of CSV files containing data pertaining to customers, payschedules, contract prefixes, transactions, payout, etc. It is a service offered to our Clients by Debitsuccess.
| Info |
|---|
This service is available by request only through |
...
our Account Management team. |
Debitsuccess will deliver these files once per day to the client’s choice of cloud-based storage, either AWS S3 bucket, Azure Data Lake or Azure Blob Storage , that is managed by them.
The following is a list of files that can be requested through this service. Data provided is an end of day figure (as of midnight prior day). To learn more about fields provided in each file, please click on the file names below:
File naming: DS_<FacilityGroup>_<FileName>_<YYYYMMDD><Timestamp>
Note: Timestamp → HHMMSS
Other Information:
The fields in the CSV files are separated using the pipe delimiter. Empty or Null fields will be an empty string.
File sending : Clients will receive each of the files they are subscribed for daily, regardless of whether data exist in the file or not.
i.e. If there is no data from the preceding day, the file will only contain the header row. In the event of an issue during file generation, Debitsuccess will hold off sending the entire set of files until the issue is resolved to prevent partial data sending.
File Name | File Description | |
|---|---|---|
| 1 | Newly loaded customer accounts from yesterday | |
| 2 |
One-off and recurring payschedules which have been added to active customer accounts from yesterday | |
| 3 |
One-off and recurring payschedules which exist in active customer accounts |
CF? - Payschedules for customer accounts, that are either current or have a start date in the future
| 4 | Cancelled customer accounts from yesterday | |
| 5 |
Active customer accounts with |
an amount |
owing, as at the end of the day yesterday | |
| 6 |
Customers who are currently on suspension and/or have future suspensions
Active customers who are currently on suspension and/or have suspensions with a start date in the future | ||
| 7 | Client's contract prefix for each business account | |
| 8 |
A list of all customers active for the Client as |
of the end of the day yesterday | ||
| 9 | Summary of client’s payout run |
from yesterday | |
| 10 |
Transaction level detail file for customer payments, from all payout runs in the PayoutSummary file. | ||
| 11 | Transactions recorded against a customer’s account from yesterday | |
| 12 | One-off supplemental fees payschedules added from the prior day |
<Only applicable to Goodlife Health Clubs Australia>
CF? - 1. should we avoid naming the client for public docs? 2. should we exclude this from public as the process is only there for GL?<Client specific process only> |