DecionisDevelopers
Policy pack

Salesforce Revenue Execution

Dual-gate governance for the Salesforce → SAP front-to-back pipeline — state admission (SAP master-data sync and field-shape safety for Commerce Cloud orders and CPQ quotes) and execution authority (margin floor, manual-discount floor, credit limit, payment terms, promo hygiene) before a sales order is committed.

Key
salesforce
Version
salesforce-revops-v1
Rules
13
Domain
SALESFORCE_EXECUTION_AUTHORITY
Every packHow a pack decides

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. Required SAP-mapping fields present

    priority 200

    state-required-fields · *

    When
    • gate = "state_admission"
    • missing_required_fields > 0
    Then

    AUTO_REJECT → REJECT · urgent

    Salesforce payload is missing fields required to build a valid SAP sales order.

  2. Order within the SAP credit limit

    priority 200

    exec-credit-limit · *

    When
    • gate = "execution_authority"
    • over_credit_limit = true
    Then

    ESCALATE → ESCALATE · urgent · SLA 30 min

    Order total exceeds the customer's SAP-defined credit limit.

  3. Salesforce account is synced to an SAP customer master

    priority 195

    state-customer-master-synced · *

    When
    • gate = "state_admission"
    • customer_master_synced = false
    Then

    AUTO_REJECT → REJECT · urgent

    Salesforce Account must map to a validated SAP customer master (KNA1/KUNNR) before order admission.

  4. Net margin floor protected

    priority 195

    exec-margin-floor · *

    When
    • gate = "execution_authority"
    • margin_below_floor = true
    Then

    AUTO_REJECT → REJECT · urgent

    Order net margin falls below the policy floor against the SAP cost basis (e.g., a flash-sale promo breaching margin).

  5. Material numbers fit SAP field limits

    priority 190

    state-material-number-valid · *

    When
    • gate = "state_admission"
    • material_number_overflow = true
    Then

    AUTO_REJECT → REJECT · urgent

    A material number exceeds the SAP 18-character limit (VBAP overflow).

  6. Sales organization and distribution channel present

    priority 185

    state-sales-org-valid · *

    When
    • gate = "state_admission"
    • sales_org_valid = false
    Then

    AUTO_REJECT → REJECT · urgent

    Sales organization (VKORG) and distribution channel (VTWEG) are required for the SAP order header.

  7. Manual discount within compliance floor

    priority 185

    exec-discount-floor · *

    When
    • gate = "execution_authority"
    • manual_discount_violation = true
    Then

    REQUIRE_REVIEW → REVIEW · elevated · SLA 120 min

    A manual line discount exceeds the threshold for a non-Strategic account and needs manager override.

  8. Order line amounts and quantities are valid

    priority 180

    state-amounts-valid · *

    When
    • gate = "state_admission"
    • amounts_invalid = true
    Then

    AUTO_REJECT → REJECT · urgent

    Order line net price and quantity must be positive numeric values.

  9. Behavioral risk within tolerance (Data Cloud)

    priority 180

    exec-data-cloud-risk · *

    When
    • gate = "execution_authority"
    • risk_elevated = true
    Then

    REQUIRE_REVIEW → REVIEW · elevated · SLA 60 min

    Salesforce Data Cloud behavioral risk for this customer is elevated; hold B2B purchasing eligibility for review.

  10. B2B payment terms permitted for region

    priority 175

    exec-payment-terms-allowed · *

    When
    • gate = "execution_authority"
    • payment_terms_allowed = false
    Then

    REQUIRE_REVIEW → REVIEW · elevated · SLA 120 min

    Requested B2B payment terms are not permitted for this region without review.

  11. Promotion / coupon stacking review

    priority 170

    exec-promo-stacking · *

    When
    • gate = "execution_authority"
    • promo_stacking = true
    Then

    REQUIRE_REVIEW → REVIEW · elevated · SLA 60 min

    Multiple concurrent discount sources are stacked on one order and need review.

  12. Admit a clean Salesforce order intent

    priority 1

    state-admit-default · *

    When
    • gate = "state_admission"
    Then

    AUTO_APPROVE → APPROVE

    Salesforce intent maps cleanly to SAP structures and is eligible for execution review.

  13. Authorize a compliant Salesforce order

    priority 1

    exec-authorize-default · *

    When
    • gate = "execution_authority"
    Then

    AUTO_APPROVE → APPROVE

    Order satisfies revenue policy and may be committed to SAP.

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_evaluate arguments

{ "policy_pack": "salesforce", "payload": { "action": "<decision type>" } }

In a hosted evaluate-decision request

"vertical_pack": "salesforce",
"policy_version": "salesforce-revops-v1",
"require_exact_policy_version": true

What its rules read

Every fact below comes from the request's context.

  • amounts_invalid
  • customer_master_synced
  • gate
  • manual_discount_violation
  • margin_below_floor
  • material_number_overflow
  • missing_required_fields
  • over_credit_limit
  • payment_terms_allowed
  • promo_stacking
  • risk_elevated
  • sales_org_valid

Signals it maps

  • salesforce_order_admission_ratesalesforce_commerce_cpq
  • salesforce_revenue_policy_breach_ratesalesforce_commerce_cpq