How to Split One Payment Across Several Projects and Months

In an agency there's a situation that constantly breaks simple bookkeeping: a client pays for several things at once in a single transfer. Say they send you 200k, and inside it is payment for the current project, an advance on the next one, and a monthly retainer. Or they pay three months of work up front. If you log this as one incoming payment against one project, all your analytics go sideways: one project balloons, the others look "cashless."

Being able to correctly split one payment across several projects and months is a basic managerial-accounting skill in services. Let's break down why it matters and how to do it right.

Why one payment is often several revenues

It's convenient for the client to pay in a single transfer, but you need the truth for each project. Those two needs are in conflict. If you leave the payment undivided, one project gets all the money in your books even though it really belongs to three. Profitability gets distorted: the "rich" project looks wildly profitable, while the rest look underfunded.

So the rule is simple: in your books, money follows its purpose, not the bank transfer. One bank payment can and should be broken into several records across different projects.

How to split a payment between projects

The mechanics are simple. When a 200k payment comes in, you break it into parts by purpose: 120k — project A (closing it out), 50k — project B (advance), 30k — the monthly retainer. It still adds up to the same 200k, but now each project has received exactly what's its own. That keeps every project's profitability honest. It's the same logic as the client-level view in the article Client profitability: the 20% that deliver 80%.

How to split a payment between months

A special case is payment up front for several periods. A client pays 90k for three months of retainer. If you book it all in the current month, that month looks "golden" and the next two look empty — even though the work carries on. The right way is to spread it as 30k across each of the three months, because revenue is recognized when the work is done. That way months don't jump around, and each one's profitability reflects reality.

A special case: advances and prepayments

An advance / prepayment for a future project isn't revenue yet — it's an obligation to do the work. So when you split the payment, it's worth flagging the advance portion separately: the money is in the account, but it becomes "earned" only once you've delivered. This saves you from the classic illusion where prepayments inflate the month's profit, and then, once the work is done and no new advances arrive, a slump sets in.

Example: one payment — three projects

A client transfers 240k. Without splitting it, this would look like a wildly profitable project A. We divide it by purpose: 140 — project A (final payment, its costs are already incurred, so the margin shows immediately), 60 — project B (advance, flagged as an obligation), 40 — the August retainer. Now A shows its real margin, B doesn't inflate the current month, and the retainer lands where it belongs. One transfer — three honest records.

Where to start

Make it a rule: before you log a big "bundled" payment, ask yourself — what exactly is this money for? And spread it by purpose and period. At first it feels like extra work, but it's precisely undivided payments that most often make your per-project analytics lie. The general principles of tracking several projects are in the article Tracking several projects at once.

In Finmap, one payment can be split into several parts across projects and periods in a few clicks — and each project sees exactly its own money. Try it free for 7 days.