← Back to catalogue
Published

Financial Account

vr.wm-eco-015 · wm-eco-015-financial-account

Give an agent the context needed to identify a financial account, know who holds and services it, what it is denominated in, what state it is in, what rules and protections bind it, and which contained or neighbouring models own everything else.

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

Bundle → Layer → Finding → Questions Filled

6 bundles · 14 layers · 26 findings · 102 questions

Account Identity and Classification How an account is denoted, aliased and typed, across the identifier schemes and classification schemes that different authorities impose on the same account.

Identifier Schemes and Naming

The identifier values that denote the account, their governing schemes, and the human-facing labels and proxies layered over them.

Account identifier schemes and precedence

An account carries one authoritative servicer-assigned identifier plus zero or more scheme-governed public identifiers; each value must record its scheme, scheme owner and validity window.

  1. Which identifier is the authoritative master-system identifier assigned by the account servicer, and in which namespace is it unique? identity
  2. Which additional identifier schemes denote this account, and who governs each scheme? interoperability
  3. Is each identifier immutable for the life of the account, or may it be reissued or reassigned? constraint
  4. From which instant is each identifier valid, and when did it cease to denote this account? temporal

Aliases, proxies and display labels

Non-authoritative labels attached to the account: customer nickname, servicer description, masked identifiers and proxy or alias values resolved to the account by an external directory.

  1. What is each alias or display label for, and is it customer-supplied or servicer-supplied? definition
  2. Which external directory resolves a proxy or alias to this account, and what is the reference to that directory entry? relationship
  3. Which identifier values must be masked or truncated when displayed or shared? privacy

Classification and Typing

Product, regulatory and tax classifications applied to the same account by different authorities, each with its own scheme, version and effective period.

Product and regulatory classification

Classification of the account by product family and subtype and by regulatory category such as payment account, payment account with basic features, deposit account, loan or credit account or internal ledger account.

  1. Which product family and subtype does the servicer assign to this account, and under which code set? classification
  2. Which regulatory categories apply to the account in each jurisdiction where it is offered? authority
  3. Is the account held for personal or business purposes, and does that designation change the applicable rules? decision
  4. Over which effective period does each classification hold, and what triggered a reclassification? temporal

Tax reporting status and self-certification

The account's status under automatic exchange of information regimes: financial account category, reportable or excluded status, and the self-certification that supports it.

  1. Which financial account category applies for automatic exchange of information purposes? classification
  2. Is the account an excluded account, and on what documented basis? exception
  3. What self-certification or documentary evidence establishes the account holder's tax residence? evidence
  4. Is the account pre-existing or new relative to the applicable regime start date, and which due-diligence path follows? process
Parties, Ownership and Operating Authority Who holds the account, who really controls it, who services it, and who is permitted to operate it.

Holders and Ownership Structure

The set of parties that own the account, how ownership is shared, and who ultimately controls or benefits from it.

Account holders and ownership structure

The holder set with primary and secondary roles, the ownership form (single, joint, trust, entity, government), declared shares, and the ownership category used by protection schemes.

  1. Which parties hold this account, and which holder is primary? ownership
  2. What ownership form does the account take, and which protection-scheme ownership category follows from it? classification
  3. How is entitlement divided between holders when shares are not equal? composition
  4. What event added or removed a holder, and when did the change take effect? event

Beneficial owners and controlling persons

Natural persons who ultimately own or control an entity holder, recorded as references with the threshold, prong and regime that produced the determination.

  1. Which natural persons are recorded as beneficial owners or controlling persons of an entity holder? ownership
  2. Which ownership threshold and regime produced each determination? authority
  3. Through which intermediate entities does control reach the account, and how is that chain referenced? relationship
  4. When was the beneficial ownership record last confirmed, and what triggers re-confirmation? temporal

Servicing and Operating Authority

The institution that maintains the account and the authority granted to parties to operate it.

Account servicer and provider

The institution that maintains the account and any branch, agent or sub-servicer arrangement, identified by governed institution identifiers.

  1. Which institution services this account, and by which governed identifier is it denoted? identity
  2. At which branch, booking location or jurisdiction is the account maintained? spatial
  3. Is any part of servicing delegated to an agent, sub-servicer or platform, and under what reference? relationship

Mandates and operating authority

Grants of authority to operate the account: signatories, powers of attorney, guardianship, delegated limits and joint-signature requirements.

  1. Which parties may instruct on this account, and with what scope of authority? authority
  2. Does an instruction require more than one authorised signature, and under what combination rule? constraint
  3. Which instrument grants the authority, and does it originate from the holder, a court or a statute? provenance
  4. When does the mandate expire, and what event revokes it? lifecycle
Denomination, Terms and Protection What the account is denominated in, the terms and limits that bind it, and the protection scheme designation that applies to its balances.

Denomination and Instrument Scope

The monetary unit or instrument in which the account is expressed and the set of instruments it may hold, carried strictly as references.

Denomination and permitted monetary instruments

The account's denomination reference and any permitted additional instruments, including electronic money products and central bank digital currencies where the regime recognises them.

  1. In which monetary unit or instrument is this account denominated, and how is that unit referenced? definition
  2. May the account hold more than one denomination simultaneously, and how are sub-balances distinguished? composition
  3. Which instrument classes may be held, such as deposit claims, electronic money products or central bank digital currency? constraint
  4. Under what conditions may the denomination change, and what record captures the change? exception

Contractual Terms, Pricing and Limits

The priced terms and the operating constraints that the servicer applies to the account.

Pricing, fees and interest terms

Fee items, charging basis and interest terms bound to the account, together with the pre-contract fee disclosure and the periodic statement of fees required in some jurisdictions.

  1. Which fee items apply to this account and on what charging basis? measurement
  2. What interest rates apply to credit and debit balances, and how are they determined? requirement
  3. Which pre-contract disclosure was provided, and when was it supplied to the holder? evidence
  4. Over which period does each periodic fee statement report, and how often must it be issued? temporal

Limits, facilities and operating constraints

Quantitative and behavioural constraints on the account: credit or overdraft limits, transaction and balance limits, notice periods and withdrawal restrictions or penalties.

  1. What credit or overdraft facility is attached, and what is its limit and expiry? constraint
  2. Which transaction, frequency or balance limits constrain use of the account? requirement
  3. Do the account terms prevent withdrawal or impose a penalty or disincentive on withdrawal? constraint
  4. Which minimum service set must the account provide if it is a regulated basic-features account? requirement

Protection and Guarantee Designation

The depositor protection or guarantee scheme designation attached to the account and the evidence that the holder was informed of it.

Deposit protection and guarantee designation

Which protection scheme covers the account, which eligibility and ownership category applies, and what information the holder acknowledged; coverage computation stays with the scheme.

  1. Which deposit guarantee or insurance scheme covers this account, and in which jurisdiction? authority
  2. Is the account an eligible or excluded deposit under the scheme, and on what basis? classification
  3. Which ownership or aggregation category does the account fall into for coverage purposes? classification
  4. Is any balance flagged as temporarily protected above the standard limit, and for how long? exception
State, Lifecycle and Time The account's status model, restrictions, opening, closure, switching and dormancy determination, with event time separated from observation time throughout.

Status and Restrictions

The current operating state of the account and any restriction, freeze or hold that narrows what may be done with it.

Account status and state transitions

The account's current status, the permitted transitions between statuses, and the timestamps that distinguish when a change occurred from when it was observed.

  1. What is the account's current status, and under which status code set is it expressed? state
  2. Which status transitions are permitted, and which are terminal? lifecycle
  3. When did the status change take effect, and when was the change observed or ingested by this model? temporal
  4. Which capabilities are suspended or enabled by the current status? decision

Restrictions, freezes and holds

Designation that the account is blocked, frozen or restricted, with the scope, the authority behind it and a reference to the originating order, which this model does not own.

  1. What scope of activity is restricted: all activity, debits only, or specified counterparties or amounts? constraint
  2. Which authority or contractual ground supports the restriction? authority
  3. How long does the restriction last, and what condition lifts it? temporal
  4. May the restriction and its reason be disclosed to the account holder? privacy

Opening, Closure and Switching

The bounding events of the account relationship and the portability of the arrangement to another provider.

Opening and onboarding record

The account opening decision, its date, the framework contract concluded and the grounds relied on where opening was refused or conditional.

  1. On which date was the account opened, and from which instant was it operable? event
  2. Which framework contract or agreement governs the account, and in which version? provenance
  3. If an application was refused or conditionally accepted, on what permitted ground? exception
  4. Through which channel and instruction was the account opened? process

Closure and termination record

The termination of the account relationship: who initiated it, on what ground, what notice was given and how the residual balance was directed.

  1. Who initiated closure, and on what contractual or legal ground? decision
  2. What notice period applied, and when was notice given to the holder? temporal
  3. Where was any residual balance directed on closure? process
  4. Is closure reversible, and what identifier remains resolvable after closure? lifecycle

Switching and portability

Transfer of the account arrangement to another provider: authorisation, the items to be moved, redirection of incoming payments and the effect on identifiers.

  1. What authorisation did the holder give to the receiving provider to run the switch? authority
  2. Which recurring arrangements and balances are in scope of the switch? composition
  3. For how long are incoming payments redirected, and by which mechanism? process
  4. Does the account identifier survive the switch, and if not how are old references resolved? identity

Dormancy and Balance Disposition

Determination that an account is dormant or abandoned and the reference to any statutory transfer of its balance.

Dormancy determination and escheatment linkage

The inactivity inputs, jurisdictional test and resulting dormancy designation, plus a reference to any transfer of the balance to a reclaim fund or state administrator.

  1. When did the holder last initiate a transaction or otherwise engage with the account? temporal
  2. Which jurisdictional inactivity test applies, and over what period? requirement
  3. Does an exception prevent dormancy, such as a no-contact instruction or terms that block or penalise withdrawal? exception
  4. Was the balance transferred to a reclaim fund or administrator, and what reclaim reference preserves the holder's right to repayment? ownership
Position Expression and Contained Records How the account expresses balances as observations and how it binds to the postings it contains without absorbing their semantics.

Balance and Statement Declaration

Typed balance observations and the designation of periodic statements reporting them.

Declared balances and statement designation

Balance observations qualified by balance type, denomination reference and as-of instant, plus the designation and delivery arrangement of periodic account statements.

  1. Which balance types does this account report, such as booked, available or pending? measurement
  2. As of which instant does each balance hold, and when was it observed by this model? temporal
  3. Which model derives the balance from underlying entries, and is the value reported or recomputed here? provenance
  4. Over which period and at what frequency are statements issued for this account, and to whom? process

Contained Record Binding

The declared binding between the account and the postings it contains.

Posting container binding

The reference and selection criteria by which the account's contained postings are located in WM-ECO-016, with no local posting semantics.

  1. By which key are the postings belonging to this account selected in the contained posting model? composition
  2. Which posting attributes may this model read, and which operations remain exclusive to the posting model? relationship
  3. Are contained postings partitioned by denomination, sub-account or ledger dimension? classification
  4. How is a mismatch between a declared balance and the contained postings recorded rather than silently corrected? quality
Provenance, Evidence, Retention, Access and Alignment How account context is sourced, evidenced, validated, retained, shared and mapped to external representations.

Provenance, Evidence and Retention

Where each assertion came from, what evidence supports it, and how long the record must be kept.

Record provenance and source system

For each asserted element, the source system, asserting party, assertion time and ingestion time, so that conflicting reports about the same account can be adjudicated.

  1. Which system of record asserted this element, and which party operates it? provenance
  2. When was the value asserted at source, and when was it ingested into this model? temporal
  3. When two sources disagree about the same element, which precedence rule decides? decision
  4. What confidence or completeness qualifier attaches to a value obtained through a restricted or partial interface? quality

Supporting evidence linkage

An index of the evidence that supports account assertions, holding references and evidence types rather than copies of documents owned by other models.

  1. Which evidence items support the identity, party and classification assertions on this account? evidence
  2. Which model or system holds each evidence item, and how is it retrieved? relationship
  3. Until when does each evidence item remain valid, and what triggers refresh? temporal
  4. Is the evidence set sufficient under the applicable regime, and what is missing? validation

Retention and disposition designation

How long each class of account context must be retained, when disposition falls due, and which policy owner executes deletion, which is outside this model.

  1. What retention period applies to each class of account context, and which instrument sets it? retention
  2. From which event does the retention clock start: opening, last activity, closure or transfer? temporal
  3. Is any record under legal hold that suspends disposition? exception
  4. Which policy owner executes disposition, and what tombstone remains after deletion? authority

Validation, Access Designation and Standards Alignment

The controls that keep account context correct, the designation of who may see it, and the mappings that let it travel between representations.

Validation rules and quality measures

Structural and referential checks applied to account context, including identifier structure and check-digit validation, mandatory-field rules and cross-field consistency.

  1. Which structural and check-digit rules validate each identifier scheme value? validation
  2. Which elements are mandatory for this account's classification and interface profile? requirement
  3. Which cross-field consistency rules must hold, for example between status, closure timestamp and dormancy designation? constraint
  4. How are completeness and freshness of account context measured and reported? quality

Access and sharing designation

Which classes of account context may be disclosed to which recipient categories under which permission scope, expressed as designation and consent reference only.

  1. Which classes of account context are shareable, and which are restricted or maskable? access
  2. Which permission scope must a requester hold to see detailed identification and servicer data rather than basic data? security
  3. Which authorisation record permits a third party to receive this account's data, and where is it held? relationship
  4. Which regulatory access obligation is asserted for this account, and how settled is it? authority

Standards crosswalks and conflict register

Mappings from this model to external account representations and a register of the points where those representations conflict or cannot be satisfied simultaneously.

  1. To which external representations is this model mapped, and at which version of each? interoperability
  2. Which elements have no counterpart in a target representation, and how is the loss recorded? quality
  3. Where do two aligned standards impose incompatible cardinality or semantics on the same element? constraint
  4. What evidence supports any conformance claim, and where is a claim explicitly withheld? evidence

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
entity
Navigation path
NAV.SOC.ECO.ACC
Domain
SOC.ECO.ACC
Industry
Cross-industry
Tags
financialaccountsoc.eco.acc

What it is Filled

A financial account is an identified, durable container maintained by a financial institution or ledger operator for a business arrangement with one or more holders. This model owns account identity, identifier schemes, classification, party role bindings, servicing arrangement, denomination reference, bound terms and limits, protection designation, state and lifecycle, position declaration, provenance, evidence linkage, retention designation and interoperability projections. It owns no posting semantics, no monetary-unit semantics, no party master data, no payment execution and no runtime authorisation, enforcement or audit-trail semantics.

In scope

  • Account identity and the identifier schemes that denote it (IBAN, domestic BBAN, sort code plus account number, masked PAN, proprietary and interface resource identifiers)
  • Aliases, proxies, nicknames and display labels bound to the account
  • Product, regulatory and tax classification, each carried with its scheme and scheme version
  • Holder set, ownership structure (single, joint, trust, entity) and declared ownership shares
  • Beneficial owner and controlling-person role bindings expressed as references to party identifiers
  • Account servicer or provider and the servicing relationship
  • Operating authority: mandates, authorised signatories, powers of attorney and delegated operating rights
  • Denomination reference and permitted monetary instrument set, carried only as a reference
  • Terms bound to the account: fees, interest, limits, facilities, notice periods and withdrawal restrictions
  • Protection and guarantee designation (deposit guarantee scheme or deposit insurance ownership category)
  • Account status, state transitions, restrictions, opening, closure, switching and dormancy determination
  • Declared balances and statement designation as observations with an explicit as-of instant
  • Provenance, supporting-evidence linkage, validation controls, retention designation, access designation and standards crosswalks

Out of scope

  • Definition of currency, monetary units, minor units or instrument semantics (owned by WM-ECO-004)
  • Creation, amendment, reversal, matching or interpretation of postings and derivation of balances from them (owned by WM-ECO-016)
  • Party and legal-entity master data, entity verification and ownership hierarchies (referenced by identifier only)
  • Payment instruction, clearing, settlement and funds-availability execution
  • Issuance, evaluation, revocation or enforcement of data-access consents and the audit-trail record model
  • Product catalogue definition and price-list governance independent of a specific account
  • Deposit guarantee payout calculation and scheme operation
  • Custody of escheated balances and reclaim-fund repayment obligations
  • AML transaction monitoring, alerting, sanctions screening execution and case management
  • Credit decisioning, risk scoring and capital treatment
  • Card or payment instrument issuance and lifecycle
  • Chart-of-accounts taxonomy governance and accounting policy
  • Statement rendering channels, delivery infrastructure and notification transport

Why it exists Filled

Give an agent the context needed to identify a financial account, know who holds and services it, what it is denominated in, what state it is in, what rules and protections bind it, and which contained or neighbouring models own everything else.

Distinguishing features Filled

  • Identifies an account, its holders, servicer, denomination, state and protections, not its postings.
  • Unlike a party record, it references holders and servicers rather than owning their identity.
  • Unlike a payment instruction, it does not move funds.
  • Separates account status from consent and authorisation decisions made elsewhere.

What robots and AI may and may not do Filled

Must not

  • Display full account or card numbers where masking is required.
  • Initiate payments or transfers.
  • Evaluate or enforce data-access consent.
  • Delete account records under retention or legal hold.
  • Claim deposit protection without recorded evidence.

Only with a human decision

  • Opening, freezing or closing an account.
  • Declaring an account dormant or transferring unclaimed funds.

May

  • Register an account and normalise its identifier set.
  • Bind party roles such as holder and servicer.
  • Record state transitions with effective dates.
  • Flag dormancy candidates for review.

Moral aspects Filled

  • Account data reveals personal financial life and needs strong confidentiality.
  • Wrongful freezes or closures can cut people off from essential services.
  • Vulnerable customers may need protections recorded and respected.

Who is affected

  • Account holders
  • Servicing institutions
  • Authorised third parties
  • Regulators and deposit guarantee schemes

Owners Filled

Steward

A Dimension adopting this model must name a single accountable owner for account context, which is the contracting party, the financial institution servicing the account or the supervising regulator, and record the basis of that ownership.

Roles

Account context owner
Accountable for the correctness and currency of account identity, classification, party bindings, terms and status within the adopting Dimension; Approves source precedence rules and resolves conflicting assertions about the same account
Standards and alignment steward
Maintains crosswalks to external representations and the versions they target; Maintains the alignment conflict register and refuses conformance claims that lack recorded evidence
Regulatory and jurisdiction steward
Declares the jurisdictions in force and maps classification, protection, dormancy, access and retention obligations onto them; Records obligations that are contested or under reconsideration as unsettled rather than as compliance facts
Boundary and composition reviewer
Checks that no bundle, layer, finding or function reproduces a referenced or contained model's lifecycle, evaluation, execution, enforcement or audit-trail semantics; Routes any locally modelled target-owned concept to a composition link, out-of-scope entry or boundary note
Data quality and validation operator
Runs the validation rule set against the account population and publishes validation run reports; Raises integrity failures and completeness gaps as quality findings rather than correcting source data silently
Retention and disposition policy owner
Maintains the retention schedule and legal holds and executes disposition decisions emitted by this model; Confirms execution back to the model so tombstones carry an execution reference

Links to other meta-models Filled

references

  • WM-ECO-004 - The account declares its denomination and permitted monetary instruments by reference; identity, parties, lifecycle and rules stay with this model and unit or instrument semantics stay with the target.
  • Party and legal-entity identity model (candidate sibling, not yet registered) - Holder, beneficial owner, controlling person, servicer and mandate-holder bindings resolve to externally governed party identifiers such as the LEI; party master data and verification stay with the sibling.
  • Consent and data-access authorisation model (candidate sibling, not yet registered) - The account carries a sharing designation and an authorisation reference only; issuance, runtime evaluation, revocation and access logging belong to the sibling.
  • Payment instruction and credit transfer model (candidate sibling, not yet registered) - The account is referenced as debtor or creditor account by payment instructions; instruction lifecycle, reachability, clearing and settlement stay with the sibling.
  • Deposit guarantee or deposit insurance scheme model (candidate sibling, not yet registered) - The account carries scheme designation, eligibility status and ownership category; coverage computation, aggregation across accounts and payout stay with the scheme.

child

  • WM-ECO-016 - The account is the container for its postings and supplies the container binding and selection key; posting creation, amendment, reversal and balance derivation are owned by the target.

composes

  • WM-XCT-014 - This model composes into the registered parent container; cross-account exchange semantics and orchestration remain with the parent.

aligned

  • ISO 20022 account and account-management business components (acmt, camt) - Align account identification, type, servicer, opening, mandate maintenance, switching, closing and account reporting concepts with the ISO 20022 repository without claiming conformance.
  • ISO 13616 IBAN structure and national IBAN format registry - Align the IBAN identifier scheme, its structure and its check-digit validation with the ISO standard and the registry maintained by its Registration Authority.
  • FIBO FBC ClientsAndAccounts ontology - Align the account, account holder, account provider, account identifier, deposit account, loan or credit account and ledger account concepts with the published ontology definitions.
  • Open Banking Read/Write API v4.0 account resource - Align the account resource projection, identification scheme choices, status and permission-scoped field visibility with a deployed interface specification.
  • CRS and FATCA financial account categories - Align the tax classification of the account with the depository, custodial, equity or debt interest, cash value insurance and annuity categories and their excluded-account carve-outs.

neighbor

  • WM-ECO-004 monetary unit or instrument - The account declares its denomination and permitted instrument set as a reference; it does not define currency codes, minor units, redenomination or instrument behaviour.
  • WM-ECO-016 posting - The account supplies the container binding and selection criteria for its postings; posting lifecycle, reversal, matching and balance derivation stay in WM-ECO-016.
  • WM-XCT-014 parent exchange or transaction container - This model composes into the parent; cross-account orchestration and exchange-level semantics are not modelled here.
  • Party and legal-entity identity master - The account carries role bindings and identifier references such as the LEI; it does not own party records, verification outcomes or corporate hierarchies.
  • Consent and data-access authorisation model - The account carries an access designation and a consent reference only; issuance, runtime evaluation, revocation and audit trails are owned by the authorisation model.
  • Payment instruction and credit transfer model - The account is referenced as debtor or creditor account; instruction lifecycle, reachability and settlement remain outside.
  • Product and offering catalogue - The account carries a bound terms instance and product reference; generic product definition and tariff governance sit in the product model.
  • Deposit guarantee scheme or deposit insurance model - The account carries scheme-scoped eligibility and ownership-category designation; coverage computation and payout are performed by the scheme.
  • Unclaimed property or reclaim fund model - The account carries dormancy inputs, the determination and a transfer reference; custody of transferred balances and the repayment obligation are external.

parent

  • WM-XCT-014

contains

  • WM-ECO-016

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • The authoritative master-system identifier assigned by the system of record, which for a financial account is the servicing institution's account identifier and for an artifact is the identifier assigned by the system that produced it.
  • A governed global identifier or IRI issued by a recognised authority, such as an IBAN under ISO 13616 for the account or an LEI under ISO 17442 for a legal entity, used when no master-system identifier is available or when cross-institution resolution is required.
  • A UUID or ULID assigned by the adopting Dimension, used only when neither of the above exists, and always recorded as Dimension-assigned rather than presented as authoritative.
  • A date, a period, a status, a balance or a party name is never an identifier; where a natural key seems to exist it is recorded as an attribute and a surrogate identifier is minted instead.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • An account has a servicer-issued identifier, holders, a currency, a type, a state and governing terms.
  • Often confused with a ledger posting, a payment, a customer party record and a product offering.

Capabilities and actions required Filled

  • Register account record: Create the model's context record for an account by binding its authoritative master-system identifier, servicer reference and opening timestamp.
  • Resolve and normalise the identifier set: Normalise, structurally validate and rank the scheme-qualified identifiers that denote the account, including check-digit verification where the scheme defines one.
  • Assign account classifications: Attach product, regulatory and tax classifications to the account, each carrying its code set, version, jurisdiction and effective period.
  • Bind party roles to the account: Attach holder, beneficial owner, controlling person and mandate-holder role bindings as references to externally governed party identifiers.
  • Declare denomination reference: Attach the account's denomination and permitted instrument references to the monetary unit or instrument model.
  • Record account state transition: Record a change in account status with its event timestamp, observation timestamp, cause reference and resulting capability effects.
  • Derive dormancy candidacy: Apply the jurisdictional inactivity test to the last holder-initiated activity timestamp and produce a dormancy determination with its basis and exceptions.
  • Bind the posting container: Register the reference and selection key by which the account's contained postings are located in the posting model.
  • Assemble the account context package: Produce the agent-readable package for one account, comprising the bootstrap file, the bundle and layer structure and the resolvable artifact references.
  • Project to an interchange profile: Map the account context onto an external representation and report the elements that cannot be carried by that representation.
  • Schedule retention disposition: Compute disposition due dates from the retention schedule and emit a disposition decision record for the adopting Dimension to execute.

Hazards and failure modes required Filled

  • Fraud from exposed account identifiers.
  • Financial exclusion from wrong status changes.
  • Loss of funds through misattributed holders.

Standards and interfaces required Filled

  • ISO 13616 IBAN.
  • ISO 9362 BIC.
  • ISO 4217 currency codes.
  • ISO 20022 account messages.
  • PCI DSS for card account data.

Context of use required Filled

  • IBAN-first identification is assumed only for the European Economic Area and other adopting countries; United States accounts are identified by routing number plus account number and many jurisdictions use a domestic basic bank account number alone.
  • The payment account, basic-features account, fee information document, statement of fees and switching-service constructs are assumed only for European Union and European Economic Area consumer payment accounts.
  • Deposit guarantee constructs follow the European Union directive for European accounts and the Federal Deposit Insurance Corporation framework for United States insured depository institutions; other jurisdictions operate different schemes not modelled here.
  • HMRC manual pages are used as an accessible rendering of the Common Reporting Standard; implementing legislation and excluded-account lists vary by jurisdiction.
  • The fifteen-year dormancy test and the reclaim-fund mechanism are United Kingdom specific and are not assumed elsewhere.
  • The Open Banking Read/Write API v4.0 projection reflects the United Kingdom ecosystem; other open-finance frameworks expose different account resources and permission models.

Sources Filled

  1. FIBO FBC/ProductsAndServices/ClientsAndAccounts ontology - EDM Council (standardised through OMG)
  2. Open Banking Read/Write API v4.0 - Accounts resource and data model - Open Banking Limited (UK)
  3. Directive 2014/92/EU on comparability of fees, payment account switching and access to payment accounts with basic features - European Union (Official Journal, EUR-Lex)
  4. Directive 2014/49/EU on deposit guarantee schemes - European Union (Official Journal, EUR-Lex)
  5. Dormant Bank and Building Society Accounts Act 2008, section 10 (Meaning of 'dormant') - UK Parliament (legislation.gov.uk, The National Archives)
  6. Introducing the Legal Entity Identifier (LEI) - Global Legal Entity Identifier Foundation (GLEIF)
  7. FDIC - Financial products insured by the FDIC and deposit insurance ownership categories - Federal Deposit Insurance Corporation (United States)
  8. IBAN rules - Deutsche Bundesbank
  9. Required Rulemaking on Personal Financial Data Rights (12 CFR part 1033) - Consumer Financial Protection Bureau (United States)
  10. IEIM401505 - Financial Accounts: Introduction - HM Revenue and Customs (UK)
  11. IEIM401540 - Financial Accounts: Depository Account - HM Revenue and Customs (UK)
  12. ISO 20022 Message Definitions catalogue (business areas including acmt Account Management and camt Cash Management) - ISO 20022 Registration Authority
  13. ISO 13616-1:2020 Financial services - International bank account number (IBAN) - Part 1: Structure of the IBAN - International Organization for Standardization
  14. Personal Financial Data Rights Reconsideration (advance notice of proposed rulemaking) - Consumer Financial Protection Bureau (United States)

Open questions

  • Retrieve FATF Recommendations 10 and 11 and FinCEN 31 CFR 1010.230 through an alternate non-blocked channel to ground the beneficial-ownership threshold, the control prong and the five-year record-keeping rule that currently rest on HMRC and EU proxies.
  • Retrieve the ISO 20022 e-Repository CashAccount business component and the ISO 13616 IBAN Registry file to replace the Bundesbank and Open Banking renderings with element-level normative support for identifier structure and validation.
  • Cite the OECD Common Reporting Standard primary text directly instead of relying on HMRC internal manual pages IEIM401505 and IEIM401540 as the only support for tax-status-classification, including the 1 January 2026 depository-account expansion.
  • Verify United States state unclaimed-property dormancy periods and the Revised Uniform Unclaimed Property Act so dormancy is grounded in more than the UK fifteen-year statutory test before derive-dormancy-candidacy is parameterized by jurisdiction.
  • Confirm whether planning/VERCY-MODEL-RELATIONS.csv holds an inbound CONTAINS row from WM-XCT-014 to WM-ECO-015, since the registry asserts the parent but the frozen contract shows only the two outbound rows.
  • Decide whether the seven unregistered neighbour references (party master, consent and authorisation, payment instruction, product catalogue, deposit guarantee scheme, unclaimed property, and any statement-rendering owner) need registered REFERENCE rows, and register them before those boundary notes become typed edges.
  • Open an account-group model candidate covering cross-institution aggregation, umbrella and relationship accounts, notional pooling and virtual account hierarchies, together with securities and custody account decomposition, Islamic and profit-sharing structures, escrow and client-money segregation, and tokenised deposit identifier schemes, all currently declared as gaps or under-modelled.
  • FATF Recommendations 10 and 11 and the FinCEN customer due diligence rule at 31 CFR 1010.230 could not be retrieved live because the publishers blocked automated access, so the beneficial ownership threshold, the control prong and the five-year record-keeping rule are represented only through HMRC and EU proxies and are marked as unverified detail.
  • The ISO 20022 e-Repository page for the CashAccount business component and the ISO 13616 IBAN Registry file did not render for this research, so element-level ISO 20022 and IBAN detail is grounded in the Bundesbank and Open Banking renderings and treated as alignment rather than verified normative text.
  • United States state unclaimed-property dormancy periods and the Revised Uniform Unclaimed Property Act could not be verified, so only the United Kingdom fifteen-year statutory test is cited and dormancy is treated as jurisdictional.
  • Securities and custody account internal structure, including position holdings, safekeeping accounts and segregation of client assets, is only classified, not decomposed.
  • Islamic and profit-sharing account structures, notional pooling, virtual account hierarchies and escrow or client-money segregation rules are under-modelled and no primary source was secured.
  • Tokenised deposit and account-based digital currency identifier schemes are acknowledged only through the CRS depository-account expansion and are otherwise not modelled.
  • Payment card account specifics beyond a masked primary account number as an identifier scheme are not modelled.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-eco-015-financial-account/spec.yaml, ver-cy/world-models/card-supplements/wm-eco-015-financial-account.json