Related Parties: Governance and Pricing Controls

Quick View

Why It Matters

Related-party definitions differ across company law, accounting standards, tax and securities regulation. The company should maintain a master list by legal entity and update it when directors, relatives, ownership or group structures change.

Before commitment, record the counterparty, relationship, business need, alternatives, price evidence, credit terms and conflicts. Approval after payment weakens the control.

Ordinary-course and arm’s-length analysis is fact-specific. Even where an approval exemption applies, accounting disclosure, tax documentation or board conflict rules can remain relevant.

Control Framework

Action Checklist

1. Create a related-party master.
2. Add conflict declarations to procurement.
3. Benchmark price and credit terms.
4. Obtain approvals before signing.
5. Reconcile balances and disclosures.
6. Report exceptions to the board.

Practical Example

Evidence to Keep

• Related-party register.
• Director and key-person declarations.
• Commercial comparison or valuation.
• Board or committee papers.
• Contract and invoices.
• Accounting and statutory disclosures.

Warning Signs

Management Decision

Treat related-party controls as a trust mechanism, not a prohibition. Transparent transactions can be legitimate when the company proves need, fairness and proper approval.

Review balances as well as new contracts. Long-outstanding advances, reimbursements and loans can create different legal and tax risks from the original transaction.

Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.

Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.

Monthly Review Test

Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?

The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.

Exception Review

The operating record should connect the control stages—identification, commercial case, approval, monitoring—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.

Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.

Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.

Conflicts and judgement should be visible before approval. A founder, director or business owner with a personal interest should disclose it and follow the appropriate review route rather than approve the transaction informally.

Diligence quality improves when records are maintained during ordinary operations. Reconstructed minutes, unsigned contracts and after-the-fact explanations may answer a question temporarily but weaken trust and can create separate legal risk.