How to read an EU Commission control statistics report before a conformity audit

The control statistics report lands on your desk every year looking like a formality. It isn't one, not when a DG AGRI conformity clearance mission is already scheduled. The auditors arriving in a few weeks will have read your return line by line before they walk through the door, and they'll be testing whether the numbers you submitted match what their own sample finds on the ground. Reading the report the way they will, before they arrive, is the difference between a mission that confirms your system works and one that opens a financial correction file.

What the report measures

The control statistics return is the paying agency's own account of how its control system performed that scheme year: how many claims went through administrative checks, how many parcels were pulled for an OTSC, what error rate came out of each, and how the risk analysis that selected those parcels performed against a random sample. DG AGRI reads it for consistency between the administrative check error rate and the OTSC error rate, and for whether your risk-based selection catches more irregularities than a random draw would. If risk-based and random samples come back showing similar error rates, that's the first thing an auditor will flag, because it means the risk model isn't doing its job.

Go through your own return looking for the same gap. If the risk-targeted sample and the random sample land close together, you already know what the mission's opening question will be, and you have weeks instead of hours to put together an answer.

The numbers that get tested on the ground

Three figures in the report carry more weight than the rest, and all three get re-tested during the mission, usually against a parallel sample the Commission draws itself.

• The control rate achieved against the minimum required. If you cleared the floor by a thin margin, or made it up with a late addition of extra checks in one region, the auditor will ask why the shortfall happened in the first place.
• The error rate split by scheme and by region. A national average that looks fine can be hiding one region running hot. Auditors pull regional breakdowns specifically because paying agencies tend to report at the aggregate level.
• The residual error rate, the irregularity rate left after corrections and recoveries. This is the figure that drives any flat-rate or extrapolated financial correction, so it gets checked against the underlying case files, not just the summary table.

Pull your own regional breakdowns before the mission does. If a region's error rate sits well above the national figure, you want to already know why, not find out from the auditor's own re-sample.

Where paying agencies get caught out

The report matching a control population that was never checked in full causes more trouble than a wrong number in the report. If your OTSC round covered the required minimum percentage of claims, but the claims outside that sample were never looked at again, the Commission's own re-sample is effectively testing the parcels you didn't check, and that's where discrepancies turn up. A control statistics return built on a sampled inspection round can look clean on paper and still fail the moment the auditor's sample lands on a parcel your system never touched.

Fixing this gap before the report goes in costs far less than explaining it during the mission. A season-long check of every claimed parcel against satellite imagery shows the auditor what was observed on every parcel in the claim population, including the ones an inspector never reached that season. That's the approach behind Subsidy Monitoring's parcel-by-parcel flag list, built for paying agencies who want every claimed parcel checked before the file goes to DG AGRI.

If your next control statistics report is still built around a sampled inspection round, it's worth seeing what a full-parcel check looks like before the mission is on the calendar.