A compliance audit can report broad adherence to requirements and still identify a control issue that warrants attention. The Illinois Teachers’ Retirement System’s examination for the year ended June 30, 2017, offers a clear example: auditors concluded that the system complied in all material respects with specified state requirements, while also reporting incomplete disclosures from investment managers under the Illinois Pension Code.
For industrial organizations, the practical lesson is relevant beyond pension administration. When regulatory obligations depend on information supplied by external parties, a reliable process must establish not only that forms were received, but that required fields contain accurate, supportable answers.
What the compliance audit examined
The examination covered the system’s use of public funds, compliance with applicable laws and regulations, state revenue and receipt records, and the administration and accounting of assets held for the state or in trust. The work was conducted under attestation standards, Government Auditing Standards, the Illinois State Auditing Act, and the state auditor’s guide.
Auditors gave an overall opinion that the system complied in all material respects with the specified requirements. Separately, they reported one instance of noncompliance, identified as Finding 2017-001. The finding concerned disclosure requirements for investment services, consulting services, and commitments to private market funds.
The report also distinguished between information that received audit procedures and information that did not. Fiscal schedules and the investment listing were subjected to procedures applied in the financial statement audit and additional procedures; the auditors said they were fairly stated in relation to the basic financial statements. The Analysis of Operations section was unaudited and carried no audit opinion or assurance.
Where investment-manager disclosures fell short
The Illinois Pension Code required investment advisers, consultants, and private market funds to disclose information before a contract was awarded. Among other items, disclosures covered the number and percentage of investment and senior staff who were minority persons, women, or persons with disabilities. They also covered contracts with businesses owned by people in those groups, along with specified contracts with other businesses.
Auditors found that 10 of 30 disclosures returned by investment managers—33% of those tested—did not properly provide required information. The exceptions related to staff counts or percentages and contract counts. System officials said the compliance department checked that disclosures were received during due diligence, but some managers did not track, or could not legally provide, all information requested under the law’s wording.
The issue was not simply whether a questionnaire had been submitted. A disclosure with missing or unsupported information could leave the system unable to demonstrate that it had obtained the information required before awarding a contract. The auditors concluded that this resulted in noncompliance with the Pension Code.
Why a completed form is not the same as verified data
The system disputed the finding. It said its questionnaire responses addressed the law and provided enough information for an informed judgment about managers’ commitment to diversity. It also objected to treating blank fields as noncompliant when the total for a requested category was zero: in its view, adding zeros to empty boxes did not add useful information.
The auditors focused on whether the reported values were actually supported. They noted that the system had begun using a macro formula to prepopulate disclosure forms with totals. When a manager made no disclosure, the total could automatically appear as zero; when a manager entered data, the formula would calculate a total. Auditors accepted that zero can be a valid answer, but counted an exception where other information on the form conflicted with a prepopulated zero.
This distinction matters for any organization that uses templates, automated calculations, or intake forms as part of a compliance workflow. A field populated by a formula is not necessarily evidence that a third party supplied or confirmed the value. Review procedures need to distinguish a verified zero from missing information that has been converted into a zero by the form itself.
Control practices for managing disclosure requirements
The report recommended that the system work with investment managers to meet the disclosure requirements or seek a legislative remedy. The finding was repeated from the prior report, making the issue’s persistence another important element of the control picture.
Organizations managing similar obligations can use the case to assess whether their processes clearly address:
- Completeness: Are all required data points answered before approval or contract award?
- Accuracy: Can reviewers distinguish a confirmed zero from a blank, unavailable, or system-generated value?
- Evidence: Is there a record showing who provided the information and when it was reviewed?
- Escalation: Are unresolved data limitations referred to compliance, legal, procurement, or other appropriate decision-makers?
- Follow-through: Are recurring exceptions tracked and addressed rather than treated as isolated paperwork issues?
These are process considerations, not a substitute for interpreting the specific legal requirement. In the Illinois TRS case, the recommendation expressly included working with managers or seeking a legislative remedy, reflecting the system’s stated concerns about what some firms could provide.
Practical implications for compliance leaders
The examination did not report a material weakness in internal control over compliance, and the separate financial statement audit report did not identify reportable noncompliance under Government Auditing Standards. Those conclusions coexist with the specific state compliance finding: different audit procedures and reporting criteria can produce distinct results within the same examination.
For technical and operational leaders, the broader takeaway is to design compliance controls around the quality and traceability of information, not just task completion. Receipt checks, automated forms, and summary totals can support an efficient workflow, but they should not obscure missing evidence or contradictory data. A defensible process makes exceptions visible, assigns responsibility for resolving them, and records the basis for the final decision.
In short, the Illinois TRS examination shows why a compliance audit should be read at both levels: the overall opinion and the detailed findings. Even when overall compliance is reported, repeated gaps in required disclosures can signal that review steps need clearer validation and stronger follow-through.