We've replicated this issue locally by having someone on a nil assessment with relevant purchases linked to auto-contribution elements. When we ended the provisions via the care package screens, the auto-contribution elements remained current.
The only way to end those auto-contributions at this point is by using the purchase workstep instead of the care package screens to end services. After that, you can generate the contributions via the button. Once you go back into the care package screens, it will reflect the changes you want.
For non-nil assessment service users, ending services through the care package screens will also end the auto-contribution elements as expected. However, we recommend always making changes to the care package via workflow.
For the few customers using the care package screens to perform 'Unplanned end' of services, you can report why services are ending via the dropdown options, which can’t be done in the purchase steps. If you review your processes, you could probably achieve the same reporting outcome in the purchase step by configuring an optional form with a reportable end reason field.
So, when you use the purchase screens in the purchase step to end the service, you could bring up an optional form to capture the reason and then map this to a local report.
Auto-Contributions remaining current when ending services in care package screens
In this article, we explain why a nil-assessed service user may still have active auto-contribution elements after services are cancelled.
Y
Written by Yusef Abulaynain
Updated over 5 months ago