EXECUTIVE SUMMARY
The financial infrastructure problem most healthcare CFOs inherit
Multi-location healthcare organizations — clinic groups, hospital-affiliated practices, physician networks, and healthcare services companies — share a structural financial management problem that grows more acute with every location added. The EHR manages the clinical record. A separate billing system handles claims. QuickBooks or a legacy general ledger handles the books. And the finance team spends the close cycle manually stitching those systems together, locating denied claims, estimating accruals, and assembling a consolidated picture that is already weeks old by the time leadership sees it.
This guide is written for the CFO or VP Finance of a multi-location healthcare organization who knows the pain is structural but has not yet seen what a properly configured ERP looks like for their specific operating environment. It covers the four areas where NetSuite — configured by Archer Insights with healthcare-specific workflows — changes the financial operation most materially: revenue cycle integration, multi-entity consolidation, close acceleration, and operational controls.
Key Industry Metrics
- 11.8% – Industry avg. claim denial rate, 2024
- 40%+ – Of providers wait 2+ months for reimbursement
- $360B – Annual savings possible with automation
- 25% – Jump in net revenue leakage, 2025
CHAPTER ONE
Revenue cycle: where healthcare organizations lose the most money
Revenue cycle management is the most consequential financial function in a healthcare organization, and it is almost always the least well-integrated with the general ledger. The clinical encounter happens in the EHR. The charge is captured somewhere between the EHR and the billing system. The claim goes out. The denial comes back. And by the time the write-off shows up in the general ledger, the opportunity to recover it has often passed.
The root cause in most multi-location organizations is a manual bridging step between clinical data and the financial system. Charge data, diagnosis codes, and visit information require re-entry or export from the EHR before they enter the revenue cycle. Every manual step is a potential error. Every error is a potential denial. And at an industry average denial rate of 11.8% — with best-in-class at under 3% — the gap between where most organizations sit and where they could be represents real money.
The EHR-to-GL gap
Clinical documentation lives in the EHR. Revenue accounting lives in the ERP. When those systems do not connect cleanly, coding errors and authorization gaps enter the billing cycle before a single claim is submitted.
Diagnosis codes entered in the EHR do not automatically appear in the claim. Charge capture requires manual translation. Authorization status is tracked separately from the billing record. Each disconnect is a source of systematic denials that have nothing to do with the care delivered.
Archer's EHR/EMR connector for NetSuite pulls encounter data, charge capture, and diagnosis codes directly into the revenue cycle — eliminating the manual bridging that generates billing errors at the source.
Denial management that does not wait for month-end
Most denial management workflows are reactive: claims age into the 90-day bucket, finance notices at month-end, and recovery is attempted on claims that may be past timely filing windows.
NetSuite's revenue cycle integration surfaces denial root causes, payer-specific underpayment patterns, and A/R aging trends in real time — giving revenue cycle staff the information to act within the billing cycle rather than discovering problems at close.
Days in A/R above 35 and aged A/R above 15% at 90 days are the measurable indicators of a revenue cycle that is losing the denial battle. The target is Days in A/R under 35. Most multi-location healthcare organizations exceed both thresholds.
📋 Provider credentialing: the denial source no one sees coming
Physician and advanced practice provider credentialing determines billing eligibility — and credential lapses generate claim denials retroactively. When credentialing status is not tracked in the ERP, finance discovers the problem after claims have been denied for providers whose credentials expired without notification. Archer's credentialing workflow module tracks license expiration dates and payer enrollment status, triggering renewal workflows before credentials lapse and billing eligibility is lost.
CHAPTER TWO
Multi-entity consolidation: closing the books without rebuilding them
Multi-location healthcare organizations operate legal entities that are distinct for regulatory, tax, or ownership reasons while their management needs to see consolidated financial performance. That gap — between entity-level accounting and consolidated visibility — is where most healthcare finance teams spend disproportionate time at every close cycle.
The typical workaround is an Excel consolidation model: export data from each entity's accounting system, normalize the account structures, identify and eliminate intercompany transactions, and assemble a consolidated view. In a three-entity organization this might take a day. In a ten-location group with shared services entities and affiliated practices, it routinely consumes a week of senior finance staff time every month.
HOW NETSUITE HANDLES MULTI-ENTITY HEALTHCARE OPERATIONS
| Structure | How NetSuite handles it | What this eliminates |
|---|---|---|
| Multi-location clinic group | Separate sub-ledgers per location within one NetSuite environment; consolidated P&L available in real time | Manual export-and-assemble consolidation at every close |
| Hospital-owned affiliated practices | Each practice entity maintains its own books; intercompany eliminations run automatically at close | Manual intercompany reconciliation and elimination workbook |
| Shared services entities | Costs allocated from shared services to practice entities using configured allocation rules | Manual allocation calculations outside the ERP |
| Management company structure | Management fee income and expense recorded automatically per the intercompany agreement | Manual management fee journal entries and reconciliation |
| Multi-state physician group | Separate entity per state; consolidated reporting across all states available without manual assembly | State-by-state consolidation spreadsheet at every reporting cycle |
The architectural principle is consolidation by design rather than consolidation by process. When the multi-entity structure is configured correctly in NetSuite, the consolidated view is a product of normal operations rather than a manual construction that has to be rebuilt every period. For a ten-location group, the difference between these two approaches is measured in days of finance staff capacity recovered per month.
CHAPTER THREE
Close acceleration: what a controlled close actually looks like
The month-end close at a multi-location healthcare organization typically involves the same sequence of activities repeated in slightly different order and slightly different tools depending on who is running it that month. Gather data from each location's system. Import into the consolidation model. Estimate the accruals that cannot be confirmed until invoices arrive. Chase approvals for anything above threshold. Produce the draft financials. Find the errors. Fix them. Produce the final financials. The whole process takes two to three weeks for organizations that have been doing it this way for years.
A controlled close is not faster because people work faster. It is faster because the structure of the close is different. Data is already in one place. Accruals are calculated by the system rather than estimated by the controller. Approvals have already been captured at the time of the transaction rather than reconstructed afterward. Eliminations run automatically. What remains for the finance team is review and judgment rather than data assembly.
What a manual close looks like
- Data gathering from multiple systems: 2 to 3 days
- Accrual estimation across locations: 1 to 2 days
- Intercompany reconciliation and elimination: 1 to 2 days
- Approval reconstruction and documentation: 1 day
- Draft financial review and error correction: 1 to 2 days
- Final financials produced: Day 12 to Day 18 of the following month
Bottom line: Finance leadership reviews financial information that is already two to three weeks old when they receive it.
What a configured close looks like
- All entity data already in NetSuite: no gathering step
- Accruals posted automatically based on system logic: no estimation
- Intercompany eliminations run automatically at period-end: no reconciliation
- Approvals already time-stamped in NetSuite at point of transaction: no reconstruction
- Review and adjustments only: 2 to 3 days
- Final financials produced: Day 3 to Day 5 of the following month
Bottom line: Finance leadership reviews financial information that reflects actual current performance rather than last month's.
CHAPTER FOUR
Operational controls: building the infrastructure auditors can verify
Healthcare organizations face audit exposure from multiple directions simultaneously: external financial auditors, payer audits, Medicare and Medicaid compliance reviews, and in some structures PCAOB-standard oversight. The common thread across all of these is that auditors need to verify that a control existed and was followed at the time of a specific transaction — not that a control exists in a policy document and will be applied in the future.
The control infrastructure that satisfies this requirement is not a set of policies. It is a set of system behaviors that make it structurally impossible to bypass the control. An approval authority policy that lives in a handbook and is enforced by a manager's review of a paper document does not satisfy an auditor who is trying to confirm that no transaction above a threshold was committed without documented authorization. An approval authority rule in NetSuite that blocks a transaction from being committed until the right approver has clicked approve in the system does.
Delegation of Authority: system-enforced, not manager-enforced
Archer's Approvals Application configures Delegation of Authority rules directly within NetSuite. Every purchase order, vendor invoice, and financial commitment routes automatically to the appropriate approver based on department, dollar amount, and location. The approval is captured as an immutable, time-stamped record in NetSuite at the moment it occurs.
For a multi-location healthcare organization with 50 to 200 employees, this means that the approval authority policy is enforced consistently across every location, every day, without requiring a manager to remember the policy or a finance team to verify compliance after the fact.
Control Framework
| Control area | What Archer configures in NetSuite | Why this matters for auditors |
|---|---|---|
| Delegation of Authority | Multi-tier approval routing by amount, department, and location; no transaction committed without system-captured approval | Auditors can pull the complete approval chain for any transaction directly from NetSuite in seconds |
| Vendor onboarding | Structured onboarding workflow; vendor record not created without completed documentation and approval | Vendor population is controlled; unauthorized vendor creation is structurally blocked |
| Contract enforcement | CLM module enforces spending limits against vendor contracts at the PO level; over-limit POs blocked automatically | Overspend against vendor contracts is prevented before it occurs, not discovered after |
| Segregation of duties | Role-based access controls prevent the same user from creating, approving, and paying a transaction | Classic segregation-of-duties control enforced by the system rather than by manual review |
| Audit trail | Every transaction carries a complete, immutable history of who created, modified, and approved it | Audit preparation requires no manual documentation assembly; all evidence is in the system |
WHAT ARCHER BUILDS
The Archer module set for healthcare operators
Archer Insights configures NetSuite with a module set specifically designed for the financial and operational requirements of multi-location healthcare organizations. These are not generic NetSuite modules applied to a healthcare context — they are configurations and proprietary modules built from engagements with healthcare operators, compounding pharmacies, specialty pharmacy networks, physician groups, and other regulated healthcare businesses.
Module Framework
| Module | What it does | Healthcare-specific value |
|---|---|---|
| EHR/EMR Integration | Pulls encounter data, charge capture, and diagnosis codes from EHR into NetSuite revenue cycle | Eliminates manual charge entry; reduces denial rate by addressing coding errors at the source |
| Multi-Entity Financials | Unified chart of accounts across all locations with automated intercompany eliminations | Close cycle reduced from weeks to days; consolidated reporting available in real time |
| Archer Approvals App | DOA-enforced multi-tier approval routing for all financial transactions | Every commitment is documented and auditable; approval policies enforced by the system |
| Contract Lifecycle Management | Vendor contract terms enforced at the PO level; spending blocked when contract limits reached | Prevents overspend on clinical service agreements, staffing contracts, and supply vendor commitments |
| Vendor Onboarding Portal | Structured onboarding workflow with documentation requirements before vendor activation | Controlled vendor population; audit-ready documentation of every vendor relationship |
| JP Morgan Banking Integration | Direct bank connection for payments and daily automated reconciliation | Real-time cash visibility; third-party payment platforms eliminated |
| Provider Credentialing Workflow | Tracks license expiration and payer enrollment; triggers renewal workflows automatically | Billing eligibility protected; credential-lapse denials prevented before they occur |
FINAL THOUGHT
The question worth asking before the next close
The next time your close cycle stretches into its second week, it is worth asking which part of that timeline is necessary and which part is structural — a byproduct of systems that were not designed for what your organization has become. Most multi-location healthcare CFOs find that the majority of close time is data assembly, accrual estimation, and approval reconstruction: work the system should do and does not, because the system was not configured for it.
Archer Insights has built the financial infrastructure described in this guide for compounding pharmacy networks, physician group management companies, specialty pharmacy operators, and other multi-location healthcare businesses. The engagements are faster than a generalist implementation because the configurations are pre-built. The controls are more precise because they are designed for the healthcare regulatory environment specifically. And the post-go-live support is grounded in direct experience with the operational challenges healthcare finance teams face.
Archer Insights is a five-time consecutive NetSuite Alliance Partner Spotlight Award winner (2022 through 2026), recognized specifically for its work in the Life Sciences and Healthcare sector.
Call to Action
If your multi-location healthcare organization is managing its finances across disconnected systems and your close cycle is consuming two weeks of every month, Archer can show you what the alternative looks like.
archerinsights.com | Schedule a conversation with our healthcare team