CALPADS error brief · CERT
CERT040
Official CALPADS rule
What CALPADS is rejecting
Focus fields
Fields validated
SENR Data AnomaliesRecommended correction path
Suggested resolution
Why this appears after records have posted
Transactional validation asks whether an individual record is structurally and logically acceptable. Fall 1 certification rebuilds a snapshot and asks whether the resulting collection is complete and credible across schools, students, programs, histories, and anomalies. Passing the first test does not guarantee passing the second.
Data evaluated
- Fall 1 SENR snapshot enrollment
- Concurrent Enrollment anomalies (CCE)
- Multiple Identifier anomalies (MID)
- Anomaly percentage calculation
Six questions that resolve the certification finding
| Certification question | What to establish | Evidence to use |
|---|---|---|
| What passed transactional validation? | Enrollment records may have posted even though they created or preserved cross-record anomalies. | SENR submission detail and ODS histories |
| What did the snapshot expect? | Unresolved counted anomalies must remain below 2% of snapshot enrollment. | Snapshot enrollment denominator and anomaly numerator |
| What is absent or inconsistent? | Student identity or enrollment ownership is unresolved across records or SSIDs. | Report 12.1 and CCE/MID management queues |
| Which system owns the correction? | The SIS supplies evidence; CALPADS anomaly management performs the formal CCE/MID resolution. | Local enrollment records, SSID history, inter-LEA communication |
| Which transaction is required? | Correct SENR when wrong, then resolve the appropriate CCE or MID case—sometimes with another LEA. | Anomaly type, focus SSID, enrollment dates, and ownership |
| Which reports prove resolution? | The counted anomaly numerator and refreshed snapshot percentage must fall below the threshold. | 12.1 Anomaly Status Report and 1.0 Certification Errors |
Calculate before making changes
(unresolved CCEs + unresolved MIDs) ÷ snapshot enrollment × 100
Use the population and anomaly status CALPADS applies to the snapshot. Do not add ERDs to this numerator, and do not use a current SIS headcount as a substitute for the snapshot denominator.
Resolve the anomaly type, not merely the percentage
| Anomaly | What it usually means | Resolution focus |
|---|---|---|
| CCE — Concurrent Enrollment | The student appears to hold conflicting primary enrollment relationships. | Verify dates, status, school history, and coordinate with the other LEA when necessary. |
| MID — Multiple Identifier | One student may have more than one SSID. | Establish identity, select the correct focus SSID, and preserve the accurate enrollment history. |
| ERD — Enrollment Reporting Discrepancy | Enrollment histories require attention but are excluded from CERT040’s percentage. | Resolve appropriately, but do not count it as the mathematical cause of CERT040. |
Recommended correction path
- 1
Run Report 12.1
Separate unresolved CCEs, MIDs, and ERDs and identify the students contributing to the counted numerator.
- 2
Reproduce the percentage
Use unresolved CCE plus MID counts and the Fall 1 snapshot enrollment denominator.
- 3
Research each student
Compare SIS enrollment history, CALPADS history, identity evidence, and any other LEA relationship needed for resolution.
- 4
Correct and resolve in sequence
Fix an inaccurate SENR record first, allow processing, and then complete the appropriate CCE or MID anomaly workflow.
- 5
Refresh the snapshot
Confirm resolved anomalies leave the numerator and the certification calculation.
- 6
Document a suspected defect
If CALPADS still triggers CERT040 below 2%, preserve the calculation and report evidence and submit a service request referencing active defect 7313.
Official CERT040 guidance · Current CALPADS certification and real-time reports · SDLA CALPADS report directory