Appearance
Savings Product Datatables (m_savings_product)
Savings product datatables attach custom data to savings and deposit product definitions. Like loan product datatables, data here describes the product itself - its regulatory standing, market positioning, and governance attributes - rather than individual accounts. This supports product governance, regulatory reporting by product type, and product portfolio management.
All examples below use apptableName: "m_savings_product". All are one-to-one per product.
Regulatory Classification
Deposit products are classified and reported to regulators under specific product taxonomies. Setting these at the product level means all accounts under the product inherit the classification automatically.
Use case: Assigning regulatory codes to each savings product so that deposit portfolio reports and regulatory returns can be generated by product category without account-level manual input.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Regulatory_Product_Code | String (20) | Code from the central bank's deposit product taxonomy |
Deposit_Category | Dropdown | Demand deposit / Time deposit / Savings / Notice account / Current account / Escrow |
Is_Insured | Boolean | Whether deposits under this product are covered by deposit insurance |
Insurance_Scheme | Dropdown | Name or code of the deposit insurance scheme |
Insurance_Coverage_Limit | Decimal | Maximum insured amount per depositor |
Qualifies_as_Liquid_Asset | Boolean | For liquidity ratio reporting |
Reserve_Requirement_Applies | Boolean | Whether mandatory reserve requirements apply to this deposit type |
Deposit Insurance and Consumer Protection
Regulatory requirements in many jurisdictions mandate that customers are informed of deposit insurance status at account opening. A datatable ensures this is consistently recorded per product.
Use case: Documenting deposit insurance attributes and consumer protection compliance status for each product, to support regulatory reporting and customer disclosure obligations.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Insurance_Scheme_Name | String (150) | Full name of the insurance fund or guarantee scheme |
Insurance_Regulator | String (150) | Supervising authority for the scheme |
Coverage_Per_Depositor | Decimal | Maximum coverage per individual depositor |
Currency_of_Coverage | Dropdown | |
Disclosure_Required | Boolean | Whether disclosure at account opening is legally required |
Disclosure_Template_Version | String (20) | Version of the disclosure document used |
Last_Regulatory_Confirmation_Date | Date | Date the product's insurance status was confirmed with the regulator |
Market Positioning and Target Segment
Savings products are designed for specific customer segments - individual savers, businesses, youth, women's groups, or specific income bands. Recording this at the product level enables portfolio analysis by segment without account-level data entry.
Use case: Tracking the intended market segment and social positioning of each savings product for impact reporting and portfolio segmentation.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Target_Segment | Dropdown | General public / Youth / Women / Agriculture / SME / Salary earners / Low-income / Other |
Minimum_Age | Number | Minimum account holder age (for youth products) |
Maximum_Age | Number | Maximum age (e.g. for retirement or pension savings products) |
Gender_Targeted | Dropdown | All / Women only / Men only |
Rural_Urban_Target | Dropdown | Urban / Peri-urban / Rural / All |
Impact_Category | Dropdown | Financial inclusion / Women's empowerment / Youth savings / Agricultural finance / Other |
Is_Group_Product | Boolean | Whether the product is designed for groups rather than individuals |
Pricing and Terms Documentation
Savings product pricing - interest rates, minimum balances, and fees - is configured in the core Fineract product setup. A datatable supplements this with governance and disclosure documentation.
Use case: Recording pricing approval history and consumer disclosure compliance for each savings product.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Advertised_Rate | Decimal | Rate used in marketing materials |
Effective_Annual_Rate | Decimal | True EAR accounting for compounding |
Rate_Approved_By | String (150) | Board or committee that approved the current rate |
Rate_Approval_Date | Date | |
Rate_Review_Date | Date | Date of next scheduled rate review |
Rate_Disclosed_on_Website | Boolean | |
Fee_Schedule_Version | String (20) | Version of the applicable fee schedule |
Product Lifecycle
Savings products are introduced, modified, and sometimes withdrawn. Tracking lifecycle events at the product level supports regulatory notification obligations and product portfolio management.
Use case: Managing the savings product lifecycle from launch through discontinuation for governance and regulatory compliance.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Product_Status | Dropdown | Active / Pilot / Suspended / Discontinued |
Launch_Date | Date | |
Pilot_Start_Date | Date | |
Pilot_End_Date | Date | |
Discontinuation_Date | Date | Date new accounts were no longer accepted |
Run-off_Completion_Date | Date | Date all remaining accounts were closed or migrated |
Discontinuation_Reason | Dropdown | Low demand / Product redesign / Regulatory change / Merger / Other |
Regulatory_Notification_Date | Date | Date the regulator was notified of the product change |
Channel and Technology Availability
For multi-channel institutions, some savings products are available only through specific distribution channels or require different onboarding flows.
Use case: Recording channel availability and digital onboarding capabilities per product for technology planning and distribution management.
Example fields:
| Field name | Type | Notes |
|---|---|---|
Available_at_Branch | Boolean | |
Available_via_Agent | Boolean | |
Available_on_Mobile | Boolean | |
Available_Digitally | Boolean | Self-service digital onboarding available |
eKYC_Supported | Boolean | Whether electronic KYC can be used for onboarding |
Instant_Account_Opening | Boolean | Whether the account can be opened and funded in a single session |
External_System_Code | String (50) | Product code in a partner or external system |