Why Do Our Hospice Claims Keep Landing in RTP?

How to Keep the Monthly Hospice Billing Chain Unbroken

The goal is one clean sequence: every month billed in date order with no gap, and no RTP left sitting long enough to stall the chain behind it. Here is what makes that happen, move by move.

1. Reconcile the Dates Before the Claim Goes Out

Sequential billing lives and dies on dates lining up: the through date of one month has to match the from date of the next, with no gap. The first move is to reconcile those dates before submission, checking that the current claim picks up exactly where the prior one ended. Medicare treats even a one-day gap as a discharge and readmission rather than continuous care, so a date that is off by a single day is not a rounding error; it is an RTP waiting to happen.

2. Bill Every Month in Strict Date Order

Hospice claims must be filed monthly and in sequence, and a month submitted out of order goes straight to the RTP file. The second move is to hold the sequence: no month is submitted until the month before it has processed, so the chain builds in order instead of jamming. Skipping ahead feels faster, but it guarantees the later claim returns and the earlier gap still has to be fixed anyway.

3. Catch and Clear RTPs the Same Day They Land

Because one held claim blocks every month after it, an RTP left sitting is not one stuck claim, it is a growing stack. This is where the systems you already run let a remote team member watch the RTP file daily, read the reason code, and rework the claim the day it returns, so the chain stalls for hours instead of months. An RTP nobody clears becomes a quarter of frozen revenue for that patient.

4. Reconcile Census, Transfers, and Level-of-Care Changes First

The gaps that break the chain usually start upstream, in a census change, a transfer with a mismatched from and through date, or a level-of-care correction that shifts a date. The fourth move is to catch those before they hit billing: a transfer's receiving from date has to equal the transferring through date, and a corrected discharge date has to flow through cleanly. Fixing the date at the source keeps the gap from ever reaching the claim.

5. Hand the Whole Chain to a Dedicated Outsourced Team

Hospices that stop losing cash flow to RTPs do it by handing sequential billing to a dedicated outsourced team: credentialed remote team members reconciling dates, billing in strict monthly sequence, and clearing the RTP file same-day, live in 1 to 2 weeks. Stalled claim chains drop toward zero inside the first weeks, a trained backup keeps the sequence moving, and your billing staff stop discovering that a mistyped date froze a quarter of a patient's revenue. Below is what it sounds like when nobody owns this yet, in hospice teams' own words.

Why This Keeps Happening

If the rule is that clear, why do good hospices keep landing in RTP? Because sequential billing turns one small date error into a chain reaction. Medicare requires hospice claims to be filed monthly and in date order, with the through date of one month matching the from date of the next and no gap between them. When a claim is held or returned, every subsequent month for that patient cannot process until it clears, so a single stuck claim silently freezes everything behind it. The rule is simple; the consequence of breaking it is not proportional.

Now add where the gaps come from. The dates that break the chain rarely start in billing; they start upstream in a census change, a transfer with a mismatched from and through date, or a level-of-care correction that nudges a date by a day. CMS treats any gap, even one day, as a discharge and readmission rather than continuous care, so a claim that looks continuous on the floor reads as broken to the system and drops to the RTP file. If no one reconciles those changes before they reach billing, the gap arrives as a returned claim. This is exactly the gap disciplined claims and documentation support is built to close.

And the cost is cash flow, not just a reworked claim. Because one RTP blocks the months after it, an unnoticed return does not delay one payment; it floats an entire patient's ongoing care until someone finds and fixes the date that broke the sequence. The scenario hospices see most is exactly the frozen one: a March claim RTPs over a one-day gap from a mistyped discharge date, April, May, and June cannot process behind it, and the hospice floats four months of routine care costs while the chain sits stalled and the biller works backward to the single date at the root of it.

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:

The Solution

So what does "someone whose whole job it is" actually look like on the monthly chain? Before each claim goes out, the remote team member reconciles the through-to-from dates against the prior month, so the current claim picks up exactly where the last one ended with no gap. They bill every month in strict date order, holding a month until the one before it has processed. That sequence discipline is the whole difference, and it is why we run it alongside disciplined clinical documentation integrity so the census and level-of-care records the dates come from are clean.

Then comes the part that protects cash flow. The remote team member watches the RTP file every day, reads the reason code the moment a claim returns, and reworks it the same day, before the months behind it stall. They are not letting a returned claim sit for the next cash-flow review to surface; they are clearing it while the chain has only paused for hours. They also reconcile census changes, transfers, and level-of-care corrections at the source, so the receiving from date matches the transferring through date and a corrected discharge date flows through without creating a gap. Your billing team feels the change inside the first weeks, because the chain stops jamming.

Behind all of it, an AI layer surfaces the date gaps and the RTPs and a trained human reviewer owns the reconciliation and rework. The system flags a through-to-from mismatch before submission and every claim sitting in the RTP file; the remote team member confirms the correction cleared and the sequence resumed. When a return turns out to be a true denial rather than a date fix, it extends into denial management and appeal drafting, so the claims that need a fight get one and the rest get cleared.

Who Actually Does This Work

Fair question: why would an outsourced team keep the sequence cleaner than your own hospice billing staff? Because their whole day is the chain, and your billing staff's day is spread across every part of the revenue cycle at once. The people running sequential billing on our side include trained healthcare operations professionals with backgrounds that may include medicine, nursing, and pharmacy, all trained specifically in hospice billing and the sequential and monthly filing rules. They reconcile dates before submission and clear the RTP file daily, because keeping the chain unbroken is the job. When a claim returns for a one-day gap, the person catching it fixes the date and resumes the sequence that day, across many hospices, without the rest of the revenue cycle pulling them off it.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ team members, 24/7 coverage, and the AI first-pass plus human-verify workflow you just read about running behind every one of them. A typical hospice is live in 1 to 2 weeks, at approximately 68% below equivalent in-house staffing costs, and you can review our HIPAA and security posture before a single patient record moves. And nobody on our side goes out without a trained backup already inside your workflow, so the monthly chain never stops moving.

And the security piece your compliance officer will ask about: Staffingly maintains active ISO/IEC 27001:2022 certification and operates under HIPAA-compliant controls and signed BAAs. SOC 2 Type II reporting and security controls apply according to the relevant entity, client environment, facility, device, and workflow. Venn Blue Border and related workstation restrictions are used where applicable. Staffingly maintains $5M in professional liability (E&O) and cyber insurance as part of its enterprise risk-management program; 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.

How We Build a More Durable Process

Reconciling one claim is not the fix, and neither is clearing one RTP. The fix is date reconciliation before every submission, strict monthly sequence, a daily RTP watch, and a documented playbook that says exactly how dates are checked, how the sequence is held, how an RTP is worked the day it lands, and how census, transfer, and level-of-care changes are reconciled at the source. Before we take a single month for a new hospice, we map how your claims move from census to submission to acceptance, and we build the rules against it: how through-to-from dates are verified, how the sequence is protected, and the exact path a returned claim follows back to a clean chain.

From there sequential billing becomes a living playbook rather than a scramble every time a chain jams. It records how dates are reconciled, how months are held in order, how the RTP file is worked daily, and how a transfer or level-of-care correction is checked before it reaches billing. It is written down, kept current, and owned by the team. When your remote team member is out, a trained backup works the same playbook the same way, so the chain keeps moving whether or not any one person is at their desk that day.

That is the difference between surviving this month's RTPs and fixing the process for good, and it is what a dedicated hospice billing partner actually buys you. A biller leaving used to mean the RTP file stopped getting watched and the chain jammed again. Under this model the AI keeps flagging, the playbook stays, the backup steps in, and a mistyped date stops freezing a quarter of a patient's revenue.

The Whole Thing in Four Sentences

Hospice claims keep landing in RTP because sequential billing requires monthly claims in strict date order with no gap between one month's through date and the next month's from date, and any mismatch from a census change, transfer, or level-of-care correction breaks the chain, with one held claim blocking every month after it. Billing without reconciling dates, billing ahead to chase cash, and working the RTP file only when cash flow looks off all fail the same way, by letting a single gap freeze a quarter of a patient's revenue. The fix is date reconciliation before submission, strict monthly sequence, and same-day RTP clearance by a dedicated remote team member. A multi-site hospice can use this workflow without exposing patient information or naming client organizations.

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 keep your billing chain unbroken? Start with a Two-Week Free Trial: your real monthly claims, reconciled dates, a held sequence, and a dedicated remote specialist clearing RTPs the day they land, 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.

Written By

Dan Nandan

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

Dan Nandan is the Founder and CEO of Staffingly, Inc., based in Piscataway, New Jersey. He has 25+ years in IT consulting and IT staffing, with the last decade focused on healthcare outsourcing. He was among the first to establish an RPO operation in India more than 20 years ago and has been featured in Computerworld. He leads Staffingly's U.S. clients and delivery teams behind the workflows described on this page.

Connect on LinkedIn

This page is general educational information for healthcare operations teams. It is not legal, medical, billing, coding, or compliance advice, and it does not create any professional or advisory relationship. Payer rules, codes, forms, and regulations change and vary by plan and region, so confirm every requirement with the applicable payer or authority before acting. Staffingly, Inc. makes no warranty as to accuracy or completeness and accepts no liability for decisions made based on this content.

Where the Claims on This Page Come From