Consumer Data Mapping

In a perfect world, your collection system will have all the data points needed for an integration with the website, which would allow you to control the functions of the web portal using only a single system. In the real world we know that your collection system may not be configured to send all the data needed for a full integration. This is where Custom Integrations can help.

Custom Integrations are setup during the onboarding process. The can be used to modify some of the data being imported from your collection system. A common use is to add new fields that your collection system does not have.

For a full list of fields please see the Standard CSV Consumer Data Import article. These fields are the data that can be sent to the web portal. If some of them are not available in your system, we can assist you during the onboarding by adding some custom mappings.

For example, your collection system may have standard fields such as name, balance, etc. But it does not have the concept of Minimum Payment because it is not a web portal. When this happens, there may be no way for you to import a minimum payment to control what the website will allow. Let's say, for example, that you want the minimum payment to be 10% of the current balance which would be a dynamic amount based on each consumer. Your collection system has no way to store or calculate this. This is where a Custom Integration can be added.

All Custom Integrations need to be configured at Onboarding. They are rules that are not intended to change. 

Here are some example of custom integrations that can be added. All logic needs to be based on data that already exists on each consumer record. 

For a list of fields that can be mapped click here:

https://support.concepts2code.com/support/solutions/articles/44002503591-standard-data-fields

• CanMakePayment - Set this field to true when status is "Active". False for all other statuses.
• AcceptCheckingPayment - Set this to true if ClientName is "Bank of Buffalo". False for all others
• AcceptCreditCardPayment  - Set this to true for all customers where CanMakePayment is true. False for all others.

In all three examples, custom logic will be applied in order to set the value of the field. You do not need to supply the field as part of your data feed. If you have any API integration, the custom Integration will be applied after pulling in the API data.

Custom Integrations cannot be use if your logic cannot be described simply and absolutely. This means that the data fields provided for each customer must be the only variables needed to compute the new value. Customizations are a simple calculation. In general, if you can use excel to write a formula for the calculation that only relies on the data in that row, then we can help you customize the same logic with a custom integration.