Loading…
Open-Policy Exchange
~8 min to deploy
Workday Payroll Circuit Breaker
Catches an out-of-band payroll run — a bank-detail change, an off-cycle payment, a headcount jump — before the money leaves.
For: Payroll and HR operations teams on Workday
SOC 2 CC1.4ISO 27001 A.6.1SOX payroll controls
What it enforces
Off-cycle run escalation
Escalates any payroll run outside the published calendar.
Bank-detail change hold
Blocks payment to an employee whose bank details changed inside the cooling-off window.
Headcount delta restraint
Restrains a run whose net pay moves more than the allowed delta versus last cycle.
workday-payroll-circuit-breaker.yaml
# Workday Payroll Circuit Breaker
# Fork: set the cooling-off window and the acceptable cycle delta.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: workday-payroll-circuit-breaker
surface: workday
workflow_key: payroll_run_release
standards: [SOC2-CC1.4, ISO27001-A.6.1]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: off_cycle_run_escalation
when: "action == 'payroll.run'"
decision: |
ESCALATE IF run.date not in payroll_calendar
ALLOW OTHERWISE
reason_code: off_cycle_payroll_run
- name: bank_detail_change_hold
when: "action == 'payroll.pay_worker'"
decision: |
BLOCK IF worker.bank_details_changed_hours_ago < 72
ALLOW OTHERWISE
reason_code: bank_change_inside_cooling_off
- name: headcount_delta_restraint
when: "action == 'payroll.run'"
decision: |
RESTRAIN IF abs(run.net_pay_usd - previous_run.net_pay_usd) / previous_run.net_pay_usd > 0.15
ALLOW OTHERWISE
reason_code: payroll_delta_over_threshold
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.