Inter-Company Transactions Across Your Group
If you run multiple entities — a holding company, operating companies, a related trading arm — inter-company transactions are a constant source of month-end reconciliation work. Done manually, they produce mismatched balances, audit queries, and finance staff spending days chasing entries that should have balanced automatically.
What Inter-Company Transactions Actually Cover
"Inter-company" spans several different transaction types, each with different system requirements:
| Transaction Type | Example | System Requirement |
|---|---|---|
| Stock transfer | Company A ships goods to Company B for resale | Sale in A, purchase in B, elimination at group level |
| Shared services billing | Management fees, IT costs recharged from holding to operating co | Invoice in billing entity, expense in receiving entity |
| Loans and financing | Holding company advances funds to subsidiary | Loan account in both entities, interest accrual |
| Asset transfer | Equipment moved from one entity to another | Disposal in source, addition in destination |
| Group consolidation eliminations | Removing inter-company profit from group P&L | Consolidation journal at group level |
Each of these needs to be recorded in both entities — and the entries need to match for group reporting to be clean.
Why Manual Matching Fails
The typical workaround for group companies without inter-company automation is a shared spreadsheet or a manual journal process at month-end. The problems with this:
Finance staff in each entity record transactions independently. By month-end, one entity shows a receivable and the other shows a payable — but for different amounts, different dates, or different descriptions. Reconciling them requires going back through both ledgers to find where they diverged.
Volume compounds the problem. At five inter-company transactions per month, manual reconciliation is manageable. At fifty — particularly if stock transfers between related trading entities are frequent — it becomes a half-week job.
The Automation Approach
A proper inter-company module in a custom ERP handles the matching automatically. When Company A raises an invoice to Company B, the system creates the corresponding purchase record in Company B's ledger — same amount, same date, matching reference. Both sides of the transaction are created from a single entry point.
For AutoCount integration, where each related company may run its own AutoCount instance, the integration layer connects the instances. A sales invoice in Company A's AutoCount triggers a purchase invoice in Company B's AutoCount, with the reference number linking them for reconciliation.
Stock Transfer Between Related Companies
Stock transfer between related entities is the most common inter-company transaction for trading and distribution groups. The clean process:
- Transfer request raised in the source company
- Transfer priced at agreed internal transfer price
- Delivery order created in source company, goods receipt created in destination
- Invoice and corresponding purchase created in both ledgers
- At consolidation, the inter-company revenue and cost eliminate against each other
The transfer pricing needs to be agreed and consistent — using different internal prices in different periods creates consolidation adjustments that are hard to explain to auditors.
Consolidation and Elimination
Group financial reporting requires eliminating inter-company balances: the receivable in one entity matches the payable in another, and both are removed from the consolidated balance sheet. Inter-company revenue and the corresponding cost of goods also eliminate against each other in the consolidated P&L.
If the underlying inter-company transactions are clean and matched, these eliminations are mechanical. If they're not matched — amounts differ, some transactions were recorded in one entity but not the other — consolidation becomes a manual patching exercise.
FAQ
Can AutoCount handle inter-company transactions across two separate company files?
AutoCount's standard setup is single-entity. Connecting two AutoCount databases requires either manual journal entries that mirror transactions, or a custom integration layer that synchronises inter-company transactions between the two company files. The integration approach is more reliable at volume.
What's the right transfer price for inter-company stock transfers?
Transfer pricing is both an accounting question and a tax question. Common approaches are cost-plus, market price, or a negotiated internal price. The method needs to be documented and consistent — Singaporen tax authorities can question transfer pricing arrangements between related parties, particularly if they affect taxable income in either entity.
Do we need a full ERP to manage inter-company transactions, or can this be added to what we have?
It depends on the volume and complexity. For a group with two or three entities and fewer than twenty inter-company transactions per month, an integration between existing systems may be sufficient. For a group with frequent stock transfers, shared services billing, and consolidation reporting requirements, a unified group ERP or a dedicated inter-company module is the more practical long-term approach.
Book a System Audit