Overview

Payment policies let you define automated rules that control what happens when a payment or bill is created. A policy can either block a transaction outright or require approval before it can proceed. Policies evaluate conditions you set - like payment amount thresholds, specific currencies, or destination countries - and take action when those conditions are met.

How Policies Work

Each policy has three parts:

Conditions - The criteria that determine when the policy applies
Action - What happens when the conditions are met (block or require approval)
Approval Steps - If the action is “Require Approval,” the ordered steps that define who must approve and how many approvals are needed

When a payment instruction or bill is created, TreasuryPath evaluates it against all active, deployed policies for the company. If a matching policy requires approval, the transaction enters the approval workflow. If a matching policy blocks, the transaction is stopped.

Policy Types

Policies apply to specific transaction types:

Policy Type	Applies To	Available Conditions
Payment	Payment Instructions	Instructed amount, instructed currency, destination country
Bill	Bills	Bill amount, bill currency

Creating a Policy

Navigate to Settings then Policies
Click New Policy
Enter a name and optional description
Select the policy type (Payment or Bill)
Choose the action: Block or Require Approval
Add condition groups with individual conditions
If the action is Require Approval, configure approval steps
Save the policy as a draft

Condition Groups

Conditions are organized into condition groups. Each group has an operator that determines how conditions within it are evaluated:

AND - All conditions in the group must be true
OR - At least one condition in the group must be true

Available Condition Fields

For Payment policies:

Field	Description	Allowed Operators
Instructed Amount	The payment amount	Equal, Not Equal, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal
Instructed Currency	The payment currency code	Equal, Not Equal, In, Not In
Destination Country	The destination country code	Equal, Not Equal, In, Not In

For Bill policies:

Field	Description	Allowed Operators
Bill Amount	The bill amount	Equal, Not Equal, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal
Bill Currency	The bill currency code	Equal, Not Equal, In, Not In

Supported currencies for currency conditions include: USD, EUR, GBP, CAD, AUD, JPY, CHF, CNY, HKD, and SGD.

Supported countries for destination country conditions include: US, GB, CA, AU, DE, FR, JP, CN, SG, and HK.

Policy Actions

Block - The transaction is immediately blocked and cannot proceed. The creator is notified that their transaction was blocked by a policy.
Require Approval - The transaction enters the approval workflow. You must configure at least one approval step to define who can approve.

Configuring Approval Steps

When the action is “Require Approval,” you define one or more approval steps:

Click Add Step
Give the step a name (e.g., “Manager Review”)
Assign approvers - Select team members who can approve at this step
Set the required approvals count (optional) - The minimum number of approvals needed. If left blank, all assigned approvers must approve.

Steps are executed in order. Step 1 must be fully approved before Step 2 becomes active. You can add multiple steps to create layered approval chains.

Draft vs Deployed

Policies have a deployment lifecycle:

Draft - The policy is being edited and is not active. Changes can be made freely.
Deployed - The policy is live and actively evaluating transactions.

When you deploy a policy, TreasuryPath takes a snapshot of the conditions and approval steps at that point in time. This means you can continue editing the draft version without affecting the live policy.

Versioning

Each deployed policy maintains a reference to the draft it was deployed from (deployed_from) and a version_date timestamp. This creates an audit trail of when policies were activated and what conditions were in effect at any given time.

Frequently Asked Questions

Can I have multiple active policies?

Yes. All deployed policies are evaluated when a transaction is created. If multiple policies match, the most restrictive action takes precedence (block overrides require approval).

What happens if I edit a deployed policy?

Editing a deployed policy creates a new draft version. The currently deployed version remains active until you deploy the updated draft.

Can I temporarily disable a policy?

Yes. Each policy has an active toggle. You can deactivate a policy without deleting it, and reactivate it later.

How do I test a policy before deploying?

Policies in Draft status do not evaluate transactions. You can review the conditions and approval steps, and only deploy when you are satisfied with the configuration.

Can one transaction trigger multiple policies?

Yes. TreasuryPath evaluates all active, deployed policies. If a transaction matches multiple policies, the strictest action applies: a block action from any matching policy will block the transaction, even if other matching policies only require approval.

Setting Up Payment Policies