Skip to main content

Payment Conditions

Define When You Get Paid

Updated today

There is a particular kind of frustration that most service professionals know deeply and personally, even if they have never named it out loud.

You show up.

You do the work.

You deliver something real — a legal consultation, a therapy session, a fitness class, a website feature, a financial review.

You send the invoice afterward, with a polite note that it is due within thirty days, and then you wait.

Sometimes the payment arrives promptly and you feel a brief wave of relief.

More often, the days stretch out.

You send a follow-up email.

Then another.

The client is not malicious; they are simply busy, and paying you is not their most pressing concern right now.

Meanwhile, your rent is due, your software subscriptions renew, your own invoices arrive from the people who supply the things that allow you to keep working.

This is the cash flow problem, and it is one of the most quietly damaging forces in the lives of freelancers and independent service providers around the world.

Cash flow, to be clear, is not the same thing as profitability. A business can be profitable — meaning that over time, it earns more than it spends — and still struggle with cash flow.

Cash flow is about timing.

It is about whether the money you are owed arrives in your account before the money you owe leaves it.

When you consistently do work first and collect payment later, you are essentially extending a short-term loan to every single client, often without thinking of it that way.

You are financing their consumption of your time with your own savings, your own credit, your own stress.

  • The solution to this problem is not to hire a collections agency or to become more aggressive in your follow-up emails.

  • The solution is to change when payment happens, and to build that change directly into the structure of how you do business.

This is precisely what payment conditions are designed to do.

Payment Conditions

A payment condition is, at its simplest, a rule that defines when payment is triggered in relation to the service you are providing.

It is not a separate conversation you need to have with each client, and it is not a policy you paste into the footer of your emails.

It is a setting built into your booking and invoicing process that determines the moment at which payment becomes required.

Schemon, the all-in-one platform built for freelancers and service-based businesses, allows you to configure payment conditions at the level of individual clients, client groups, or your practice as a whole.

You decide the rule.

The platform enforces it consistently, automatically, without awkwardness.

There are four distinct payment conditions available within Schemon, and each one serves a different purpose, suits a different relationship, and creates a different dynamic between you and your client.

Understanding all four — and understanding when to apply each — is one of the most practically valuable things a service professional can do for the long-term health of their business.

1) Payment at Booking

The first condition is payment at booking.

This means that a client cannot complete the booking process without providing payment at the same moment that they reserve their spot.

The booking and the payment are a single, indivisible action.

Think of it the way you would think of purchasing a theatre ticket or reserving a hotel room. The seat is not held, the room is not yours, until the card clears.

In the context of professional services, this condition communicates something important and entirely accurate: your time has value, and the act of reserving it carries a cost.

When a client books a session and pays at the same moment, they have made a genuine commitment. They have moved money from their account to yours in exchange for a specific block of your attention.

That transaction creates a psychological shift — the appointment becomes real to them in a way that a confirmed-but-unpaid booking simply does not.

The way this works within Schemon is straightforward.

When you set payment at booking as your condition, the client moves through the scheduling interface — selecting a date, a time, a session type — and at the final step, before the booking is confirmed, they are presented with a payment screen.

They can pay via credit or debit card, bank transfer, PayPal, or any other payment method you have enabled.

The booking is confirmed only after payment is successfully processed.

The client receives an automatic confirmation. You receive notification of both the booking and the payment. No invoice needs to be chased. No awkward email needs to be sent. The transaction is complete before the relationship has even formally begun.

This condition is particularly well-suited to new clients, to high-demand practitioners whose time is genuinely scarce, to sessions that are defined and bounded in scope, and to any professional who has experienced the specific pain of no-shows.

A no-show, to define the term precisely, is when a client does not appear for a scheduled session and does not give you sufficient notice to fill that slot with another client or productive work.

The economics of a single no-show are worth examining carefully, because practitioners often underestimate the true cost.

  • If your hourly rate is one hundred pounds, a no-show does not simply cost you one hundred pounds.

  • It costs you the time you spent preparing for that client, the time you kept available and could not offer to anyone else, and often the administrative time you spend following up afterward.

  • If you drive to a client's location or hold a room or studio, it costs you the travel and the room fee on top of everything else.

  • It may also cost you the emotional energy of sitting in uncertainty, wondering whether the client is simply late or has forgotten entirely.

When you add all of this together, the true cost of a no-show for many practitioners is significantly higher than the face value of the missed session.

Payment at booking eliminates this cost entirely. The client has already paid. Whether they attend or not, your time has been compensated.

The incentive structure for the client has also changed fundamentally:

they now have a financial reason to show up,

or at minimum, a financial reason to give you

adequate notice when they cannot.

2) Pre-Session Payment

The second payment condition is pre-session payment.

This is subtly but meaningfully different from payment at booking. With pre-session payment, the client can book the session without paying immediately, but they are required to pay before the session begins.

The session will not proceed until payment is confirmed. This condition is slightly more flexible — it allows the client to plan ahead and secure a time without needing their card in hand at that precise moment — but it maintains the fundamental principle that payment leads rather than follows the service.

Within Schemon, the flow for pre-session payment works as follows.

  1. The client books in the normal way.

  2. Schemon then automatically sends a payment request — this can be delivered within the app, via a payment link in an email, or through whichever channel you have configured.

  3. The client has until a defined point before the session to complete payment.

  4. If payment is not received by that time, the session is flagged and you can choose how to respond: you might send an additional reminder, choose to cancel the session, or reach out directly.

  5. Schemon handles the reminders automatically, so you are not in the position of manually chasing each client before every appointment.

The system does the administrative work so that you can focus on the professional work.

Pre-session payment is particularly useful for practitioners who see returning clients on a regular schedule, because it maintains cash flow consistency without requiring payment to happen at the exact moment of booking.

A therapist who sees clients weekly, for example, might find that payment at booking suits new clients, while pre-session payment works naturally for established clients who have a standing appointment and simply need to settle payment a day or two before the session.

3) During-Session Payment

The third condition is during-session payment.

This one is the most situational of the four, but it is precisely right for certain kinds of work.

In a during-session payment model, you generate and send a payment request while the session is actively in progress, typically after the scope of work has been discussed and agreed upon.

The client receives the payment request, reviews it, and pays while you are still in conversation together.

This model is particularly valuable in consulting, legal advice sessions, and any professional context where the scope of the work is not fully known until you have spoken with the client.

A lawyer who takes an initial consultation call, for example, may not know at the outset exactly how long the conversation will run or precisely which questions will need to be addressed. Once the relevant issues have been identified and a fee agreed, the invoice is sent mid-session and payment is made before the conversation concludes.

This eliminates the post-session invoice entirely and ensures that payment is never separated from the moment of value delivery.

Similarly, a business consultant who is brought in to diagnose a problem might find that the nature and depth of the problem only becomes clear during the initial session. Agreeing on a fee and collecting payment while the session is still happening removes the follow-up friction entirely.

Schemon makes this possible through its integrated payment request system, which allows you to send a payment link or request directly from within the platform during an active session.

Because Schemon's video chat and payment infrastructure are part of the same environment, you do not need to switch between tools or ask the client to navigate to an external website.

The request is sent, the client pays, and the session continues.

The entire flow is smooth and professional, which matters because the moment of payment should feel like a normal part of doing business, not an interruption.

4) Post-Session Payment

The fourth condition is post-session payment, and it is the most familiar.

Post-session payment means that the service is delivered first, an invoice is generated after the session concludes, and the client pays within an agreed timeframe.

Schemon handles the invoicing automatically — as soon as a session ends, an invoice can be generated and sent without you needing to touch it.

The platform also tracks payment status, sends automatic reminders for overdue invoices, and maintains a full transaction log so that you always know exactly where things stand.

Post-session payment is not inherently a bad model.

For long-established clients with a strong track record, for corporate accounts where invoicing is part of a structured procurement process, or for the specific kinds of professional relationships where billing after delivery is simply the norm, it works well.

The key is that it should be a deliberate choice applied to the right client relationships, not the default setting applied to everyone because it feels less awkward than asking for money upfront.

Client Groups Based Conditions

This brings us to one of the most powerful features of Schemon's approach to payment conditions: the ability to configure different conditions for different client groups.

In Schemon, clients can be organised into categories — you might call them new clients, returning clients, premium clients, or whatever groupings make sense for your practice.

Payment conditions can be set at the group level, which means that a new client who books with you for the first time is automatically required to pay at booking or before the session, while a long-standing client with a perfect attendance record and a history of prompt payment can be set to post-session invoicing without any manual intervention on your part.

The system knows which group each client belongs to, and it applies the appropriate rule automatically.

Client Ratings Based Conditions

This is also where Schemon's client rating system becomes relevant.

Schemon automatically tracks client behaviour over time — punctuality, attendance, payment promptness — and generates a behavioural rating for each client.

  • A client who repeatedly cancels at the last minute or pays invoices late will have a lower rating.

  • A client who consistently attends, pays promptly, and communicates reliably will have a higher one.

These ratings are not punitive; they are informational. They allow you to make smarter decisions about how to structure relationships.

A client whose rating has declined significantly might be moved from a post-session payment group to a pre-session payment group, not as a punishment, but as a reasonable business response to demonstrated behaviour.

Schemon's AI scheduling engine also uses these ratings to manage time slot allocation, prioritising reliable clients when slots are in demand.

Example Scenarios

Consider the practical transformation for a professional who makes the shift from a default post-session invoice model to a thoughtfully configured payment condition system.

A freelance web developer who previously completed project milestones, sent invoices, and waited thirty-plus days might instead configure payment at booking for initial consultations, require a deposit before work begins on any project, and use milestone-based payment requests sent during working sessions as scope is confirmed and deliverables are agreed.

The result is that money moves into their account at every meaningful stage of a project rather than in a single, uncertain lump at the end. Their cash flow becomes smoother, their financial stress decreases, and they spend significantly less time on administrative follow-up.

A fitness trainer who previously invoiced weekly sessions in arrears might switch to a monthly package model where clients pay upfront for a block of sessions, with pre-session payment required for anyone who wants to book on a single-session basis.

Their revenue becomes predictable — they know at the beginning of each month exactly what they will earn from existing clients, and any new bookings represent additional income on top of a stable base.

A no-show from a client who has pre-paid does not cost them a session's income; it frees up an hour they can use for planning, professional development, or simply rest.

A therapist working in private practice might use payment at booking for all new clients — this serves as an implicit commitment device that ensures people who are genuinely motivated to begin therapy are the ones who take up her limited weekly slots — while moving established clients, particularly those in ongoing therapeutic relationships, to pre-session payment that is processed automatically a day before each session.

The administrative overhead of managing payments across a full caseload drops dramatically, and the conversations that do happen with clients are focused on the therapeutic work rather than on chasing outstanding invoices.

A solicitor who offers paid legal consultations might use during-session payment exclusively. Clients book the session, they speak, the relevant issues are identified, a fee is agreed, the invoice is sent via Schemon's integrated system during the call, and payment is received before the call ends.

There is no ambiguity about whether the session was worth the fee, because the client has agreed and paid while the value of the advice is still fresh in their mind.

Conclusion

What connects all of these examples is not a specific payment condition but a philosophy that:

payment is not an afterthought,

not a conversation to be avoided,

not an uncomfortable request

that follows the real work.

Payment is part of the structure of professional service.

Defining when it happens is not about distrust; it is about respect — respect for your own time, respect for the sustainability of your practice, and ultimately respect for your clients, who deserve to work with a professional who is financially stable, appropriately compensated, and not carrying the invisible stress of cash flow uncertainty into every session.

Schemon's payment infrastructure is fully regulated and encrypted, meaning that every transaction is secure regardless of which method the client uses to pay.

Payment requests can be sent from within the app, via a shared link, or directly to a client's email address, giving clients maximum flexibility while giving you maximum certainty.

Custom invoices can be uploaded if your specific context requires it, and all transactions are logged and trackable from within your Schemon dashboard.

The transformation begins with a single decision:

to define, clearly and deliberately, when you get paid.

Not because you distrust your clients.

Not because you are difficult to work with.

But because a sustainable, well-run practice is one where the money flows in a way that supports the work, rather than undermining it from the inside.

Not Signed Up Yet?

If you are ready to take control of your cash flow, to stop chasing invoices, and to build a payment structure that actually reflects the value of what you do, visit schemon.com today and sign up.

Your schedule, your communication, your files, your sessions, and your payments — all in one place, all working together, finally built the way your business deserves.

Did this answer your question?