Expense and Travel
Expense claims and travel bookings by category: per-diem and category caps, a receipt above a threshold, and an approver for anything out of policy.
- Key
- expense_and_travel
- Version
- expense_and_travel-v1
- Rules
- 7
- Domain
- EXPENSE
Rules, in the order the evaluator tries them
Highest priority first. The first rule whose conditions all hold decides; with none, the decision is a REVIEW.
Escalate an amount in a currency the template does not list
priority 1000exp-currency-unlisted · EXPENSE
When- context.currency not in ["USD"]
ThenESCALATE → ESCALATE · elevated · SLA 60 min
An amount with no currency, or in a currency without limits, cannot be compared with a limit, so a person decides it.
Ask for the receipt above the receipt threshold
priority 500exp-receipt-required · EXPENSE
When- transaction_type in ["expense", "travel_booking"]
- amount > 25
- context.receipt_attached ≠ true
ThenREQUEST_INFO → REVIEW · routine · SLA 1440 min
A claim above the receipt threshold needs its receipt before anyone can approve it.
Meals within the daily per diem
priority 100exp-meals-within-cap · EXPENSE
When- transaction_type in ["expense", "travel_booking"]
- context.expense_category = "meals"
- amount > 0
- amount ≤ 75
ThenAUTO_APPROVE → APPROVE
A meals line at or under the starter cap of 75 clears. Replace the cap with your policy's.
Lodging within the nightly cap
priority 100exp-lodging-within-cap · EXPENSE
When- transaction_type in ["expense", "travel_booking"]
- context.expense_category = "lodging"
- amount > 0
- amount ≤ 250
ThenAUTO_APPROVE → APPROVE
A lodging line at or under the starter cap of 250 clears. Replace the cap with your policy's.
Ground transport within the cap
priority 100exp-ground-transport-within-cap · EXPENSE
When- transaction_type in ["expense", "travel_booking"]
- context.expense_category = "ground_transport"
- amount > 0
- amount ≤ 100
ThenAUTO_APPROVE → APPROVE
A ground transport line at or under the starter cap of 100 clears. Replace the cap with your policy's.
Airfare within the cap
priority 100exp-airfare-within-cap · EXPENSE
When- transaction_type in ["expense", "travel_booking"]
- context.expense_category = "airfare"
- amount > 0
- amount ≤ 800
ThenAUTO_APPROVE → APPROVE
A airfare line at or under the starter cap of 800 clears. Replace the cap with your policy's.
Escalate every claim outside the expense policy
priority 0exp-out-of-policy · EXPENSE
WhenThenESCALATE → ESCALATE · elevated · SLA 1440 min
Over a category cap, in an unlisted category, or missing the amount or category: an approver decides.
Evaluate under it
Locally, with @decionis/mcp: the payload becomes the request's context, and its action the decision type. On the hosted protocol, once the bundle is stored for your organization, name vertical_pack, policy_version and require_exact_policy_version: true. @decionis/mcp 0.4.0 does not carry this pack: the hosted protocol decides a hosted gateway's requests under it.
decionis_evaluate arguments
{ "policy_pack": "expense_and_travel", "payload": { "action": "<decision type>" } }In a hosted evaluate-decision request
"vertical_pack": "expense_and_travel",
"policy_version": "expense_and_travel-v1",
"require_exact_policy_version": trueWorkflow keys that resolve to this pack: expense_and_travel.
What its rules read
amount, transaction_type are fields of the request itself, not of its context. A value put only in the context is discarded, and the evaluator holds the decision as an ESCALATE rather than decide without it. @decionis/mcp puts the whole payload in the context, so a payload that carries amount, transaction_type is held.
- amountrequest
- context.currency
- context.expense_category
- context.receipt_attached
- transaction_typerequest
Signals it maps
- auto_clear_ratiofinance_workflow
- out_of_policy_ratiofinance_workflow
- receipt_request_countfinance_workflow
