A collection order starts with one or more invoices of a customer, runs through a flow that sends messages and waits, and ends with a payment, a settlement, or "ended without payment".
The life cycle
- Creation. The collection order comes in through an integration (API, Collection Sync) or an upload. The timeline shows "New invoice" and "Start in {flow}".
- Messages. The flow sends messages (email, SMS, letter) according to its steps. Letters first go through Quality control. Every message sent appears in the timeline ("Email: {template}") and on the Messages tab.
- Customer response. The customer pays through the paylink, requests a settlement or makes a payment promise. A payment comes into the collection order automatically, and the collection order gets the status Paid.
- Exceptions. Bounces, missing contact info or a missed term create a task and can pause the collection order.
- End. The collection order is Paid or Ended without payment (the flow has finished without full payment). You can resume an ended collection order or switch it to another flow.
Action by an employee
| What | Where |
|---|---|
| Change amounts | Editing the invoice lines of a collection order |
| Another flow or step | Switching a collection order to another flow |
| Pause, resume, withdraw | Pausing, resuming, rescheduling or withdrawing a collection order |
| Give a separate paylink | Creating a paylink |
| Record a payment made outside POM | Marking a message as paid |