Skip to main content
Collections is the process that follows an invoice that isn’t paid: retries, reminders, and the final decision to mark it uncollectible. Orvlin runs it automatically once you set the rules.

​
Payment retries

When a charge fails, Orvlin retries it on a schedule. Read and change the schedule:

​
Dunning policies

A dunning policy is a set of steps: reminders sent to the customer, and actions taken if the invoice stays unpaid. Create a policy with a name and at least one step.

​
What your customers and team see

  • Customers receive reminders according to the policy you set.
  • Your application gets webhooks for each state change:
See Webhooks for the signature and delivery rules.
  1. Set a retry schedule that spreads attempts over at least a week, so one bad day doesn’t end a relationship.
  2. Add a dunning policy with a reminder before the first retry, and a final notice before the invoice is marked uncollectible.
  3. Route invoice.marked_uncollectible to your team, so someone decides on the account.
  4. Review the collection metrics each month.
Marking an invoice uncollectible is a significant step. Confirm the account status with the customer before it happens.