Explore scenarios to gain insights into how to customize the conditions for approval policies with practical situations, and adapt them to fit the distinctive needs and goals of your organization.
On this page, we delve into a variety of real-world scenarios of conditions for triggering approval policies. These scenarios are designed to help you understand how approval policies can be automatically set to specific invoices and how to customize these conditions to address specific operational, compliance, and governance needs within your organization.
The conditions mentioned on this page are designed using the
TesouroScript and must be inserted into the trigger
field. Check the Evaluated string
section for further information about the syntax. - The "{event_name == "submitted_for_approval"} " condition is mandatory in triggers. - The if, then, and else statements are not allowed
in triggers. - When a payable has enforce_approval_policy_id set, the TesouroScript trigger
conditions are ignored.
By amount, currency, tags, AND specific counterpart
Set an approval policy for all invoices worth more than 1000 USD, from a specific counterpart AND with specific tags:
{ "name": "By amount, currency, tag, AND specific counterpart", "description": "Invoices worth more than 1000 USD, from a specific counterpart AND with specific tags", "trigger": { "all": [ "{event_name == 'submitted_for_approval'}", "{invoice.amount > 100000}", "{invoice.currency == 'USD'}", "{invoice.counterpart_id == '398b2748-b255-46da-b8dc-a01219539ec8'}", "{'d566f374-463a-4a07-b252-2eb0200d62ce' in invoice.tags.id}", "{'398b2748-b255-46da-b8dc-a01219539ec9' in invoice.tags.id}" ] }, "script": [ ... ]}