Category: Compliance, KYC & Accounting

The Quiet Disaster That Unfolds When Money Flows Freely Between Projects

It starts innocently enough. A project contractor receives a deposit for Project A and uses part of it to pay an overdue supplier invoice from Project B. After all, the money is there, the supplier needs to be paid, and Project A's expenses will not come due for another month. By the time Project A's costs arrive, there will be new revenue from Project C to cover them. It is just cash flow management — practical, flexible, and seemingly harmless.

Except it is not harmless. It is, in fact, one of the most dangerous financial practices a project-based business can adopt. Mixing project funds with operating funds — known as commingling — creates a compliance time bomb that may not detonate for months or even years, but when it does, the consequences can be devastating.

Why Mixing Funds Creates Reconciliation Chaos

The fundamental problem with commingled funds is that it becomes impossible to determine, at any given moment, how much money belongs to which project. When all income flows into a single account and all expenses flow out of it, the accounting relies entirely on the accuracy and completeness of your bookkeeping — and bookkeeping, in practice, is rarely as precise as it should be.

Consider a project contractor running three concurrent projects. Project A has a budget of $200,000, Project B $350,000, and Project C $150,000. All revenue and all expenses pass through a single operating account. At the end of the month, the contractor wants to know: how much has been spent on each project? How much revenue has been received? What is the remaining budget for each?

In theory, the answers are in the accounting system. Every transaction has been categorised by project. The reality, however, is messier. Some expenses benefit multiple projects — a bulk materials purchase, a shared subcontractor, overhead allocations. Some transactions are miscategorised — an expense coded to Project A that should have been coded to Project B. Some transactions are not categorised at all — they sit in the accounting system as uncategorised expenses that will be allocated "later," a later that never seems to arrive.

Over time, the reconciliation drift becomes significant. The accounting system says Project A has spent $120,000, but a detailed review reveals that $15,000 of those expenses were actually for Project B, and $8,000 were general overhead that should have been allocated across all three. Project A's actual spend is $97,000, not $120,000. But the project manager has been making decisions based on the $120,000 figure — declining to authorise additional work, pushing back on supplier quotes, telling the client that the budget is tighter than it actually is.

This is reconciliation chaos, and it is the inevitable consequence of commingled funds. The more projects you run, the more currencies you deal in, and the more complex your supplier base, the worse it gets.

The Auditor's Perspective on Fund Segregation

Auditors take a particularly dim view of commingled funds. From their perspective, fund segregation is not a best practice — it is a fundamental requirement of sound financial management. The reasons are both practical and principled.

Practically, commingled funds make it extremely difficult for auditors to verify the financial position of individual projects. If they cannot trace a specific receipt to a specific project and a specific expense to a specific project, they cannot confirm that the project accounts are accurate. This creates audit risk — the possibility that the financial statements contain material misstatements that the auditor cannot detect.

Principally, commingled funds raise questions about the integrity of the financial reporting. If project funds are not segregated, how can the auditor be confident that project revenue has been recognised correctly? That project costs have been allocated accurately? That the business is not using funds from one project to mask losses on another? These questions, once raised, are difficult to answer to an auditor's satisfaction.

For project contractors, the audit implications are particularly serious. Many client contracts include audit provisions that give the client the right to inspect project financial records. If the contractor cannot produce clean, segregated project accounts, the client may question whether the project has been managed properly — and may use this as grounds for withholding payment, imposing penalties, or declining to renew the relationship.

In regulated industries — construction, defence, government contracting — the consequences can be more severe still. Fund segregation may be a contractual or regulatory requirement, and commingling may constitute a breach that triggers fines, contract termination, or debarment from future work.

Per-Project Reporting Requirements

Beyond audit concerns, there are practical reasons why project-based businesses need per-project financial reporting. Effective project management requires accurate, timely financial data for each project: budget versus actual spend, remaining funds, projected costs to completion, and margin analysis. When funds are commingled, producing this data requires painstaking allocation work that is both time-consuming and error-prone.

Clients increasingly expect per-project reporting as a contractual requirement. A client who is paying $350,000 for a project wants to see exactly where their money is going — not a summary that blends their project with others. They want to see receipts, payments, and balances that relate specifically to their engagement. If you cannot provide this, you are at a competitive disadvantage.

Tax authorities may also require per-project reporting, particularly for businesses that operate across jurisdictions. If a project is performed in one country but managed from another, the tax obligations may differ from those of a project performed entirely domestically. Commingled funds make it difficult to allocate revenue and expenses to the correct jurisdiction, creating tax compliance risk.

Separate Accounts Versus Separate Balances

The traditional solution to fund segregation is to maintain separate bank accounts for each project. This is the approach used by large construction firms, government contractors, and any business where fund segregation is a regulatory requirement. Each project has its own account, its own statement, and its own audit trail.

For small project-based businesses, however, separate accounts are often impractical. Each additional account brings KYC requirements, monthly fees, reconciliation overhead, and management complexity. A contractor running five concurrent projects would need five separate accounts — each with its own compliance burden and cost.

An increasingly viable alternative is to use separate balances within a single account or platform. Many modern financial platforms allow you to create labelled or ring-fenced balances that are functionally equivalent to separate accounts but without the administrative overhead. Funds allocated to a specific project are held in a labelled balance, and payments from that balance are automatically tracked against the project budget.

This approach offers most of the benefits of separate accounts — fund segregation, per-project reporting, audit clarity — with significantly less overhead. It is not appropriate for every situation: if you are holding client funds in trust, separate legal accounts may be required. But for the vast majority of project-based businesses, labelled balances provide the segregation they need without the accounts they do not.

How to Allocate and Track Project Funds

Implementing effective fund allocation and tracking requires both systems and discipline. The systems provide the infrastructure; the discipline ensures it is used consistently.

Establish a project fund structure at the outset. Before any money flows, define how funds will be allocated for each project. What percentage of the project budget will be held in reserve? How will shared costs be allocated? What is the approval process for project expenditures? Documenting these decisions at the start prevents disputes and confusion later.

Allocate receipts immediately. When a client payment arrives, allocate it to the relevant project balance on the same day. Do not let unallocated funds accumulate — they are the seed from which commingling grows. If a receipt relates to multiple projects, split it according to the pre-agreed allocation.

Code expenses at the point of initiation. Every payment should be coded to a project at the moment it is initiated, not after the fact. If a payment benefits multiple projects, allocate it at initiation according to the pre-agreed formula. Do not leave expenses uncoded, even temporarily.

Reconcile project balances regularly. At minimum, reconcile project balances monthly. Compare the project balance in your financial system to the actual funds available, and investigate any discrepancies immediately. The longer you wait, the harder it is to identify and correct allocation errors.

Report per-project financials to stakeholders. Provide project managers and clients with regular financial reports that show budget, spend, remaining funds, and projected costs to completion. This creates accountability and ensures that problems are identified early.

The legal implications of commingling depend on the nature of the business and the jurisdiction, but they can be serious. In some jurisdictions, commingling client funds with operating funds is illegal — a violation of trust account regulations or professional conduct rules. Even where it is not explicitly illegal, it can create legal liability in several ways.

If a business becomes insolvent and project funds have been commingled with operating funds, it may be impossible to determine which funds belong to which project or client. This can result in claims from clients that their funds were misappropriated — claims that are difficult to defend when the funds cannot be clearly traced.

In contractual disputes, the inability to produce segregated project accounts can undermine your position. If a client alleges that you have overbilled or under-delivered, and you cannot demonstrate exactly how their funds were used, the dispute may be resolved in the client's favour by default.

For businesses operating through a managed business workspace or similar structure, the legal implications may be mitigated by the fact that the workspace provider maintains the segregated fund structure. The operator benefits from the segregation without having to implement it themselves — a significant advantage for small businesses that lack the resources to maintain separate accounts for each project.

The Multi-Currency Dimension of Commingling

For cross-border operators, the commingling problem is amplified by currency complexity. When project revenues arrive in euros, dollars, and sterling, and project expenses are paid in yuan, rupees, and dirhams, the single-account approach creates not just allocation confusion but also FX confusion. It becomes nearly impossible to determine which currency exposure belongs to which project, and FX gains or losses from one project's currency conversions may inadvertently offset or obscure losses on another.

Consider a scenario where Project A generates a £20,000 FX gain on a euro conversion, while Project B incurs a £15,000 FX loss on a yuan payment. In a commingled account, these amounts net to a £5,000 gain — which masks the fact that Project B is underperforming on currency management. The project manager for Project B never sees the problem, and no corrective action is taken. By the time the project completes, the cumulative FX losses may have erased the project's operating margin entirely.

This multi-currency commingling is particularly dangerous because it can create the illusion of overall profitability while individual projects are losing money. The contractor may believe they are performing well across the portfolio, when in reality one or two projects are subsidising losses on others. Without per-project, per-currency tracking, this illusion can persist until it is too late to correct.

Building a Fund Management System That Keeps Projects Clean

The ultimate goal is a fund management system that keeps project finances clean, auditable, and defensible without requiring excessive administrative effort. This means choosing financial infrastructure that supports fund segregation — whether through separate accounts, labelled balances, or an integrated operating perimeter — and implementing processes that ensure consistent use of that infrastructure.

The system should produce, at any moment, a clear answer to three questions for each project: how much has been received, how much has been spent, and how much remains. It should produce this answer without manual calculation, without allocation guesswork, and without reconciliation adjustment. When it can do that, you have a fund management system that works — and you have defused the compliance time bomb that commingled funds inevitably create.

The cost of getting this wrong is not merely administrative. It is financial, legal, and reputational. The cost of getting it right is modest by comparison — and the peace of mind that comes from knowing that every project's finances are clean and defensible is, for most operators, well worth the investment.