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 payment arrangements?

• Dashboard: The Promise-to-Pays section shows all outstanding promises, with unfulfilled ones prioritised at the top.

• Promises to Pay Report: Under Reports, gives a detailed list with due dates and fulfilment status.

What should I do when a promise is broken?

1. Check the account: Open the account detail view to confirm no partial payment was made.

2. Resume follow-ups: If the account was paused while the arrangement was active, un-pause it so workflow actions can resume.

3. Add a note: Record that the arrangement was not honoured, including the original promise date and amount. This creates an audit trail.

4. Consider escalation: If the account is already at an advanced workflow stage, proceed to the next legal step (Letter of Demand or Section 41).

Where do I manage promise-to-pay records?

Promise-to-pay records must be managed and marked as complete or broken within d6+ Plus Finance. Fease displays promise data but does not allow direct editing of promise records.

Frequently asked questions

Can I mark a promise as broken directly in Fease?

No. Promise-to-pay records must be managed in d6+ Plus Finance. Fease displays them but does not allow direct editing.

Will workflow actions automatically resume if a promise is broken?

Only if the account was previously un-paused. If the account was paused while the arrangement was active, you need to manually un-pause it before workflow actions will resume.

Should I send a Letter of Demand immediately after a broken promise?

This depends on the account's current workflow stage and your school's policy. Review the account history and consider whether an additional reminder or direct escalation is more appropriate.