Direct answer
For a skilled nursing facility, direct iQIES submission is the CMS-native path after the August 17, 2026 PBJ cutover, while a vendor platform adds workflow controls outside CMS. ePeople is most useful when the operational risk is not the upload itself, but late corrections, role access delays, and quarter-end staffing proof.
Key takeaways
- CMS requires all PBJ staffing data to be submitted in iQIES starting August 17, 2026, but quarterly deadlines still stay 45 days after quarter end.
- Direct iQIES works best when one team owns HARP access, file prep, validation review, and corrections inside CMS without cross-facility complexity.
- A vendor platform earns its keep when a multi-building operator needs one workflow for census checks, pre-validation, audit trails, and quarter-close follow-up before data reaches CMS.
- Missing or erroneous PBJ data affects more than submission status: CMS uses accepted-by-deadline PBJ data in staffing calculations and the Five-Star staffing domain.
- The decision is less about whether CMS accepts a file and more about where your SNF wants to catch errors: before upload in an operations workflow or after upload inside iQIES.
What changed for PBJ submission on August 17, 2026?
CMS moved PBJ into iQIES on August 17, 2026, and from that date forward all PBJ staffing data must be submitted there. The reporting rules did not change: CMS still requires electronic submission of complete and accurate direct-care staffing information under 42 CFR 483.70(p), and the due date is still the end of the 45th calendar day after each fiscal quarter, with CMS listing February 14, May 15, August 14, and November 14 as the standard quarter deadlines on its PBJ submission page. For operators, the comparison is no longer vendor versus old QIES. It is vendor workflow wrapped around iQIES versus going into iQIES directly.
What does direct iQIES submission actually include?
Direct iQIES submission includes more than a file drop. CMS's iQIES PBJ User Manual shows three practical functions: file submission, employee record management, and staffing-hours entry. The system supports two PBJ file types, employee data files and employee link files, and it returns submission results inside the CMS workflow. CMS also built role-based access into iQIES, including PSO, PBJ Submitter, Provider Administrator, and PBJ Viewer roles in the transition memo. That means a single-building SNF with disciplined payroll exports and one reliable owner of corrections can run PBJ directly without buying another submission layer.
When is a vendor platform better than direct iQIES?
A vendor platform is better when your failure point happens before CMS sees the file. That is common in regional SNF groups that reconcile agency hours, employee IDs, weekend coverage, and census inputs across multiple buildings before quarter close. CMS says vendors may hold the same PBJ Submitter role as providers in iQIES, but vendors must request access for each facility and obtain approval from each facility's PSO using the CCN in the CMS transition memo. So the value is not regulatory substitution. The value is upstream workflow: normalization, pre-validation, cross-building visibility, and a cleaner handoff into the same CMS endpoint.
PBJ submission path comparison for skilled nursing facilities after the iQIES cutover
| Decision point | Direct iQIES submission | Vendor platform feeding iQIES |
|---|---|---|
| System of record at CMS | Native CMS path inside iQIES | Still ends at iQIES because CMS requires PBJ there after August 17, 2026 |
| User access dependency | Facility must maintain HARP account, PBJ role, and PSO approval | Vendor still needs facility-by-facility access approval, plus facility oversight |
| Best fit | Single site or tightly run small group with internal PBJ owner | Multi-building operator with recurring payroll, census, or agency reconciliation issues |
| Where errors get caught | Mostly after upload, during CMS validation and review | Often before upload through workflow checks and exception queues |
| Operational burden on scheduler or payroll lead | Higher at quarter close if files need manual cleanup | Lower if the platform standardizes imports and reminders |
| Audit trail outside CMS | Limited to CMS reports and internal spreadsheets/processes | Usually stronger if the platform logs review, correction, and handoff steps |
| Risk if one access owner is out | High if only one person holds the right role | Lower if workflow and permissions are distributed across team or vendor support |
| Cost profile | No separate software fee for CMS access | Added software or service cost that must justify fewer late fixes and cleaner closes |
| Best question to ask | Can we reliably prepare, validate, and correct PBJ internally every quarter? | Do repeated upstream errors cost more than the platform fee and implementation time? |
Where does direct iQIES create the most quarter-end risk?
The risk is usually access and timing, not the existence of an upload button. CMS strongly advised users to set up roles before launch, and QTSO warned that iQIES access can lapse after 60 days of inactivity. The iQIES PBJ manual also says sessions time out after 30 minutes of nonuse, which matters if your team is doing manual correction work on deadline day. In practice, direct submission is fragile when only one payroll or staffing person knows the file spec, the HARP credentials, the facility role setup, and the correction path. A vacation, password problem, or rejected file can turn a routine quarter close into a weekend scramble.
How much does submission accuracy matter after the file is accepted?
A lot, because PBJ is not just a transmission requirement. CMS says the public PBJ files include only data received by the deadline and exclude facilities with incomplete or erroneous data in its PBJ methodology documentation. CMS's January 2026 Five-Star Technical Users' Guide also states that only data submitted and accepted by the deadline are used in staffing calculations and the Five-Star Rating System. For turnover measures, the guide says a facility that fails to submit or submits erroneous data for one or more required quarters receives the lowest score possible for the affected turnover measures. That makes pre-upload cleanup economically different from simple IT convenience.
What does CMS tell you about the real downstream stakes?
CMS uses PBJ data for more than hours-per-resident-day. The staffing domain now includes six measures in the Five-Star Technical Users' Guide: total nurse staffing, RN staffing, weekend total nurse staffing, total nurse turnover, RN turnover, and administrator turnover. That means a weak PBJ process can distort your public staffing profile even if bedside coverage was stronger than the posted result. CMS highlighted this connection when it added weekend staffing and turnover to Care Compare and Five-Star in QSO-22-08-NH. For operators, the reporting workflow and the reputation workflow are now the same workflow.
What do PBJ-based studies say about why clean staffing data matters?
PBJ matters because CMS and researchers use it as an auditable staffing dataset, not a rough self-attestation. In a 2022 peer-reviewed study, researchers used PBJ data from 13,631 facilities and found mean annual turnover rates of about 44% for RNs and 46% for total nurse staff; higher turnover was consistently associated with lower quality of care. A separate 2021 Health Affairs study listed in PubMed argued that high nursing staff turnover offers important quality information for consumers and policymakers. Those findings do not prove a vendor platform is necessary, but they do explain why sloppy PBJ operations create more risk than a missed clerical task.
How should a single-building SNF decide between the two paths?
A single-building SNF should usually start with direct iQIES if four conditions are true: one, payroll exports are consistent each pay period; two, agency and contract labor are reconciled before quarter close; three, at least two internal users can access iQIES with the right roles; and four, the building already reviews CMS validation output without delay. If those controls are stable, direct iQIES keeps the workflow close to the source and avoids extra software spend. If even one of those controls routinely fails, the better question is not whether CMS offers a free portal. It is whether the free portal is being used as a substitute for process discipline.
- Use direct iQIES when your file prep is standardized, your HARP and role access are current, and your corrections are usually minor.
- Escalate to a vendor workflow when rejected records, agency mapping, census mismatches, or multi-building quarter-close coordination happen repeatedly.
- Keep at least two trained PBJ users per facility or region so access loss or turnover does not stall submission.
How should a regional or multi-facility operator decide?
A regional operator should decide based on repeatability, not on whether one building can muddle through. CMS requires vendor access to be approved facility by facility, so a vendor does not remove governance. What it can remove is fragmentation. If five or twenty SNFs are closing PBJ with different spreadsheets, naming conventions, agency feeds, and review habits, direct iQIES often means each building repeats the same cleanup separately. That is where ePeople can fit: not as legal counsel and not as a guarantee of a CMS outcome, but as an operations layer designed to surface missing staffing proof, inconsistent hour mapping, and quarter-close exceptions before the CMS submission window becomes a crisis.
What is the safest operating model before the next PBJ deadline?
The safest model is a hybrid discipline regardless of tool choice: reconcile labor weekly, test access before the quarter ends, validate file specs before upload, and assign one owner for submission plus one backup. CMS required FileSpecVersion 4.10.0 starting April 1, 2026, and QTSO said the legacy QIES PBJ application remains available only 30 days post-migration for limited report retrieval tied to prior submissions. In other words, the safer choice is the one that reduces end-of-quarter surprises. For some SNFs that is direct iQIES with backup coverage. For others it is a vendor layer that catches errors earlier and keeps one staffing workflow across the portfolio.
