SAP is the most powerful financial reporting system most controllers will ever work with. It is also one of the most underused. The average SAP installation in a mid-size company runs perhaps 10 to 15 percent of the reporting capability the system actually has. The rest sits unused, not because it is unavailable, but because nobody configured it, nobody trained the team to use it, and the path of least resistance was to export data to Excel and rebuild the report manually every month.

This article covers the reporting capabilities in SAP that are most relevant for a controller doing management accounting work: the CO module’s cost centre and profitability tools, the standard report sets that are worth configuring, and the extraction approach that makes Excel reporting faster and more reliable when full SAP reporting is not available.

The focus is FI/CO, which is where the management accounting work lives. SAP BI and BW are more powerful but require specialist configuration and are outside the scope of what most controllers manage directly.

Understanding the FI/CO Split

The first thing to understand about SAP reporting is that financial accounting (FI) and controlling (CO) are technically separate modules with separate data structures, even though they post from the same transactions.

FI is the legal accounting layer. It records every transaction in journal entry format, maintains the general ledger, and produces the statutory financial statements. FI data is always complete and auditable.

CO is the management accounting layer. It records costs and revenues in a parallel structure organised around cost centres, profit centres, internal orders, and profitability analysis objects. CO data is the foundation of all management reporting in SAP.

The relationship between FI and CO is automatic for most transactions: when a vendor invoice posts in FI, a corresponding cost posting is made in CO to the relevant cost centre or internal order. When payroll posts in FI, CO receives the allocation across cost centres. The two modules stay in sync for external costs. The CO module adds additional postings that exist only in management accounting: allocations between cost centres, activity-based settlements, and profitability analysis postings.

This means that if the CO configuration is incomplete or wrong, your management reports will be wrong even if the FI ledger is perfectly clean. A controller who only reviews FI and ignores CO is seeing the statutory picture, not the management picture.

Cost Centre Reporting: The Standard Tools

The primary cost centre reporting tools in SAP CO are in the Cost Centre Accounting (CCA) component. The most useful standard reports are in the transaction S_ALR_87013611 series (cost centres: actual/plan/variance) and the cost centre line item report (KSB1).

S_ALR_87013611 - Cost Centres: Actual/Plan/Variance. This is the core management accounting report in SAP. For a given controlling area, fiscal period, and cost centre selection, it shows actual costs versus planned costs (budget) with the variance for each cost element. The cost element is the CO equivalent of the GL account: each cost element corresponds to one or more FI accounts and represents a specific cost category.

The output is a matrix: cost centres across the columns, cost elements down the rows. The variance column shows the absolute difference and the percentage variance. This report, run at the cost centre group level, gives you a complete view of how each area of the business is performing against budget. If it is configured correctly, it should be the starting point for the monthly variance commentary, not Excel.

KSB1 - Cost Centre: Actual Line Items. When the aggregate variance in S_ALR_87013611 shows a meaningful deviation, KSB1 is the drill-down tool. It lists every individual posting to the selected cost centre and cost element in the period, with the document number, posting date, vendor or employee, and amount. This is where you find the specific invoice or payroll posting that is driving an unexplained variance.

The combination of the aggregate report for variance identification and the line item report for investigation eliminates the need to go to FI for most cost centre queries.

Profit Centre Reporting

Profit centre accounting in SAP (PCA) provides the segment-level P&L reporting that cost centre accounting cannot. Where cost centres track costs by organisational unit, profit centres track both revenues and costs by business segment: product line, geography, channel, or any other dimension that reflects how the business is managed.

The standard profit centre reports are in the S_ALR_87013326 series. The most useful is the profit centre: actual/plan/variance report, which mirrors the cost centre report but at the profit centre level and includes both revenue and cost lines.

For profit centre reporting to be useful, three things need to be in place: profit centres must be defined in the system configuration to match the management reporting segments, every revenue and cost posting must carry a profit centre assignment, and the cost allocation methodology from cost centres to profit centres must be configured and running.

The last point is where most implementations fall short. It is common to have cost centres properly configured but profit centre assignments missing on many transactions, either because the configuration was never completed or because the team posting the transactions does not know they need to assign one. The symptom is a profit centre report with a large “unassigned” column that absorbs a significant portion of the total cost. If your profit centre report has an unassigned column above 5 to 10 percent of total costs, the assignment logic has a structural gap.

Internal Orders: The Project-Level Tool

Internal orders in SAP CO are the mechanism for tracking costs at a level below cost centre: a specific project, a marketing campaign, a capital expenditure item, or any activity that has a defined start and end and a budget that needs to be monitored.

Each internal order has its own budget, which is loaded separately from the cost centre plan. Costs are posted to the order as they are incurred, and the order report shows the budget, actual, and remaining balance. When the activity is complete, the order is settled: its accumulated costs are transferred to a cost centre, a profit centre, or an asset.

For controllers managing project-based businesses or businesses with significant capital expenditure, internal orders are the tool that makes project-level cost tracking possible within SAP without a separate project management system. The key configuration requirements are: orders must be created before the project begins (not retrospectively), budget must be loaded to the order, and the team must post costs to the order rather than directly to the cost centre.

The budget availability check can be activated on internal orders, which prevents posting beyond the approved budget without an explicit override. This is a useful control in environments where budget discipline at the project level is important.

Building a Standard Monthly Extraction

For controllers who need to produce management reports in Excel from SAP, the quality and efficiency of the extraction process determines how much time the month-end reporting takes. A poorly designed extraction requires manual manipulation after export. A well-designed one feeds a template that is largely pre-built.

The principle is to design the extraction once and use it every month without modification. The extraction should pull exactly the data the management report template needs, in the format the template expects, with no additional columns that need to be deleted and no missing columns that need to be added manually.

In SAP, extractions can be saved as variants: named combinations of selection parameters that can be executed with a single transaction code call. Setting up named variants for the two or three reports you run every month, such as cost centre actuals for the period, year-to-date, and the equivalent budget plan lines, means the monthly extraction takes minutes rather than an hour of re-entering parameters.

The extracted data should land in a defined Excel structure: consistent column headers, consistent account numbers, consistent cost centre codes. If the structure is consistent every month, the pivot tables and formulas in the management report template can be designed to update automatically when new data is pasted in, rather than requiring reconstruction.

When Excel Is Unavoidable

SAP’s standard reports cover most of what a controller needs for the management accounting work. But there are legitimate situations where Excel is the right tool: multi-entity consolidation where the SAP instance does not have a proper consolidation module configured, the management report layout that needs a specific visual format not producible in SAP standard, or the forward-looking forecast that lives outside the ERP entirely.

In these situations, the quality of the SAP extraction determines the quality of the Excel work. An extraction that is clean, consistently structured, and automated removes the data preparation step and leaves the controller’s time for the analysis and commentary that actually requires human judgment.

The investment is front-loaded: designing the extraction variants, building the Excel template to receive the data cleanly, and testing the integration across two or three monthly cycles. Once the infrastructure is in place, the monthly reporting process becomes a consistent, efficient, and lower-risk operation than the manual rebuild it replaces.

Need help getting better reporting from your ERP? Download professional Excel templates or book a free call.

Alessandro Ratzenberger is a fractional CFO and business controller based in Zurich, with 15 years of operational finance experience at Dufry Group and Bomi (UPS Group).