Don't automate the mess: sequencing finance transformation with SECAR

For decades, the default playbook for finance transformation has been some version of lift, shift, then fix. Move fragmented, manual processes to a shared service centre or outsourcing partner first, then clean them up and automate them later.

The results are familiar to anyone who has lived through one of these programmes:

• Long stabilisation periods. Twelve to twenty-four months of “service debt” after transition, while the receiving team learns undocumented workarounds.
• High attrition in the shared service centre. Analysts spend their days on swivel-chair work and firefighting exceptions nobody wrote down.
• Poor returns on digital investment. Expensive RPA and OCR tools are layered on top of broken, redundant steps, effectively hard-coding the technical debt.

The problem isn’t the tools or the location. It’s the sequence.

The SECAR sequence

SECAR stands for Simplify, Eliminate, Consolidate, Automate, Relocate. It is a sequencing model with one strict rule: you don’t move to the downstream levers, Automate and Relocate, until the upstream work, Simplify, Eliminate and Consolidate, has removed process complexity and standardised the underlying data.

Relocation is not a transformation tool. Relocation is the operational consequence of a successful transformation.

Each stage is a gate, with its own evidence required to pass.

1. 01SimplifyFewer steps, layers, hand-offs
2. 02EliminateRemove work that drives no decision
3. 03ConsolidateOne standard, one set of data
4. 04AutomateAPIs, rules, matching, AI
5. 05RelocateMove stable exceptions only

• People decision
• Control point
• System / automated

1. Simplify: de-complexify and de-layer

Complexity builds up quietly through reorganisations, acquisitions, regulatory patches and staff turnover. Teams add shadow controls, local workarounds and extra approval layers to manage one-off failures, and those additions never go away.

Simplify strips them back before you touch systems or organisation design:

• Replace long sequential approval chains with risk-weighted, threshold-based routing.
• Replace email inboxes and ad-hoc file drops with one structured, validated intake channel.
• Cut the hand-offs between requesters, local controllers, procurement and accounting.

Risk avoided: automating or offshoring convoluted rules that should have been fixed at the policy level.

2. Eliminate: zero-base every activity

Finance functions carry a surprising amount of work that exists purely because “we’ve always done it this way”. Eliminate asks of every task, report and check: what decision does this drive?

• Audit report consumption. If a schedule or dashboard drives no capital, risk or compliance decision, sunset it. A useful test is a “silent shutdown”: pause distribution and see whether anyone asks for it within 30 days.
• Remove duplicate validations where an ERP rule, such as a three-way match tolerance, already enforces the control.
• Retire shadow spreadsheets that run alongside the core system.

Risk avoided: spending transformation budget or outsourcing fees to run work that adds no value.

3. Consolidate: one standard, one set of data

Decentralised organisations end up with many local variants of the same process: different charts of accounts, vendor definitions, payment terms and payment runs.

• Harmonise master data: chart of accounts, cost centres, vendors, customers and items.
• Standardise policies: payment terms, credit limits, expenses.
• Consolidate cycles: replace ad-hoc daily runs with predictable, enterprise-wide schedules.

Risk avoided: building and maintaining separate automations, or separate teams, for fifteen regional variants of one process.

4. Automate: deterministic first, intelligent where it counts

Only now, with a simplified, purged and standardised process, can automation be deployed reliably:

• System-to-system integration through APIs, EDI and host-to-host bank connections.
• ERP rule-based matching and clearing, such as GR/IR auto-clearing and cash application.
• Intelligent document processing to read invoices and remittances straight into the ERP.

This is where our principle “AI reads, rules decide” applies. AI extracts the data; transparent business rules make the decisions.

Risk avoided: fragile automations that break because the data feeding them is volatile or unstandardised.

5. Relocate: move stable work, not chaos

By this point the process has shed its noise, manual volumes have dropped, and what remains is stable, rule-based exception handling. That is the right moment to move work to a shared service centre, global capability centre or partner, through:

• structured knowledge transfer against lean, documented procedures
• clear service levels and KPIs
• a shift to exception-only operations, where analysts resolve discrepancies and find root causes rather than key data.

Risk avoided: chaotic transitions, expensive hypercare and service collapse.

• Onshore finance
• Illustrative shared-service locations

Illustrative only. The locations are typical examples, not a recommendation. Under SECAR, work moves only after it has been simplified, standardised and automated.

What it looks like across finance

Process	Simplify	Eliminate	Consolidate	Automate	Relocate
Procure-to-Pay	Flatten PO approvals; guided buying	Stop retrospective POs and tracking spreadsheets	Standard payment terms; one vendor master	Invoice capture, 3-way match, bank integration	Price/quantity exceptions and statement recs
Order-to-Cash	Objective credit scoring; fewer dispute codes	Stop manual order re-keying and low-balance chasing	Group credit limits; one billing engine	EDI orders, automated cash application, dunning	Complex cash allocation, disputes, tier-2 collections
Record-to-Report	Parallel close calendar; standard journal templates	Remove immaterial accruals and repeat top-sides	Global chart of accounts; intercompany hub	Recurring journals, auto-reconciliations	Variance-based recs, journal review, fixed assets
FP&A	Driver-based planning; clear variance thresholds	Kill unconsumed reports and manual data wrangling	One semantic data layer; central reporting	Automated pipelines, self-service BI, forecasting	Reporting factory and baseline modelling

Typical measures move with each stage: first-time match rate and cost per invoice in P2P, unapplied cash and dispute cycle time in O2C, days to close and auto-reconciled accounts in R2R, and the ratio of business partnering to data assembly in FP&A.

Where Lean, Six Sigma and Agile fit

SECAR doesn’t replace established methods. It gives them a sequence:

• Lean supplies the diagnostic tools for Simplify and Eliminate: value stream mapping and the eight wastes. But Lean says little about when to automate or relocate.
• Six Sigma and DMAIC are powerful inside a stage, for example to find the root cause of recurring billing errors during Consolidate. Without SECAR, teams risk perfecting a reconciliation that should have been eliminated.
• Agile is the right way to run Automate: once rules and data are consolidated, the build breaks down into sprints. Without the upstream gates, Agile teams quickly automate unstable requirements.
• Kaizen takes over after Relocate, as the daily improvement culture in a stable shared service team.

Making the gates real

A sequence only works if it’s enforced. In practice that means:

1. A steering committee with gate authority. No automation licences or outsourcing contracts are signed until the Simplify, Eliminate and Consolidate gates are signed off.
2. Global process owners accountable for each end-to-end process across regions.
3. Measurable gate criteria. For example, a material cut in approval steps before passing Simplify, a single active chart of accounts and vendor master before passing Consolidate, and a target straight-through processing rate before relocation.
4. Psychological safety for elimination. Separate “this task should go” from “my job is at risk”, and commit to reskilling people into higher-value analysis.
5. “Comply or explain” for local variants. Any non-standard process must be justified by a genuine statutory or tax requirement.

And watch for the classic anti-patterns: the automated mess, the lift-and-shift disaster, zombie tasks that quietly come back, master data neglect, and knowledge drain from a rushed transition. A dual-running period, where the receiving team completes several clean cycles before the old team steps away, is cheap insurance.

The bottom line

Lean gives you the language of waste. Six Sigma gives you the maths of variation. Agile gives you delivery speed. None of them, on their own, enforces the order of operations that stops organisations from offshoring or automating broken processes.

SECAR does. Simplify, eliminate and consolidate first. Then automate. Relocate last, when the work is stable enough to move. Done in that order, shared services and capability centres become what they were meant to be: highly automated centres of excellence, not low-cost clearing houses for process defects.

Simplabs uses the SECAR sequence across its transformation, process re-engineering and automation work. See how we apply it →

Frequently asked questions

What is the SECAR framework?

SECAR is a sequencing model for finance transformation: Simplify, Eliminate, Consolidate, Automate, Relocate. Each stage is a gate that must be passed before the next, so organisations don’t automate or offshore broken processes.

Why should relocation come last?

Moving fragmented, manual work to a shared service centre or partner exports the problem. Once a process is simplified, standardised and automated, the remaining work is stable exception handling that transfers cleanly.

How does SECAR relate to Lean and Six Sigma?

Lean supplies the waste diagnostics for Simplify and Eliminate, Six Sigma and DMAIC solve root causes within a stage, Agile delivers the Automate stage, and Kaizen drives improvement after Relocate.

Can SECAR be applied to e-invoicing or ERP programmes?

Yes. For e-invoicing, for example, simplify intake routes, eliminate PDF and paper channels, consolidate supplier master data and tax codes, then automate Access Point integration and matching.

Published 5 November 2026 · Simplabs Limited