A client with four related entities is not four times the work of a client with one. It is closer to eight times the work, because intercompany transactions create reconciliation obligations that did not exist when everything sat in a single entity. Each entity has its own BAS, its own payroll, its own loan accounts, and its own year-end file — but the entities are economically interdependent, and a journal entry in one entity usually has a mirror entry in another.
Understanding how to structure and manage multi-entity clients — from file naming to month-end workflow to Division 7A monitoring — is the difference between a bookkeeping engagement that runs smoothly and one that consumes the accountant's year-end time in unravelling errors.
The Typical Structure and Why It Exists
Most multi-entity structures in Australian SME contexts follow a recognisable pattern. A discretionary (family) trust operates the business and distributes income to beneficiaries. A company (the corporate trustee or a separate trading entity) employs staff and holds contracts. A holding company sits above the trading company and accumulates retained earnings in a more asset-protected vehicle. An SMSF exists separately to accumulate retirement savings, sometimes holding property or shares in the operating group.
This structure exists for asset protection, tax planning flexibility, and succession planning. The bookkeeper does not need to fully understand the strategic rationale, but they do need to understand which entity owns what assets, employs which staff, holds which bank accounts, and is party to which contracts — because all of these facts determine how transactions are coded.
File Naming and Chart of Accounts Consistency
The first practical decision when onboarding a multi-entity client is how to structure the files and chart of accounts so that month-end work is systematic rather than improvised.
For file naming, a consistent prefix system by entity type works well: TRADE for the trading entity, HOLD for the holdco, TRUST for the discretionary trust, SMSF for the fund. If the client has multiple trading entities, TRADE1 and TRADE2. Each entity file follows the same template structure — same account numbering ranges, same section headings — so that intercompany balances can be traced across files without hunting through different coding conventions.
Chart of accounts consistency across entities means that account code 2-1100 means "Intercompany Loan — Receivable" in every entity file. This is not the same account everywhere — TRADE's receivable from HOLD is HOLD's payable to TRADE — but the position in the chart and the numbering convention is mirrored. When you need to run a multi-entity intercompany check, consistent numbering makes it mechanical.
Intercompany loan accounts should include the counterparty in the account name: "Loan Receivable — Holdco" in TradeCo's file; "Loan Payable — TradeCo" in Holdco's file. This eliminates ambiguity when a client has four or more entities each lending to and borrowing from each other.
Managing Intercompany Loan Accounts Month-to-Month
The intercompany loan account is the bookkeeper's single greatest source of multi-entity reconciliation risk. Left unreconciled, it accumulates timing differences, unrecorded transactions, and rounding errors that compound over time. By year-end, a loan account that should balance to zero across the group may have a material unexplained discrepancy.
Best practice is to include the intercompany loan reconciliation in the monthly close checklist, the same way a bank reconciliation is completed monthly. At month-end, extract the intercompany receivable balance from each lending entity and the intercompany payable balance from each borrowing entity, and confirm they agree. Any difference requires investigation before the period is closed.
When a payment is made between entities — HoldCo's bank account pays TradeCo's supplier directly — the entry in HoldCo is:
- Debit Loan to TradeCo $X
- Credit Bank $X
And in TradeCo:
- Debit Accounts Payable (or Expense) $X
- Credit Loan from HoldCo $X
If the TradeCo bookkeeper is not notified of the HoldCo payment, TradeCo's books will show an unpaid creditor while HoldCo shows an intercompany receivable — a mismatch that can persist for months if intercompany reconciliations are not routine.
Division 7A Monitoring Across the Group
When managing a group that includes private companies, Division 7A exposure must be tracked at the group level, not entity by entity. A loan from TradeCo (a private company) to the individual shareholder, and a separate loan from HoldCo (another private company) to the same shareholder, are both separately subject to Division 7A. The shareholder's minimum repayment obligations cover each loan independently.
The bookkeeper's job is to maintain a Division 7A register: a running schedule of all outstanding private company loans to shareholders or associates, the applicable benchmark interest rate for each year the loan is outstanding, the minimum annual repayment due, and whether that repayment has been made before the relevant lodgement date. This register should be reviewed and updated each financial year and provided to the accountant prior to the year-end review.
Minimum repayments that are not made before the company's tax lodgement date cause the shortfall to be deemed a dividend — assessable income for the shareholder, with no franking credits. This is one of the most expensive inadvertent tax events in multi-entity bookkeeping, and it is entirely preventable with a well-maintained register.
Which Entity Pays Shared Expenses, and How to Recharge
In many multi-entity groups, one entity holds the primary bank account and pays expenses on behalf of the group — rent for shared office space, insurance, software subscriptions, payroll for shared staff. The other entities then owe their share via intercompany recharges.
The recharge methodology should be documented and consistent. If HoldCo pays $10,000 per month in shared rent for a space used 40% by TradeCo and 60% by HoldCo, the monthly recharge to TradeCo is $4,000 plus GST ($4,400). The journal in HoldCo:
- Debit Intercompany Receivable — TradeCo $4,400
- Credit Rent Expense $4,000
- Credit GST Collected $400
And in TradeCo:
- Debit Rent Expense $4,000
- Debit GST Paid $400
- Credit Intercompany Payable — HoldCo $4,400
The recharge methodology — square footage, headcount, revenue split, or a fixed agreed allocation — should be written down and reviewed annually. Undocumented recharge allocations that appear arbitrary will not withstand ATO scrutiny and risk being recharacterised as non-arm's length transactions.
Practical Month-End Workflow for Four-Plus Entities
The most efficient multi-entity month-end workflow processes entities in dependency order. Entities that receive recharges from others should be closed after the entities that generate the recharges. The holding company, which often acts as the central payer, should be processed first so that intercompany entries can be pushed downstream.
A structured monthly checklist per entity — bank reconciliation, payroll reconciliation, intercompany balance check, BAS preparation (where applicable), outstanding creditors and debtors review — applied consistently across all entities, prevents the most common failure mode: completing four sets of books where each is individually plausible but the intercompany balances do not agree with each other.
Standardised workpaper templates for intercompany reconciliations, shared via a cloud document system with the accountant, allow the year-end review to proceed efficiently. The accountant who can see the intercompany reconciliation for every month of the year, with differences explained as they arose, has significantly less year-end untangling work than one confronted with twelve months of unexplained variances in a single sitting.