Skip to main content

CALPADS error brief · IVR

IVR0007

Invalid SSID
Severity Fatal
Error type Input Validation
Record type IVR

Official CALPADS rule

What CALPADS is rejecting

SSID must be a valid CALPADS SSID in the ODS

Focus fields

Fields validated

1.08 - SSID

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: SSID must be a valid CALPADS SSID in the ODS

Severity: Fatal   Type: Input Validation

Field validated:

  • 1.08 SSID

Version 18 structure: 10 numeric digits; the first digit cannot be zero; the final digit is a calculated check digit.

Three different questions must be answered

A number can pass one test and fail another
Validation layerQuestionWhy it matters
FormatDoes the value contain exactly ten numeric digits, begin with 1–9, and satisfy the check-digit rule?A local ID, truncated SSID, extra space, or transposed digit can fail before CALPADS finds a student.
ODS existenceDoes that exact SSID currently exist as a valid CALPADS identifier?A mathematically plausible number is not valid merely because its format works.
Student identityDoes the valid SSID actually belong to this student?Using another student’s valid SSID can pass an existence check while corrupting both students’ histories.

What commonly produces IVR0007

Symptoms, evidence, and durable corrections
Failure patternWhat it looks likeDurable correction
Duplicate SSID was mergedThe SIS still submits an older SSID after CALPADS combined multiple identifiers under a surviving Focus ID.Confirm the posted MID resolution, update the student to the surviving SSID, and replace the retired value across connected systems.
New SSID requested at each schoolThe same student has separate SSIDs associated with different schools or LEAs and similar demographics.Research the complete history and resolve the MID through the authorized CALPADS process; do not pick one informally.
Local student ID submitted as SSIDA familiar district or school identifier appears in field 1.08.Keep the statewide SSID in 1.08 and the LEA’s local identifier in 1.09.
Transcription or spreadsheet damageA digit is missing, transposed, rounded, displayed in scientific notation, or converted to text with spaces.Recover the authorized ten-digit SSID from a trusted source and preserve the field as text.
Wrong student’s SSIDThe number exists, but identity or enrollment details belong to another student.Stop the submission, separate both student records, and perform an identity review before correcting either record.
Stale import or interfaceThe SIS was corrected, but special education, assessment, food service, data warehouse, or another integration restores the old SSID.Identify the system of origin, govern the surviving identifier, and update every interface and scheduled job.
SSID entered where it should be blankAn Add/Update workflow intended to find or obtain the student carries an unverified number.Use the authorized SSID matching/request process and follow current transaction rules; never invent a value to satisfy the field.
Row or column misalignmentA valid-looking ten-digit value from another field shifts into position 1.08.Repair the structural layout before changing student identifiers.

Never merge students based only on a matching name and birth date. Twins, siblings, repeated names, data-entry errors, and shared demographic patterns can create false matches. Conversely, legitimate name, gender, birthplace, guardianship, or demographic changes can make one student appear different across time. Reconcile the complete identity and enrollment history.

Build an identity reconciliation packet

Evidence to compare before selecting or combining an SSID
Evidence groupComparePossible explanation for differencesWho may verify
Legal identityLegal first, middle, last, suffix, prior names, and documented changes.Name change, adoption, guardianship, punctuation, spacing, transliteration, or data-entry error.Authorized registrar/student-records staff using approved documentation.
Birth informationBirth date, city, state/province, and country.Transposition, default values, incomplete cumulative records, or genuine different students.Authorized staff using cumulative records or accepted identity documentation.
Enrollment historySchools, LEAs, start/exit dates, grades, and overlapping enrollments.Transfers, concurrent enrollment, short-term enrollment, duplicated records, or fragmented SSIDs.CALPADS coordinator and enrollment staff, potentially across LEAs.
Local identifiersDistrict, school, SIS, special-education, and prior-system IDs.Each organization may assign its own local identifier to the same student.SIS/data owners and prior LEA anomaly contacts.
Program and longitudinal historyELAS, special education, program participation, assessment, completion, and cohort records.Records may be split across duplicate SSIDs or legitimately differ over time.Authorized program owners working through the CALPADS coordinator.
Family/contact contextOnly the minimum authorized contextual evidence needed to distinguish students.Shared households, siblings, guardianship changes, and privacy restrictions.Authorized records staff under local privacy procedures.

Understand the MID reconciliation decision

1. Candidate SSIDsCALPADS or local research identifies two or more identifiers that may represent one student.
2. Evidence reviewAuthorized staff compare demographics, local IDs, schools, dates, and longitudinal records.
3. DispositionCombine true duplicates under the appropriate Focus ID—or mark them as different students when they are not duplicates.
4. Post-resolution repairUpdate the SIS and every downstream system to use the surviving SSID and reconcile resulting records.

CALPADS identifies a Multiple Identifier anomaly when two or more SSIDs have exactly matching or very similar demographics. Its MID interface supports combining SSIDs with a Focus ID or marking a candidate as a known non-anomaly. Review any predicted fatal errors and concurrent-enrollment consequences before posting the resolution.

Choose the diagnostic pathway

  • Inspect the literal SSID
    • What exact characters appear in field 1.08?
    • Does the value contain exactly ten digits?
    • Does the first digit begin with 1–9?
    • Are there spaces, punctuation, scientific notation, rounding, or a transposed digit?
    • Does the full SENR row remain structurally aligned?
  • SSID versus local student ID
    • Does field 1.08 contain the statewide SSID or a district/school identifier?
    • What value appears in field 1.09 Local Student ID?
    • Did an import or crosswalk swap the two fields?
    • Do different local systems use different identifiers for the same student?
    • Which field is authoritative for statewide identity?
  • Possible duplicate or retired SSID
    • Does the student appear in an unresolved or resolved MID set?
    • Was this SSID recently combined under another Focus ID?
    • Which SSID is active after the posted resolution?
    • Did another LEA participate in the MID set?
    • Which local systems still store the retired identifier?
  • Confirm the person—not just the demographics
    • Do legal name, prior names, birth information, gender, and birthplace evidence support one person?
    • Do the enrollment histories form a plausible sequence?
    • Are overlapping enrollments legitimate or evidence of duplication?
    • Could the records represent twins, siblings, or different students with similar demographics?
    • What authorized documentation resolves the ambiguity?
  • Coordinate across schools or LEAs
    • Which schools and LEAs created or used each SSID?
    • Who are the authorized anomaly contacts?
    • Can each LEA confirm local IDs, enrollment dates, and source records?
    • Which organization owns the current Focus ID?
    • How will corrections be coordinated without transmitting more student information than necessary?
  • SIS and downstream systems
    • Where is the SSID stored and which system is authoritative locally?
    • Which imports can overwrite the corrected value?
    • Do special education, assessment, meal, program, transcript, and data-warehouse systems use the same surviving SSID?
    • Are historical records linked rather than duplicated?
    • Will the next scheduled extract reproduce the invalid identifier?

Resolve identity before rebuilding history

  1. PreserveCapture both identifiers.
  2. ResearchCompare identity and history.
  3. ResolvePost the MID disposition.
  4. RepairUpdate every system.
  5. ReconcileVerify longitudinal records.

Primary participants for this error

  • CALPADS coordinator and anomaly contact
  • Registrar or authorized student-records staff
  • Current and prior LEA contacts when applicable
  • Program owners affected by fragmented records
  • SIS system owner and integration/vendor support

Choose the owner from the pattern

  • Malformed number: SIS/extract owner.
  • Wrong student: authorized identity review.
  • MID or retired SSID: CALPADS anomaly process.
  • Old value returns: downstream integration owner.

Recommended correction path

  1. Stop and preserve the rejected evidence

    Capture the submission ID, row, field 1.08, Local Student ID, error details, untouched file, and source-system record before editing.

  2. Rule out a simple format or alignment defect

    Inspect the ten digits, check-digit structure, spaces, spreadsheet conversion, field positions, and any swap with Local Student ID.

  3. Search the authorized CALPADS identity history

    Determine whether the SSID exists, was merged or retired, appears in a MID set, or belongs to another student.

  4. Assemble and compare identity evidence

    Reconcile legal names, birth information, local identifiers, schools, grades, enrollment dates, and relevant longitudinal records.

  5. Coordinate the MID disposition when needed

    Work with authorized anomaly contacts across affected schools or LEAs to combine true duplicates or mark different students as non-anomalies.

  6. Confirm the active surviving SSID

    Use the Focus ID established by the posted CALPADS resolution; do not choose a number based on age, convenience, or local preference.

  7. Repair the complete local ecosystem

    Update the SIS and governed crosswalks, then correct every authorized downstream system and interface that carries the retired or wrong SSID.

  8. Resubmit and reconcile longitudinal history

    Confirm IVR0007 clears, then review enrollments, demographics, ELAS, programs, special education, assessment, completion, cohort, and duplicate/concurrent anomalies.

Official CALPADS rule and operational expansion

Official rule: SSID must be a valid CALPADS SSID in the ODS.

Operational expansion: Verify the literal identifier, search for the student’s existing statewide identity, and determine whether a posted MID resolution changed the active SSID. If multiple identifiers may represent one student, reconcile them through CALPADS rather than assigning or selecting an SSID informally.

Before closing the issue

  • Confirm field 1.08 contains the active ten-digit SSID for the correct student.
  • Verify field 1.09 separately contains the correct Local Student ID.
  • Confirm any MID disposition is posted and the surviving Focus ID is documented locally.
  • Reconcile legal identity, enrollment chronology, and affected longitudinal records.
  • Update connected systems and prevent stale imports from restoring the retired SSID.
  • Review other students created or transferred through the same matching and SSID-request process.

Official SENR IVR0007 troubleshooting page  |  CALPADS Multiple Identifier resolution guidance  |  SSID Match Tool guidance  |  Current CALPADS system documents

Statewide SSID versus local student ID

  • SSID—field 1.08: a ten-digit statewide identifier maintained in CALPADS. It follows the student across California schools and LEAs.
  • Local Student ID—field 1.09: an identifier assigned by an LEA. The same student may receive a different local ID in each LEA.
  • School-system or application IDs: additional internal identifiers may exist in special education, assessment, food service, transportation, learning, or other systems.
  • Local Special Education Student ID: another program-specific identifier that is not automatically the statewide SSID.

SSID reconciliation participant directory

Engage only authorized roles needed for the identity, MID, enrollment, or system-repair issue.

  • CALPADS coordinator or anomaly contact
  • Registrar or enrollment staff
  • Authorized student-records staff
  • Current or prior LEA anomaly contact
  • Special education data staff when affected
  • SIS and identity-governance owner
  • Extract, integration, or vendor support