Skip to main content

Element type added to payment cycle by mistake

In this article, we examine an issue where a no-cycle element was incorrectly assigned a payment cycle, affecting service user data.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

If you've picked up unwanted payments during an incomplete payment cycle because a worker misconfigured something, here's what you can try to work around the issue.

Could you test the following steps on a test instance:

  • Reject the invoices and complete the payment cycle.

  • Remove the cycle type from the element type provisions in the supplier config screens using the admin tool as usual.

  • Re-run the payment cycles so the new invoices don’t include those payments.

Since the payments tied to these commitments won’t have a cycle type anymore, they won’t show up on the front end unless you link them again. You can leave it there if that works for you. But if you’d prefer to have those payments removed, that would be a chargeable piece of work. If you’d like to go ahead with that, please raise a new case.

Did this answer your question?