The Durban brief: tighter control on deposits and stock spend
The client was a small catering business based in Durban, serving private events, school functions and corporate lunches across the city and nearby suburbs. Work was coming in steadily, but cash flow was getting hard to read because deposit payments, supplier bills and wage runs were being handled across different spreadsheets and bank messages. When the owner wanted a clearer picture of what was actually left after each event, the numbers were often a week or two behind.
The brief was simple enough on paper. Keep the books current, track deposits against each booking, separate food cost from labour cost and make payroll easier for casual kitchen staff and delivery helpers. The business also needed a system that could handle seasonal spikes around year-end, public holidays and school terms without creating extra admin. In Durban humidity is hard on dry goods and planning, so the owner wanted controls that made stock ordering more disciplined and less guesswork.
- Business type: micro catering operation
- Town: Durban, KwaZulu-Natal
- Core pain points: deposit tracking, ingredient spend, casual payroll
- Decision maker: owner-manager handling sales and operations
What was holding the numbers back
The main issue was not a lack of work, it was a lack of structure. Deposits were sometimes received weeks before the event but not always matched to the correct booking straight away. Supplier invoices arrived after deliveries, while card receipts and petrol claims were still being sorted out. That made it hard to know whether each event was profitable until much later. The owner also had part-time staff who worked different hours from one week to the next, so payroll took too long and there were occasional questions about overtime and leave balances.
We found a few practical constraints that mattered on the ground. The business had limited office time because the kitchen and prep team were busy from early morning. Load-shedding also affected workflow, so any process needed to work even when power cuts disrupted the day. The owner did not want a heavy admin system or a pile of files on the laptop. What was needed was a clean monthly routine that could be followed by the team without confusion, and without adding more cost than a micro business can carry.
- Records had been split between bank statements, messages and manual notes
- Payroll was being prepared ad hoc for casual and hourly staff
- Event margins were difficult to measure per booking
- Stock buying decisions were based on rough estimates instead of actual usage
Our setup over four weeks
Affo worked with the owner over a four week period to reset the bookkeeping rhythm and put the payroll steps in order. We started by mapping the client's event cycle: quote, deposit, shopping, prep, function, final payment and staff pay run. That let us align the paperwork to the real business flow instead of forcing the business into a generic month-end routine. We then set up a simple process for recording deposits as soon as they landed, attaching each one to the correct event and logging the expected balance due.
On the expense side, we created categories that made sense for a caterer: fresh produce, dry goods, meat, transport, disposable serving items, venue-related costs and casual labour. This made it easier to compare budgeted food spend with actual spend for each function. Payroll was organised around fixed and variable hours so the owner could see what was owed before the weekend rush, not after the fact. We also added leave tracking, new employee setup steps and holiday payroll cover for busy periods. The result was a routine that could be kept up even when the team was short on time.
- Implementation time: 4 weeks
- Records standardised by event and by month
- Payroll grouped for weekly wage staff and casual helpers
- Reporting designed for quick owner review, not accounting jargon
Services used for the project
The project used a mix of bookkeeping and payroll support that matched the business size. Monthly bookkeeping gave the owner a current view of income, supplier payments and unpaid balances. Weekly wage payroll helped where kitchen and delivery staff were paid by the week rather than on a monthly salary. Payslip processing was handled for each pay cycle so the team could see deductions clearly and ask questions before payday. Timesheet capture was also tightened up, which reduced disputes about hours worked on event days.
We also assisted with payroll cleanup. That meant sorting out old entries, checking deduction support and making sure termination pay could be handled cleanly if a staff member moved on after a season. The client valued that the support was personal and direct, because in a small business there is no time to repeat the same instruction three times. The process had to be clear enough for the owner and practical enough for the people doing the actual prep and serving.
- Monthly Payroll
- Weekly Wage Payroll
- Payslip Processing
- Leave Tracking
- Timesheet Capture
- Payroll Cleanup
What changed after the numbers were brought together
By the end of the project, the owner had a much clearer view of cash in and cash out for each job. Deposits were no longer floating around unassigned and ingredient purchases could be checked against bookings before the next shopping run. That helped reduce overbuying, which matters when fresh stock has a short shelf life and storage space is tight. The business also became more confident about pricing because the owner could see where labour and food costs were creeping up.
Payroll became quicker and less stressful. Casual staff were paid on time, payslips were easier to issue, and leave balances were more visible. The owner spent less time checking old messages and more time planning menus and taking bookings. The most useful change was probably not dramatic on paper but very practical in the day to day running of the business: more control, fewer surprises, and a cleaner month-end close.
- Better deposit tracking for each event booking
- Clearer food cost visibility per function
- Faster payroll turnaround for casual staff
- Less time spent reconciling messages, notes and bank entries
What we would do again for a catering business
If we were starting the same project again, we would keep the setup lean and focused on the real workflow. For a micro caterer, the best system is the one that gets used every week, not the one with the longest feature list. We would again start with event deposits, supplier spend and staff pay, then build the rest around those three areas. That approach keeps the books readable and helps the owner make quick decisions before ingredients are bought or a function is confirmed.
We would also keep the reporting short and regular. A small business owner does not need a thick pack of figures every month. They need to know whether the next two events are covered, whether staff have been paid correctly and whether the business is keeping a margin after transport and spoilage. For a Durban catering operation, those are the numbers that matter most, especially when trading through peak season, load-shedding and a busy coastal calendar.
Key facts
| Client type | Micro catering business |
|---|---|
| Town | Durban, KwaZulu-Natal |
| Project length | 4 weeks |
| Core focus | Event deposits, ingredient spend, payroll control |
| Staffing pattern | Weekly wage and casual event staff |
| Outcome | Clearer cash flow and faster payroll handling |
