# Funding Over-commitment Notifications

Source: https://docs.astalty.com.au/guide/notifications/funding-over-commitment-notifications

> Alert selected staff when spent and booked charges take a Participant's Service over the funding available through a funding period.

Set up **Funding Over-commitment** notifications to alert selected staff when spent and booked charges take a Participant's Service over the funding available through a funding period. This notification type appears when funding periods are enabled for your account.

Only Admins can manage these notifications. Recipients can still receive an alert without access to the Notifications page.

## Create A Funding Over-commitment Notification

1. Open [**Notifications**](https://app.astalty.com.au/notifications), then choose **Funding Over-commitment** under **Plans & Services**.
2. Select **Create Notification**.
3. Choose at least one **Category**. The rule only applies to Services in the support categories you select.
4. Optionally add **Notification email content**. This appears in emails only.
5. Choose at least one recipient under **Notification recipients**.
6. Choose **Within Astalty**, **Email**, or both under **Notification methods**.
7. Select **Add Notification**.

New rules start with **Primary Coordinator**, **Service Coordinator**, **Within Astalty**, and **Email** selected. Review these defaults before you save.

## Choose Recipients

- **Primary Coordinator** includes the Participant's Primary Coordinator.
- **Service Coordinator** includes the coordinator of the Service that went over.
- **User Groups** and **Users** send the alert to the staff you select directly.

The **All Users** and **Support Worker** groups are not offered. Deactivated users are skipped, and someone selected in more than one way receives one alert per rule.

## When Alerts Are Sent

Astalty checks Services that have not ended. For a Service with a funding schedule, it adds spent and booked billable charges through each funding period and compares that total with the funding available through the period. A matching rule sends when a current or upcoming period goes over. Past funding periods do not trigger an alert. [Funding Utilisation](https://docs.astalty.com.au/guide/participants/ndis-plan/funding-utilisation#how-funding-periods-affect-what-is-left) explains how funding released in earlier periods carries forward.

For a Service without a funding schedule, Astalty compares spent and booked billable charges with the Service's full funding amount.

Booking and charge changes prompt a new check. Astalty also checks overnight at about 4:30am Brisbane time, which picks up changes such as a new funding period becoming current.

Each funding period is alerted once while it stays over. When one change puts several periods over, they are covered by a single alert. A later period that goes over sends its own alert, even while an earlier period is still over. A period that returns within funding and later goes over again is alerted again.

> **New rules do not send catch-up alerts**
>
> Creating a rule while a Service is already over does not send an immediate alert. The rule applies when a Service next enters an over-committed position.

## What Recipients See

In-app alerts and emails are titled **Funding Over-committed** and link to the Participant. They name the Service and the first alerted funding period that is still over, and count any later periods that went over at the same time, for example: *Spent and booked charges for Rhea's Community Access are $2,905.91 over the funding released for 1 Jan to 31 Mar 2027, and over in 3 later funding periods.* Recipients who can view support charges see how far the Service is over. Other recipients are told that it is over without seeing the amount.

Optional content from the rule appears in the email only. If none of the alerted periods is still over when a queued alert is sent, Astalty cancels it.

## Manage Notification Rules

The list shows each rule's categories, delivery methods, and recipients. Select a row to edit it, or use its actions menu to **Edit**, **Clone**, or **Delete** it.

You can create separate rules for different support categories, recipients, or delivery methods. Deleting a rule stops future alerts from that rule and does not remove alerts already sent.