Settlement Checkpoint Escalation Patterns

Settlement checkpoints translate policy into system gates. When a payment cannot pass a gate automatically, escalation patterns prevent two failure modes: paralysis (nothing moves) and silent bypass (everything moves without audit).

Common escalation patterns

1. Amount tier escalation — auto below threshold, human review above.
2. Reference ambiguity escalation — missing or corrupted memos route to support with commerce context.
3. Rail instability escalation — freeze auto-posting, manual verification for affected window.
4. Finance hold escalation — Confirmed allowed, treasury posting blocked pending reconciliation.
5. Policy exception escalation — controller approval with time-bounded override.

Evidence required at escalation

Escalation without payment_id, rail context, and current lifecycle state recreates drift. Require structured notes and resolution codes aligned to exception taxonomy.

After escalation resolves

Apply transitions through normal provider flows when possible so webhooks and audit logs align. If manual correction is unavoidable, backfill provider plane reads and document matcher re-runs.