Your workflows are associated by default with a customer, not an invoice. Know how they are triggered to optimize your communication!

Each of your customers will be assigned to a workflow. It can be the “default” one or a specific one if a smart rule is in place. You can pause them as needed or unassign the workflow from the customer.

When setting it up, you decide:

• The logic that carries the workflow

• When the first action should be triggered

• How often are its actions executed

The intervals of these actions are based on an invoice’s due date. ⤵️

The carrying invoice

You can assign one workflow per customer.

As a result, if a customer has several invoices falling in your workflow’s criteria, they will all be addressed at once, depending on the tags used in your templates. See how to customize your action templates.

The interval between its actions is based on the carrying invoice, which is the oldest unpaid invoice of your customer.

If the customer has multiple invoices with the same due date, the carrying invoice will be the one with the highest total.

Carrying invoice status transfer

• As soon as your carrying invoice is paid, if your customer has other outstanding invoices, the oldest one will inherit the status.

• If an older invoice is uploaded to Upflow after a workflow has started, it will also steal the spotlight and become the carrying invoice. Therefore, it'll restart the workflow based on this invoice's due date and the workflow logic.

Triggers

Your actions are triggered by a delay you define following the carrying invoice’s due date. This delay is calculated straightforwardly and can be overruled by settings or context.

Do you have any questions? Click on Submit a request above to see suggested articles, or Contact our Support team.