Back-office Automation

Once a form is submitted it kicks off a dedicated workflow in IEG4’s RPO engine OpenProcess.

In terms of back-office updates* the SPD form can, depending upon the circumstance:

1. Terminate a current account

2. Transfer a person from an old account to a new account with the discount

3. Create a new person or people where someone/some people has/have moved in

4. Carry out a benefit change in circumstances where someone has moved out

5. Add/remove the Single Person Discount to/from the new account

6. Maintain the occupancy period to ensure this reflects the new occupants

7. Calculate the bill on the old account

8. Generate a bill on the old account

9. Transfer any credit due from one account to another

10. Calculate the bill on the new account

11. Generate a bill on the new account

12. Set up a Direct Debit Payment Method and Instalment Plan if a new account created and they wish to pay by direct debit

13. Adds any contact details for email/phone number to the party completing the form

14. Adds a notepad entry to each account affected to explain the updates made E.g.

“Council tax account 20000868320 has liable party with surname McMahon

Account 20000868320 terminated on 2020-03-31 and new account 2000119406 created

Person 654321 added as a liable party to account 2000119406 from 2020-04-01

Person ‘Claire McMahon' added as a new person. Reference: 987654 Person 987654 added as a liable party to account 2000119406 from 2020-04-01

No balance to transfer from 20000868320 Direct debit setup on account 2000119406"

10. Optionally the account can be suspended for a set period of time prior to billing to allow for QA

*The number of steps involved and functions available in the automation is dictated by the APIs available in the back-office application. E.g. NEC has more APIs than Capita/Civica, and the ability to transfer a credit from one account to another is not possible with the Capita One (Academy) Council Tax application.