Deleting Support Charges

Overview

Charges are removed from a support on its Finance tab. If the charge was applied across a repeating support, Astalty asks which occurrences in the series the removal should apply to — including occurrences that have already happened — and then tells you exactly what it removed and what it left alone.

This matters most when you are cleaning up a duplicate charge. If the duplicate was created part way through a series, the earlier dates need clearing too, otherwise they keep the extra charge and it reappears the next time those dates are invoiced.

Deleting a charge

1. Open the support and go to the Finance tab.
2. Find the charge in the table and select the three dot menu at the end of its row.
3. Select Delete.
4. Confirm with Delete.

For a charge that only ever applied to this one support, that is the whole job — the charge is removed and nothing else changes.

Choosing occurrences on a repeating support

A charge that was added across a repeating series carries a 🔁 icon next to the Charge Item name — hover over it to see "This is a recurring charge." Charges get this marker when they were created with this support and following or this and selected following.

Deleting one of these opens the Delete Recurring Charge panel after you confirm. It lists every occurrence in the series, past and future, so you can clear the charge from dates that have already been delivered as well as ones still to come.

• The occurrence you started from is ticked and can't be unticked. It is marked (Current), or (Current - Past) if that support has already finished.
• Tick any other occurrences the charge should be removed from.
• The checkbox in the table header ticks or clears every occurrence that can be changed.
• The Select dropdown offers day-of-week shortcuts such as Every Monday, which is handy on a series that runs on more than one day. It appears once there are enough occurrences to make the shortcut useful.
• The line beneath the table keeps a running count, and the button reads Delete 3 Charges so you can see the size of the change before committing to it.

Only occurrences you have access to are listed, so the panel reflects the supports you can see.

Occurrences that can't be changed

Some occurrences are past the point where a charge can be pulled off them. These are still listed so you can see them, but they are highlighted and their checkbox is disabled, with a padlock chip giving the reason:

To remove one of these, deal with the invoice or batch first — see Voiding Invoices and Invoice Batches.

What Astalty reports back

Once the removal runs, an alert appears above the charges table summarising the outcome:

• If everything you selected was removed, the alert is green and reads "Removed 3 charges."
• If some occurrences were locked, the alert is amber and adds "2 occurrences were left unchanged.", then lists each one with its date and reason — for example "Monday 10/08/2026 - Invoiced".

Read this before moving on. It is the confirmation that the dates you expected to be cleared actually were, and it names the ones you still need to follow up. Close the alert with the × when you are done with it.

Charges Astalty creates from the support's hours

The automatically created hourly charge on a repeating support isn't part of a charge series, so it doesn't use the panel above. Deleting it offers the current support and the supports that follow it, and does not list occurrences that have already happened. On a group support, it offers the group supports in the series instead.

Keeping track of what changed

Charge removals are recorded against the support, so you can confirm after the fact who removed a charge and when. Open the support, select Actions, then the three dots, then Audit Trail — see Support Audit Log.

Related pages

• Additional Charges — adding a charge to a direct or group support, and applying it across a series.
• Managing Manual Charges — controlling exactly what a support bills.
• Service Dates on Support Charges — correcting the day a charge sits on instead of deleting it.
• Recurring Shifts — setting up and managing repeating supports.