When a business operates through a single entity, accounts payable is relatively straightforward. Invoices arrive, they get coded to one chart of accounts, routed to one set of approvers and posted to one Xero or MYOB file.
When you add a second entity, the workload does not double — it more than doubles. And by the time you are running three, four or five entities, the finance team is spending a disproportionate amount of time on the operational overhead of managing AP across separate accounting files.
This is one of the most common scaling problems in Australian SMBs. Group structures, franchise operations, holding companies, businesses that have separated trading and property entities — they all hit the same wall. The invoices keep coming. The entities keep multiplying. And the finance team does not grow at the same rate.
Why multi-entity AP is harder than it looks
Each entity in Xero or MYOB is a separate file. Separate chart of accounts. Separate supplier list. Separate bank account. Separate approval settings.
This creates a set of problems that single-entity businesses never encounter:
Invoice routing errors. When a supplier sends an invoice, someone has to determine which entity it belongs to. If the supplier works across multiple entities — a freight provider, a maintenance contractor, an insurance broker — the same supplier might invoice different entities on different jobs. Route the invoice to the wrong entity and you have a coding error that surfaces during reconciliation.
Inconsistent coding. Entity A codes office supplies to 6100. Entity B codes them to 6150. Entity C uses a different tracking category structure entirely. When one person processes invoices across all three entities, the cognitive load of switching between charts of accounts leads to coding errors. When different people handle different entities, coding drift happens silently.
Approval confusion. The delegation of authority is different for each entity. The construction entity might require two approvals above $5,000. The property entity might have a single approver for everything under $20,000. If your approval process is informal — email-based or verbal — keeping these rules straight across entities is almost impossible.
Duplicate payments across entities. A supplier invoices Entity A for a job. Someone processes it. The supplier re-sends the invoice — this time addressed to Entity B. It gets processed again. Two payments go out for the same work. This is not a hypothetical scenario. It happens regularly in multi-entity businesses where there is no cross-entity duplicate detection.
Month-end compounding. Every reconciliation issue that exists in a single-entity business is multiplied by the number of entities. Inter-company transactions need to balance. Invoices posted to the wrong entity need to be reversed and re-posted. The month-end close that takes two days for one entity takes six days for three — not because the work is three times harder, but because the coordination overhead grows non-linearly.
How most multi-entity businesses handle AP today
The typical approach falls into one of three patterns:
Pattern 1: One person, multiple logins
A single finance team member — often the bookkeeper or accounts payable officer — logs in and out of each Xero or MYOB file throughout the day. They download invoices from a shared inbox, decide which entity each invoice belongs to, log into the right file, enter the invoice, send an approval email and move to the next one.
This works at two entities. It breaks at three. By four or five entities, the person is spending more time switching contexts and managing the process than actually processing invoices.
Pattern 2: One person per entity
Each entity gets a dedicated accounts payable person. This eliminates the context-switching problem but creates a staffing cost problem. It also makes it harder to maintain consistent controls — each person develops their own habits, and coding and approval standards drift over time.
Pattern 3: Outsource to the accountant
The external accounting practice handles AP for all entities. This moves the problem but does not solve it. The accountant faces the same multi-entity complexity, often with less context about which entity an invoice belongs to. Turnaround times increase because the accountant is batching work rather than processing in real time.
None of these patterns scale. And none of them provide the controls that a multi-entity business actually needs — consistent approval rules, cross-entity duplicate detection and a unified audit trail.
What a structured multi-entity AP process looks like
The solution is a centralised AP layer that sits above all your accounting files and handles the upstream processing — capture, coding, matching, approval, validation — in one place, while respecting each entity’s individual chart of accounts, suppliers and approval rules.
Here is what that looks like in practice:
Single inbox, automatic entity routing
All invoices arrive in one place — a shared email address or upload portal. The system determines which entity the invoice belongs to based on the supplier, the purchase order, the project code or the entity name on the invoice. The finance team does not need to sort invoices into entity-specific folders manually.
For suppliers that work across multiple entities, the routing can be based on the purchase order number, the delivery address or a default entity assignment that the team sets once and the system applies going forward.
Entity-aware coding
The system applies account codes from the correct entity’s chart of accounts. If Entity A uses code 5100 for materials and Entity B uses 5200, the system knows which code to apply based on which entity the invoice is routed to. The finance team sees the right chart of accounts for each invoice without switching between files.
Over time, the coding engine learns the patterns for each entity. Supplier X invoicing Entity A for concrete gets coded to 5100 with tracking category “Project Alpha.” The same supplier invoicing Entity B for a different job gets coded to 5200 with tracking category “Maintenance.” The system handles both without the finance team needing to remember the difference.
Entity-specific approval rules
Each entity has its own delegation of authority. The system enforces the right approval chain for each entity — different thresholds, different approvers, different escalation paths. An invoice for $8,000 against the construction entity might need two approvals. The same amount against the holding company might need only one.
Approvers see only the invoices relevant to their entity and their approval authority. They do not need to sort through invoices from other entities to find the ones that need their attention.
Cross-entity duplicate detection
The system checks incoming invoices against all entities — not just the one the invoice is routed to. If Supplier X has already been paid $4,500 by Entity A this month and an invoice for the same amount arrives addressed to Entity B, the system flags it. This catches both genuine duplicates and accidental re-processing across entities.
Unified audit trail
Every action on every invoice across every entity is recorded in one place. When the auditor asks to see the approval history for a specific invoice, the finance team does not need to search through three separate Xero files and a folder of emails. The audit trail shows who received the invoice, how it was coded, who approved it, what was changed and when it was posted — regardless of which entity it belongs to.
Consolidated reporting
The finance team can see AP metrics across the entire group — total invoices outstanding, average cycle time, exception rates — broken down by entity. This makes it possible to identify which entity is causing month-end delays, which entity has the highest exception rate and where the process needs attention.
The staffing equation
The most immediate benefit of structured multi-entity AP is that it breaks the linear relationship between entity count and headcount.
In a manual process, each new entity adds roughly 0.3 to 0.5 of a full-time equivalent to the AP workload — not a full person, but enough that by four or five entities, you need an additional hire. And that hire spends most of their time on process overhead, not value-adding work.
With a centralised AP layer, the incremental cost of adding a new entity is close to zero for the finance team. The system handles the routing, coding and approval enforcement. The team handles the exceptions and the decisions that require human judgement. The ratio shifts from one person per two entities to one person per five or six entities.
For a business running four entities with an average of 150 invoices per entity per month, that is the difference between a three-person AP team and a one-person AP team with better controls.
Common objections
“Our entities have completely different businesses — the chart of accounts is too different.”
That is fine. A proper multi-entity AP system does not try to standardise your chart of accounts across entities. It works with each entity’s existing chart of accounts as-is. The system is entity-aware, not entity-agnostic. Different codes, different tracking categories, different tax treatments — all handled per entity.
“Our approvers need to see invoices from all entities.”
Some approvers — typically the CFO or financial controller — do need visibility across all entities. The system should support role-based visibility: entity-level approvers see only their entity, group-level approvers see everything. This is a configuration decision, not a structural limitation.
“We’re planning to consolidate to fewer entities.”
Consolidation plans are common. Consolidation execution is slow. In the meantime, your finance team is processing invoices across the current entity structure every day. Solving the multi-entity AP problem now does not prevent you from consolidating later — and when you do consolidate, having clean AP data across all entities makes the transition significantly easier.
What to look for in a multi-entity AP solution
If you are evaluating AP automation for a multi-entity business, these are the capabilities that matter:
- Simultaneous connection to multiple Xero or MYOB files — not sequential, not requiring separate logins
- Entity-aware coding — the system applies the right chart of accounts for each entity automatically
- Entity-specific approval workflows — different rules for different entities, enforced by the system
- Cross-entity duplicate detection — checking invoices against all entities, not just the target entity
- Unified audit trail — one place to see every action across every entity
- Group-level reporting — AP metrics across the entire group, with entity-level drill-down
- Supplier management across entities — the same supplier can have different default coding for different entities
The goal is not to merge your entities into one AP process. It is to give your finance team one place to manage AP for all entities, with controls that respect each entity’s individual requirements.
The bottom line
Multi-entity AP is an operational problem that grows faster than most businesses expect. Two entities feel manageable. Three entities feel busy. Four or more entities without a structured AP layer means your finance team is spending their time on logistics — sorting, routing, switching, reconciling — instead of on the work that actually matters.
The fix is not more people. It is a process that scales with entity count without scaling headcount. That means centralised capture, entity-aware automation and controls that work across the group while respecting each entity’s individual structure.
Further reading: Best AP Automation Software Australia 2026 · What a Modern AP System Needs to Do · The Real Cost of Manual AP