Skip to main content

CALPADS error brief · GERR

GERR0005

LEA does not have ownership of student enrollment to make the update
Severity Fatal
Error type Input Validation
Record type GERR

Official CALPADS rule

What CALPADS is rejecting

The student’s SINF Effective Start - End date range does not align with the LEA's enrollment.

Focus fields

Fields validated

1.23 - Enrollment Start Date 1.26 - Enrollment Exit Date 2.04 - Effective Start Date 2.05 - Effective End Date

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: The SINF Effective Start Date–Effective End Date range must overlap the LEA’s enrollment ownership period for the student.

Severity: Fatal   Type: Input Validation/Data Integrity

Fields to reconcile under Version 18:

  • 1.22 Enrollment Start Date
  • 1.25 Enrollment Exit Date
  • 2.04 Effective Start Date
  • 2.05 Effective End Date

Do not force the SINF dates to fit an inaccurate enrollment. If SENR is wrong, repair and post SENR first. If SENR is correct, adjust SINF only to the effective period supported by the student information and the LEA’s ownership.

See the date overlap

Illustrative examples; always use the student’s actual dates
CALPADS historyDate relationshipResult and response
SENR: 20260812–open
SINF: 20260812–open		SINF begins on the accepted primary enrollment start date.Aligned. Continue only if student, LEA, SSID, and source information are also correct.
SENR: 20260812–open
SINF: 20260701–open		SINF begins before this LEA’s enrollment/ownership period.GERR0005 likely. Verify whether the SINF start is wrong or a preceding SENR enrollment is missing.
SENR: 20260812–20260930
SINF: 20261001–open		The SINF segment begins after the enrollment has ended.No overlap. Verify exit history, later enrollment, Reporting LEA, and the intended SINF effective date.
SENR posted for SSID A
SINF submitted for SSID B		The dates may look compatible, but they belong to different student identities.No supporting ownership. Reconcile the SSID; do not move demographics between students.

Determine which history is wrong

Correct the first point where SIS, extract, and CALPADS diverge
What you findDurable correctionDo not do this
SENR record is missing or rejectedCorrect the SENR error, successfully post the enrollment, verify it in CALPADS, and then resubmit SINF.Do not repeatedly resubmit the same SINF row before ownership exists.
SENR contains the wrong SSID, LEA, school, start date, status, or exit dateReconstruct the actual enrollment, correct the SIS/extract, and use the proper SENR transaction method.Do not bend SINF dates around a false enrollment history.
SENR is correct; SINF Effective Start Date is wrongCorrect field 2.04 to the supported date within the LEA’s maintenance period.Do not automatically use the upload date or current date.
SENR is correct; SINF Effective End Date is wrongCorrect field 2.05 so the segment represents the supported historical period without an unintended gap or overlap.Do not arbitrarily close a still-current demographic/address record.
A later primary enrollment at another LEA limits ownershipConfirm the later enrollment and submit only the SINF history your LEA is authorized to maintain.Do not attempt to overwrite another LEA’s effective period.
Only a short-term enrollment supports the requestReview the current ownership rule and primary enrollment status; official guidance says short-term enrollment owners cannot update SINF unless the primary enrollment is closed.Do not convert an enrollment status merely to gain edit authority.

Inspect more than four date fields

The dates trigger the rule, but these surrounding values often explain why CALPADS cannot find the supporting enrollment:

  • 1.03 Local Record ID
  • 1.04 Reporting LEA
  • 1.05 School of Attendance
  • 1.08 SSID
  • 1.22 Enrollment Start Date
  • 1.23 Enrollment Status Code
  • 1.25 Enrollment Exit Date
  • 1.26 Student Exit Reason Code
  • 2.03 SSID
  • 2.04–2.05 SINF effective dates

Choose the diagnostic pathway

  • Confirm the SENR record actually posted
    • Was the SENR submission uploaded, validated, and posted?
    • Did this student’s individual row accept, or did it reject?
    • Does the accepted ODS history show the intended SSID, Reporting LEA, School of Attendance, status, and dates?
    • Was the enrollment posted before the SINF submission was processed?
  • Reconcile the student and SSID
    • Do the SENR and SINF rows contain the same correct SSID?
    • Does the SSID belong to this student rather than a duplicate or sibling record?
    • Do legal name and birth information identify the same person?
    • Did an SSID replacement or reconciliation leave the extract using an obsolete identifier?
  • Reconstruct enrollment ownership
    • Which primary enrollment begins this LEA’s maintenance period?
    • Was there an earlier enrollment at this LEA that is missing from CALPADS?
    • Does a subsequent primary enrollment at another LEA limit the period?
    • Is a short-term enrollment being mistaken for primary ownership?
    • Are exit and subsequent-start dates accurate?
  • Inspect the SINF effective segment
    • What real event caused the demographic or address information to become effective?
    • Does field 2.04 fall within the supported enrollment period?
    • Is field 2.05 blank because the information remains current, or should the historical segment end?
    • Will changing the dates create a gap, overlap, or rewrite of earlier history?
  • Trace the SIS and extract
    • Is the authoritative SIS enrollment correct?
    • Did the SENR extract omit, reject, or alter the row?
    • Did the SINF extract default its Effective Start Date to July 1, an import date, or a prior LEA date?
    • Will the next scheduled extract recreate the rejected values?

Recommended correction path

  1. Preserve the rejected evidence

    Capture submission ID, raw SENR and SINF rows, SSID, Reporting LEA, school, transaction status, and all enrollment/effective dates.

  2. Open CALPADS enrollment history

    Verify that the intended SENR record—not merely its file—was accepted and posted.

  3. Verify the authoritative enrollment

    Compare CALPADS with enrollment, attendance, withdrawal, cumulative-file, and local SIS evidence.

  4. Correct and post SENR first

    Repair any incorrect SSID, LEA, school, start, status, exit, or transaction issue; then confirm the corrected enrollment in the ODS.

  5. Identify the ownership window

    Determine the period in which this LEA may maintain SINF, including the effect of any subsequent primary enrollment.

  6. Verify the SINF change event

    Use authorized source information to establish when the demographic or address value actually became effective.

  7. Correct the owning SIS or extract

    Repair fields 2.04/2.05, SSID selection, effective-date derivation, or file mapping so the next submission remains correct.

  8. Resubmit SINF and review history

    Confirm GERR0005 clears and that CALPADS preserves the intended current and historical segments without gaps or unintended overwrites.

  9. Check the affected population

    If the cause was an extract default, mapping, rollover, or unposted SENR batch, identify other students exposed to the same defect.

Before closing the issue

  • Confirm the accurate SENR record is posted for the correct SSID, LEA, and school.
  • Verify the SINF effective range overlaps the authorized enrollment period.
  • Confirm any subsequent primary enrollment and short-term enrollment implications.
  • Review the complete effective-dated SINF history for gaps, overlaps, or overwritten facts.
  • Ensure the SIS and next SENR/SINF extracts reproduce the accepted result.
  • Document which source established the enrollment and student-information dates.

Official CALPADS GERR0005 page  |  CALPADS file-upload and SENR-first guidance  |  CALPADS Student Information guidance