PBJ in iQIES: Submission, Validation and Reconciliation for Nursing Homes

Confirm the reporting scope and current system

As checked November 10, 2026, the CMS Staffing Data Submission: PBJ reports the August 17, 2026 move to iQIES and required role registration. It also identifies linked System Employee ID error -1025 for totals over 22.5 hours in a day. That edit is a data-validation limit, not a safe schedule or staffing recommendation.

The CMS PBJ Policy Manual v2.8, August 2026, sections 1.1–1.2, applies PBJ to long-term care facilities subject to 42 CFR Part 483, Subpart B, and excludes swing beds. It sets the deadline at 11:59 p.m. Eastern Time on the 45th calendar day after each CMS reporting quarter (October–December, January–March, April–June and July–September). Validation may take up to 24 hours, so leave time for correction before the deadline. Consult the current manual and technical instructions for the actual submission; this guide supplies an original reconciliation workpack.

Assemble the workpack before upload

Keep six linked artifacts in approved restricted storage: source extract and cutoff; employee/agency crosswalk; dated job mapping; prepared file; submission ledger; and retrieved result/reconciliation evidence. Give a backup their own authorized access and a way to locate the current versions. Do not substitute shared credentials for continuity.

Use a key that preserves facility, source system, source employee ID, work date and relevant category. An agency worker number may be unique only within that agency. Agency A-104 and B-104 are not automatically one person because the numeric portion matches.

The policy manual's section 2.1(g) addresses maintaining employee IDs through vendor changes and linking changed IDs. Preserve that reporting relationship separately from local source aliases. A new payroll ID should not silently erase the old crosswalk.

For job mapping, keep local role key, reviewed duties, applicable CMS definition, effective period, approver and output test. A familiar local job title does not by itself decide the reporting category. Route ambiguous cases to the qualified reporting owner; a required export field is not a reason to guess.

Reconcile hours at record level

This hypothetical two-person example deliberately passes a total check:

The identities carry the wrong hours even though the aggregate matches. Compare person, date, category and facility before summarizing. Retain supported reporting transformations separately from source corrections; do not rewrite source records merely to force agreement.

A second test links old ID X and new ID Y to one synthetic person. Each shows twelve hours on the same day, producing 24 linked hours. Investigation might reveal a duplicated shift, an incorrect identity link or a different source problem. The total identifies a question; it does not tell the reviewer to reduce hours to 22.5. Preserve the original values and evidence supporting any correction.

Scheduled, paid and PBJ-prepared hours should also remain distinct. If 1,000 hours were planned and 940 were recorded on a comparable basis, the sixty-hour difference needs an explanation. If payroll includes forty additional hours in another earning category, its 980 total answers a different question. Those figures do not determine reportability; qualified staff apply current definitions to actual records.

Choose the report that answers the next question

The CMS iQIES Reports Guide: PBJ v1.0, August 3, 2026, printed pages 7–17 and 29–38, describes these current report functions:

The CMS PBJ iQIES transition and reporting reminder, August 11, 2026 distinguishes migrated historical data from the Submitter report restriction. Its QIES/iQIES reporting section describes historical data available to other iQIES reports; the Submitter report cannot retrieve QIES submissions using legacy Submission IDs. Do not apply that restriction to every report.

Validation records also identify Staffing Data Process Type as Merge or Replace where applicable. Inspect that field and current submission instructions before assuming what a corrected file will change. A receipt does not tell you that all prior data was replaced, and an error does not establish the whole package's disposition.

Preserve one row per submission attempt

Use internal labels distinct from official status values:

Keep actual submission identifiers, timestamps, returned messages and file-specification version with these rows. The backup should be able to explain what changed without the primary preparer's notes. Do not repeatedly upload a file until a favorable screen appears; establish the cause and verify the affected population.

Check the census as a different population

The policy manual, section 2.4, derives daily census from MDS records. Align facility, census date and report-generation time before comparing it with a local operational view.

Suppose the local population is A, B, C, D and E, while the CMS report lists A, B, C, D and F. Both total five. E and F still require separate investigation. Use the report's resident identifiers and assessment references to ask the qualified MDS reviewer about the actual record history. A difference can reflect timing or definitions and does not automatically justify an assessment correction.

An independent facility needs a workable handoff between payroll, MDS and the backup submitter. An enterprise needs facility-specific results beneath any central completion badge; one building's unresolved error cannot disappear into a regional total. Keep sensitive personnel and resident details restricted while leadership sees status, reason and accountable next action.

The complete workpack demonstrates which sources, transformations, files and results were checked. It also shows what remains uncertain. That is a stronger completion record than a screenshot saying the upload succeeded.