Skip to main content

CALPADS error brief · SENR

SENR0018

Invalid Exit Date for the submitted Exit Reason
Severity Fatal
Error type Input Validation
Record type SENR

Official CALPADS rule

What CALPADS is rejecting

Enrollment Exit Date must be greater than or equal to Enrollment Start Date unless the Student Exit Reason Code = N470 (NoShowOther), in which case the date must be on or one day prior to the Start Date.

Focus fields

Fields validated

1.22 - Enrollment Start Date 1.25 - Enrollment Exit Date

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: Enrollment Exit Date must be greater than or equal to Enrollment Start Date unless Student Exit Reason Code equals N470 (NoShowOther). For N470, the Exit Date must be on or one day before the Start Date.

Severity: Fatal   Type: Input Validation

Fields validated:

  • 1.22 Enrollment Start Date
  • 1.25 Enrollment Exit Date

Conditioning field: 1.26 Student Exit Reason Code determines whether the ordinary sequence or N470 exception applies.

Do not simply swap the dates. Start Date and Exit Date represent different documented events. A reversed sequence may come from a wrong year, wrong enrollment segment, no-show coding error, copied date, field mapping defect, or correction to only one half of the chronology.

Three date patterns—not one

Illustrative examples using an Enrollment Start Date of August 17, 2026
Student/eventExit ReasonSupported Exit Date patternExample
Ordinary enrollment exitAny supported non-N470 reasonOn or after Enrollment Start DateStart 20260817; Exit 20260930
General-education no-showN470One day before Enrollment Start Date under the official resolutionStart 20260817; Exit 20260816
Student with disabilities no-showN470Equal to Enrollment Start Date under the official resolutionStart 20260817; Exit 20260817

The general Version 18 field validation describes N470 as equal to or one day before Start Date. The SENR0018 troubleshooting page gives the more specific general-education/SWD distinction shown above. Verify current special-education status and follow the current rule for the student; do not choose the version that merely clears the record.

Which field is actually wrong?

Use evidence to identify the correction owner
What the evidence showsLikely correctionImportant consequence
The student attended; Start Date is wrongCorrect field 1.22 to the supported first expected attendance date.Start Date is part of the SENR operational key; changing it requires the supported old-key delete/new-key add workflow.
The student attended; Exit Date is wrongUpdate field 1.25 to the supported last expected attendance date.Exit Date is not part of the SENR operational key, but reason, completion, attendance, and downstream chronology must still align.
The student never appeared; reason is not N470Verify and correct field 1.26, then apply the appropriate no-show date pattern.Do not backdate an ordinary transfer/withdrawal merely to fit the exception.
The student did attend; reason is N470Remove the no-show treatment and report the actual enrollment/exit event.N470 is not a shortcut for resolving overlap, absence, or delayed withdrawal.
The row belongs to another enrollment or studentCorrect the segment, SSID, or extract selection before editing dates.Changing dates can conceal an identity or operational-key mismatch.

Use N470 only for a genuine no-show

Questions to answer before applying the exception
QuestionEvidence to examineRisk if skipped
Was the student expected to attend?Enrollment/registration records, prior-year return status, placement, and school calendar.An inquiry or tentative application may be mistaken for an enrollment.
Did the student generate attendance?Daily attendance, classroom rosters, service logs, and school-site confirmation.A student who attended may be incorrectly erased as a no-show.
Was the no-show investigation completed?Local contact attempts, whereabouts review, transfer information, and authorized withdrawal documentation.The enrollment may be closed prematurely or with the wrong reason.
Is the student a student with disabilities?Current SWDS/plan status and authoritative special-education records for the applicable date.The wrong equal-date/one-day-prior pattern may distort special-education status reporting.
Are start, exit, and reason on the same segment?SIS enrollment key, raw SENR row, and CALPADS ODS history.Dates from different enrollments can form an artificial reversal.

What commonly produces SENR0018

Symptoms, likely causes, and durable corrections
What you findLikely causeDurable correction
Month/day look correct; years are reversedRollover, copy-forward, or manual entry assigned the wrong academic year.Verify both events and correct the owning enrollment record.
Start and Exit Dates were swappedExtract mapping or spreadsheet column handling reversed fields 1.22 and 1.25.Repair the file layout and regression-test other dates.
Exit is one day before start, but reason is not N470Staff applied no-show date logic without the qualifying reason.Reconstruct the actual outcome and correct reason/dates together.
N470 with a much earlier exitA prior segment’s date or arbitrary backdate was used.Apply the exact current no-show date rule for the student’s status.
SWD status differs between teamsSIS, special-education system, and CALPADS effective records are not synchronized.Resolve status for the applicable date before choosing equal or prior-day treatment.
SIS chronology is correct; file is notThe extract joined different enrollment segments or selected a stale exit.Repair segment/key selection and inspect the broader population.
A Start Date was corrected without replacing the keyOnly the new value was transmitted, leaving the old SENR record behind.Use the coordinated old-key delete/new-key add workflow and reconcile both records.

Choose the diagnostic pathway

  • Inspect the complete rejected row
    • What exact values appear in fields 1.22, 1.25, and 1.26?
    • Are dates in CCYYMMDD format and correct columns?
    • How many days separate them?
    • Do they belong to the same student, school, and enrollment key?
    • What enrollment history already exists in CALPADS?
  • Verify ordinary enrollment chronology
    • When was the student first expected to attend?
    • Did the student attend?
    • When was the student last expected to attend?
    • What circumstance ended the enrollment?
    • Do attendance, withdrawal, transfer, and completion evidence agree?
  • Verify an N470 no-show
    • Was the student truly expected but never appeared?
    • Was the local no-show investigation completed?
    • Is N470 supported rather than defaulted?
    • Is the Exit Date equal to or exactly one day before Start Date as applicable?
    • Did the student generate any attendance or services?
  • Determine disability status for the applicable date
    • Do authoritative special-education records identify the student as a student with disabilities?
    • What effective SWDS/plan record applies?
    • Are SIS, special-education system, and CALPADS synchronized?
    • Has the special-education data owner confirmed the equal-date treatment?
  • Assess operational-key implications
    • Is Enrollment Start Date the value being corrected?
    • What old operational key exists in CALPADS?
    • Has the delete row preserved the old School, SSID, and Start Date?
    • Has the corrected Add/Update row used the new key?
    • Will any duplicate or orphan enrollment remain?
  • Trace SIS and extract behavior
    • Are source dates and reason correct on the same segment?
    • Did a rollover, import, report, join, or spreadsheet alter them?
    • Will the next file reproduce the sequence?
    • Which other records share the same workflow or mapping?

Reconstruct the enrollment before changing it

  1. ExpectedConfirm the intended start.
  2. OutcomeAttended or no-show?
  3. StatusGeneral education or SWD?
  4. CorrectRepair dates/reason/key.
  5. VerifyConfirm CALPADS history.

Primary participants

  • Registrar or enrollment staff
  • Attendance or school-site office staff
  • CALPADS coordinator
  • Special-education data staff when applicable
  • SIS owner and vendor/integration support

Evidence to preserve

  • Expected attendance and actual attendance
  • No-show investigation
  • Applicable disability status
  • Raw fields 1.22, 1.25, and 1.26
  • Old and corrected SENR keys

Recommended correction path

  1. Preserve the rejected evidence

    Capture submission ID, SSID, raw row, fields 1.22/1.25/1.26, and current CALPADS history.

  2. Confirm the intended enrollment

    Match student, school, start date, enrollment status, grade, and SIS segment.

  3. Reconstruct attendance

    Determine whether the student attended, exited later, or never appeared.

  4. Verify both dates independently

    Establish the first and last expected attendance dates from enrollment and attendance evidence.

  5. Confirm the exit reason

    Use N470 only for a supported no-show; otherwise report the actual exit circumstance.

  6. Apply the correct N470 pattern

    Use one day before Start Date for general education and the same date for a student with disabilities under current official guidance.

  7. Handle any Start Date key change

    If 1.22 is wrong, use the supported old-key delete/new-key add process rather than creating a duplicate.

  8. Correct the source and extract

    Repair SIS entry, rollover, segment join, cross-system status, mapping, or transformation.

  9. Submit, verify, and broaden the check

    Confirm SENR0018 clears, review the resulting enrollment/SWD history, and inspect other records sharing the defect.

Before closing the issue

  • Confirm Start Date, Exit Date, and Exit Reason describe the same enrollment outcome.
  • Verify non-N470 exits occur on or after Start Date.
  • For N470, confirm both the genuine no-show and applicable general-education/SWD date pattern.
  • Ensure a Start Date correction did not leave a duplicate or orphan operational key.
  • Reconcile SIS, attendance, special-education status, SENR extract, and accepted CALPADS history.
  • Review other students affected by the same rollover, mapping, join, or workflow.

Official SENR0018 troubleshooting page  |  SDLA CALPADS Code Sets V.18  |  Current CALPADS system documents