Policy pack

Journal Entry Materiality

Journal entries above a materiality amount go to an approver; at or below it they post.

Key
journal_entry_materiality
Version
journal_entry_materiality-v1
Rules
4
Domain
JOURNAL_ENTRY

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.

  1. Escalate an amount in a currency the template does not list

    priority 1000

    je-currency-unlisted · JOURNAL_ENTRY

    When
    • context.currency not in ["USD"]
    Then

    ESCALATE → 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.

  2. Escalate a journal entry above materiality

    priority 200

    je-above-materiality · JOURNAL_ENTRY

    When
    • transaction_type = "journal_entry"
    • amount > 10000
    Then

    ESCALATE → ESCALATE · elevated · SLA 240 min

    An entry above the starter materiality of 10000 needs an approver; through Presence, its preparer cannot approve it. Replace the amount with your materiality.

  3. A journal entry within materiality

    priority 100

    je-within-materiality · JOURNAL_ENTRY

    When
    • transaction_type = "journal_entry"
    • amount > 0
    • amount ≤ 10000
    Then

    AUTO_APPROVE → APPROVE

    An entry at or under the starter materiality of 10000 posts.

  4. Escalate every other entry

    priority 0

    je-out-of-policy · JOURNAL_ENTRY

    When
      Then

      ESCALATE → ESCALATE · elevated · SLA 240 min

      An entry with no amount or a non-positive amount, or an unlisted action, 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": "journal_entry_materiality", "payload": { "action": "<decision type>" } }

    In a hosted evaluate-decision request

    "vertical_pack": "journal_entry_materiality",
    "policy_version": "journal_entry_materiality-v1",
    "require_exact_policy_version": true

    Workflow keys that resolve to this pack: journal_entry_materiality.

    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
    • transaction_typerequest

    Signals it maps

    • auto_clear_ratiofinance_workflow
    • escalation_ratiofinance_workflow
    • above_materiality_countfinance_workflow