Start a fixed-deposit application

A Fixed Deposit Application records the Customer's requested principal, tenure, interest instruction, maturity instruction, and settlement Accounts.

Access required

You need Create Fixed Deposit Application and data-access scope over the selected Customer and Accounts. Opening the saved record requires Read Fixed Deposit Application. L0 users also select the Company.

Before you begin

Complete Before accepting the first Fixed Deposit. Use an active, Authorized Customer and an Authorized Fixed Deposit Product.

Create the Application

Open Operations → Fixed Deposits → Applications.
Select Create Fixed Deposit Application.
On General, select the Company when shown, Fixed Deposit Product, Customer, principal, currency, requested start date, and tenure.
On Terms, choose whether interest is paid At Maturity or Periodic. For periodic interest, select the payout frequency.
Choose Payout or Rollover as the principal maturity action. A rollover also requires its amount mode.
On Accounts, select the Customer's Funding and Payout Accounts when they are already known.
Under Additional Information, enter a requested negotiated rate only when applicable and give the reason.
Select Save as Draft or Save & Submit.

The maturity date is derived from the start date and tenure. Product rules still validate the permitted principal, currency, tenure, interest payout, and maturity choices on the server.

Settlement Accounts

The Funding Account must use the Application currency, belong to the Customer, be active and Authorized, and allow debits. The Payout Account has the same ownership, currency, and status requirements and must allow credits. Both are mandatory when terms are approved, even if omitted from the first Draft.

The selectors show only Accounts that currently meet those operational rules. remoteEaze validates them again when approved terms are saved and immediately before booking, so an Account that later becomes blocked or loses its posting capability cannot silently enter the Contract.

Save or submit

Save as Draft creates a Captured / Draft Application. Save & Submit starts its maker-checker authorization, beginning at L3 when three levels are required. The operational workflow becomes available after the record is Authorized.

Continue with Progress a Fixed Deposit Application.