UDISE Plus SDMS APAAR ID 2026-27 – "Generated" Does Not Always Mean Valid

UDISE Plus SDMS APAAR ID Status 2026-27 — Generated Pending Deactivated
UDISE Plus SDMS APAAR ID Status 2026-27 — Generated Pending Deactivated
🏛
Official UDISE+ Portal: This guide is based on the official UDISE+ Portal — udiseplus.gov.in. For login, data entry, and all official UDISE+ services, always go directly to the official portal.

When "APAAR Generated" Does Not Mean What You Think

The SDMS dashboard showed "APAAR Generated" for all 340 students. You submitted. Two weeks later, the BRC sends data back. You open SDMS and check the APAAR status list — 28 students show "Deactivated," 12 show "Pending," 4 have a note that reads "Duplicate Record Found." The school operator generated all of them correctly. The status changed after submission.

"APAAR Generated" on screen during data entry does not mean the APAAR is in a final, valid state. APAAR status can change after submission, after BRC processing, after data unlock, and even after certification. Each status means something different and needs a different action.

This page explains what each APAAR status in SDMS means, why statuses change after BRC involvement, and how to resolve duplicate APAAR records — the one problem schools cannot fix without external help.

🔍
APAAR status problems covered in this guide:
  • APAAR status meanings: Generated / Pending / Deactivated / Duplicate / Not Generated
  • Why APAAR deactivates after BRC unlocks and returns data
  • How duplicate APAAR records form and who resolves them
  • APAAR shows on screen but is not saved permanently
  • State-wise SDMS differences in APAAR generation behavior
  • After certification — generating APAAR for students who were missed

APAAR Status Guide: Generated, Pending, Deactivated, Duplicate, Not Generated

StatusWhat It MeansAction Required?What to Do
GeneratedAPAAR ID created and confirmed by UIDAI — valid and activeNoVerify the 12-digit ID is visible in the student's profile. No further action.
PendingAPAAR generation requested but confirmation not yet received from UIDAIWait 24-48 hours firstIf still Pending after 48 hours, re-open GP and re-authenticate Aadhaar.
DeactivatedAPAAR was generated but has been deactivated — usually because Aadhaar details were corrected or a duplicate was resolvedYes — must regenerateVerify Aadhaar details, re-authenticate, generate new APAAR ID.
Duplicate FoundSame Aadhaar is registered in SDMS under two different student recordsYes — requires BRC involvementReport to Block MIS Coordinator with both student names. Do not create a third entry.
Not GeneratedAPAAR process was not completed — Aadhaar not entered, authentication failed, or consent not checkedYes — must generateEnter Aadhaar, tick consent checkbox, authenticate, generate APAAR ID.

Problem: APAAR Deactivates After BRC Unlocks Data

You submitted with "Generated" for all students. BRC unlocked data for a correction. After BRC action, some APAARs show "Deactivated." Why?

When BRC unlocks and returns data, they sometimes correct student records from their end — especially if they noticed an Aadhaar mismatch or a student appearing in two schools. When they modify the linked Aadhaar or change the student's school association, the system may automatically deactivate the original APAAR as part of the correction process.

What to do after BRC returns data:

  1. Check the APAAR status list in SDMS — look for any student whose status changed from "Generated" to "Deactivated"
  2. For each deactivated APAAR, open the student's GP
  3. Check if the Aadhaar number or name in GP has changed from what you entered
  4. If changed: BRC corrected an error — re-authenticate with the corrected Aadhaar and regenerate APAAR
  5. If unchanged: ask the BRC what caused the deactivation — they can tell you which system action triggered it
  6. After regenerating, save and check the new APAAR ID before resubmitting

Problem: Duplicate APAAR Records — How They Form and Who Resolves Them

A duplicate APAAR record means the system has linked one Aadhaar number to two different SDMS student profiles. This almost always happens because:

  • A parent handed the same Aadhaar card for two siblings and the data entry operator used it twice
  • Two different schools registered the same student with the same Aadhaar — one school did not mark them as Transfer Out
  • A student's Aadhaar number was entered with one digit wrong and coincidentally matched another real student's Aadhaar in the database

What schools can do:

  1. Do not create a new entry. Do not delete any existing entry.
  2. Note the student's name, class, and APAAR ID (if showing), and the duplicate notification details
  3. Contact Block MIS Coordinator with this information
  4. The BRC investigates at district level — they can see which school's record is the original registration and which is the duplicate
  5. Resolution typically takes 3-7 days. In the meantime, save the student in SDMS without APAAR ID — do not leave data entry incomplete while waiting
⚠️
Schools cannot resolve APAAR duplicates independently. Any attempt to delete or overwrite one of the records will make the situation worse. Report it and wait for district-level resolution.

Problem: APAAR Generates on Screen But Is Not Saved Permanently

Authentication succeeds. The 12-digit APAAR ID appears on screen. You close the student profile. When you reopen it, the APAAR field is blank.

Two causes:

  • Consent checkbox was not ticked. In SDMS, you must check the parent consent checkbox before you click "Generate APAAR ID." If you leave it unchecked, most portals display the APAAR during the current session but do not save it to the database. When you close the tab or log out, it disappears. Fix: open GP, tick the consent checkbox, save GP, re-authenticate Aadhaar, generate APAAR again in one uninterrupted process.
  • Session expired during the APAAR generation process. If the OTP took a long time to arrive and the portal session expired before you clicked Generate, the system orphans the authentication result. The system displayed a temporary APAAR ID that it never committed to the database. Fix: log out, log back in, re-authenticate Aadhaar with a new OTP, and generate APAAR in a single session without delays.

State-Wise SDMS Differences in APAAR Behavior

SDMS is the national portal at sdms.udiseplus.gov.in, but states customize its behavior. A few things that vary by state:

  • Consent form requirement: Some states require you to upload a physical paper consent form as a scanned document before you can generate the APAAR. Other states only require the consent checkbox in the portal. If the portal blocks APAAR generation without showing an upload option, ask your BRC whether they require a scanned consent form upload in your state.
  • OTP delivery: All states use OTP to the parent's Aadhaar-linked mobile for student APAAR generation. If the same mobile number is used across multiple children's Aadhaar cards, the OTP arrives for the Aadhaar being authenticated — make sure the parent knows which child's OTP to read out.
  • State-specific login URL: Direct login links include a state-id parameter (for example, sdms.udiseplus.gov.in/p3/v1/login?state-id=109 for UP). Using your state's direct link sometimes resolves login timeouts that happen on the generic login page when server load is high. Ask your BRC for your state's direct SDMS login URL if you experience frequent timeouts.

For state-wise SDMS direct login links for all 36 states and UTs, visit our State-Wise SDMS Login page.

After Certification — Can You Still Generate APAAR for Missed Students?

After district certification, the district locks the SDMS data. However, you can sometimes still complete APAAR ID generation for students whom you missed — because the system treats APAAR generation as an ongoing requirement separate from the annual data certification deadline.

What is possible after certification:

  • In many states, BRC can unlock specific student records for APAAR generation even after district certification — because APAAR completion is a continuous program requirement, not just an annual data field
  • Contact your Block MIS Coordinator and ask specifically whether APAAR completion is possible for students who were missed. If yes, they will unlock those specific records.
  • If you cannot generate the APAAR post-certification for the current year, you must complete it at the start of the next year's data entry before you apply any promotions to those students
After completing APAAR generation, note each student's APAAR ID in the school register. Do not rely only on the SDMS portal to store this. APAAR IDs can change if you make corrections — a physical record protects the school if the portal shows a different status later.

❓ Frequently Asked Questions (FAQs)

Here are the most common questions people ask about UDISE Plus SDMS APAAR ID 2026-27 – "Generated" Does Not Always Mean Valid.

"APAAR Pending" means the operator has submitted the generation request to UIDAI, but the system has not yet received confirmation. This can happen when the UIDAI Aadhaar authentication service is slow or when the SDMS and UIDAI systems are out of sync. In most cases, "Pending" APAARs resolve to "Generated" within 24-48 hours without action. If a record stays in "Pending" for more than 3 days, re-open the student's GP, re-authenticate Aadhaar, and attempt APAAR generation again. If authentication fails this time, the Aadhaar details may have a mismatch that you must correct first.
A deactivated APAAR ID is not linked to active scholarship systems, which means the student's government scholarship status may show as incomplete. Once you generate a new APAAR, report the old ID and new ID pair to your Block MIS Coordinator so they can flag the change in block-level records. Do not delay regeneration — the longer the APAAR stays deactivated, the more scholarship and benefit records fall out of sync for that student.
This happens for two reasons: (1) You did not tick the parent consent checkbox before generating the APAAR for those 30 students — the APAAR appeared on screen during the session but the system did not save it permanently. (2) The APAAR generation happened but a system error prevented the save — these records show as if you never generated them. Fix: check the 30 students' GP sections one by one. For any student where you left the consent checkbox unchecked, tick it, save GP, then re-authenticate and regenerate APAAR.
Same APAAR ID for two students means the operator entered one of their Aadhaar numbers incorrectly — the operator used the same Aadhaar for both students accidentally. You cannot resolve this system-level error from the school portal. Report to your Block MIS Coordinator with both students' names and the duplicated APAAR ID. The BRC will contact the SDMS district team to investigate which student legitimately owns the APAAR. For the other student, you must correct the Aadhaar and regenerate the APAAR.
Yes, and this is the correct process for transfer students. The APAAR ID belongs to the student, not the school. When a student transfers, the new school searches for them in SDMS using their Aadhaar number, finds their existing APAAR ID, and clicks "Link to My School." The APAAR ID does not change — only the linked school changes. The new school can view the student's academic history from the previous school through the APAAR record.
The Report Module reflects certified data, while SDMS shows current portal status. If you generated the student's APAAR after the BRC certified the data — or if the BRC certified the data before you completed the APAAR generation — the certified report will show a blank APAAR. The APAAR in SDMS is correct and current. After the next certification cycle, when BRC re-certifies or you certify any data update, the report will reflect the APAAR ID. This discrepancy is normal during the active data entry period.

✅ Conclusion

APAAR ID status in SDMS can change after submission, after BRC unlock, and even after certification — in ways that are not obvious from the school dashboard. "Generated" at submission time does not guarantee "Generated" after BRC processing. The safest practice is to note each student's APAAR ID after generation, check the status list again after BRC returns data, and regenerate any APAARs that show as "Deactivated" or "Pending" before resubmitting. For duplicate APAAR records, the only path to resolution is through the Block MIS Coordinator — schools cannot resolve APAAR duplicates on their own.

Pooja Sharma
Written By

Pooja Sharma

Teacher & Contributor 🎓 BSc. (Physics), MSc. (Physics) and BEd.

Pooja Sharma is a qualified physics graduate (BSc, MSc) and certified teacher (BEd). As an active educator and contributor, she simplifies complex school portal processes, student registrations, and educational data entry tasks for academic administrators.

🗺️ Direct SDMS Login – Quick Access by State

Click your state below for the direct UDISE Plus SDMS login link and complete data entry guide.

All 39 States & UTs →