An Internal Control System is the documented procedure by which a Farmer Producer Organisation inspects and approves its own members. Under NPOP group certification, the certifying body does not inspect every farmer. It inspects your ICS, then verifies a sample of farmers against your records. If the two disagree, the finding applies to the group, not to the individual.
This is the part FPOs most often underestimate. One farmer's undocumented input can place the entire group's certificate at risk. This article sets out what an ICS must contain, who staffs it, and the records it has to produce on demand.
What an Internal Control System Must Contain
An ICS is not a single document. A certifying body expects a defined set of components, each with evidence that it operates in practice rather than on paper.
| Component | What it establishes | Evidence required |
|---|---|---|
| ICS manual | Your written procedure | Approved, dated, version controlled |
| Farmer register | Who is in the group | Land details, survey numbers, plot areas |
| Internal inspection reports | That you inspect your own members | One per farmer per season, signed |
| Approval and sanction records | That findings have consequences | Decisions on non-compliant farmers |
| Training records | Farmers know the standard | Dates, attendance, subject covered |
| Input approval records | Only permitted inputs are used | Invoices and usage logs per farmer |
The component most often missing is the fourth. Many FPOs inspect their farmers and record the findings, but never document what happened next. An inspection report noting a problem, with no corresponding decision, reads to an auditor as a system that detects issues and ignores them.
Who Staffs the ICS, and the Conflict of Interest Rule
Three roles must be filled, and they cannot all be the same person.
- Internal inspectors visit farmers and record findings against the standard.
- The approval committee reviews those findings and decides whether each farmer is approved, warned or suspended.
- The ICS manager maintains the records and is the auditor's point of contact.
An internal inspector cannot approve their own inspection. Where the same individual inspects a farmer and signs off the decision, the certifying body treats that approval as unsupported. In a small FPO this is usually solved by having the approval committee sit as a group, with any member declaring an interest excluded from that farmer's decision.
Inspectors should also not inspect their own land, or a close relative's. Rotating inspectors between villages each season removes the question entirely and is straightforward to evidence in your records.
Group certification means the group holds one certificate. A finding against one member's records is a finding against the group, and can suspend every farmer in it.
Running Internal Inspections That Hold Up
Every registered farmer must be internally inspected at least once per production cycle, before the external audit. The inspection covers what the external auditor will check, so that nothing is discovered for the first time on audit day.
Each inspection record should establish:
- Plot identity. Survey number and area, matching the farmer register exactly.
- Crops in the ground against what the farmer declared for the season.
- Inputs used since the last visit, checked against purchase invoices.
- Buffer zones where a plot adjoins conventionally farmed land.
- Storage separation where organic and non-organic produce are handled together.
- Yield estimate for the plot, which is later checked against quantities sold.
The yield estimate matters more than most FPOs expect. If a farmer's declared plot area cannot plausibly produce the quantity sold as organic, that gap is the first thing a certifying body examines. Recording an estimate at inspection, before harvest, protects you from that question later.
Keeping the ICS Consistent With Portal Records
Where produce is destined for export, farmer and plot data also sits on APEDA Tracenet. Two records of the same farmer, maintained separately, will drift. The mismatches that follow are found at inspection, when there is no time to reconcile them.
Three practices prevent this:
- Treat one source as authoritative — usually your farmer register — and update the portal from it, never the other way round.
- Record plot area to the same precision in both places. A plot recorded as 1.5 hectares in one system and 1.50 in another is fine; 1.5 against 1.55 is a finding.
- Reconcile the farmer count between your register and the portal after every submission, not annually.
An ICS that passes audit is one where inspections happen on a defined cycle, decisions are recorded alongside findings, and the same farmer data appears identically in your register and on the portal. The manual matters less than the evidence that the manual is followed.
KrushiFlow keeps the farmer register, plot details and inspection records in one place, and submits the same data to PGS India and APEDA Tracenet so the two do not diverge. If your ICS currently spans several spreadsheets maintained by different people, reconciling them is the work worth doing before your next inspection.