Recording Customer Deposits and Payments the Right Way

A customer pays you a 30 percent deposit to lock in the job. Cash, in the driveway, in a hurry. You'll write it down later. Then three weeks pass, the job's done, the final invoice goes out — and the customer swears they already paid more than your records show. Now you're arguing over money with no paper trail, and even if you're right, you look disorganised. That's the whole case for recording deposits and payments properly: not bookkeeping for its own sake, but protecting yourself.

Money coming in is the half of your finances people are weirdly casual about. They'll chase a tiny expense receipt but won't log a 3,000 dollar deposit because "I'll remember that one." You won't. Here's how to record every payment in so it's clear, reconciled, and impossible to dispute.

What a properly recorded payment actually contains

A scribble that says "deposit – 3k" is almost useless. Three months later you won't know which job, what day, or whether it cleared. A payment record that actually protects you has five things, every time:

• Method — was it a bank transfer or cash? These reconcile completely differently, so you have to know which.
• Amount — the exact figure, not a rounded guess.
• Date — the day the money actually landed, which matters for cash flow and for the financial year it falls in.
• Bank transaction ID — the reference from the transfer, so the entry matches a real line on your bank statement.
• Proof of payment — an optional screenshot or photo for the awkward cases, especially cash.

Projects Plus is built around exactly these fields. When you log cash in, you pick bank or cash, enter the amount and date, drop in the bank transaction ID, and attach optional proof. It takes about as long as reading this paragraph, and it leaves you with a record that holds up.

Bank versus cash: why the method matters

Treating every payment the same is how things get muddled. The two methods need different handling.

Bank transfers

These are the easy ones to verify because the bank does half the work. The thing that makes them genuinely useful is the bank transaction ID. Record it against the payment and your in-app entry maps one-to-one to a line on your statement. That's what reconciling means — proving every payment you logged matches money that genuinely hit your account, with nothing invented and nothing missed.

Cash

Cash has no automatic trail, which makes it both the most common source of disputes and the easiest to lose track of for tax. The discipline is simple but non-negotiable: log it immediately, with the date and amount, and attach proof if there's any chance of it being questioned later. A photo of the cash with the job sheet, a signed acknowledgement — whatever gives you something to point to. Future-you will be grateful.

Projects Plus records every payment in with method, amount, date, bank transaction ID and optional proof — so money-in is always clear and reconcilable. Free on iPhone, iPad and Mac.

Why reconciling money-in protects you

Reconciling sounds like an accountant's word, but the idea is plain: making sure what you recorded matches what actually happened in your bank account. Skip it and three quiet problems creep in.

1. 1Payment disputes you can't win. Without a dated, referenced record, a he-said-she-said over a deposit comes down to who's more confident — not who's right.
2. 2Money you forgot to chase. A deposit recorded but no final payment logged is a flag that someone still owes you. No record, no flag, and the balance quietly slips away.
3. 3A tax-time mess. Come the financial year end you need a clean, honest list of income. Reconstructing it from memory and bank scrolling is both painful and risky — see the end-of-financial-year prep guide for how much smoother it is when money-in is already squared away.

Every payment you record is a small insurance policy. You hope you never need to point to it — but the day a customer says they already paid, you'll be very glad it's there with a date and a reference next to it.

Deposits, progress payments and the final balance

Bigger jobs rarely get paid in one hit. A deposit up front, maybe a progress payment at the halfway mark, then the balance on completion. The risk is losing track of how much of the total has actually landed.

The answer is to log each one as a separate payment line against the same job, each with its own method, amount, date and reference. Now the job carries its own running tally of money in, and when you build the final invoice the balance owing is obvious rather than something you reverse-engineer. This is also why money-in and money-out belong in the same place — once you're tracking cash in and out together, the deposits sit right alongside the expenses and the profit-per-job picture finishes itself.

Make it a habit, not a homework session

None of this works if recording a payment is a hassle. The whole method hinges on logging money the instant it arrives, which only happens if it's a few taps on the phone in your pocket rather than a spreadsheet waiting at home. That's the practical difference a native job management app makes — the record gets created in the moment, on site, while the detail is fresh and the customer is still standing there to confirm it.

Get that habit in place and recording deposits stops being something you mean to do and becomes something that's simply already done. Every dollar in, logged and reconcilable, with zero paperwork nights.

Record every deposit and payment the moment it lands — and never argue over money again. See Projects Plus [features](/features) or [pricing](/pricing).

Frequently asked questions