Your workflows are associated 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 (if you do not define it, the one set as “default” will automatically be applied). You can pause them shall need be, but cannot leave an account unassigned (workflow-wise).
When setting it up, you decide:
When it starts
How often are its reminders executed
The intervals of these actions are based on an invoice’s due date.
The carrying invoice
You assign one workflow per customer, not per invoice.
As a result, if a customer has several invoices falling in your workflow’s criteria, they will all be addressed at once.
The interval between its actions are based on what is called the carrying invoice. That is the oldest unpaid invoice of the batch.
Carrying invoice status transfer
As soon as your carrying invoice is paid, if other invoices from the managed batch are still due, 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.
You can decide whether you prefer your workflow to start over every time the status is transferred or continue as if nothing. This is set from the Workflow configuration panel, at the workflow logic level.
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.