Vendor Master Change
New vendors and vendor bank-detail changes always go to an approver before they take effect.
- Key
- vendor_master_change
- Version
- vendor_master_change-v1
- Rules
- 3
- Domain
- VENDOR_MASTER
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 every vendor bank-detail change
priority 200vmc-bank-change · VENDOR_MASTER
When- transaction_type = "vendor_bank_change"
ThenESCALATE → ESCALATE · urgent · SLA 60 min
Changed bank details are how payments are diverted, so a person confirms every change with the vendor through a known contact. A payment soon after a change is held by the exposure ledger's cooling-off (cooling_off_seconds on its sequence limit), not by this rule.
Escalate every new vendor
priority 200vmc-vendor-create · VENDOR_MASTER
When- transaction_type = "vendor_create"
ThenESCALATE → ESCALATE · elevated · SLA 240 min
A new vendor can be paid, so a person confirms it before it is created.
Escalate every other vendor-master action
priority 0vmc-out-of-policy · VENDOR_MASTER
WhenThenESCALATE → ESCALATE · elevated · SLA 240 min
Any other change to vendor-master data, or an action with no type, is decided by a person.
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": "vendor_master_change", "payload": { "action": "<decision type>" } }In a hosted evaluate-decision request
"vertical_pack": "vendor_master_change",
"policy_version": "vendor_master_change-v1",
"require_exact_policy_version": trueWorkflow keys that resolve to this pack: vendor_master_change.
What its rules read
transaction_type is a field 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 transaction_type is held.
- transaction_typerequest
Signals it maps
- escalation_ratiofinance_workflow
- bank_change_countfinance_workflow
- vendor_create_countfinance_workflow
