Why IVF Treatment Packages Break Ordinary Billing Software

A treatment package is a single payment and a long list of services delivered over weeks. Most billing software is built for the opposite: one service, one charge, one payment, settled the same day.

That mismatch is where package billing goes wrong. Not in the finance team, and not in the pricing — in the software’s inability to answer a simple question at any point mid-package: how much of this has actually been delivered?

A package is not one transaction

When a clinic sells a bundled cycle — monitoring, retrieval, embryology, transfer at a fixed price — it has made a commitment that unwinds over time. The money arrives at the start. The obligation is discharged in pieces.

Ordinary billing systems record the payment as a completed event. From that moment the ledger says the transaction is done, while clinically almost none of it has happened yet. Everything that follows — what has been delivered, what remains, what happens if the cycle stops — sits outside what the system can see.

This is not a rare edge case. Roughly half of US clinics offer some form of multi-cycle package or discounted bundle (FertilityIQ), and the underlying reason is clinical: most patients need more than one cycle to succeed (reported by PatientPay, citing Fertility Bridge). Packages exist because single-cycle pricing does not match how treatment actually goes.

What the billing engine has to know, and finance cannot tell it

Here is the part that gets missed. The billing system does not fail because the finance rules are complicated. It fails because it does not know what happened in the lab.

To charge correctly against a package, the system needs to know that the retrieval completed. That the transfer happened. That this particular cycle was cancelled at day nine. Those are clinical events, recorded by clinical staff, in the clinical record.

If billing lives in a separate system, that knowledge has to cross a gap — and it crosses it the same way it always does: someone reads one screen and types into another. Every reconciliation problem downstream starts there.

This is the specific reason a payments platform, however good, cannot solve package billing on its own. It can move money precisely. It cannot know whether the embryologist completed the fertilisation check this morning.

Milestone billing in practice

The alternative is to let the clinical event trigger the charge directly. MedART Billing ties invoices to clinical milestones — auto-billing on OPU completion, auto-billing on embryo transfer — so the financial record advances as the cycle advances, without anyone re-entering it.

Three things change when billing works this way:

1. Timing stops being a judgement call. The charge fires when the event completes, not when someone gets round to processing it.
2. The record matches the treatment. If the cycle stopped before transfer, the billing reflects that, because it never received the transfer event.
3. Nobody reconciles clinical against financial. They are the same data, read from the same cycle record.

Consumed versus included, mid-package

The question that exposes most systems is asked halfway through: what is left in this package?

Answering it requires the system to hold both sides — the services the package includes, and the services actually delivered so far. MedART tracks what is consumed against what was included as each milestone completes, which turns an open package from an unknown into a position you can read.

Without that, a clinic knows two things: what it sold, and what it collected. It does not know what it still owes in service terms — and that number is the one that matters when a patient asks to pause, switch protocol, or stop.

When the cycle is cancelled

Cancellation is the hardest case, and it is common enough that a package programme has to handle it as routine rather than exception.

Some of the package has been delivered. Some has not. The undelivered portion has to become something the patient can use later or get back — not a line item somebody writes off because unpicking it was too hard.

MedART processes partial and full refunds with reason documentation and a full audit trail, and applies credit notes against future invoices with configurable approval thresholds. The approval threshold matters more than it sounds: refunds are exactly the transaction where a clinic wants a defined authorisation path rather than an individual’s discretion.

There is a collections dimension too. Large outstanding balances are materially harder to recover — one analysis puts collection rates at around 32% for balances between $5,000 and $7,500, falling to roughly 17% above $7,500 (reported by PatientPay, citing TechTarget). A credit that never gets applied becomes a balance that never gets collected.

Cross-border patients and multi-currency packages

For clinics serving international patients, a package adds a second complication: it may be agreed in one currency and settled in another, across a treatment period long enough for that to matter.

MedART Billing supports invoicing in AED, KZT, PHP, GEL, USD and EUR among others — which is less a feature list than a reflection of where fertility patients actually travel. A clinic in Dubai billing a patient from Kazakhstan, or one in Manila treating patients from across the region, is running a package across a currency boundary as standard practice, not as an exception.

Insurance adds the same shape of problem. MedART supports IVF insurance billing including DHA NABIDH-connected claims, DOH MALAFFI-linked claims and TPA workflows, so a package that is partly insured does not have to be split across two processes.

What to check in your own system

You do not need to audit the whole revenue cycle. Ask three questions:

• Pick an open package. How much of it has been delivered? If answering means opening the clinical system and counting, billing cannot see the cycle.
• Take a cancelled cycle from last quarter. Where did the undelivered value go? If it was written off or handled by email, the credit path is manual.
• Ask what triggers an invoice. If the answer is a person, rather than a completed clinical event, every timing problem you have is downstream of that.

None of these need a project to answer. They tell you whether your billing system is reading the cycle or being told about it afterwards.

For the wider argument about clinical and financial data sitting in separate systems, see how to manage fragmented data in IVF clinics. And if you are setting package prices, the true cost of an IVF cycle covers why a package priced against an average will be underpriced for exactly the complex cases most likely to use it.

Reporting across all of it — collections, receivables, revenue by procedure — sits in AI & Analytics, which reads the same cycle records that MedART bills from.