Farmer enrolment on the NMNF portal fails when Aadhaar authentication does not go through. Most failures come from a mismatch between the portal entry and the Aadhaar record, or from the mobile number linked to Aadhaar. This guide covers the fixes in the order to try them.
The short version
- Match the Aadhaar record exactly: name, date of birth and gender.
- Check the linked mobile number on UIDAI's official site.
- Real errors in Aadhaar need an update at an Aadhaar centre, tracked by URN.
- Only then suspect the portal — browser, connection, or support.
Why Aadhaar Checks Fail
Almost always a mismatch: name, date of birth or gender entered differently from Aadhaar, or no working mobile number linked to it.
| Cause | What to check |
|---|---|
| Name mismatch | Spelling, initials, full stops and the order of names — "Ram Kumar Singh" is not "R.K. Singh" |
| Date of birth | Day, month and four-digit year identical |
| Gender | Recorded exactly as on Aadhaar |
| Mobile number | Linked to Aadhaar, active, and able to receive the OTP |
Did you know?Updating only the mobile number linked to Aadhaar does not need supporting documents — the Aadhaar card itself is enough at an Aadhaar centre.
Fix the Data at Source
Compare the portal entry with a current e-Aadhaar field by field; correct your entry, or have the farmer update Aadhaar if the record itself is wrong.
- Get the current record: a recent Aadhaar copy, or the e-Aadhaar downloaded from uidai.gov.in.
- Compare field by field with the NMNF entry and correct any typing error on your side.
- Check the mobile link with UIDAI's official verify-mobile service.
- If Aadhaar itself is wrong, the farmer visits an Aadhaar Seva Kendra with supporting documents; a mobile number update needs only the Aadhaar.
- Keep the URN (update request number) and retry enrolment only once the update shows as complete.
Checking details and guiding a farmer through an update takes 10–15 minutes each, before any travel. For 75 farmers that is more than 12 hours of staff time.
When the Data Is Right but It Still Fails
Rule out the browser and connection, avoid repeated retries, and escalate to portal support with the exact error.
- Clear cache and cookies, restart the browser, or try another browser.
- Use a stable connection — an interrupted OTP exchange fails the check.
- Do not retry repeatedly: repeated failed authentications can be blocked for a while by the system, so pause before trying again.
- Escalate to NMNF portal support with a screenshot and the steps already tried.
For enrolment and cluster set-up, see Agency Guide: NMNF Enrollment & Cluster Formation.
Check yourself
Tap an answer to see whether you are right, and why.
The portal shows a demographic mismatch. What do you check first?
- Your internet
- Name, date of birth and gender against Aadhaar
- The cluster status
Mismatches between the portal entry and the Aadhaar record are the most common cause.
The farmer's Aadhaar record itself has a wrong spelling. Who fixes it?
- You, on the NMNF portal
- The farmer, through an Aadhaar update
- The Regional Council
Only an Aadhaar update corrects the record; the portal entry must match what Aadhaar holds.
Remember these things
- Match Aadhaar exactly, field by field.
- Confirm the linked mobile can receive the OTP.
- Suspect the portal only after the data is right.
Most Aadhaar rejections are data problems, fixed at source before the portal is tried again. KrushiFlow validates these fields and submits farmer records to the portal in bulk.