When Admissions or any member of staff looks to merge family structures there is a chance when they merge sibling family into other sibling(s) they will replace a contact that has a billing account code. This isn't abundantly clear when the user is undertaking this action. Likewise, when a user goes to delete / merge mum/dad into Parents record there is a chance the user will accidentally delete a record that has a billing account code attached to it - billing account code ends up dissociated and in the ether.
Later down the line when Fee Billing is in full swing, I'd expect this won't be a problem as more data locks will be in place but while in the setup process with the 2 behaviours above there is a high chance of orphaned billing account codes (still retained by the deleted contact record).
We do not want to localise who can make changes to contacts to avoid this issue - this shifts workload onto fewer individuals which doesn't make sense. We have already done this to an extent.
My suggestion would be to include a backend check and then set an alert for users to be notified if they are perhaps going to create this orphaned situation. e.g., "Careful! You are about to delete a contact that has a Billing Account Code assigned to them. Please re-assign this billing account code if applicable before proceeding or please re-think this action"
