Skip to main content

Financial Profile Examples

Financial Compliance Monitor​

A compliance agent for a universal financial institution that monitors both banking activity (wire and ACH transfers, deposits) and brokerage activity (securities trading) for AML, fraud, and regulatory compliance. It spans the deposit-taking and broker-dealer sides of the house: BSA/AML and GLBA on the banking side, FINRA, SEC, and MiFID II on the brokerage side.

financial-compliance-agent.adl.yaml
$schema: https://adl-spec.org/0.3/schema.json
adl_spec: 0.3.0
name: Financial Compliance Monitor
description: Monitors both banking activity (wires, deposits) and brokerage activity (securities trading) across a
  universal financial institution for AML, fraud, and regulatory compliance.
version: 1.0.0
profiles:
  - urn:adl:profile:financial:1.0
lifecycle:
  status: active
  effective_date: 2026-01-01T00:00:00Z
provider:
  name: Meridian Financial Group
  url: https://meridian.example
  contact: compliance@meridian.example
model:
  capabilities:
    - function_calling
tools:
  - name: screen_wire_transfers
    description: Screen banking wire and ACH transfers for BSA/AML and sanctions risk
    parameters:
      type: object
      properties:
        account_id:
          type: string
        lookback_days:
          type: integer
          default: 30
      required:
        - account_id
    read_only: true
  - name: surveil_trades
    description: Surveil securities trading activity for market manipulation and insider trading
    parameters:
      type: object
      properties:
        account_id:
          type: string
        instrument:
          type: string
      required:
        - account_id
    read_only: true
  - name: file_sar
    description: File a Suspicious Activity Report with FinCEN (covers both banking and brokerage activity)
    parameters:
      type: object
      properties:
        subject_ids:
          type: array
          items:
            type: string
        activity_type:
          type: string
          enum:
            - banking
            - securities
        narrative:
          type: string
      required:
        - subject_ids
        - narrative
    requires_confirmation: true
permissions:
  network:
    allowed_hosts:
      - core-banking.meridian.example
      - market-surveillance.meridian.example
      - fincen.gov
    allowed_protocols:
      - https
    deny_private: true
  filesystem:
    allowed_paths:
      - path: /data/banking/**
        access: read
      - path: /data/trading/**
        access: read
      - path: /data/reports/**
        access: read_write
security:
  authentication:
    type: mtls
    required: true
  encryption:
    in_transit:
      required: true
      min_version: "1.3"
    at_rest:
      required: true
      algorithm: AES-256-GCM
data_classification:
  sensitivity: confidential
  categories:
    - pii
    - financial
  retention:
    min_days: 1825
  handling:
    encryption_required: true
    logging_required: true
  financial:
    data_types:
      - transaction_data
      - nonpublic_personal_info
      - market_data
      - material_nonpublic_info
    pci_applicable: false
financial_data_handling:
  pci_scope:
    in_scope: false
  data_residency:
    - jurisdiction: US
      regulation: GLBA
    - jurisdiction: EU
      regulation: MIFID_II
transaction_controls:
  transaction_limits:
    max_single_amount: 10000000
    currency: USD
  pre_execution_controls:
    enabled: true
    price_tolerance_pct: 2
    requires_approval_above: 1000000
  kill_switch:
    enabled: true
    trigger_conditions:
      - error_rate_threshold
      - anomaly_detection
    notification_targets:
      - compliance-team@meridian.example
  segregation_of_duties:
    enabled: true
    restricted_actions:
      - file_sar
    approval_role: Compliance Officer
regulatory_scope:
  applicable_regulations:
    - GLBA
    - BSA_AML
    - BASEL_III
    - FINRA
    - SEC_REG
    - MIFID_II
  jurisdictions:
    - jurisdiction: US
      regulation: BSA_AML
    - jurisdiction: EU
      regulation: MIFID_II
  record_retention:
    min_retention_days: 1825
    tamper_proof: true
financial_risk_management:
  model_risk:
    tier: tier_2
    validated_by: Model Risk Committee
    validated_at: 2025-12-15T00:00:00Z
    methodology: Champion-challenger with backtesting
  aml_controls:
    screening_required: true
    monitoring_level: real_time
    kyc_refresh_days: 365
  operational_risk:
    category: high
    assessed_by: Operational Risk Committee
    assessed_at: 2025-12-15T00:00:00Z
    capital_reserve: true
metadata:
  authors:
    - name: Meridian Compliance Team
      email: compliance@meridian.example
  license: Proprietary
  tags:
    - financial
    - banking
    - brokerage
    - aml
    - compliance

Both Sides of the House​

BankingBrokerage
screen_wire_transfers tool (wire/ACH AML)surveil_trades tool (market surveillance)
GLBA, BSA_AML, BASEL_III regulationsFINRA, SEC_REG, MIFID_II regulations
nonpublic_personal_info, transaction_datamarket_data, material_nonpublic_info
transaction_limits (wire ceilings)pre_execution_controls (pre-trade checks)

file_sar and the AML controls in financial_risk_management apply across both — a single FinCEN SAR pipeline and shared KYC/monitoring cadence.

Key Financial Fields​

FieldPurpose
financial_data_handlingPCI scope assessment and multi-jurisdiction data residency
transaction_controlsTransaction limits, pre-trade checks, kill switch, segregation of duties
regulatory_scopeBanking + brokerage regulations and record retention
financial_risk_managementModel risk tier, AML controls, operational risk capital
data_classification.financialBanking and brokerage data types

Compliance Highlights​

  • Authentication: Mutual TLS (mTLS) for all connections
  • Encryption: TLS 1.3 in transit, AES-256-GCM at rest
  • Kill Switch: Triggered on error rate threshold or anomaly detection (required under MiFID II)
  • Segregation of Duties: SAR filing requires Compliance Officer approval
  • Record Retention: 5-year minimum, tamper-proof storage
  • AML: Real-time monitoring across banking and brokerage, annual KYC refresh

Composed with the Governance Profile​

The Financial Profile is designed to compose with the Governance Profile. The composite example below declares both urn:adl:profile:governance:1.0 and urn:adl:profile:financial:1.0, adding the governance-required autonomy and compliance_framework members on top of the financial members above.

composite/governance-financial-agent.adl.yaml
$schema: https://adl-spec.org/0.3/schema.json
adl_spec: 0.3.0
name: Financial Compliance Monitor
description: Monitors both banking activity (wires, deposits) and brokerage activity (securities trading) across a
  universal financial institution for AML, fraud, and regulatory compliance.
version: 1.0.0
profiles:
  - urn:adl:profile:governance:1.0
  - urn:adl:profile:financial:1.0
lifecycle:
  status: active
  effective_date: 2026-01-01T00:00:00Z
provider:
  name: Meridian Financial Group
  url: https://meridian.example
  contact: compliance@meridian.example
model:
  capabilities:
    - function_calling
tools:
  - name: screen_wire_transfers
    description: Screen banking wire and ACH transfers for BSA/AML and sanctions risk
    parameters:
      type: object
      properties:
        account_id:
          type: string
        lookback_days:
          type: integer
          default: 30
      required:
        - account_id
    read_only: true
  - name: surveil_trades
    description: Surveil securities trading activity for market manipulation and insider trading
    parameters:
      type: object
      properties:
        account_id:
          type: string
        instrument:
          type: string
      required:
        - account_id
    read_only: true
  - name: file_sar
    description: File a Suspicious Activity Report with FinCEN (covers both banking and brokerage activity)
    parameters:
      type: object
      properties:
        subject_ids:
          type: array
          items:
            type: string
        activity_type:
          type: string
          enum:
            - banking
            - securities
        narrative:
          type: string
      required:
        - subject_ids
        - narrative
    requires_confirmation: true
permissions:
  network:
    allowed_hosts:
      - core-banking.meridian.example
      - market-surveillance.meridian.example
      - fincen.gov
    allowed_protocols:
      - https
    deny_private: true
  filesystem:
    allowed_paths:
      - path: /data/banking/**
        access: read
      - path: /data/trading/**
        access: read
      - path: /data/reports/**
        access: read_write
security:
  authentication:
    type: mtls
    required: true
  encryption:
    in_transit:
      required: true
      min_version: "1.3"
    at_rest:
      required: true
      algorithm: AES-256-GCM
data_classification:
  sensitivity: confidential
  categories:
    - pii
    - financial
  retention:
    min_days: 1825
  handling:
    encryption_required: true
    logging_required: true
  financial:
    data_types:
      - transaction_data
      - nonpublic_personal_info
      - market_data
      - material_nonpublic_info
    pci_applicable: false
financial_data_handling:
  pci_scope:
    in_scope: false
  data_residency:
    - jurisdiction: US
      regulation: GLBA
    - jurisdiction: EU
      regulation: MIFID_II
transaction_controls:
  transaction_limits:
    max_single_amount: 10000000
    currency: USD
  pre_execution_controls:
    enabled: true
    price_tolerance_pct: 2
    requires_approval_above: 1000000
  kill_switch:
    enabled: true
    trigger_conditions:
      - error_rate_threshold
      - anomaly_detection
    notification_targets:
      - compliance-team@meridian.example
  segregation_of_duties:
    enabled: true
    restricted_actions:
      - file_sar
    approval_role: Compliance Officer
regulatory_scope:
  applicable_regulations:
    - GLBA
    - BSA_AML
    - BASEL_III
    - FINRA
    - SEC_REG
    - MIFID_II
  jurisdictions:
    - jurisdiction: US
      regulation: BSA_AML
    - jurisdiction: EU
      regulation: MIFID_II
  record_retention:
    min_retention_days: 1825
    tamper_proof: true
financial_risk_management:
  model_risk:
    tier: tier_2
    validated_by: Model Risk Committee
    validated_at: 2025-12-15T00:00:00Z
    methodology: Champion-challenger with backtesting
  aml_controls:
    screening_required: true
    monitoring_level: real_time
    kyc_refresh_days: 365
  operational_risk:
    category: high
    assessed_by: Operational Risk Committee
    assessed_at: 2025-12-15T00:00:00Z
    capital_reserve: true
autonomy:
  tier: 1
  basis: Supervised financial-crimes monitoring; all SAR filings require human confirmation.
  classified_by: Meridian Compliance Team
  classified_at: 2026-01-01T00:00:00Z
compliance_framework:
  primary_framework: NIST_800_53
  control_mappings:
    - framework: NIST
      control_id: AU-2
      status: implemented
    - framework: NIST
      control_id: AC-5
      status: implemented
    - framework: NIST
      control_id: SC-13
      status: implemented
metadata:
  authors:
    - name: Meridian Compliance Team
      email: compliance@meridian.example
  license: Proprietary
  tags:
    - financial
    - banking
    - brokerage
    - aml
    - compliance