Investigate unmatched allocations and settlement instructions without granting agents trading or settlement authority.
Explore in the architecture studioIllustrative reference architecture. Validate requirements for your organization.
Illustrative architecture: A securities operations desk must resolve settlement breaks across broker allocations, custodian instructions, and internal books before market-specific cutoffs. The illustrative system prepares operational evidence for qualified staff; it does not provide investment advice or choose trades.
A trade can match economically while failing on account, instrument, or settlement-location identifiers. Messages arrive out of order and corrections supersede prior instructions. A plausible narrative that ignores a late amendment can cause an operator to approve the wrong repair.
Specialists partition reconciliation by instrument identity, allocation economics, standing instructions, and exception history. Deterministic comparison services perform calculations; agents explain mismatches and retrieve context while a workflow tracks source versions and cutoffs.
The intended result is a reviewable operational decision with source evidence and explicit ownership. Evaluate whether the desk spends less time assembling facts while maintaining correct repair decisions. Distinguish message acceptance, matching, and final settlement in dashboards so an intermediate success cannot hide unresolved exposure.
Compare quantities, price, net amount, and allocation identifiers using exact decimal calculations.
Cannot allocate, execute, or amend a trade.
Map external identifiers to the approved instrument master and flag ambiguous mappings.
Cannot create a new security master record.
Retrieve authenticated standing settlement instructions effective for the counterparty and date.
Cannot accept bank-detail changes from free text.
Build a ranked operations queue and proposed repair packet from confirmed evidence.
Priority rules are desk-approved; release remains a named operator's decision.
Authoritative execution and allocation versions with immutable trade identifiers.
Supplies acknowledgements and settlement status, including rejected and pending messages.
Separate trusted settlement data from analyst proposals and retain reviewer decisions.
flowchart LR
N0["Trade settlement break resolution"]
N1["Allocation reconciler"]
N2["Instrument resolver"]
N3["Instruction investigator"]
N4["Break briefing agent"]
N5["Evidence ledger"]
N6["Human decision"]
N7["Authorized adapter"]
N0 --> N1
N0 --> N2
N2 --> N3
N1 --> N4
N3 --> N4
N4 --> N5
N5 --> N6
N6 --> N7sequenceDiagram
participant O as "Case orchestrator"
participant S as "Order and trade book"
participant H as "Accountable reviewer"
O->>S: Read allocation revision
S-->>O: Revision with unmatched fields
O->>H: Request approval of repair delta
H-->>O: Approve recorded revision
O->>S: Compare revision before submit
S-->>O: New allocation amendment exists
O->>H: Withdraw stale repair for reviewDeduplicate the mismatch event and attach trading date, settlement date, account scope, and market cutoff.
Match instrument and counterparty identifiers through governed master data; unresolved mappings stop downstream repair generation.
Compare allocation quantities and amounts with deterministic tolerances configured for the instrument and market.
Read the trusted instruction version and message history; treat email attachments as evidence requiring authentication.
Present proposed field-level changes, source versions, unresolved risks, and remaining cutoff time to the authorized operator.
The gateway rechecks trade and instruction versions, sends an approved repair with a stable key, then tracks acknowledgement separately from settlement completion.
Detect: Optimistic version checks find a different allocation revision before submission.
Recover: Cancel the staged repair and request approval of the new delta rather than merging silently.
Detect: Gateway freshness and elapsed deadline checks classify the status as unknown.
Recover: Escalate to the desk's established contingency process and reconcile before any duplicate instruction.
Measurement definitions, not promised improvements.
Time from unmatched event to complete repair packet, reported by market and instrument class.
Reviewed alerts with no actionable discrepancy divided by all reviewed alerts.
Repair submissions blocked by changed source versions divided by attempted approved submissions.
Count and notional of unresolved breaks at desk-defined cutoff checkpoints, with currency conversion provenance.
| Decision | Benefit | Cost |
|---|---|---|
| Instrument-specific rules | Preserve exact reconciliation semantics. | Require maintained rules for different products and markets. |
| Event-time processing | Handles out-of-order amendments correctly. | Adds watermarks and explicit pending-state complexity. |
| Strict instruction provenance | Reduces risk from forged change requests. | Some urgent repairs require slower manual authentication. |
Operations confirms amendment ordering, cutoff handling, and arithmetic on representative resolved breaks.
Analysts compare proposed packets with existing practice and validate information-barrier enforcement.
One instrument class enables submission after duplicate, stale-approval, and gateway-outage exercises pass.