Insurance Payment Operations at Scale: What Multi-Location Healthcare Groups Get Wrong

Running insurance payment operations for a single practice is already complex. Scale that to 5, 10, or 50 locations and the complexity doesn’t just multiply — it compounds. Every new location adds NPIs, TINs, bank accounts, EHR instances, payer contracts, and staff who need to be trained on processes. The healthcare groups that get payment operations right treat it as infrastructure. The ones that struggle treat it as an administrative task to be distributed.

After working with multi-location groups ranging from 3 sites to 50+ — spanning multi-specialty physician practices, urgent care chains, physical therapy networks, dermatology groups, and more — the patterns are clear. Here’s what multi-location healthcare organizations get wrong about insurance payment operations, and what the best operators do differently.

Why Multi-Location Creates Exponential Complexity

A single practice has a relatively simple payment infrastructure:

• 1 NPI (National Provider Identifier) per provider, 1 organizational NPI
• 1 TIN (Tax Identification Number)
• 1-2 bank accounts
• 1 EHR/practice management system instance
• 20-40 active payer contracts

Now multiply. A 10-location healthcare group might have:

• 30-80 individual provider NPIs + 10 organizational NPIs
• 1-10 TINs (depending on legal structure)
• 10-20 bank accounts
• 10 EHR instances (or 1 with 10 databases)
• 300+ active payer contracts (many overlapping, with location-specific rates)

The number of unique relationships between these entities grows combinatorially. Each NPI-TIN-payer combination has its own fee schedule, its own EFT enrollment, its own ERA delivery path, and its own reconciliation requirement. A 10-location group doesn’t have 10x the complexity of a single practice — it has 50-100x the complexity.

This is true whether you’re running urgent care clinics billing UnitedHealthcare, Aetna, and BCBS for E&M visits, or managing a physical therapy chain reconciling reimbursements from Cigna, Humana, and Medicare across dozens of treating therapists. The infrastructure problem is the same.

The Centralized vs. Decentralized Billing Debate

This is the first strategic decision every growing healthcare group faces, and it’s where many get it wrong.

The Decentralized Model

Each location handles its own billing. The office manager or billing coordinator at each site downloads ERAs, posts payments, reconciles deposits, and manages the local revenue cycle.

Why groups choose this: It’s the default. When you acquire a practice, they already have a billing workflow. Letting them keep running it avoids disruption. A dermatology group that picks up three independent practices inherits three separate billing processes overnight.

Why it fails at scale:

• No visibility. The central operations team has no real-time view of payment status across locations. Month-end becomes a scramble to collect reports from each site.
• Inconsistent processes. Each location develops its own posting habits, adjustment code usage, and reconciliation cadence. A multi-specialty group may find that its orthopedic office uses completely different write-off logic than its primary care clinic — making consolidated reporting meaningless.
• Talent dependency. When one location’s billing person leaves (and turnover in medical billing averages 30-40% annually), that location’s payment operations stop until a replacement is hired and trained.
• Impossible to reconcile centrally. If each location has its own bank account and its own posting process, the central finance team can’t produce a unified picture of insurance AR without manually aggregating data from every site.

The Centralized Model

A central billing team handles insurance payment processing for all locations. ERAs are funneled to a central team (or system) that posts payments, reconciles deposits, and manages exceptions across all locations.

Why it works better:

• Standardized processes ensure consistent data quality across locations
• Specialized staff who do nothing but billing are more efficient and accurate than generalists at each site
• Single point of visibility for the operations and finance teams
• Resilient to turnover at individual locations

Why it’s hard to implement:

• Requires infrastructure to route ERAs and payments to the right location in the EHR
• Each location’s practice management system may be configured differently — an acquired urgent care clinic on Athenahealth and an internal medicine practice on eClinicalWorks present very different integration challenges
• Central staff need access to every location’s system
• Some payers deliver ERAs at the provider or location level, not the organizational level

The best healthcare groups centralize the billing function but invest in the infrastructure to make centralization work — standardized EHR configurations, unified clearinghouse accounts, and automated payment routing.

The Five Failure Modes at Scale

1. Payments Posted to the Wrong Location

This is the most common and most expensive error in multi-location groups. An ERA arrives for Location A, but gets posted to Location B because the billing staff confused the organizational NPI or the EHR database. The result:

• Location A’s AR shows an outstanding balance that’s actually been paid
• Location B shows revenue it didn’t earn
• The patient may receive an incorrect statement
• The bank reconciliation for both locations is wrong

At scale, this happens dozens of times per month. Each instance takes 30-60 minutes to untangle — find the error, void the incorrect posting, repost to the correct location, and re-reconcile both accounts. A physician practice management organization with 20 locations could lose hundreds of staff hours per quarter to wrong-location posting cleanup.

2. Duplicate Posting

When multiple people have access to the same clearinghouse account, or when ERAs are downloaded to multiple locations, the same payment gets posted twice. Revenue is inflated, patient balances are incorrect, and the duplicate has to be found and reversed.

In decentralized models, duplicate posting rates run as high as 2-3% of total payments. For a group processing $2 million/month in insurance payments across UnitedHealthcare, BCBS, Aetna, Cigna, and Medicare, that’s $40,000-$60,000 in phantom revenue that inflates reports and creates reconciliation nightmares.

3. Missing Deposits

With multiple bank accounts across locations, tracking which payer deposits went to which account becomes a full-time job. A payment from BCBS might go to the main operating account, a different bank account set up during an acquisition, or (if EFT enrollment was never updated) a closed account.

Missing deposits often aren’t discovered for weeks or months. The ERA shows the payment was issued, the EHR shows it was posted, but the money never arrived — or arrived in an account nobody is monitoring. This is especially common during transitions: a physical therapy chain acquires two clinics, migrates their bank accounts, but forgets to re-enroll Humana and Medicaid EFTs at the new account. Paper checks start going to an old address, and nobody notices until the cash flow gap becomes impossible to ignore.

4. EFT Enrollment Chaos

EFT enrollment is per-NPI-TIN-payer combination. A 10-location group with 60 providers and 30 payers could have up to 1,800 unique EFT enrollment relationships to manage. In practice, the number is lower (not every provider bills every payer), but it’s still hundreds.

When a new provider joins, a location changes its TIN, or a bank account changes, EFT enrollments need to be updated with every affected payer. Missing even one enrollment means that payer reverts to paper checks for that provider — and nobody notices until the checks start arriving (or don’t). A new cardiologist at an acquired multi-specialty practice starts seeing patients, bills Medicare and Aetna, but EFT enrollment was never initiated under the group’s TIN. Paper checks trickle in weeks late, or get returned to the payer entirely.

Groups that track EFT enrollment in spreadsheets inevitably lose track. The spreadsheet goes stale within weeks of being created, and the actual enrollment state diverges from the documented state.

5. Reporting Fragmentation

The CEO or CFO of a healthcare group needs to answer basic questions: What’s our total insurance AR? What’s our average days to payment? Which payers are paying slowest? Which locations have reconciliation gaps?

In a decentralized model with multiple EHR instances, answering these questions requires pulling reports from every location, normalizing the data (because each system may use different reporting formats), and aggregating manually. A practice management organization running eClinicalWorks at three sites, Athenahealth at four, and NextGen at another two can’t simply merge reports — the data models are fundamentally different. By the time the report is assembled, the data is already stale.

Even in a centralized model, if the payment data isn’t systematically reconciled against bank deposits, the reports are only as accurate as the postings — which, as we’ve established, have a 5-8% manual error rate.

What the Best Healthcare Groups Do Differently

The most operationally mature multi-location healthcare organizations we work with share a few common characteristics:

They Treat Payment Operations as Infrastructure

Payment processing isn’t an office manager’s side job — it’s a dedicated function with its own budget, KPIs, and leadership. The best groups have a VP or Director of Revenue Cycle Management who owns payment operations across all locations, whether those locations are urgent care clinics, specialty practices, or primary care offices.

They Standardize Before They Scale

Before acquiring or opening a new location, they have a playbook for onboarding: standardized EHR configuration, unified clearinghouse account, EFT enrollment for all payers, and integration with the central payment system. The new location is operational within days, not months. This is true whether the acquisition is a solo dermatology practice or a five-provider orthopedic group — the onboarding playbook doesn’t change.

They Automate the Match, Not Just the Posting

Posting payments is only half the job. The other half — reconciling against bank deposits and verifying accuracy — is where money is found or lost. The best operators run automated three-way matching (ERA → EHR → bank) across every location, every day. When a $14,000 Medicare deposit doesn’t match the sum of posted ERAs, they know about it that afternoon — not at the end of the quarter.

They Monitor EFT Enrollment Continuously

Instead of one-time enrollment efforts, the best groups run regular audits of their EFT status across all NPI-TIN-payer combinations. When a payer falls back to paper checks, they catch it within days — not months. This is critical for groups that are actively acquiring: every new practice brings a new set of enrollment relationships that need to be migrated to the group’s banking infrastructure.

They Use a Unified Platform

Per-location tools don’t scale. A group running separate billing software at each location has N systems to maintain, N sets of credentials, and N reconciliation processes. The most efficient groups use a single platform that handles all locations, with role-based access and location-level reporting — regardless of whether the underlying EHR is Epic, Athenahealth, eClinicalWorks, or anything else.

The Takeaway

Multi-location healthcare groups can’t afford to treat insurance payment operations as an extension of single-practice billing. The complexity is fundamentally different, and the failure modes — wrong-location posting, duplicates, missing deposits, EFT chaos — have real financial impact that scales with the number of locations.

The groups that get this right start by acknowledging that payment operations is infrastructure, not administration. They centralize the function, standardize the processes, and invest in systems that match the scale of their operations. The groups that don’t get it right spend their time fixing errors instead of growing the business.

If you’re operating multiple locations and still managing payments per-site, the question isn’t whether you’ll centralize — it’s how much it will cost you before you do.