Short answer: Most workforce corrections never show up in the December variance report, because a correction's whole job is to make the numbers come out right. The rate gets fixed, the missed hour gets paid, the staffing partner's invoice gets credited, and the site closes the year close to budget. What the report can't show is how many times the record had to be repaired to get there, or how many hours people spent doing it.
The variance report shows what you spent and hides what it took to get there
The December variance report for a workforce line fits on one page. Budget, actual, the variance in dollars and percent, and a short note next to anything outside tolerance. The note usually says rate, volume, or timing.
It's a good report. It answers the question finance has to answer: did we spend what we said we would? But there's a second question that matters just as much to the people running the operation, and the report has no column for it. How many times did someone have to fix the record to get to that number?
In some teams, making the records match takes hundreds of hours a month
Nearly every healthcare organization I work with has people who spend a big part of their week tracking down information. For most of them, it isn't their job title. They sit in payroll, scheduling, credentialing, or finance. But a real share of their time goes to making sure the schedule, the timecard, the rate, and the staffing partner's invoice all say the same thing.
Here's what one of those looks like. A swap gets agreed on a phone call early in the morning, confirmed in a text thread, and never makes it back onto the shift. Weeks later, the staffing partner's invoice shows one clinician on a Saturday shift and timekeeping shows another. Someone pulls the schedule, which still shows the original assignment. They call the site. They call the staffing partner. They dig through email. They adjust the record and request a credit for the shift that was billed twice. If the answer doesn't hold up, they go track it down again.
That's one shift. In some of the teams I advise, it's hundreds of these every month.
And once the credit posts, the variance report says nothing happened. A rate fixed in a retro pay run looks like ordinary wages. A credit quietly lowers the external coverage line. An approved missed punch looks like every other approved punch. The dollars land in the right place, and the work it took to get them there doesn't post anywhere.
The real cost of a correction is the time it takes
The best recent measure I've seen comes from outside healthcare. In October, Paycom released an inflation-adjusted update of payroll error research it commissioned from EY. EY estimated that each payroll error now costs an average of $339 to correct, and respondents reported errors in about one of every five payrolls. Missing or incorrect time punches were the costliest and most time-consuming errors to fix.
That research doesn't break out healthcare, so I wouldn't carry the dollar figure straight over to a hospital or physician group. But it matches what I see. The expensive part is rarely the amount being corrected. It's the research, the confirming, the second approval, the call to the staffing partner, and the conversation with the clinician whose check just changed.
That time belongs to salaried people whose hours are already in the budget. So when they spend a week in December untangling September, the variance report doesn't move. The organization pays for the fix, and then pays again for everything those people didn't get to do instead.
December is when a year of corrections comes due
Corrections happen all year. December stacks them up. The year has to close, so every open reconciliation gets forced to an answer. Invoices that were close enough in July get tied out line by line. Accruals get trued up. Holiday premium rules kick in against schedules that change by the hour. And the person who agreed to that September swap is asked to remember why, three months later, with nothing on the shift to remind them.
Finance teams are very good at getting the number right by year-end, and they rarely get credit for it. The ledger will be accurate. It just won't tell you anything about the work that produced it.
Corrections are a visibility problem, not a people problem
It's easy to read a stack of December corrections as a discipline issue. Someone should have updated the shift. Someone should have caught the rate.
In my experience, those people were paying attention. The scheduler who took the swap call at 5:40 in the morning was solving the problem in front of her, a shift about to go uncovered, and she solved it. The staffing partner billed what its records showed. Payroll paid what it was given. Everyone did their part correctly against the record they had. The problem was that each of them was holding a different piece of it.
When the same kind of correction keeps coming back, the cause is almost always upstream. The swap lived in a text thread. The rate exception lived in an email. Capable people working from disconnected records will create corrections all year, and other capable people will spend December cleaning them up.
Your own records can show you where the hidden work is
If you want to know how much of this is happening in your organization, you don't have to guess. The evidence is already in your systems. It's just filed by the date the fix happened, which is why it all blends into December.
Pull three things for the year: retro pay adjustments, credits and rebills from your staffing partners, and timecard edits made after approval. Then line them up by the site and month the shift was actually worked, not the month the correction posted.
Now you can see where the problems started. In most organizations, the corrections bunch up at a handful of sites and come from the same couple of situations, usually shift swaps and last-minute assignments. You'll probably also find that some of the sites with the best-looking variance numbers are the ones creating the most cleanup work. Their numbers look clean because someone spent hours making them clean.
That's the conversation worth having in January. A clean variance report doesn't mean a clean operation.
Why we built Kimedics the way we did
Kimedics is the clinician workforce operations platform built by healthcare operators, and that last part matters more than it sounds. Many of the people who built it spent years on the other side of this problem. They were the ones on the phone with the site in December, scrolling back through text threads, trying to figure out who actually worked a Saturday shift in September.
What they kept running into was that nobody had done anything wrong. The scheduler covered the shift. The staffing partner billed what it had. Payroll paid what it was given. The trouble was that the change and the record lived in different places, and every week the distance between them grew a little more.
So the starting idea was simple. When something changes, the change should happen on the shift itself. If a swap gets agreed at 5:40 in the morning, the shift should show the clinician who actually worked it, and the schedule, the timecard, and the invoice should all follow from that one record. That's why scheduling, credentialing, time, and pay run on one connected record in Kimedics instead of four separate ones.
The back and forth mattered too. Most of those December phone calls are really an attempt to rebuild a conversation that happened months earlier. In Kimedics, confirmations happen and are tracked in the platform, with a change log showing who asked for the change, who confirmed it, and when. When a question comes up in December, the answer is already sitting on the shift.
The same thinking carried into the details that usually end up in someone's inbox. A rate exception sits on the record where the scheduler and payroll can both see it. Whether a clinician is credentialed and eligible for that site on that day gets checked when they're assigned, so it isn't discovered at payroll. And it all works the same way whether the clinician is your own or a staffing partner's, so both sides are reconciling against the same shift. For staffing partners, that means fewer disputed invoices and fewer of their own people pulled into year-end cleanup.
None of this stops coverage from moving. That's healthcare, and it always will be. What changes is that the shift and the record move together. Fewer corrections in September means fewer to find in December, and the ones that still happen leave a trail anyone can read without picking up the phone.
The organizations I've seen make real progress stopped measuring success by how cleanly the year closed. They started measuring it by how little work closing the year took. That's the year I'd like every finance and operations team I work with to have in 2027, and it's the work I'm focused on.
Frequently asked questions
Why don't workforce corrections show up in the variance report? Because a correction is designed to make the record match what actually happened. Once it posts, it looks like ordinary wages, a routine credit, or an approved punch.
Where do most workforce corrections start? Usually with changes made outside the record: shift swaps agreed by phone or text, late assignments, and rate exceptions kept in email.
How can a team see the correction work it's doing today? Pull retro pay adjustments, staffing partner credits and rebills, and timecard edits made after approval, then sort them by the site and month the original shift was worked.
What does it look like when the change and the record stay together? Kimedics is the clinician workforce operations platform built by healthcare operators, and this is the problem it was built around. The change is made on the shift itself, the back and forth to confirm it is tracked with a history of who asked and who confirmed, and the schedule, timecard, and invoice all come from that same record.
Learn more about Kimedics
Kimedics is the clinician workforce operations platform built by healthcare operators. We help healthcare organizations gain visibility across internal and external staffing to reduce complexity and improve financial performance. For more information, book a demo or email kimedics@kimedics.com
