The deposit ledger nobody keeps: late and partial deposits for event businesses

Search "catering deposit tracking" and you mostly get software pages telling you to take deposits online. Search "untracked deposits" or "client deposits not tracked" and there is barely anything at all — which is strange, because for a caterer, a wedding vendor, or anyone who books work weeks ahead and does it in stages, the deposit is where the money and the job first meet. Part of the money arrives before the job. Part arrives after. Sometimes a second part arrives in between, late, or short. And in a lot of small event businesses, none of that is written down in one place anyone else can read. The deposit exists in the client's hands and in nobody's ledger. So when someone asks the only question that matters about a job's money — what a job has actually paid so far — nobody can answer it from a record. They answer it by asking around: who took the call, who saw the transfer, who remembers what was agreed. This page is about the ledger nobody keeps, what one line in it has to hold, and why late, partial, and missing deposits are not the same problem wearing three coats.

The question you cannot answer on the day

The question sounds simple: for this job, what has been paid, and what is still to come? On the day itself — the week of the event, when the food order and the staffing both depend on the job being real and paid for as agreed — that question is the one the business runs on. If the answer lives in one person's memory, the answer walks out of the room when that person does. If the answer lives in a thread of messages, a notebook, and a bank feed that nobody has matched to the job, then answering it is a small investigation, run again for every job, usually at the worst moment.

Notice what the problem is not. It is not that clients never pay. Most deposits do arrive. The problem is that arrival is not the same as a record. Money that arrived and was never written against the job is, for every practical purpose on the day, money nobody can prove the job has. And money that was agreed and never arrived looks exactly the same as money that arrived and was not recorded — both show up as a blank where the job's payments should be. That is why untracked deposits are worse than late ones: a late deposit at least has a date you are waiting for. An untracked one has nothing to wait for and nothing to check.

What a deposit ledger actually is

A deposit ledger is not accounting software and it is not a new system. It is one line per payment, written when the money arrives, holding the same fields every time:

• Job: the job the money belongs to, named the way the business names it — client and date, so the line cannot drift onto the wrong event.
• Date the money arrived: the day it actually landed, not the day it was promised.
• Amount that arrived: what came in on that date, as it came in — a partial payment is recorded as the amount that arrived, not rounded up in your head to what was agreed.
• What it was for: the deposit, a further payment, the balance — the stage this payment was meant to be.
• Balance still to come: what the job still owes after this line, worked out on the line itself, while the numbers are in front of you.
• Who recorded it: the person who wrote the line, so a question about it has somewhere to go.

Six fields. The discipline is not the fields — it is the timing and the place. One line, in one place, written when the money arrives, by whoever saw it arrive. A ledger written up at the end of the month from memory is the old problem with neater handwriting. And a ledger that only the owner can read or update has the same single point of failure as the memory it replaced: the record has to be somewhere the person running the job on the day can actually look.

Late, partial, and missing are three different problems

Owners talk about deposit trouble as one thing — "the deposits are a mess" — but the ledger separates it into three different problems, and each one has a different next step:

• A late deposit was agreed, has a date it was due, and has not arrived by that date. The record is fine; the money is late. The next step is a chase, and the ledger is what makes the chase a fact instead of a feeling: agreed on this date, due on that date, nothing recorded since.
• A partial deposit arrived, but for less than the amount agreed for that stage. The money is partly there and the shortfall is the problem. Recorded honestly — amount that arrived, balance still to come updated — a partial payment is manageable. Recorded as if the full stage had been paid, it becomes a missing amount that only surfaces when the final invoice is argued over.
• A missing deposit is the untracked case: nobody can say from a record whether it arrived at all. There is no line, or the line was never matched to this job. The next step is not a chase and not a shortfall conversation — it is reconstruction, and reconstruction is the expensive version of a line that would have taken a minute to write when the money arrived.

Late is a timing problem. Partial is an amount problem. Missing is a record problem. Treating a record problem as if it were a timing problem — waiting, politely, for money that may already be sitting in the account unmatched — is how a job gets to the week of the event with its money still a rumour.

What the published sample shows, and what it does not break out

The worked example behind these Notes is Taste & Thyme Catering, a synthetic example whose sample plan is published on this site. Its weekly catering operations workflow — booking in, event staffed, food ordered, invoice out — takes 18.62 hours a week and costs $722.31 a week, which is $37,560 a year, priced block by block from the hours and rates stated in the sample:

• The owner's own work — 5 hours a week at $60 an hour. That is $300 a week, and $15,600 a year.
• Event coordination — 12 hours a week at $30 an hour. That is $360 a week, and $18,720 a year.
• Kitchen deep-clean coordination — 2 times a month, 2.5 hours each time, at $30 an hour. Spread across the weeks of a year, that is $34.62 a week, and $1,800 a year.
• Kitchen equipment servicing — 1 time a quarter, 6 hours each time, at $60 an hour. Spread the same way, that is $27.69 a week, and $1,440 a year.

One of the four problems the sample records, in the business's own words, is invoices retyped by hand, and deposits nobody tracks. The deposit half is this page's subject: in the sample's workflow, the invoice figures already exist in the workflow's own records and are typed again anyway, and the deposit has no line in any record at all — the exact blank this page's ledger is the fix for.

One honesty note, because a page about records should keep its own straight: the sample does not break out a separate cost for the deposit problem, or for invoicing. Its published figures price the blocks of the workflow, and the retyping and the deposit tracking sit inside those blocks alongside the booking, coordination, and ordering work. Splitting out a deposit share would mean guessing at a split the sample never made, so this page does not do it. What the sample gives you is the shape — a workflow heavy enough, at $37,560 a year, that a blank in its records is not a small thing — and the words the business itself uses for the problem.

A labelled example: what has this job paid so far?

Here is the balance question worked through once, with numbers that are there only to show the shape. The inputs are examples — replace them with your own job's real ones. Say a job's agreed total is $2,000. A first payment of $500 arrives and is written on the ledger line for that job, with its date. Later, a second payment of $300 arrives — less than was expected at that stage, so it is recorded as $300, the amount that arrived, and the balance still to come is updated on the line. The ledger now answers the question without anyone being asked: the job has paid $800 so far, and $1,200 is still to come.

Read the same week without the ledger. The first payment is in a message thread. The second, being short, was mentioned on a call and written nowhere. The person building the final invoice works from memory, and the shortfall is discovered either by the client — who knows what they paid — or not at all. Nothing about the example's numbers is a claim about your business: $2,000 is not a typical job, $500 is not a typical deposit, and this is not a recommended split of a job's price into stages. It is one job's arithmetic, labelled as an example, showing the only thing the ledger has to do — hold each amount that arrived, when it arrived, so the balance is a subtraction anyone can check instead of a memory only one person holds.

Keeping the ledger from today

You do not need to rebuild last year's jobs to start. Start with the next payment that arrives, and keep four habits:

• Write the line when the money arrives. Not at the end of the week, not when the invoice goes out. The line is cheapest at the moment the facts are in front of you.
• Record what arrived, not what was agreed. A partial payment written as the full stage is a missing amount you have created yourself.
• Update the balance on the same line of work. The balance still to come is worked out when the payment is recorded, so the next person never has to redo the subtraction from fragments.
• Build the final invoice from the ledger. The invoice is where the untracked deposit does its damage — a final bill that ignores a payment, or double-counts one, turns a records problem into an argument with a client about money. If the final invoice is built from the ledger lines for that job, it agrees with what the client paid because it was written from the same record.

That is the whole fix at the level of habit. Whether it lives in a notebook page per job, a sheet, or the tool named in the next section matters less than that it is one place, written at arrival, readable by whoever runs the job on the day.

What the named fix costs

The sample plan names a fix for the retyped invoices and untracked deposits, and the plan catalog this studio publishes lists its price: QuickBooks Online, at $456 a year, together with Stripe for taking payment. The catalog lists Stripe as pay-as-you-go and gives it no annual price, so this page gives it none either.

Put that price next to the right thing. The comparison is not the tool against a deposit — a deposit is the client's money passing through your records, not a cost of yours. The comparison is the tool's published price against the time your workflow spends retyping invoices and reconstructing what jobs have paid, inside blocks that, in the sample, add up to $37,560 a year for the whole workflow. If your own version of that reconstruction happens once a year, a notebook page per job may be the whole fix and it costs nothing but the habit. If it happens every week, on every job, the published price of the tool that holds the ledger for you is the number to weigh. That judgement — your blocks, a named fix's published price — is the only comparison this page will make. It does not claim the tool will make clients pay earlier, and it does not turn anyone else's late-payment figures into a promise about yours.

The worked examples behind this page

Four pieces in these Notes show the rest of this problem and its method with every number visible. The worksheet, "The free workflow-audit worksheet", at https://www.agenticartists.com/blog/free-workflow-audit-worksheet is the blank form of the capture this ledger belongs to — steps, owners, exceptions, time, and cost for one workflow, with this same catering example filled in. The invoicing breakdown, "The cost of manual invoicing", at https://www.agenticartists.com/blog/cost-of-manual-invoicing works through the other half of this sample problem — the retyping, the fixing, and the chasing — from your own hours and rate. The teardown, "What a catering workflow costs", at https://www.agenticartists.com/blog/what-a-catering-workflow-costs pulls the sample workflow apart block by block and problem by problem. And the method guide, "How to audit one workflow", at https://www.agenticartists.com/blog/how-to-audit-one-workflow walks through running the same audit by hand, on a workflow of your own, step by step. Read the invoicing post for the full chain the deposit sits in, the worksheet for the form, and the teardown for the numbers.

Doing this with Where AI Fits

Where AI Fits runs the capture behind this page for one of your workflows: a guided conversation reconstructs the workflow, you confirm the steps, the owners, the exceptions, the hours, and the rates, and the paid AI Integration Plan, at $49, writes up the time and cost block by block, names the problems in your business's own words — untracked deposits among them, if they are there — and puts a named fix and its catalog price next to each one. The sample plan used throughout this page is published on this site, so you can check every figure here against the finished document before deciding.

Sources

Every number on this page traces to the studio's own published sample or catalog, checked on 2026-10-30, or to a worked example whose inputs are labelled as examples. Taste & Thyme Catering is a synthetic example, labelled as such on the sample plan itself; its figures are the sample's own, not measurements of a real business. No external statistic or price is used on this page.

• Taste & Thyme Catering sample plan — $722.31 a week, $37,560 a year, 18.62 hours a week, and the problem recorded in the business's own words as invoices retyped by hand and deposits nobody tracks — https://www.agenticartists.com/products/where-ai-fits/sample-plan — checked 2026-10-30
• The Wave 4 teardown of the same sample — the four problems in the business's own words and the named fixes with their catalog prices — https://www.agenticartists.com/blog/what-a-catering-workflow-costs — checked 2026-10-30
• The Wave 6 invoicing post — the deposit half of the same problem, and the final invoice built on memory when deposits are not tracked — https://www.agenticartists.com/blog/cost-of-manual-invoicing — checked 2026-10-30
• The Wave 12 worksheet — the capture form (steps, owners, exceptions, time, cost) this ledger belongs to — https://www.agenticartists.com/blog/free-workflow-audit-worksheet — checked 2026-10-30
• The Wave 3 method guide — the capture method worked step by step — https://www.agenticartists.com/blog/how-to-audit-one-workflow — checked 2026-10-30
• Where AI Fits plan catalog prices, checked against the catalog in this tree on 2026-10-30 — QuickBooks Online $456 a year; Stripe listed as pay-as-you-go with no annual price
• Where AI Fits — $49 for the AI Integration Plan for one workflow, published on this site at /products/where-ai-fits — checked 2026-10-30

Back to Notes