Deposit Product Flags

Deposit product flags are configurable switches and values that control how a deposit product behaves. They let administrators build product variants without creating separate custom workflows for every product.

Use this guide when configuring savings, current, fixed-deposit, wallet, funding, or community-finance deposit products.

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Deposit Products	Deposits -> Setup -> Products	Configure product classification, inherited defaults, overrides, runtime preview, and approval state.
Pricing	Administration -> Financial Setup -> Pricing	Maintain fees, charges, penalties, or interest-linked pricing where enabled.
GL Posting Rules	Accounting -> Setup -> GL Posting Rules	Confirm interest, fee, tax, and balance postings are mapped before live use.
Deposit Accounts	Deposits -> Operations -> Accounts	Test account opening, transactions, interest, restrictions, and status behavior against product flags.

What Product Flags Control

Flags can affect:

• Account opening requirements.
• Customer access channels.
• Transaction limits.
• Minimum and maximum balances.
• Interest calculation and payout.
• Fixed-deposit maturity and rollover.
• Withdrawal restrictions and penalties.
• Dormancy rules.
• Pricing and fee behavior.
• GL posting behavior.
• Governance requirements such as joint signatories.

The exact flags available depend on the selected product classification.

How Defaults Work

Deposit flags are resolved in this order:

1. Product override: values configured directly on the product.
2. Product type default: defaults inherited from the selected product type.
3. Catalog default: platform default where no product-specific value exists.

This means a product does not need every flag manually configured. Administrators usually start from the product type defaults, then override only the behavior that makes this product different.

Product Classification

When creating a product, first choose the product classification.

Common classifications include:

• Fixed deposit.
• Savings account.
• Savings plan.
• Current account.
• Stored value or wallet account.
• Funding account.
• Community finance account.

The classification determines which flag groups appear in the form.

Main Flag Groups

Group	What it controls
Limits	Balance limits, transaction caps, and monthly count limits.
Access	ATM, mobile, online, cheque book, card, branch, and similar access options.
Overdraft	Whether negative balances or overdraft limits are allowed.
KYC	Customer eligibility, identity, residency, employment, age, and verification controls.
Interest	Whether the product earns interest, how it is calculated, and how it is paid.
Fixed Deposit	Tenure, maturity, early withdrawal, penalties, rollover, and payout behavior.
Savings Plan	Goals, installments, missed payments, and plan discipline.
Community	Group-account, pooled-fund, or rotation behavior.
Governance	Joint operation, signatories, and approval-style controls.
Dormancy	Inactivity detection and dormancy treatment.
Integration	Pricing, GL, wallet, sweep, and channel-linked behavior.
Regulatory	Tax, certification, insurance, and compliance attributes.
Trigger Events	Which account events should trigger pricing or posting follow-up.

Creating Or Editing A Product With Flags

Use the product form:

1. Select the product classification.
2. Review the flags that load for that classification.
3. Keep inherited defaults where they match the intended product.
4. Override only the flags that need product-specific behavior.
5. Review the runtime preview if shown.
6. Save the product.
7. Test opening or transacting on an account before publishing the product widely.

Runtime Preview

Where available, the product form shows a runtime preview of enabled behavior.

Use the preview to confirm:

• Whether the product is interest-bearing.
• Which channels are available.
• Whether fixed-deposit rules apply.
• Whether pricing, GL, or workflow triggers are enabled.
• Whether limits or restrictions are active.

The preview is a review aid, not a substitute for testing the product workflow.

Interest Flags

Interest flags are especially important because they affect customer balances and finance reporting.

Review:

• Whether the product earns interest.
• Whether the rate is fixed, tiered, indexed, or otherwise configured.
• Whether interest is accrued, capitalised, paid out, or withheld.
• Whether withholding tax applies.
• Whether the payout frequency matches the product terms.

Do not publish an interest-bearing product until finance confirms the accounting and tax treatment.

Fixed-Deposit Flags

Fixed-deposit flags define how term deposits behave.

Review:

• Tenure and maturity settings.
• Early withdrawal policy.
• Penalty behavior.
• Rollover options.
• Whether interest is paid periodically or at maturity.
• Whether principal and interest return to the same account or a nominated account.

These settings should match the customer-facing product terms.

Limit And Access Flags

Limit and access flags control operational risk.

Review:

• Minimum opening balance.
• Minimum operating balance.
• Maximum balance.
• Per-transaction limits.
• Monthly transaction counts.
• Branch, mobile, online, card, or cheque access.

Do not enable access channels casually. Each enabled channel can affect operational controls, fees, reconciliation, and customer support.

Governance And KYC Flags

Governance and KYC flags control eligibility and account operation.

Review:

• Required KYC level.
• Whether biometric or enhanced verification is needed.
• Residency or age restrictions.
• Whether joint signatories are allowed or required.
• Whether special approval is needed for onboarding or transactions.

These settings should align with policy, not just convenience.

GL And Pricing Implications

Some flags affect fees, pricing, interest, and GL posting.

Before publishing the product, confirm:

• Pricing rules exist for enabled fee triggers.
• GL setup exists for interest, fees, taxes, and product balances.
• Any event-triggered pricing behavior is intentional.
• Finance has reviewed the product's accounting impact.

If pricing or GL setup is incomplete, transactions may be blocked or require correction later.

Common Mistakes To Avoid

• Do not override every flag manually when the product type default already fits.
• Do not enable an access channel without confirming operational controls.
• Do not publish a fixed-deposit product without validating maturity and early withdrawal behavior.
• Do not treat the runtime preview as final testing.
• Do not change flags on a live product without understanding existing accounts that use it.

Related Pages

• Deposit Products
• Deposit Accounts
• Pricing
• GL Posting Rules