An intercompany expense is easy to create and hard to clean up later. An employee of one entity pays for something that benefits another — a shared workshop, travel to help a sister company, software the whole group uses — and the cost now sits in the wrong company’s books until someone notices, explains it, and moves it.
The cleanup is expensive precisely because it happens late. By reconciliation time the person who knew why the cost was shared has moved on to other work, the receipt is a month old, and the allocation rationale has to be reconstructed instead of recorded. What would have been a thirty-second field at submission becomes an email thread at close.
This guide covers how cross-entity expenses arise in an employee reimbursement workflow, why late allocation weakens the evidence, what to capture on the claim itself, how the settlement leg works, and which compensating controls matter when the same finance people run several entities.
An intercompany expense is any cost that involves more than one legal entity in the same group — one entity pays, another (or several) receives the benefit. In an employee expense workflow they arrive in a handful of recurring shapes:
The unifying property: the entity that reimburses the employee and the entity that should bear the cost are not the same, so the reimbursement creates an intercompany balance — a receivable in one company, a payable in the other — that exists whether or not anyone has written it down yet.
Cross-entity costs found at month end instead of at submission carry three compounding penalties.
The evidence has decayed. The strongest statement of why a cost was shared is the one made by the person who incurred it, at the time they incurred it. A rationale reconstructed weeks later by someone in finance is an inference, not a record — and it reads as one to an auditor.
The balances are related-party balances. Transactions between group companies are related-party transactions, and IAS 24 exists precisely because of them: its objective is to ensure financial statements draw attention to the possibility that an entity’s position and results have been affected by related parties and by transactions and outstanding balances with them, and it requires disclosure of the nature of the relationship and information about those transactions and balances. An intercompany balance nobody documented at source is a disclosure item assembled from guesswork.
The charge may need to survive a tax examination. When the entities sit in different jurisdictions, the intercompany charge that moves the cost is a controlled transaction. In the United States, section 482 authorizes the IRS to adjust the income, deductions, credits, or allowances of commonly controlled taxpayers to prevent tax evasion or to clearly reflect income, and the regulations generally require intercompany prices to yield results consistent with what uncontrolled parties would have realized in the same transaction under the same circumstances — the arm’s-length standard. Most tax authorities apply an equivalent principle. A recharge backed by a contemporaneous business purpose and allocation rationale is defensible; a lump “management fee” invented at close is the kind that gets examined.
None of this requires expense software to compute transfer prices — it requires the workflow to preserve, at source, the facts the accountants and advisers will need: who spent, for whose benefit, why, and on what basis it was split.
The single highest-leverage change is to move the allocation question from reconciliation to submission. Three facts have to be on the claim before it is approved:
Route on the benefiting entity, not just the employing one. A workflow that only ever routes to the submitter’s manager will approve cross-entity costs all day without anyone on the receiving side ever seeing them — every one a small surprise scheduled for month end.
The claim itself is the best container for the allocation evidence, because it is the record everyone can already find — attached to the receipt, the amounts, and the approval history. A separate month-end allocation spreadsheet divorces the rationale from the evidence and ages badly. What finance needs on the claim:
| Field | Why finance needs it |
|---|---|
| Employing entity | Determines who reimburses the employee and where the payable to the employee sits |
| Benefiting entity or entities | Shows where the cost belongs and which intercompany balance the claim creates |
| Allocation basis and percentages | Explains how a shared cost was split — headcount, usage, project share — so the split is a method, not a negotiation |
| Business purpose | The contemporaneous statement of why the cost served the benefiting entity — the sentence the recharge documentation will quote |
| Cost center or project | Lets the receiving entity book the cost where its own reporting needs it |
| Approver identity and role | Proves someone with authority over the benefiting budget accepted the cost, and when |
| Currency and rate applied | Cross-entity usually means cross-currency; the recharge must use a stated, dated rate |
| Supporting documents | Receipt, and for recurring arrangements the agreement the recharge sits under |
Two of these deserve emphasis. The allocation basis turns a percentage from an assertion into a method — “40/60 by project headcount” can be checked next quarter; “40/60” cannot. And the business purpose is the field with the longest useful life: it feeds the entity’s own audit file, the related-party disclosure, and the transfer-pricing documentation, all from one sentence written while the facts were fresh.
Clara keeps this evidence in the workflow: each entity’s claims, approvals, and documents stay inside that entity’s boundary, and a claim carries its attachments and approval history with it — so the allocation record is wherever the claim is, not in a parallel spreadsheet. For what the surrounding trail must capture field by field, see expense audit trails.
Reimbursing the employee closes the loop with the person; it does not close the loop between the entities. The full sequence has four stages, and skipping the middle two is where groups accumulate their unexplained balances:
Currency spans the whole sequence: the employee may spend in one currency, the employing entity reimburses in another, and the recharge lands in a third. Fixing the conversion moment early is what keeps the three amounts reconcilable — in Clara the rate applied is the one for the date of the transaction, fetched automatically from a market feed and locked onto the claim at submission, so the recharge documentation can point at a stated rate on a stated date. The rate-documentation mechanics are covered in foreign currency expenses.
Cross-entity expense flows concentrate risk in a specific way: the people most likely to handle them — group finance, shared-services accountants, multi-entity administrators — are exactly the people whose access spans entities. One person may administer the workflow in entity A, approve in entity B, and prepare payments in both.
The role design that contains this is entity-scoped: a person’s role is granted per entity, so the same individual can be an administrator in one entity and only a submitter in another, and visibility follows membership rather than seniority. Clara scopes roles and visibility per entity in exactly this way. But scoping alone does not resolve every conflict — small teams will still have individuals with broad access — so compensating controls carry the rest:
The general duty-splitting framework — which conflicts matter most and a matrix to test your own — is covered in segregation of duties in expenses, and the entity-boundary design that makes these controls enforceable is the subject of multi-entity expense management.
An intercompany expense is a cost that involves more than one legal entity within the same corporate group — one entity pays it, and another entity (or several) receives some or all of the benefit. In an employee reimbursement context the common cases are an employee of one entity doing work that benefits a sister entity, a shared purchase consumed by several entities, and spend by people in group-level roles whose work serves multiple companies.
The defining consequence is that the reimbursement and the economic cost end up in different companies’ books, which creates an intercompany balance — a receivable in the paying entity, a payable in the benefiting one — that must be documented, recharged, and settled. Because the entities are related parties, these transactions also carry disclosure obligations under accounting standards such as IAS 24, and when the entities sit in different tax jurisdictions, the recharge between them generally has to be defensible at arm’s length.
Two approvals matter, and they answer different questions. The submitter’s own manager (or the employing entity’s normal chain) confirms the spend was legitimate — the person was authorized to incur it. The budget owner in the benefiting entity confirms the allocation — that their entity agrees to bear the cost. A workflow that collects only the first will approve cross-entity costs without the receiving side ever seeing them, which is how allocation disputes get scheduled for month end.
In practice the second approval belongs to whoever is accountable for the receiving budget: the benefiting entity’s manager for a project cost, its finance owner for shared overhead, or a group-level owner where a single person holds authority over both sides. What matters for the audit trail is that the record shows someone with authority over the benefiting entity’s money accepted the charge, and when.
They are one of the classic close-stalling items. Consolidation requires intercompany balances to agree and eliminate — the receivable in one entity must match the payable in the other. Cross-entity expenses found late break this in three ways: balances that one side recorded and the other did not, recharges issued without supporting detail so the receiving entity cannot book them to the right cost center, and currency mismatches where the two sides converted at different rates or dates. Each becomes a reconciling item that has to be investigated while the close clock runs.
Capturing the benefiting entity, the allocation basis, and the rate on the claim at submission removes the investigation step: the balance is recognized on both sides from the same record at the same moment, and the recharge inherits its line-item support automatically.
The reimbursement to the employee itself does not — that is a domestic transaction between an entity and its own employee under its own expense policy. What can fall under transfer pricing rules is the recharge between entities that follows, when the entities are under common control and especially when they sit in different tax jurisdictions. In the United States, section 482 authorizes the IRS to adjust income and deductions of commonly controlled taxpayers to clearly reflect income, and the regulations generally require intercompany charges to be consistent with what unrelated parties would have agreed — the arm’s-length standard; most other tax authorities apply an equivalent principle.
For routine expense recharges the practical requirement is documentation rather than complex pricing: a contemporaneous business purpose, a stated allocation basis, the supporting claims, and a consistent method period to period. Whether a given recharge needs a markup, a formal agreement, or specific local documentation is a question for your tax adviser.
As a method, not a number. “Entity A 40%, entity B 60%” is an assertion; “split by project headcount at the time of the event: 4 participants from A, 6 from B” is a method someone can verify next quarter and reapply next time. Good allocation bases are observable and proportionate to the benefit: headcount for shared events, users or seats for shared tools, project time for cross-entity work, revenue share only where benefit genuinely tracks revenue.
Record the basis on the claim itself, next to the percentages and the business purpose, so the recharge documentation can cite it without reconstruction. Two disciplines keep the method honest: use the same basis for the same kind of cost across periods (a basis that changes every month looks like steering), and round from the method rather than to convenient numbers — a file full of exact 50/50 splits on costs with unequal beneficiaries is a pattern reviewers notice.
Written from the recurring close and audit problems that cross-entity employee expenses cause for controllers, anchored to what the cited IFRS Foundation and IRS pages verifiably state, each URL verified to resolve before citation. The workflow sequence, field table, and control list are practitioner guidance, not quoted from any authority.
Manage your team's expenses in any country and currency. Receipts, approvals, and bank-ready payment reports — all in one place.