- Knowledge Base
- Revenues Forms
- Revenues Process Orchestration (API's)
-
Events
-
Customer Portal
-
Customer Engagement Centre (Previously known as CSVu)
-
General Form Guidance
-
Editing Forms
-
Benefit Forms
-
Revenues Forms
-
'How to...' Sessions
-
Health (CHC)
-
Technical Area
-
Open Process
-
Forms
-
Blue Badge and Concessionary Travel
-
Waste Services
-
Awards and Grants
-
Social Care Financial Assessments
-
IEG4 Team Updates
-
BACAS
-
Tender Responses - General
-
Internal Process Guides
-
Public Protection
-
Built Environment
Capita Revenues Integration - 1.2
This release relates specifically to the integration engine for Council Tax automation with the Capita back office council tax application.
Two changes have been made:
1) Some councils have multiple addresses associated with a given account, which was unexpected and meant the oldest property for an account was being shown when the customer authenticated themselves in any Council Tax form.
We now understand that some Capita using councils do not create a new account when a person moves to a new property in the area and the cause of this.
So now, when authenticating / checking the customer's details, we sort the addresses we get back to find the most recent one.
2) On Single Person Discount, Capita behaves unusually if the name of the person does not EXACTLY match that held. I.e. if John MCMAHON was in the form but the back office has JOHN MICHAEL MCMAHON it would fail to integrate.
To rectify this we now use the details held in the back office when we push the SPD data into the Capita system.