Home / Field Notes

IFS

IFS and SAP Share the Same Cost Accounting Tradition

The SAP CO module and the IFS Code String architecture grow from the same cost accounting root. How their concepts map to each other, and the key architectural difference between the two ERPs.

Product
IFS Applications 7–10
Level
Intermediate
Reading
~4 min

From the outside, IFS and SAP look like two very different ERPs. Yet their financial sides lead back to the same place: the tradition of corporate cost accounting.

Common root: corporate cost accounting

From the 1980s on, three core concepts became standard in large enterprise ERPs:

  • Account
  • Cost Center
  • Cost Element

The SAP CO module set the standard

SAP made this highly systematic under the CO (Controlling) module. In the SAP R/2 and later SAP R/3 era, the following concepts became the de facto standard in the enterprise ERP world:

  • Cost Center
  • Cost Element
  • Internal Order
  • Profit Center
  • Activity Type

SAP’s CO module was influential enough to define the language of this field across the ERP industry.

IFS started from the same principles

IFS was founded in Sweden in 1983. It was initially strong in maintenance management (EAM), manufacturing and project management. When building its financial structure, it used the same academic and industrial cost accounting principles as SAP.

Concept mapping

This common origin creates a striking overlap between the two systems’ concepts:

SAP IFS
Cost Center Cost Center (Code Part B)
Cost Element Cost Element (Code Part C)
Internal Order Project / Activity
Profit Center Function Group / Profit Center
CO Reporting Analysis Reporting

Architectural difference: FI + CO versus Code String

Although the concepts overlap, the architectures differ.

In SAP there is a split between FI and CO: financial accounting (FI) and cost accounting (CO) are separate modules.

In IFS, on the other hand, there is the Code String logic. The account and analysis dimensions are not embedded inside a single code; they are carried as separate code parts on the same accounting line:

Account (A)        770
Cost Center        PRD-01
Project            P-2026-14
Object             LINE-03

What each code part (B–J) represents is defined per company. The cost element, in turn, is mostly derived from the account through mapping. As a result, account, cost center and project information are held on a single accounting line at the same time, in independent fields.

Assessment

In my view, this is IFS’s greatest strength.

What many local ERPs are trying to bolt on today under the name “analytical accounting”, IFS had already solved in the 1990s.

SAP is a registered trademark of SAP SE; IFS and IFS Applications are registered trademarks of IFS AB. This note is an independent assessment.