Studio booking deposits are the first money rule most studios need to get right, and the one that causes the most disputes. If a client cancels a shoot two days before, who keeps the deposit? If a prepaid package is half used, what gets invoiced? This guide explains how to define deposits, cancellation windows, reschedules and package balances so that the booking calendar and the accounts always agree, whether you bill in Egyptian pounds or mix currencies.
Why deposits and cancellations break studio operations
Most studios start with a shared calendar, a WhatsApp group and a notebook for payments. That works until two clients want the same room, a cancelled shoot is still on the invoice, or a deposit is paid but never matched to a booking. The root cause is usually not the calendar. It is that the money rules live in people's heads rather than in the system.
Writing the rules down before you build anything is the cheapest fix. Once they are written, they become the specification for your booking software, and a vendor can price and test them.
Choose a deposit model that matches your bookings
Different studios need different deposit models. Pick one per service type rather than one for the whole business, because a half-day portrait session and a multi-day commercial production carry very different risk.
- Full prepayment: the client pays the whole amount to confirm. Simple to reconcile, but it can slow down bookings from corporate clients who pay on invoice.
- Percentage deposit: a fixed share, often on the order of a third to a half, confirms the slot and the balance is due before or on the day.
- Flat booking fee: a non-refundable amount that reserves the slot, separate from the service price. Works well for long productions.
- Pay on the day: no deposit, suitable only for repeat clients with a good payment history or for low-value services.
Whichever model you choose, the system should record the deposit as a payment against a specific booking, not as a loose balance on the customer account. That single link is what makes refunds and disputes traceable later.
Cancellation and reschedule rules to encode
A cancellation policy is a table of notice windows and outcomes. Keep it short enough that staff can apply it without calling a manager every time. The table below is an example to adapt with your team, not a standard.
| Notice before the session | Deposit outcome | Reschedule option |
|---|---|---|
| More than 7 days | Refunded, minus a stated processing fee, or held as studio credit | One free reschedule within 60 days |
| 2 to 7 days | Part retained, for example 50 percent | One reschedule, subject to slot availability |
| Under 48 hours or no-show | Fully retained | No reschedule |
Three details are easy to forget and cause the most disputes:
- Which clock counts: the notice period should be measured from the moment the cancellation is received, using the system timestamp, not from when staff read a message.
- Who can override: define which role can waive a rule and make every waiver leave an audit trail.
- Force majeure and studio-side cancellations: if the studio cancels, the client should get a full refund or a rebooking with no penalty. Build this path too, or it will be handled by hand.
Handle prepaid packages and partial use
Packages, such as ten editing hours or a set number of studio sessions, create a balance that must be tracked over time. A package is a liability until it is used, so the system needs to show remaining value per customer at any moment.
Define four things in advance:
- The unit of use: a session, an hour, or a deliverable.
- The expiry rule: for example, 12 months from purchase, and whether unused value is refunded or forfeited.
- When invoices are issued: at purchase for the full package, or at each use. Your accountant should confirm which treatment fits your tax position.
- How overages are priced: usually at the standard rate, shown clearly on the next invoice.
When a session is booked against a package, the system should deduct the balance automatically and stop the booking if the balance is zero. Manual deductions are where package balances drift out of sync.
Invoicing in EGP without reconciliation pain
Every deposit, balance payment, refund and credit should produce a traceable entry. Give invoices and credit notes sequential numbers, store the tax treatment with each line, and keep Egyptian pound amounts rounded consistently so totals match the bank records. If your business is required to issue electronic invoices, the same booking data must feed that process, which is covered in our article on e-invoicing requirements in Egypt.
If your studio also runs equipment, staff payroll or supplier purchasing, these money flows should reach your accounts from the same source. Keeping booking, invoicing and accounting in one data model is the main reason many studios move from spreadsheets to a custom ERP system as they grow.
What to build and what to test
Once the rules are written, the build scope is clear. A practical first release should include:
- Service catalogue with prices per service and per package, in EGP
- Deposit collection tied to a specific booking, with the model set per service
- Automatic cancellation outcomes based on notice time from the system clock
- Role-based waivers with an audit log
- Package balances that deduct on booking and block when empty
- Invoices, credit notes and refunds with sequential numbering
- Customer statements showing deposits, balances and credits
Test the edge cases before launch: a cancellation exactly at the notice boundary, a reschedule of a package booking, a refund after a partial package use, and a studio-side cancellation. Each should have a scripted test with the expected money outcome.
How we approach this in practice
We have built this kind of logic before. Our Inngez Studio Management System is a bilingual system for a media production studio, covering studio bookings, service pricing, customer accounts and invoicing in Egyptian pounds. The most useful part of that work is the discovery stage, where we turn the studio's unwritten rules into a specification that can be built and tested.
If you are planning a booking system and want the deposit and cancellation rules mapped before any code is written, contact us with your service list and your current policy. We will help you turn it into a scope a vendor can price. You can also see our wider range of custom software services.
Frequently asked questions
How much deposit should a studio ask for?
There is no universal figure. Many studios use a percentage deposit for standard sessions and a higher share or a booking fee for long productions. Set the amount by weighing your cancellation losses against how much friction clients will accept.
Should studio deposits be refundable?
Usually partly. A common approach is to refund deposits in full when cancellation notice is generous, retain part of them within a middle window, and retain them fully for short-notice cancellations and no-shows. Write the policy down and show it at booking.
Can booking software handle deposits and balances separately?
Yes, and it should. Each payment should be linked to a booking so the system can show what is paid, what is due and what was refunded. Keeping them separate also simplifies invoicing and reporting.
How do prepaid studio packages affect invoicing?
The timing of invoices for prepaid packages depends on your accounting treatment, so confirm it with your accountant. In software, the key requirement is a live package balance that deducts automatically on each booking and blocks further use when empty.
Do I need a custom system or can I use a generic booking tool?
Generic tools handle simple bookings well. If your deposit rules, package logic or Egyptian pound invoicing do not fit a standard template, a custom system avoids workarounds that break under volume. Our team can help you compare the two options against your actual rules.
