Blog

LPIS vs IACS: what's the difference for a paying agency?

13 October 2026

A farm track running between a green crop field and a ploughed brown field, divided by a hedge.

If you work inside a paying agency, you hear both terms in the same breath, often from people who use them interchangeably. They're not the same system, and mixing them up is how audit findings start. Here's the distinction as it actually plays out in the office.

IACS is the whole control framework

IACS, the Integrated Administration and Control System, is the umbrella. It's the full set of procedures a paying agency runs to administer CAP support: the claim register, the control strategy, the sanction rules, the payment calculations, the reporting back to the Commission. IACS is process. It covers who applied for what, how the claim gets checked, and what happens when a check turns up a discrepancy.

LPIS, the Land Parcel Identification System, is one component sitting inside IACS. It's the reference layer, the geospatial record of every reference parcel and its boundary, maintained so that a declared parcel on a claim form can be matched against a known, surveyed piece of ground. When you open a claim and check the declared area against the reference parcel, you're using LPIS. When you're deciding whether that claim is eligible, applying a reduction, or logging the case for the annual control statistics, you're operating inside IACS.

Put another way: IACS is the case file and the rulebook. LPIS is the base map that tells you where the parcel is and how big it's supposed to be.

Where the confusion actually causes problems

The mix-up isn't just semantic. It shows up in three places during the declared-crop check:

Boundary versus crop. LPIS gives you the reference boundary and the maximum eligible area. It does not, on its own, tell you what's growing inside that boundary this season. A farmer can declare wheat on a parcel whose LPIS geometry is accurate to the centimetre and still have declared the wrong crop. The reference layer and the crop-type call are two separate facts, and an auditor who treats LPIS as proof of crop type is going to get a finding.

Where VGI fits. Member States can use vector-based geo-tagged images, VGI, submitted by the applicant as supporting evidence instead of sending an inspector to walk the field. That evidence sits inside IACS as part of the claim file. It's not part of LPIS, and it doesn't update the reference parcel. A geo-tagged photo of a field can support a crop-type determination for one claim in one year. It doesn't change what the base layer says the parcel boundary is.

Who owns the update. LPIS updates run on their own cycle, usually tied to orthophoto refresh and the annual quality assessment the agency has to report. IACS case decisions, including sanctions and recoveries, run on the claim year. An LPIS correction made in March doesn't retroactively fix a crop-type question flagged on a 2025 claim. Agencies that treat the two as a single update stream end up chasing paperwork across the wrong cycle.

What this means for the annual check

None of this changes what the control statistics require: a crop-type determination on every declared parcel, dated and defensible, sitting in the claim file next to the area measurement. LPIS tells an officer where the parcel is. It doesn't tell them what's in it. That gap is exactly where manual sample-plot visits, or applicant-submitted VGI, have historically had to carry the load, parcel by parcel, season by season.

A seasonal reflectance read across the declared block closes that gap without adding another field visit to the calendar. Crop Type Mapping turns that signature into one crop-type call per parcel, dated and sourced, in a layer built to sit next to the claim file rather than replace it.

Get the crop-type call sorted once a season and the LPIS-versus-IACS question stops being the thing that trips up your file review.