Adds costs to the outstanding amount of the collection order, as a new invoice line. The higher amount is used in all following messages and steps.
Ports
| Port | Meaning |
|---|---|
| in | Input |
| out | Fires after the costs are added |
Settings
| Setting | Required | Explanation |
|---|---|---|
| Mode | Yes | Fixed amount (available); Percentage, WIK Netherlands and WIK Belgium (coming soon) |
| Amount | With fixed amount | Greater than 0; variables are allowed |
| Invoice number | Yes | Number of the cost line; variables are allowed |
| Description | Yes | For example "Collection costs" |
| Type | Yes | principal, collection costs, VAT, interest, transaction costs or other |
The date of the line is the day the node runs.
Coming soon
- Percentage of a choice of invoice types (for example only the principal), rounded up, down or as standard.
- WIK Netherlands and WIK Belgium: the legal scale for collection costs.
Use
- After the last reminder without payment: add costs and then send a final notice with the new amount.
- Combine with a Calculate node before it if the amount depends on something else.
Good to know
- Only add costs when you are legally allowed to (in the Netherlands after a final notice with a term of fourteen days). The workflow does not enforce this.
- Build the workflow so that costs are only added to a collection order that is still unpaid, for example behind the no response after x days port.
- To prevent double costs when a collection order passes the node twice, use a Logic node that checks whether the costs were already added.
See also
- Collection costs and WIK
- How a collection order works