3 minutes read
If a fee payer has been incorrectly added to a resident’s booking, you can archive them. Archiving removes the fee payer from the fee payer table view and ensures they are no longer involved in any billing-related activity.
Top tip: Archiving should only be used when a fee payer was added in error. If a fee payer has simply stopped funding the resident or their funding has changed, use the “Finalise” option instead and end the fee payers contribution
To archive a fee payer
- Go to the Resident Profile.
- Select the Booking tab.
- Click the Fee Payer tab.
- Locate the Fee Payer you would like to archive.
- Click the three-dot menu next to their name.
- Select Archive.
Once archived, the fee payer will be moved from the fee payer table to the archived table.
You will not be able to archive a Fee Payer if:
- They have an active invoice schedule, or
- They are associated with an active billing contract.
In these cases, first stop the invoice schedule or remove them from the contract before attempting to archive.
How to restore a fee payer
- Go to the Resident Profile.
- Select the Booking tab.
- Click the Fee Payer tab.
- Click the Archived toggle near Add Fee Payer.
- Find the Fee Payer you want to restore.
- Click the three-dot menu and select Restore Fee Payer.
- Enter the new weekly contribution and start date of their renewed funding.
When to restore a fee payer
A common reason to restore a Fee Payer is when one was archived in error.
For example, you may have initially believed the resident’s funding was private and archived a local authority fee payer. However, before the billing cycle began, you discovered that local authority funding was indeed correct, so you archive the private fee payer.
Later on, if the funding changes again and the private party becomes responsible, it’s more appropriate to restore the original private fee payer instead of creating a new one—this maintains accurate funding history and avoids duplication.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article