
Why reconcile SAP costing-based Profitability Analysis (CO-PA) with the general ledger (GL)? The GL is the book of record for external reporting, while CO-PA provides detailed profitability information that finance teams use for management reporting and forecasting.
In the company example below, CO-PA provides revenue and cost of sales (COS) by sales order, product line, and customer, beyond the totals used in the GL comparison. This detail helps explain profitability and forecast future sales and COS. To use it with confidence, finance teams need procedures to reconcile and explain differences between CO-PA and the GL.
Scope: This historical case study, originally published in 2014, describes Elitza's costing-based CO-PA process at SPX Genfare. The account requirements, posting behavior, and repair-order differences below reflect that company's configuration and should be checked against your own system.
Table of Contents
- Why Reconciliation Matters for Forecasting
- 1. Include Manual Postings in KE24
- 2. Check Profitability Fields
- 3. Explain Timing Differences with KEAT
- 4. Review Repair Sales Orders
- Related Reading
Why Reconciliation Matters for Forecasting
At my previous company, SPX Genfare, it was important to reconcile CO-PA to the GL because we used the CO-PA line item report KE24 to provide monthly actuals by customer, product type, and contract size. We loaded this data into our Hyperion Planning forecasting system. An accurate forecasting base required accurate historical data, with no material unexplained difference.
The following four steps explain how we reconciled the CO-PA line item report KE24 to the GL.
1. Include Manual Postings in KE24
Include manual journal entries (record type B) when running KE24.
2. Check Profitability Fields
In this process, manual journal entries involving revenue and COS needed profitability fields, such as sales order and customer, to post to CO-PA. The company applied these requirements:
- Profitability fields for all revenue accounts and manual COS accounts were mandatory.
- Profitability fields for the general COS account were not mandatory because some journal entries recorded to COS did not relate to a specific sales order. These entries became reconciling items between CO-PA and the GL.
3. Explain Timing Differences with KEAT
The preceding steps minimized reconciling differences but did not eliminate them. In the process described here, timing differences arose because:
- CO-PA posted both revenue and COS when an item was invoiced.
- The GL posted COS at goods issue and revenue when the item was invoiced.
Run transaction KEAT to investigate postings to the GL in previous periods that have not yet been billed.
4. Review Repair Sales Orders
The remaining differences in our example related to revenue and COS from repair sales orders. Most repair-order revenue and COS were not recorded in CO-PA because of the order billing types. At the time of the original article, we were investigating how to prevent these items from remaining reconciliation differences.
Related Reading
- Reconciling SAP CO-PA to the General Ledger — further background on the reconciliation challenge.
- SAP Accounting Powered by SAP HANA: FAQs and S/4HANA Evolution — background on financial accounting and profitability reporting integration.
- SAP Margin Analysis Extensibility — related reading for S/4HANA profitability reporting.
Need Help Reconciling SAP CO-PA and the General Ledger?
ERPCorp helps finance teams investigate profitability reporting differences, review SAP Finance and Controlling processes, and improve reconciliation and month-end reporting.
SAP Controlling Conference 2027
Join SAP Finance and Controlling professionals in San Diego on September 12–14, 2027, as we celebrate 15 years of shared knowledge and connections.
Explore practical insights into Product Costing, Margin Analysis, SAP S/4HANA Finance, and reporting.
