How to Track RIF and LIF (Registered Income Fund and Life Income Fund) Requests
Learn how to monitor the progress of RIF or LIF requests, understand each step, and resolve rejected tickets.
After submitting a Modify or Stop RIF/LIF request, a ticket is created in the Plan Pipeline. Use this guide to effectively track each stage, understand the workflow, and quickly address rejections.
How to Find RIF or LIF Tickets
You can find your submitted RIF or LIF ticket in two places:
- The right-side panel under Tickets on the Client’s CRM Contact Record
- In the Plan Pipeline (CRM → Tickets → Plan Pipeline)
RIF or LIF Workflow and Pipeline Stages
Below is the typical workflow a RIF or LIF ticket follows, outlining the various stages of the process, the roles responsible for each task, the specific actions being taken at each step, and the expected timelines for completion.
Modify a RIF or LIF Workflow and Pipeline Stages
Stage: In Review
Action Item: Portfolio Manager Review
- When required: If submitted by someone other than the assigned Portfolio Manager.
- Assigned to: Portfolio Manager
-
What’s happening: Ensuring suitability of instructions.
- SLA: Same-day
- Next Step: Moves to Pending Action (In Process) upon approval.
Stage: In Process
Action Item: Pending Action
-
Assigned to: Money Movement Team
-
What’s happening: Reviewing RIF or LIF modification request and preparing updates.
-
SLA: Within 24 hours
-
Next Step: Moves to Transmitted upon processing.
Action Item: Transmitted
-
Assigned to: Account Administration
-
What’s happening: Submitting RIF or LIF modification to the custodian system.
-
SLA: Same-day
-
Next Step: Moves to Completed upon successful transmission.
Stage: Completed
- What’s happening: Ticket is closed and finalized. No further action required.
Stopping a RIF or LIF Workflow and Pipeline Stages
Stage: In Review
Action Item: Portfolio Manager Review
- When required: If submitted by someone other than the assigned Portfolio Manager.
- Assigned to: Portfolio Manager
-
What’s happening: Ensuring suitability of instructions.
- SLA: Same-day
- Next Step: Moves to Pending Action (In Process) upon approval.
Stage: In Process
Action Item: Pending Action
-
Assigned to: Money Movement Team
-
What’s happening: Reviewing RIF or LIF stop request and preparing instructions for transmission.
-
SLA: Within 24 hours
-
Next Step: Moves to Transmitted upon processing.
Action Item: Transmitted
-
Assigned to: Money Movement Team
-
What’s happening: Submitting RIF or LIF stop instructions to the custodian system.
-
SLA: Same-day
-
Next Step: Moves to Completed upon confirmation.
Action Item: Completed
-
Assigned to: Money Movement Team
-
What’s happening: Final internal confirmation of the RIF or LIF stop.
-
SLA: Same-day
-
Next Step: Moves to Completed stage.
Stage: Completed
- What’s happening: Ticket is closed and finalized. No further action required.
Handling Rejected RIF or LIF Requests
If your request is rejected, the ticket will clearly indicate why. Common rejection reasons include:
- Request submitted outside the minimum timeframe ( RIF or LIF modifications must be submitted 14 calendar days before the first/next payment date)
- Duplicate ticket submitted (a similar request already exists or is pending)
- Modify amount for more than one payment ahead (RIF or LIF modifications can only apply to the next scheduled payment, not multiple future payments)
- Elected amount greater than maximum (the amount chosen for withdrawal exceeds the maximum allowable limit for a LIF under pension legislation)
- Minimum amount already paid out (the client has already received the required minimum payment for the year, so additional "minimum" withdrawals are not permitted)
- Tax Rate for Minimum not provided (the tax rate to apply to the minimum annual withdrawal amount was not specified, and is required to process the payment)
If your request was rejected, resolve the noted issue, then submit a new RIF or LIF request.
Tracking Your Ticket & Next Steps
Monitor progress regularly through pipeline stages outlined above. If you’re responsible for actioning tickets, see: