---
title: "Intercompany close: why spreadsheets become the bottleneck"
description: "When Excel stops scaling for multi-entity intercompany: version sprawl, weak evidence trails, lost context—and how a governed workspace differs from a giant ERP programme."
locale: en
canonical: https://www.ninonai.com/en/solutions/intercompany-vs-excel
last_updated: "2026-08-05"
---

# Intercompany work and Excel: when the spreadsheet turns into the main close risk

Excel wins on ad-hoc agility; it falters when closing is a team sport on repeat—controllers must replay the same scenarios, auditors ask who approved which version and platform owners fear opaque macros. Intercompany magnifies the weakness: parallel ‘final_FINAL’ workbooks, brittle joins on heterogeneous narrations, key-person glue holding the process together. Moving to structured tooling is about reproducibility and proof, not techno-luxury.

## Finance symptoms groups recognise

Teams notice recurring end-of-month delays, debates about breaks ‘we already solved three closes ago’ and an inability to narrate a coherent event log for outsiders. Coordination cost grows faster than entity count because flows and formats diversify long before row volume explodes. Hero-dependent adjustments are as much an operational risk as a hiring risk.

## What a workspace adds beyond a workbook

Governed sessions tie work to a period, expose reconciliation status and make decisions legible in a consistent schema. Proposals carry rationales before approvals, shifting audit conversations from spreadsheet archaeology to substantive review. Memory shrinks recurring noise—tolled rounding policies or bridge accounts should not be re-negotiated via email every cycle. APIs let automation live outside one person’s macro toolbox while remaining observable to engineering.

## Avoiding a big-bang vanity migration

Prudent programmes start with a controlled data perimeter—often standard GL extracts—and disciplined human review. Measure control-time savings and dossier quality before widening connectors. This page mirrors the concise decision narrative from the spreadsheet guide for executives who want the executive summary.

## Honest boundaries (spreadsheet or not)

No tool removes judgement on corporate policy, rates or statutory interpretation. The candid aim is observable, documented intercompany work with fewer single points of failure—not a frictionless fairy tale.

## Leave spreadsheets via a Pilot, not a card checkout

The credible path: Close Pilot on a real period (CSV, review, audit pack), then annual Workspace if you go ahead. Essentiel self-serve remains a teaser for 2–5 entities. Links: Pilot, Pricing, and the Close Pilot guide.

## FAQ

**Q.** Should finance ‘ban’ Excel?
**R.** No—it remains brilliant for modelling. Risk spikes when unmanaged workbooks become the system of evidentiary record for statutory close.

**Q.** Can we migrate progressively?
**R.** Yes: start with a Pilot (limited period and entities) or one flow type, then extend sessions and rules.

**Q.** Are formulas always bad?
**R.** They hurt when fragile logic encodes mission-critical policies without formal review, documentation or regression awareness across closes.

**Q.** How should IT be pitched?
**R.** Emphasise operational risk reduction, standard exports and authenticated APIs rather than unsubstantiated headcount removals.

**Q.** Suggested next reads?
**R.** Close Pilot to start, Pricing for packs, then the intercompany software pillar and Excel / multi-ERP guides.

## Sitemap

See the full [sitemap](/en/sitemap.md) for all pages.