Access Official Technical PDF

Share Summary:LinkedInEmail

Compliance audit findings can reveal a specific control gap even when an organization receives an overall opinion that it complied with applicable requirements in all material respects. The Illinois Teachers’ Retirement System’s examination for the year ended June 30, 2018, illustrates this distinction. Auditors reported one recurring issue involving investment-manager disclosures required by the Illinois Pension Code, while concluding that the System was materially compliant overall.

For industrial organizations, system integrators and other businesses that manage regulated procurement, the report offers a useful reminder: a control process needs to address not only whether documents are collected, but whether required information is complete, reviewable and resolved before a contract is awarded.

What the 2018 compliance examination covered

The examination assessed the System’s compliance with requirements concerning the use of public funds, applicable laws and regulations, state accounting, revenue records, and the administration of money and assets held on behalf of the State or in trust. The work was conducted under Government Auditing Standards, the Illinois State Auditing Act and the Auditor General’s Audit Guide.

The accountants concluded that the System complied, in all material respects, with the specified requirements during the year. They nevertheless reported an instance of noncompliance that the Audit Guide required them to disclose. This is not a contradiction: an overall compliance opinion and an individual reported finding answer different questions. The opinion addresses compliance in all material respects across the requirements examined; a finding identifies a particular exception that merits attention.

The report also stated that the examination did not identify any deficiencies in internal control over compliance that the auditors considered material weaknesses. That conclusion was bounded by the work performed: the auditors noted that their review was not designed to identify every possible control deficiency, and that unidentified material weaknesses could exist.

The investment-manager disclosure gap

The finding concerned disclosures that investment advisers, consultants and private market funds must provide under section 40 ILCS 5/1-113.21 of the Illinois Pension Code. The required information included workforce demographics and counts of contracts with certain minority-owned, women-owned or businesses owned by people with disabilities. The statute also addressed contracts with other businesses when more than half of the services were performed by people in those groups.

During testing, auditors found that 10 of 25 investment-manager disclosures returned to the System—40% of the items tested—did not properly report required contract counts. The managers told the System that they did not track all of the information. System officials said their compliance department checked that disclosures were received during due diligence, but some managers did not track or could not legally provide every item under the statute’s wording.

The auditors’ concern was that failing to obtain the required disclosures before awarding a contract resulted in noncompliance. They recommended working with investment managers to meet the requirements or seeking a legislative remedy. The System disagreed with the finding and said it believed its existing approach complied with the law’s intent. The report records both the auditors’ conclusion and management’s response; it does not present the response as independently validated by the auditors.

Why receiving a form is not the same as validating it

The distinction between document receipt and disclosure completeness is central to this case. A process can confirm that a form arrived while still allowing missing, inaccurate or unsupported fields to pass through. When a requirement calls for information that a supplier may not routinely collect, a checklist limited to document presence may not be enough to demonstrate that the organization addressed the requirement.

In industrial procurement, the same control-design question can arise wherever supplier or contractor information is required before an award. The report does not address automation vendors or industrial contracting specifically, but its documented issue suggests a general control principle: map each requirement to evidence, review criteria and an accountable decision-maker.

Control questions for procurement and compliance teams

  • Define completeness: Specify which fields must be present and what qualifies as an acceptable response.
  • Review before approval: Make the timing of the disclosure check explicit in the contracting workflow.
  • Handle unavailable information: Set out how the organization should document a supplier’s inability or refusal to provide required data and who can determine next steps.
  • Escalate exceptions: Route incomplete or disputed disclosures to an authorized compliance or legal reviewer rather than treating them as routine paperwork gaps.
  • Retain evidence: Keep the disclosure, review record and resolution together so the basis for the contracting decision can be examined later.

These are practical control considerations, not steps specifically reported as having been implemented by the System. The examination records the finding, recommendation and management disagreement; it does not describe a subsequent resolution.

Recurring findings call for a response review

The disclosure issue was not new. The report identified it as a repeat finding from the two prior examinations, listing the earlier reference numbers as 2017-001 and 2016-001. The summary showed one current finding and one prior finding, with no prior recommendations marked as implemented or not repeated.

A recurring finding does not, by itself, establish why a control issue persists. Here, the reported circumstances included managers’ limits in tracking or providing the requested information, alongside disagreement between the System and auditors about how the statutory requirement should be applied. For organizations facing a similar impasse, it is important to distinguish an operational fix from an interpretation or policy issue. Each may require a different owner, evidence trail and escalation route.

Read audit results with their scope in mind

The compliance report should also be read alongside its stated scope. The System’s basic financial statements received an unmodified audit opinion, and the report on internal control over financial reporting did not identify deficiencies considered material weaknesses. Those results do not erase the separate disclosure finding, just as the finding does not imply that the financial statements were misstated.

The report further distinguished audited supplementary schedules from the Analysis of Operations section. Schedules 1 through 7 and the investment listing were subjected to specified audit procedures and were judged fairly stated in relation to the basic financial statements. The Analysis of Operations was unaudited and received no audit opinion or assurance. Understanding these boundaries helps decision-makers avoid treating every schedule or narrative in a report as having the same level of assurance.

Practical implications

The 2018 examination shows why organizations should connect compliance requirements to specific procurement controls, rather than relying on document collection alone. For a requirement that depends on third-party information, control owners need a defined completeness check, a process for exceptions and a clear path for resolving legal or operational barriers before a decision is finalized.

It also demonstrates the value of reading audit conclusions precisely. An overall opinion of material compliance can coexist with a reportable exception, and a clean result in one audit area does not settle a finding in another. For industrial automation leaders and other technical decision-makers, the practical takeaway is to make supplier compliance evidence part of the decision workflow, document unresolved gaps, and ensure recurring issues reach the appropriate governance level.

Access Official Technical PDF

About The Author