...
File Name | File Description | |
---|---|---|
1 | Newly loaded customer accounts from yesterday | |
2 | Payschedules which have been added to active customer accounts from yesterday | |
3 | Payschedules One-off and recurring payschedules which exist in customer accountsCF? - Payschedules for customer accounts, that are either current or have a start date in the futureactive customer accounts | |
4 | Cancelled customer accounts from yesterday | |
5 | CustomersOverdueCustomer accounts with amount owing | CF? - Customer accounts with an amount of overdue funds owing, as at the end of day yesterday |
6 | CustomersCurrentAndFutureSuspensionsCustomers who are currently on suspension and/or have future suspensions | CF? - 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 | Client’s current customer listing CF? - A list of all customers active for the Client as at the end of day yesterday | |
9 | Summary of client’s payout run CF? - Summary of client’s payout run from yesterday | |
10 | PayoutTransactionsTransactions which have been paid-out as part of the payout run in the PayoutSummary file | CF? - 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 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> |