Elior : Payroll and treasury continuity under disruption, operational in under a month

The context: a large, distributed food services group

Elior is one of Europe's leading contract catering and food services groups, operating thousands of sites across multiple countries. With a workforce running into the tens of thousands, payroll is not a back-office function — it is a front-line operational commitment. The same applies to treasury: supplier payments, cash pooling, and intercompany settlements underpin the daily rhythm of the business.

When Elior began evaluating its operational resilience posture, the starting question was straightforward: if the primary ERP and HR systems became unavailable for several days or weeks, what would actually happen to payroll and treasury? The honest answer — at that point — was that no one knew precisely. That ambiguity was the risk.

The problem: invisible dependencies and no executable fallback

Like most large organisations, Elior had business continuity documentation. Plans existed. But when the Finance and HR teams walked through a realistic disruption scenario, the gaps became visible quickly.

• Payroll data — employee records, salary parameters, variable pay inputs — lived inside systems that would be unreachable under a cyber incident or infrastructure outage
• Treasury workflows depended on banking portals and approval chains routed through Active Directory; an AD outage would sever both
• The people who knew how to execute these processes in degraded mode were not documented — the knowledge was informal and individual
• No tested fallback environment existed; any recovery would have required improvisation under pressure

The approach: continuity as an operational asset, not a document

Elior engaged with Astran to implement AlwaysReady — Astran's operational continuity platform — with a specific scope: get payroll execution and treasury continuity to a state where both could be operated in a controlled, auditable manner without access to primary systems.

The implementation followed a structured sequence. Rather than trying to map everything at once, the team prioritised the two or three most time-critical processes in each function — the ones where a failure to execute within 24 to 48 hours would have material consequences. Everything else could wait.

Payroll continuity

The payroll scope centred on ensuring that even under a major system outage, the Finance team could identify who was owed what, issue payments via an out-of-band channel, and maintain an auditable record of every action taken. This required extracting and curating the right data into a resilient environment, defining the step-by-step workflow that Finance staff would follow, and assigning clear ownership for each step.

Treasury continuity

For treasury, the priority was ensuring that critical supplier payments and cash position visibility could be maintained independently of the ERP and the primary banking portal. The team built fallback payment workflows with appropriate dual-approval controls — ensuring that continuity did not come at the cost of internal controls — and validated that the data needed to execute was available in the resilient environment.

The outcome: operational in under a month

From kickoff to first successful end-to-end simulation, the implementation took less than four weeks. By the end of the first month, Elior's Finance and HR teams could demonstrate — not just describe — what they would do if primary systems went down.

• Payroll execution workflows were live and tested, with documented handoffs and approval steps
• Treasury fallback workflows covered the top critical payment categories, with dual-approval controls intact
• Both workflows were accessible independently of Active Directory and the primary infrastructure
• A simulation run produced timestamped evidence of the process, usable for internal audit and regulatory purposes

What made it work

Several factors contributed to the speed and solidity of the implementation.

Tight scope. Rather than trying to cover every process, the team focused on the handful of workflows where failure within days would be unacceptable. This kept the initial implementation manageable and produced a working capability quickly. Coverage can be extended incrementally.

Business ownership. The Finance and HR teams drove the process definition. IT supported the technical setup, but the workflow logic — who does what, what data is needed, what controls apply — was owned by the people who actually run these processes. This matters: continuity that Finance people have designed is continuity Finance people can execute.

Testing before sign-off. The implementation was not considered complete until a simulation had been run and reviewed. Testing under realistic conditions — not just a walkthrough but an actual execution of the workflow — identified two process gaps that were corrected before go-live. Those gaps would have surfaced, at cost, during a real incident.

Implications for Finance and HR leaders in similar organisations

Elior's experience illustrates a pattern that applies across large distributed organisations in food services, retail, facilities management, and other sectors with high payroll complexity and treasury volume.

The barrier to operational continuity is rarely willingness. It is the assumption that the problem is too complex to solve quickly, or that solving it requires a large IT programme. In practice, a focused implementation targeting the most critical processes — with the right platform and a business-led approach — can produce a working capability in weeks, not quarters.

For Finance leaders facing regulatory scrutiny under DORA, NIS2, or similar frameworks, the ability to demonstrate tested continuity for treasury and payroll processes is increasingly expected, not optional. The Elior implementation shows that this level of readiness is achievable within a normal project cycle.