NIN Not Found — Three Reasons NIMC Returns 'No Record'

Three causes account for almost every "NIN not found" response in the wild. They have nothing to do with each other and they each take a different fix. Before you spend a naira or a day on this, work out which one applies to your case.

• A typo or wrong NIN entered at the verifier. The most common cause, and the easiest to fix. The verifier captured the wrong eleven digits or transposed two characters. Your record is fine. The fix is at the bank, the telco, or the form, not at NIMC.
• A record temporarily in a pending state after a recent modification. If you submitted a name, date-of-birth, or address change on the self-service portal in the last few days, your record can sit in a transitional state where verifiers fail to resolve it cleanly. The fix here is patience — sometimes paired with a verifier-side ticket — not another modification.
• A pre-enrolment that never actually completed at the centre. A reader who filled the pre-enrolment form online, printed the Pre-Enrolment Slip, but never had biometrics captured, has no NIN at all. The slip is not the NIN. Every verifier returns "no record" because no record exists yet.

Sort yourself into one of the three before doing anything else. Wrong diagnosis here costs a week of cycles and sometimes a duplicate-NIN problem that takes longer to unwind than the original issue. If the issue is that NIMC found the record but the data on it disagrees with your form, that is a different problem — see NIN validation failed for the field-mismatch flow.

The cheapest cause to diagnose and the cheapest to fix. The eleven-digit NIN you submitted to the bank or the form is not the one NIMC actually issued you, or the verifier's data-capture clerk fat-fingered it on intake.

Diagnose with a single USSD call. Dial Dial *346# from the SIM linked to your NIN. Works on MTN, Airtel, Glo and 9mobile. Select option 1 for NIN retrieval. The NIN is displayed once and also delivered by SMS. in a one-line summary: from the SIM linked to your NIN, dial *346#, and the official short code returns your eleven-digit NIN on screen and by SMS. The cost is ₦50 in telco airtime, not a NIMC fee. If the eleven digits returned by USSD match what you submitted to the verifier, this cause is ruled out. If they do not, you have your fix.

Once you have the correct NIN in hand, the route forward is:

• Re-enter the right value at the verifier. Resubmit the form, re-link the bank account, retry the SIM registration. Verification should succeed on the corrected input.
• Where the verifier is a closed system that won't let you re-enter (an HR portal, a JAMB profile after lock), open a support ticket with the verifier's helpdesk and ask them to update the captured NIN to the value on the slip.

If you cannot use USSD because the linked SIM is lost or blocked, how to retrieve your NIN walks through the alternative channels — the NIMC MobileID app, the SMS retrieval, and the in-person enrolment-centre retrieval. Until you can confirm the correct NIN, there is no point speculating about the other causes.

The second cause is the one most readers do not consider because nothing visibly changed. Your NIN existed yesterday. A verification succeeded last week. Today the same verifier returns "no record".

If you submitted a modification on the self-service portal in the last few days — a name correction, a DOB change, an address update, a phone-number swap — your record can sit in a state where the live NIMC view is in flight between the old data and the new. Verifiers pulling fresh records during that window sometimes return "no record" rather than the partially-updated value.

The same effect appears when NIMC re-runs deduplication against your record. A second enrolment surfacing in the deduplication queue can briefly mark both records as pending while NIMC reconciles them.

The fix here is patience, with two practical steps in parallel:

• Wait 24 to 72 hours. Most pending states resolve in that window. Retry the verification on day two; do not modify in the meantime.
• Open a verifier-side ticket if the issue is time-critical. A bank or telco that holds a ticket reference is more likely to push a manual refresh once NIMC's record settles. State plainly: "NIN modification in progress, please re-verify after 72 hours." Attach the new slip once it is issued.

Do not submit another modification while one is in flight. NIMC processes modifications through a single review queue per field, and a second submission against an unsettled record produces a confused review and slows the cycle for both. The self-service portal does not show the pending state explicitly — you find out by retrying the verifier two days later.

The cause readers most want not to be theirs, and the one that takes the longest to fix. A reader who filled the pre-enrolment form at penrol.nimc.gov.ng, printed the Pre-Enrolment Slip with its barcode, and walked away believing the enrolment was done — but never went to a centre for biometrics, or went but the capture failed.

The structural truth: the NIN is issued only after biometrics are captured at an enrolment centre. The pre-enrolment slip carries an Application Reference Number, not a NIN. Until fingerprints, facial image, and signature are captured against that reference, no NIN exists. Every verifier in Nigeria returns "no record" because there genuinely is no record.

Diagnose by asking three questions.

• Do you have an eleven-digit NIN written on any document NIMC issued you? Not the pre-enrolment slip's reference number, but a separate eleven-digit number on a NIN slip, a national e-ID card, or an SMS NIMC sent. If the answer is no, the enrolment may never have completed.
• Has the USSD *346# from your originally registered SIM ever returned a NIN? If not, and you have tried more than once on different days, the linked SIM either was never bound to a NIN or the binding failed because no NIN was ever issued.
• Did you receive a notification from NIMC after the centre visit? Successful biometric capture is usually followed by an email or SMS within 1 to 5 working days for minors and a few working days for adults. Silence over weeks suggests the capture did not register.

Where any one of those answers points to an incomplete enrolment, the fix is to complete the enrolment, not to start a fresh one. Return to the centre with your pre-enrolment slip's barcode and ask for the original capture to be completed against that reference. If the centre cannot find the original record, then and only then is a fresh enrolment the right route — and even then, alert the centre that an earlier attempt may exist so the deduplication engine catches the overlap rather than creating a duplicate. The full registration walkthrough is at how to register for NIN.

A fourth possibility sits outside the three causes because it has nothing to do with your record. NIMC's verification service has been down for extended periods, most publicly during the July 2025 vendor switch from the previous platform to Bluesalt, when banks, telcos, and the NIS passport portal all reported being unable to verify customers for weeks (Vanguard and Punch reported this in July 2025).

During a sustained outage, every verifier returns "no record" or "verification failed" regardless of the underlying database. No amount of modification will help. The diagnostic is to check whether multiple unrelated verifications (bank, telco, NYSC) all fail on the same day. If they do, the issue is upstream of you, and the fix is to wait until NIMC's status normalises.

Public reporting at vanguardngr.com, punchng.com, and biometricupdate.com is the most reliable signal — NIMC itself does not publish a status page. If a single verifier fails while others succeed, the outage explanation does not apply; revisit the three causes above.

The diagnosis above maps cleanly to a fix path. The order matters because each step rules out a cause cheaply before moving to the costlier ones.

1. 1
   Confirm the digitsDial *346# from the SIM bound to your NIN. If it returns an eleven-digit NIN, the record exists. Cross-check those digits against what the failing verifier captured. If they differ, you have a typo and the fix is at the verifier.
2. 2
   Check the date of any recent NIMC interactionIf you submitted a modification on the self-service portal in the last seven days, give the record 24 to 72 hours to settle and retry the verification on day two or three. Do not modify again in the interval.
3. 3
   Rule out a verification outageCheck whether unrelated verifiers (bank, telco, NYSC) all fail on the same day. If they do, the issue is upstream — wait and retry once public reporting confirms the service is back.
4. 4
   Confirm enrolment actually completedIf USSD returns nothing and no NIN was ever issued to you on a separate slip, the original enrolment likely did not finish. Return to the centre with your pre-enrolment reference and complete the capture against that record.
5. 5
   Open a verifier-side ticketIf the record exists but a specific verifier still returns 'not found' after a week, the issue is verifier-side — a stale cache or a captured-data error. Open a ticket with the bank or telco support and attach a fresh NIN slip.

Some verifiers report "no record" when the underlying issue is really a field mismatch. Banks running an older NIBSS integration sometimes fail at the name-comparison step but report it as a no-record error to the customer. Telcos with batch verification can return "not found" during the gap between submission and the verification round.

If the three causes above and the outage check all turn up nothing, treat the failure as a possible field mismatch and follow NIN validation failed instead. That guide walks through the field-by-field comparison and the per-surface decision tree. The diagnostic tools are the same; what differs is the underlying cause.

For the broader system context — how third-party verification actually works, why caches refresh on different schedules, and what stays out of NIMC's reach — see NIN verification — how it works.