The finance core —
run on S/4HANA.
One source of financial truth — statutory, management and consolidation on S/4HANA, delivered by teams who've closed real books.
SAP Finance & Controlling on S/4HANA is where the group's numbers live. FI, CO, Treasury, Asset Accounting, Project Systems and Financial Supply Chain — one journal, one universal ledger, real-time close.
Phoenix designs and delivers this layer for enterprises that have to satisfy statutory reporting in multiple jurisdictions AND give management reliable, near-live numbers to run the business. Local GAAP, IFRS, tax authorities and consolidation — under one governed model.
What's in scope.
Controlling (CO)
Treasury & FSCM
Consolidation & Planning
Governance & Compliance
What actually moves.
Faster close
Universal Journal + parallel ledgers collapse reconciliations that used to take days. Real-world programmes have moved month-end from 10+ days to under 5.
Management + statutory in one model
One ledger serves both — no more shadow spreadsheets to bridge CFO views to filed accounts. IFRS and local GAAP handled in parallel ledgers.
Group consolidation without a second stack
Group Reporting (or SAP BPC where the customer's already invested) runs consolidation on the same data, on the same platform.
Compliance held under change
GRC-driven Segregation of Duties and access management keep audit-ready even as the organisation reorgs, acquires and divests.
The approach.
Chart of accounts, legal-entity structure, close pain points, statutory scope, GRC posture — mapped end-to-end.
Target ledger model, universal journal design, parallel-ledger strategy, controlling structure, group consolidation approach.
Build + test + cutover with iterative close-simulations. Data migration handled as a dedicated stream.
First 3 real closes run under hyper-care with the delivery team on the floor. Handover to AMS from there.
Named deliverables.
Every engagement lands specific artefacts — not slides.
Group-wide chart of accounts + controlling model, documented and governed
Universal Journal + parallel-ledger configuration for IFRS + local GAAP
Cost allocations, product costing model, CO-PA reporting layer
Treasury cash-position + liquidity forecasting model
Group consolidation (Group Reporting or BPC) with intercompany matching
GRC access-control ruleset with SoD mitigations documented
Close-cycle runbook: pre-close, close, post-close, statutory
Customers on this journey.
Real Phoenix engagements — measured outcomes at MEA scale.
Pharmaoverseas Group
Egypt's largest pharma distributor moves SAP to the cloud.
EGIC Group
Plumbing market-leader upgrades SAP to RISE on AWS in a month.
Arab Developers Holding
Real-estate group refactors SAP to HANA — with GenAI on top.
The wider SAP practice.
Frequently asked
Do you deliver Group Reporting or stay on BPC?
Both — the right answer depends on where the customer is today. Group Reporting is the SAP-strategic direction on S/4HANA and is our default for greenfield programmes. Where a mature BPC investment is in place, Phoenix continues to deliver on BPC while planning the Group Reporting transition as a discrete workstream.
How do you handle parallel ledgers for IFRS + local GAAP?
One universal journal with parallel ledger accounting. IFRS as the leading ledger, local GAAP as parallel ledgers per country. All postings written in parallel; adjustments handled through valuation and specific ledger postings — not through a shadow ledger or spreadsheet reconciliation.
Can you compress the month-end close?
Yes — closes moving from 10+ days to under 5 is common with S/4HANA's Universal Journal, embedded consolidation and continuous accounting. The gain doesn't come from technology alone; the close-cycle runbook and role clarity around each activity are equally important.
What about GRC and Segregation of Duties?
GRC Access Control is included in the standard scope. We deliver an SoD ruleset appropriate to your organisation size and audit posture, plus a mitigation-controls library. Emergency access management (SPM) and Process Control extensions are on the menu but scoped separately.
Do you cover TRM and cash management?
Yes — Treasury and Risk Management, plus Cash Management, Liquidity Planning and Financial Supply Chain Management (FSCM: Credit, Dispute, Collections). Common combinations include TRM + Cash Management for corporate treasuries; FSCM Credit + Dispute for high-volume O2C environments.
The earliest conversations
are usually the most useful.
Whether you're scoping an SAP move to cloud, restarting a stalled programme, or just trying to figure out where data and AI fit — start with a conversation.