Skip to main content

CALPADS error brief · IVR

IVR0001

Invalid Submitter
Severity Fatal
Error type Input Validation
Record type IVR

Official CALPADS rule

What CALPADS is rejecting

Reporting LEA must equal CDS code associated with submitter User ID

Focus fields

Fields validated

1.04 - Reporting LEA

Recommended correction path

Suggested resolution

Read the complete validation

CALPADS rule: Reporting LEA must equal the CDS code associated with the submitter User ID

Severity: Fatal   Type: Input Validation

Field validated:

  • 1.04 Reporting LEA

Four identities must not be confused

What each identifier tells you
IdentityWhere it appearsWhat it meansCommon mistake
Submitter’s institutionCALPADS account and organizational accessThe institution for which the user and assigned roles authorize submission.Assuming access to one LEA automatically authorizes submission for every LEA the person supports.
Reporting LEASENR field 1.04The legal reporting entity responsible for the enrollment and SSID context.Populating the student’s school code, a neighboring LEA’s code, or an obsolete local default.
School of AttendanceSENR field 1.05The school associated with the enrollment.Copying the school identifier into Reporting LEA without considering the reporting relationship.
File identityFilename, folder, download batch, or transfer locationA local clue about what the file is supposed to contain; it is not CALPADS proof.Trusting an unlabeled numeric filename without inspecting field 1.04 inside the file.

Do not change Reporting LEA merely to match your account. First establish which legal LEA truly owns the enrollment. If the file belongs to another LEA, stop and route it through the authorized process for that LEA. If the file belongs to the intended LEA, correct the account access or the erroneous source mapping—whichever is actually wrong.

Recognize the failure pattern

Symptoms, evidence, and durable corrections
PatternWhat to inspectDurable correction
Wrong file selectedThe filename is only a numeric code; field 1.04 consistently identifies another LEA; the student population also belongs elsewhere.Stop the submission, label and segregate files by human-readable LEA name plus code, then select the correct file.
Correct file, wrong Reporting LEAStudents and schools belong to the intended LEA, but field 1.04 contains another organization’s default value.Repair the SIS district setup, extract parameter, crosswalk, or report constant and regenerate the file.
Correct LEA, insufficient user accessField 1.04 and enrollment ownership are correct, but the account lacks the necessary institution access or role.Have the appropriate CALPADS administrator review the user’s institution and roles; do not borrow another person’s credentials.
School and Reporting LEA confusedField 1.04 contains a School code even though the school reports through a district or county office.Use the responsible district/COE County-District code in 1.04 and the correct School of Attendance in 1.05.
Independently reporting charter treated like district schoolThe extract uses an authorizer or district code even though the charter reports independently.Confirm the current reporting status and configure the charter’s seven-digit School code as specified.
NPS submission attempted by school-level userThe intended record involves a nonpublic school and the submitter has only school-level authorization.Route the submission to an appropriately authorized LEA-level user and verify the reporting relationship.
Mixed-LEA fileField 1.04 changes across rows, or the student/school population spans legal LEAs unexpectedly.Quarantine the file, determine how populations were merged, and generate separate authorized submissions.

A safer naming and folder convention

1. Human nameBegin the local filename with a recognizable LEA name or approved abbreviation.
2. Official codeInclude the verified seven-digit Reporting LEA code without removing leading zeros.
3. File and dateAdd SENR, school year or extract date, and a version marker.
4. Separate workspaceKeep each legal LEA’s unsubmitted, submitted, accepted, and rejected files in distinct controlled locations.

Illustrative local filename: LEA-NAME_1234567_SENR_2026-08-26_v01.txt. Rename only the controlled local copy; do not alter file contents or rely on the filename as evidence of the Reporting LEA.

Choose the diagnostic pathway

  • Was the wrong file selected?
    • What LEA name and code does the filename or source folder imply?
    • What exact seven-character value appears in field 1.04 of the first data row?
    • Is that same value present in every row?
    • Do the schools and students in the file belong to the same intended legal LEA?
    • Was another LEA’s file created or downloaded during the same work session?
  • Is Reporting LEA wrong inside the file?
    • Which SIS organization, report parameter, or integration supplies field 1.04?
    • Did a copied report retain another LEA’s constant?
    • Was School of Attendance mistakenly mapped into Reporting LEA?
    • Does the file mix more than one Reporting LEA?
    • Will regenerating the extract reproduce the same value?
  • Is the account or role wrong?
    • Is the user associated with the intended institution?
    • Does the user have the role required for this submission?
    • Has the user changed assignments, organizations, or responsibilities?
    • Can the LEA administrator confirm the access without exposing or sharing credentials?
    • Is a school-level account attempting an LEA-level or NPS submission?
  • District, COE, charter, or NPS relationship
    • Is the organization a district, county office, independently reporting charter, dependent charter, or nonpublic school?
    • Which entity is legally responsible for reporting this enrollment?
    • Does the current California School Directory entry support the assumed relationship and operational status?
    • For an independently reporting charter, are fields 1.04 and 1.05 using the correct School code?
    • For an NPS enrollment, is an appropriately authorized LEA-level user submitting?
  • One row or the entire extract?
    • Does every row carry the same unexpected Reporting LEA?
    • Did a single student arrive through a cross-district import or manual entry?
    • Is the issue isolated to one school, program, report, or extract job?
    • Which other files are produced by the same organization mapping?
    • What regression population must be tested after the correction?

Resolve identity before touching enrollment facts

  1. IdentifyName the file and intended LEA.
  2. InspectRead field 1.04 inside it.
  3. AuthorizeVerify account and roles.
  4. RepairFix file, access, or mapping.
  5. ConfirmSubmit and reconcile.

Primary participants for this error

  • CALPADS coordinator
  • LEA CALPADS administrator or authorized account manager
  • Registrar or enrollment staff
  • SIS system owner
  • Extract, integration, or vendor support

Choose the owner from the evidence

  • Wrong file: submission operator and file-control process.
  • Wrong field 1.04: SIS/extract configuration owner.
  • Correct code, blocked user: authorized CALPADS account administrator.
  • Unclear reporting relationship: CALPADS coordinator and responsible LEA leadership.

Recommended correction path

  1. Stop and preserve the attempted submission

    Record the submission ID, selected filename, folder, timestamp, user, intended LEA, error details, and untouched file before making changes.

  2. Inspect field 1.04 inside the file

    Read the first data row and test the entire Reporting LEA column. Do not infer file ownership from its numeric filename alone.

  3. Decode and confirm the organization

    Match the seven-character value to the official district, county office, or independently reporting charter and preserve any leading zeros.

  4. Verify the enrollment’s true reporting owner

    Confirm which legal LEA is responsible for this student, school, and enrollment; distinguish Reporting LEA from School of Attendance.

  5. Verify submitter access and roles

    Have an authorized administrator confirm the user’s institution and necessary CALPADS roles. A school-level user may not submit records for an NPS school.

  6. Correct the actual failure

    Select the right file, correct the source Reporting LEA, or obtain appropriate access. Never change a valid LEA code solely to match the current user.

  7. Strengthen the repeatable process

    Repair the SIS mapping or extract parameter and adopt human-readable filenames, controlled folders, and a pre-upload LEA checklist for multi-LEA work.

  8. Regenerate, submit, and reconcile

    Confirm IVR0001 clears under the correct authorized account, then verify the accepted enrollment and inspect other records produced by the same configuration.

Official CALPADS guidance

Understanding the error: CALPADS compares the CDS code in the submitter’s account with the Reporting LEA in the submitted file to verify that the person is authorized to submit data for that LEA.

Things to check: Verify that the Reporting LEA in the file is correct.

Suggested resolution: Confirm that the user has appropriate access and roles for the Reporting LEA, noting that school-level users are not authorized to submit records for an NPS school; or correct field 1.04 when the file contains the wrong Reporting LEA for the student’s enrollment.

Before closing the issue

  • Confirm the uploaded file belongs to the intended legal LEA.
  • Verify every SENR row contains the correct seven-character Reporting LEA in field 1.04.
  • Confirm field 1.05 separately identifies the correct School of Attendance.
  • Confirm the submitter has appropriate institution access and roles without credential sharing.
  • Verify the accepted enrollment appears under the intended student, school, and LEA.
  • Review other files created by the same organization mapping and improve multi-LEA file naming and segregation.

Official SENR IVR0001 troubleshooting page  |  California School Directory  |  Current CALPADS system documents

The 60-second file identity check

  1. State aloud or write down the LEA you intend to submit for.
  2. Read the complete local filename and source folder; do not rely on the selected-row highlight.
  3. Open a protected working copy as plain text and inspect SENR field 1.04 in the first data row.
  4. Verify that value across the file; stop if it changes unexpectedly.
  5. Decode the seven-character value using the California School Directory or approved crosswalk.
  6. Confirm the student and School of Attendance population belongs to that Reporting LEA.
  7. Confirm your CALPADS account has the intended institution access and roles.

SENR participant directory

Engage only the roles needed for the file, account, reporting relationship, or source-mapping problem.

  • CALPADS coordinator
  • LEA CALPADS administrator or authorized account manager
  • Registrar or enrollment staff
  • School-site office staff
  • Student-records staff
  • District, charter, or program administrator
  • Special education or NPS data staff when applicable
  • SIS system owner
  • Extract, integration, or vendor support