Money — what Bookodile does and does not do

Bookodile is booking and scheduling software. It does not take your customers' money. Payment happens between you and them, however you already do it — cash, card machine, bank transfer.

What Bookodile gives you is a record of what arrived, so your own numbers add up without a paper sheet. That is the payment-tracking add-on.

What the add-on records

For each visit: the amount received, the method, and the tip.

The model is one line:

received − price = tip

Received and price are the two figures you enter. The tip is whatever is left over, floored at zero.

Tips are never counted as revenue

A tip is stored separately and shown as its own figure everywhere. It is excluded from what the visit counted as taking.

This is the main reason the add-on exists. Money through the till and a gratuity are different things, and mixing them makes both numbers useless.

Where tips are shared between people, the split is frozen when it is recorded — later editing the price does not retroactively move money someone has already been given.

Part-payments edit the balance, not the total

When you record a payment, the amount field is pre-filled with what is still owed, not the full price of the visit.

Record €20 against a €32 visit and €12 remains outstanding. Record the €12 later and the visit is settled at €32. If you change that second figure, the visit's total becomes what you already collected plus the new balance — it does not overwrite the total.

"Unpaid" only appears once a visit has happened

A visit is only badged unpaid if it has already started and falls inside your tracked window. Confirmed but future bookings are not chased for money, and anything before you switched the add-on on is left alone.

That second part matters: switching on payment tracking in an established business does not surface years of past bookings as unreconciled. Tracking starts the day you turn it on.

The collection date is the date money arrived

A transfer that lands two days after the appointment belongs to the day it landed, not the day of the visit. Otherwise the daily totals never balance.

Who can see it

Recording a payment needs permission to manage bookings. Seeing everyone's money — including everyone's tips — is governed by whether someone can view all reports or only their own. That is what stops one team member reading another's tips.

What is not available

This is the part to be clear about, because it is easy to assume otherwise.

• Bookodile does not process payments. There is no card processing, no payment link sent to the customer, no money held or forwarded.
• Online deposits are not available. Services carry deposit fields in the data model, and there is scaffolding for a checkout step, but it is not switched on in production and there is no way to set a deposit from the dashboard. Do not promise a customer a deposit taken at booking time.
• There are no refunds to issue, because nothing was collected here.
• It is not a receipt or tax-document system. It records what you were paid. What you are required to issue, keep or declare differs by country — check what yours requires.
• No counter sales. A walk-in is a booking; there is one path in.

Worked example

A €45 colour appointment. The customer pays €50 in cash.

You record: received €50, price €45, method cash. The visit is marked paid, €45 counts as revenue for the day, and €5 is recorded as a tip — kept out of the revenue figure and shown separately in reports.

Next week you edit the service price. The €5 already recorded does not move.

Limits

• The add-on only records what you tell it. Nothing reconciles against a bank feed or a card terminal.
• Tip splitting is an equal split. There are no weighted rules.
• History is bounded by the date you enabled tracking.