Everything about AI in the revenue cycle.

LunaBill is an AI revenue cycle management platform that automates accounts receivable (AR) for hospitals and RCM firms. A coordinated team of AI agents works each claim end to end: checking payer portals, calling insurance companies, handling denials, filing appeals, and resubmitting claims, so your billing staff review outcomes instead of sitting on hold.

LunaBill works your AR queue for you. Its agents log into payer portals, place claim status calls, navigate phone trees, read back denials, draft and file appeals, resubmit corrected claims, and leave a full audit trail, around the clock and in parallel, inside the systems you already run.

LunaBill's AI agents do the mechanical work that slows revenue cycle teams down. They log into payer portals, place and hold claim status calls, navigate phone trees, read back denials, and queue the right next action, in parallel and around the clock, inside the EHR you already run. Your team keeps the judgment calls; the agents do the volume.

Yes. Luna places real calls to payers, waits on hold, navigates the IVR, and gets a live answer without using a single staff minute. Across the LunaBill portfolio that is more than 90,000 payer interactions a month.

Yes. Waiting on hold is one of the things Luna does best. The agent stays on the line, works through the IVR phone tree, and only surfaces once it has a live answer, so no staff time is spent listening to hold music.

Luna takes the next claim that needs a status check off the worklist, dials the payer, holds, navigates the IVR, asks the same status questions a seasoned biller would, captures the reference number, and writes a structured note back into the workflow with the next action.

Yes. Luna reads the denial reason code, classifies the root cause, drafts the appeal with the detail the payer requires, files it, and resubmits corrected claims through your clearinghouse, following payer-specific rules.

Yes. When a claim needs a correction, such as a payer ID or coordination-of-benefits fix, Luna makes the correction and resubmits the claim through your existing clearinghouse, then follows it to resolution.

Yes. Luna logs into payer portals, including Availity, Waystar, and payer-specific portals, and retrieves claim status, eligibility, and remittance automatically, in parallel across the queue, falling back to a payer call when the portal cannot answer.

Luna identifies an unpaid, delayed, or denied claim, checks the payer portal for status, determines what the claim needs, places a call if one is required, captures the result and next action, executes or routes that action such as a resubmission or appeal, and tracks the claim through to payment with visibility for your team.

LunaBill deploys a coordinated team of 13 specialized AI agents across the revenue cycle, each focused on a part of the claim-resolution workflow, from portal retrieval to payer calls to denials and appeals.

Yes. Your team keeps the judgment calls, handling escalations, complex appeals, and patient-facing work, while the agents do the mechanical volume. Every agent action carries a full audit trail your team can review.

Yes. Every action Luna takes on a claim, from a portal check to a payer call to a resubmission, is recorded in a full audit trail your compliance team can review and, for RCM firms, hand to the client.

Luna works the full AR queue, and it prioritizes the aged and 60+ day commercial claims that cost the most to leave sitting, because the longer a claim goes unworked, the harder it is to collect.

Yes. Aged claims are exactly where a lot of unworked revenue sits, because manual teams triage them away. Because Luna works claims at a fraction of the manual cost, the long tail of aged and small-balance claims becomes worth pursuing again.

Generally, yes: the longer a claim sits unworked, the harder it becomes to collect. That is why LunaBill focuses on working claims quickly and continuously, so fewer accounts age into low-recovery territory before anyone follows up.

Luna conducts the claim-specific conversation a biller would, asking why a claim was not paid, what is missing, and what the next step is, then acts on the answer. It handles the follow-up dialogue so your team does not have to.

Both, but voice is only the entry point. Calling payers is one step. LunaBill automates the surrounding workflow too: portal checks, denials, appeals, resubmissions, and tracking, so it works the whole claim-resolution process rather than just placing calls.

Luna handles the AR follow-up workflow and captures remittance and outcomes on each claim. Posting back into your EHR, such as ERAs and call notes, is scoped and configured with your team during onboarding.

Yes. The agents run in parallel and around the clock, so your backlog no longer depends on how many hours your staff can spend on the phone. Throughput stops tracking headcount.

Yes, on the work that needs a human. Your billers stop holding for payers and start reviewing outcomes and handling escalations and complex appeals, while Luna takes the holds, the portal pulls, and the routine resubmissions.

Yes. Because the agents run in parallel, capacity is not limited by headcount. LunaBill can work a growing backlog without you hiring enough people to manually pursue every claim.

Yes. Commercial claims, especially aged 60+ day commercial claims, are a core focus, because they are often the hardest and most valuable slice of the AR book to work manually.

Luna falls back to a payer call, holding and navigating the IVR to get a live answer, so a claim is never stuck just because one channel came up short.

No. Luna runs inside the EHR and clearinghouse your team already uses. There is no new system for your billers to learn; they simply spend their time reviewing outcomes instead of sitting on hold.

No. The model is one component. LunaBill's product is the healthcare workflow around it: payer and hospital context, portal and call integrations, denial logic, compliance processes, and an understanding of how revenue cycle teams actually work.

Yes. As part of portal retrieval, Luna can pull eligibility along with claim status and remittance information, reconciled against the claim in your system.

Yes. Every claim carries a record of the actions taken and the outcomes, so your team has accountability and visibility rather than a black box.

Pricing is performance based. LunaBill bills 1.5% of net collections recovered, only after the money lands. There is nothing upfront, no license fees, and no implementation fees. If we recover nothing, you owe nothing.

LunaBill is fully performance based: you pay 1.5% of net collections recovered, billed only after the money is collected. There are no seats, no license fees, and no setup fees.

No. There is nothing upfront. Setup, EHR and clearinghouse integration, onboarding, the BAA, and ongoing tuning are all included in the performance fee. The first time you pay LunaBill anything is after it has recovered money for you.

It is the money that actually lands in your account on the claims Luna works, net of any reversals. You are billed a percentage of dollars collected, not of claims touched or hours worked, so the fee only grows when your cash does.

Then you owe nothing. The model is fully performance based, so the downside of trying LunaBill on your backlog is zero. That is also why we start with a free pilot on your actual claims.

Only after money is collected. LunaBill bills a share of net collections recovered once the payment lands, never in advance and never for effort that did not result in a collection.

No. LunaBill is not priced per seat or per license. You pay a percentage of what is actually collected, so cost scales with recovered revenue instead of with the size of your team.

Yes. LunaBill works a sample of your actual worklist on our dime so you can see the recovery and cost per claim on your own claims before any commitment. Pricing is performance based, so there is nothing to lose by testing it.

Everything: every AI agent in the platform, setup and integration with your EHR and clearinghouse, onboarding, the BAA, the full audit trail, and ongoing support and tuning as your payer mix changes. There is no separate line item for any of it.

Collection agencies typically take a large share of what they recover, and only after a claim has already aged and been handed off. LunaBill is performance based too, but it works claims before they age out, so you keep far more of what you are owed and fewer accounts ever reach the costly collection stage.

Traditional outsourcing bills you for effort: seats, hours, or FTEs, whether or not the claim is collected. LunaBill is billed on outcomes, a share of net collections, so your cost is aligned with recovered revenue rather than payroll.

Because the product is tied directly to recovered cash rather than a vague promise of saved time. Even a small percentage improvement in collections can represent meaningful dollars at a hospital with large net patient revenue, and you only pay on what actually lands.

Both, but the pitch is revenue first: LunaBill recovers money you are already owed that would otherwise be delayed, underworked, or written off. It also lowers the cost to work each claim, but the primary outcome is cash collected.

At Nutex Health, the fully loaded internal cost to work a claim was $22.28; with LunaBill the cost per claim was $2.00, roughly an order of magnitude lower. When the unit cost drops that far, claims that were uneconomic to touch become worth working.

No. Integration with your EHR and clearinghouse and the whole implementation are included in the performance fee. You do not pay a separate implementation cost.

The model is the same for both: performance based, a share of net collections recovered, billed only after the money lands. For RCM firms, that keeps your cost aligned with recovered dollars as you scale client portfolios.

Yes. That is what the free pilot is for. We work a sample of your backlog and show you the recovery and the cost per claim on your own claims before you commit to anything.

Yes, by design. Because billing is a share of recovered dollars, LunaBill earns more only when it collects more for you. The incentive is aligned by construction.

The engagement starts with a free pilot on your real backlog, and pricing stays performance based throughout, so you are not locked into paying for a tool that is not producing collections. For specifics on terms, the team will walk you through them on the first call.

At Nutex Health, a 24 campus U.S. health system, LunaBill worked $32M+ of AR in 30 days with zero added headcount. Days in AR on 60+ day commercial claims fell from 45 to 7, and fully loaded cost per claim dropped from $22.28 to $2.00.

LunaBill worked $32M+ of AR at Nutex Health in 30 days, with zero added headcount, across a 24 campus U.S. health system running Epic and GoRev.

On the hardest slice of the book, 60+ day commercial claims, days in AR at Nutex fell from 45 to 7 within three months of go live.

Fully loaded cost per claim went from $22.28 (Nutex's internal benchmark) to $2.00 (LunaBill's price per claim), roughly an order-of-magnitude reduction.

At Nutex, staff time per claim follow up fell from 22 minutes to 4, because the agents took over the holds, the portal pulls, and the routine resubmissions.

Across the LunaBill portfolio, trailing 30 days, the agents handle more than 90,000 payer interactions a month.

Portfolio wide, trailing 30 days, LunaBill worked $64.4M of claim value and handled 90,000+ payer interactions per month.

No. Nutex worked $32M+ of AR in 30 days with zero added headcount. The 60+ person revenue cycle team stayed in seat and moved to the work that needs a human while the agents absorbed the volume.

Yes. The Nutex Health case study details how a 24 campus health system took 60+ day commercial claims from 45 to 7 days in AR, cut cost per claim from $22.28 to $2.00, and added zero headcount. It is available on the case study page.

The 11.1× figure is the ratio between Nutex's fully loaded internal cost per claim ($22.28) and LunaBill's price per claim ($2.00). It is a cost ratio, not a net ROI figure, and cost per claim is labeled that way throughout the site.

“Worked” means a claim received a completed status retrieval, payer call, denial action, or resubmission through LunaBill. Days-in-AR figures are measured on commercial claims aged 60+ days, comparing the three months after go live with the period before.

Yes. The headline figures come from the Nutex Health engagement, a 24 campus U.S. health system on Epic and GoRev, plus portfolio-wide totals across all LunaBill customers over the trailing 30 days.

Reworking a denied commercial claim costs $63.76 on average, per Premier Inc. ($43.84 across all payers). At that cost, teams triage rationally and let the long tail rot, which is why, per the Change Healthcare Denials Index, 65% of denied claims are never reworked at all.

Per the Change Healthcare Revenue Cycle Denials Index, 65% of denied claims are never reworked at all. Lowering the cost to work a claim is what turns that unworked revenue back into money worth collecting.

LunaBill plugs into the systems you already run, including Epic, Cerner, GoRev, Waystar, and Availity. Most customers are piloting on their own claims within 48 hours, with a BAA signed in under a day.

Yes. Luna works the AR queue inside Epic, reading claim status, eligibility, and remittance where your team already lives. Nutex Health runs Epic and GoRev.

Yes. Luna runs inside Cerner to pull status, handle denials, and resubmit, with no new system for your billers to learn.

Yes. LunaBill is native to GoRev workflows for hospital revenue cycle operations, from status checks through resubmission.

Yes. Luna retrieves status and remittance through Waystar and resubmits corrected claims through your existing clearinghouse.

Yes. Luna logs into Availity to pull claim status and eligibility across payers automatically, in parallel across the queue.

Luna retrieves status from payer portals including Availity, Waystar, and payer-specific portals, and falls back to a payer call when the portal cannot answer.

The named systems are where most of our customers run today, not a hard limit. Tell us your stack on the first call and we will scope integration during onboarding.

No. Luna operates inside the EHR and clearinghouse your team already uses. There is no new application for your billers to learn.

Agents read claim status, eligibility, and remittance data. Posting back to the EHR, such as ERAs and call notes, is scoped and configured with your team during onboarding, and every action carries a full audit trail.

Inside them. Luna operates in the systems your team already trusts, with scoped access and an audit trail on everything, rather than bolting on a separate tool alongside your stack.

Most customers are piloting on their own claims within 48 hours, with a BAA signed in under a day. Integration with your EHR and clearinghouse is part of that onboarding.

Yes. Luna retrieves status and remittance and resubmits corrected claims through your existing clearinghouse, including Waystar and Availity.

Yes. The agents run in parallel across portals and systems, so status retrieval and follow-up happen across the whole queue at the same time rather than one login at a time.

LunaBill focuses on the hospital revenue cycle and works inside the EHRs and clearinghouses hospitals run. If your environment spans multiple billing systems, tell us on the first call and we will scope it during onboarding.

Credential storage, secrets management, and access controls are documented in our security packet, shared during vendor review, and every portal action carries a full audit trail your compliance team can review.

Yes. As part of portal retrieval, Luna can pull remittance and ERA data alongside claim status, and reconcile it against the claim in your system.

LunaBill works inside the systems hospital revenue cycle teams already run. Share your specific practice-management and EHR setup on the first call, and we will scope what integration looks like for you.

Yes. LunaBill is HIPAA compliant with enterprise grade security, executes a BAA before any PHI moves, and is SOC 2 Type I with Type II in progress. A public trust center is available at trust.lunabill.com.

Yes, before any PHI moves. The BAA is typically executed in under a day, and standard go live is 48 hours from signature. No PHI touches LunaBill systems until the BAA is in place.

LunaBill is SOC 2 Type I certified. The Type II audit is in progress, and you can track live control status at trust.lunabill.com. The Type I report is available under NDA during security review.

Disclosure is handled per payer and state requirements. Where a payer or state requires the agent to identify itself as automated, it does.

PHI is handled exclusively inside the product under a signed BAA, with enterprise grade security and a full audit trail on every agent action. No PHI moves before the BAA is executed.

Call recordings and transcripts follow a documented retention schedule, covered in the security packet and tailored to your policies during onboarding.

A current subprocessor list, with the role each one plays and the agreements behind it, is provided during security review and kept updated under the BAA.

No. The marketing site collects only contact details you choose to share. PHI is handled exclusively inside the product, under a signed BAA.

Yes. A public trust center is available at trust.lunabill.com, where you can track live control status and see the current security and compliance posture.

Please do. We would rather clear vendor review in week one than month three. The security packet, SOC 2 report, and subprocessor list are ready when your IT, compliance, and privacy reviewers are.

The security packet documents credential storage, secrets management, access controls, data retention, and subprocessors, and is shared during vendor review so your team can complete their assessment quickly.

Yes. Every action an agent takes on a claim is recorded in a full audit trail that your compliance team can review at any time.

Access is scoped and configured with your team during onboarding. Agents read claim status, eligibility, and remittance; write-back is explicitly scoped, and access controls are documented in the security packet.

LunaBill uses enterprise grade security to protect data. Specifics on encryption, secrets management, and access controls are documented in the security packet shared during vendor review.

Only after a BAA is signed. No PHI touches LunaBill systems until the Business Associate Agreement is executed, which typically happens in under a day.

Yes. LunaBill is built for the teams who say no, meaning IT, compliance, and privacy reviewers. The trust page answers the questions those teams ask on every vendor call, before the call.

The SOC 2 Type I report is available under NDA during security review. Type II is in progress, with live control status tracked at trust.lunabill.com.

Your team keeps the judgment calls and handles escalations and complex appeals, while agents do the mechanical volume. Every action is auditable, and oversight is configured with your team during onboarding.

LunaBill is designed to pass hospital compliance and IT review: HIPAA, SOC 2 Type I, a fast BAA, documented security controls, and a trust center. Bring your procurement and security teams to the first call and we will work through their checklist.

PHI is handled inside the product under your BAA and governed by the agreements documented during security review. The subprocessor list and data handling are provided and kept current under the BAA.

Because the security packet, SOC 2 report, and subprocessor list are ready up front and the BAA executes in under a day, LunaBill is built to clear vendor review fast rather than dragging on for months.

Yes. LunaBill is HIPAA compliant with enterprise grade security, SOC 2 Type I certified (Type II in progress), and carries a full audit trail on every agent action.

At the public trust center, trust.lunabill.com, which shows live control status, plus the security packet and SOC 2 report shared during security review.

Only what you scope. Agents read claim data by default; write-back, such as ERAs and call notes, is explicitly scoped and configured with your team during onboarding, with a full audit trail.

Book a short demo. We show Luna working a claim on your payer mix and EHR, sign a BAA, and scope a free pilot on your actual backlog. Most customers are piloting within 48 hours.

Most customers are piloting on their own claims within 48 hours, with a BAA signed in under a day. Because there is no new software for staff to learn, there is no long training cycle.

A signed BAA and scoped, read access to a sample of claims in the systems you already use. No new software for your team to learn, and no PHI moves before the BAA is in place.

A short demo. We show Luna working a claim on your payer mix and EHR, walk through security and compliance, and scope a free pilot on your backlog. Bring whoever needs to see it, including IT and compliance.

We work a sample of your real worklist through LunaBill on our dime, then show you the outcomes and the cost per claim on your own claims before any commitment. Pricing stays performance based, so there is nothing to lose.

The BAA is typically executed in under a day. No PHI moves to LunaBill until it is signed.

Revenue cycle leadership to scope the work, plus IT and compliance for vendor onboarding. Bringing security to the first call is encouraged, so review happens up front rather than later.

No. There is no new application for your billers to learn, so onboarding is about integration and access rather than staff training. Most customers are piloting within 48 hours.

Yes. The pilot is scoped on a sample of your actual worklist, so you can start small, see the recovery and cost per claim on your own claims, and expand from there.

You can book a demo directly from the site, or email suhail@lunabill.com. No PHI is required to book, and the first call includes a walkthrough on your real claims.

The free pilot. We work a sample of your backlog on our dime and show you the recovery on your own claims, usually within days of signing the BAA, before you commit to anything.

Only under a signed BAA, and only for the pilot scope. No PHI touches LunaBill systems until the BAA is executed, which typically happens in under a day.

Yes. Many customers start with a narrow, high-value workflow such as claim status calls and expand into portal checks, denials, appeals, and full AR follow-up once Luna is integrated and trusted.

Signing a BAA, scoping access to the systems you already run, and configuring what the agents read and write back. There is no new software to deploy for your staff, and it is included in the performance fee.

LunaBill is built for hospital and health system revenue cycle teams that need to work a growing backlog without growing headcount, and for RCM and BPO firms that want to scale client portfolios without scaling payroll.

LunaBill focuses on hospitals and health systems and the RCM and BPO firms that serve them. Its core work is the hospital revenue cycle: payer calls, portals, denials, appeals, and AR follow-up.

Yes. RCM and BPO firms deploy LunaBill across client accounts to scale portfolios without scaling payroll, with a full audit trail on every claim they can hand to the client.

Yes. Smaller and rural hospitals often have the least leverage against payers and the most to lose from delayed revenue. Because pricing is performance based with nothing upfront, LunaBill is accessible without a large capital outlay.

Revenue cycle leadership is the economic buyer, with billers, claim-follow-up teams, and AR staff as the primary users, and IT and compliance involved in vendor onboarding.

Yes. LunaBill ties directly to cash: recovered collections, lower cost per claim, and aged receivables worked down. Because you pay a share of what is actually collected, the finance case is concrete rather than a productivity promise.

Yes, as their teammate. Billers and AR staff stop holding for payers and shift to reviewing outcomes and handling escalations and complex appeals, while the agents do the repetitive volume.

Yes. LunaBill's reference customer, Nutex Health, is a 24 campus U.S. health system. Because the agents run in parallel, LunaBill scales to large claim volumes without proportional headcount.

No. LunaBill is deliberately focused on the financial workflow, the revenue cycle, rather than patient access tasks like scheduling, intake, or general patient calls. Its advantage is deep revenue cycle expertise.

Any revenue cycle team facing a backlog it cannot fully staff. LunaBill is most valuable where claim volume outstrips the hours a team can spend on the phone, so lower-priority and aged claims are getting left behind.

Yes. BPOs use LunaBill to break the link between portfolio size and payroll, keeping turnaround and quality consistent across client accounts instead of swinging with staffing.

Yes. LunaBill can reduce dependence on large outsourced billing workforces and high-percentage collection agencies by automating the mechanical follow-up work, with cost tied to collections rather than to seats.

Hospitals that collect what they are owed are better able to stay financially viable and keep serving their communities. When a local or rural hospital is destabilized by unrecovered revenue, patients can end up traveling much farther for care.

Yes. Nutex Health, a 24 campus health system, runs Epic and GoRev, and LunaBill works inside both. It also runs inside Cerner and clearinghouses like Waystar and Availity.

LunaBill is a product of LunaHealth Technologies, Inc. It is an AI-native revenue cycle automation company focused on hospitals and RCM firms, and it is backed by Y Combinator.

LunaBill was built by Suhail Parry (cofounder and CEO) and David Day (cofounder and CTO), operators and engineers who shipped revenue cycle software before and saw exactly where it broke.

Yes. LunaBill (LunaHealth Technologies, Inc.) is backed by Y Combinator.

LunaBill treats revenue recovery as infrastructure for keeping hospitals viable. Stronger revenue operations help providers, especially smaller and rural ones, stay open and keep care locally accessible, so billing is framed as a patient-access story, not just a back-office one.

Healthcare AI and revenue cycle management: specifically AI-native accounts receivable automation for hospitals, including voice agents for payer calls and end-to-end claim-resolution automation.

It means the system is designed around the outcome, an accurate claim that gets paid, rather than digitizing paper-era front, middle, and back office silos. LunaBill rebuilds the workflow instead of layering AI on top of legacy structure.

The long-term thesis is that hospital revenue cycle work becomes largely automated and rebuilt as an AI-native system, with far fewer manual payer calls and claims resolved end to end, rather than preserving decades of technical debt and departmental handoffs.

Voice is the wedge, not the identity. Payer phone calls are a painful, high-volume, measurable workflow, so automating them earns trust and access. From there, LunaBill expands into the surrounding revenue cycle work where it has the deepest advantage.

Not just access to an AI model. The moat is revenue cycle domain expertise, hospital relationships and trust, workflow integration, operational reliability, responsiveness, and completed compliance and IT onboarding, which together are hard for a general-purpose model to replace.

A focused company can solve a revenue cycle team's problem in days rather than the months a massive, multi-product incumbent might take. LunaBill is built to be fast, responsive, and personally accountable to the revenue cycle buyer.

RPA replays a fixed, recorded sequence of clicks, so it breaks when a portal changes and cannot make phone calls or read unstructured denials. LunaBill's AI agents reason about each claim, adapt to change, call payers, and work denials end to end.

No. RPA operates on a screen and cannot place calls, hold, or navigate an IVR. LunaBill's voice agents do exactly that, which is where much of manual AR time is actually spent.

Offshoring moves labor cost but not the ceiling: throughput still tracks headcount, and quality and turnaround swing with staffing. LunaBill's agents run in parallel around the clock, and you pay a share of collections rather than for seats.

Collection agencies take a large share of what they recover and only after a claim has aged. LunaBill works claims before they age out, so fewer accounts ever reach the costly collection stage and you keep more of what you are owed.

Every biller you add comes with the same minutes per claim, the same hold time, and the same eight-hour ceiling, and labor is expensive. LunaBill adds capacity without adding headcount, working the backlog in parallel.

No. The agents do the mechanical volume, holds, portal pulls, and routine resubmissions, so your team stays in seat and moves to escalations, complex appeals, and patient-facing work.

LunaBill is a healthcare company that uses voice, not a general-purpose voice platform. Its advantage is revenue cycle workflow knowledge, payer and hospital context, and integrations, not training voice models for every industry.

A general model lacks payer and hospital context, workflow logic, integrations, operational reliability, and compliance processes. Those layers, plus customer relationships, are what turn raw model intelligence into a product that actually resolves claims.

Epic is a powerful incumbent, but its scale can mean a specific revenue cycle issue takes months to resolve, and its architecture can preserve old front, middle, and back office silos. LunaBill is an AI-native workflow built to move fast on the cash-flow problems hospitals need solved now.

Traditional denial software still relies on your staff to do the calling, portal work, and appeals. LunaBill's agents do that work themselves, end to end, and are billed on collections recovered rather than as a license.

Building this in house means recreating payer and portal integrations, call automation, denial logic, compliance, and reliability, then maintaining it as payers change. LunaBill delivers that as a managed, performance-based service with nothing upfront.

Once Luna is integrated across portals, calls, actions, and tracking, and has cleared compliance and IT review, it is embedded in the workflow rather than being a standalone endpoint, and it can expand into adjacent revenue cycle steps.