Rule Fields Reference

Every rule in the Policy Engine is built from a set of fields that together define exactly when a rule applies and what happens when it does. This reference covers each field, what it accepts, and how it affects rule matching

​

Field Names

Each policy rule is defined by the following fields. All fields except Rule Name and Frequency Actions are optional filters, leaving a field blank means “any value is permitted.”

​

Action Types

PrimeVault supports the following transaction action types, each configurable with independent policies:

​

Frequency Actions

Frequency Actions define the spend limits and approval requirements that apply within a given time window. You can configure up to 5 frequency tiers per rule.

​

Time Windows

• Per Transaction:  Limit applies to each individual transaction
• Daily:  Cumulative limit resets every 24 hours
• Weekly: Cumulative limit resets every 7 days
• Monthly: Cumulative limit resets each calendar month
• Quarterly: Cumulative limit resets each quarter

​

Action Type (within Frequency)

For each frequency tier you can configure one of two action types: you can configure as many as you want let say 200 you need 2 approval 300 you need 3 approval and 400 block Additional Approval:  It gives the flexibility to add minimum number of approval required for transaction to go through as well as define the mandatory approvers Block: Unconditionally reject any transaction that meets or exceeds the specified amount. Example: Per Transaction Amount ≥ $100: require 2 approvals, with Akansh as mandatory. Amount ≥ $200: block entirely. This means transactions between $100–$199 require 2 approvals (including Robert), while anything $200+ is auto-blocked.