Treatment sold as a package of sessions

A clinic sells a course of treatment: ten sessions, paid up front, often at a discount against the single-session price. It is a good commercial arrangement for both sides and it quietly turns a healthcare system into an accounting one.

The money has been received. The care has not been given. Until the tenth session, the clinic holds an obligation rather than revenue, and the balance owed is denominated in sessions, not currency.

Two ledgers that have to agree

Every package has two running balances, and neither is derivable from the other without care.

The financial balance is what has been paid against what was agreed — straightforward while payment is a single transaction, considerably less so once instalments exist. The delivery balance is what has been given against what was promised: sessions scheduled, attended, cancelled, missed.

These drift apart immediately in practice. A patient on a monthly instalment plan can consume seven sessions in three weeks. Another pays in full and attends twice in a year. The system has to answer both what does this patient still owe and what does this clinic still owe this patient, and the second question is the one that gets forgotten because nothing prompts it.

Attendance is not one state

Booked, attended, cancelled with notice, cancelled late, did not attend. Each has a different effect on the package, and the policy differs by clinic:

• An attended session decrements the balance.
• A cancellation with adequate notice usually does not.
• A late cancellation or non-attendance may decrement it, which is the clinic's protection against an unused slot.

That last rule is where disputes come from, so the record has to show what happened and when it was communicated — not merely that a counter went down. A session consumed without care being delivered is a decision the patient will eventually query, and the system says so is not an answer.

Instalments against consumption

Instalments introduce the case that causes the most trouble: a patient who has consumed more sessions than they have paid for, and stops paying.

The clinic has delivered care it will not be paid for. The system needs to have seen this coming — which means the relationship between payments received and sessions consumed has to be visible while it is developing, not discovered when a card fails.

The design question is whether consumption is allowed to outrun payment at all, and by how much. It is a business decision, but it has to be a decision. Systems that never ask end up extending unsecured credit by accident.

Multiple branches, one balance

Once a package bought at one location can be used at another, several previously simple things stop being simple.

Which branch recognises the revenue? Which one carries the liability for the undelivered sessions? If the two are different, the internal transfer has to be recorded, or one branch's figures will look better than they are and another's worse.

Sessions are also consumed concurrently in ways single-location systems never test — the same package used at two branches on the same day, both writing against one balance. The counter needs to be authoritative in one place rather than cached in two.

Expiry and refunds

Both are policy questions the system must express rather than assume.

Packages that lapse after a period raise the question of what happens to sessions already paid for, and forfeiting prepaid care outright is the sort of term that attracts attention from outside the clinic. Whatever the policy is, it should be visible on the record from the day of purchase, not applied retrospectively.

Refunds are the sharper case. A ten-session package was discounted against the single-session price. The patient has taken four sessions and wants to stop. Refunding at the package rate means they received discounted sessions on the strength of a commitment they did not keep. Refunding at the single-session rate means clawing back the discount, which needs to have been disclosed at purchase.

There is no universally right answer. There is only an answer the clinic chose, disclosed and applied consistently — and a system that cannot express both options will force one silently.

Why it is worth modelling properly

Treated as a counter on a patient record, this works until the first instalment plan, the first transfer between branches, or the first mid-course refund.

Treated as an obligation with two balances, a delivery history and an explicit policy for each edge, it holds. The difference in build cost is a matter of days. The difference afterwards is whether the clinic can tell you what it owes.