In a customer-level workflow, you can configure Add tag and Remove tag steps to act only on invoices that match the workflow trigger.
This prevents unrelated invoices such as paid or current invoices from being tagged.
For example, if a workflow starts when an invoice is more than 60 days overdue, the workflow can tag only those overdue invoices instead of every invoice belonging to the customer.
Existing workflows are unchanged. Tag steps continue to use all of the customer’s invoices until you change the setting.
Choose which invoices the step affects
Open a customer-level workflow.
Open an Add tag or Remove tag step.
Set the step to tag invoices.
Choose one of the following options:
All of the customer’s invoices the default.
Only the invoices matching the trigger only invoices that meet the trigger’s invoice conditions.
This setting is available only for invoice tags in customer-level workflows. It does not appear when the step tags the customer itself or when the workflow is invoice-level.
How matching works
Kolleno checks the trigger’s invoice conditions such as days overdue, balance, or status when the step runs.
The check is performed each time the step runs. If you update the trigger, the next run uses the new conditions.
If the trigger has no invoice conditions, every invoice matches.
Invoice conditions count whether they are in the invoice section or included within the customer conditions.
Preview the affected invoices
While configuring the step, Kolleno marks the invoices that match the trigger in the customer’s invoice list. Use this preview to confirm which invoices will be tagged or untagged.
Remove tags from matching invoices
The Remove tag step uses the same setting. When you choose the matching-invoices option, Kolleno removes the tag only from invoices that meet the trigger conditions. Other invoices keep the tag.
Important limitations
This option currently applies to invoices only. Credit notes and payments are not supported.
Workflow emails and text messages are not changed by this setting; they already use the trigger’s matching invoices.