AR at Group Scale: How Inconsistent Invoice Processes Across Entities Quietly Destroy Your Liquidity

AR looks manageable in the consolidated view. The group DSO is within acceptable range. The overdue percentage is not alarming. And then one entity misses a supplier payment run because its collections have been running at 90-day effective DSO for three months while the group average - pooled across eight entities - concealed the problem entirely. AR inconsistency across a group is not primarily a collections failure. It is a visibility and governance failure that accumulated one month at a time until it became a cash event.

Why group DSO is a misleading metric in most multi-entity structures

DSO calculated at group level averages the performance of all entities. An entity with strong collections discipline pulls the group number down. An entity with deteriorating collections is masked until the average deteriorates - by which point the entity-level problem has typically been running for two to four months and the cash impact has already been realised.

The problem is compounded by a measurement error that is almost universal in multi-entity groups: the inclusion of intercompany receivables in the DSO calculation. A group with significant intragroup charging - shared services, management fees, IT allocations - carries intercompany receivables on entity balance sheets. These are not real credit risk. They carry no collection uncertainty. But they inflate the receivables numerator in the DSO calculation, making the group's external credit exposure appear better managed than it is. A group that does not strip intercompany from its DSO calculation is managing to a misleadingly favourable number and does not know it.

EY's 2023 working capital survey found that 54% of multi-entity Group CFOs reported that their group DSO calculation included intercompany receivables. Among those who corrected for intercompany when asked, the adjusted external DSO was on average 12% higher than the reported figure. In a group with EUR 50M of annual external revenue and 60-day payment terms, a 12% DSO overstatement represents approximately EUR 600,000 of misclassified credit risk.

Three structural causes of AR inconsistency across entities

Different payment terms that have never been brought to a group policy. Standard payment terms differ materially across European markets. Thirty-day terms are common in Germany. Sixty-day terms are standard in Italy. Forty-five days is typical in Poland. Without a group policy that defines acceptable terms ranges by market and customer tier, entity-level finance teams negotiate terms based on commercial relationships and local norms. The result: a group whose payment terms structure is unmanaged, whose DSO variation reflects commercial decisions made at entity level without reference to group working capital targets, and whose ability to enforce consistent terms in a centralised renegotiation is limited because the terms have never been documented or approved at group level.

Different escalation protocols that produce different recovery rates. When an invoice goes overdue, the sequence of escalation - automated reminder, second notice, account manager engagement, legal referral - should follow a defined protocol. In most multi-entity groups, this protocol exists locally, if at all, and varies significantly across entities. Some entities have automated reminder workflows. Others rely on an individual noticing that an invoice is 30 days overdue. The cost-to-collect ratio and the recovery rate across the group are therefore a function of who manages AR in each entity, not a function of group policy. This variation is invisible in the consolidated AR report and accounts for significant unexplained variation in entity-level DSO.

Aging bucket definitions that differ across entities. Thirty-day, sixty-day, ninety-day overdue - these categories look standard. What they include is not. Some entities include disputed invoices in the overdue bucket. Others exclude them. Some entities age from invoice date. Others age from the contractual due date. A group aging report assembled from entity data that uses different aging conventions is not a group view. It is an aggregation of incompatible inputs that understates or overstates the true delinquency position. The finance team cannot identify which entities are carrying the real credit risk because the underlying data is not measured consistently enough to support that analysis.

Building a group AR governance framework

The Group CFO's responsibility in AR is to set the framework and hold entities to it - not to manage collections at entity level. Three elements define an effective group AR governance structure.

A group payment terms policy with market-specific ranges. Not a fixed term applied uniformly across all markets - that is commercially unworkable. A defined range by market tier and customer type that establishes what entity finance teams are authorised to offer without Group CFO approval. A new customer in Italy can be offered sixty-day terms within policy. A customer representing more than 5% of an entity's annualised revenue requires Group CFO endorsement for any terms beyond forty-five days. The policy creates a documented terms structure that can be reviewed, optimised, and renegotiated at group level when financing conditions change.

A standardised AR KPI set, calculated consistently across all entities. DSO excluding intercompany - calculated from the same aging date in every entity. Percentage overdue by aging bucket - using the same bucket definitions across all entities. Cost-to-collect ratio. Recovery rate on amounts 60-plus days overdue. These metrics, calculated consistently and reported to group finance on a weekly basis, produce a group AR view that identifies where the real credit risk sits - not where the consolidated average suggests it sits.

A defined escalation protocol from invoice to legal referral. The specific steps, the specific timelines, and the specific trigger points that initiate each escalation level - agreed at group level, applied at entity level, with local legal variation permitted only in the enforcement mechanism at the final step. An automated reminder at day 15 after due date, a second notice at day 30, account manager engagement at day 45, legal referral at day 60 - these are group standards that every entity implements, regardless of local market convention. The protocol is group-mandated. The legal mechanism at the end of it is locally specific.

The case for group AR governance: EUR 120M distribution group

A PE-backed distribution group, EUR 120M revenue, 6 entities across three markets, discovered during a group treasury review that one entity's effective external DSO was 88 days against a reported group DSO of 51 days. The entity represented 19% of group revenue. Its largest customer - representing 31% of that entity's revenue - was 74 days overdue on an invoice. The customer had not been formally escalated because the entity's escalation protocol was informal and not enforced consistently.

The group AR governance programme that followed took 8 weeks. It established a group terms policy, standardised the DSO calculation to exclude intercompany, and implemented an automated escalation workflow across all entities. Within two quarters, entity-level DSO ranges had narrowed from 28-91 days to 34-64 days. The weighted group DSO (excluding intercompany) improved from 47 days to 41 days. The improvement represented approximately EUR 1.6M of freed working capital - available immediately, without any change to the group's external financing arrangements.

If your group DSO is not calculated on a consistent basis across entities, or if you have identified a working capital stress in one entity that was not visible at group level until it had become acute - talk to us about building an AR governance framework that gives you entity-level visibility without requiring entity-level micromanagement.