Pain Point, Solved 4.9 ★★★★★ Google Rating

Which SNF Ambulance Transports Does the Facility Pay Versus Medicare?

Which SNF transports the facility pays versus Medicare comes down to the resident’s Part A status, whether the trip is emergency or non-emergency, and the origin and destination of the run. During a covered Part A stay, most non-emergency transports, including routine trips to a physician appointment or between two SNFs, fall under SNF consolidated billing, so the facility pays and Medicare will deny the claim. Emergency transports and specific carve-outs like dialysis roundtrips, transport to the hospital for intensive outpatient services, and the trips into and out of the stay stay Medicare-billable. The fix has four moves: determine the payer at dispatch while the trip type is still knowable, get a signed SNF agreement that names your rates and payment terms before you run for that facility, invoice the facility cleanly for the runs that are theirs, and work the denials that slip through to the right payer before they age out. We run those moves inside the systems you already use, so every run lands on the payer that actually owes for it. The table of contents maps the whole method; the moves after it are the detail.

How to Sort SNF Transports to the Right Payer Before They Deny

The goal is simple: every run billed to the payer that actually owes for it, a signed agreement behind every facility, and no year-end write-off fight over runs nobody can trace. Here is what does that, move by move.

1. Determine the Payer at Dispatch, Not at Billing

The emergency versus non-emergency call and the resident’s Part A status decide the payer, and both are far easier to capture when the run is booked than to reconstruct 30 days later off a trip sheet. Build a determination step into intake: is the resident in a covered Part A stay, is this emergency or routine, and what are the origin and destination modifiers. A routine appointment transport for a Part A resident is almost always the facility’s cost under consolidated billing; an emergency run to the hospital usually is not. Capturing that at dispatch is the difference between a clean bill and a denial you have to unwind.

2. Get a Signed SNF Agreement Before You Run

Most write-off fights start with a facility that never agreed in writing to pay for the runs that are legally its cost. Before your service takes routine transports for a nursing facility, put an agreement in place that names the per-run rate, the payment terms, and exactly which trips the facility owns versus which you bill to Medicare. When the back-invoice arrives, the facility cannot claim there was no agreement, because there is one, signed, that spells out the arrangement. That single document is what turns a disputed year of runs into a payable invoice.

3. Invoice the Facility Cleanly for the Runs That Are Theirs

Consolidated-billing runs are not lost revenue; they are facility revenue, and they only get paid if you invoice them correctly and on time. That means a clean facility invoice tied to each trip, the resident and date, the agreed rate, and the reason the run is the facility’s cost rather than Medicare’s. Sent monthly against a signed agreement, those invoices get paid like any other vendor bill. Left to pile up as a surprise annual back-invoice with no paper behind it, they become the fight you are trying to avoid.

4. Work the Denials to the Right Payer Before They Age

When a run is billed to Medicare and denied under a consolidated-billing edit, that is not the end; it is a routing signal. The moment the denial lands, the trip gets re-sorted, invoiced to the facility if it is theirs, or corrected and resubmitted if the modifier or Part A status was misread. Tracking every consolidated-billing denial, its true payer, and the facility it belongs to in one place is what keeps a year of runs from quietly aging into an uncollectible write-off.

5. Hand Payer Determination and Facility Billing to a Dedicated Team

Services that stop losing SNF runs to the payer runaround do it by handing transport-level determination and facility invoicing to a dedicated team: remote specialists who sort the payer at dispatch, manage the SNF agreements, invoice the facility, and work the denials, live in 1 to 2 weeks. The billing office stops eating write-offs on runs that were always someone’s cost, a trained backup covers every gap, and the consolidated-billing denials stop being the pile nobody owns. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Key Pain Points and Discussions by Providers

real reports from practice staff, lightly edited

“We billed Medicare for a year of routine appointment runs for Part A residents, and the consolidated-billing edits denied every one of them. Now the facility says it never agreed to pay us, and I am staring at a write-off on runs we actually made.” – billing lead, ambulance service

“Nobody captures whether the resident is in a Part A stay at dispatch. The crew just runs the call, and we find out it was the facility’s cost 45 days later when the denial hits. By then the trip sheet is the only thing I have to argue with.” – office manager, EMS agency

“We have no signed agreement with half the nursing homes we serve. When I send a facility the invoice for the runs that are legally theirs, they act like it is the first they are hearing of it, and I have no contract to point to.” – practice administrator, ambulance company

“The emergency versus non-emergency call decides who pays, and my crews do not think in billing terms on scene. A routine transfer gets documented like it is nothing, and then the whole payer determination falls on me weeks later with no clean record.” – billing manager, EMS service

“I have learned to invoice the facilities monthly against a signed rate agreement instead of letting the consolidated-billing runs pile up. The year I sent one giant back-invoice, I collected almost none of it. Sent monthly with a contract behind them, they pay.” – revenue cycle lead, ambulance service

Our Answer

Here is what we actually do. A dedicated remote specialist builds payer determination into dispatch, checking the resident’s Part A status, the emergency-versus-non-emergency call, and the origin and destination modifiers, so each run is routed to the right payer before it is ever billed. For the runs that are the facility’s cost under consolidated billing, they manage the SNF agreement that names your rates and terms, invoice the facility cleanly each month, and reconcile against the contract. When a consolidated-billing denial slips through, they re-sort the trip to the facility or correct and resubmit to Medicare before it ages. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses, working inside your billing and dispatch systems, with AI drafting the first-pass determination and a human verifying every call. This is our revenue cycle management support built for ambulance and SNF transport billing, in one paragraph.

Why This Keeps Happening

If the crew ran the call and the paperwork is complete, why does the payer determination still go wrong? Because the rule is not about whether the transport happened; it is about who is responsible for paying, and that hinges on details that are invisible on a trip sheet. Under Medicare’s SNF consolidated billing, the facility carries billing responsibility for the package of care a resident receives during a covered Part A stay, and CMS treats most non-emergency transports during that stay, including routine appointment runs and transfers between two SNFs, as the facility’s cost rather than a separately Medicare-billable service. The distinction between an emergency run and a routine one, and whether the resident is in a Part A stay, decides the payer, and neither is something a crew captures cleanly in the moment.

The carve-outs are where it gets genuinely confusing. CMS keeps specific transports separately Medicare-billable even during a covered stay: the ambulance run that brings the resident to the SNF at the start, the run that takes them out at the end other than a transfer to another SNF, and roundtrip runs offsite for dialysis or certain intensive or emergency outpatient hospital services. Everything else routine tends to fall to the facility. When a billing office does not sort those categories at dispatch, it defaults to billing Medicare, and the consolidated-billing edits deny the runs weeks later, which is exactly the gap a documented denial management workflow is built to close.

And the cost is not just a single denied claim. It is a year of runs re-sorted at once into a back-invoice that a facility, with no signed agreement to hold it, can simply refuse. The write-off fight that follows is expensive in a way that never shows on a single remit: staff hours reconstructing trip sheets, a soured relationship with a facility you still have to serve, and cash that was always collectible turning uncollectible because nobody determined the payer, and got the agreement, before the wheels rolled.

⚠️ The quiet one that hurts most: The quiet one that hurts most: the year-end back-invoice with no agreement behind it. When consolidated-billing runs pile up all year and get sent to a facility as one surprise bill, the facility can, and often does, refuse it outright, citing no contract and no prior notice. It reads on paper like a collectible receivable, but without a signed agreement naming the rate and terms, there is nothing to enforce. Unless someone determines the payer at dispatch and gets the facility agreement in place before the runs start, the most collectible revenue you have becomes the write-off you cannot fight.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

What you tried What actually happened Who ended up doing the work
Billed every SNF run to Medicare and hoped Consolidated-billing edits denied the routine runs weeks later, and a year of them came due at once Whoever worked the denial queue
Sent the facility one big back-invoice at year end The facility refused it, citing no signed agreement and no prior notice Nobody, it became a write-off
Asked crews to note the payer on the trip sheet Crews think clinically on scene, not in billing terms, so the determination still fell on billing weeks later The billing office, with no clean record
Gave determination and facility billing to a dedicated specialist Payer sorted at dispatch, signed agreements in place, facilities invoiced monthly, denials worked to the right payer Someone whose whole job it is

The Solution

So what does “someone whose whole job it is” look like on a routine SNF run? The specialist starts where the billing office usually cannot: at dispatch, checking the resident’s Part A status, the emergency-versus-non-emergency call, and the origin and destination modifiers, so the payer is known before the run is billed. The consolidated-billing runs are flagged as the facility’s cost, and the Medicare-billable carve-outs, dialysis roundtrips, the trips in and out of the stay, emergency hospital runs, go to Medicare. That single sorting step, done up front, is what dedicated revenue cycle management support is built to solve before a denial ever posts.

For the runs that are the facility’s cost, the specialist manages the SNF agreement and the invoicing so the money actually arrives. They keep a signed agreement on file for each facility that names the per-run rate and payment terms, invoice the facility cleanly each month against that agreement, and reconcile the payments. There is no year-end surprise, because the facility has been paying a monthly bill it agreed to in writing all along. The runs that used to become a write-off fight become a routine receivable.

Behind all of it, AI drafts the first-pass determination and a credentialed human verifies. The workflow reads the trip data, proposes the payer and the modifiers, and flags the runs that need a facility invoice; a person confirms the Part A status and the emergency call and owns the agreement and the appeal. Every security control that protects the resident and trip data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving patient transport records through a billing workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team sort your SNF payer determinations better than your own billing office? Because reading consolidated-billing rules, checking Part A status, and managing facility agreements is their entire day, not the thing they squeeze between posting payments. The people working your transports are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US ambulance billing and SNF consolidated-billing workflows. They know which runs a facility owns, which carve-outs stay Medicare-billable, and how to structure a facility agreement that holds up. That is not a task handed to whoever is free; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical service is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a year of SNF runs never sits unbilled because the one person who understands consolidated billing is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

✓ What stops happening: What stops happening: the year of routine runs denied under consolidated billing all at once. The surprise back-invoice a facility refuses because there is no agreement. The write-off on runs your crews actually made. The crew documenting a routine transfer with no payer determination behind it. The consolidated-billing denial queue nobody owns quietly aging into uncollectible cash.
2-Week Free Trial

Ready to Stop Writing Off SNF Runs?

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented SNF transport workflow: which runs fall under consolidated billing versus which stay Medicare-billable, the Part A determination step at dispatch, a signed agreement on file for every facility, and a monthly facility invoicing cadence, all written down and worked the same way every time. Before we take a single run for a new service, we chart your top consolidated-billing denials by facility so we can see where runs are actually being lost, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than tribal knowledge in one biller’s head. It records how each facility’s agreement reads, which trip types the facility owns, how to determine Part A status at dispatch, and the escalation path when a run is denied to the wrong payer. It is written down, kept current as CMS updates the consolidated-billing edits, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so a denied SNF run never waits for one person to come back.

That is the difference between reworking this year’s denials and fixing the process for good, and it is what a dedicated revenue cycle management partner actually buys you. A biller leaving used to mean the consolidated-billing denials piled up and the facility agreements lapsed. Under this model the workflow keeps running, the playbook stays, the backup steps in, and a mis-sorted SNF run stops being the thing that quietly costs you a year of collectible revenue.

The Whole Thing in Four Sentences

Which SNF transports the facility pays versus Medicare comes down to the resident’s Part A status, whether the run is emergency or non-emergency, and the origin and destination, not whether the transport happened. Most routine non-emergency runs during a covered Part A stay are the facility’s cost under consolidated billing; emergency runs and specific carve-outs stay Medicare-billable. Billing everything to Medicare, sending a surprise year-end back-invoice, or asking crews to note the payer all fail the same way. The fix is to determine the payer at dispatch, get a signed facility agreement before you run, invoice the facility monthly, and work the denials to the right payer before they age. An ambulance service runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop writing off SNF runs? Try us risk free: two weeks, your real consolidated-billing denial queue, dedicated specialists sorting the payer and managing the facility agreements, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Transparent Weekly Pricing

One Flat Weekly Rate. 45 Hours of Coverage.

No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.

Single
$399/ week

One dedicated remote specialist owning transport-level payer determination and SNF invoice management, single ambulance service or EMS agency

Enterprise
$299/ week

10+ remote specialists, multi-county ambulance network or PE-backed EMS platform running SNF payer sorting and agreement management across many facilities

  How Pricing Works

45 hours of coverage for less than others charge for 40.

Standard US full-time year: 40 hrs x 52 weeks = 2,080 hours, the federal basis for computing hourly pay per the U.S. Office of Personnel Management. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour. Typical US market rates for healthcare virtual assistants run $9.50 to $13.00 per hour for 40 hours of coverage.

Trained backup VA Dedicated success manager Monthly training updates HIPAA-certified staff $5M E&O and cyber liability

Sort Your SNF Transports to the Right Payer This Month

You have seen the whole method. The pilot proves it on your own denial queue, with a tracker your team can watch every day.

Start My 2-Week Free Trial

Request Information

Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.

Frequently Asked Questions

During a covered Part A stay, most non-emergency transports, including routine trips to a physician appointment and transfers between two SNFs, fall under SNF consolidated billing, so the facility pays and Medicare will deny the claim. Emergency transports and specific carve-outs stay Medicare-billable. CMS makes the resident’s Part A status, the emergency-versus-non-emergency call, and the origin and destination the deciding factors, which is why the determination has to happen at dispatch rather than at billing.
CMS keeps several transports separately Medicare-billable even during a covered Part A stay: the run that brings the resident to the SNF at the start of the stay, the run that takes them out at the end other than a transfer to another SNF, roundtrip runs offsite for dialysis, and transport for certain intensive or emergency outpatient hospital services. Emergency runs are generally billable as well. Everything routine during the stay tends to be the facility’s cost under consolidated billing.
Almost always because they were subject to SNF consolidated billing and should have been billed to the facility, not Medicare. When a resident is in a covered Part A stay, CMS edits deny routine non-emergency transports as the facility’s cost. The claim was not wrong because the run did not happen; it was routed to the wrong payer. The fix is to determine the payer at dispatch and invoice the facility for the runs that are legally its cost.
With a signed agreement in place before you run, and monthly invoicing against it. The write-off fights start when a service sends a surprise year-end back-invoice to a facility that never agreed in writing to pay. A signed agreement that names your per-run rate, the payment terms, and which trips the facility owns turns those runs into a routine receivable the facility pays like any other vendor bill.
Staffingly charges a flat weekly rate per dedicated remote specialist, with lower per-person rates for teams of 5 or more and 10 or more. Every plan covers 45 hours of coverage per week with a trained backup included, and there is no percentage of your collections. The pricing section on this page shows how the flat rate compares with typical US market rates for this work.
No. AI drafts the first pass, reading the trip data and proposing the payer and modifiers, and a credentialed human verifies every determination and owns the facility agreements and appeals. The judgment on Part A status and the emergency call stays with people. Automation removes the repetitive sorting work so the specialist spends their time on the runs that need a human, not on retyping the same determination logic.
No. Our specialists work inside the dispatch and billing systems you already use, so there is no migration and no new platform for your crews or office to learn. They read your trip data and documentation where it already lives and bill and invoice through the systems you already have, which is why a typical service is live in 1 to 2 weeks rather than months.
Usually within the first two weeks. Once a dedicated specialist is determining the payer at dispatch, keeping signed agreements on file, and invoicing facilities monthly, the runs that used to be denied under consolidated billing start going to the payer that owes for them, and the year-end write-off pile stops building.
Your dedicated specialist works a 9-hour day, Monday to Friday, which is 45 hours of coverage each week. The ninth hour is part of the flat weekly rate, not billed as overtime. Over a year that is 2,340 hours of coverage, against the standard US full-time work year of 2,080 hours (40 hours x 52 weeks, the same basis the U.S. Office of Personnel Management uses to compute hourly rates of pay). That is how $399 per week works out to $8.87 per hour.
Dan Nandan, CEO of Staffingly, Inc.

Written By

Dan Nandan
Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From

Sources & References

  • CMS Skilled Nursing Facility (SNF) Consolidated Billing. Official Medicare guidance on which services, including ambulance transports, fall under a facility’s consolidated billing responsibility during a covered Part A stay. cms.gov
  • CMS Medicare Claims Processing Manual, Chapter 15, Ambulance. Payer determination rules for ambulance services, including origin and destination modifiers and the emergency versus non-emergency distinction. cms.gov
  • American Ambulance Association SNF Consolidated Billing Edits FAQ. Industry guidance for ambulance services on which SNF transports the facility owes for and how to manage consolidated-billing denials. ambulance.org
  • MGMA Revenue Cycle and Payer Determination Resources. Benchmarks and guidance on claim routing, denials, and payer determination for medical group and provider organizations. mgma.com
  • HFMA Revenue Cycle and Denials Management Resources. Guidance on payer routing, denials workflow, and the revenue impact of claims billed to the wrong payer. hfma.org