Separate unbilled from unpaid
These are two different problems.
An unpaid invoice exists. It has a client, an amount, a date, and a status. The next step may be an automatic reminder, a payment link, or a calm personal follow-up.
An unbilled session has not reached that point. No invoice exists, so there is nothing for the client to pay and nothing for a reminder system to send. Waiting longer will not move it forward.
This distinction matters because a general thought such as "I need to deal with billing" is too vague to act on. You need two lists:
- Completed sessions that do not have an invoice
- Sent invoices that have not been paid
Work the first list before the second. Creating the invoice is the handoff that makes every later step possible.
Decide when a session becomes billable
The cleanest billing process begins with one plain rule: when is a session ready to invoice?
For many practices, the answer is when the appointment is marked complete. For others, you may need to confirm the service provided, add a product, adjust the fee, or wait for a practitioner to finish a small piece of documentation.
The exact rule can vary. The important part is that it is visible and consistent.
If one practitioner invoices at checkout, another waits until Friday, and a third assumes the front desk will handle it, the gaps are not a memory problem. They are a handoff problem. Nobody can reliably find work that does not have an owner or a moment attached to it.
Write down the trigger in one sentence:
A session is ready to invoice when [specific event happens].
Then name who owns the next step. In a solo practice, that may still be you, but naming the role helps. You are not vaguely "doing admin." You are closing the billing handoff for completed sessions.
Give the handoff a home in the day
You do not need to create every invoice the second a client walks out. You do need a dependable place where completed sessions become invoices.
Choose a moment that already exists:
- At checkout, before the client leaves
- Immediately after you mark the appointment complete
- During a short midday admin block
- Before you close the practice for the day
- In a twice-weekly billing pass
The best choice depends on how much each invoice changes.
If the service and price are usually the same as the booking, invoice creation can happen right away or automatically. If you often adjust line items, add products, or confirm coverage, a short review block may be safer.
Avoid building the process around "when I have time." Open time is usually claimed by something louder. A fixed handoff can be brief. An undefined handoff can sit for weeks.
Review exceptions, not every ordinary session
Billing becomes heavy when every appointment requires a fresh decision.
Most completed sessions are ordinary. The client attended the service that was booked. The price is correct. No special item needs to be added. Those sessions should move through the same path each time.
Save your attention for exceptions:
- The service changed during the visit
- The session ran for a different length
- A package or credit should apply
- The appointment was complimentary
- A product or assessment needs its own line item
- The client or insurer needs different invoice details
Mark the exception while the session is still fresh. A short, privacy-safe billing note such as "confirm package balance before invoicing" is more useful than trying to reconstruct the decision next week.
Do not put clinical details into a billing task or a personal note. The billing cue should tell you what action is needed without copying private care information into a place that was not designed to hold it.
Run a short missing-invoice check
Even a good process needs a backstop.
Once or twice a week, compare completed, billable appointments with the invoices that exist. You are looking for absence, not doing a full financial review.
For each missing invoice, ask:
- Was this a completed appointment with a client and a fee?
- Is there already an invoice somewhere under a different date or number?
- Was the session meant to be included in a package, written off, or provided at no charge?
- If it should be billed, what is the smallest next step?
That last step should usually be "create the draft," not "solve everything."
A draft gives the session a visible place in the billing workflow. You can review the details before sending it. Leaving the session only on the calendar asks the calendar to do a job it was not built to do.
Keep this check narrow. You are not reconciling the bank, reviewing every paid invoice, or rewriting your policies. You are finding completed work that never crossed into billing.
Start with the oldest gaps
When you find several unbilled sessions, the newest one often feels easiest. The details are fresh and the client may still be on this week's calendar.
Start with the oldest instead.
Older gaps are more likely to become awkward if they sit longer. The client may not remember the expected amount. A package balance may have changed. You may need more time to confirm what happened.
Open the oldest session, verify the service and fee, create the draft, and move to the next. If something is unclear, place it in a small exception list with one specific question. Do not let one complicated case stop the ordinary invoices behind it.
You may also discover that a session should not be billed. That is useful. Record the correct outcome so it stops appearing as unfinished work.
The goal is not to force every calendar entry into an invoice. The goal is for every completed, billable session to have an intentional outcome.
Make the first cleanup calm
If you have been relying on memory, the first review may uncover more than you expected. Do not turn that discovery into a verdict about how you run your practice.
Pick a small batch, such as the five oldest sessions. Verify each one. Create the drafts that should exist. Name the exceptions. Then stop and schedule the next batch.
Be careful about sending old invoices without checking them. Confirm the client, service, amount, date, tax treatment, package status, and any payment already received. A fast cleanup that sends the wrong charge creates more work than a measured one.
If a delayed invoice may surprise the client, use one direct sentence when you send it:
I noticed the invoice for your [date] appointment had not been sent. I have corrected that now, and the details are included here. Please let me know if anything looks different from what you expected.
You do not need a long apology or a story about why it happened. Take responsibility, give the client a clear way to ask a question, and keep the tone factual.
Fix the point where the gap begins
After the backlog is clear, look for the repeated cause.
Perhaps appointments are not being marked complete. Perhaps the person who creates invoices cannot tell when a fee changed. Perhaps package sessions follow a different path that nobody documented. Perhaps you wait until the end of the week, when the details are already fading.
Change the earliest broken step.
If the ordinary service and price rarely change, automate invoice creation or attach it directly to appointment completion. If invoices need review, make the draft automatic and keep sending as the human step. If exceptions are the problem, create one clear way to flag them before the handoff.
The goal is not to remove your judgment. It is to stop spending judgment on the sessions that do not need it.
Let completed work become visible money
Care can be complete while the administrative record is not. That does not mean you failed to finish the work. It means the practice needs a clearer bridge between the session and the invoice.
Start by separating unbilled sessions from unpaid invoices. Choose the moment when a session becomes billable. Give the handoff an owner. Then run a short missing-invoice check often enough that no gap has time to become old.
Stillpoint brings completed, billable sessions without invoices and overdue invoices into one Receivables view. You can create a draft invoice from the missing-session list, or set a service to generate invoices automatically when that fits your workflow. The aim is simple: make sure completed work does not depend on memory to become visible.
