Fixed deposits
Fixed-deposit application, contract, maturity, and liquidation journeys.
A Fixed Deposit moves from a Customer request through workflow decisioning, approved terms, booking, funding, scheduled interest or maturity events, and, when applicable, renewal or early liquidation.
The operating journey
- Start a Fixed Deposit Application.
- Assign and progress the Application.
- Evaluate eligibility, quote the rate, and approve terms.
- Authorize, book, and fund the deposit.
- Use the Contract, schedule, transaction, and certificate views.
- Manage payouts, maturity, and renewal instructions.
- Request and process full or partial liquidation.
Access is permission-based
There is no single “Fixed Deposit officer” permission. Application capture, workflow decisions, Contract creation, funding, schedule processing, certificates, renewal instructions, and liquidation use separate entity/action permissions. Data-access scope and record state still apply.
Read the statuses correctly
Fixed Deposits use separate statuses for separate controls:
| Status | What it tells you |
|---|---|
| Application status | Whether the request is Draft, In Review, Approved, Offered, Rejected, Withdrawn, or Closed. |
| Approval status | Whether the Application, policy, instruction, or liquidation has completed its maker-checker approvals. |
| Contract status | Whether the booked agreement is Booked, Active, Matured, Closed, Rolled Over, Liquidated, or Cancelled. |
| Funding status | Whether the principal posting is Pending, Posted, Failed, or Cancelled. |
| Payout status | Whether one scheduled event is Pending, Due, Processing, Paid, Rolled, Failed, Cancelled, or Superseded. |
For example, an Application can be Authorized for workflow processing without yet being Approved for booking. A Contract can be Booked while its funding is still Pending. Always check the status for the operation you are investigating.
Begin with Before accepting the first Fixed Deposit if the company has not completed the necessary configuration.