Common Purse, Clear Mandate: Governing a Consortium's Shared Account

A consortium bank account often begins as a practical answer to a practical problem. Several organisations win work together, a lead partner opens an account, and funds begin to arrive. The arrangement feels provisional, so the paperwork is kept light. That is precisely when governance matters most. Shared money concentrates risk, authority and expectation in one place. If the board has not agreed how that money will be controlled, the account will soon govern the partnership rather than the other way round.

The account is not the agreement

A bank mandate tells a institution who may instruct payments. It does not tell partners whose money is being spent, on what, or under whose authority. Those questions belong in a consortium finance protocol approved by each board before any transfer is made. The protocol should sit alongside the collaboration agreement, not behind it. It should be short enough to be used and specific enough to settle disputes.

The protocol need not replicate the full funding agreement. It should translate the funding agreement into operating rules: the purpose of the pot, the contribution schedule, the approved budget, the decision rights, the reporting rhythm and the exit route. If the consortium cannot state those matters in plain language, it is not ready to hold a shared balance.

Define the purpose and the perimeter

A common purse needs a clear perimeter. The board should approve what the fund may pay for, what it may not pay for, and how variations are authorised. Restricted grant funding, partner contributions and any earned income should be identified separately. The consortium should be able to answer three questions without returning to the funder: whose money is it, what is it for, and what happens if it is not spent?

The perimeter should also address indirect costs and shared services. A lead partner may provide finance, HR or programme management. Those services should be charged on an agreed basis, not absorbed informally and then reconstructed at the end. Boards should be cautious about treating the pot as a general float for the partnership. A shared account is not a substitute for each partner's own working capital.

Signatories, thresholds and decision rights

The bank mandate is the starting point, not the whole control environment. The board should approve signatory rules that require at least two authorised people for material payments, with thresholds set according to risk rather than habit. Below-threshold payments may be delegated to a consortium finance lead or programme director, but the delegation should be documented and reviewed.

Decision rights require equal attention. Who may approve a budget variation? Who may commit the consortium to a new supplier? Who may authorise an emergency payment when a partner is unavailable? The protocol should distinguish between operational decisions, management decisions and matters reserved to the consortium board or partner boards. It should also address conflicts of interest, particularly where a signatory's own organisation is a beneficiary of the spend.

A simple decision log can be more useful than a long constitution. Every material commitment should record the decision, the authority relied on, the amount and the budget line. That log becomes the audit trail for later questions, including the ones asked when a partner exits.

Cashflow is a shared forecast, not a host partner's problem

A pooled fund is exposed to timing risk. Funders pay in arrears, suppliers expect payment, and partners incur costs at different rates. The lead partner may hold the account, but the cashflow forecast belongs to the consortium. A forecast prepared only at bid stage will usually be out of date before the first quarter ends.

The finance protocol should require a rolling forecast showing receipts, payments, commitments and the projected balance. It should identify any working capital gap and state who will bridge it, for how long and on what terms. Partners should report their forward commitments, not just their invoices. The consortium board should see the forecast at every meeting, with a clear commentary on variance. If the pot is likely to go below an agreed minimum balance, the board should have a pre-agreed response rather than an emergency conversation.

VAT, tax and the contracting question

VAT and tax treatment cannot be assumed from the lead partner's existing arrangements. The consortium should establish who contracts with the funder or customer, who supplies goods or services to whom, and how transactions between partners will be treated. The answers may affect invoices, recoverability and the amount available for programme delivery. In some cases a VAT group or a formal cost-sharing arrangement may be relevant; in others it will not. The board should take professional advice before the first transaction, not after the first query.

The same discipline applies to employment taxes and supplier status. A shared account can obscure who is really employing a worker or purchasing a service. The protocol should require the consortium to document the contracting entity for each significant commitment. Clarity at the point of purchase is cheaper than correction later.

Liability, risk and the limits of the pot

The board should know whether the consortium's liabilities are limited to the shared funds or reach into partners' own reserves. Funding agreements and collaboration agreements may create joint and several liability, indemnities or repayment obligations. A partner may assume that the pot is the boundary of its exposure when the contract says otherwise.

The protocol should summarise the liability position in plain terms and identify any cap, guarantee or contingency. It should also state what happens if a partner cannot meet a contribution or an overpayment must be recovered. A contingency reserve is not a sign of weak planning; it is a recognition that consortium delivery rarely follows a straight line. The board should approve the reserve policy and the circumstances in which it may be released.

Audit trail and the discipline of reconciliation

Every payment from a shared account should be traceable to an approved budget line, a decision record and an eligible cost. That is the minimum standard. The consortium should maintain a shared ledger or finance report that partners can access, with a monthly reconciliation between the bank balance, the ledger and outstanding commitments. A shared account without a shared ledger is an invitation to dispute.

The board should receive a fund report at each meeting: balance, commitments, forecast, variances, aged items and any unresolved queries. The report should be prepared by the finance lead and reviewed by a partner with no direct interest in the payments concerned. Retention periods for records should be agreed at the outset, along with arrangements for access after the partnership ends.

The exit checklist

A consortium should agree its reconciliation method before it needs it. When the partnership ends or a partner exits, the board should work through a documented checklist:

• Freeze discretionary spend and confirm who retains authority during the wind-down.
• Reconcile the bank balance to the ledger and identify all outstanding commitments.
• Settle liabilities, retain an agreed contingency and confirm when it can be released.
• Allocate any surplus or deficit using the formula in the finance protocol, not according to who holds the account.
• Deal separately with restricted funds, assets and any repayable balances.
• Obtain a final audit or independent review proportionate to the funds involved.
• Record the lessons for future consortium arrangements and formally release signatories.

Fairness at exit depends on agreement at entry. If the protocol does not say how the pot will be divided, the board should expect the division to be contested.

Conclusion

Shared money is a governance test. It reveals whether partners have agreed purpose, authority and risk before events make those choices for them. Boards should approve a consortium finance protocol before the first transfer and review it when the partnership changes shape. The first invoice is too late to discover that the common purse has no common mandate.