SAP S/4HANA Finance gives controllers earlier visibility into costs, revenue, and margins. The Universal Journal can capture reporting dimensions when a transaction posts, and event-based accounting can create follow-on entries for selected processes during the period.
Some closing activities still depend on period-end balances or exchange rates. To plan the close, identify which values are available with the original posting, which require a follow-on entry, and which still come from a scheduled run.
Three Ways SAP S/4HANA Handles Finance Postings
Table 1 compares how the three patterns affect what controllers can see during the period.
| Pattern | When the Data Becomes Available | Example |
|---|---|---|
| Enrich the original posting | When SAP posts the journal entry and can derive the reporting attributes. | Margin Analysis adds a customer or product characteristic to a relevant journal entry. |
| Post a follow-on entry | When a supported business event triggers a calculation and posting. | A project cost posting triggers a revenue recognition adjustment under the applicable recognition rules. |
| Run a periodic close task | At the scheduled valuation or reporting date. | Foreign currency valuation uses the applicable closing-date exchange rates. |
Capture Market Segment Data in the Universal Journal
When the relevant characteristics are available, Margin Analysis can derive a profitability segment for reporting when the journal entry posts. For example, an expense assigned to a project may already be visible by customer if SAP can derive that customer from the available account assignment.
An attributed profitability segment provides reporting context. The underlying account assignment may still be the order or project, and settlement or allocation can still be required. When information becomes available later, realignment can update eligible profitability characteristics on posted data. See SAP Help on Margin Analysis.
Trigger Overhead and Revenue Recognition with Business Events
With the applicable configuration, event-based overhead can post alongside eligible business transactions. For a manufacturing example, see Event-Based Production Accounting in SAP S/4HANA.
In a supported professional services scenario, confirming hours on a consulting project posts the underlying labor cost. Event-Based Revenue Recognition can then post a separate adjustment according to the project’s recognition method. Controllers can trace the adjustment to the underlying transaction and review the resulting margin during the period.
Keep Period-End Valuations and Reconciliations on the Close Calendar
Tasks such as closing-date foreign currency valuation and final reconciliations still depend on the reporting date and the transactions posted through that date. Review in-period results as entries post, then use the close to confirm completeness, investigate exceptions, and post any remaining adjustments.
About the Author
Birgit Oettinger is a product manager for Management Accounting at SAP SE. She began as an SAP FI/CO consultant focused on product costing and integration and has worked on finance solutions for cloud and on-premise deployments. She was a featured speaker at Controlling 2017.