Reason Audit delays #7: Related Parties and Directors’ Transactions—The Disclosures That Stall Sign-Off (and How to Get Them Right)

Audits rarely collapse because a company lacks revenue or because the balance sheet is “too complicated.” In Jamaica and across the wider Caribbean, audits most often run late because something far more basic fails at the worst possible time: governance disclosure readiness.

Few areas illustrate this better than related parties and directors’ transactions.

Even when financial numbers are largely correct, audits can be delayed—sometimes by weeks—when management cannot clearly answer:

• Who are the related parties?

• What transactions occurred with them?

• Are balances complete and accurately measured?

• Were approvals obtained and properly documented?

• Are disclosures complete and consistent with board minutes and governance records?

This is a high-sensitivity area. Regulators, lenders, shareholders, donors, and boards focus heavily on related party transparency because it speaks to integrity: conflicts of interest, preferential terms, “off-market” transactions, and the risk of undisclosed benefits. Auditors therefore treat related parties as both a disclosure area and a fraud risk area, which means weak documentation triggers additional procedures and senior review.

This article addresses the seventh major cause of late audits: related party identification and documentation is incomplete, late, or inconsistent—and provides a practical framework for getting related party governance and disclosures audit-ready well before fieldwork.

Why related parties create audit bottlenecks

Related party work slows audits for four structural reasons:

1) It is not purely an accounting task

Related parties are a governance topic. The information sits in board knowledge, executive relationships, ownership structures, and management behavior—not just the accounting system.

2) Completeness is the primary risk

Auditors are less concerned with the arithmetic of a related party balance than with whether all related parties and transactions have been captured. Completeness requires inquiry, confirmation, and cross-checking.

3) It touches high-risk judgments

Related party transactions often involve:

• non-standard terms (interest-free loans, long credit periods)

• management fees and allocations

• property leases and related occupancy arrangements

• directors’ expenses and reimbursements

• “connected” procurement relationships

• one-off settlements and restructuring transactions

These create scope for misstatement and require careful documentation.

4) It is a late-stage sign-off dependency

Even if testing is substantially complete, the audit cannot be finalized if the disclosures are not complete. That is why related party issues often show up at the end and stall sign-off.

What counts as a related party (in practical terms)

Accounting standards define related parties broadly. You do not need to become technical to operationalize this. You need a clear, practical understanding of the common categories.

A related party typically includes:

• Parent entities and subsidiaries (and fellow subsidiaries under common control)

• Entities under common ownership or control (including beneficial ownership structures)

• Associates and joint ventures

• Key management personnel (directors and senior executives who have authority over planning, directing, and controlling activities)

• Close family members of key management (where their relationships may influence transactions)

• Entities controlled or significantly influenced by directors or key management

• Trusts, partnerships, or holding structures linked to directors or owners

The operational implication is straightforward: related parties extend beyond entities “in the group.” They include entities connected through ownership, control, influence, or close relationships.

The most common related party failures that delay audits

Failure 1: Management identifies related parties late (or incompletely)

Often, the first time related parties are discussed is when the auditor requests the list. Management then “remembers” additional parties during fieldwork. Each new party introduces new transactions, balances, evidence requests, and disclosure updates.

Audit impact: expanded testing and rework at a late stage; increased partner review attention.

Fix: implement an annual related party declaration process and maintain a live register (details below).

Failure 2: Transactions exist but are not tagged as related party in the accounting records

Many related party transactions are recorded as ordinary suppliers/customers or as generic “loan” or “expense” postings without a related party identifier.

Audit impact: auditors must rely on detective work—reviewing vendor lists, customer lists, journal entries, and board minutes—to detect related party activity.

Fix: tag related parties in the accounting system (even if only via naming conventions or codes) and maintain a related party transaction ledger.

Failure 3: Related party balances do not reconcile or lack evidence

Common examples:

• directors’ loan accounts with unclear movements

• management fees without agreements or allocation basis

• intercompany balances without reconciliation and settlement logic

• reimbursements without supporting documents and approvals

Audit impact: additional confirmation procedures, expanded sample testing, and potential classification issues.

Fix: treat related party balances as “priority reconciliations” with clear movement schedules and evidence.

Failure 4: Approvals and governance documentation are weak

Boards may approve transactions in principle, but evidence is not retrievable: minutes are missing, conflicts are not documented, or approvals are not clearly linked to the transaction.

Audit impact: auditors question governance integrity, seek more evidence, and escalate issues.

Fix: maintain an approvals repository: board minutes extracts, resolutions, and conflict declarations linked to each material transaction.

Failure 5: Disclosures are drafted at the end and don’t match reality

Disclosures might conflict with:

• board minutes

• related party registers

• loan agreements

• payroll/expense claims

• intercompany confirmations

Audit impact: prolonged disclosure review and multiple revisions, delaying final issuance.

Fix: draft disclosures early and maintain them as a living document.

What auditors typically do when related party risk is high

Understanding auditor behavior helps you build the right evidence pack.

When related party risk is high or documentation is weak, auditors commonly:

• conduct expanded inquiries of directors and senior management

• inspect board minutes for undisclosed relationships and approvals

• scan supplier/customer master files for common addresses, names, or ownership links

• test journals for unusual postings (especially near year-end)

• perform “round-dollar” and unusual transaction analytics

• request confirmations for related party balances (where appropriate)

• increase senior review scrutiny before signing the opinion

This is not “auditor overreach.” It is a standard risk response. The best way to avoid it is to provide completeness and clarity early.

The Related Party Audit-Ready Pack: what to prepare

To prevent delays, you want to produce a set of documents that make related party completeness and disclosure straightforward. The best practice is a structured “Related Party Audit-Ready Pack” that contains:

A. Related Party Register (the master document)

Include:

• name of related party (individual/entity)

• relationship type (director, shareholder, common control, close family, etc.)

• ownership/control basis (as applicable)

• effective date (when they became related)

• whether they are a customer, supplier, lender, landlord, employee, etc.

• key identifiers (TRN where appropriate, address, registration number)

• status (active/inactive)

This register should be maintained throughout the year, not created at year-end.

B. Annual Declarations and Conflict Statements

• director declarations of interests

• key management declarations

• updates for changes during the year

• conflict-of-interest disclosures and recusal notes (where relevant)

C. Related Party Transactions Summary (by party and by type)

For each related party:

• transaction types: sales, purchases, services, management fees, rent, loans, reimbursements, guarantees

• total value for the year

• terms (interest rate, repayment terms, credit terms)

• evidence references (contract, invoice range, approval)

D. Related Party Balances and Movement Schedules

• opening balance

• additions/transactions

• repayments/settlements

• reclassifications

• closing balance

• reconciliation to the trial balance line items

• evidence for material movements

E. Agreements and Supporting Documents

• loan agreements (including informal arrangements documented in writing)

• management service agreements and allocation methodology

• lease agreements with directors or related entities

• guarantees or commitments documentation

• material invoices and supporting approvals

F. Board Minutes and Approvals Index

• minutes extracts where transactions were discussed/approved

• resolutions and approvals (especially for non-standard terms)

• evidence of disclosures made and conflicts managed

G. Draft Disclosure Note (early)

Draft the related party note early and update it as you refine data. This dramatically shortens the final review cycle.

How to build a related party governance system that works

Most organizations do not fail because they “hide” related parties. They fail because the process is informal, memory-based, and not documented. The solution is to operationalize a simple governance system.

Step 1: Establish a related party definition guide for your organization

Create a one-page “definition and examples” document tailored to your structure:

• list common relationships relevant to your business

• include examples of transactions that must be captured

• specify who must declare interests and when

This improves consistency and reduces “I didn’t realize that counted” situations.

Step 2: Implement annual declarations (with updates as needed)

At minimum:

• annual director declarations of interest

• annual key management declarations

• update declarations when a new director/exec joins or when relationships change

Make it a formal year-end close deliverable.

Step 3: Create a living related party register and assign ownership

Assign ownership to a role (e.g., company secretary, compliance officer, finance manager) and ensure updates occur when:

• board changes occur

• new entities are formed or acquired

• significant vendors/customers are onboarded where relationships exist

• new financing arrangements occur

Step 4: Tag related parties in the accounting system

Even without sophisticated ERP functionality, you can implement:

• naming conventions (e.g., “RP – Entity Name”)

• a related party code in vendor/customer master

• separate GL accounts for director loans and related party balances

• memo fields and document links in the accounting system

This reduces forensic work later and strengthens completeness.

Step 5: Build a monthly (or quarterly) related party transaction review

Do not wait for year-end. Review:

• related party purchases and sales

• director loan movements

• expense reimbursements and benefits

• management fees and allocations

• unusual journals affecting related party accounts

A small amount of periodic review prevents a large year-end scramble.

The hardest related party categories (and how to get them audit-ready)

1) Directors’ loans and advances

These accounts are frequently messy due to:

• mixed personal/business transactions

• informal repayment terms

• offsets against expenses and reimbursements

• unclear classification between current/non-current

Audit-ready approach:

• prepare a movement schedule for each director

• document repayment terms and interest (even if zero)

• support cash movements with bank evidence

• support offsets with invoices/expense claims and approvals

• consider classification (current vs non-current) based on terms and expected settlement

2) Management fees and allocations

Group structures often charge management fees. Auditors will ask:

• what is the agreement?

• what is the basis of allocation?

• is it reasonable and consistently applied?

• has it been approved appropriately?

Audit-ready approach:

• written agreement or documented policy

• allocation basis (headcount, revenue, time, direct costs)

• calculation workpaper and evidence

• approval evidence

• consistent application and year-over-year explanation for changes

3) Related party leases (property, vehicles, equipment)

These are common in the region and high sensitivity because of pricing and conflict concerns.

Audit-ready approach:

• lease agreement and payment evidence

• demonstration of terms (market-based or rationale if not)

• approvals and disclosure of the relationship

• proper accounting treatment (including IFRS considerations where applicable)

4) Procurement relationships and “connected suppliers”

This area can create reputational risk if not managed well.

Audit-ready approach:

• conflict declarations

• procurement approvals and tender evidence (where applicable)

• rationale for supplier selection

• documented pricing or benchmarking where feasible

• clear disclosure where required

5) Guarantees, commitments, and support arrangements

Directors or related entities may provide guarantees, letters of support, or informal financial backing.

Audit-ready approach:

• documentation of the arrangement

• assessment of disclosure requirements

• board awareness and approvals

• consistent treatment in notes and going concern discussions (as applicable)

The disclosure workflow that prevents late-stage rework

A common cause of delay is drafting disclosures at the end. Instead, treat disclosure as a controlled workflow:

1. Draft the related party note early using the register and preliminary transaction summaries

2. Tie all amounts to the TB (balances and totals)

3. Cross-check with board minutes for completeness

4. Cross-check vendor/customer master files for undisclosed relationships

5. Lock the disclosure note subject to final tie-out and minor updates

6. Have management sign-off on completeness before audit finalization

This approach reduces “surprise” additions and compresses the final review cycle.

Common pitfalls (and how to avoid them)

Pitfall 1: Treating related party disclosure as “just a note”

Related party disclosure is a governance narrative supported by numbers. Treat it as a core deliverable, not a formatting exercise.

Pitfall 2: Using a list that is not updated for board changes

Changes in directors, owners, or key management require updates. If you rely on last year’s list, you will miss parties.

Pitfall 3: Not reconciling director balances to bank activity

Auditors will trace movements. If the story is unclear, they will expand procedures.

Pitfall 4: Assuming “market terms” without support

If a related party transaction is described as arm’s length, be prepared to support that statement (or avoid making the claim).

Pitfall 5: Not aligning disclosures with minutes and approvals

If minutes show approvals or discussions, auditors will expect disclosures to reflect the relationship and transaction reality.

A practical 14-day related party readiness plan

If you are behind, you can still stabilize this area quickly.

Week 1: Identification and governance

• compile director and key management list for the year (including changes)

• obtain declarations of interest and update the related party register

• extract board minutes for the year and identify related party references

• tag related parties in vendor/customer lists where possible

Week 2: Transactions, balances, and disclosures

• produce related party transaction summaries by party and type

• produce balance movement schedules for each related party balance

• reconcile all balances to the TB

• compile agreements and approvals evidence

• draft the related party disclosure note and align with minutes

By the end of day 14, most organizations can provide an audit-ready related party pack and reduce late-stage delays materially.

Related party KPIs that strengthen control

• percentage of directors and key management with completed annual declarations (target 100%)

• time to update register after a governance change (target within 7 days)

• number of late-discovered related parties during audit (target zero)

• number of related party balances lacking agreements/terms documentation (target zero for material balances)

• number of approval exceptions (tracked and resolved)

These KPIs are not bureaucracy. They are governance controls that protect audit timelines and reputation.

Closing perspective: related party readiness is reputation readiness

In the Caribbean, business networks are often close-knit. That reality is not a problem—unless it is undocumented, undisclosed, or poorly governed. Related party transparency strengthens trust: with boards, lenders, regulators, shareholders, donors, and the market.

Audits run late when related party information is assembled late and inconsistently. Audits run on time when management can present a complete register, reconciled balances, clear terms, approvals, and well-prepared disclosures.

The fix is operational: implement declarations, maintain a register, tag transactions, reconcile balances, and draft disclosures early. When those are in place, related party work becomes predictable—and sign-off accelerates.

Next Step: request a proposal

If your organization wants to reduce audit delays by strengthening related party identification, directors’ transaction governance, and disclosure readiness, Dawgen Global can support you across Jamaica and the wider Caribbean with Related Party Audit Readiness, Close Acceleration (“Close Sprint”), and end-to-end Audit + Compliance services.

Request a proposal by emailing [email protected] with the subject line: “Related Party Audit Readiness Proposal Request”. Please include your year-end date, number of entities (if a group), whether directors’ loans are material, and whether you have management fees, related leases, or connected suppliers. We will respond with a structured scope, deliverables, and an execution timetable tailored to your organization.

About Dawgen Global