Skip to main content

Silos to Synergy: Achieving End-to-End Intercompany Excellence

Key takeaways from our recent webinar on breaking down intercompany silos across Controllership, Tax and Treasury

Intercompany accounting has a habit of starting as a “finance issue” and quickly becoming everyone’s issue. As organisations scale through M&A, expand into new jurisdictions, and face rising expectations for faster close and greater transparency, the friction created by disconnected processes, data and ownership becomes harder to ignore.

In our webinar Silos to Synergy: Achieving End-to-End Intercompany Excellence, Simon Atherton was joined by Ross Pflaeger and Jenny Holehouse to explore what “good” looks like for intercompany, how to build a pragmatic transformation roadmap, and where AI can accelerate progress when the fundamentals are in place.

What we heard from the room (polling insights)

Before diving into frameworks and solutions, we began by asking attendees our first polling question to pinpoint where intercompany pain is showing up most strongly today. The results were telling: 

This reinforces what many teams experience: when transactions aren’t booked consistently on both sides—or lack the detail to be understood locally—disputes multiply and period-end becomes a firefight.We also asked how teams work together across the end-to-end process. While collaboration is happening, the “synergy” many organisations want isn’t quite there yet:

This matters because intercompany performance is rarely constrained by one team’s effort alone. For example, controllership teams may be forced into manual “translation” work (tagging transactions, building offline reports) simply to give Tax and local finance what they need—work that can often be avoided by designing for shared outcomes and data requirements from the start.

Finally, we took a pulse on AI readiness in intercompany:

The message here is not “AI is far away”—it’s that many organisations still have significant value to unlock by standardising processes and data first. AI can be a genuine accelerator, but it works best when the underlying intercompany “plumbing” is strong.

A practical 3-step approach to intercompany transformation

Across the discussion, we returned to a simple structure for moving from “pain” to performance:

1. Identify the problem by understanding the current-state process, operating model and end-to-end data flow.
2. Define the transformation by designing toward leading practice across governance, data, technology and ways of working.
3. Calculate the benefit across Finance, Tax and Treasury to build a business case that reflects the true end-to-end value.

Intercompany breakdowns show up in controllership first—missing mirror entries, unclear coding, late adjustments—but the consequences land across the enterprise. Tax teams rely on intercompany data to evidence transfer pricing policies and support local filings; treasury teams feel the impact through delayed settlements, extra FX transactions and avoidable cash friction.

A strong starting point is to make intercompany visible: map transaction types end-to-end (often through a service catalogue), and build a clear view of volumes, value and pain points—sometimes via an intercompany “heat map”. This helps teams challenge legacy transaction types, rationalise complexity, and focus transformation effort where it will matter most.
From a transfer pricing perspective, the risks are increasingly operational: misalignment between policy and execution, gaps in invoice-level information for VAT/GST, and rising demands from authorities for timely, explainable data. As noted in the session, HMRC’s transfer pricing yield for the 2024/2025 tax year was cited as £3.4bn (almost 90% higher than the prior year), with a significant portion attributed to implementation issues rather than flawed policy design.

Achieving end-to-end excellence requires more than improving reconciliation tooling. In the webinar, we shared a framework of seven pillars that work together to reduce friction, improve control, and create transparency from initiation through to reporting.

  • Governance and policies: clear global standards, materiality thresholds, and preventative/detective controls.
  • Intercompany pricing & tax: defined methodologies and indirect tax requirements, aligned to how calculations are actually executed.
  • Data management: owned master data, common definitions and consistent coding across systems.
  • Transaction management: automated invoicing and workflow approvals, with controls to support dual-sided booking.
  • Netting and settlement: more automated and dynamic settlement models to support cash efficiency and reduce FX volatility.
  • Reconciliation and elimination: transaction-level matching and elimination to move away from spreadsheet-led dispute management.
  • Internal and external reporting: KPI-driven dashboards with drill-down to individual transactions for explainability.

A key takeaway: intercompany doesn’t start on Day 0 of close. It starts upstream—with agreements, pricing logic, contracting, and the mechanisms that enable consistent dual-sided booking. When those upstream steps are strong, reconciliation becomes confirmation rather than investigation.

In practical terms, a leading intercompany solution is designed to be strategically touchless where possible, transfer pricing and indirect tax compliant, system-agnostic (critical in multi-ERP landscapes), and transparent end-to-end—centralising intercompany data so teams can trace the “what, why and how” behind each number.

Building the roadmap: start where you are, but design for where you’re going

Intercompany transformations rarely happen in a vacuum. ERP programmes, M&A integration, and evolving tax and regulatory demands all influence timelines and scope. The organisations that make sustained progress are often those that invest time up front to define a shared future-state vision—agreeing how policies, contracting, calculations, invoicing, reporting and governance should work end-to-end—then sequence initiatives to unlock value along the way (not only at the end of a multi-year programme).

Where AI can help (and what to fix first)

AI is increasingly being applied to intercompany, but the highest-impact use cases tend to cluster around two areas: (1) improving the quality and accessibility of knowledge (policies, agreements, playbooks), and (2) accelerating documentation and control activities that rely on extracting and interpreting large volumes of information.

  • Intercompany policy assistant: using an organisation’s LLM to help draft, refine and validate intercompany policy content against actual transaction types—spotting gaps and inconsistencies early.
  • Transfer pricing documentation acceleration: assembling evidence, populating templates and supporting local file preparation at scale. 
  • VAT/GST compliance checks: scanning invoice data to validate required local fields and flag high-risk items before submission.
  • Audit preparation: drafting response packs and evidence summaries to improve speed and consistency when queries arise.

As with any finance and tax process, governance matters: teams need clarity on where the data comes from, how models behave, who has access, and whether there is an audit trail. Where AI output affects tax positions or statutory reporting, it should be AI-powered with human oversight—not AI-only.

Intercompany business cases can stall when they focus only on finance effort reduction—particularly where intercompany work is distributed across teams rather than owned by a single dedicated group. A stronger business case captures the wider value: reduced transfer pricing implementation risk, better indirect tax compliance, improved cash efficiency through settlement and netting, and more reliable profitability and performance insight by entity, product or service line.

Five practical takeaways to start moving from silos to synergy

  1. Map your intercompany universe. Build a clear inventory of transaction types, volumes and pain points (a heat map is a good start).
  2. Fix upstream first. Strengthen agreements, booking standards and data requirements so reconciliation becomes faster and more automated.
  3. Design for shared outcomes. Bring Controllership, Tax, Treasury and key “data consumers” into the design early to avoid manual workarounds later.
  4. Automate where it reduces disputes. Prioritise solutions that enable dual-sided posting, standard coding and transaction-level matching.
  5. Be intentional about AI. Start with high-value, low-risk use cases (policy support, documentation, controls), and apply strong governance and human oversight.


Audience Q&A: questions we didn’t get to live(answered from the session)

We weren’t able to cover every audience question during the live Q&A. Below are responses we can provide: 

1. How do you recommend defining ownership between Accounting, Tax, Treasury, and business teams where intercompany mismatches arise from source system or master data issues rather than accounting entries?

The session emphasised that intercompany issues are rarely “owned” by one function end-to-end, so ownership needs to follow the lifecycle of the data and transaction. Practically, that means (1) establishing clear governance and policies that define who owns master data, standards and controls, (2) treating data management as a foundational pillar with named owners for intercompany master data and standard definitions, and (3) aligning Tax and Treasury into the process early so requirements (e.g., tax data points, settlement needs) are designed in rather than “reverse engineered” later. It was also noted that many organisations are moving toward a combined intercompany/transfer pricing operating model (e.g., a centre of excellence) to reduce silo-driven handoffs and ensure policy updates, calculation inputs, invoicing and reporting stay aligned.

2. Do you have clients that have debit notes processes in place for under receipting / over invoicing on price / quantity and how do they manage this from a reconciliation / payout clearing perspective?

Yes—many organisations operate debit/credit note (or claims/deductions) processes to address short/over receipts, price/quantity variances and other invoice disputes. Typically the variance is raised in a controlled workflow (often in AP/AR or a deductions module) with a clear reason code and supporting evidence (e.g., PO/contract, GRN, POD, price list). From a reconciliation and payout-clearing perspective, leading practice is to (1) match and track variances at invoice/line level, (2) post to a dedicated clearing/claims account until the debit note is approved and settled, and (3) clear via either an offset on the next remittance/settlement run, a netting arrangement, or a standalone payment/refund—ensuring the remittance advice explicitly references the original invoice and the debit note. This keeps the supplier/customer statement reconciliation clean and provides an audit trail from dispute through to final clearing.

3. Do all intercompany recharges require an actual invoice for the recharge or is a supporting spreadsheet and policy enough to just make the booking? If the recharges are all UK to UK and all the companies are in the same UK tax group for both CT and VAT?

Best practice is to raise an intercompany invoice (or equivalent internal billing document) to evidence the recharge, support intercompany AR/AP reconciliation and provide a clear audit trail. However, for UK-to-UK recharges where entities are in the same UK VAT group, intra-group supplies are generally disregarded for VAT so a VAT invoice is typically not required; a documented recharge pack (policy/ICA + spreadsheet calculation and approvals) is often sufficient to support the journal, provided it is clearly referenced and retained.

If you’d like to continue the conversation—whether you’re tackling manual reconciliations, looking to align transfer pricing implementation, or exploring the right path to automation and AI—we’d be happy to connect and share what we’re seeing across the market.