IFS Cloud ERP Consulting Services | Data Migration & SCM Expertise
  1. You are here:  
  2. Home
  3. IFS Cloud
IFS-ERP CRIMS customization of IFS Cloud
IFS Cloud ERP consulting partner for rollouts, supply chain, and data governance. Uses tested methods to cut risk and speed implementation
Crystal Reports Roadmap 2025-2026: Reinstatement in 25R2 and Final Removal

Crystal Reports in IFS Cloud

Lifecycle Alert (TL;TR)

Critical Update: Crystal Reports is returning temporarily to bridge the gap for upgrades, but its final removal date is now officially set.

  • 🔴 Reinstatement: Crystal will return in IFS Cloud 25R2 via a Service Update (SU).
  • 🔴 Last Call: It remains available in 26R1 to facilitate upgrades from 25R1.
  • 🔴 Hard Exit: Full removal occurs in 26R2; no support exists beyond 26R1.
  • 🔴 Action: Transition to IFS Cloud Native Reporting (Operational Reporting) is mandatory.

Crystal Reports in IFS Cloud: The Final Roadmap

For many years, Crystal Reports served as a cornerstone for complex layouts and external document generation within the IFS ecosystem. As businesses move toward IFS Cloud, the strategy has shifted toward a more integrated, web-native reporting architecture.

IFS has recently confirmed the revised lifecycle for Crystal Reports integration. This update is vital for customers planning their upgrade path beyond 25R1, as it provides a temporary "grace period" before the technology is retired permanently.

Confirmed Release Schedule

IFS Cloud Release Status of Crystal Reports
25R2 (Service Update) Reinstated. Crystal Reports returns via a Service Update to support current business logic.
26R1 Available. Allows customers to upgrade and maintain reporting continuity during the transition.
26R2 Fully Removed. Not available in this or any future releases.

Planning Your Migration

The reinstatement in 25R2 and 26R1 is not an invitation to stay on Crystal Reports long-term. It is a strategic window provided by IFS to allow organizations to migrate their reporting logic to IFS Cloud Native Reporting.

Once support for 26R1 concludes, the Crystal Reports integration will officially become "End of Life." To avoid operational disruptions, companies must begin re-mapping their document layouts today.

Read our previous technical guide on Crystal Reports Integration.

Frequently Asked Questions

Q: Can I keep my Crystal Reports after 26R2?

A: No. Starting with 26R2, the integration will be entirely removed from the IFS Cloud codebase. Reports will no longer be accessible or executable within the system.

Q: Why is IFS reinstating it in 25R2?

A: To provide a bridge for customers who need more time to upgrade beyond 25R1 without losing their critical operational reporting during the process.

Q: What should I use instead of Crystal Reports?

A: The recommended path is IFS Cloud's native Operational Reporting (Report Designer) and web-based lobbies for data visualization.

Secure Your Reporting Future

Don't wait for 26R2 to fix your reporting strategy. Our consultants specialize in IFS Cloud migration and report redesign.

Request a Migration Audit
Why most IFS Cloud projects fail after Go-Live and how to fix it. A strategic guide for CIOs on shifting from technical delivery to enterprise behaviour change.

The Go-Live Fallacy: Why Your IFS Cloud “Finish Line” Is Actually a Risk Handover

  • IFS Cloud
  • ERP
  • Implementation
  • Go-Live

January 2026 | IFS​-ERP​.Con​sult​ing Strategy Team


Most ERP programmes celebrate go-live like it’s the finish line. The steering committee pops the champagne, the System Integrator closes their tickets, and the project is marked «Green.» In reality, you haven’t finished the job. You have just handed over the risk.

Over the last few weeks, we’ve spoken to organisations that have invested $10m – $100m+ in ERP platforms — and are now quietly battling a different problem:

The Silent Failure

Their people don’t want to use the system. Not because the technology failed, but because adoption was treated as an event, not a strategy.

For IT Directors and CIOs, this is critical. The system is technically stable. The uptime is 99.9%. But business value is flatlining.

What Actually Went Wrong?

  • Governance owned delivery, not outcomes. PMOs measure «On Time, On Budget,» but often dissolve before «Value Realization» begins.
  • Adoption was assumed, not designed. Organizations assume that because IFS Cloud is modern, users will naturally flock to it. They won’t.
  • Training focused on “how”, not “why”. Users are taught which buttons to click, but not why the data matters to the downstream supply chain.
  • Post-go-live support vanished. The expert consultants left just as the reality of the new process hit the shop floor.

Turning the Ship Around: 4 Strategic Pivots

If your ERP is live but value isn’t, the work isn’t finished — it’s just starting. Here is how we turn ERP programmes around.

Reframe the Narrative

Shift from «System Implementation» to Enterprise Behaviour Change. When you frame it as a technical upgrade, you get technical engagement. When you frame it as an operational shift, you get executive buy-in.

Redesign Governance

In an Evergreen environment like IFS Cloud (R1/R2 releases), governance must be perpetual. Assign a Product Owner whose KPI is User Adoption, not just system stability.

Treat Adoption as Risk

Low adoption is a commercial risk, not an HR issue. Track metrics like «Percentage of POs created via automation» and report them to the Board alongside uptime.

Capability After Go-Live

Shift your training budget. Reserve 40% for months 2 – 6. Learning sticks when users are facing real scenarios, not during UAT in a sandbox.

Long-term success isn’t technical. It’s cultural.

If you are looking at your post-go-live landscape and seeing frustration instead of flow, it is time to stop patching the software and start patching the strategy.


Curious how other IFS customers are tackling post-go-live adoption? Let’s compare notes.

Schedule a Strategy Call

Frequently Asked Questions

Adoption often fails because the focus is placed on delivery milestones rather than behavioural change. If training focuses only on «how» to click buttons rather than «why» the process matters, and if support vanishes immediately after Go-Live, users revert to old habits or workarounds like Excel.

Unlike legacy ERPs, IFS Cloud updates twice a year (Releases R1 and R2). «Evergreen Governance» means maintaining a permanent Center of Excellence or Product Owner role to manage these updates, test new features, and drive continuous improvement, rather than dissolving the project team after the initial launch.

We recommend reserving approximately 40% of your training budget for the post-go-live period (Months 2 – 6). Users absorb information best when they are facing real-world scenarios. Heavy front-loaded training in a sandbox environment is often forgotten by the time the system is live.

Move beyond «System Uptime.» Track business value metrics such as the percentage of automated transactions vs. manual interventions, the time to complete key workflows, or the reduction in offline spreadsheets. These indicators reveal whether the system is actually being used to perform or just to comply.
The Architect’s Dilemma: Balancing Innovation and Governance in IFS Cloud

The Architect’s Dilemma: Balancing Innovation and Governance in IFS Cloud

Introduction

In the fast-paced world of enterprise resource planning, IFS Cloud stands out for its agility and continuous innovation. However, architects tasked with implementing and maintaining the system face a significant challenge: balancing the need for customization with the imperative of governance. The Evergreen model of IFS Cloud, with its bi-annual updates, forces architects to confront this dilemma head-on. Customizations that once remained untouched for years now face scrutiny every six months, turning technical debt from a theoretical concern into an immediate risk.

The Evergreen Reality: A Double-Edged Sword

IFS Cloud’s Evergreen model is designed to keep organizations at the cutting edge, delivering new features and improvements twice a year. While this ensures businesses can leverage the latest advancements, it also means that every customization — no matter how small — must be re-evaluated with each update. What was once a «set and forget» modification in older versions like IFS Applications 9 or 10 now requires ongoing attention. The consequence of weak governance isn’t just inefficiency; it’s the potential for complete paralysis during upgrades.

The Tiered Governance Model: A Structured Approach

To navigate this challenge, architects must move beyond the traditional «Standard vs. Custom» binary. The Tiered Governance Model provides a framework for managing customizations based on their risk and impact. This model categorizes modifications into three tiers, each with its own governance rules and scrutiny levels:

  • Tier 1: Low-Code/No-Code Configurations – Changes made through Page Designer, Custom Fields, Events, Lobbies, and Automation Workflows. While these modifications are generally «upgrade-safe,» they introduce significant data risks if left unchecked. Every custom attribute must undergo a Data Impact Assessment to determine ownership, regulatory requirements, and inclusion in the Data Warehouse.
  • Tier 2: Extend on the Outside – Extensions built using REST APIs in platforms like Boomi, Azure, or Mendix. These integrations offer high flexibility with low core risk but require governance to ensure API Contract Stability. Only public and supported APIs should be used to avoid disruptions.
  • Tier 3: Extend on the Inside – Modifications to Projections, Logical Units (LUs), or underlying business logic. These high-risk changes should be a last resort and must be developed within the IFS Lifecycle Experience (LE) with mandatory automated test scripts.

Operationalizing Governance: From Theory to Practice

Governance isn’t effective if it’s not enforced. To operationalize the Tiered Governance Model, architects must embed governance into every stage of the development lifecycle:

  • Configuration Change Control Board (CCB) – Evaluates the method of implementation for customizations, ensuring every change aligns with architectural best practices.
  • Lifecycle as the Enforcer – IFS Build Place pipelines should act as the «governance sheriff,» blocking merges that lack associated documentation or fail static code analysis. If governance artifacts are missing, the build fails — no exceptions.
  • Expiration Date Strategy – Every customization should have a review date. Aggressive pruning of outdated customizations is essential to prevent technical debt from accumulating.

The Architect’s Bottom Line: Stewardship Over Speed

The role of an architect in IFS Cloud is not just to enable innovation but to ensure that innovation is sustainable. This requires a shift in mindset: from seeing governance as a barrier to recognizing it as the foundation of a resilient system. By defining ownership, lifecycle, and validation rules before a single line of code is written, architects can transform IFS Cloud from a fragile house of cards into a robust, evolving platform.

Action Plan: What You Can Do Today

  • Audit your customizations and document ownership, purpose, and review dates for each.
  • Enforce Data Impact Assessments for all custom attributes.
  • Lock down APIs to public, supported interfaces only.
  • Automate governance by configuring pipelines to block non-compliant merges.
  • Schedule regular reviews and retire obsolete customizations.
  • Train your team on governance responsibilities to ensure everyone understands the rules.

Conclusion

The next IFS Cloud update is always around the corner. By implementing a Tiered Governance Model and embedding governance into the development lifecycle, architects can ensure their customizations are ready for the future. Governance is not about saying «no» but about saying «do it right.»

Frequently Asked Questions

What is the Evergreen model in IFS Cloud?

The Evergreen model in IFS Cloud refers to the bi-annual updates that deliver new features and improvements. This model ensures organizations stay current with the latest advancements but requires ongoing evaluation of customizations to avoid technical debt and upgrade issues.

What is the Tiered Governance Model?

The Tiered Governance Model is a structured approach to managing customizations in IFS Cloud. It categorizes modifications into three tiers based on risk and impact: Tier 1 (Low-Code/No-Code Configurations), Tier 2 (Extend on the Outside), and Tier 3 (Extend on the Inside). Each tier has specific governance rules to ensure sustainability and compliance.

Why is governance important in IFS Cloud customizations?

Governance is crucial in IFS Cloud customizations to prevent technical debt, ensure compliance, and maintain system integrity. Without proper governance, customizations can become liabilities, hindering upgrades and increasing risks.

What is a Data Impact Assessment?

A Data Impact Assessment is a mandatory evaluation for all custom attributes in IFS Cloud. It determines data ownership, regulatory requirements, and whether the data should be included in the Data Warehouse. This assessment ensures that customizations are documented and compliant.

How can architects enforce governance in IFS Cloud?

Architects can enforce governance by embedding it into the development lifecycle. This includes using a Configuration Change Control Board (CCB) to evaluate implementation methods, automating governance through pipelines, and scheduling regular reviews to retire obsolete customizations.

What is the role of the Configuration Change Control Board (CCB)?

The CCB evaluates the method of implementation for customizations, ensuring they align with architectural best practices. It approves or rejects changes based on their potential risks and compliance with governance rules.

What is the Expiration Date Strategy?

The Expiration Date Strategy involves assigning review dates to all customizations. This ensures that workarounds or temporary solutions are retired when they become obsolete, preventing the accumulation of technical debt.

How can organizations prepare for IFS Cloud updates?

Organizations can prepare for IFS Cloud updates by auditing customizations, enforcing Data Impact Assessments, locking down APIs to public and supported interfaces, automating governance through pipelines, and training teams on governance responsibilities.

A detailed guide on implementing centralized purchasing in IFS Cloud, including technical prerequisites, workflow automation, and integration with Data Mesh for real-time data synchronization.

Mastering Centralized Purchasing in IFS Cloud: Strategic Implementation Guide

  • IFS Cloud
  • Purchasing
  • Demand
  • Delivery

Core Concept: Consolidate Demand, Decentralize Delivery

Centralized purchasing separates the transactional flow (ordering) from the physical flow (delivery):

  • Transactional Flow: Local purchase requisitions are consolidated into a single Purchase Order (PO) by a central purchaser. This PO is issued to the supplier as a unified order.
  • Physical Flow: The supplier delivers goods directly to the demand site, eliminating internal inventory transactions and reducing logistical complexity.

Key Benefit: No internal inventory transactions are required between the demand site and the ordering site, as receipt and arrival registration occur at the demand site.

Strategic Configuration and Prerequisites

To implement centralized purchasing effectively, enforce the following data consistency rules:

1. Purchase Part Standardization

All sites must use identical:

  • Part Numbers: Ensure the same part number is used across all locations.
  • Unit of Measure (UoM): Standardize the purchase UoM and conversion factors to inventory UoM.
  • Catalog Alignment: The central purchasing site’s catalog must include all parts from demand sites.

Failure to standardize: Leads to order errors, delayed deliveries, and increased operational costs.

2. Site Basic Data Setup

Configure site-level rules to define interactions between central and local entities:

  • Validity Periods: Define time intervals for default purchasing sites.
  • Pricing Logic: Choose whether prices are fetched from the Purchasing Site (PO Header) or Demand Site (PO Line).
  • Strategic Note: Using «Demand Site» pricing simplifies part administration by limiting basic data setup to the demand site.

Operational Workflow

From Requisition to Order

The transition from local requisition to central order can be automated or manual:

  • Automatic Detection: The «Central Order» option is enabled automatically if the demand site has valid centralized basic data.
  • Manual Selection: Buyers can manually select the central order option and specify the site and part pricing method.
  • Consolidation: Buyers can add lines to existing POs, converting normal POs to centralized POs.

Receipt and Arrival

Receipt and arrival registration are handled entirely by demand sites:

  • No central action is required for part arrivals.
  • Inventory transactions are recorded locally as usual.
  • For direct customer deliveries, the end customer’s address is saved on the PO line, and the process is managed by the demand site.

Risk Mitigation and Data Integration

Data Consistency Risks

Inconsistent part data across sites can disrupt centralized purchasing. Mitigate risks by:

  • Conducting a pre-implementation audit of part numbers, UoM, and catalogs.
  • Using Data Mesh and OData projections for real-time data synchronization.

Testing Scenarios

Before go-live, test the following scenarios:

  • Multi-site orders to a single supplier.
  • Direct deliveries to end customers.
  • Manual override of automated central order detection.

Frequently Asked Questions (FAQ)

How does the system determine the price for a centralized order?
A centralized order retrieves price-related information from either the Purchasing Site (PO Header) or the Demand Site (PO Line), based on configuration.
Are internal inventory transactions required between the central site and local sites?
No. Receipt and arrival registration at the demand site eliminate the need for internal inventory transactions.
What happens if centralized basic data is missing during requisition conversion?
The «Central Order» option will not enable automatically. However, buyers can manually select it and specify part pricing and site details.
Must part numbers be identical across all sites?
Yes. Parts must have the same number, UoM, and conversion factors across all sites to ensure seamless processing.
How can Data Mesh improve centralized purchasing?
Data Mesh enables real-time data synchronization across decentralized locations, ensuring consistency and reducing errors in multi-site procurement.

Implementation Checklist

Use this checklist to ensure a successful centralized purchasing implementation:

  1. Audit part numbers, UoM, and catalogs for consistency across all sites.
  2. Configure validity periods and pricing logic for each site.
  3. Test automated and manual central order processes.
  4. Simulate direct deliveries to end customers.
  5. Integrate Data Mesh for real-time data synchronization (if applicable).
  6. Train procurement teams on new workflows and error handling.

Key Performance Indicators (KPIs)

Measure the success of your centralized purchasing implementation with these KPIs:

  • Reduction in the number of purchase orders by X%.
  • Decrease in order processing time by Y days.
  • Cost savings from bulk purchasing and improved supplier terms.
  • Reduction in order errors and delivery delays.

Centralized Purchasing FAQ

How does the system determine the price for a centralized order?

A centralized order retrieves price-related information from either the Purchasing Site (PO Header) or the Demand Site (PO Line). This depends entirely on your specific configuration preferences for pricing logic.

Are internal inventory transactions required between the central site and local sites?

No. One of the key benefits of this model is that receipt and arrival registration occur directly at the demand site, effectively eliminating the need for complex internal inventory transactions.

What happens if centralized basic data is missing during requisition conversion?

The system is designed for safety; the «Central Order» option will not enable automatically if data is missing. However, buyers can intervene by manually selecting the option and specifying the necessary part pricing and site details.

Must part numbers be identical across all sites?

Yes, this is a strict prerequisite. For seamless processing, parts must share the same Part Number, Unit of Measure (UoM), and conversion factors across all participating sites.

How can Data Mesh improve centralized purchasing?

Data Mesh architecture facilitates real-time data synchronization across decentralized locations. This ensures consistency (e.g., matching part numbers) and significantly reduces errors inherent in multi-site procurement strategies.

New Purchasing Functionality in IFS Cloud 25R2

New Purchasing Functionality in IFS Cloud 25R2

  • IFS Cloud
  • Purchasing

In the complex ecosystem of Enterprise Resource Planning (ERP), the disconnect between maintenance operations and procurement has traditionally been a source of friction. For organizations in asset-intensive industries such as aerospace, defense, automotive, and heavy manufacturing , the need to acquire materials is often triggered directly by a maintenance event. Historically, linking these work tasks to the appropriate procurement vehicle, especially for non-standard scenarios such as borrowed or exchanged parts, required manual workarounds, spreadsheets, and disconnected communication.

With the release of IFS Cloud 25R2, this operational silo is effectively dismantled. The update introduces a robust integration between Work Orders, Work Tasks, and Procurement processes. This «Flexible Procurement Handling» capability empowers organizations to manage the entire lifecycle of an item — from the initial requirement on a shop floor to the final return of a loaned component — within a single, unified digital environment. This shift is not merely a functional update; it represents a strategic move towards a more responsive and data-driven supply chain.

The Core Evolution: Flexible Procurement Handling

The standout feature of the 25R2 update is the ability to connect Work Tasks directly with advanced procurement options. Previously, a technician or planner identifying a material need often had limited options within the maintenance interface, sometimes necessitating a switch to a separate purchasing module to handle complex requests.

Now, by adding a material line to a Work Task and selecting Purchase Order as the Supply Code, users unlock a suite of sophisticated sourcing methodologies. This integration ensures that the intent of the maintenance activity is perfectly preserved in the purchasing execution, enhancing data governance and reducing the risk of administrative errors.

Expanded Supply Codes: Beyond Standard Purchasing

IFS Cloud 25R2 democratizes access to complex purchasing types directly from the maintenance workflow. The «Purchase Order» supply code now acts as a gateway to four distinct procurement logic flows:

  • Regular Purchase: The standard acquisition model for parts or materials intended for consumption or inventory replenishment.
  • Exchange Order: A critical function for industries managing rotables. It streamlines the process of sending out a core part and receiving a serviceable unit, ensuring accurate cost tracking and inventory adjustments.
  • Repair Order: Facilitates the external service process by sending unserviceable parts to a supplier for repair and subsequent return, maintaining traceability throughout the external loop.
  • Borrow Order: Perhaps the most significant addition for short-term operational flexibility. It handles the temporary acquisition of supplier-loaned parts, automatically configuring ownership settings and serial tracking to prevent these assets from being mistakenly absorbed into general inventory.

Streamlined Returns and Closed-Loop Logistics

One of the most persistent challenges in Supply Chain Management (SCM) is the «reverse logistics» of loaned or exchanged parts. In previous iterations, returning a borrowed item often required manually creating a new Purchase Order or Return Material Authorization (RMA), a process prone to data entry errors and delays.

IFS Cloud 25R2 addresses this with a dedicated Returns tab within the Work Task interface. This feature is supported by a guided assistant that:

  1. Automates Data Entry: Automatically applies shipment details to selected material lines, ensuring the return matches the original receipt.
  2. Triggers Backend Transactions: eliminating the need for manual PO creation or separate receipt processing.
  3. Ensures Traceability: Maintains a digital thread from the moment the part was borrowed to the moment it leaves the facility, a crucial capability for compliance and auditability in regulated sectors.

Conclusion

The enhancements in IFS Cloud 25R2 transform purchasing from a transactional back-office function into a strategic enabler of maintenance efficiency. By embedding sophisticated supply logic directly into the Work Task, IFS Cloud reduces manual effort, sharpens financial accuracy, and fosters stronger, more transparent relationships with suppliers.

IFS Cloud continues to evolve to improve efficiency and flexibility in work management and procurement. In many industries, companies often need materials or parts temporarily or source them from external suppliers. Previously, linking work tasks to procurement, especially for borrowed or supplier-loaned items, required manual workarounds and raised the risk of errors.

Now, IFS Cloud supports seamless integration between work orders, work tasks, and procurement processes. This allows organizations to flexibly decide how to source items and efficiently manage the return or purchase of loaned materials. These changes reduce manual work, ensure accurate financial handling, and build stronger supplier relationships.

IFS Cloud eliminates the operational disconnect between work management and procurement. Previously, linking maintenance tasks to procurement, especially for temporary, borrowed, or externally repaired materials, required manual workarounds. This led to errors, task delays, and complex financial tracking due to reliance on spreadsheets and limited visibility.

Now, IFS Cloud offers a fully integrated procurement workflow. Flexible Procurement Handling connects Work Tasks directly with procurement options. This allows organizations to manage the entire lifecycle of items, from simple purchases to complex supplier loans, within a single environment.

Key benefits include flexibility, as you can execute multiple procurement methods directly from the work task. It improves efficiency by reducing manual effort and eliminating workarounds. Accuracy is enhanced through precise cost tracking and streamlined financial follow-up. It also strengthens control over supplier relationships and inventory management.

The process starts by adding a material line to a Work Task and selecting «Purchase Order» as the Supply Code. This unlocks options like Regular Purchase, Exchange Order, Repair Order, and Borrow Order.

Regular Purchase is used for standard acquisition of parts or materials. Exchange Order manages cost-effective part exchanges with suppliers and ensures financial and inventory accuracy. Repair Order initiates external service processes for unserviceable parts and tracks their return. Borrow Order handles the temporary acquisition of supplier-loaned parts, with automatic ownership settings and serial tracking.

For supplier-loaned parts, IFS Cloud simplifies the return process. Users initiate returns directly from the Work Task’s «Returns» tab. A guided assistant ensures fast and accurate data entry by applying shipment details to all selected lines. The system automates backend transactions, eliminating manual PO creation and receipt processing and ensuring full traceability.

This functionality transforms disjointed workflows into a unified, controlled process. It reduces manual effort, minimizes errors, and provides end-to-end visibility from task initiation to procurement and inventory updates. The result is operational flexibility, precise financial control, and stronger supplier collaboration across industries like aerospace, automotive, and heavy equipment.

Details in the following PDF file: Download IFS-ERP_Consulting_Integrated_Work_Procurement

In the complex ecosystem of Enterprise Resource Planning (ERP), the disconnect between maintenance operations and procurement has traditionally been a source of friction. For organizations in asset-intensive industries such as aerospace, defense, automotive, and heavy manufacturing, the need to acquire materials is often triggered directly by a maintenance event. Historically, linking these work tasks to the appropriate procurement vehicle, especially for non-standard scenarios such as borrowed or exchanged parts, required manual workarounds, spreadsheets, and disconnected communication.

With the release of IFS Cloud 25R2, this operational silo is effectively dismantled. The update introduces a robust integration between Work Orders, Work Tasks, and Procurement processes. This «Flexible Procurement Handling» capability empowers organizations to manage the entire lifecycle of an item — from the initial requirement on a shop floor to the final return of a loaned component — within a single, unified digital environment. This shift is not merely a functional update; it represents a strategic move towards a more responsive and data-driven supply chain.

The Core Evolution: Flexible Procurement Handling

The standout feature of the 25R2 update is the ability to connect Work Tasks directly with advanced procurement options. Previously, a technician or planner identifying a material need often had limited options within the maintenance interface, sometimes necessitating a switch to a separate purchasing module to handle complex requests.

Now, by adding a material line to a Work Task and selecting Purchase Order as the Supply Code, users unlock a suite of sophisticated sourcing methodologies. This integration ensures that the intent of the maintenance activity is perfectly preserved in the purchasing execution, enhancing data governance and reducing the risk of administrative errors.

Expanded Supply Codes: Beyond Standard Purchasing

IFS Cloud 25R2 democratizes access to complex purchasing types directly from the maintenance workflow. The «Purchase Order» supply code now acts as a gateway to four distinct procurement logic flows:

  • Regular Purchase: The standard acquisition model for parts or materials intended for consumption or inventory replenishment.
  • Exchange Order: A critical function for industries managing rotables. It streamlines the process of sending out a core part and receiving a serviceable unit, ensuring accurate cost tracking and inventory adjustments.
  • Repair Order: Facilitates the external service process by sending unserviceable parts to a supplier for repair and subsequent return, maintaining traceability throughout the external loop.
  • Borrow Order: Perhaps the most significant addition for short-term operational flexibility. It handles the temporary acquisition of supplier-loaned parts, automatically configuring ownership settings and serial tracking to prevent these assets from being mistakenly absorbed into general inventory.

Streamlined Returns and Closed-Loop Logistics

One of the most persistent challenges in Supply Chain Management (SCM) is the «reverse logistics» of loaned or exchange parts. In previous iterations, returning a borrowed item often required manually creating a new Purchase Order or Return Material Authorization (RMA), a process prone to data entry errors and delays.

IFS Cloud 25R2 addresses this with a dedicated Returns tab within the Work Task interface. This feature is supported by a guided assistant that:

  1. Automates Data Entry: Automatically applies shipment details to selected material lines, ensuring the return matches the original receipt.
  2. Triggers Backend Transactions: eliminating the need for manual PO creation or separate receipt processing.
  3. Ensures Traceability: Maintains a digital thread from the moment the part is borrowed to the moment it leaves the facility, a crucial capability for compliance and auditability in regulated sectors.

Conclusion

The enhancements in IFS Cloud 25R2 transform purchasing from a transactional back-office function into a strategic enabler of maintenance efficiency. By embedding sophisticated supply logic directly into the Work Task, IFS Cloud reduces manual effort, sharpens financial accuracy, and fosters stronger, more transparent relationships with suppliers.

Frequently Asked Questions

Q: What is the key purchasing improvement in IFS Cloud 25R2 regarding Work Tasks?

A: The key improvement is the direct integration of procurement options within Work Tasks. Users can now select «Purchase Order» as a Supply Code to access flexible sourcing options like Regular Purchase, Exchange Order, Repair Order, and Borrow Order directly from the maintenance interface.

Q: How does the «Borrow Order» supply code function in IFS Cloud?

A: The «Borrow Order» supply code allows organizations to handle the temporary acquisition of parts loaned from suppliers. It automatically manages ownership settings and tracks serial numbers, ensuring that loaned items are distinguished from company-owned inventory throughout their lifecycle. 

Q: Does IFS Cloud 25R2 support the return of supplier-loaned parts?

A: Yes, IFS Cloud 25R2 simplifies this process significantly. Users can initiate returns directly from the «Returns» tab of a Work Task. A guided assistant populates shipment details and automates backend transactions, removing the need for manual Purchase Order creation.

Q: Which industries benefit most from the new Work Task procurement integration?

A: Industries with heavy maintenance and repair operations, such as aerospace, automotive, and heavy equipment, benefit most. These sectors frequently rely on exchanging, repairing, or borrowing high-value components, and the new integration streamlines these complex logistical flows.

IFS Group Consolidation

IFS Group Consolidation: Stop Spreadsheet Chaos and Consolidate with Confidence

If your organization operates across multiple offices, currencies, or frequently changing structures, you’re likely familiar with the challenges of financial consolidation. Piecing together data from disparate systems, tracking ownership, converting currencies, and hunting for errors can turn the close process into a nightmare. IFS Group Consolidation changes that by automating the entire process, giving you accuracy, speed, and peace of mind.

Why Spreadsheets Fall Short

Many finance teams still rely on spreadsheets for consolidation. While spreadsheets are flexible, they’re also error-prone, time-consuming, and difficult to audit. Manual processes, such as FX translations, intercompany matching, and equity tracking, consume valuable time that could be spent on strategic analysis. Research shows that organizations using spreadsheets for consolidation spend up to 50% of their close time on manual work — time that could be better spent driving business insights.

How IFS Group Consolidation Transforms Financial Reporting

1. One Unified System for All Your Data

IFS Group Consolidation brings all your financial data into a single, unified system. No more jumping between tools or reconciling disparate sources. With everything in one place, you gain a comprehensive view of your financial position and can easily drill down into the details.

2. Seamless Multi-Currency and Multi-System Support

Operating across borders means dealing with multiple currencies and accounting standards. IFS Group Consolidation automatically converts and translates financial data, ensuring consistency and accuracy in your consolidated reports. Whether you’re dealing with EUR, USD, or JPY, the system handles it all — eliminating manual FX calculations and reducing the risk of errors.

3. Automation of Repetitive Tasks

Intercompany transactions, ownership adjustments, and eliminations are some of the most tedious aspects of consolidation. IFS Group Consolidation automates these processes, freeing your team from manual work and allowing them to focus on higher-value activities. The result? Faster closes and fewer errors.

4. Customizable Views for Different Stakeholders

Different stakeholders require different perspectives on the data. IFS Group Consolidation lets you create tailored reports for auditors, leadership, and other teams, all from the same underlying data. This ensures consistency and eliminates the risk of discrepancies between reports.

5. Full Audit Trail for Compliance and Confidence

Transparency is critical in financial reporting. IFS Group Consolidation provides a complete audit trail, allowing you to trace every number back to its source. This not only simplifies compliance but also gives CFOs and controllers the confidence that their reports are accurate and reliable.

The Real-World Impact

Organizations that switch to IFS Group Consolidation typically see a 30 – 50% reduction in close times. By automating manual processes and eliminating spreadsheet errors, finance teams can shift their focus from data collection to strategic analysis. Whether you’re managing growth, navigating M&A, or simply looking to streamline your close process, IFS Group Consolidation delivers measurable results.

Is IFS Group Consolidation Right for You?

If you’re tired of closing in Excel or struggling with the complexities of multi-entity consolidation, it’s time to explore a better solution. IFS Group Consolidation is designed for organizations that need:

  • Automated intercompany eliminations and adjustments
  • Seamless handling of multiple currencies and accounting standards
  • A full audit trail for compliance and transparency
  • Customizable reporting for different stakeholders
  • Faster, more accurate financial closes

What’s Your Biggest Consolidation Challenge?

Every organization faces unique consolidation challenges. For some, it’s FX translations. For others, it’s intercompany matching or equity tracking. Whatever your pain point, IFS Group Consolidation can help. By automating the boring stuff, you can spend less time on spreadsheets and more time on what truly matters — driving your business forward.

Ready to Make the Switch?

If you’re ready to leave spreadsheet chaos behind and consolidate with confidence, reach out to our experts. We’ll show you how IFS Group Consolidation can transform your financial reporting process.

Frequently Asked Questions

What is IFS Group Consolidation?

IFS Group Consolidation is a financial consolidation solution designed for organizations with multiple entities, currencies, or accounting systems. It automates intercompany transactions, currency conversions, and reporting, providing a unified view of financial data and reducing reliance on spreadsheets.

How does IFS Group Consolidation handle multiple currencies?

The system automatically converts and translates financial data across different currencies, ensuring consistency and accuracy in consolidated reports. This eliminates manual FX calculations and reduces errors.

Can IFS Group Consolidation manage intercompany transactions?

Yes. IFS Group Consolidation automates intercompany eliminations and adjustments, ensuring transactions are accurately matched and reconciled without manual intervention.

What are the benefits of using IFS Group Consolidation over spreadsheets?

IFS Group Consolidation reduces close times by 30 – 50% by automating repetitive tasks like data aggregation, currency conversion, and intercompany matching. It also provides a full audit trail, improving transparency and compliance.

How does IFS Group Consolidation support audit requirements?

Every number in IFS Group Consolidation can be traced back to its source, providing a complete audit trail. This ensures compliance and gives CFOs and controllers confidence in the accuracy of their financial reports.

Is IFS Group Consolidation suitable for organizations with complex structures?

Absolutely. The system is designed to accommodate dynamic organizational structures, including mergers and acquisitions (M&A) activity, multiple subsidiaries, and shifting ownership. It adapts to your needs without requiring manual reconfiguration.

How can IFS Group Consolidation improve financial reporting for leadership and auditors?

IFS Group Consolidation allows you to create customized views for various stakeholders, including leadership and auditors, from a single data set. This ensures consistency and eliminates discrepancies between reports.

  1. How can leaders help teams connect their daily work to a larger purpose or mission?
  2. How do you balance accountability with team morale when enforcing these strategies?
  3. What concrete strategies can replace hope in ERP upgrade planning?
  4. What’s the fastest way to assess whether business users are truly prepared for an ERP upgrade?

Page 1 of 6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • Home
  • Offer
  • IFS Cloud
  • Data Governance
  • Contact
  • Implementation of IFS Cloud Data Mesh
  • Downloads
    • IFS OData Excel Client
  • Innovations
  • Business Process Optimisation