The 2019 compliance examination of the Teachers’ Retirement System of the State of Illinois (TRS) offers a useful example of how public-sector compliance depends not only on an organization’s own controls, but also on information provided by external investment managers and consultants. For industrial organizations and other regulated entities, the central lesson is practical: compliance workflows must identify required records, check them for completeness and address gaps before decisions are finalized.
What the Illinois TRS compliance examination covered
The examination covered the fiscal year ended June 30, 2019. It assessed whether TRS handled public funds in accordance with authorized purposes and restrictions, complied with applicable laws and accounting requirements, recorded state revenues and receipts properly, and administered assets held for the state or in trust.
Auditors reported that TRS complied with the specified requirements in all material respects. They also identified a reportable instance of noncompliance, described in finding 2019-001. Separately, the financial statement audit report stated that no internal control deficiencies considered material weaknesses were identified. These conclusions address different matters: a finding can identify a compliance exception without the auditors concluding that a material weakness exists.
Investment disclosures were the recurring compliance issue
The finding concerned disclosures required by the Illinois Pension Code before certain investment and consulting contracts are awarded. TRS used forms and contract provisions to request information from prospective investment managers and consultants during due diligence. However, auditors found that some returned disclosures were incomplete.
Among 33 investment manager disclosures tested, 11 did not properly report required information about contracts with minority-owned, women-owned, or businesses owned by people with disabilities, as well as other related contract information. Auditors also noted that one of nine investment consultants did not properly disclose the number of investment-service searches it had conducted.
The issue was not simply whether TRS had requested the forms. The statutory requirements called for specific information to be disclosed and considered before contracts were awarded. Some firms told TRS that they did not track all of the requested information; the examination also noted an international firm’s explanation that relevant diversity initiatives were not defined in the same way under its laws.
Why complete disclosures matter in procurement
Disclosure requirements become operational controls when they are built into procurement and approval processes. A request form can establish what information is expected, but a process also needs a way to determine whether each response is complete, whether a missing item has been resolved, and whether the required information was available before a contract decision.
For regulated organizations, this distinction applies well beyond pension systems. In industrial procurement, for example, supplier qualification may involve certifications, safety records, insurance documentation, or other mandatory evidence. Receiving a document is not equivalent to verifying that it contains the required information. Clear ownership, documented review, and escalation procedures help prevent an incomplete submission from being treated as a completed control.
Key process considerations
- Define required fields: Translate applicable laws, contract terms, and internal policies into a clear checklist for each type of vendor or service provider.
- Validate responses: Review submissions for missing, ambiguous, or inconsistent information rather than relying only on confirmation that a form was returned.
- Record timing: Keep evidence showing that the review occurred before the relevant contract award or approval.
- Escalate exceptions: Route unavailable or incomplete information to the appropriate compliance, legal, procurement, and decision-making personnel.
- Retain an audit trail: Maintain the request, response, follow-up, review, and disposition together so the control can be demonstrated later.
Audit findings and management response
The auditors recommended that TRS work with investment managers and consultants to meet the disclosure requirements or seek a legislative remedy. TRS disagreed with the finding and stated that it believed its existing approach complied with the statute’s intent. The examination records this response but notes that management’s response was not subjected to the audit procedures and that no opinion was expressed on it.
The finding was repeated from prior examinations, making the issue more than a one-time documentation exception. Recurrence is a signal for organizations to reassess whether existing procedures can reliably produce the evidence required, particularly when external parties control the underlying data. If a legal or operational constraint prevents complete reporting, that constraint needs a defined path for review and resolution rather than an informal assumption that the requirement has been satisfied.
What the examination does—and does not—say
The examination’s overall conclusion was material compliance, alongside the specific disclosure finding. It also included fiscal schedules and supplementary information on appropriations, expenditures, investment activity, administrative expenses, and other operations. Some operational analysis was explicitly unaudited, while identified supplementary schedules were examined in relation to the basic financial statements. Readers should distinguish these sections and their assurance levels rather than treating every table in a compliance report as having the same audit status.
That distinction is relevant to technical decision-makers who use assurance reports to assess governance or operational risk. An audit opinion, a compliance finding, an internal-control observation, and unaudited analysis each communicate different kinds of evidence. Understanding the scope helps prevent both overstatement and underestimation of what an examination establishes.
Practical implications for compliance teams
The TRS case shows how a well-defined form and a due-diligence review can still leave compliance exposure when the data requested is not tracked or supplied completely. Effective controls need to address the full lifecycle: identify the rule, obtain the evidence, verify it, document how exceptions were handled, and preserve proof that the review occurred at the required point in the decision process.
For plant managers, system integrators, and operations leaders, the broader takeaway is to treat compliance evidence as part of process design. Assign clear accountability for validation, make exception handling explicit, and ensure records are retrievable for independent review. These practices help organizations demonstrate not only that a control exists, but that it operates as intended.