Skip to main content

CALPADS error brief · SENR

SENR0013

Enrollment Start Date Less Than Birth Date
Severity Fatal
Error type Input Validation
Record type SENR

Official CALPADS rule

What CALPADS is rejecting

Enrollment Start Date must be greater than Student Birth Date

Focus fields

Fields validated

1.17 - Student Birth Date 1.22 - Enrollment Start Date

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: Enrollment Start Date must be greater than Student Birth Date.

Severity: Fatal   Type: Input Validation

Fields validated:

  • 1.17 Student Birth Date
  • 1.22 Enrollment Start Date

Both dates must be real calendar dates represented as eight digits in CCYYMMDD order, and field 1.22 must occur later than field 1.17.

Do not “change either date” merely to clear the error. Birth Date is a legal demographic/identity value. Enrollment Start Date describes a documented school event. Each has different evidence, owners, and downstream consequences. Change only the value authoritative records establish as wrong.

Read the two dates as a sequence

Illustrative examples—format alone does not establish accuracy
Birth DateEnrollment Start DateResultWhat it suggests
2017081420260812Valid sequenceThe enrollment occurs after birth; separately verify the student, age, grade, and actual start date.
2027081420260812InvalidThe Birth Date may contain a wrong year or century.
2017081420160812InvalidThe Enrollment Start Date may contain the wrong year.
2017081420170814Invalid“Greater than” does not permit the two dates to be equal.
2009050720260507Valid sequence, possible concernThe rule passes, but staff should still verify whether the age and grade context are plausible.

Verify each date from the appropriate source

Separate identity evidence from enrollment-event evidence
ValueEvidence to compareCorrection boundary
1.17 Student Birth DateSIS demographic record, cumulative file, and—when authorized and available—birth certificate or other locally accepted identity documentation.Use the LEA’s authorized demographic-correction process. A birth-date correction may require SINF/SSID reconciliation.
1.22 Enrollment Start DateEnrollment application, first expected attendance date, attendance, transfer information, school calendar, and surrounding CALPADS enrollment history.Correct the enrollment record and any operational-key implications; do not alter identity data to preserve a mistaken start date.
Student/SSID matchLegal name, local student ID, SSID, birth date, school, and enrollment evidence viewed together.If the row belongs to another student, correct the identity linkage or extract selection before editing either date.
Raw SENR exportUntouched delimited row, exact column positions, field mapping, and comparison with a known accepted row.If SIS values are correct but the file is wrong, repair the report, integration, or mapping—not the source facts.

What commonly produces SENR0013

Symptoms, likely causes, and durable corrections
What you findLikely causeDurable correction
Birth month/day look right; year is later than enrollmentThe birth year was mistyped, defaulted to the current year, or expanded to the wrong century.Verify the full birth date and correct it through the authorized demographic process.
Enrollment month/day look right; year predates birthA rollover, pre-enrollment record, or copy-forward process retained the wrong year.Verify the actual start event and correct the enrollment source.
The two values are identicalOne date was copied into both fields or the same source column was mapped twice.Repair the source entry or field mapping; equality does not satisfy this rule.
SIS dates are correct; file dates are reversedFields 1.17 and 1.22 were swapped or column positions shifted.Correct the extract layout and inspect other date columns and students.
Birth date belongs to another childSibling, duplicate student, or wrong local-ID/SSID crosswalk contaminated the row.Reconcile identity first; do not manufacture a chronology for the wrong person.
Start date resembles a birth dateAn import or report mapped the demographic field into the enrollment field.Correct the mapping and regression-test the entire batch.
Many records share the same impossible dateA placeholder, default, spreadsheet conversion, or bulk import defect was exported.Repair the systemic source and identify every affected student.

Choose the diagnostic pathway

  • Inspect the literal submitted values
    • What exact eight characters appear in fields 1.17 and 1.22?
    • Are the columns in the correct positions?
    • Are both values in CCYYMMDD order?
    • Is the start date earlier than or equal to the birth date?
    • Did a spreadsheet or integration transform either value?
  • Confirm the student and SSID
    • Does the row belong to the intended student?
    • Do legal name, local student ID, SSID, and birth date align?
    • Could a sibling, duplicate, retired SSID, or merged identity be involved?
    • Does CALPADS already contain a conflicting demographic history?
  • Verify Student Birth Date
    • What does the cumulative file establish?
    • When authorized and available, what does accepted identity documentation establish?
    • Was the year or century mistyped?
    • Was a prior birth-date correction completed in both SIS and CALPADS?
  • Verify Enrollment Start Date
    • When was the student first expected to attend this school for this enrollment?
    • Do registration, attendance, transfer, and school-calendar evidence agree?
    • Was a rollover, pre-enrollment, or copy-forward year used?
    • Does the date fit the surrounding CALPADS enrollment sequence?
  • Trace SIS and extract behavior
    • Are both SIS values correct?
    • Did the extract swap, duplicate, default, or reformat them?
    • Will the next scheduled file reproduce the same conflict?
    • How many records share the same report, import, or mapping?
  • Review downstream consequences
    • Will a birth-date change affect identity matching, SINF history, age, grade, assessment, or special education?
    • Will a start-date change affect the SENR operational key, attendance, programs, SELA, overlaps, cohort, or reporting ownership?
    • Does the corrected record remain consistent across CALPADS?

Reconstruct the chronology from evidence

  1. StudentConfirm identity and SSID.
  2. BirthVerify the demographic fact.
  3. EnrollmentVerify the school event.
  4. ExtractInspect both fields.
  5. CALPADSConfirm the accepted sequence.

Primary participants

  • Registrar or enrollment staff
  • Authorized student-records staff
  • CALPADS coordinator
  • SIS demographic and enrollment owners
  • Extract, integration, or vendor support

Keep the evidence streams separate

  • Birth Date: identity documentation and demographic process.
  • Start Date: enrollment and attendance evidence.
  • Student match: identity and SSID reconciliation.
  • File values: report and integration verification.

Recommended correction path

  1. Preserve the rejected row

    Capture the submission ID, row number, SSID, exact field 1.17 and 1.22 values, and untouched extract.

  2. Confirm the intended student

    Match legal identity, local student ID, SSID, school, and enrollment before editing either date.

  3. Read the chronology literally

    Confirm both values are real CCYYMMDD dates and identify whether start is earlier than or equal to birth.

  4. Verify the birth date independently

    Use the cumulative file and, when authorized and available, the birth certificate or other accepted identity documentation.

  5. Verify the enrollment start independently

    Use registration, first expected attendance, attendance, transfer, calendar, and surrounding enrollment evidence.

  6. Find the first divergence

    Determine whether the wrong value originated in source entry, identity linkage, enrollment workflow, import, report, integration, or spreadsheet handling.

  7. Correct the authorized owner

    Use the demographic process for Birth Date and enrollment process for Start Date; address any SENR key or SINF implications.

  8. Regenerate and verify

    Confirm SENR0013 clears and the accepted record remains attached to the correct student with a plausible chronology.

  9. Review the larger population

    If a default, import, mapping, or transformation caused the conflict, identify every record processed by the same mechanism.

Before closing the issue

  • Confirm both dates belong to the intended student and enrollment.
  • Verify Enrollment Start Date is later than Student Birth Date.
  • Confirm the complete dates—not merely their order—are supported and plausible.
  • Reconcile any Birth Date correction through SINF and authorized demographic procedures.
  • Review operational-key and downstream effects of any Enrollment Start Date correction.
  • Check other students affected by the same source, import, or extract logic.

Official SENR0013 troubleshooting page  |  CALPADS SENR guidance  |  CALPADS Student Information guidance