← Back to catalogue
Published

Clearing / Settlement

vr.wm-eco-010 · wm-eco-010-clearing-settlement

Clearing of payment and trade obligations and their final settlement between accounts.

World Models Society, people and institutions SOC.ECO.STL

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 5 findings · 10 questions

Obligations What must be settled and between whom.

Clearing

Matching, netting and novation of obligations.

Obligation set

The obligations submitted for clearing and their netting result.

  1. Which trades or payments are included, and between which participants?
  2. Were obligations netted, and what is each net position?

Counterparty role

Whether a central counterparty stepped in.

  1. Did a central counterparty become the counterparty to each side?
  2. Which margin or collateral covers the exposure?
Settlement How obligations are discharged.

Movements and finality

The account movements and the moment they become final.

Settlement movement

Debits and credits of money or assets on settlement accounts.

  1. Which accounts were debited and credited, by which quantities and in which asset?
  2. Was settlement delivery versus payment or free of payment?

Finality

When the transfer became irrevocable under the system's rules.

  1. At what time did settlement become final and irrevocable?
  2. Which system rules define finality?
Exceptions What happens when settlement fails.

Fails and defaults

Failed settlements, buy-ins and participant defaults.

Settlement fail

A movement that did not settle on the intended date.

  1. Which movement failed, and for what reason?
  2. Which penalty, buy-in or default procedure applies?

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
aggregate
Navigation path
NAV.SOC.ECO.STL
Domain
SOC.ECO.STL
Industry
Cross-industry
Tags
clearingsettlementsoc.eco.stl
Also called
R2

What it is Filled

Clearing and settlement is the process by which obligations arising from payments and trades are calculated, confirmed and finally discharged by transferring money or assets between accounts, recorded as append-only movements of quantities. It covers clearing houses, central counterparties, securities settlement and payment settlement systems, but not the trade or payment instruction itself.

In scope

  • Case identity, participants, applicable system and jurisdiction profile, obligation membership and clearing evidence
  • Gross or net allocations, optional counterparty substitution, resource dependencies and linked settlement legs
  • Partial outcomes, separate entry/revocation/finality assertions, reconciliation and authorized exception records

Out of scope

  • Trade execution, payment origination, account and ledger masters, general accounting and asset issuance
  • Operating a settlement rail, transferring funds, releasing instructions, declaring default or enforcing a penalty
  • Margin valuation engines, liquidity optimization, full infrastructure governance and recovery planning, physical delivery logistics
  • Universal legal opinions, guaranteed settlement, investment advice and operational compliance certification

Why it exists Filled

Clearing of payment and trade obligations and their final settlement between accounts.

Distinguishing features Filled

  • Movements are append-only: errors are reversed by new entries, never by editing past ones.
  • Finality is a legal moment defined by system rules, after which a transfer cannot be unwound.
  • It discharges obligations created elsewhere, by trades or payment orders.
  • Distinct from a general ledger, which records an organization's own accounting view of the same movements.

What robots and AI may and may not do Filled

Must not

  • Release, cancel or alter settlement instructions without authorization.
  • Edit or delete a booked movement instead of posting a reversal.
  • Disclose one participant's positions to another.
  • Give investment or trading advice based on settlement data.

Only with a human decision

  • Releasing payment or settlement instructions.
  • Declaring a participant default or triggering a buy-in.
  • Changing system rules, cut-off times or finality conditions.

May

  • Reconcile settlement reports against expected obligations.
  • Report net positions, fails and finality times to authorized participants.
  • Flag mismatches and pending fails before cut-off times.
  • Prepare settlement instructions for human release.

Moral aspects Filled

  • Settlement failures can spread losses through the financial system and to ordinary account holders.
  • Positions and flows are confidential and can be misused for market advantage.
  • Access rules for settlement systems shape who can compete in markets.

Who is affected

  • Participants and their customers
  • Central banks and supervisors
  • Investors and payment users

Owners Filled

Steward

The operator of the clearing or settlement system, under oversight of the central bank or market supervisor.

Roles

Case steward
Maintains case scope and master-reference integrity.
Settlement operations reviewer
Reviews reported execution and readiness without obtaining implicit transfer authority.
Legal and rule-profile reviewer
Qualifies jurisdiction, finality interpretation and exceptional remedies.
Reconciliation reviewer
Investigates differences and proposes evidence-backed corrections.
Records and access custodian
Maintains scoped disclosure, retention and disposal decisions.
Independent auditor
Reviews evidence under explicit scope; cannot silently mutate operational records.

Master systems

  • Central counterparty clearing system
  • Central securities depository
  • Real-time gross settlement system

Links to other meta-models Filled

references

  • WM-XCT-014 - Candidate binding to Ledger / Account for authoritative accounts and postings. Required conceptually for recorded account movements; this specific model/version binding remains optional and unpinned.
  • WM-ECO-009 - Candidate originating payment reference when applicable; not all cases originate from this model.
  • WM-ECO-016 - Candidate accounting projection reference, not authoritative settlement evidence by itself.
  • wm-eco-009-payment - Payments create the obligations that are cleared and settled.

aligned

  • ISO 20022 - Conceptual alignment with selected message families. Pin an actual message and usage profile before implementation.
  • W3C PROV-O - Candidate evidence lineage mapping; no ontology conformance asserted.

neighbor

  • WM-XCT-014 Ledger / Account and legacy R2 - R2 remains the ledger model. This aggregate links account and posting masters but does not inherit append-only bookkeeping as the definition of clearing or legal finality. Local record correction and an economic counter-transfer are distinct.
  • WM-ECO-009 Payment - Reference originating payments or transfer orders where applicable. A settlement case can also arise from trades; payment creation and customer payment status remain external.
  • WM-ECO-016 Financial Transaction / Journal Entry - Participant accounting entries are separate projections. Balanced journals alone do not establish discharge of an obligation under system rules.
  • Clearing infrastructure, counterparty, depository and settlement operator - Reference institutional roles and versioned rulebooks. The root is a case aggregate, not the entire institution, its risk model or all customer positions.
  • wm-eco-016-financial-transaction-journal-entry - Participants record the same movements in their own books.

requires

  • world-r2-ledger-and-account - Settlement movements are booked on append-only ledger accounts.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Participants are identified by LEI and system participant codes; securities by ISIN.
  • Settlement instructions and movements carry transaction references unique within the system.

Direct properties not applicable Not applicable

Not applicable

Clearing and settlement are institutional processes; quantities are amounts and positions, not physical measurements.

Recognition optional Filled

  • A settlement record names participants, an asset, a quantity, an intended date and a status.
  • Often confused with the trade, the payment order or the bank's internal ledger posting.

Capabilities and actions required Filled

  • Obligations can be matched, netted and novated to a central counterparty.
  • Movements can settle, fail, be partially settled or be reversed by a new entry.
  • Finality is reached at a defined moment under system rules.

Hazards and failure modes required Filled

  • Settlement fails and cascading defaults.
  • Operational outages around cut-off times.
  • Fraudulent or erroneous instructions released into the system.

Standards and interfaces required Filled

  • ISO 20022 messages for payments and securities settlement.
  • ISO 15022 messages still used in securities settlement.
  • ISO 17442 Legal Entity Identifier and ISO 6166 ISIN for parties and securities.

Context of use required Filled

  • Operated by financial market infrastructures under central bank and supervisory oversight.
  • Settlement finality is protected by law, for example the EU Settlement Finality Directive.

Sources Filled

  1. Principles for financial market infrastructures - CPSS and IOSCO
  2. What is T2S? - European Central Bank
  3. Fedwire Funds Services - Board of Governors of the Federal Reserve System
  4. Directive 98/26/EC on settlement finality in payment and securities settlement systems - European Parliament and Council of the European Union
  5. ISO 20022 Message Definitions - ISO 20022 Registration Authority
  6. PROV-O: The PROV Ontology - World Wide Web Consortium
  7. RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
  8. Principles for Financial Market Infrastructures (CPMI-IOSCO)
  9. Directive 98/26/EC on settlement finality in payment and securities settlement systems (European Union)
  10. ISO 20022 Financial services - Universal financial industry message scheme (ISO)

Open questions

  • Verify exact current source editions, consolidated laws, national transposition and system operating rules for each adopting jurisdiction and infrastructure.
  • Implement pinned instance and message profiles with fixtures for gross and net cases, duplicate reports, partial legs, missing finality evidence, insolvency notices, correction versus compensation, retention and cross-participant disclosure.
  • Restore independent external review before any canonical or publishable-draft promotion.
  • Current consolidated law, designated-system status, cross-border conflict rules and operating circulars are not fully verified.
  • Margin engines, collateral valuation, liquidity optimization, full default waterfalls and recovery execution are delegated and not specified.
  • Nested instance schemas, live master bindings, exact message mappings, business calendars and executable acceptance fixtures remain incomplete.
  • Tokenized settlement, retail scheme chargebacks, corporate actions, tax, fees and physical delivery require separate profiles.
  • Independent external provider review and direct HTTP measurements are absent.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-eco-010-clearing-settlement/spec.yaml, ver-cy/world-models/card-supplements/wm-eco-010-clearing-settlement.json