Account Upload
Operation Region
The Account Upload specification is different in each operating region. Please select a Region to show the supported fields in that region.
Select your region to see relevant specifications:
Uploading Accounts
You can create new customers and accounts, and you can update existing customers and accounts via Account Upload.
This document is updated to require additional fields to be completed to support accurate calculation of Statute of Limitations date, as well as for complete Notice of Assignment details.
Sample Accounts
The Sample file above has the following details:
- John has one account
- Olivia has two accounts
- All available account upload fields as included
- All mandatory fields are populated for the sample accounts
info
We recommend using a date-based filename convention: YYYY-MM-DD-hh-mm-ss.csv, based on the time that you (or your system) generated the file.
Account And Customer Details
| Header | Format | Description |
|---|---|---|
| AccountRef * | String, unique constraint | Unique value representing the account in your system. Use the same reference for updating existing accounts. |
| StatementOfWorkID * | String | The Statement of Work to assign this account to. Once assigned, this value cannot be changed. |
| DueDate * | String date formatted as YYYY-MM-DD | Date when the account was due for payment. This is used for allocating payments to the account with the oldest due date. |
| ChargeOffDate | String date formatted as YYYY-MM-DD | Date when the account was charged off |
| DateOfLastPaymentReceived ⚠️ | String date formatted as YYYY-MM-DD | Date when the last payment received from customer was processed. Can be blank if not applied. ⚠️ This date must be before referral time |
OutOfStatuteDate  | String date formatted as YYYY-MM-DD | Date when the statute of limitations expires. |
| DelinquencyDate | String date formatted as YYYY-MM-DD | Date when the account first became delinquent. This value cannot be changed. |
| Balance ⚠️ | Integer representing a monetary value in cents, e.g. 100 means $1.00 | The amount to collect for this account. ⚠️ This value must be greater than zero when creating new accounts and it will be ignored when updating existing accounts. For updating this value, see Transaction Upload. ⚠️ Where commission is passed on to the customer, this balance should not include the commission that InDebted will collect in addition to the referred amount. |
| CustomerRef * | String, unique constraint, cannot contain any PII | Unique value representing the customer in your system. Use the same reference for updating existing customers. |
| Title | Constant, e.g. Mx | Customer's title. See all Customer Titles below. Invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| FirstName * | String | When the customer has a last name, their last name is required for regulatory compliance. |
| MiddleName | String | When the customer has a last name, their last name is required for regulatory compliance. |
| LastName | String | When the customer has a last name, their last name is required for regulatory compliance. |
| DOB SOON will be Required | String data formatted as YYYY-MM-DD | |
| Emails | String delimited by semicolon, e.g. joe@abc.com; joe@def.com | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| Phones | String delimited by semicolon, including country code, e.g. +61444555666; +61999888777 | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| AddressLine1 | String, required when any address field is provided | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| AddressLine2 | String, optional | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| City | String, required when any address field is provided | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| State | String, required when any address field is provided, except for the United Kingdom and New Zealand | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| Postcode | String, required when any address field is provided | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
| Country | String, required when any address field is provided | For regulatory compliance, at least two of the following must be provided: date of birth, email, phone, address. Further, invalid values will be ignored so the customer and account are still created successfully, provided all other validations succeed. |
Product Information
This information may be used for different use cases like BNPL Merchants, Credit Card and Loan Labels. This helps your customers remember their purchase or agreement which in turn improves your collections performance.
Download a sample file with Product Information.
| Header | Format | Description |
|---|---|---|
| ProductVendor | String | The name of the business or entity where the purchase was made and accepts the payment. It's the name under which the transaction is processed and appears on the credit card statement of the cardholder. For example, if you make a purchase at a store called "ABC Mart," "ABC Mart" would be the merchant name that appears on your credit card statement for that transaction |
| ProductName | String | Name of the product or service such as the good purchased with BNPL. |
| ProductAmount | Integer representing a monetary value in cents, e.g. 100 means $1.00 | The purchase or service amount agreed upon. |
| ProductAgreementDate | String date formatted as YYYY-MM-DD | Date when the purchase or service agreement has taken place. |
Client Display Name
If your company operates under multiple brands or branches and each customer is familiar with a different name, you can customise the name to be displayed for each customer which helps setting up the context for collections.
Download a sample file with Client Display Name.
| Header | Format | Description |
|---|---|---|
| ClientDisplayName | String | Your brand or branch name to be used in all communications as a replacement for your company name, specifically for this customer. |
Customer Titles
| Title |
|---|
Dr |
Madam |
Master |
Miss |
Mr |
Mrs |
Ms |
Mx |