SAP · 2 min read

SAP CO-PA: Account-Based vs Costing-Based Profitability Analysis

Two ways to see profitability by product, customer and region, what changed in S/4HANA, and what it takes for SD data to flow correctly into CO-PA.

SAP CO-PA (Profitability Analysis) is the controlling component that analyses profit by market segment: product, customer, region and sales channel. Accounting tells you the total profit; CO-PA shows where it comes from and where it is lost.

Characteristics and value fields

CO-PA rests on two concepts. Characteristics are the dimensions of analysis: customer, material, product group, country, sales organisation. Value fields are the amounts measured: gross sales, discounts, freight, cost of goods sold, contribution margin. Good CO-PA design starts with choosing characteristics that answer the questions management actually asks.

Costing-based vs account-based: what is the difference?

  • Costing-based CO-PA: values are stored in dedicated tables, split into value fields. It gives an immediate margin at the time of sale using standard cost, but reconciling with accounting takes extra effort.
  • Account-based CO-PA (Margin Analysis): values are stored by G/L account in the accounting document itself. It always reconciles with accounting; the level of detail depends on the chart of accounts design.

What changed in S/4HANA?

In S/4HANA, accounting and controlling data were merged into a single line-item table (ACDOCA). Account-based profitability analysis became a natural part of this structure and is SAP's recommended approach. Costing-based CO-PA is still available on-premise, but in new projects the reason for choosing it should be clearly documented. Features such as splitting cost of goods sold into its components largely close the old gaps of the account-based approach.

Getting SD data into CO-PA correctly

  1. Pricing lines: every condition type must go to the right account and value field. That link is built in the pricing procedure and account determination.
  2. Cost: cost of goods sold arises at goods issue and should be consistent with the statistical cost line on the invoice.
  3. Characteristic derivation: characteristics such as product group and region should be derived automatically from master data; manual entry means wrong reports.
  4. Freight and insurance: tracking them separately in exports makes export profitability visible.

Common mistakes

  • Defining too many characteristics until reports become unreadable
  • Lumping discounts and freight into a single value field
  • Leaving fields such as product group or region empty in master data
  • Presenting CO-PA reports to management without reconciling them with accounting

From profitability report to decision

The value of CO-PA lies in reports that lead to decisions: spotting loss-making product–customer combinations, fixing discount policy, re-pricing markets with high freight costs. That is why the design should be done with finance and sales management, not by the technical team alone. In SAP SD and CO-PA consulting, the first question is always: "Which decision do you want to make better?"

Frequently asked questions

Can costing-based CO-PA be used in S/4HANA?

Costing-based CO-PA is still available in on-premise S/4HANA, but SAP's recommended approach, integrated with ACDOCA, is account-based profitability analysis (Margin Analysis).

Why doesn't my CO-PA report match accounting?

In costing-based CO-PA values are stored in separate tables at standard cost, so differences can arise. Missing account-to-value-field mappings and empty characteristics are other common causes.

Erhan AI — ERP & SAP Assistant

SAP S/4HANA & AI Consulting

Hello! I am Erhan Deniz's ERP and AI assistant. I can answer your questions about SAP S/4HANA (SD, ABAP, CO-PA), ERP consulting or AI solutions. How can I help you?