In this article we describe the functional range of our atriga integration and explain the advantages of using the integration for billwerk customers.
If you would like to use the atriga integration or have questions about the functionality please contact email@example.com.
The functionality and advantages of the atriga integration:
With the integration, receivables can be completely processed via the collection service provider atriga. billwerk maps all events from atriga in the system. Through the integration, the complete dunning process is passed on to the collection service provider. Your customers will be reminded in case of late payment, reminder fees can be charged and the collection process can be initiated if reminders are ignored.
Note: Currently, the integration to atriga only supports a transfer of open direct debit payments.
Configuration of atria in billwerk:
Go to Settings > billwerk Apps > 3rd Party Integrations and for "Atriga" go to "Edit":
Choose if you want to use atriga in test mode or live mode and store your atriga customer id as well as your code and save the settings:
Now configure the transfer to atriga at a desired time in the payment escalation:
Workflow of an atriga case
If a receivable is overdue and the payment escalation process is configured accordingly, the case is transferred to atriga with the action "Transfer to Atriga". As soon as the case has been transferred to atriga, a check takes place to determine whether it is accepted or not. An example for rejecting the case would be an incorrectly stored customer address.
When processing the cases, atriga regularly reports the corresponding status back to billwerk, which you can view in the customer's contract details. If a case is closed successfully and all open claims are settled, the atriga esclation is reset.
Additional contract details when using atriga integration
In the Contract Details of the customers, additional information is displayed when using the atriga integration. This gives you an overview of the dunning level of a customer's contract at any time.
Furthermore, you can view the triggered atriga events with the respective date, status and dunning level in the Contract History of the Contract Details.
The following statuses may apply here:
|billwerk has identified an overdue payment and must transmit the data to atriga
|billwerk has transmitted the data to atriga
|atriga has sent a feedback to billwerk whether the data could be processed (accepted) or not (rejected)
|First dunning phase initiated at atriga
|2nd Dunning Phase
|Second dunning phase initiated at atriga
|Debt collection initiated
|Status if a case could be closed successfully or not (this can be done already after the 1st dunning phase)