Access Official Technical PDF

Share Summary:LinkedInEmail

The 2017 SURS compliance examination offers a focused example of how statutory requirements, management processes, and audit evidence can intersect. For organizations responsible for public funds, Illinois Pension Code compliance depends not only on having a formal process, but also on whether required information is obtained and documented in a way that satisfies the applicable rules. The examination found that the State Universities Retirement System of Illinois (SURS) materially complied with the tested state requirements overall, while identifying a specific issue with investment-manager disclosures.

What the SURS compliance examination covered

The examination addressed the fiscal year ended June 30, 2017. Auditors evaluated whether SURS handled public funds according to their authorized purposes and legal restrictions, complied with applicable laws and accounting requirements, recorded state revenues and receipts fairly, and properly administered money and securities held on behalf of the state or in trust.

The independent accountant concluded that SURS complied, in all material respects, with the requirements examined. That overall conclusion came with a reportable exception: finding 2017-001, concerning disclosures required from investment managers under the Illinois Pension Code. The report also stated that auditors did not identify material weaknesses in internal control over compliance. These conclusions address different questions: an overall compliance opinion does not mean that no individual compliance issue was found.

Illinois Pension Code compliance and manager disclosures

The finding concerned Section 40 ILCS 5/1-113.21. As described in the examination, before an investment-services, consulting-services, or private-market-fund contract is awarded, the relevant provider must disclose information about the diversity of its investment and senior staff and its contracts with businesses owned by minorities, women, or people with disabilities. The statute also addresses certain contracts with other businesses when more than half of the services are performed by people in those groups.

The System used a request-for-proposal form to request and record these data elements. In testing, auditors found that two of nine investment-manager disclosures returned to SURS did not properly provide numerical information about the specified business contracts. Some managers had indicated that they did not know, did not track, or could not legally provide all requested information. The auditors treated the failure to obtain the required disclosures before contract awards as noncompliance.

The report notes that the disclosure information was provided to board members as part of the manager-selection process. It also records SURS’s position that fiduciary prudence under other provisions of the Pension Code shaped how the information should be considered and that the statute did not require managers to create information they did not already possess. SURS disputed the finding, while explaining that it had revised its process to require numerical responses without additional notations. The response is management’s position; the examination report’s finding remains the auditors’ conclusion.

Why the process details matter

This case illustrates a practical distinction between requesting information and securing a response that meets a defined requirement. A form can list every required data element, but if respondents can substitute an explanation for a required numerical disclosure, the resulting record may not meet the auditor’s interpretation of the statute.

For compliance owners, procurement teams, and governance bodies, the report points to several process questions worth resolving before a contract decision:

  • Are requirements translated into explicit response fields? The requested information should be clear enough that providers understand what must be supplied.
  • How are incomplete responses handled? A process should specify what happens when a provider reports that data are unavailable, untracked, or cannot be provided.
  • Is review documented? Records should show what information was received and how it was considered before the award, particularly where the law requires consideration within fiduciary constraints.
  • Do procedures match the governing requirement? Internal forms and instructions should be reviewed against the statutory language and any relevant interpretation used by oversight bodies.

These are general lessons about control design and documentation, not findings about industrial automation systems. The SURS examination concerns a public retirement system and investment contracting. Its value to a broader technical audience lies in the way it makes a familiar governance issue concrete: a control is only as effective as the requirements it captures, the exceptions it manages, and the evidence it preserves.

Reading the audit findings in context

The report distinguishes compliance testing from the audit of financial statements. In its separate financial-statement reporting, the auditors stated that their tests disclosed no matters required to be reported under Government Auditing Standards. The state compliance examination, however, identified the investment-disclosure issue under the Audit Guide for Illinois state agencies. Different audit objectives and criteria can therefore produce distinct findings without contradicting one another.

The report also included supplementary schedules covering appropriations and expenditures, revenues and expenses, administrative costs, investments, and other operational measures. Audited supplementary schedules were assessed in relation to the basic financial statements. The Analysis of Operations section was identified as unaudited and was not given an audit opinion or assurance. That distinction is important when readers use supporting information for oversight or decision-making.

Practical implications

The 2017 examination shows why compliance programs need more than a policy statement or a completed form. They need clear data requirements, a defined route for handling exceptions, and records that demonstrate how decision-makers addressed the information available to them. SURS reported changes to its request process, while maintaining that its approach was consistent with its fiduciary responsibilities.

For any organization managing regulated funds or contracts, the central takeaway is to align operational procedures with the governing rule and to preserve evidence of both the response and the review. In the SURS case, overall compliance was affirmed, but a specific disclosure process still drew a repeat finding. That combination underscores the importance of treating individual control gaps seriously even when the broader compliance framework receives a favorable opinion.

Access Official Technical PDF

About The Author