Coriza
“We Had to Change Everything”: Leading Business Transformation in PNG with SAP and Coriza

“We Had to Change Everything”: Leading Business Transformation in PNG with SAP and Coriza

by | Sep 29, 2025 | Blog Post, Case Study, CFO, CIO, Cross Industry, Financial Controller, Manufacturing, Program Manager, SAP S/4HANA Cloud, Warehouse Manager

Running a market-leading business in Papua New Guinea is not for the faint-hearted.

by Simon Barstow – General Manager Dulux PNG

 

At Dulux PNG, we manufacture and distribute paints, coatings, and chemicals across some of the most complex and challenging terrains in the world. Our teams operate in a fast-paced, resource-constrained environment, and we take immense pride in doing it well.

But a few years ago, it became clear that we couldn’t keep going the way we were. Our systems were outdated, our processes manual and error prone, and our people didn’t trust the ERP platform. Each department kept its own spreadsheets, and decisions were made in a silo rather than based on validated information.

We didn’t just need better software, we needed to fundamentally rethink how the business operated.

When I joined Dulux PNG, our ERP system wasn’t designed for manufacturing or commercial use, didn’t support remote sales, and offered zero visibility into procurement, production costs, or sales performance.

Everything from warehouse picking to delivery tracking was done manually. I still remember customers saying they couldn’t pay invoices because they hadn’t received the delivery docket, which meant we had to go digging through boxes to find it.

That kind of inefficiency wasn’t sustainable, not for our people, not for our customers, and certainly not for our future.

 

Download our eBook

The Impact of the Systems and Partners You Choose

Since DuluxGroup uses SAP globally, it made sense for us to align from a platform perspective. But implementing SAP in Papua New Guinea is not a simple copy-paste. Our business environment is unique, fast-moving, hands-on, and full of operational nuances that don’t exist in a typical corporate playbook. We needed more than a system, we needed a partner who could navigate that reality with us.

I was looking for a team that wouldn’t just deploy technology, but one that would embed themselves in our business. A team willing to listen, challenge our assumptions, and work alongside us to build something sustainable for the long term. We didn’t need a vendor, we needed a true partner.

That’s exactly what we found in Coriza.

From the beginning, they were clear, honest, and deeply engaged. They didn’t try to impress with buzzwords or over promise outcomes. Instead, they asked hard questions, pushed us to rethink old habits, and helped us focus on what would truly drive value. That kind of straight talk, and their commitment to understanding our context, was invaluable.

 

Fixing the Foundations: Data, Process and People

Before we could move forward, we had to understand exactly where our processes were hitting a wall. That meant starting with a full health check across every core function: finance, warehousing, procurement, sales, and beyond. We looked at how transactions flowed, where handoffs stalled, and how data was being captured, shared, or lost along the way. It quickly became clear that our problems weren’t isolated. They were systemic.

Once we had that baseline, we went straight to the heart of it: the data. Poor-quality data was undermining everything: product codes were inconsistent, pricing data was duplicated, vendor records had gaps. Cleaning up our master data was no small job, but it was essential. Once that work was done, I could finally look at a report and know it reflected the truth.

With better data came the chance to revisit how our processes actually worked. We didn’t just want to replicate old habits in a new system. We mapped out how we wanted things to run, using SAP’s standard capabilities as the reference point. That forced us to rethink how quotes got created, how inventory moved, and how approvals were managed. In many cases, simplifying our processes created efficiencies we hadn’t even been aiming for.

And of course, none of it would stick without our people. This wasn’t just about learning to click the right buttons. We spent time explaining why the changes mattered, showing how their work connected to business outcomes, and giving them space to ask questions and test things out. It wasn’t always smooth, but gradually, people stopped seeing SAP as an obstacle and started seeing it as a tool they could trust.

One of the biggest turning points came when team members who had previously avoided SAP started coming to us saying, “I’m still doing this in Excel, how do I move it into SAP?” That shift, from resistance to ownership, was when I knew the culture was changing.

The Results: Faster, Smarter, More Agile

The transformation has been significant.

  • We now close our books on Day 1. The finance team has live, clean data and no longer needs to spend days chasing adjustments.
  • Quotes that used to take 4–5 days now go out in 24 hours. Our sales teams can act quickly, and our customers notice the difference.
  • Warehouse operations are dramatically faster. Bin locations mean our teams pick, pack, and move without wasting time.
  • OTIF is now over 95%. That’s a major boost to customer satisfaction.
  • We’re nearly fully paperless. This isn’t just about efficiency, it’s a big win for sustainability too.

And the biggest shift? We now run the business based on facts, not assumptions. Decisions are made with real-time data at our fingertips, giving us the confidence to act quickly and accurately. Whether it’s approving a purchase order, reviewing a sales pipeline, or assessing performance, we know we’re working from a single, trusted source of truth. I travel often, but even from a plane I can review quotes, approve POs, and stay in control. That visibility changes everything.

Lessons from the Journey

Looking back, here’s what I’d tell anyone starting a similar transformation:

  1. Avoid customisation wherever possible. Sticking to SAP’s standard features keeps the system simpler, cheaper to run, and easier to upgrade. The more you customise, the more you introduce long-term complexity and cost.
  2. Get your data right. Clean, consistent data is the foundation for everything.
  3. Choose a partner who tells you the truth. You want people who know your business and aren’t afraid to challenge you.
  4. Empower your team. The system only works if your people believe in it and take ownership.
  5. Treat it as a journey. We’re still improving, still digitising, and still finding ways to get better.

Where We’re Headed

We’ve laid a solid foundation, but we’re not finished. Next, we’re building out reporting dashboards, expanding forecasting capabilities, and digitising the last of our manual workflows.

With Coriza as our long-term partner, I’m confident we’ll get there.

SAP and Coriza haven’t just modernised our systems, they’ve helped us become faster, more resilient, and more in control. We’re leading the market in PNG, and we’re only just getting started.

More Resources

AI for SAP: Joule or Copilot — What CFOs and Business Leaders Need to Know

AI for SAP: Joule or Copilot — What CFOs and Business Leaders Need to Know

by | Sep 29, 2025 | AI & Automation, Blog Post, CFO, CHRO, CIO, Consumer Products, Cross Industry, Demand Planner, Distribution, Finance Leadership, Financial Controller, HRIS Manager, Manufacturing, Professional Services, Program Manager, SAP S/4HANA Cloud, Warehouse Manager

Most executives no longer ask whether AI makes a difference. We have all seen how quickly a draft board paper or customer email can appear on screen. What once took hours now takes minutes. The question has shifted. It is no longer “does AI help?” It is “where do we apply it, and how do we apply it safely?

For organisations that run SAP and Microsoft 365, the practical conversation almost always comes down to two names: SAP Joule and Microsoft Copilot.

There are plenty of other AI products in the market. ChatGPT, Gemini and Grok are all part of the landscape. But for CFOs and CIOs leading organisations built on SAP, and with Microsoft 365 as the productivity backbone, the real decision point is whether to adopt Joule, Copilot, or both.This article explains what each option offers, why they matter for finance and operations leaders, and what questions you should be asking before you take the next step.

 

Why This Matters Now

Most executives no longer ask whether AI makes a difference. We have all seen how quickly a draft board paper or customer email can appear on screen. What once took hours now takes minutes. The question has shifted. It is no longer “does AI help?” It is “where do we apply it, and how do we apply it safely?

For organisations that run SAP and Microsoft 365, the practical conversation almost always comes down to two names: SAP Joule and Microsoft Copilot.

There are plenty of other AI products in the market. ChatGPT, Gemini and Grok are all part of the landscape. But for CFOs and CIOs leading organisations built on SAP, and with Microsoft 365 as the productivity backbone, the real decision point is whether to adopt Joule, Copilot, or both.This article explains what each option offers, why they matter for finance and operations leaders, and what questions you should be asking before you take the next step.

 

SAP Joule: AI inside the ERP

SAP Joule is not an add-on. It is built into SAP’s cloud applications, including S/4HANA Cloud and SuccessFactors. That means it already understands SAP’s data models, transactions, and authorisations.

Think of it as a native assistant. Ask Joule why a purchase order is blocked, and it will respond using the same rules and data you trust inside SAP. Ask it to provide a summary of supplier performance, and it draws from your live transactional data. There is no need to build connectors or map roles. Joule already knows who you are and what you are allowed to see.

This is its greatest strength. Joule inherits SAP’s governance model. If your role in SAP restricts you from seeing certain data, Joule respects that same rule. SAP has also confirmed that customer data processed by Joule is not used to train external foundation models. For leaders, this offers a level of confidence that consumer AI tools cannot provide.

Joule is also designed to evolve as SAP evolves. SAP has committed to extending Joule’s reach across its portfolio, with new skills and agents arriving over time. That roadmap is important. It means that adopting Joule is not a one-off project. It is a way of ensuring that AI becomes part of how you run SAP, release after release

Microsoft Copilot: AI where your people work

While Joule is embedded in SAP, Microsoft Copilot lives in the tools your teams use every day — Outlook, Excel and Teams. This is where most finance teams spend their time, so the productivity benefit is immediate.

The way it works is straightforward. Copilot connects into SAP using certified APIs. From there, it can bring live data into the Microsoft 365 environment. Ask Copilot in Outlook to prepare a collections email, and it can pull the relevant balances from SAP, merge them with customer details, and draft the email ready for review. Ask Copilot in Excel why operating expenses are above budget, and it can analyse the variance, link to SAP transactions, and draft commentary that you can paste straight into a board pack.

The real advantage of Copilot is that it can combine SAP data with other corporate information managed inside Microsoft 365. That might include policy documents stored in SharePoint, supplier contracts in OneDrive, or communications in Teams. This cross-system capability is powerful because real decisions are rarely made on ERP data alone. Leaders often need context, documents and communication history. Copilot can surface these in one place.

Microsoft has also developed a specific Copilot for Finance. This is designed for finance teams and supports scenarios such as reconciliations, variance analysis and collections. While some of these features are still in preview, the direction is clear: Microsoft is making finance a core focus for Copilot inside Microsoft 365.

Why not just use ChatGPT?

It is a fair question. ChatGPT is quick, flexible and already used by many teams. For some tasks it works well. But when it comes to ERP data, the risks are obvious.

ChatGPT does not enforce SAP authorisations. It does not integrate with Microsoft tenant security. And while consumer versions of ChatGPT may use prompts to improve their models, both SAP and Microsoft have been clear that enterprise data accessed through Joule or Copilot is not used to train foundation models for others.

ChatGPT can generate answers, but it cannot act directly on SAP data. It cannot approve an invoice, prepare a live collections email, or provide commentary linked to transactions in your ERP. That is why organisations serious about AI in finance and operations look to Joule or Copilot. They are designed for enterprise use, with security, governance and auditability in mind.

Security and governance considerations

For most CFOs and CIOs, the attraction of AI is tempered by a single concern: security. Productivity gains are only valuable if they do not compromise compliance or governance.

With Joule, the rules are clear. It inherits SAP’s security model. Authorisations apply and the ERP remains the system of record. With Copilot, governance is handled through Microsoft tenant controls. Data policies and loss-prevention rules set the boundaries for how SAP data is used inside Microsoft 365. In both cases, prompts and actions should be logged so there is always an audit trail.

There is also the question of ownership. AI that draws on ERP data is not just an IT project. Finance leaders need to be directly involved in shaping use cases, testing outputs, and defining success measures. CIOs bring the technical expertise to manage connectors, security and compliance. CFOs bring the accountability for process integrity and financial outcomes. Both roles must share ownership from the outset.

Data quality and readiness

Another consideration is data quality. AI is only as good as the data it draws from. If your SAP master data is inconsistent, if roles and authorisations are poorly managed, or if your processes rely heavily on manual workarounds, AI will simply amplify those issues.

This is where experience shows that sequencing matters. Organisations that have stabilised their ERP first — cleaned master data, simplified processes, built trust in the system — are better placed to benefit from AI. If those foundations are weak, AI adoption can expose flaws instead of delivering value.

Joule or Copilot? The Practical Answer

So which should you choose? In reality, most organisations will end up using both. Joule is best for AI inside SAP transactions. Copilot is best when SAP data needs to be combined with other information inside Microsoft 365.

For example:

  • A supply chain manager may use Joule to explain why a purchase order is blocked and suggest the next step.
  • The finance team may use Copilot in Outlook to prepare a collections email that merges SAP data with customer contact details.
  • A CFO may use Copilot in Excel to draft board commentary based on SAP variances, while relying on Joule inside SAP to confirm transactional accuracy.

The two products are already being integrated. SAP and Microsoft have announced bi-directional links between Joule and Microsoft 365 Copilot. That means users will increasingly be able to start in either environment and reach into the other.

The choice is not either/or. The real decision is where to start, how to scale, and what guardrails to put in place.

Adoption guardrails: a practical roadmap

Executives need more than a vision. They need to see a disciplined approach. A simple adoption roadmap could look like this:

Phase 1: Identify scenarios (0–30 days)
Start with 2–3 scenarios that matter most to Finance. Collections, variance commentary and reconciliations are common candidates. Define the KPIs you want to influence, such as DSO, close cycle time or audit preparation hours.

Phase 2: Secure governance (30–60 days)

Review SAP roles and authorisations to ensure they are accurate. Configure Microsoft tenant policies, including data loss prevention rules, for Copilot. Establish a process for logging prompts and responses.

Phase 3: Run pilots with Finance ownership (60–90 days)

Deploy Joule or Copilot in the chosen scenarios. Have Finance own the outcomes while IT ensures compliance. Measure progress against the defined KPIs.

Phase 4: Scale carefully (beyond 90 days)

Extend to additional use cases once the first pilots prove reliable. Continue reviewing governance and data quality. Treat AI adoption as a business discipline, not a technology experiment.

This phased approach keeps expectations realistic, avoids technical debt, and demonstrates value early.

What CFOs and CIOs should ask now

Before you commit to a path, ask yourself these questions:

  1. Do we have a clean ERP foundation that AI can build on?
  2. Are our SAP roles and authorisations accurate and enforced?
  3. Do we have Microsoft tenant policies in place to govern the use of SAP data inside Copilot?
  4. Which finance metrics matter most in the next 90 days — cash, close cycle time, audit readiness — and how could AI improve them?
  5. What guardrails will we use to measure and control the impact of AI adoption?

These questions ensure that AI adoption is not just a technology choice but a business discipline.

Act with Intent

AI in SAP is no longer theoretical. Joule and Microsoft Copilot are here now. Each has distinct strengths. Joule is embedded in SAP and designed for in-system intelligence. Copilot is integrated into Microsoft 365 and designed for cross-system context. Together, they cover most use cases CFOs and CIOs face.

The question is not which is better. The question is how to apply them safely, in the right sequence, and with the right guardrails.

At Coriza, we help organisations answer that question. We focus on practical adoption that delivers results in 90 days. Whether it is accelerating cash collections, shortening the close, or strengthening governance, we ensure AI adoption is measurable, secure and aligned with your business.

Book a 30-minute AI Readiness Review with Coriza. We will map out your Joule and Copilot opportunities, review your governance posture, and create a plan that works for your organisation.

 

More Resources

Your ERP Partner Needs the Confidence to Guide, Not Just the Skills to Configure

Your ERP Partner Needs the Confidence to Guide, Not Just the Skills to Configure

by | Sep 20, 2025 | Blog Post, CFO, CHRO, CIO, Consumer Products, Cross Industry, Distribution, Financial Controller, Manufacturing, Professional Services, Program Manager, SAP S/4HANA Cloud, Warehouse Manager

The Hidden Risk in ERP Projects

ERP implementations are among the most complex initiatives an organisation can undertake. They promise new levels of transparency, control, and agility, yet too many still fall short. Projects run over budget, take longer than expected, or fail to deliver the business improvements that executives were counting on.

The problem is not usually the technology. SAP S/4HANA Cloud, SuccessFactors, and other leading ERP platforms are proven, reliable, and scalable. The problem is in how they are implemented.

One of the most overlooked risks is the partner dynamic. Many ERP partners are highly skilled technically, but weaker when it comes to business process advisory. As a result, they fall into a pattern of saying “yes” to client requests. On the surface, this feels safe: the client gets what they ask for, and the partner avoids blame if something later breaks.

But safe is not the same as successful. An ERP partner that cannot challenge assumptions, push back on poor decisions, or guide clients toward fit-to-standard practices leaves the business exposed to failure.

The truth is simple. ERP projects succeed when partners combine technical skills with the confidence and process expertise to guide.

Why Partners Say Yes Too Often

It is easy to see why “yes” becomes the default response.

  • Technical focus without process strength: Many consultants know the system inside out but are less confident discussing the client’s broader business operations. If they are not sure how a design choice will impact finance, procurement, or compliance, they default to following instructions.
  • Client-driven safety net: Some partners believe that if the client makes the decision, the responsibility for failure sits with them. If the project under delivers, the partner can say, “We built what you asked for.”
  • Avoiding conflict: ERP projects are stressful and high stakes. It can feel easier to keep clients comfortable than to confront them with hard truths.

The result is an ERP system that mirrors the old world. Legacy processes are rebuilt inside a new platform. Data issues are papered over instead of solved. Customisations proliferate because no one was confident enough to explain why they were unnecessary.

That is how businesses end up with expensive, complex systems that still require workarounds and do not earn the trust of their people.

The Value of Confidence in ERP Delivery

A confident partner does not just configure the system. They guide the business toward practices that are proven, sustainable, and aligned with cloud principles.

  • They challenge assumptions. If a client wants to rebuild an old approval chain that adds no value, they explain why it should be simplified.
  • They protect the long term. By resisting unnecessary customisation, they ensure upgrades remain simple and costs remain low.
  • They strengthen adoption. By showing staff not just how the system works but why processes are changing, they build ownership and trust.
  • They reduce risk. By insisting on data cleansing and fit-to-standard processes, they prevent failure before it happens.

This is not about being combative. It is about bringing the right mix of business process strength and technical expertise so clients can make informed decisions.

Dulux PNG: Transformation Through Guidance

When Coriza partnered with Dulux PNG, the business was struggling. Systems were outdated, processes were manual, and staff did not trust the ERP. Customers even refused to pay invoices because proof-of-delivery documents were missing.

The easy path would have been to say “yes” to every request: rebuild processes as they were, configure around messy data, and hope for the best. Instead, we took the harder path.

  • We told the business their data had to be cleansed and standardised before transformation could succeed.
  • We challenged legacy processes, mapping them back to SAP best practice instead of replicating old inefficiencies.
  • We worked with staff to build ownership, explaining why change mattered and giving them confidence to move work out of spreadsheets and into the system.

The results were significant:

  • Day 1 month-end close instead of weeks of adjustments.
  • Sales quotes in 24 hours instead of 4–5 days.
  • On Time In Full (OTIF) above 95 percent, a direct lift in customer satisfaction.
  • Warehouse operations digitised and accelerated, with bin locations and paperless workflows.

Perhaps the most important shift was cultural. Employees who had avoided SAP began asking how to use it for more of their work. That transformation did not come from saying yes. It came from having the confidence to guide.

Bubs Australia and the Cook Islands: Facing Hard Realities

The same approach shaped our work with other clients.

  • Bubs Australia, a fast-growing FMCG company operating across Australia, the USA, and China, had fragmented systems that slowed order management. We were clear: their patchwork could not scale. By moving to SAP Cloud ERP and integrating with Shopify, they achieved real-time stock visibility, faster order processing, and a unified platform for international growth.
  • The Cook Islands National Superannuation Fund relied on Excel for core finance and procurement. It worked in the short term, but left the organisation exposed to errors and inefficiency. Our position was firm: spreadsheets are not a system of record. By adopting SAP Cloud ERP, the Fund gained real-time bank reconciliation, stronger compliance, and audit-ready reporting.

In both cases, the outcome depended on more than technical configuration. It depended on telling clients the truth about what was holding them back, then guiding them toward best practice.

The Cloud Mindset: Learning from Larger Enterprises

One of the biggest traps in ERP transformation is trying to replicate what came before. Clients ask for custom reports, bespoke workflows, or approval hierarchies designed for another era.

The problem is that cloud ERP is not meant to be a copy of legacy systems. It is built on decades of best practice. The businesses that succeed in the cloud are the ones that embrace that standard.

Larger enterprises that spent decades running heavily customised ERP systems have now made it a priority to simplify. Their common goals are clear:

  • Remove customisations that created complexity and cost.
  • Adopt standard content so the system is easier to run and easier to upgrade.
  • Eliminate technical debt that has been holding them back.

For new adopters of cloud ERP, the lesson is obvious. Do not repeat the mistakes of the past. Do not replicate inefficiencies or build technical debt into your first system. Start clean, adopt standard, and design for the future.

Why Clients Resist Best Practice

If fit-to-standard and clean design are so clearly beneficial, why do many clients resist them?

  • Familiarity: People are comfortable with the way things have always been done, even if those processes are inefficient.
  • Perceived uniqueness: Every organisation believes its processes are different. In reality, most are standard variations already covered in cloud ERP.
  • Fear of change: Simplification feels like losing control, when in fact it creates control by reducing hidden workarounds and errors.

This is where partner confidence matters most. Without it, clients default to old habits and partners fall into the trap of saying yes. With it, the business is guided toward choices that will stand the test of time.

Four Truths Every ERP Project Needs

Across industries and regions, four truths consistently separate successful projects from failed ones:

  • Data is non-negotiable. Clean, consistent master data underpins everything.
  • Customisation kills agility. Stick to SAP standard unless there is a clear, costed business case and an exit plan.
  • People drive adoption. ERP is not just a system change, it is a cultural shift. Teams must understand why the changes matter.
  • Transformation is a journey. Go-live is only a milestone. Continuous improvement is what sustains value.

Manufacturing is at a Crossroads: Why Truth Matters Now

Australian manufacturing illustrates why this matters. The sector contributes just 5.5 percent of GDP, down from double digits in past decades, yet still employs over 930,000 people. Costs are rising, demand is fragile, and churn is high, with 437,000 businesses opened in 2024–25 and 370,000 closed in the same period.

In this environment, transformation is not optional. It is survival.

Yet too many manufacturers still rely on spreadsheets, outdated systems, and manual workarounds. The result is slow reporting, unreliable customer commitments, and cash locked in the wrong inventory.

The truth is straightforward:

  • Excel is not ERP.
  • Manual processes do not scale.
  • Siloed data kills transparency.

The Dulux PNG story shows what happens when these truths are accepted. Month-end closes fall to Day 1, customer reliability improves, and decisions are made on real-time data. That is the payoff of choosing a partner with the confidence to guide.

What Executives Should Demand from Their ERP Partners

For CFOs, CIOs, and COOs, the choice of partner can make or break transformation. The right partner should:

  • Challenge assumptions and explain alternatives.
  • Insist on cleansing and standardising data before configuration.
  • Resist unnecessary customisation and protect the long term.
  • Stand by business outcomes, not just technical go-live.

These are the hallmarks of a partner that has both technical strength and business process confidence.

More Resources

Manufacturing at a Crossroads: Why Transformation Can’t Wait

Manufacturing at a Crossroads: Why Transformation Can’t Wait

by | Sep 16, 2025 | Blog Post, CFO, CIO, Consumer Products, Financial Controller, Manufacturing, Program Manager, SAP S/4HANA Cloud, Warehouse Manager

 

Australian Manufacturing Under Pressure

ERP implementations are among the most complex initiatives an organisation can undertake. They promise new levels of transparency, control, and agility, yet too many still fall short. Projects run over budget, take longer than expected, or fail to deliver the business improvements that executives were counting on.

The problem is not usually the technology. SAP S/4HANA Cloud, SuccessFactors, and other leading ERP platforms are proven, reliable, and scalable. The problem is in how they are implemented.

One of the most overlooked risks is the partner dynamic. Many ERP partners are highly skilled technically, but weaker when it comes to business process advisory. As a result, they fall into a pattern of saying “yes” to client requests. On the surface, this feels safe: the client gets what they ask for, and the partner avoids blame if something later breaks.

But safe is not the same as successful. An ERP partner that cannot challenge assumptions, push back on poor decisions, or guide clients toward fit-to-standard practices leaves the business exposed to failure.

The truth is simple. ERP projects succeed when partners combine technical skills with the confidence and process expertise to guide.

Download our eBook

Why Digital Transformation in Manufacturing Matters

For established manufacturers, cost headwinds, skills shortages, and supply risks mean efficiency and agility are non-negotiable. For new entrants, building digital foundations from day one is the difference between scaling successfully and becoming another exit statistic.

Digital transformation in manufacturing is no longer optional, it is the first step to safeguarding competitiveness, resilience, and growth.

From Efficiency to Intelligent Manufacturing

Modern transformation means more than cost-cutting. It requires rethinking how businesses operate, creating a single operating rhythm where finance, production, and sales all work from the same facts.

When those foundations are in place, manufacturers can layer on intelligence:

  • Automation to remove repetitive tasks
  • AI to predict risks before they hit
  • Real-time insights to protect margin and cash flow

Case Study: DuluxGroup PNG’s Manufacturing Transformation

DuluxGroup PNG faced legacy systems, spreadsheets, and paper-based bottlenecks. Leadership partnered with Coriza to rebuild their operations with Cloud ERP – creating trusted data and connected processes.

The results were immediate:

  • Month-end closed on day one
  • Quotes reduced from nearly a week to 24 hours
  • On-time-in-full delivery rose above 95%
  • Managers could finally make real-time decisions on cash and purchasing

This was not an IT upgrade – it was a complete business transformation.

A Practical Guide for Manufacturing Leaders

That’s why we created Manufacturing at a Crossroads: A Practical Guide to Transformation. Inside, you’ll find:

  • A 7-step roadmap to manufacturing transformation
  • The metrics that matter for protecting margin and cash
  • Guidance on moving from efficiency to AI-powered intelligence
  • Lessons from real manufacturers who have transformed under pressure

The Bottom Line

Manufacturing is no longer about survival, it’s about transformation. Leaders who act now can strengthen resilience, safeguard competitiveness, and position their businesses to grow through disruption.

Start today. Get the clarity and confidence you need to take the first step.

More Resources

From Siloed Systems to Strategic Insights: Empowering Finance Teams with Cloud ERP

From Siloed Systems to Strategic Insights: Empowering Finance Teams with Cloud ERP

by | Mar 31, 2025 | Blog Post, CFO, Cross Industry, Finance Leadership, Financial Controller, Uncategorized

Mid-Market companies operate in an increasingly complex environment. Finance teams in these organisations are often at the epicenter of this complexity, tasked with delivering accurate insights, managing budgets, and ensuring compliance. Yet, their potential to act as strategic partners is often stifled by dated systems that consume excessive resources and hinder agility.

This blog explores how outdated systems impact finance teams and how Cloud ERP can enable them to embrace their role as drivers of business transformation

Access Aberdeen Research Report

Unlocking Finance Excellence: Harnessing Cloud ERP for Mid-market Success. here

The Mid-Market Finance Challenge: Resource Strain and Operational Inefficiency

Finance teams in mid-market companies frequently contend with the limitations of legacy systems. These challenges include:

  • Integration Barriers: Siloed systems lead to fragmented data, requiring manual work to create consolidated reports, often riddled with delays and inaccuracies.
  • Excessive Resource Demands: Maintaining on-premise systems involves IT teams focusing on routine upkeep rather than strategic innovation, leaving finance teams waiting for essential updates or fixes.
  • Limited Scalability: Legacy systems struggle to support the growing complexity of mid-market businesses, particularly during expansions or acquisitions.
  • Manual Processes: Finance teams resort to spreadsheets and manual reconciliations to close gaps left by outdated systems, wasting time and increasing the likelihood of errors.
  • Skill Gaps: Supporting fragmented systems demands diverse technical expertise, often unavailable within mid-market IT teams, leaving finance dependent on external support.

These constraints prevent finance from focusing on value-added activities such as strategic planning, forecasting, and providing actionable insights to leadership.

Why Cloud ERP is a Catalyst for Modern Finance

Cloud ERP systems offer mid-market finance teams a path to efficiency, scalability, and strategic influence. These platforms are designed to address the core limitations of legacy systems. Here’s how they enable transformation:

  1. Data Centralisation: Cloud ERP integrates data across departments, eliminating silos and providing a single source of truth. Finance teams can access real-time, accurate information to make informed decisions.
  2. Automation of Manual Tasks: Processes such as data entry, reconciliation, and reporting are automated, freeing up resources and reducing errors.
  3. Cost Efficiency: By reducing the need for hardware and maintenance, Cloud ERP shifts resources from IT overhead to strategic investments.
  4. Scalable Infrastructure: These systems adapt to growth, supporting acquisitions, new markets, or additional reporting requirements with minimal disruption.
  5. Improved Collaboration: Cloud-based solutions enable seamless communication and data sharing across dispersed teams, empowering finance to work cohesively with other departments.

How Legacy Systems Hinder the Modern Finance Mandate

Modern finance teams are expected to go beyond transactional roles and become strategic partners in driving business outcomes. Legacy systems, however, force them into reactive positions. Here are specific ways in which outdated systems derail the finance function:

1. Inhibited Decision-Making

Without real-time data, finance leaders struggle to provide timely insights to the C-suite. This delay impacts the organization’s ability to respond to market changes or capitalize on emerging opportunities.

2. Compliance Risks

Fragmented systems increase the complexity of adhering to regulatory requirements. Manual reporting and reconciliation processes heighten the risk of non-compliance and potential penalties.

3. Reduced Forecasting Accuracy

Siloed data and reliance on spreadsheets compromise the accuracy of budgeting and forecasting, leading to decisions based on incomplete or outdated information.

4. Resource Misallocation

Time spent troubleshooting system issues or performing manual tasks detracts from higher-value activities like financial modeling and scenario planning.

Steps to Transition Finance Teams from Reactive to Strategic Roles

Mid-market companies can empower their finance teams by adopting Cloud ERP and focusing on the following strategies:

1. Evaluate Current Pain Points

Conduct a thorough review of existing systems and processes. Identify inefficiencies that hinder finance’s ability to deliver timely and accurate insights.

2. Automate Core Processes

Streamline repetitive tasks such as financial close, accounts reconciliation, and regulatory reporting. Automation reduces cycle times and minimizes errors.

3. Enable Real-Time Reporting

Leverage dashboards and analytics tools within Cloud ERP to provide leaders with up-to-date financial insights. This capability is critical for strategic decision-making.

4. Foster Collaboration Across Departments

Break down silos by using Cloud ERP’s collaborative features. Encourage cross-departmental participation in financial planning and analysis.

5. Invest in Training and Upskilling

Ensure your finance team is equipped to maximize the capabilities of Cloud ERP. Training programs should focus on analytics, strategic planning, and scenario modeling.

The ROI of Cloud ERP for Finance

The benefits of Cloud ERP extend beyond operational efficiency to strategic enablement. Here’s how finance teams can drive measurable ROI:

  • Faster Close Cycles: Automating financial close processes reduces timelines from weeks to days.

  • Enhanced Forecasting Accuracy: Centralized data and advanced analytics improve the precision of forecasts.

  • Reduced Compliance Costs: Automated reporting ensures adherence to regulations, avoiding penalties and audits.

  • Increased Strategic Capacity: Freed from manual tasks, finance teams can focus on driving long-term business value.

For mid-market companies, the transition to Cloud ERP represents a transformative opportunity for finance teams. By overcoming the limitations of legacy systems, finance can shift from a transactional to a strategic role, delivering insights that drive growth and resilience.

In an era where agility and data-driven decision-making are critical, Cloud ERP provides the foundation for finance teams to thrive. Start your journey today by evaluating your current systems and envisioning how Cloud ERP can empower your finance team to lead with confidence.

Find Out How Best in-Class Are Surging Ahead

Aberdeen Research’s report “Harnessing Cloud for mid-market Success” is packed full of business case ideas to help you get started. Download your copy here

The Future of Finance: Cloud ERP as the Cornerstone of Transformation

The Future of Finance: Cloud ERP as the Cornerstone of Transformation

by | Dec 19, 2024 | Blog Post, CFO, Finance Leadership, Financial Controller, SAP S/4HANA Cloud

How CFOs Can Leverage Technology to Drive Strategic Growth and Resilience

The finance function is evolving at a breakneck pace. As Anders Liu-Lindberg outlines in his insightful article, “How Should Finance Functions Operate in the Future?”, the role of finance is transforming from a traditional focus on control and compliance to a strategic driver of business growth and resilience. Liu-Lindberg’s perspective highlights how finance must now enable agility, foster collaboration, and deliver actionable insights—all while maintaining robust governance. This shift demands a rethinking of not just roles and processes, but also the technology that underpins them.

In this post, I aim to build on Liu-Lindberg’s themes through the lens of Cloud ERP, specifically SAP S/4HANA Cloud, as an enabler of this transformation. We’ll explore how modern Cloud ERP systems empower CFOs and finance teams to thrive in this new paradigm by driving efficiency, delivering real-time insights, and providing the adaptability required to navigate constant change.

1. Operational Efficiency: Freeing Up Capacity for Strategic Work

Traditional finance functions have long been burdened by transactional tasks such as closing books, reconciling accounts, and managing compliance. While critical, these activities consume significant time and resources that could be better spent on strategic initiatives. Liu-Lindberg underscores the need for finance teams to pivot towards value creation—and this is where Cloud ERP platforms come into play.

Modern Cloud ERP systems, like SAP S/4HANA Cloud, bring automation to the forefront. By leveraging machine learning and robotic process automation (RPA), these platforms can handle repetitive tasks with precision and speed. For instance, SAP’s intelligent technologies automate invoice matching, anomaly detection, and financial reporting, allowing teams to focus on strategic priorities like scenario planning and mergers and acquisitions.

According to McKinsey, automation and digitization can reduce the time finance teams spend on transactional tasks by up to 40%. For CFOs, this isn’t just a time-saving measure; it’s a game-changer that unlocks capacity for strategic work such as embedding ESG metrics into financial strategies or optimizing cash flow in real-time.

2. Real-Time Insights: Enabling Proactive Decision-Making

Liu-Lindberg’s article emphasizes the shift from backward-looking reporting to forward-looking analysis as a cornerstone of the future finance function. This requires technology that can process and analyze data in real-time, providing actionable insights to drive proactive decision-making.

Cloud ERP platforms excel in this area. SAP S/4HANA Cloud, for example, integrates transactional and analytical data into a single platform. This provides CFOs with a unified view of their organization’s financial health—a “single source of truth.” Advanced analytics capabilities enable predictive forecasting, scenario modeling, and instant performance tracking, empowering finance teams to make informed decisions at speed.

Imagine a manufacturing company facing sudden increases in raw material costs. With real-time insights from SAP S/4HANA Cloud, the CFO can immediately model the financial impact, assess inventory levels, and collaborate with procurement to renegotiate contracts or adjust pricing strategies. This agility isn’t just a competitive advantage—it’s a survival mechanism in today’s volatile markets.

3. Adaptability: Thriving in a World of Constant Change

The ability to adapt quickly to changing circumstances is a recurring theme in Liu-Lindberg’s article. Whether it’s responding to regulatory shifts, economic disruptions, or evolving business models, finance functions must operate with agility and resilience.

Cloud ERP platforms are designed with adaptability in mind. Unlike legacy systems, which are often rigid and costly to modify, platforms like SAP S/4HANA Cloud are inherently flexible and scalable. This allows organizations to pivot swiftly when conditions demand it. For instance, SAP’s support for subscription-based billing models enables businesses to explore new revenue streams without overhauling their financial systems.

Moreover, the cloud delivery model ensures continuous updates and compliance with evolving regulations. Quarterly updates to SAP S/4HANA Cloud introduce new features and regulatory tools, ensuring finance teams are always equipped with the latest capabilities. For CFOs navigating complex, multi-jurisdictional operations, this adaptability is invaluable.

From Enabler to Strategic Partner

As Liu-Lindberg rightly points out, the finance function of the future must transcend its traditional role to become a strategic partner to the business. This evolution demands not just a shift in mindset but also a technological foundation that enables the finance team to deliver value at every level.

Cloud ERP platforms like SAP S/4HANA Cloud are more than just tools—they are catalysts for this transformation. By driving efficiency, enabling real-time insights, and supporting adaptability, these platforms position CFOs to lead their organizations through uncertainty and toward sustainable growth.

A Call to Action for CFOs

Liu-Lindberg’s article challenges CFOs to envision a finance function that is dynamic, strategic, and forward-looking. The question is not whether to embrace this vision but how to make it a reality. Technology is the linchpin of this transformation, and Cloud ERP is the foundation upon which the future of finance will be built.

For CFOs evaluating their next steps, I offer this advice: Begin with a clear vision of how your finance function can drive value in the years to come. Then, invest in technology that aligns with that vision. SAP S/4HANA Cloud offers the tools to not only transform finance processes but to reimagine the role of finance within your organization.

The future of finance is here. It’s time to lead the charge.

Discover SAP S/4HANA Cloud

Transform Your Finance Function with Cloud ERP

Start your Journey Today