Defaults and refunds: protocol for centers (and minimum version for self-employed workers)

Defaults rarely start out as a conflict. They usually start out as something small: “I'll do it to you later”, “I missed it”, “the transfer is done”, “it gave me an error”, “I'll send it to you tomorrow”.

Friction appears when there is no protocol. When each case is handled differently, when the therapist resolves it between sessions, when a return is made without a trace and the team ends up with the feeling of putting out fires.

This article gives you a clear protocol for Defaults in a psychology office, with a full version for schools and a minimum version for freelancers. It includes an internal checklist and communication templates to keep you calm and in a good tone.

‍

Why defaults wear out so much

A default weighs on the outstanding money, yes. But most of all it weighs because of the head it carries.

In individual consultation, the charge is mixed with the therapeutic relationship and sometimes it is difficult to find the right point: to be clear without bothering. In centers, in addition, the volume enters. There are more charges per day, more payment methods, more hands touching the process and more chances of an earring being left “floating” without an owner.

When the system is properly assembled, most cases are resolved quickly. When it isn't, the same default generates three problems at once: uncomfortable communication, lack of registration and eternal month closures.

‍

Two decisions that save you 80% of the hassle

Who communicates to the patient

In centers, it usually works very well if the therapist is not the one who manages the outstanding charge. It protects the clinical relationship and prevents the topic from creeping into the session. It is usually carried by coordination or administration, with a neutral and consistent tone.

In freelancers, you manage it yourself, but it helps to use short and repeatable messages. When you improvise, you end up dedicating more energy than necessary.

When a payment becomes “pending”

Define a clear criterion. For example: payment pending at the end of the session, payment pending if it is not reflected in 24—48 hours, or payment pending if the transfer does not arrive in X days. The important thing is that the team wears the same watch.

‍

Protocol for schools: defaults and returns without improvising

This flow is designed to hold volume without burning the equipment. If you apply it consistently, lower the back-and-forth and improve traceability.

Step 1. Detect and record the earring

As soon as it is detected, it is marked with:

• patient
• associated session
• Amount
• intended method
• status: pending/under review/resolved

The key is that you don't stay in a chat.

Step 2. Review billing before writing

Before contacting, see if there is an invoice and what state it is in. Here it helps a lot to be clear about the difference between draft and final. If your team needs to align, this article calmly explains it:
https://www.eholo.health/blog/factura-en-borrador-vs-factura-definitiva-cual-es-la-diferencia-y-por-que-es-importante

Step 3. First contact: neutral, short, without voltage

The first message is intended as a reminder. A lot of defaults come from carelessness or friction with the payment method.

Step 4. Second contact: resolve with a clear path

If there's no answer, the second message makes it easy: payment link, transfer details, or alternative. Time is saved here.

Step 5. Closure and internal registration

When you pay or agree on something, you record:

• payment date
• method
• if there was an adjustment, discount or compensation
• If there was a return and reason
• What's going on with the bill

Step 6. Returns: always with traceability

If there is a refund, it must be associated with the original payment and the session. This avoids the typical “it was returned, but I don't know who did it or why”.

‍

Minimum version for freelancers: 5 sustainable steps

If you're working on your own, what helps is to have a clear thread that you can repeat without thinking too much:

1. Define when you think a payment is pending.
2. Send a short, neutral first message.
3. If necessary, send a second message with a clear payment method.
4. Decide what to do if X days go by without an answer.
5. Always record the closure: date, method and session.

When this is defined, non-payment ceases to occupy mental space between sessions.

‍

Internal checklist for centers

Before writing to the patient:

• Correct session and amount?
• Agreed method?
• Is there an invoice? Is it in draft or final?
• Who is contacting, coordination or administration?
• Is there a prior agreement, bonus, exception or incident?

After solving:

• Registered payment with date and method?
• Issued or updated invoice, if applicable?
• If there was a refund, is it linked to the original payment?
• Is there anything that needs to be adjusted so that it doesn't happen again?

This checklist avoids most silly mistakes and removes friction in closures.

‍

Communication templates

Adjust the channel to the way you work. In centers, these templates go very well when they are always used by the same team figure and with a consistent tone.

1) First message: neutral reminder
Hello, [Name]. We are writing to you for the outstanding payment for the [day] session.
When you can, you review it and confirm it for us. Thank you.

2) Second message: make it easy
Hello, [Name]. To leave it resolved, you can do it by [method] here: [link]/[data].
If you prefer another shape, let us know and we'll adjust it.

3) “It's already paid”
Thank you, [Name]. We review it and confirm it as soon as it appears reflected.
If you have it handy, you can send us the receipt and we will leave it registered.

4) Error with card or link
Thank you for letting us know. Sometimes it fails because of a bank issue or coverage.
Please try again in a few minutes. If it's still the same, let us know and we'll give you an alternative.

5) Close
Perfect, you're already registered. Thank you, [Name].

6) Short email (center)
Subject: Payment pending for the [day] session
Hello, [Name]. We are writing to you for the outstanding payment for the [day] session. To leave it resolved, you can do it by [method] here: [link/data].
If you prefer another option, reply to this email and we'll handle it.
Thank you,
[Center Signature]

‍

Returns with order

Returns usually appear due to duplicate billing, amount error, cancellation with an agreed return, or administrative adjustment. It helps to take it easy here, because a return without registration causes problems later.

Before returning, always check:

• What is the original payment
• If an invoice has been issued and what state is it in
• What is registered and what remains to be registered

If you need to review the minimum data on an invoice to avoid issuance errors, this guide makes it very clear:
https://www.eholo.health/blog/datos-de-facturacion-que-debe-contener-una-factura-al-ser-psicologo

‍

Common mistakes that turn an earring into a problem

• Leave the pendant in messages and do not register it.
• Send long or tense reminders right from the start
• Do not check if there is an invoice and what state it is in before making an adjustment.
• In centers, it is not clear who manages and who registers.
• Make a return and not link it to the original payment and the session.

These errors appear out of haste, not out of ill intent. A short protocol reduces them a lot.

‍

Eholo Pay for billing and traceability

When there are defaults and refunds, the same thing almost always hurts: poor visibility and little connection between collection, session and billing. The payment comes by one method, the session lives on the agenda, the invoice is issued on the other hand and, when it is necessary to rebuild what happened, time is wasted and there is room for errors.

This is where Eholo Pay It usually helps in a very practical way. The idea is that the payment is more connected to the workflow of the center or the query, so that you have traceability and can resolve issues without relying on messages, memory or Excel.

On a daily basis, this translates into concrete things:

• clearly see which sessions are paid and which are still pending
• have a single point of reference for reviewing what was charged, when and by what method
• allow coordination or administration to manage the circuit with common criteria, without burdening the therapist with persecution
• Maintain order in adjustments and returns to make closures easier

You can see it here:
https://www.eholo.health/soluciones/eholo-pay

‍

So that defaults and returns don't eat up your day

Defaults and refunds will exist. What makes the difference is whether each case is resolved “as it comes out” or if the center has a clear thread: who manages, when it is contacted, what is reviewed before returning and what is recorded afterwards.

With defined roles, an internal checklist and consistent messages, most issues are resolved quickly and in a good tone. In addition, the computer stops loading the situation in its head, because the process is sustained by system, not by memory. If you want to start with a simple improvement, adopt the minimum version: a pending criterion, two standard messages and an always-registered closure. In centers with volume, the leap in quality usually comes from the same thing: a single point of registration and traceability so that payment, session and invoice are not separated.

If you want to see how a more orderly billing flow would fit into your daily life, you have Eholo Pay here:
https://www.eholo.health/soluciones/eholo-pay

‍