What does an assurance provider test about the system rather than the numbers?
16 November 2026 · 28 min read · Mian Khubaib Jim

ISSA 5000 applies from 15 December 2026. 25 of the 93 ISO 27001 Annex A controls sit inside the three IT processes an assurance provider tests
General IT controls are the part of a sustainability assurance engagement that preparers rarely plan for and practitioners increasingly ask about. This paper asks one question. When an assurance provider examines the system rather than the figures what exactly is it required to examine and what can a portfolio do before the engagement opens? The answer comes from the standard that takes over in six weeks. ISSA 5000 applies to sustainability information reported for periods beginning on or after 15 December 2026 and ISAE 3410 is withdrawn from the same date [1] [7]. Its section on the system of internal control runs from paragraph 113 to paragraph 121. Three of those nine paragraph numbers apply identically whether the engagement is limited or reasonable and only one 119R exists for reasonable assurance with no limited counterpart [1]. The requirement that bites hardest is not in that section at all. Paragraph 91 asks the practitioner to evaluate whether information produced by the entity is reliable enough to use including evidence of its accuracy and completeness and it applies at both levels [1].
The engagement examines the system before it examines the total. Get general IT controls and the evidence behind every entry in order before the practitioner arrives rather than during the engagement.
Summary of findings
The findings in six numbers
Number | What it shows |
|---|---|
15 December 2026 | Date from which ISSA 5000 applies for sustainability information reported for periods beginning on or after it and the date ISAE 3410 is withdrawn [1] [7] |
3 of 9 | Paragraph numbers in the ISSA 5000 internal control section 113 to 121 that apply identically at limited and reasonable assurance. They are 117 118 and 121 [1] |
119R | The only paragraph in that section with no limited assurance counterpart. It is the one that identifies IT applications the IT environment and general IT controls [1] |
91 | The paragraph on information produced by the entity. It applies at both levels and asks for evidence of accuracy and completeness [1] |
25 of 93 | ISO/IEC 27001 Annex A controls that sit inside the three IT processes ISA 315 names. Mapping by this paper [2] [3] [4] |
58% | Share of 1176 US material weakness reports from 2021 to 2025 citing IT software security and access issues up from 31% in 2021 [13] |
Source. ISSA 5000 [1] ISA 315 in its 2019 revision and the conforming Appendix 6 [2] [3] Annex A of ISO/IEC 27001 [4] the IAASB withdrawal announcement [7] and the KPMG material weakness study [13]. Paragraph counts and the Annex A mapping are calculated by this paper.
The common assumption is that limited assurance ignores the system and reasonable assurance tests it. That is close but wrong in a way that matters. Paragraph 118 requires the practitioner to evaluate whether the information system appropriately supports preparation of the sustainability information under the applicable criteria and it carries no L or R suffix [1]. The practitioner forms a view on the system at either level. What changes with the level is how much work sits behind the view.
The second assumption is that a certified information security management system answers the question. It answers part of it. Twenty five of the 93 Annex A controls map onto the three IT processes the auditing profession names which is just over a quarter [4]. The other 68 cover matters an assurance provider is not asking about. A certificate also does the wrong job in the wrong form which Finding 5 sets out.
The exposure is concentrated where most property portfolios are weakest. Activity data arrives from a BMS a supplier file a managing agent spreadsheet and a tenant submission and every one of those is information produced by the entity under paragraph 91.
Why the system question matters now for a UK property portfolio
The standard changes in six weeks. The IAASB withdrew ISAE 3410 with effect from the date ISSA 5000 takes effect [7]. The FRC issued ISSA (UK) 5000 on 12 November 2025 and has said that neither ISAE 3410 nor ISAE 3000 in its revised form will apply to sustainability assurance engagements after that date [8]. The Department for Business and Trade confirmed on 30 January 2026 that a voluntary register of sustainability assurance providers will be run by the FRC with ISSA (UK) 5000 proposed as a condition of registration [9].
Who is in scope is now settled for two of the three routes. Under the final rules the FCA published on 30 September 2026 listed companies in scope report against UK SRS on a comply or explain basis for accounting periods beginning on or after 1 January 2027 and must confirm whether third party assurance was obtained from whom over what and at what level [10]. For a group with qualifying EU subsidiaries Directive (EU) 2026/470 left limited assurance as the standing requirement under CSRD and removed the move to reasonable assurance with harmonised EU limited assurance standards due by 1 July 2027 [11]. SECR reporting requires no assurance at all which is why many portfolios meet a practitioner for the first time under CSRD reporting or under a lender request.
The decision that changes with the answer is where to spend the preparation. A team that spends it on the totals will be asked about the system. A team that can describe the system name who holds which rights and evidence where each entry came from has answered most of what the standard requires before the sampling begins.
Definitions
Assurance is an independent examination of reported sustainability information issued as limited assurance where the conclusion is expressed negatively or reasonable assurance which is a materially higher bar. General IT controls are controls over the IT processes that keep the IT environment working properly supporting the continued effective functioning of information processing controls and the integrity of information [2]. The IT environment is the IT applications the supporting infrastructure and the IT processes and personnel the entity uses where applications include data warehouses and report writers and infrastructure includes the network operating systems databases and the hardware and software around them [2].
Information produced by the entity is any report extract calculation or file the entity itself generates and the practitioner then relies on. Complementary user entity controls are controls a service organisation assumes its customers will operate named in the report on that service organisation without which its own controls do not achieve their objective. A one to many report is an assurance report designed for use by many user entities and their practitioners across a value chain [1].
Activity data is the underlying physical quantity a calculation is applied to such as kilowatt hours of electricity or cubic metres of gas. Estimated data is consumption derived rather than read by extrapolating a partial year applying a benchmark or apportioning a whole building figure. A BMS is the building management system that runs heating cooling ventilation and sometimes lighting and holds operational data. Sub metering is metering downstream of the incoming supply so consumption can be attributed to a demise a floor or an item of plant. Half hourly data is electricity consumption recorded in half hour intervals and collected automatically from the meter. An MPAN is the Meter Point Administration Number identifying an electricity supply point in Great Britain. An organisational boundary defines which assets an organisation reports consolidated by operational control financial control or equity share. These terms are defined in the Sustainify AI glossary.
ISSA 5000 is the International Standard on Sustainability Assurance 5000 General Requirements for Sustainability Assurance Engagements issued by the IAASB in November 2024 [1]. ISA 315 in its 2019 revision is the auditing standard on identifying and assessing risks of material misstatement and it is where the IT control vocabulary used across the profession is defined [2].
Method
The text of ISSA 5000 was read on 29 October 2026 from the IAASB final standard [1]. Every requirement paragraph in the section on the system of internal control paragraphs 113 to 121 was recorded as applying to both levels without distinction as having paired limited and reasonable versions or as existing for one level only. Paragraphs 50 to 52 on using the work of another practitioner paragraph 90 on the relevance and reliability of evidence and paragraph 91 on information produced by the entity were read in the same session. The counts in Finding 1 follow from that list.
The IT vocabulary was taken from ISA 315 in its 2019 revision which defines general IT controls and the IT environment and names the IT processes at paragraph 12(g)(iii) [2]. The example general IT controls and the risks each process addresses were read from Appendix 6 of the conforming Australian standard ASAE equivalent ASA 315 which reproduces the IAASB appendix [3]. The Annex A control identifiers and names were taken from the published list for ISO/IEC 27001 in its 2022 revision [4] and the control detail from ISO/IEC 27002 [5].
The mapping in Finding 4 is original analysis by this paper. Each example general IT control in Appendix 6 was read and the Annex A controls whose subject matter covers that example were recorded. A control is counted once under the IT process it principally serves. The count is a judgement about subject matter and not an equivalence claim and Limitations says what it does not establish.
Market evidence on where control failures occur comes from the KPMG study of material weaknesses disclosed in US annual reports [13]. The peer reviewed studies in Finding 6 were found through Google Scholar and each was checked at its publisher page its Digital Object Identifier record or a repository copy. Regulatory positions were read at the FCA the FRC the Department for Business and Trade and EUR Lex [8] [9] [10] [11]. What an assurance provider asks for first and how limited assurance differs from reasonable assurance are covered separately in the Insights section and are not restated here. This paper covers the system only.
Findings
Finding 1. Most of the system work is in the paragraphs that apply at both levels
ISSA 5000 sets out the system of internal control requirements across nine paragraph numbers. Paragraphs that apply to one level only carry an L or an R suffix which is the same convention ISAE 3410 used.
Table 1. What ISSA 5000 requires about the system of internal control by level
Paragraph | Subject | Limited assurance | Reasonable assurance |
|---|---|---|---|
113 | Understanding the components of the system | Through inquiry | Through inquiry and other procedures |
114 | Control environment | Understand it | Understand it and evaluate whether management has created a culture of honesty and ethical behaviour and whether the environment is an appropriate foundation for the other components |
115 | Risk assessment process | Understand the results | Understand the process and the results and evaluate whether the process is appropriate |
116 | Monitoring the system of internal control | Understand the results | Understand the process and the results and evaluate whether the process is appropriate |
117 | Information system and communication | Identical at both levels | Identical at both levels |
118 | Whether the information system supports preparation | Identical at both levels | Identical at both levels |
119R | Control activities IT applications the IT environment and general IT controls | No counterpart | Required |
120 | Design and implementation of controls | 120L applies only if the practitioner plans to test controls and covers those controls and the general IT controls related to them | 120R requires evaluating the design of each identified control and determining implementation by procedures beyond inquiry |
121 | Control deficiencies | Identical at both levels | Identical at both levels |
Source. ISSA 5000 paragraphs 113 to 121 [1]. The table summarises the requirements rather than reproducing them. The classification into identical paired and single level is by this paper.
Three paragraph numbers apply identically at both levels. Four have paired versions where the limited requirement is to understand and the reasonable requirement adds an evaluation. One 119R exists only for reasonable assurance. One 120 has a limited version that is conditional and a reasonable version that is not.
The practical reading for a preparer is that the conversation about the system happens at either level. What a reasonable assurance engagement adds is the word evaluate. A limited assurance practitioner asks how the control environment works and records the answer. A reasonable assurance practitioner asks the same question and then forms a view on whether the answer is adequate.
Finding 2. One requirement asks for a verdict on the system and it carries no suffix
Paragraph 118 is the one that preparers underestimate. Based on the understanding obtained under paragraph 117 the practitioner shall evaluate whether the information system of the entity appropriately supports preparation of the sustainability information in accordance with the applicable criteria [1]. There is no L version and no R version. The verdict is required at both levels.
Paragraph 117 sets up what that verdict rests on. It asks the practitioner to understand how the entity identifies the sustainability information to be reported how information from external sources such as service organisations or other organisations in the value chain is recorded processed corrected and incorporated and for estimates and forward looking information how the entity identifies the methods the assumptions the data sources and any changes needed to them [1].
Read that against a UK property portfolio. The external sources are supplier billing files managing agent returns a BMS export and tenant submissions. The estimates are the apportionments applied where sub metering does not exist. The question in 117(b) is not whether those sources are accurate. It is how they are recorded processed corrected and incorporated which is a question about the route rather than the number and it is answered by showing the route.
A portfolio that cannot describe the route answers 117 with a narrative and invites an adverse view under 118. A portfolio that can show the route from an MPAN and a half hourly data feed through to the reported line answers both with the system itself.
Finding 3. The hardest test is not in the internal control section at all
Paragraph 91 governs information produced by the entity. When the practitioner uses such information the practitioner shall evaluate whether it is sufficiently reliable for the purpose including as necessary obtaining evidence about its accuracy and completeness and evaluating whether it is sufficiently precise and detailed [1]. Paragraph 90 sits above it and requires evaluation of the relevance and reliability of information intended to be used as evidence including information from external sources [1]. Paragraph 94 says what happens when doubt remains which is that the practitioner considers modifying procedures and then assesses the effect on the engagement [1].
Neither 90 nor 91 carries an L or an R suffix. They apply in full at both levels.
This is the requirement that catches portfolios whose arithmetic is correct. Almost every artefact in a carbon reporting process is information produced by the entity. The consumption extract. The site list. The floor area schedule used to apportion. The list of assets inside the organisational boundary. The export that feeds the disclosure table. Each one is a report the entity generated and for each one the practitioner has to be able to get comfortable that it is accurate and complete.
Completeness is the half that is usually missing. A portfolio can evidence that every row in an extract is correct and still be unable to evidence that no row is absent. The evidence that settles completeness is a reconciliation to something independent of the extract such as a count of supply points against the asset register or a count of periods expected against periods held. That is a system artefact rather than a calculation and it is cheap to produce in advance and expensive to construct under time pressure. The article on estimated versus measured data covers how the gap is graded once it is known.
Paragraph 91 applies whether the engagement is limited or reasonable. Make every extract behind a disclosure evidence its own accuracy and completeness with assurance readiness built into the record rather than assembled afterwards.
Finding 4. The profession names three IT processes and 25 of the 93 Annex A controls sit inside them
ISSA 5000 refers to general IT controls without defining the term at length. The definition the profession uses comes from ISA 315 in its 2019 revision. General IT controls are controls over the IT processes of the entity that support the continued effective functioning of information processing controls and the integrity of information [2]. Paragraph 12(g)(iii) names the IT processes as the processes to manage access to the IT environment to manage program changes or other changes to the IT environment and to manage IT operations [2].
Table 2. The three IT processes and the risks each one addresses
IT process | Example general IT controls | Risks arising from the use of IT that the process addresses |
|---|---|---|
Manage access | Authorising new users and changes to access privileges removing access on termination or transfer authentication authorisation privileged access user access reviews security configuration physical access to the data centre | Users hold privileges beyond those needed for their duties which may create improper segregation of duties. Inappropriate changes are made to data outside application transactions. Systems are not configured or updated to restrict access to authorised users |
Manage program or other changes | Controls over designing programming testing and migrating changes separation of the ability to make a change from the ability to migrate it to production controls over data conversion | Inappropriate changes to applications containing automated controls or report logic. Inappropriate changes to database structure and data relationships. Inappropriate changes to system software. Errors introduced when converted data is incomplete redundant obsolete or inaccurate |
Manage IT operations | Monitoring jobs for successful execution controls over who can schedule and initiate jobs backup and recovery intrusion detection and vulnerability monitoring | The network does not prevent unauthorised users reaching information systems. Data cannot be recovered or accessed in time after a loss. Jobs result in inaccurate incomplete or unauthorised processing |
Source. ISA 315 in its 2019 revision at paragraph 12(g)(iii) [2] and the conforming Appendix 6 which gives the examples and the risks [3]. Wording is summarised rather than reproduced.
Those three processes are the frame an assurance provider brings. Set them against Annex A of ISO/IEC 27001 in its 2022 revision which holds 93 controls across 37 organisational 8 people 14 physical and 34 technological [4]. Twenty five of them sit inside the three processes.
Table 3. The mapping. Annex A controls that sit inside the three IT processes
IT process | Annex A controls that sit inside it | Count |
|---|---|---|
Manage access | 5.3 Segregation of duties 5.15 Access control 5.16 Identity management 5.17 Authentication information 5.18 Access rights 7.2 Physical entry 8.2 Privileged access rights 8.3 Information access restriction 8.5 Secure authentication 8.18 Use of privileged utility programs | 10 |
Manage program or other changes | 8.4 Access to source code 8.9 Configuration management 8.25 Secure development life cycle 8.29 Security testing in development and acceptance 8.31 Separation of development test and production environments 8.32 Change management 8.33 Test information | 7 |
Manage IT operations | 5.26 Response to information security incidents 8.6 Capacity management 8.7 Protection against malware 8.8 Management of technical vulnerabilities 8.13 Information backup 8.15 Logging 8.16 Monitoring activities 8.20 Networks security | 8 |
Total | Of 93 Annex A controls | 25 |
Source. Mapping by this paper from the Appendix 6 examples [3] against the Annex A control list and the ISO/IEC 27002 control detail [4] [5]. A control is counted once under the process it principally serves. This is a judgement about subject matter and not a certified equivalence.
Twenty five of 93 is 26.9%. The reading that follows is two sided and both sides matter. A certified information security management system covers the subject matter of roughly a quarter of its controls in the area an assurance provider asks about which is a real head start on a questionnaire. The remaining 68 controls cover screening supplier agreements physical security privacy continuity and incident learning none of which answers a question about a carbon figure.
Finding 5. A certificate is not an assurance report and the standard says which one it will accept
ISSA 5000 sets out what a practitioner may do with somebody else work. Paragraph 50 requires the practitioner to evaluate the competence and capabilities of the other practitioner to evaluate whether the nature scope and objectives of that work are appropriate and to determine whether the evidence is adequate [1]. Paragraph 51 covers one to many reports designed for use by user entities and their practitioners across a value chain and requires the practitioner to determine whether such a report provides sufficient appropriate evidence considering the description of procedures and results and the adequacy of the standards used [1]. Paragraph 52 requires the practitioner where it intends to obtain evidence about the operating effectiveness of controls to determine whether any complementary user entity controls identified in such a report are relevant to the user entity [1].
Three consequences follow for a portfolio that runs its carbon reporting on a platform.
The platform is a service organisation and paragraph 117(b) puts it inside the understanding the practitioner must obtain at either level [1]. Nobody can treat it as outside the system.
A certification against ISO/IEC 27001 is not what paragraphs 50 to 52 describe. A certificate records that an accredited body audited a management system against a standard and issued a certificate. An assurance report under those paragraphs describes procedures and results and is addressed to the question the user practitioner is asking. The two are different artefacts with different contents and a practitioner that needs evidence about operating effectiveness will say so. A certificate is useful at the procurement stage and is not a substitute at the engagement stage. The scope of registration on certificate 1N719TSI20261008GBRIS18Y covers the design development operation maintenance and support of digital platforms and related services which is a statement about the platform rather than about any figure the platform produced [6].
Complementary user entity controls are the part most buyers miss entirely. Where a service organisation assumes its customers will operate certain controls those controls remain the responsibility of the customer. Approving user access removing leavers reviewing privileged accounts and approving a reopening of a closed period are typically the landlord obligations not the platform obligations. Paragraph 52 makes them a question for the engagement [1].
Finding 6. In financial reporting the system is where controls actually fail
Sustainability assurance has no inspection record yet. Financial reporting does and the direction is consistent.
Table 4. Where IT sits in reported material weaknesses
Measure | Figure |
|---|---|
Annual reports reviewed in the most recent year of the study | 3307 |
Companies disclosing a material weakness in that year | 238 or 7% |
Reports disclosing a material weakness from 2021 to 2025 | 1176 |
Share of those reports citing IT software security and access issues | 58% |
The same share in 2021 | 31% |
The same share in 2024 | 54% |
The most frequently cited systems issue | General IT controls |
Source. KPMG study of material weaknesses disclosed in US annual reports covering 2021 to 2025 [13]. The population is US registrants reporting under Sarbanes Oxley and not UK sustainability reporters.
The share almost doubled across four years and the most frequently cited systems issue within it was general IT controls [13]. Lack of segregation of duties and control design was among the primary themes in the most recent year [13].
The peer reviewed literature explains why that matters for the quality of what a system produces rather than only for compliance.
Table 5. What the peer reviewed research finds about IT control weaknesses
Study | Sample | Finding |
|---|---|---|
Klamm and Watson 2009 [14] | 490 firms reporting material weaknesses in the first year of Sarbanes Oxley section 404 compliance | Firms with IT related weak components report more material weaknesses and more misstatements than firms without them with the effect concentrated in the control environment risk assessment and monitoring components |
Stoel and Muhanna 2011 [15] | Cross section of companies with audited annual assessments of IT and non IT internal controls | Firms reporting an IT internal control weakness have lower accounting earnings and a weak IT control environment lowers the earnings multiple the market applies. The results hold after controlling for non IT weaknesses |
Li and Peters and Richardson and Watson 2012 [16] | US firms with and without IT material weaknesses | Management forecasts are less accurate for firms with IT material weaknesses. The association is strongest for weaknesses tied to data processing integrity |
Haislip and Peters and Richardson 2016 [17] | Clients that changed auditor after an IT control deficiency | Clients switching to an auditor with more IT expertise are more likely to remediate a material weakness within one year. Audit firm IT expertise is negatively associated with both IT and non IT material weaknesses |
Mojtahedi and Zhou 2024 [18] | Section 404 auditor internal control opinion reports from 2014 to 2018 | The average number of IT internal control material weakness incidents per report rose from 2016 to 2018 and the mix of categories shifted against findings from pre 2010 data |
Source. Abstracts and publisher records of the studies cited found through Google Scholar. All five cover financial reporting under Sarbanes Oxley rather than sustainability reporting.
The pattern across the five is that IT control weakness is not only a compliance finding. It is associated with less reliable information coming out of the system which is the exact concern paragraph 91 of ISSA 5000 writes down [1] [16].
What this means in practice
The nine system questions and what settles each one
Table 6. The questions the standard behind them and the evidence that answers
Question | Where it comes from | What settles it |
|---|---|---|
1. How does the entity identify what sustainability information to report | ISSA 5000 117(a) [1] | A written basis of reporting naming the boundary the scopes and the exclusions |
2. How is information from service organisations and the value chain recorded processed corrected and incorporated | ISSA 5000 117(b) [1] | A diagram or record of each route in with the correction path for each |
3. For estimates how are the methods assumptions and data sources identified and changed | ISSA 5000 117(c) [1] | Versioned apportionment rules with the date each version applied from |
4. Does the information system appropriately support preparation under the criteria | ISSA 5000 118 [1] | A trace from a reported line to the entries beneath it run in front of the practitioner |
5. Have any control deficiencies been identified | ISSA 5000 121 [1] | The internal record of deficiencies and what was done about them |
6. Is each entity produced extract accurate and complete | ISSA 5000 91 [1] | A reconciliation to something independent of the extract such as supply points against the asset register |
7. Who can reach the data outside the application and who removes leavers | ISA 315 manage access [2] [3] | The permission matrix and the most recent user access review |
8. How are changes to calculation logic designed tested and migrated | ISA 315 manage program or other changes [2] [3] | A change record showing approval separate from migration |
9. Which complementary user entity controls does the platform assume you operate | ISSA 5000 52 [1] | The list from the service organisation with a named owner against each |
Source. ISSA 5000 [1] ISA 315 and its conforming Appendix 6 [2] [3]. The third column is this paper applying those requirements to a UK property portfolio.
Five actions before the next engagement
1. Write the basis of reporting before the practitioner asks for it
Questions 1 and 3 are answered by a document rather than by a conversation. The boundary the scopes the exclusions and the apportionment rules in one place dated is the cheapest point on this list and the one most often missing.
2. Reconcile every extract to something outside itself
Question 6 is where accurate portfolios fail. Count the supply points in the asset register and count the supply points in the consumption extract and explain the difference. Do the same for periods expected against periods held.
3. Produce the permission matrix and the last access review
Question 7 is the first general IT control an assurance provider will ask about because ISA 315 names manage access first and because it is the area with the clearest evidence of failure [2] [13]. Who holds elevated rights who removed the last leaver and when the list was last reviewed.
4. Ask your platform for its complementary user entity controls
Question 9 is a question for the vendor and the answer is a list. If the vendor cannot produce one that is itself the answer and it means every control in that list is unassigned.
5. Run the trace in a meeting not in a document
Question 4 is settled by doing it. Pick a reported line trace it to the entries and the source files in front of somebody who did not build it and time the exercise. Whatever it takes the engagement will take longer.
How Sustainify AI handles the system questions
Carbon data governance pins a factor set to each reporting period stores every calculation run with a run ID and locks a closed period which is what question 4 is asking to see. Carbon data lineage records the chain from source file to activity record to factor set to result at entry level which is the trace rather than a reconstruction. Carbon data integration takes meter and invoice data through a validating importer and keeps the source file against every row it creates which is what question 2 and question 6 rest on. Tenant allocation holds the apportionment rules as versioned and time bound records which is question 3. The article on automating utility data collection covers what a repeatable feed needs. The free Audit Readiness Check asks six questions about whether your carbon data would survive assurance and audit and assurance covers what goes into an evidence pack.
The platform is built and operated under a certified information security management system [6]. It does not issue an assurance opinion it does not replace an assurance provider and Finding 5 sets out why a certificate is not the artefact a practitioner needs at the engagement stage. The complementary controls a customer has to operate such as approving access and removing leavers remain the responsibility of the customer.
Disclosure of interest. This paper is published by Sustainify AI. The analysis used the public sources and the method set out in the Method section and was carried out independently of the platform.
Limitations
The standard text was read from the IAASB final standard and the excerpt available was truncated. Paragraphs 113 to 121 and 50 to 52 and 90 to 94 were read. The reporting requirements beyond paragraph 130 including what the assurance report must say about the work performed were not reached and are not described here. A reader relying on the exact wording should read the standard itself.
The counts are structural not a measure of effort. Three of nine paragraph numbers applying identically does not mean a third of the work is the same at both levels. The paired paragraphs 114 to 116 add an evaluation at the reasonable level that can be more work than everything in 117 and 118 together.
The Annex A mapping is a judgement by this paper. Twenty five of 93 is the result of reading the Appendix 6 examples against the Annex A subject matter and allocating each control once. Another reader could reasonably allocate a control to a different process include controls this paper excluded such as 8.17 Clock synchronization or exclude ones it included. The mapping is not an equivalence no certification body has endorsed it and it should not be presented to an assurance provider as one.
An information security certificate says nothing about whether a figure is correct. None of the 93 Annex A controls addresses whether a conversion factor was applied correctly or whether a boundary was drawn properly. Treating the certificate as evidence about a number is an error this paper is arguing against.
The material weakness evidence is US and is about financial reporting. The KPMG study covers US registrants reporting under Sarbanes Oxley [13]. The five peer reviewed studies cover the same population. They establish that IT controls are where control failures concentrate and that weak IT controls are associated with less reliable system output. They do not establish a rate for UK sustainability reporting which nobody has measured.
The research is read at abstract level in four of five cases. The full texts of the Klamm and Watson Stoel and Muhanna Li and colleagues and Haislip and colleagues papers sit behind subscriptions. Findings are reported as the abstracts and publisher records state them without the coefficients.
The regulatory positions are time sensitive. ISSA 5000 applies from 15 December 2026 and the UK register of assurance providers was voluntary and not confirmed as live at the time of writing [9]. The EU limited assurance standard is due by 1 July 2027 [11]. The FCA has said it will keep the case for mandatory assurance under review [10]. All should be checked against the current position before anything here is relied on.
What not to conclude. Not that limited assurance ignores the system which Findings 1 to 3 show it does not. Not that a reasonable assurance engagement is required to make the system questions worth preparing for. And not that any software including Sustainify AI answers them on its own because questions 1 5 7 and 9 are answered by the organisation rather than by a platform.
References
[1] International Auditing and Assurance Standards Board. International Standard on Sustainability Assurance 5000. General Requirements for Sustainability Assurance Engagements. November 2024. Paragraphs 15 18 50 to 52 90 91 94 and 113 to 121. Accessed 29 October 2026.
[2] International Auditing and Assurance Standards Board. International Standard on Auditing 315 in its 2019 revision. Identifying and Assessing the Risks of Material Misstatement. Definitions at paragraph 12 and the IT requirements at paragraph 26. Accessed 29 October 2026.
[3] Auditing and Assurance Standards Board Australia. ASA 315 Appendix 6. Considerations for understanding IT general IT controls and risks arising from the use of IT. Conforming Australian text of the IAASB appendix. Accessed 29 October 2026.
[4] ISO. ISO/IEC 27001. Information security management systems. 2022 revision. Annex A 93 controls across organisational people physical and technological themes. Accessed 29 October 2026.
[5] ISO. ISO/IEC 27002. Information security cybersecurity and privacy protection. Information security controls. Third edition February 2022. Control detail for the Annex A identifiers. Accessed 29 October 2026.
[6] Sustainify AI. Trust Centre. Certificate 1N719TSI20261008GBRIS18Y certified entity Codedevza AI Ltd and the scope of registration. Accessed 29 October 2026.
[7] International Auditing and Assurance Standards Board. IAASB announces withdrawal of ISAE 3410 Assurance Engagements on Greenhouse Gas Statements. 8 May 2025. Accessed 29 October 2026.
[8] Financial Reporting Council. ISSA (UK) 5000. Feedback Statement and Impact Assessment. 12 November 2025. Accessed 29 October 2026.
[9] Department for Business and Trade. Developing an oversight regime for assurance of sustainability related financial disclosures. Government response to consultation. 30 January 2026. Accessed 29 October 2026.
[10] Financial Conduct Authority. Policy Statement PS26/19. Aligning listed issuers sustainability disclosures with international standards. 30 September 2026. Accessed 29 October 2026.
[11] European Union. Directive (EU) 2026/470. Published in the Official Journal on 26 February 2026 and in force from 18 March 2026. Removal of the reasonable assurance and the 1 July 2027 date for harmonised limited assurance standards. Accessed 29 October 2026.
[12] Committee of European Auditing Oversight Bodies. Guidelines on limited assurance on sustainability reporting. 30 September 2024. Accessed 29 October 2026.
[13] KPMG LLP. Trends in material weaknesses. Study of material weaknesses disclosed in US annual reports covering 2021 to 2025 with 3307 annual reports reviewed in the most recent year. Accessed 29 October 2026.
[14] Klamm BK and Watson MW. SOX 404 Reported Internal Control Weaknesses. A Test of COSO Framework Components and Information Technology. Journal of Information Systems. Volume 23 issue 2. 2009. Sample of 490 firms. Scholar record for Klamm and Watson 2009. Accessed 29 October 2026.
[15] Stoel MD and Muhanna WA. IT internal control weaknesses and firm performance. An organizational liability lens. International Journal of Accounting Information Systems. Volume 12 issue 4 pages 280 to 304. 2011. Scholar record for Stoel and Muhanna 2011. Accessed 29 October 2026.
[16] Li C and Peters GF and Richardson VJ and Watson MW. The Consequences of Information Technology Control Weaknesses on Management Information Systems. The Case of Sarbanes Oxley Internal Control Reports. MIS Quarterly. Volume 36 issue 1 pages 179 to 203. 2012. Scholar record for Li and Peters and Richardson and Watson 2012. Accessed 29 October 2026.
[17] Haislip JZ and Peters GF and Richardson VJ. The effect of auditor IT expertise on internal controls. International Journal of Accounting Information Systems. Volume 20 pages 1 to 15. 2016. Scholar record for Haislip and Peters and Richardson 2016. Accessed 29 October 2026.
[18] Mojtahedi A and Zhou L. Information technology internal control material weaknesses in financial reporting. Categories trends associations and industry effects. International Journal of Accounting Information Systems. Volume 53. 2024. Section 404 reports from 2014 to 2018. Scholar record for Mojtahedi and Zhou 2024. Accessed 29 October 2026.
The system questions arrive whether the engagement is limited or reasonable. Prepare for sustainability assurance by evidencing the route into every figure before the first request lands.
Frequently Asked Questions
What does an assurance provider test about the system rather than the numbers?
How the entity identifies what to report how external information is recorded and corrected how estimates are made whether the information system supports preparation under the criteria whether control deficiencies exist and whether each entity produced extract is accurate and complete. Those sit at ISSA 5000 paragraphs 117 118 121 and 91 [1].
What are general IT controls?
Controls over the IT processes of the entity that keep the IT environment working properly and support the integrity of information [2]. ISA 315 names three IT processes which are managing access to the IT environment managing program or other changes to it and managing IT operations [2].
Does limited assurance look at internal control at all?
Yes. Paragraph 113L requires an understanding of the components of the system of internal control through inquiry and paragraphs 117 118 and 121 apply identically at both levels [1]. What reasonable assurance adds is evaluation rather than understanding.
Which ISSA 5000 paragraph covers general IT controls?
119R identifies the IT applications the other aspects of the IT environment subject to IT risks and the general IT controls that address them and it has no limited assurance counterpart. 120L covers the general IT controls related to any controls a limited assurance practitioner chooses to test [1].
What is information produced by the entity and why does it matter?
Any report extract or calculation the entity itself generates and the practitioner then relies on. Paragraph 91 requires the practitioner to evaluate whether it is reliable enough including obtaining evidence about its accuracy and completeness and it applies at both levels [1].
When does ISSA 5000 take effect?
It applies to sustainability information reported for periods beginning on or after 15 December 2026 or as at a specific date on or after that date with earlier application permitted. ISAE 3410 is withdrawn from the same date [1] [7].
Does ISO 27001 certification answer the general IT controls questions?
Partly. Twenty five of the 93 Annex A controls sit inside the three IT processes ISA 315 names which is just over a quarter [4]. A certificate is also a different artefact from the assurance report ISSA 5000 paragraphs 50 to 52 describe so it helps at procurement and does not substitute at the engagement [1].
What are complementary user entity controls?
Controls a service organisation assumes its customers will operate without which its own controls do not achieve their objective. Approving user access and removing leavers are typical examples. Paragraph 52 makes them a question for the engagement where the practitioner seeks evidence on operating effectiveness [1].
How often do IT controls turn out to be the problem?
In the US material weakness population 58% of 1176 reports from 2021 to 2025 cited IT software security and access issues up from 31% in 2021 and the most frequently cited systems issue was general IT controls [13].
What should a property portfolio prepare first?
The basis of reporting a reconciliation of each extract to something outside itself and the permission matrix with the last user access review. Those three answer six of the nine questions in Table 6 and none of them requires new software.