Third Party Claim
The standard input file for Third Party Claim
File type
- Delimited file format such as CSV
- Excel format (*.xlsx)
Standard fields
Column headers
Please note that the column names provided are illustrative. You have the flexibility to use your preferred column names, and we can correspondingly map them to our standard input fields.
| Column Name | Description | Mandatory |
|---|---|---|
| Brand | Brand + Portfolio combination maps to CreditorId in the Credit Clear Digital platform. | Yes - If client the only has multiple brands No - Otherwise |
| Portfolio | Brand + Portfolio combination maps to CreditorId in the Credit Clear Digital platform. | No |
| Client Reference No | Represents a unique ID for the claim when available. | No |
| Claim Number | The claim number is used as a unique ID when the Client reference is not available. | Yes |
| Payment Reference Number (PRN) | The payment reference number is associated with the claim. | No |
| Status | Represents the status of the claim. Supported values are: Active: The claim is eligible for appropriate treatment on the platform, and the customer can view the link and interact with the portal. Hold: Platform activities such as campaign communication, payment plans, etc will be paused for this claim Closed: The claim is closed in the system. The customer can perform no activity on the platform | Yes - If UPDATE on claims are also sent in file No - If only NEW claims are sent in file |
| Third-Party First Name | The third-party first name | Yes - If the third-party last name or company name is not supplied No - Otherwise |
| Third-Party Last Name | The third-party last name | Yes - If the third-party first name or company name is not supplied No - Otherwise |
| Third-Party Company Name | The third-party company name | Yes - If the third-party first name or last name is not supplied No - Otherwise |
| Third-Party DOB | The third-party date of birth If customer verification is required, providing this field is recommended as part of the 3-point verification challenge. | No |
| Third-Party Postal Code | The third-party postal code In the event of natural disasters or special events affecting certain postcodes, this field allows clients to halt communications promptly. Therefore, if this field is accessible, it’s highly recommended to include this field. If customer verification is required, providing this field is recommended as part of the 3-point verification challenge. | No |
| Third-Party Location | The third-party location. | No |
| Third-Party Mobile | The third-party mobile If customer verification is required, providing this field is recommended as part of the 3-point verification challenge. | Yes - If the client has a mobile-only workflow No - otherwise |
| Third-Party Email | The third-party email If customer verification is required, providing this field is recommended as part of the 3-point verification challenge. | No |
| Third-Party Communication Preference | This field specifies the customer’s communication preference, also referred to as the preferred method of contact. It’s important to note that the system may still use other provided methods for communication. The supported values are: Mobile | No |
| Third-Party Vehicle Registration | The third-party vehicle registration | Yes |
| Third-Party Rego state | The third-party registration state | No |
| Third-Party Vehicle Colour | The third-party vehicle colour | No |
| Third-Party Vehicle Year | The third-party vehicle year | No |
| Third-Party Vehicle Model | The third-party vehicle model | No |
| Third-Party Vehicle Make | The third-party vehicle make | No |
| Incident date or Date of loss | The date when the incident occurred | Yes |
| Incident Cause | The cause of the incident | No |
| Incident Location | The location where the incident occurred | No |
| Incident Description | The description of the incident | No |
| Insured First Name | The insured first name | No |
| Insured Last Name | The insured last name | No |
| Insured Company Name | The insured company name | No |
| Insured DOB | The insured date of birth | No |
| Insured Mobile | The insured mobile number | No |
| Insured Vehicle Registration | The insured vehicle registration number | No |
| Insured Vehicle Registration State | The insured vehicle registration state | No |
| Insured Vehicle Year | The insured vehicle's year of manufacture | No |
| Insured Vehicle Make | The insured vehicle make | No |
| Insured Vehicle Model | The insured vehicle model | No |
| Recovery Amount | This field represents the amount to be recovered from the third party. If left empty or if this column is not present, it is assumed that no repair cost is available, and the amount defaults to 0. | Yes - If UPDATE on claims are also sent in the file No - if only NEW claims are sent in the file. |
| Callback number | When provided, this number will be displayed to customers wishing to call and discuss their claims. This is particularly useful if your company has distinct phone numbers for different customer cohorts. However, if your company uses a single phone number for all customer inquiries, this field is not necessary. | No |
| SendInstantMessages | This field enables you to send instant messages to customers using pre-configured message templates. These templates can be set up in the client portal. The supported instant message types are: Sms The value must be a string that includes the desired instant message types, separated by your chosen delimiter. For instance, to send both SMS and Email messages, the value should be formatted as Sms:Email, with the colon serving as the separator | No |
Non-standard fields
Apart from the fields above, if there is data in your file that you feel is relevant for collections and campaigns, you can include them in your upload. The Credit Clear system can map all non-standard fields from your file and lets you use them in workflows and campaigns for the best results.
Please let your digital solutions consultant know of non-standard fields so that we can map them appropriately in the platform.
Updated 23 days ago