Every Hour Counts: Getting PBJ Reporting Right to Protect Your Staffing Star Rating

Payroll Based Journal (PBJ) reporting is one of the more consequential compliance obligations facing skilled nursing facilities today. Mandated by the Centers for Medicare & Medicaid Services (CMS), PBJ requires facilities to submit detailed, quarterly staffing data that directly informs the public-facing Five-Star Quality Rating System. An accurate submission protects a facility's staffing star rating; an inaccurate one — whether the result of administrative oversight or technical misconfiguration — can cause that rating to drop, trigger a formal audit, and, in the worst case, result in an automatic one-star designation.

This guide is designed to help facility leaders, compliance teams, and payroll administrators understand every stage of the PBJ process: from the initial configuration of the timekeeping system, through the technical generation and review of the submission file, to the post-submission reports that confirm data integrity. Because there is currently no mechanism to amend staffing data after a quarterly deadline has passed, the emphasis throughout is on prevention — getting the data right before it is submitted, every quarter, without exception.

Understanding the Stakes
The staffing star rating derived from PBJ data is supposed to be one of the visible indicators of a facility's quality. Prospective residents and their families rely on it when choosing a care setting, and state and federal surveyors monitor it as part of ongoing oversight activity. For this reason, the accuracy of PBJ submissions carries real-world consequences that extend well beyond the submission portal.

Consequences of Inaccurate Reporting
Errors in PBJ data can distort a facility's staffing star rating in either direction. Underreported hours cause the rating to appear lower than actual staffing levels warrant, while overreported hours create an inflated picture that may invite scrutiny. Either outcome is damaging — the former misrepresents the facility to the public; the latter creates an audit risk.

When CMS conducts a PBJ audit and determines that submitted data is inaccurate, the facility's staffing star rating is automatically reduced to one star for the affected quarter. If a subsequent audit finds that the same underlying issue has not been corrected, the one-star designation extends beyond a single quarter, and the facility must complete an additional audit to demonstrate resolution. Because deadlines are firm and no amendment pathway currently exists, every quarter's submission must be treated as final when the reporting window closes.

Building the Foundation: Payroll System Configuration
A payroll or timekeeping system that is set up correctly from the outset will generate clean, CMS-compliant data quarter after quarter. A system with gaps in its setup will consistently produce errors that require manual intervention — or, worse, errors that go undetected until an audit reveals them.

Employee Setup and Unique Identifiers
Every employee must be assigned a unique PBJ identifier at the time of onboarding. This identifier serves as the key that links the individual's hours to their job classification in the submission file. In addition to the identifier, each employee record must accurately reflect whether the individual is an exempt, non-exempt, or salaried employee. These classifications affect how hours are captured and reported, and an incorrect designation can cause hours to be miscounted or omitted entirely when the file is generated.

Pay Type and Job Title Code Alignment
CMS maintains specific code sets for both Pay Type and Job Title, and the payroll system must be configured to generate values that align with those official designations. Pay Type Codes that do not match CMS specifications can cause the submission file to be rejected outright. It is therefore critical that the correct Pay Type Code is assigned at the very beginning of a person's employment — retroactive corrections are far more difficult and time consuming.
Job Title Codes carry equal weight. When an employee is entered into the system, the role or job title assigned to their record must reflect their primary job duties and the positions they are expected to fill within the organization. Assigning an incorrect job title code — even accidentally — means that hours worked will be attributed to the wrong classification in the PBJ file, creating a discrepancy that affects staffing metrics across multiple categories.

Lunch Deductions and Break Management
One of the more nuanced configuration challenges in PBJ compliance involves the handling of meal breaks. The payroll system must be capable of accurately applying or omitting lunch deductions based on whether an employee took a break — and it must do so consistently, without manual adjustment.

The system should be able to identify if an employee took a meal break or not. If an employee took a lunch break and the system automatically deducted time anyway, the facility will underreport that individual's hours. Conversely, if an employee did not take a full break but the system fails to remove the time, hours will be overreported. Both scenarios introduce errors into the submission. For staff working double shifts, the system must also account for multiple breaks appropriately. The rules governing these deductions should be configured in the system itself, so they apply uniformly and do not depend on manual entry or supervisor intervention.

The Midnight Cutoff Rule
For PBJ purposes, hours must be reported on the calendar day on which they were worked — not the day on which a shift began. This distinction is straightforward during daytime hours but becomes important for overnight shifts that span midnight. A staff member who clocks in at 11:00 PM and works until 7:00 AM, for example, has worked one hour on the first calendar day and seven hours on the second. The system must be configured to split and report those hours accordingly.

Facilities that think of the overnight shift as belonging entirely to the punch-in date — a natural way to think about staffing — will produce incorrect PBJ files unless the system is explicitly set up to follow the midnight cutoff rule. These errors are difficult to catch without a deliberate review process.

Department and Certification Changes
If an employee’s role is not static, and the report should reflect as such. When a staff member transitions from one department to another — for example, moving from a certified nursing assistant (CNA) role into a housekeeping position — their job title code in the system must be updated to reflect the new role. Hours worked in housekeeping must not be reported as CNA hours, as this would misrepresent the facility's clinical staffing to CMS.

At the same time, if that same individual picks up shifts in their former CNA capacity on an occasional basis, those specific shifts can be reported under the CNA job title code. Failure to manage these transitions carefully is a frequent contributor to job code mismatches in submitted data.

Technical File Generation and Validation
Even when the payroll system is correctly configured, the process of generating the PBJ submission file introduces its own set of potential errors. The file must meet precise technical specifications set by CMS, and any deviation — whether in formatting, coding, or content — can result in a rejected submission or, more problematically, a file that is accepted but contains inaccurate data.

Configuring the File Export
The payroll software must be configured to generate the XML file with the correct facility identifier, quarter, and reporting year. These parameters must be verified before each quarterly submission — an incorrect facility ID, for instance, would associate the submitted data with the wrong provider in CMS's system. Some systems allow these parameters to be saved as defaults, which reduces the risk of manual entry errors but requires periodic review to ensure the values remain accurate.

Excluding Non-Qualifying Hours
Not all hours captured in a timekeeping system belong in the PBJ submission. The system should be configured to exclude categories of hours that are present in the payroll data but do not represent productive or direct care time.
Paid time off (PTO) would be an example. PTO hours typically reside in the timekeeping system alongside worked hours, but they do not represent time spent working in the facility and must therefore be excluded from the PBJ file. Many payroll systems use separate pay codes to distinguish PTO from productive time; the file generation process must be configured to recognize and exclude those codes. Similarly, shift differential coding — used by many systems to record pay premiums for evening or weekend shifts — can complicate the extraction of worked hours if not handled correctly. Only the actual hours worked should appear in the submission file, regardless of how many codes or line items are associated with a given shift in the payroll system.

Facilities that house personal care or assisted living staff within the same timekeeping system must ensure that those employees' hours are coded separately and filtered out when the PBJ file is created. Including assisted living hours or personal care hours in a skilled nursing PBJ submission would artificially inflate staffing figures and misrepresent care delivery to CMS.

Pre-Submission File Review
Before uploading the XML file to CMS, it should be reviewed carefully to confirm that it reflects what the payroll system was expected to produce. Because XML files are not designed for easy human readability, many payroll platforms can also generate a companion file in CSV or Excel format that presents the same data in a more accessible layout. Where this option is available, it should be used as the basis for the pre-submission review. Comparing the companion file against source payroll data — such as a detailed punch report — allows reviewers to identify discrepancies before they become part of the official quarterly record.

Post-Submission Review and Monitoring
Uploading the file to the CMS submission portal is not the final step in the quarterly process. CMS makes several reports available after submission, and reviewing those reports is an essential part of confirming data integrity. Treating the upload as the finish line — without reviewing what CMS has processed — leaves potential errors undiscovered and unaddressed.

File Validation Report
The File Validation Report is the first document to review after submission. It confirms that the uploaded file was received and processed without technical errors. While a clean validation report is a necessary condition for a successful submission, it is not by itself sufficient — a file can pass technical validation while still containing inaccurate staffing data. The validation report should therefore be treated as a baseline checkpoint, not a final confirmation of accuracy.

Staffing Summary Report
The Staffing Summary Report provides an aggregate view of the data CMS has recorded for the quarter. Reviewers should use this report to verify that overall staff counts are accurate and that the breakdown of exempt, non-exempt, and contracted employees matches the workforce used during the quarter. Significant discrepancies between this report and internal payroll records are a strong indicator that something went wrong during file generation and should be investigated before the reporting window closes.

PBJ Individual Daily Staffing Report
Where the Staffing Summary Report provides a high-level view, the PBJ Individual Daily Staffing Report offers granular detail: the hours attributed to each individual employee for each day of the quarter. This report should be compared against the detailed punch or hours report from the timekeeping system to verify that every employee's submitted hours align with the hours they actually worked. This comparison is the most effective way to catch errors at the employee level — including misclassified hours, missing records, and data that was incorrectly included or excluded during file generation.

Audit Preparedness
A PBJ audit is an examination by CMS to verify that submitted staffing data is accurate and consistent with facility payroll records. While audits are not triggered for every facility every quarter, any facility that submits PBJ data should operate as though an audit is always possible. The standard for audit-ready data is straightforward: the hours in the PBJ submission file must match the hours worked and documented in the payroll system, and the classifications assigned to employees must reflect their actual roles and duties. Hours reported for contract staff should be supported by paid invoices.
Facilities should maintain organized, accessible payroll records that can be produced quickly in response to a CMS data request. A well-documented audit trail — maintained as a matter of routine rather than assembled in response to an audit notice — is the most reliable protection against an adverse audit finding.

It is also worth noting the consequences of a failed audit. As described earlier, an automatic one-star rating follows a determination that submitted data was inaccurate, and the path to clearing that designation requires a subsequent audit and a demonstration that the underlying issue has been corrected. Facilities that invest in audit preparedness before a problem arises are in a far stronger position than those who must reconstruct their processes under the pressure of an active audit.

Timeline and Deadline Management
CMS establishes quarterly submission deadlines for PBJ data, and those deadlines are non-negotiable. Because there is no process by which a facility can amend submitted data after the deadline has passed, the timeline leading up to each deadline requires deliberate planning and advance preparation.

Post-submission reviews of CMS reports should similarly be built into the quarterly workflow, with assigned responsibility and a defined timeframe for completion. Treating the post-submission review as an optional step is a missed opportunity — these reports provide the clearest available signal of whether the submitted data is likely to affect the facility's star rating or trigger an audit.

Conclusion
Accurate PBJ reporting is not a one-time task — it is an ongoing operational discipline that requires attention at every stage of the quarterly cycle, from the initial configuration of the payroll system to the final review of post-submission reports. The facilities that consistently achieve clean, audit-ready submissions are those that have invested in getting the foundational elements right: properly coded employees, correctly configured system rules, careful file review, and a structured post-submission verification process.

The staffing star rating is too important — to residents, to families, to surveyors, and to the facility's reputation — to be left to chance. By treating each of the areas described in this guide as a standard element of quarterly operations, facilities can protect the accuracy of their PBJ data, safeguard their staffing star rating, and ensure they are always prepared to stand behind their submissions.