Playbook
Reconciliation close procedure
Period-close workflow across commerce, provider, and finance planes—with freeze options and evidence requirements.
01
Objective
Close an accounting period with three-plane alignment evidence—commerce, provider lifecycle, and finance postings—or explicitly owned exceptions.
02
Prerequisites
- Matchers frozen for close window (no tolerance changes mid-close).
- Exception queue aged items reviewed by owner.
- Finance sign-off roles assigned.
03
Operational signals
- Unmatched value exceeds materiality threshold.
- Exceptions reopened after prior close.
- Provider plane events missing for posted commerce orders.
04
Decision points
- Whether to invoke reconciliation freeze for new auto-posting.
- Which exception classes block close versus carry forward.
- Adjustments requiring dual control.
05
Escalation paths
- Finance close owner → engineering for provider plane gaps.
- Support → operations for reference mismatch spikes.
- Executive → policy exception for material unresolved items.
06
Failure modes
- Force-balancing by editing commerce records without provider evidence.
- Closing with generic exception codes only.
- Ignoring timing-skew class during async settlement week.
07
Recovery patterns
- Apply reconciliation freeze; stop silent auto-resolve.
- Re-run matchers with frozen tolerances.
- Document carry-forward exceptions with payment_id evidence.
- Schedule drift investigation if systematic class emerges.
- Retries are normal. Webhook delivery is at-least-once. Design consumers to tolerate duplicates and out-of-order arrivals where possible.
- Asynchronous by design. Payers, chains, and your servers operate on different clocks. UI and finance should not assume synchronous finality.
- Eventual consistency. API reads, webhooks, and portal views may briefly diverge during transitions. Reconciliation jobs exist to converge truth.
Walkthroughs: /operations