What are Ad Hoc Actions?

What are Ad Hoc Actions?

Ad Hoc Actions: Payment Reminders

Ad Hoc Actions are distinct workflows, separate from standard Workflows, that can be automated to manage specific financial activities like payment follow-ups.


Promise to Pay Reminders

The Promise to Pay feature allows schools to schedule follow-up actions for specific payment arrangements made by accounts.


Configuration and Enabling

  • Enabling Follow-up Actions: To use follow-up actions for Promise to Pays, the school must enable this feature under: Configuration > Settings > Account Settings > Enable Add On Follow-up actions

  • Workflow Type & Automation: The Promise to Pay workflow is an Ad Hoc Action. It functions similarly to a standard Workflow action but operates as a separate process. It can be automated under: Configuration > Workflows > Ad Hoc Actions.

  • Automatically send Promise to Pay reminders 1 day before the payment date is due.


The Reminder Process
  • Visibility: Once a Promise to Pay reaches the deadline set during its creation, it will appear in the “Accounts” and “To Do” columns for tracking.

  • Movement through Columns: Once a reminder is scheduled, the item moves through the workflow columns. It remains in the workflow until the reminder has been sent and the specific payment for that promise has been made.

  • Success Metric: The Success % is calculated based on whether the payment is received within 15 days after the reminder is sent.

  • Administrator Email Reminder: If a deadline passes without payment, the system automatically sends an email reminder to the administrator three days later to alert them of the outstanding activity.


Fulfilling and Paused Accounts
  • Fulfillment: To officially close a Promise to Pay, an admin user must manually complete the fulfillment process within d6+ Finance.

  • Account Pausing and Reminders: Promise to Pay reminders will continue to be sent even if the main account is paused. This is because schools typically pause accounts to stop standard collection letters while a payment arrangement is active, but still require the system to follow up on that specific arrangement.

  • Best Practice for Pausing: It is recommended to pause the account at least 7 days after the Promise to Pay date. This provides a grace period for the parent to make the payment and gives the school sufficient time to reconcile the transaction.


Abandoned Payment Reminder

This is a specific Ad Hoc Action designed to prompt users who started a digital payment process but failed to complete the transaction.


Purpose and Content
  • Goal: To remind a user to return and finalize an incomplete payment.

  • Message Focus: The reminder identifies that a payment session was started but not finalized.

  • Standard Message: It prompts the user to "finalise your payment at your earliest convenience" and advises them to "kindly disregard this reminder" if the payment was already completed.


Automation Location
  • Workflow Type & Automation: Like the Promise to Pay, the Abandoned Payment Reminder is an Ad Hoc Action and can be automated under: Configuration > Workflows > Ad Hoc Actions. Automatically send a payment reminder to parents who have started the payment process online, but did not complete it. 

  • Automated reminders are sent 24 hours after payment is created.

    • Related Articles

    • Promise to Pay Management

      Promise to Pay (PTP) Management What is the purpose of a Promise-to-Pay (PTP)? A PTP is a record used for tracking commitments made by a parent or guardian to the school. It ensures a clear record of the amount they promised to pay and the specific ...
    • How do cashless payments and the Pay Now button work?

      This article explains how the cashless payment integration works in Fease, enabling parents to pay outstanding fees directly from their statement via the Pay Now button. Fease > Configuration > Settings > Cashless Integration How does the cashless ...
    • How do I manage unfulfilled payment arrangements in Fease?

      This article explains how to identify and handle broken payment promises in Fease, including how to resume follow-ups and escalate accounts where arrangements have not been met. Fease > Dashboard / Reports > Promises to Pay How do I identify broken ...
    • How do I add follow-up actions to a workflow?

      This article explains how to add, configure, and customise individual follow-up actions within a Fease workflow, including setting age brackets, action types, recipients, and templates. Fease > Configuration > Workflows > [Workflow] How do I add a ...
    • How do I use the Payments and Promises to Pay Reports?

      This article explains how to use the Payments Report and Promises to Pay Report in Fease to track cashless payments and monitor payment commitments made by parents. Fease > Reports What does the Payments Report show? Access via Reports > Payments ...