Agenda item

Section 24 Report


The Section 24 Report was presented by the Engagement Lead, Grant Thornton. It was explained that, as auditors, Grant Thornton had powers under the Local Audit and Accountability Act 2014 to make, if necessary, statutory recommendations under Section 24 of the Act. The Committee was informed that following discussions with colleagues it was the judgment of Grant Thornton that the issues outlined within the report warranted the issuing of statutory recommendations under the Act.


The background to the statutory recommendation was outlined and it was reported that a new financial ledger system had been implemented in February 2021. However, there had been significant challenges in respect of the cash receipting module in the new system.


Members were reassured that Officers had been working with the suppliers of the Enterprise Resources Planning (ERP) system, Tech1, and that the cash receipting module issues had been resolved and this module was now live. However, despite the progress that had been made in the cash receipting module the delays experienced had impacted on the delivery of the publication of the 2020/21 Accounts, which were due by the end of July 2022. The Council had also fallen behind in the finalisation of the 2021/22 in year monitoring and other Government returns, such as Revenue Outturn and Capital Outturn.


It was highlighted that the Council had recognised these issues and in Q1 of 2022/23, planning had begun for the 2020/21 financial audit, which was when the issues highlighted above had come to the attention of the auditors. The Engagement Lead reported that Grant Thornton took a consistent approach to issuing Section 24 notices across public bodies it audited with those local bodies which had not submitted their 2020/21 Accounts being issued with Section 24 notice. The Engagement Lead added that although resolution to the issues with cash receipting had now been reported, and assurances provided about reconciliation of information from the old to the new ledger system, Grant Thornton could not give their opinion until the audit of the 2020/21 Accounts had been investigated and concluded.


The Interim Director of Finance addressed the Committee and explained that issues with cash receipting module had been reported to Members on a number of previous occasions and that these issues had now been resolved. The Committee were informed that there had been a severe loss of Council staff, resulting in only four members of the finance team remaining at one point in financial year 2020/21. Following two recruitment drives during 2021/22, the Finance team were now almost up to full capacity again. It was also noted that the closure of 2021/22 Accounts for Rubicon, completed earlier in the financial year, provided useful learning points for the work on the Redditch Council financial statements which should mean that once work on the 2020/21 Accounts was finished, the 2021/22 Accounts should be finalised a lot more quickly.


Following the presentation, a number of questions were asked by Members which included the following:


·       When was the Section 24 notice issued? – It was confirmed that the Section 24 notice had been issued on 31st October 2022 and the timeline for consideration of the statutory recommendation by the Council was within one month of issue. The recommendation was due to be considered by Full Council on 14th November 2022.

·       Would compensation be paid by the supplier of the Enterprise Resources Planning (ERP) system, Tech1, in relation to the faults with the cash receipting module? – Officers explained that overall the new ERP system worked to a very high standard and was more advanced than other systems on the market, apart from the cash receipting module which was jointly designed by the Council and the supplier of the system, Tech1. Furthermore, the ERP system and its modules were originally implemented as one entity for all three organisations (Redditch Council, Bromsgrove Council, Rubicon) which was the decision taken by Council Officers and which had also contributed to the magnitude of reconciliation work required. It was also noted that cash receipting represented the most difficult part of the system where least expertise was available. Due to these factors, the Council would not claim for any compensation from the supplier of the ERP system.

·       How much did the ERP system cost and what had been the total cost to date? – Officers explained that they did not have the information at the meeting and undertook to provide this information to Members.

·       When could the Council expect to no longer be under Section 24? – It was explained that no official statement would be issued by auditors confirming that Section 24 no longer applied to the Council. Rather it was for the auditors to be satisfied that Section 24 was no longer applicable to the Council based on evidence of progress made in addressing the statutory recommendations, for example with evidence that clear bank reconciliation was in place. It was suggested that Officers could provide a commentary on the Council’s progress in its Section 24 position at a future Committee meeting.

·       What were the issues with cash receipting module? – Jointly with Tech 1, the Council was the first implementer of the cash receipting module, and no other local authority had implemented the Tech 1 solution. It was explained that the issue with cash receipting centred around the fact that as the system recognised all three organisations under one entity, a significant amount of transactions was coded incorrectly or assigned to the wrong entity. In those cases, Officers had to manually unpick the transactions and reconcile payments to the cash receipt journal in order for the transaction to be recorded under the correct entity. It was highlighted these issues were now being rectified.

·       What were the financial implications of the Council being issued with Section 24 notice? – It was explained that there would be an impact in terms of a higher audit fee if auditors identified issues with incorrect reconciliation when auditing 2020/21 Accounts, which required additional work to correctly identify transactions. There would be no other cost associated with the Section 24 notice.

·       When could Members expect the 2020/21 Accounts to be audited? – It was explained that the audit work on the Accounts was not expected to begin until January 2023 at the earliest. Once the Accounts had been audited the Audit opinion would be published on the Council’s website and subsequently would be considered by the Committee, which could decide on whether to recommend to the Council to accept these accounts or not.


Members questioned if there had been any ‘Exit Interviews’ carried out with staff who had left and whether during these interviews the ERP system was raised as an issue.  Officers confirmed that they did not have the exact information in respect of the number of Exit Interviews carried out for those members of the Finance Team who had left during 2020 until the end of 2021. However, it was confirmed that all Council staff were offered an exit interview, although not all chose to take up the offer. In addition to this, it was noted that potentially the new skills that had been acquired by those members of staff who were trained on the new system were desirable to other employers in the work marketplace and this could have potentially been a reason why more staff than was usual left in a very short space of time.


Members queried whether it could have been possible to foresee the issues with the cash receipting module and whether risk assessment had been undertaken prior to implementation of the system. In response, it was highlighted that the previous financial system was outdated, and the cash receipting was being supported by an older version of Civica. Initially it had been agreed that an updated version of the Civica system would be used for cash receipting.  However, after the tender process the project team highlighted that Tech1 could offer assurances that a cash receipting solution could be provided as part of the new system. It was added that a project board had been in place for the implementation of the new system, and notes of the project board indicated that the system offered by Tech1 passed all the necessary tests.


It was reiterated that the loss of so many staff who originally implemented the system could not be expected or mitigated against and this led to a loss of expertise and the need to train an entirely new team which did not initially had a sufficient level of proficiency in the new ERP system.


Officers also highlighted that staff turnover was very high in the 2020/21 financial year and necessitated large amount of spending on agency staff which was not sustainable. However, provisions were now being made through implementing a new recruitment process and preparation of a draft workforce strategy which would be considered by the Executive Committee in December 2022 and would provide an action plan for the Council in terms of staff retention. It was highlighted that staff retention remained an issue across the local government sector.


The Portfolio Holder for Finance and Enabling was invited to comment and in doing so stated that she had been regularly updated by Officers on the problem with cash receipting ever since assuming the position of a portfolio holder in May 2022 and thanked the Interim Section 151 Officer and his team for recognising the issues and dealing with them. She expressed confidence that the team would be able to finalise the draft Statement of Accounts 2020/21 before the extra meeting of the Committee in December.


The Chair concluded the discussion expressing confidence that based on the information heard by the Committee most issues highlighted by auditors in Section 24 were now under control.


On being put to the vote it was




the Section 24 Statutory Recommendation is accepted, and that Council review the recommendation, endorse the actions included in the management responses which form the rectification process required as per legislation.

Supporting documents: