The receipt that went to the ex-partner
A mother brings her son in for an appointment and pays on the day with her card. The receipt goes to the email on the son's record, which is his father's, because that was the parent who registered him two years ago. The father rings to ask why he is being sent medical receipts for a visit he did not know about.
Separately, a teenager's appointment reminder goes to a parent's phone when the teenager asked for it to come to them. An insurance-style invoice for a husband's travel vaccinations lists his wife as the patient. Each one is a small error, and each one lands with a family who is paying you for a more personal service than the NHS.
Why one patient, one payer does not fit families
Most practice management systems were built around a single patient who books and pays for themselves. Contact details on the record do double duty: the same email gets reminders, receipts, results notifications and marketing. When the person who pays is not the patient, staff improvise, often by typing a parent's email into the child's record.
That works until families change. Parents separate, children turn sixteen, a grandparent starts paying for the school fees plan, a spouse takes over a corporate policy. The contact fields never get revisited, so messages drift to whoever was right years ago.
What household mix-ups cost
| Mix-up | Consequence |
|---|---|
| Receipt to the wrong parent | A complaint, and possibly a confidentiality concern for your records |
| Teen messages to a parent | Lost trust with a patient who is old enough to choose |
| Unpaid child invoices | Nobody chases because nobody knows who owes it |
| Duplicate accounts | Two records for one child created by two parents |
| Manual workarounds | Reception editing contact details before each visit |
The confidentiality angle is for your own governance lead to judge. Our part is making it hard for the system to send a message to the wrong person in the first place.
How we set up household billing that follows the family
- We add a payer link to each patient, pointing to the adult or organisation who pays, stored separately from the patient's own contact details.
- Billing messages (invoices, receipts, payment reminders) go to the payer. Appointment and clinical admin messages go to the contact the patient or guardian chose.
- A household view groups the people one payer covers, so reception can see the family plan at a glance.
- When a patient reaches an age your policy sets, staff get a prompt to review who receives what, rather than the system changing it silently.
- Changes to payer or contact details are logged with who made them and when.
- Where your practice system has an API, we write to it. Where it does not, the payer register and messaging sit alongside it and read appointment data from an export.
Day to day, once payers are separate
Reception stop editing emails before a visit. A parent who pays for three children gets one consolidated statement if you want that, rather than three scattered receipts. Separated parents are handled with a clear record of which adult is the payer and which receives appointment messages.
When something does need changing, there is one place to change it, and a history showing why.
It also makes the unpaid invoice problem smaller. When a child's bill is overdue, the reminder goes to the adult who agreed to pay it, and staff can see the whole household balance before deciding whether to raise it at the next visit.
Does this sound like your front desk?
- Children's records hold a parent's email in the patient contact field
- Receipts or reminders have reached the wrong family member
- You cannot easily list everyone one card pays for
- Duplicate records exist for the same child
- Nobody reviews contact preferences when a child becomes a teenager