Closing the books on your thirtieth building is the same job as closing them on your third. The invoices look the same, the payroll runs the same way and the review asks the same questions. So when a long-term care finance back office starts missing dates somewhere between 10 and 50 facilities, the obvious diagnosis is that it needs more accountants.
That diagnosis is usually incomplete. What grew is the work around the work: collecting, merging, chasing, rekeying and checking who has finished what. Call it assembly. Nobody is hired to do it and it appears on no close checklist, so it lands on your controller.
Here are six places it breaks, what each looks like on the ground, and whether people, process or software fixes it.
The work per facility stays flat as a group grows and the assembly around it does not. Take preparation away from your reviewers. Write the rules down before you automate them. Use software where the job is gathering and matching. Give PBJ a named owner and a calendar for each building.
Preliminary financials: reviewers turn into preparers
Every building needs a set of prelims and every set needs a reader who knows the operator. In a small group the same few people do both. As facilities get added, the people who should be reading spend the month finishing preparation. Commentary thins out as the calendar runs down.
What fixes it: people, arranged differently. Split preparation from review and staff them separately. Paradigm Healthcare runs 19 nursing homes and provides back-office accounting for another 12 facilities. Finding competent, committed finance staff in the US had become difficult and expensive. A dedicated Touch Support team now prepares the prelims and hands them to Paradigm’s onshore team for review and publishing. The back office supports 30+ facilities with prelims delivered on time and without added local headcount.
“The team shows up, works hard, takes feedback, and cares. It feels like an extension of our organization.”
Accounts payable: one vendor, coded differently in every building
Invoice volume is what everyone sees. The part that hurts as a group grows is consistency. A linen vendor lands in housekeeping supplies at one building and laundry at another, and both entries look reasonable on the day. Months later you compare two facilities and the difference on the page is a coding habit.
On the ground, administrators field vendor calls about payment, approvals wait on whoever is in the building that week, and AP staff keep private notes on each facility.
What fixes it: process. Run one vendor master across the group with a default GL account for each vendor. Write an approval path that names a role rather than a person. Do this before you hire or automate, because a rule nobody has written down cannot be handed to a new accountant, a remote team or a rules engine. Our Sage Intacct finance teams handle AP inside the client’s own system, and that page publishes the scale.
GL review: the line-by-line scan stops fitting in the month
Month-end GL review often means an accountant pulling a schedule of expenses and reading every invoice line for misclassifications. Several hours per facility is survivable with a handful of buildings. Across a portfolio it gets squeezed, and what slips through comes back as corrective journal entries, restatements and revised management reports.
What fixes it: software, because the rules are known. Let a rules engine make the first pass and have accountants review only the exceptions. One 100+ facility accounting operation moved to this model with Ledger Classifier, which runs 16 configurable rules after AP close. They look for vendor and GL mismatches, unusual amounts and missing recurring vendors.
Keep the reason for every correction too. A healthcare accounting operation estimated that roughly 15% of its GL reclassifications were documented, because the record was a separate task in a separate system after the fix was finished. A prefilled form inside Sage Intacct, appearing at the moment of correction, took capture to 100%. Any control that asks someone to do a second job after finishing the first will get skipped, so build it into the first job. A complete record also shows which GL codes keep getting corrected, and that is where your coding guidance is wrong.
Payroll investigation: one question, three systems
Owners ask why labor moved. The answer is spread across the payroll system, the GL and a stack of reports pulled per pay date. A group grown by acquisition can easily run more than one payroll platform.
One 23-facility accounting team explains every labor change above $1,000, across Paycom and Paycor, against postings in Sage Intacct. Before the data was consolidated, each facility took 3 to 4 hours of downloading, merging, pivoting and switching tabs.
What fixes it: process first, then software. Set a dollar threshold so that not every movement needs a story. Then cross-check payroll totals against GL postings before anyone starts investigating. Some variances are posting errors, and staffing analysis will never explain those.
Daily cash: the position arrives after the decisions
A CFO needs the cash position, line of credit availability and projected balances when the day starts. In a manual operation those numbers get assembled during the morning, and each facility added brings more bank accounts. Banks, the GL and credit card providers each hold part of the picture.
What fixes it: software for the collection. In the Daily Cash Projections build, AP, Treasury, Documentation and the CFO work from one set of data. If software is not on the table yet, ask who holds the current version of the cash workbook. When the answer is one person’s name, you have found the risk.
PBJ: a federal deadline that falls between payroll and compliance
Nursing homes subject to CMS’s participation requirements must electronically submit direct care staffing data through the Payroll-Based Journal each fiscal quarter. That includes agency and contract staff, based on payroll and other auditable records. Files are due by 11:59 PM Eastern on the 45th calendar day after the quarter ends. On late files, the CMS manual says: “There are no exceptions.”
| Reporting period | Due |
|---|---|
| October 1 to December 31 | February 14 |
| January 1 to March 31 | May 15 |
| April 1 to June 30 | August 14 |
| July 1 to September 30 | November 14 |
Under CMS’s Five-Star guide, a facility that submits nothing by the deadline gets a one-star staffing rating for the quarter, and that takes a star off its overall rating. Four or more days with no RN hours while residents are in the building gets the same staffing rating. Ignoring a CMS audit, or an audit finding significant discrepancies, means a one-star staffing rating for three months.
Four things get harder with every building:
What fixes it: process first, then software. Give PBJ one named owner, a calendar per building and an internal cutoff a week ahead of the CMS date. CMS moved PBJ into iQIES on August 17, 2026 and registration for PBJ roles is required before submitting, so check that access too. ProPayHR, a payroll company serving long-term care facilities, went further with PBJ Navigator, which we designed and built. It pulls hours and census daily, takes agency, therapy and consultant hours by upload, and tracks every deadline. Facilities see a live predicted star rating. That case study puts the standard cycle at 90 to 180 days after the quarter ends and lists missed submission deadlines at zero.
Which fix goes where
| What breaks | Early warning | Fix first |
|---|---|---|
| Preliminary financials | Reviewers are preparing | People |
| Accounts payable | Same vendor, different GL by building | Process |
| GL review | Review gets skimmed near the close date | Software |
| Payroll investigation | One answer needs three systems | Process, then software |
| Daily cash | The position is ready after it is needed | Software |
| PBJ | Dates live on one person’s calendar | Process, then software |
Software suits gathering and matching where the rule can be stated. People suit preparation and judgment. Process comes first whenever you cannot state the rule yet, because automating an unwritten rule only makes the inconsistency faster.
Frequently asked questions
How do I know we have outgrown our back office setup?
Watch the reviewers. If the people who should be reading prelims are preparing them, or one absence delays the cash position, you have outgrown it at any facility count.
What happens if a nursing home misses a PBJ deadline?
The system does not accept late files. A provider that submits no staffing data by the deadline receives a one-star staffing rating for that quarter, which takes a star off its overall Five-Star rating.
If a payroll vendor submits our PBJ data, are we covered?
No. CMS states that a nursing home using a vendor is still ultimately responsible for meeting all the requirements. Someone on your side should read the validation report and the staffing reports in iQIES before the deadline.
Should we hire, outsource or buy software first?
Write the rules down first, because all three depend on them. Then match the fix to the work: software for collecting and matching, trained people for preparation, your own senior staff for review and the owner relationship.
Do we need Sage Intacct for any of this?
No. Several published examples here connect to Sage Intacct, but splitting preparation from review, a shared vendor master, exception-based review and a PBJ calendar all work on any general ledger.
We are an accounting firm serving several operators. What changes?
Everything here multiplies by client, because each operator brings its own systems and coding habits. Set access per client and per facility from the start. The reclassification form above was rolled out that way.
Where to start
Pick one close. Ask everyone involved to log two numbers: hours spent finding, merging, rekeying and chasing, and hours spent reading and deciding. The split will tell you which of these six sections is yours.
If the answer is capacity, see what a dedicated skilled nursing finance team takes on. The free finance audit is ten questions across reporting, controls, payables, forecasting and systems. You get a score out of 100 and an improvement plan.
Regulatory facts: CMS Staffing Data Submission page, PBJ Policy Manual v2.8 (August 2026) and Five-Star Technical Users’ Guide (September 2026), read November 2026. Case study figures are as published on each linked page. The 69 to 92 hours is our arithmetic from the published per-facility time.
