Clearing & Netting Orchestrator
Builds clearing files and net obligations across rails, participants, currencies, and legal entities.
Collects accepted, reversed, refunded, charged back, returned, and adjusted transactions; applies scheme and rail cutoffs; nets by settlement key; and reconciles control totals before release. It coordinates exceptions and refuses a file with unexplained imbalance or duplicate economic effect.
Authority
Execute within policy
Team role
Coordinates the work
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Clearing, Settlement & Liquidity
Desk workflow
Validate accepted transactions, clear and net, forecast and fund obligations, release settlement under controls, then reconcile bank, rail, processor, merchant, and ledger positions.
Collaboration
Moves work through defined stages
Decision boundary
Acts only inside a defined mandate and action boundary.
Systems and capabilities involved
Authorized transaction stream
Rail clearing adapters
Netting and control-total engine
Exception repair router
Liquidity monitor
Handoffs
What this role gives and receives
Capabilities offered
Controlled clearing and netting
Creates balanced clearing obligations and files from final transaction states.
- Receives:
- Transaction events, reversals, returns, disputes, adjustments, participant keys, and settlement window
- Returns:
- Balanced clearing positions, files, control totals, funding handoff, and exception list
Delegates
Resolve invalid, duplicate, missing, rejected, or ambiguous clearing records. Trigger: A record fails validation or control totals do not reconcile. Returns: Repaired, rejected, or held record with rationale and state.
Delegates
Confirm forecast funding and intraday capacity before release. Trigger: Balanced obligations are available for a settlement window. Returns: Funding readiness, projected buffers, and hold conditions.
Receives from
Receives from
Context
What the role needs to do the work
- Current work
- Settlement window, transaction states, cutoffs, netting keys, control totals, files, and exceptions.
- Prior interactions
- Prior files, rejects, re-presentments, manual adjustments, and settlement outcomes.
- Policies and reference
- Rail clearing rules, settlement calendars, netting, message, and reconciliation policy.
- Working method
- Not specified for this role.
Illustrative workflow
How the work moves
Starting point
The daily card-clearing window contains a duplicated processor batch and late reversals.
- 01
Resolve event identity and final transaction state across authorization, capture, reversal, and refund streams.
- 02
Delegate duplicate and late-record repair, then rebuild net positions and control totals.
- 03
Confirm funding readiness and release one balanced file under dual control.
Result
Balanced clearing file with duplicate economic effect removed and late reversals documented.
Checks and boundaries
What must be tested or reviewed
- 01Control-total tests cover authorization, capture, reversal, refund, return, adjustment, dispute, fee, FX, and duplicate-event combinations.
- 02Chaos cases inject late files, participant rejects, cutoff changes, duplicated batches, and partial acknowledgements.
- 03No clearing release may occur with unexplained imbalance, uncertain transaction state, or failed funding control.
Human authority
- Authorized operations and treasury control owners approve material adjustments, out-of-balance release, cutoff overrides, and manual settlement files.
Keep exploring