Appearance
Savings Account Datatables (m_saving_account)
Savings account datatables attach custom data to individual savings and deposit account records. Regulatory requirements around deposit accounts are typically more demanding than for lending products - source of funds, beneficial ownership, and AML classification are standard requirements in most jurisdictions. A datatable is the right tool for capturing this structured data without modifying the core account model.
All examples below use apptableName: "m_saving_account".
Source of Funds Declaration
AML and KYC regulations in most jurisdictions require deposit-taking institutions to record the source of funds for each account at opening. This is one-to-one per account.
Use case: Satisfying regulatory requirements to document and verify the origin of funds deposited into savings and current accounts.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Primary_Source | Dropdown | Employment income / Business income / Investment returns / Remittance / Inheritance / Sale of property / Pension / Other |
Source_Description | Text | Free-text elaboration for "Other" or complex cases |
Employer_or_Business_Name | String (150) | For employment or business income |
Country_of_Source | Dropdown | For cross-border funds and remittances |
Declared_Monthly_Deposit_Volume | Decimal | Expected monthly inflow at account opening |
Declaration_Date | Date | |
Reviewed_By | String (100) | Officer who reviewed and accepted the declaration |
Verified | Boolean | Whether the source has been independently verified |
Verification_Method | Dropdown | Payslip / Bank statement / Tax return / Business registration / None |
AML Risk Classification
Risk-based AML frameworks require each account to be assigned a risk rating at opening and reviewed periodically. A datatable captures the current rating and review history. Use one-to-one for the current state, or one-to-many if full history is required.
Use case: Implementing a risk-based AML program with structured risk ratings per account, as required by most central bank AML regulations.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Risk_Rating | Dropdown | Low / Medium / High / Prohibited |
Rating_Date | Date | Date the current rating was assigned |
Rating_Basis | Dropdown | Standard criteria / Enhanced due diligence / PEP linkage / Geographic risk / Transaction pattern |
Next_Review_Date | Date | Scheduled next review date based on risk tier |
Enhanced_Due_Diligence | Boolean | Whether EDD has been completed |
EDD_Completion_Date | Date | |
Suspicious_Activity_Flag | Boolean | Whether a SAR has been filed or is under consideration |
Reviewed_By | String (100) |
A compliance officer can pull all accounts with Risk_Rating = High and Next_Review_Date overdue to generate a follow-up list without any external tools.
Account Purpose
Recording the intended purpose of an account - particularly for current and business accounts - supports both AML monitoring (expected transaction patterns) and product suitability assessments.
Use case: Documenting account purpose at opening for transaction monitoring calibration and regulatory classification.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Account_Purpose | Dropdown | Personal savings / Business operating / Payroll / Investment / Escrow / Loan repayment / School fees / Emergency fund |
Expected_Transaction_Frequency | Dropdown | Daily / Weekly / Monthly / Quarterly / Irregular |
Expected_Monthly_Turnover | Decimal | Expected monthly debit/credit volume |
Primary_Transaction_Channel | Dropdown | Branch / Mobile banking / Internet banking / Agent / ATM |
International_Transactions_Expected | Boolean | Whether cross-border transactions are anticipated |
These fields feed transaction monitoring rules: an account declared for personal savings that suddenly shows high-frequency international transfers triggers enhanced review.
Beneficial Ownership
For corporate and business accounts, AML regulations require the identification of ultimate beneficial owners (UBOs) - individuals who own or control more than a threshold percentage of the legal entity. Since there can be multiple UBOs per account, this is multiRow: true.
Use case: Capturing UBO information for corporate and business savings accounts as required by AML/CFT regulations.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Full_Name | String (150) | |
Date_of_Birth | Date | |
Nationality | Dropdown | |
ID_Type | Dropdown | Passport / National ID / Driving licence |
ID_Number | String (50) | |
Ownership_Percentage | Decimal | Percentage of shares or control |
Is_Director | Boolean | |
Is_PEP | Boolean | Politically Exposed Person |
PEP_Details | Text | Role, jurisdiction, end date if former PEP |
Verified | Boolean | Whether identity has been verified against documentation |
Verification_Date | Date |
Dormancy and Reactivation Tracking
Regulatory frameworks in many jurisdictions have specific rules for dormant accounts - definition periods, communication requirements, and unclaimed funds transfer obligations. A datatable captures the relevant state.
Use case: Managing the dormancy lifecycle per account for regulatory compliance and unclaimed funds reporting.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Dormancy_Start_Date | Date | Date the account entered dormant status |
Last_Transaction_Date | Date | Date of last customer-initiated transaction |
Dormancy_Notice_Sent | Boolean | Whether required notification was sent to the customer |
Notice_Sent_Date | Date | |
Regulatory_Transfer_Due_Date | Date | Date by which unclaimed funds must be transferred to regulator |
Funds_Transferred | Boolean | Whether funds have been transferred to the regulatory authority |
Transfer_Date | Date | |
Reactivation_Date | Date | If the account has since been reactivated |
Fixed Deposit and Term Deposit Details
For institutions using the savings module to manage fixed and term deposits, product-level configuration may not capture all deal-level attributes needed for reporting.
Use case: Recording deal-specific attributes for fixed and term deposit accounts that go beyond the standard savings product configuration.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Deposit_Type | Dropdown | Fixed / Call / Notice period / Certificate of deposit |
Agreed_Rate | Decimal | Negotiated rate if different from the product default |
Rate_Type | Dropdown | Fixed / Floating / Stepped |
Auto_Rollover | Boolean | Whether the deposit rolls over automatically at maturity |
Rollover_Instructions | Dropdown | Principal only / Principal and interest / Liquidate |
Relationship_Manager | String (100) | For high-value deposits managed by a relationship team |
Referral_Source | Dropdown | Branch walk-in / Relationship manager / Digital / Referral / Corporate |