Related parties need written rules
Most family businesses transact with people and entities close to the owners. That is normal and usually sensible. What causes trouble is the absence of a rule: no one decided who approves the rent on the founder's building, how a relative's salary is set, or how shared costs with a sister company are split. When a lender, a minority shareholder or a buyer asks, the company has to reconstruct the reasoning after the fact.
A related-party register in four columns
- Who. Each person or entity, and the relationship to the owners.
- What. Leases, loans, employment, shared services, purchases and guarantees.
- How it is priced. Market rent, a written loan agreement, a documented cost split.
- Who approves. Someone without an interest in the transaction, with the approval recorded.
Our article on related-party transactions sets out a policy you can adapt. A Board & Governance Review puts the register, the approval rule and the delegation of authority in place, and checks them against what the ledger shows.
Succession is a controls event
When a founder steps back or a long-serving finance lead retires, the controls that lived in one person's habits stop running. The month-end review they did in their head, the vendor they knew to question, the payment they would never have released: none of it is written down. We trace each money flow while that person is still there to explain it, test it against the ledger and write procedures the next team can follow. Then we train the people taking over, using the company's own transactions as examples, so the procedures are understood and not only filed.
The Controls Health Self-Check is a reasonable first look at where you stand. For an example of what full-ledger testing can surface inside a long-trusted team, read the illustrative scenario The Sunday-night entries.
