Initial commit: Financial Crime domain exemplar
This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
# [Financial Crime](../domain.md)
|
||||
|
||||
## Events
|
||||
|
||||
### Account Status Changed
|
||||
|
||||
Emitted when an account status changes in a way that affects operational behavior.
|
||||
|
||||
```yaml
|
||||
actor: Customer
|
||||
entity: Account
|
||||
emitted_on:
|
||||
- update
|
||||
business_meaning: The account lifecycle status has changed and associated controls may differ
|
||||
downstream_impact:
|
||||
- Transaction permissions and servicing controls may be recalculated
|
||||
- Compliance and customer notification workflows may be initiated
|
||||
attributes:
|
||||
event_timestamp:
|
||||
type: datetime
|
||||
description: Time the account status change was recorded
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
# [Financial Crime](../domain.md)
|
||||
|
||||
## Events
|
||||
|
||||
### Agreement Activated
|
||||
|
||||
Emitted when an agreement becomes active and enforceable.
|
||||
|
||||
```yaml
|
||||
actor: Party Role
|
||||
entity: Agreement
|
||||
emitted_on:
|
||||
- update
|
||||
business_meaning: Contractual terms are now active and govern in-scope roles and products
|
||||
downstream_impact:
|
||||
- Product and servicing rules can be applied under the active agreement
|
||||
- Contract lifecycle and compliance timelines are started
|
||||
attributes:
|
||||
event_timestamp:
|
||||
type: datetime
|
||||
description: Time the agreement became active
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
# [Financial Crime](../domain.md)
|
||||
|
||||
## Events
|
||||
|
||||
### Customer Onboarded
|
||||
|
||||
Emitted when a new Customer relationship is established and approved for service.
|
||||
|
||||
```yaml
|
||||
actor: Party
|
||||
entity: Customer
|
||||
emitted_on:
|
||||
- create
|
||||
business_meaning: A party has completed onboarding and is now recognized as a customer
|
||||
downstream_impact:
|
||||
- Customer profile is activated for product and service interactions
|
||||
- Ongoing due diligence schedule is initialized
|
||||
attributes:
|
||||
event_timestamp:
|
||||
type: datetime
|
||||
description: Time the customer onboarding status became active
|
||||
```
|
||||
@@ -0,0 +1,37 @@
|
||||
# [Financial Crime](../domain.md)
|
||||
|
||||
## Events
|
||||
|
||||
### High Risk Transaction Detected
|
||||
|
||||
Emitted when transaction monitoring identifies a transaction with high financial crime risk indicators.
|
||||
|
||||
```yaml
|
||||
actor: Transaction Monitoring System
|
||||
entity: Transaction
|
||||
emitted_on:
|
||||
- create
|
||||
business_meaning: A transaction has been identified for enhanced investigation due to elevated risk
|
||||
downstream_impact:
|
||||
- Alert and case management workflows are initiated
|
||||
- Potential reporting obligations may be triggered
|
||||
attributes:
|
||||
event_timestamp:
|
||||
type: datetime
|
||||
description: Time the high-risk detection decision was produced
|
||||
alert_type:
|
||||
type: string
|
||||
description: Category of the detection rule that triggered (e.g. structuring, velocity, geographic)
|
||||
severity:
|
||||
type: string
|
||||
description: Assessed severity level of the alert (low, medium, high, critical)
|
||||
detection_method:
|
||||
type: string
|
||||
description: Name of the detection model or rule that produced the alert
|
||||
threshold_breached:
|
||||
type: string
|
||||
description: The specific threshold or limit that was exceeded
|
||||
risk_score:
|
||||
type: decimal
|
||||
description: Numeric risk score assigned by the detection engine
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
# [Financial Crime](../domain.md)
|
||||
|
||||
## Events
|
||||
|
||||
### KYC Status Updated
|
||||
|
||||
Emitted when the KYC status of a Party is updated following review or remediation.
|
||||
|
||||
```yaml
|
||||
actor: Compliance Officer
|
||||
entity: Party
|
||||
emitted_on:
|
||||
- update
|
||||
business_meaning: The due diligence posture of a party has changed and risk treatment may be updated
|
||||
downstream_impact:
|
||||
- Risk scoring and monitoring thresholds may be recalculated
|
||||
- Relationship restrictions or approvals may be adjusted
|
||||
attributes:
|
||||
event_timestamp:
|
||||
type: datetime
|
||||
description: Time the KYC status update took effect
|
||||
```
|
||||
@@ -0,0 +1,22 @@
|
||||
# [Financial Crime](../domain.md)
|
||||
|
||||
## Events
|
||||
|
||||
### Party Role Assigned
|
||||
|
||||
Emitted when a Party assumes a new Party Role in a business context.
|
||||
|
||||
```yaml
|
||||
actor: Party
|
||||
entity: Party Role
|
||||
emitted_on:
|
||||
- create
|
||||
business_meaning: A party has been assigned a role that changes participation context and controls
|
||||
downstream_impact:
|
||||
- Access and entitlements can be updated for the new role
|
||||
- Role-based monitoring and due diligence workflows are triggered
|
||||
attributes:
|
||||
event_timestamp:
|
||||
type: datetime
|
||||
description: Time the role assignment became effective
|
||||
```
|
||||
@@ -0,0 +1,37 @@
|
||||
# [Financial Crime](../domain.md)
|
||||
|
||||
## Events
|
||||
|
||||
### Transaction Executed
|
||||
|
||||
Emitted when a financial transaction is successfully executed.
|
||||
|
||||
```yaml
|
||||
actor: Payment Initiator
|
||||
entity: Transaction
|
||||
emitted_on:
|
||||
- create
|
||||
business_meaning: Funds movement has been executed and committed as a business transaction
|
||||
downstream_impact:
|
||||
- Ledger and balance updates are triggered
|
||||
- Transaction monitoring and screening pipelines are triggered
|
||||
attributes:
|
||||
event_timestamp:
|
||||
type: datetime
|
||||
description: Time the transaction was executed
|
||||
amount:
|
||||
type: decimal
|
||||
description: Monetary value moved by the transaction
|
||||
currency_code:
|
||||
type: string
|
||||
description: ISO 4217 currency code of the transaction amount
|
||||
payer_role_identifier:
|
||||
type: string
|
||||
description: Role identifier of the payer party
|
||||
payee_role_identifier:
|
||||
type: string
|
||||
description: Role identifier of the payee party
|
||||
channel:
|
||||
type: string
|
||||
description: Channel through which the transaction was initiated (e.g. branch, online, mobile)
|
||||
```
|
||||
Reference in New Issue
Block a user