This article explains Ad Hoc Actions in Fease, covering how to configure and manage Promise-to-Pay reminders and Abandoned Payment reminders as automated follow-up processes separate from standard workflows.
Ad Hoc Actions are distinct workflows, separate from standard workflows, that can be automated to manage specific financial activities such as payment follow-ups. They operate as independent processes and are configured under Configuration > Workflows > Ad Hoc Actions.
The Promise-to-Pay (PTP) Ad Hoc Action allows schools to schedule automated follow-up reminders for specific payment arrangements made by accounts.
Enabling follow-up actions: To use follow-up actions for Promise-to-Pays, enable the feature under Configuration > Settings > Account Settings > Enable Add On Follow-up Actions.
Automation location: The Promise-to-Pay workflow is an Ad Hoc Action and can be automated under Configuration > Workflows > Ad Hoc Actions.
Reminder timing: Reminders are automatically sent 1 day before the payment date is due.
Visibility: Once a PTP reaches the deadline set during its creation, it will appear in the Accounts and To Do columns for tracking.
Column movement: Once a reminder is scheduled, the item moves through the workflow columns and remains there until the reminder has been sent and the specific payment has been received.
Success metric: The Success % is calculated based on whether payment is received within 15 days after the reminder is sent.
Administrator email alert: If a deadline passes without payment, the system automatically sends an email reminder to the administrator three days later to flag the outstanding activity.
Fulfilment: To officially close a Promise-to-Pay, an admin user must manually complete the fulfilment process within d6+ Finance.
Reminders on paused accounts: PTP reminders will continue to be sent even if the main account is paused. 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.
The Abandoned Payment Reminder is a specific Ad Hoc Action designed to prompt users who started a digital payment process but did not complete the transaction.
Goal: To remind a parent or guardian to return and finalise an incomplete payment.
Message focus: The reminder identifies that a payment session was started but not finalised, prompting the user to "finalise your payment at your earliest convenience."
Already paid: The message advises the recipient to disregard the reminder if the payment was already completed.
Automation location: Like the Promise-to-Pay, the Abandoned Payment Reminder is an Ad Hoc Action configured under Configuration > Workflows > Ad Hoc Actions.
Reminder timing: Automated reminders are sent 24 hours after the incomplete payment is created.
Go to Configuration > Settings > Account Settings and enable the Add On Follow-up Actions option. You can then set up the automation under Configuration > Workflows > Ad Hoc Actions.
The reminder is automatically sent 1 day before the payment date set on the Promise-to-Pay record.
Yes. PTP reminders are sent regardless of whether the account is paused. Pausing stops standard collection letters but does not affect Ad Hoc Action reminders tied to a specific payment arrangement.
The Success % measures whether the payment is received within 15 days of the reminder being sent.
The reminder is sent automatically 24 hours after an incomplete online payment session is created.
The system automatically sends an email alert to the administrator three days after the missed deadline to flag the outstanding activity.
Last updated: May 2026 | Version 1.0