Standing Instructions

Holds recurring automated payment mandates (mfi.standing.instruction) - scheduled transfers, sweeps and repayments authorised to run without manual intervention. Each instruction defines the source, destination, amount and schedule, governed by approval before activation. Governance reviews them to ensure recurring movements remain authorised and current.

Workflow

Open Standing Instructions under Governance.
Create an instruction with source, destination and amount.
Set the frequency and start/end dates.
Obtain approval to activate the mandate.
Suspend or amend instructions that are no longer valid.

Fields reference

Every field on this screen, drawn from the live data model.

Field	Type	Required	Description
Dst Account `dst_account_id`	Link → mfi.savings.account	—	Required for "own" + "member" rails.
Dst Phone `dst_phone`	Text	—	Required for "mpesa" rail.
End Date `end_date`	Date	—	Leave blank for no end date.
Name `name`	Text	Yes	Name
Member `member_id`	Link → mfi.member	Yes	Member
Src Account `src_account_id`	Link → mfi.savings.account	Yes	Src Account
Rail `rail`	Choice: Between own accounts, To another member, PesaLink — external bank, M-Pesa wallet	Yes	Rail
Amount `amount`	Money	Yes	Amount
Frequency `frequency`	Choice: Daily, Weekly, Monthly, Quarterly	Yes	Frequency
Start Date `start_date`	Date	Yes	Start Date
Next Run Date `next_run_date`	Date	Yes	Next Run Date
State `state`	Choice: Active, Paused, Completed (end date reached), Cancelled	Yes	State
Has Message `has_message`	Yes/No	—	Has Message
Recipient name (PesaLink) `dst_counterparty`	Text	—	Recipient name (PesaLink)
Recipient account number `dst_account_no`	Text	—	Recipient account number
Recipient bank `dst_bank_id`	Link → mfi.bank	—	Recipient bank
Currency `currency_id`	Link → res.currency	—	Currency
Memo `memo`	Text	—	Memo
Last Run Date `last_run_date`	Date	—	Last Run Date
Last Run Ok `last_run_ok`	Yes/No	—	Last Run Ok
Last Run Message `last_run_message`	Text	—	Last Run Message
Runs Count `runs_count`	Number	—	Runs Count
Failures Count `failures_count`	Number	—	Failures Count
Company `company_id`	Link → res.company	—	Company

Actions & buttons

Buttons available on this screen and what they do:

Pause
Resume
Cancel

Status lifecycle

Records on this screen move through these statuses:

Active → Paused → Completed (end date reached) → Cancelled

Notes & rules

Automates recurring transfers, sweeps and repayments.
Activation requires governance approval.
Schedule defines when each run executes.
Periodic review confirms mandates remain authorised.

Technical model: mfi.standing.instruction · Record: Standing Instruction (scheduled recurring payment)