Plans supporting this feature: Starter Growth Enterprise
A dunning plan is an automated communication process that has the aim to push customers to update their payment information and create an appropriate strategy to handle the subscriptions or the transaction status in case of delay in payment
The following can be defined:
how many emails will be sent out
how many days the process will wait between the different email sent outs and the end outcome.
Note
Multiple dunning plans can be set up and referred to when setting up a plan.
The setup of the process can be done in Configurations > Finance and accounting > Dunning management.
The default dunning plan
| Header including > Created: Date when the dunning plan was created. > Hard declines: shows if a grace period is included or not.
|
Email schedule: Showing the days of the reminder sent out and the waiting intervals. |
By clicking on 
the Email Templates open.
Create a new dunning plan
Click on New to create a new dunning plan.
Decide if the newly created dunning plan should be set as default plan by activating the default scheme toggle.
Define the grace period. A grace period is the period during which an overdue payment will not be dunned.
Decide if this dunning plan should have a grace period for hard declines.
A "hard decline" means a payment transaction was definitively rejected by the payment processor and is unlikely to succeed if retried.In the email schedule box, the dunning process can be defined - after how many days emails are sent and which email templates are sent.
Decide what shall happen as final action.
Expire the subscription
Put the subscription on hold
Keep subscription active
Click on Create to save.
Delete a dunning plan
Note
Only additional dunning plans can be deleted. One default plan always needs to be configured.
Click on Edit.
In the top right-hand corner, the delete button appears.
Click on Delete.
Caution
Once the plan has been deleted, it cannot be restored.
Creation of a one-time payment following the dunning flow
This guide shows how to handle a one-time payment, which will go into your dunning process if it is not paid in time.
In order to set up a dunning process for a one-time payment, you need to create a customer first. If you have not done this by now, please read this article How to create a customer.
Please read this guide as a preparation: How to create a plan.
Create a new plan:
We suggest to call it Manual.
Set the Price in the Pricing box to 0.
Set the Billing scheduling type in the Billing box to Manual on-demand.
The subscription we will create later will not be renewed since this plan is created with a scheduling type Manual.
Note
The plan can also be created via API: https://docs.frisbii.com/reference/createplanjson.
Create a customer or ensure that it is created.
Add the plan to the customer:
Click on Create Subscription on the Customer Details page.
Choose the plan Manual.
Choose in the Payment option box the option Hosted Page.
Click on Submit.
Copy the Payment link you receive in the pop up window by clicking on
.png)
.Note
Send this link to your customer in an email saying "Here you can save your card for paying invoices later on".
Note that it is only customers with no card saved, that need to go through the process of saving their card.
The creation of the subscription can also be done by API: Create subscription.
Stay on the Subscription Details page. Click on Create Invoice which leads you to the Charge Subscription screen.
Select Automatic in the Charge Options.
In the Invoice options box activate the Include switch for creating Order lines.
Note
In order to create invoices for this subscription, you can also use the API https://docs.frisbii.com/reference/createsubscriptioninvoice.
If your customer already added a payment method, then you do not need to continue with the next step.
Go back to the Customer Details page and set a Payment Method by clicking on Add payment method.
Select Online transaction, which will settle the amount instantly and send a receipt to the customer.
If the settle cannot be carried out, the invoice will go into the dunning flow since it's created under the subscription.
Synchronize with an ERP system for invoice sent out
Learn how to conduct a simple integration between Frisbii Pay/Frisbii Billing and your ERP system to send invoices from your ERP to your customers.
Caution
This guide addresses developers or administrators having a general technical understanding. You need to know what APIs and webhooks are.
You will need to build a middleware between Frisbii Pay/Frisbii Billing and your ERP system to communicate with both systems.
Create two dunning plans. One dunning plan for card payments and one dunning plan for invoice payments.
The dunning plan for invoice payments
must not send out any mails
and the Final action is set to Keep subscription active.
Put the Grace period
to the number of days your customers have to pay the invoice that is sent from your ERP system.
Create two plans.
The first plan: for customers who would like to pay by card.
The second plan: for customers who would like to pay by invoice.
Set the corresponding dunning plan on each plan.
Subscribe to webhooks from your Frisbii Pay/Frisbii Billing account.
You can insert your webhook URL in the Webhook interface.
Wait for an invoice_created webhook.
When you receive the webhook call the get_invoice API and look at the plan argument.
Here you will find the plan_handle.
Look up the plan handle by calling the get_plan API.
Check if the plan is the invoice plan you made earlier.
Note
You could also store the plan handles instead of calling Frisbii Pay each time.
If the plan_handle matches the plan you made for invoice payments, you can create an invoice in your ERP system and send out an invoice to the customer.
Now call manual_settled to set the correct status on the invoice created in Frisbii Pay/Frisbii Billing*.
You can choose bank_transfer under the method argument.
The invoice will now have status settled in Frisbii Pay/Frisbii Billing and paid by bank transfer.
Note
* If your ERP system can notify you when the customer has actually paid the invoice, you have to wait to call the manual_settle API until your ERP system has told you that the invoice has been paid. In this way, both systems will be fully synchronized.