There's a leak in almost every studio I've looked at, and it's not the one people worry about. It's not the vendor who overcharged or the site guy who wasted material. It's quieter than that. It's the advance you collected six months ago, put into the bank, mentally filed as "paid," and never adjusted against a single invoice.
That money isn't stolen. It's just floating. And floating money, over enough projects, quietly turns into lakhs you either double-count, refund by mistake, or eat as a shortfall you can never explain.
Let me walk you through how this actually happens, because it's rarely one big blunder. It's a hundred small ones.
The advance that never comes home
Here's the normal flow. Client signs off on the design. You raise a 40% advance, say ₹4,00,000 on a ₹10,00,000 project. Client pays. Work starts.
Now three, four, five months go by. Site is running. You're raising running bills as milestones clear. Somewhere in month three, your accountant or your junior raises an invoice for the modular kitchen milestone, ₹2,80,000. The client asks, quite reasonably, "Wasn't part of this covered by the advance I already paid?"
And now you're scrambling. Was it? How much of that ₹4,00,000 has already been adjusted? Against which bills? What's the running balance of unadjusted advance sitting on this project?
Nine times out of ten nobody has a clean answer. It's in someone's head, or in a WhatsApp message, or in a Tally entry that only your CA understands. So you either:
- Give the client the benefit of the doubt and knock off an amount you're not sure about (you just gave away margin)
- Insist the advance was already adjusted when it wasn't (client feels cheated, trust cracks)
- Kick the can down the road to "final settlement" where nobody remembers the numbers and the last 10% never gets collected
Every one of those outcomes costs you real money. The advance was supposed to be your money, held against work you'd do. Instead it became a source of confusion that the client, sensibly, resolves in their own favour.
Why the leak is invisible
The reason nobody notices this leak is that the advance looks like a win. Money came in. Bank balance went up. Everyone feels good.
But an advance is a liability, not income. It's cash you owe as work-not-yet-done. Until you raise an invoice and formally adjust the advance against it, that ₹4,00,000 is still, in accounting terms, sitting on the wrong side of your books. And under GST it gets thornier, because the timing of when you collected the advance and when you raise the tax invoice affects how and when the tax gets reported. If you're not tracking the adjustment cleanly, you can end up paying tax on money, then paying again on the invoice, and never reconciling the two. I've written separately about how to handle client advances and GST the right way, and it's worth your time, because the compliance side of this is where a small tracking gap becomes an actual cash penalty.
The core problem is structural. In most studios, three things live in three different places:
- The advance lives in your bank statement and maybe a Tally ledger
- The project scope and milestones live in an Excel sheet or someone's head
- The invoices live in Tally, or a billing tool, or as PDFs your accountant makes at month end
Nothing connects them. So there's no single number that says: "For Sharma residence, you collected ₹4,00,000 advance, adjusted ₹1,20,000 so far across two invoices, and ₹2,80,000 is still un-adjusted." That number should be one glance away. Instead it's a forensic exercise every single time.
Where the actual money goes
Let me be concrete about the loss, because "poor tracking" sounds soft. It isn't.
Double collection you have to refund. You collect an advance, then months later raise a full invoice without adjusting the advance, and the client pays that too. Now you're holding money you'll have to return, or worse, you don't realise and the client does, and they trust you a little less forever.
Advances you forget to adjust and eat as a shortfall. The opposite case. You adjust the advance too generously or too early, then at final settlement you're short and can't chase it because you have no clean paper trail.
The last mile that never gets collected. This is the big one. On a lot of projects the final 10 to 15% is where your profit actually sits, because the earlier payments covered material and labour. When the advance-to-invoice trail is muddy, that final payment becomes a negotiation instead of a formality, and negotiations you enter without clean numbers, you lose. This ties directly into the broader pattern I laid out in 7 places your design studio quietly leaks margin, the advance mess is arguably the sneakiest of the lot because it disguises itself as cash in hand.
GST paid twice. Covered above, but worth repeating: an advance-tax mismatch is real rupees to the government you don't get back easily.
None of these show up as a line item called "loss." They show up as a studio that's always somehow tighter on cash than the project P&L says it should be. You feel it as stress, not as a number. That's exactly why it goes unfixed for years.
How to actually track advances right
The fix isn't complicated in principle. It's just that doing it manually across ten live projects is more discipline than any busy studio owner has. Here's what "right" looks like:
One ledger per project, not per bank account
Every advance must be attached to a specific project the moment it lands. Not "₹4,00,000 received from Mr. Sharma" floating in a bank feed, but "₹4,00,000 advance, Sharma 3BHK Whitefield, received 12 Jan." The unit of tracking is the project, because that's where the advance eventually gets consumed.
A running un-adjusted balance you can see anytime
For each project you want one live figure: advance collected, minus advance already adjusted against invoices, equals advance still available. When you raise the next invoice, the system should ask you how much of the outstanding advance to apply, adjust it, and update that running balance automatically. No mental math. No archaeology.
Advance adjustment baked into the invoice itself
This is the piece manual setups always miss. The adjustment shouldn't be a separate note. When you generate a GST invoice, the advance applied to this invoice should appear as a line, reduce the payable amount, and reduce the project's remaining advance in the same action. One event, three books updated. If you're already collecting through Razorpay, this matters even more, because the payment and the invoice need to reconcile cleanly, I walked through that whole flow in how to send GST invoices and collect payment via Razorpay.
A trail the client can see too
Half the disputes vanish when the client can log in and see, in plain terms, "You paid ₹4,00,000 advance. ₹1,20,000 has been adjusted against these two invoices. ₹2,80,000 remains as credit toward future bills." When the number is transparent and always current, nobody argues, because there's nothing to argue about. This is a big part of why I keep saying protecting margin is mostly about clarity, not toughness, more on that in how to protect your margin on every design project.
Why a connected system is the only real fix
You can try to do all of the above with an Excel sheet and iron discipline. Some studios manage it for a while. But the moment you're running six, eight, ten projects, the manual ledger drifts, and the day it drifts is the day you lose money without knowing it.
The reason the leak exists is that your money moves through disconnected tools. The advance hits the bank. The scope lives in a sheet. The invoice comes out of Tally. Nothing knows about the others. When those three are one connected flow, enquiry to spec to quote to invoice to collection, with advances riding along the whole way and adjusting themselves against each bill, the leak simply can't open, because there's nowhere for the money to fall through. That's the whole argument for why one connected system beats five disconnected tools, and advance tracking is the cleanest example of it.
This is exactly what we built Designa to do for Indian studios. Advances attach to the project, adjust against GST invoices automatically, keep a live remaining-balance you and your client can both see, and sync to Tally and Zoho Books so your CA isn't reconstructing history at year end. Razorpay collection is built in, so the money and the invoice always match.
If advances quietly leaking out of your studio sounds a little too familiar, go see the whole flow live at demo.designa.work, then grab the founding plan, the entire studio, up to 10 members, for ₹2,299 + GST a year, at go.designa.work. Plug this one leak and it pays for itself on your next project.