Maturity, payouts, and renewal

Close of Business marks eligible schedule events Due. Processing an event then capitalizes interest, pays it to the Payout Account, settles maturity, or performs the Authorized renewal instruction.

Process a payout event

Open Operations → Fixed Deposits → Payouts, then open a Due or Failed event. With Update Fixed Deposit Schedule, select Process Event. remoteEaze uses an idempotency key, so retrying the same operation does not create a second financial result.

Periodic interest may be capitalized into the deposit Account or paid to the Payout Account according to the Contract instruction. At maturity, remoteEaze uses the maturity action and the active Authorized renewal instruction. Processing moves through Processing to Paid or Rolled; failures are shown as Failed for an operator retry after the cause is corrected.

Create a renewal instruction

On the Contract, open Renewal Instructions and select New Renewal Instruction. You need Create Fixed Deposit Renewal Instruction. Record the new tenure, interest and maturity instructions, and any optional note. The current implementation supports the prevailing rate at renewal.

Save the instruction as a Draft or Save & Submit. Updates to a Captured or Rejected instruction require Update Fixed Deposit Renewal Instruction. Submission and approval follow maker-checker and the configured L3 → L2 → L1 levels. Only an Authorized instruction is used at maturity.

Only one non-terminal instruction may exist for a Contract. The Contract must be Active and funded, and the maturity event must not already be Processing.

Maturity outcomes

• Payout settles principal and unpaid interest to the Payout Account and closes the Contract.
• Rollover applies the Authorized renewal terms, produces the successor deposit outcome, and marks the original Contract Rolled Over.

The event detail and Contract transaction history provide the resulting posting references.