Two counterparties. One canonical trade identity. When terms match, both sides derive the same Sigrid. When they don’t, Sigrid shows the exact field-level break.
ONE IDENTIFIER.
TWO PARTIES. ONE TRUTH.
Built for buy-side and dealer operations teams processing high-volume OTC attestations.
| Status | Match | Reason | CP | Aging |
|---|---|---|---|---|
| break | MCH-8821-FZQ2 | Rate / spread | UBS | 23m |
| break | MCH-8822-LMD9 | Dates | J.P. Morgan | 47m |
| awaiting | MCH-8823-VNT7 | — | BlackRock | 1h 24m |
| break | MCH-8824-RK1P | Notional | UBS | 2h 15m |
Most reconciliation tools show that two records disagree. Sigrid shows why. By deriving identity from canonical trade terms, every match, break, and awaiting item becomes explainable at field level.
Internal reference numbers don't translate between counterparties, so every break conversation restarts with identity reconciliation.
Analysts stitch screenshots and emails to figure out which field actually disagrees, instead of working the break.
Items sit in an awaiting state with no shared owner or visibility until they cross a deadline and become incidents.
Amendments and novations fragment the audit trail — there's no shared line from open to current state.
Each party attests the economic and lifecycle terms of the trade in canonical form.
The same terms produce the same deterministic Sigrid.
Different terms produce different Sigrids and a field-level diff for triage.
Same terms → same Sigrid. Different terms → different Sigrid + field-level diff.
Shared prioritised view of breaks and awaiting items, filterable by reason, counterparty, and aging bucket.
Open any break to see both parties' canonical terms, the exact field-level diff, notes, and resolution actions.
Every amendment and novation is a node on a shared timeline. Auditors and ops see the same story.
Sigrid is a deterministic identity and exception layer for bilateral OTC matching.
Sigrid is not an OMS, trade booking system, chat tool, allocation workflow, or regulatory reporting product.
ISDA's Common Domain Model is a schema. Trade matching is an operation on data. The first does not give you the second.
Walk through what actually happens between 09:14 and 09:45 when an IRS doesn't affirm. The forensic part is finding the field that differs.
A deterministic identifier gives counterparties a shared way to know whether they are talking about the same OTC trade terms.
We’re speaking with buy-side and dealer operations teams processing high-volume OTC workflows.