Overview and rates
Fixed Term Deposit overview
Understand how Flinq manages a deposit from request to maturity.
Written by Katrin Erb Updated Published Flinq keeps a Fixed Term Deposit (FTD) request, approvals, bank instructions, confirmation, supporting evidence and maturity decision connected in one office-level record.
The Fixed Term Deposit lifecycle
An internal request starts as Awaiting Approval when the office requires a separate approval, or as Requested when it does not. A portal request first enters Portal Submitted for an authorised internal reviewer to complete.
The Fixed Term Deposits list brings the operational queue, status totals and records requiring action together.
Downloading the bank instruction for an approved or directly requested deposit records that it has been sent to the bank and moves it to Pending Confirmation. Confirmation records the bank-agreed dates, amount, rate, funding account and interest. The deposit then becomes Live when its effective value date arrives.
As maturity approaches, Flinq marks the deposit Maturing according to the office configuration. The final route is settlement, full rollover, partial rollover or an early break.
Requested, indicative and confirmed values
Requested values describe the intended placement. An indicative rate supports comparison but is not a commitment or bank confirmation. When a user with confirmation permission re-keys the bank-agreed values, Flinq treats those confirmed values as effective for dates, amount, rate, interest and funding-account reporting.
Roles and separation of duties
A user with Create FTDs can prepare a request and record maturity instructions.
A user with Approve FTDs can approve an Awaiting Approval request, but cannot approve a request they created or submitted through the portal.
A user with Confirm FTDs can record the values confirmed by the bank.
A user with Review portal FTD requests can complete or reject a portal submission.
Document viewing, creation and deletion follow separate FTD permissions.
Portal users
Client portal access is separate from access to the internal Flinq application. An authorised administrator can invite a portal user, resend a pending invitation or revoke portal access without assigning an internal system role. Portal permissions and the office's portal-request feature still determine which actions the user can perform.
Action-required indicators
The FTD navigation badge and Show Requiring Action filter identify portal submissions, approval requests, unconfirmed requests whose value date has passed and deposits whose effective maturity date has passed. Treat the indicator as an operational queue and open each record to see the available action.
Records and audit evidence
Each deposit has an FTD ID, record timeline and optional supporting documents. Downloaded bank or internal instructions, approvals, confirmation values, portal review data, cancellation reasons, break calculations and rollover lineage remain associated with the deposit according to your permissions and retention process.
Keep reading