Skip to content
English
  • There are no suggestions because the search field is empty.

How to Track PAC (Pre-authorized contribution plan) Requests 

Learn how to monitor the progress of PAC requests, understand each step, and resolve rejected tickets.

After submitting a Create, Modify or Stop PAC 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 Pre-Authorized Contribution Ticket

You can find your submitted PAC 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)

PAC Workflow and Pipeline Stages

Below is the typical workflow a PAC 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. 

Create a PAC 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 PAC creation request and preparing updates.

    • SLA: Within 24 hours

    • Next Step: Moves to Transmitted upon submission.

    Action Item: Transmitted 

    • Assigned to: Money Movement Team

    • What’s happening: Submitting PAC creation to the custodian system.

    • SLA: 1–2 business days

    • Next Step: Moves to Completed upon confirmation.

    Stage: Completed

    • What’s happening: Ticket is closed and finalized. No further action required.

    Modify a PAC 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 PAC 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 PAC 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 PAC 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 PAC 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 PAC 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 PAC 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 PAC Requests

        If your request is rejected, the ticket will clearly indicate why. Common rejection reasons include:

        • Request submitted outside the minimum timeframe ( PAC creations and modifications must be submitted 7 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 (PAC modifications can only apply to the next scheduled payment, not multiple future payments)
        • Incorrect Banking (the banking information provided is invalid, incomplete, or does not match the client’s records)

        If your request was rejected, resolve the noted issue, then submit a new PAC request.

        Tracking Your Ticket & Next Steps

        Monitor progress regularly through pipeline stages outlined above. If you’re responsible for actioning tickets, see:

        • How to Action Tickets