Written by Takanashi — Paddy & Water Inc. / Finance & Controlling

Controlling: A Complete Guide to Cost Center Accounting, Internal Orders, Product Cost Management, Profitability Analysis, and Profit Center Accounting

June 2026

Chapter 1: Overview of SAP CO and the Universal Journal

Differences in Roles Between CO and FI

SAP FI (Financial Accounting) is accounting record-keeping for “external reporting” (financial statements for tax authorities, shareholders, and creditors). SAP CO (Management Accounting), on the other hand, is a system for “internal management” (analysis of costs and revenues to support decision-making by executives and department heads).

Specific example: An FI journal entry of “a ¥1,000,000 posting to the subcontracted processing cost account” records “how much subcontracted processing cost was incurred,” but it does not show “for which product or which production order that subcontracted processing cost was incurred.” CO manages the reason and destination of the cost by “assigning that same ¥1,000,000 to a specific production order (CO-PC), cost center (CCA), or WBS element (PS).”

FI vs CO in a Nutshell

FI: A record of “what happened” (recording of facts) for external reporting CO: An analysis of “why and where it happened” (analysis of cause and attribution) for internal management In S/4HANA’s Universal Journal (ACDOCA), FI and CO have been unified into a single table.

Universal Journal (ACDOCA): The Integration of FI and CO

The greatest architectural innovation in SAP S/4HANA is the introduction of the “Universal Journal” (universal ledger). Implemented as the ACDOCA table, it unifies the FI and CO journal entries that previously existed separately into a single table.

• Conventional approach (ECC): FI and CO were managed redundantly in separate tables. Periodic reconciliation work was required. The problem of “discrepancies between FI and CO” occurred chronically.

• S/4HANA: A single posting is recorded only once in ACDOCA. From there, views are generated according to each purpose — financial, management, and analytical. Discrepancies between FI and CO are structurally eliminated.

• Each ACDOCA line item: In addition to the G/L account (the financial accounting key), management accounting dimensions such as “cost center, profit center, cost object, profitability segment, and project” are attached, so all costs and revenues are posted to management accounting dimensions in real time as well.

List of CO Sub-components

• CO-OM (Overhead Management): Includes Cost Center Accounting (CCA) and Internal Orders (IO). The focus is on managing overhead costs (manufacturing overhead, SG&A) by organizational unit.

• CO-PC (Product Cost Controlling): Manages product cost planning (standard cost rollup), collection of actual costs by production order, actual costing, and variance analysis. Explained in detail in the separate document “SAP_CO_Product_Cost_Controlling_Guide.docx.”

• CO-PA (Profitability Analysis): Performs profit and loss analysis by “segment,” such as product, customer, and sales region. Explained in detail in the separate document “SAP_CO_Profitability_Analysis_Guide.docx.”

• EC-PCA (Profit Center Accounting): Manages internal profit and loss and balance sheets by business division, product line, and region. Explained in detail in the separate document “SAP_CO_Profitability_Analysis_Guide.docx.”

Basic CO Concepts: Controlling Area

The Controlling Area is the highest-level organizational unit in CO. One or more company codes are assigned to a controlling area, and CO cost allocations and transfers can only be carried out within a single controlling area.

• OK06 (Controlling Area Settings): Sets the controlling area number, name, currency, fiscal year variant, and cost center standard hierarchy.

• OX19 (Assignment of Controlling Area to Company Code): Assigns company codes to a controlling area.

• OKKP (Component Activation): Sets which CO components (CO-PC, CO-PA, CCA, IO, etc.) are activated for each controlling area.

Journal Entry Generation and Workflow Control

As a “management accounting lens,” CO re-aggregates FI’s financial journal entries along management dimensions such as cost center, project, and product. In S/4HANA’s Universal Journal (ACDOCA), the CO-side cost posting is unified into a single record simultaneously with the FI posting.

Type of CO Posting	Content and Linked Journal Entry	Related Tx
Simultaneous FI-CO Posting	When an FI journal entry (expense account) is posted, it is simultaneously posted to the CO cost center/internal order as well (unified via the Universal Journal)	FB01/MIRO/VF01, etc. FI Tx
Allocation Posting (Internal to CO)	Running an allocation cycle (KSV5) posts costs from a sender cost center to a receiver cost center (an internal transfer not accompanied by an actual FI entry)	KSV5 / KSUB
CO-PA Posting	When an SD billing document is created, revenue, cost, and discount amounts are automatically posted to CO-PA (Profitability Analysis)	SD-CO-PA integration setting (KE4I)
Adjustment Posting to FI (Monthly)	Cost adjustment between CO and FI (transaction 1KEI); reflects internal management accounting allocations in the FI reconciliation account	1KEI / KAL1

▌ Workflow: Budget Management and Cost Approval

· Approval of cost center planning: After KP06 (cost planning entry), a process can be set up whereby a supervisor reviews and approves the planned values · Budget overrun warnings and workflow: Budget ceilings are set for internal orders (KO22) and WBS elements (CJ30). When exceeded, the originator and approver are automatically notified · Approval of period-end allocations: Before executing the monthly allocation cycle, the allocation results are displayed as a simulation, and the process is executed for real only after the responsible person approves it

Chapter 2: Cost Center Accounting (CCA: Cost Center Accounting)

What Is a Cost Center?

A cost center is “the location where costs are incurred and a unit of responsibility.” “Manufacturing department, quality control department, general affairs department, IT department, sales department,” and so on are set up as cost centers. All overhead costs (personnel costs, utility costs, depreciation, etc.) are posted to some cost center. The purpose of CCA is “cost management and clarification of responsibility by department” — each department head manages actual costs against the cost plan for their own cost center and bears accountability for explaining variances.

Cost Center Master Data

Operation Image: KS01/KS02/KS03 — Create/Change/Display Cost Center

• Launch KS01 (Create Cost Center). Enter the controlling area, cost center code, and validity start date, then press Enter.

• Basic data: Enter the name, description, the standard hierarchy node it belongs to, the cost center category (manufacturing/service/administration/sales, etc.), the person responsible, and the currency.

• Validity Period: A cost center is master data with a validity period. When an organizational change occurs, a revised version is created with a new validity period. Old data is retained as history.

• OKEON (Cost Center Standard Hierarchy Settings): Organizes cost centers into a tree structure such as “company-wide → business division → plant → manufacturing department → manufacturing section.” Used for hierarchical aggregation and allocation settings.

• KSH1/KSH2 (Cost Center Groups): Defines cross-cutting “groups for analytical purposes” (e.g., direct manufacturing departments, administrative/overhead departments) separately from the standard hierarchy.

Operation Image: KL01/KL02 — Create/Change Activity Type

• KL01 (Create Activity Type): Defines the unit of service provided by a cost center. Examples: “MAH01: Machine hours (unit: h),” “LAB01: Direct labor hours (unit: h),” “SETUP: Setup time (unit: h).”

• Sets the activity type category (1: manual entry, 2: indirect determination, 3: manual allocation, 4: indirect allocation). Activities entered directly via confirmation of PP production orders (CO11N) use category 1.

Cost Planning and Activity Quantity Planning

Operation Image: KP06 — Cost Planning Entry

• Launch KP06 (Primary Cost Element Planning). Specify the version (0), period (1–12), fiscal year, cost center, and cost element (G/L account).

• Enter “fixed planned costs and variable planned costs” on a monthly basis in a grid format. Example: personnel costs ¥2,000,000 (fixed) and supplies expense ¥200,000 (variable) per month.

• Variable costs can also be entered as “cost per unit of activity quantity.” This forms the basis of the “Flexible Budget,” in which the variable cost portion is automatically adjusted when the activity quantity changes.

Operation Image: KP26 — Activity Quantity Planning Entry

• KP26 (Activity Quantity Planning): Enters the “annual planned activity quantity” for each cost center and activity type. Example: Manufacturing Dept. 1, machine hours, planned activity quantity of 6,000 hours/year.

• KSPI (Calculation of Planned Activity Price): The “planned activity price = planned cost ÷ planned activity quantity” is automatically calculated from the planned costs in KP06 and the planned activity quantity in KP26. This price is used in CK11N (standard cost rollup).

Allocation Cycles: Cross-organizational Transfer of Overhead Costs

Costs collected in the cost centers of indirect departments (maintenance, IT, quality control, etc.) are transferred to manufacturing department cost centers or production orders through an “Allocation Cycle.”

Operation Image: KSU1/KSU5 — Setting Up and Executing Assessment Cycles

• KSU1 (Setting Up an Actual Assessment Cycle): Sets the cycle name, validity period, the “sender” (sending cost center), and the “receiver” (receiving cost center/CO-PA segment).

• Allocation Key (Tracing Factor): Selected from fixed percentages (e.g., Dept. A 20% / Dept. B 50% / Dept. C 30%), planned activity quantity ratios, or statistical key figures (headcount, floor space, etc.).

• KSU5 (Execute Actual Assessment): Specifies the plant, period, and cycle name. Confirm the allocation amounts in a test run before executing the actual run.

Operation Image: KSV1/KSV5 — Setting Up and Executing Distribution Cycles

• Distribution posts to the receiver “while retaining the breakdown by cost element (G/L account).” Even at the receiver, the original breakdown by cost element — such as personnel costs, utility costs, and communication costs — can be verified.

• With Assessment, the receiver receives the costs under a single cost element called “allocated overhead” (the breakdown of the original cost items is not visible).

• Selection criteria: Use Distribution when you want to trace costs without losing their nature; use Assessment when a breakdown at the receiver is unnecessary and a simple allocation is sufficient.

Operation Image: KSII — Revaluation at Actual Activity Price

• KSII (Revaluation at Actual Activity Price): Executed as a month-end process. It corrects the difference in activity costs posted to production orders during the month at the planned activity price, using the actual activity price (actual cost ÷ actual activity quantity). This allows the “activity price variance” of production orders to be calculated accurately.

• KSII is executed before CO88 (production order settlement), so that the variance after revaluation can be settled in CO88.

Cost Center Reports and Variance Analysis

Operation Image: KSB1/KSBL — Cost Center Line Item / Balance Reports

• KSB1 (Cost Center Line Item Report): Displays cost line items by specifying the cost center, period, and fiscal year. Can be drilled down by “cost element, document, and posting date.”

• KSBL (Cost Center Balance Report): Displays “planned cost, actual cost, variance, and variance rate (%)” by cost center. If a flexible budget has been set up, the variance between the “activity-adjusted plan” and “actual cost” (input quantity variance) can also be checked.

• S_ALR_87013611 (Cost Center Plan/Actual Variance Analysis): A list of plan/actual variances across multiple cost centers. Used as material for monthly cost management meetings.

Chapter 3: Internal Orders (IO)

Concept and Purpose of Internal Orders

An Internal Order is “a temporary management account, separate from production orders (PP-SFC), for individually collecting the costs of specific projects, campaigns, repairs, capital investments, and the like.” Whereas cost centers collect costs for “permanent organizational units,” internal orders collect costs for “time-limited activities or events.”

Typical uses of internal orders: new product development projects, trade show expenses, minor equipment repairs, plant improvement activities, advertising campaign costs, and vehicle maintenance costs.

Internal Order Master Data and Operations

Operation Image: KO01/KO02/KO03 — Create/Change/Display Internal Order

• Launch KO01 (Create Internal Order). Select the order type (e.g., “9010: Equipment Repair,” “9020: Internal Project,” “9030: Marketing Expense,” etc.) and press Enter.

• Header data: Enter the order name, description, responsible department, cost center (the final destination of the costs), profit center, start date, end date, and budget.

• Status management: The order is managed through the statuses “Created (CRTD) → Released (REL) → Technically Completed (TECO) → Closed (CLSD).” Costs cannot be posted unless the order has been released.

• KO02 (Change Internal Order): Used to change the budget, extend the end date, and approve additional costs.

Operation Image: KO88 — Settlement of Internal Order

• KO88 (Settlement of Internal Order): Settles the costs collected on an internal order to final accounts (cost center, G/L account, CO-PA segment, etc.) based on the configured settlement rule.

• Setting the settlement rule (Settlement Rule tab in KO02): Sets the “settlement receiver (receiver category: CTR = cost center, PA = CO-PA segment, etc.), receiver code, settlement percentage (%), and settlement method (FUL = full amount, PER = periodic).”

• The standard flow is to settle via KO88 after TECO (technical completion). After settlement, the internal order balance becomes zero.

Budget Management for Internal Orders

• KO22 (Internal Order Budget Setting): Sets an “annual budget ceiling” for an internal order. If the budget is exceeded when a cost is posted, a “budget overrun warning” or a “posting block” (depending on the Commitment Accounting configuration) occurs.

• KO2E (Supplement Budget): A transaction for approving additional amounts to cover shortfalls in the original budget. Additional budget is set after going through the approval workflow.

• KOB1/KOB2 (Internal Order Reports): Displays a list of “planned cost, actual cost, variance, and remaining budget” for each order. Serves as the starting point for project cost management.

Chapter 4: Overview of Product Cost Controlling (CO-PC)

Role of CO-PC

Product Cost Controlling (CO-PC) is a function that manages “how much it costs to make a product” through the three cycles of plan, actual, and variance. Its core consists of four functions: “standard costing,” “collection of actual costs on production orders,” “actual costing (Material Ledger),” and “variance analysis.”

For a detailed explanation of CO-PC, please refer to the separate document “SAP_CO_Product_Cost_Controlling_Guide.docx.” Here, as a CO overview, only the positioning of CO-PC and its main transactions are summarized.

Key CO-PC Transactions (Reference List)

• CK11N (Cost Estimate: Standard Cost Rollup): Rolls up the standard cost of a product using the BOM × routing × activity price.

• CK40N (Mass Cost Estimate Run): Runs cost estimates for all materials in a batch. Used when revising standard costs annually.

• CKMVFM (Standard Price Update): Reflects the price from the cost estimate calculated in CK40N into the material master.

• CO88 (Production Order Settlement): At period-end, analyzes and settles the variance between the actual and planned costs of production orders.

• CKMLCP (Actual Costing Run): Executes multi-level rollup of actual costs using the Material Ledger.

Chapter 5: Overview of Profitability Analysis (CO-PA)

Role of CO-PA

Profitability Analysis (CO-PA) is a function that visualizes, by segment, “which products are sold to which customers, in which regions, for how much, and how much profit is made.” It manages contribution margin across multiple dimensions, such as “by product × by customer × by sales channel × by region.”

For a detailed explanation of CO-PA, please refer to the separate document “SAP_CO_Profitability_Analysis_Guide.docx.” Here, only the positioning of CO-PA and its main transactions are summarized.

Key CO-PA Transactions (Reference List)

• KEA0 (Operating Concern Settings): Defines the analysis dimensions of CO-PA (profitability segment characteristics: product group, customer group, sales region, etc.).

• KE21N (CO-PA Manual Entry): Manually posts revenues and costs to a CO-PA segment.

• KE30 (CO-PA Report): Displays a profit and loss statement by profitability segment.

• KE4U (CO-PA: Automatic Posting Settings from SD): Configures automatic posting to a CO-PA segment when an SD billing document is posted.

Chapter 6: Overview of Profit Center Accounting (EC-PCA)

Role of Profit Centers

A Profit Center is CO’s unit for “quasi-divisional management.” By setting up “product divisions, regional divisions, plants,” and so on as profit centers, and managing the revenue, costs, and inventory of each center, a “profit and loss statement by division” and a “pseudo balance sheet by division” are created.

For a detailed explanation of PCA, please refer to the separate document “SAP_CO_Profitability_Analysis_Guide.docx.”

Operation Image: KE51/KE52 — Create/Change Profit Center

• KE51 (Create Profit Center): Sets the profit center code, name, person responsible, and profit center group (standard hierarchy node).

• Assigning profit centers to material masters, cost centers, and fixed assets: By setting the profit center in the MRP view or basic data of each material master, the inventory and cost of goods sold for that material are automatically attributed to the profit center.

• 1KE5 (Profit Center Standard Hierarchy): Organizes all profit centers into a hierarchy of “group → division → center.”

Chapter 7: End-to-End Transaction Operation Guide

Scenario 1: Monthly Cost Center Expense Management Flow

Operation Image: Step 1 — Automatic Posting from FI

• FI postings such as payroll payment (F110), utility invoices (MIRO), and depreciation (AFAB) are automatically posted to cost centers. Because each FI journal entry carries a cost center code, the costs are collected in ACDOCA.

Operation Image: Step 2 — Receiving and Sending Activity Allocations

• KB21N (Direct Activity Allocation): Enters the labor hours when the maintenance department performs equipment repairs for the manufacturing department. “Maintenance dept. CC → Manufacturing dept. CC, machine repair time 3h × planned rate ¥5,000/h = ¥15,000” is calculated automatically.

Operation Image: Step 3 — Executing Period-End Allocation Cycles

• KSU5 (Execute Assessment) / KSV5 (Execute Distribution): At month-end, allocates the costs of indirect departments to manufacturing departments and CO-PA. Performed in the order of test run → production run.

Operation Image: Step 4 — Revaluation of Actual Activity Prices

• KSII: Corrects the planned activity price posted to production orders using the actual price.

Operation Image: Step 5 — Reports and Variance Analysis

• KSB1, KSBL, S_ALR_87013611: Check the cost line items and plan/actual variances by cost center.

Scenario 2: Equipment Repair Cost Management Using Internal Orders

Operation Image: Step 1 — Creating and Releasing the Internal Order

• KO01 (Create Internal Order): Creates a “minor equipment repair” order. The budget is set in KO22 and the order is released in KO02.

Operation Image: Step 2 — Posting Costs

• When issuing the parts used for repair in MM (MIGO: movement type 201), the internal order number is specified as the account assignment object. Outsourced repair costs are posted to the internal order via MIRO.

Operation Image: Step 3 — Settling the Order

• After the repair is completed, TECO (technical completion) is set in KO02. The costs collected are posted to the final account (e.g., the cost center for equipment maintenance expense) via KO88 (settlement).

Chapter 8: SPRO Configuration in Detail

Controlling Area Settings

• OKKP (Controlling Area/Component Activation): Activates the CCA cost center, internal order, CO-PC, and CO-PA components for each controlling area.

• OKEQ (Version Settings): Configures planning versions (0: actual, 1: plan, etc.). Multiple planning scenarios can be managed.

Cost Center Accounting Settings

• OKEON (Cost Center Standard Hierarchy Settings): Defines the standard hierarchy node that contains all cost centers. One standard hierarchy is required per controlling area.

• OKB9 (Account Determination: Default Cost Element): Sets a default cost center for a specific G/L account (cost element). Automatically assigns the cost center for postings that do not explicitly specify one.

Internal Order Settings

• KOT2 (Internal Order Type Settings): Sets the “number range, settlement profile, budget profile, and approval workflow” for each order type.

• OKB2 (Settlement Profile Settings): Defines the settlement execution method (periodic settlement, completion settlement) and the allowable range of receiver categories (cost center, G/L, CO-PA).

CO-PC Settings

• OKKN (Costing Variant Settings): Sets the costing method used in CK11N/CK40N (BOM usage, routing usage, and price source references).

• OPK4 (Costing Collector Profile): Sets, for each production order type, “which CO cost collection object (WBS/internal order/production order, etc.) costs are collected against.”

CO-PA Settings

• KEA0 (Operating Concern): Defines the profitability segment characteristics of CO-PA (product group, customer group, region, sales channel, etc.). Up to 50 characteristics can be set.

• KEQ3 (Profitability Report): Defines the layout (display columns, rows, drill-down dimensions) of CO-PA’s profit and loss report.

Chapter 9: Implementation Case Studies

Case 1: Manufacturing — Visualizing Overhead Costs through Cost Center Restructuring and Activity Allocation

Background and Challenges

At a precision equipment manufacturer with 800 employees, manufacturing overhead (maintenance, quality, logistics) was posted to a single, lump-sum “manufacturing department” cost center. It was impossible to grasp how much overhead each product was consuming, and the accuracy of profitability by product was low.

Redesigning CCA and Establishing Activity Allocation

• Cost centers were separated into “Maintenance Dept. CC,” “Quality Control Dept. CC,” and “Logistics Dept. CC.” Costs are now collected individually for each department.

• Activity types (“machine repair time,” “quality inspection time,” “transport time”) were defined in KL01, and activity allocation to the manufacturing department (KB21N, KSU5) was established.

• The allocation by activity type from each department is reflected on production orders (CO-PC), making the overhead cost breakdown by product visible.

Results

• It became possible to grasp overhead costs by product at the activity-type level, enabling identification of priority targets for overhead cost reduction activities.

• It was discovered that, for three product types, “the ratio of overhead cost to sales was actually twice that of other product types,” which became a basis for decisions on price revisions and product discontinuation.

Case 2: Services — Project-Based Cost Management Using Internal Orders

Background and Challenges

At an IT consulting firm, the costs of multiple internal projects (system development, customer support, internal training, etc.) were posted in a lump sum to the department’s cost center, making profitability by project unclear.

Introducing Project-Based Cost Management Using Internal Orders

• An internal order was created for each project (KO01). The budget was set in KO22, and entry of the internal order number was made mandatory when posting costs.

• The cost consumption status by project is monitored weekly using KOB1 (Internal Order Cost Report).

• After a project is completed, costs are transferred via KO88 to the final cost center (settled to CO-PA for customer-facing projects).

Results

• Plan/actual management by project became possible, enabling early detection of and response to budget overruns.

• The “standard cost for similarly-sized projects” could be calculated from past project performance data, improving estimation accuracy.

Case 3: Multi-Business Company — Visualizing Profit by Product × Customer through CO-PA Implementation

Background and Challenges

At a consumer goods manufacturer selling a wide variety of products through multiple sales channels (direct sales, distributors, EC), while a company-wide profit and loss statement existed, it was unclear “which products, sold through which channels and in which regions, yielded the highest profit margin.”

CO-PA Implementation

• The operating concern was set up in KEA0. Four characteristics were defined as dimensions: “product group, sales channel, customer group, and sales region.”

• Automatic posting to CO-PA upon SD billing document posting was configured via KE4U. Sales revenue, discounts, standard cost, and selling expenses are automatically posted to the profitability segment.

• A drill-down report was set up in KE30, achieving drill-down analysis along two axes: “division → product group → individual product” and “sales channel → customer group → individual customer.”

Results

• It was discovered that “the profit margin of the EC channel was 1.8 times that of distributors,” which became the supporting data for the investment decision to strengthen EC sales.

• It became visible that the discount rate applied to a specific customer group was twice that of other groups, leading to a review of discount policy.

End

What You Can Do with SAP CO — Key Management Accounting Functions and Operations

SAP CO (Controlling) is a module that provides management accounting information to support business decision-making. It has the capability to aggregate and analyze FI’s financial data from multiple angles for management purposes, covering cost centers, internal orders, product costs, profitability analysis, and more.

▌ ① Cost Center Management (CO-CCA)

· Cost allocation to cost centers: Aggregates costs by department, line, and process · Primary and secondary allocation: Automatically distributes common costs (administrative departments) to benefiting departments using allocation rules · Plan vs. actual variance report: Checks the monthly/annual budget comparison at the cost center level · Activity types: Sets machine operating hours and labor unit costs for automatic cost apportionment

▌ ② Internal Orders (CO-OPA)

· Used as a collection unit for projects and specific costs (e.g., trade show expenses, equipment refurbishment) · Setting budget ceilings and automatic warnings/blocking when exceeded · Settlement posting to a cost center or asset upon completion

▌ ③ Product Cost Calculation (CO-PC)

· Standard costing: Rolls up raw materials, labor costs, and manufacturing overhead from the BOM and routing · Actual costing: Aggregates actual costs from the actual quantities consumed on production orders · Variance analysis: Automatically calculates the variance (quantity variance, price variance) between standard cost and actual cost · Cost reports: Cost details by product, by production order, and by process

▌ ④ Profitability Analysis (CO-PA)

· Profit and loss analysis across multiple dimensions, such as product, customer, sales region, and sales channel · Automatically posts revenue, cost, and discount amounts to CO-PA at the time of SD order/billing · Contribution margin report: Displays contribution margin ratio by segment in real time · Plan vs. actual: Variance analysis between budgeted margin and actual margin