RISE for professional services.

RISE with SAP deployments inside professional services firms have an operating profile that differs structurally from the manufacturing, retail, and financial services deployments that the SAP commercial proposal typically anticipates. The professional services firm runs the business through the chargeable time of the partner and consultant workforce, recognises revenue against the project lifecycle that the time supports, and consolidates the result across a network of legal entities that frequently combines partnerships, corporations, and joint ventures across multiple jurisdictions. The user classification, the project accounting, the revenue recognition, the partnership accounting, and the multi entity rollup each carry implications for the FUE consumption profile, the configuration choices, and the contract structure. This article walks through the operating model of the professional services firm, the user profile and FUE classification challenges, the project accounting and revenue recognition requirements, the multi entity accounting structure, and the negotiation of the professional services edition.

The operating model of professional services firms

The professional services firm operates a business model in which the revenue depends on the chargeable time of the partner and consultant workforce, the project margin depends on the realisation rate of the chargeable time against the project budget, and the firm profitability depends on the utilisation of the workforce against the available capacity. The SAP estate that supports the firm needs to capture the time, the expense, the project budget, the project actuals, the revenue recognition, the billing, and the consolidated result, all integrated against a workforce of partners and staff that frequently exceeds the size of the manufacturing workforce that a similar revenue manufacturer would carry.

The operating model creates a user population that is large relative to the revenue of the firm, with a higher proportion of the workforce engaging with the SAP estate than the proportion that engages in a manufacturing or retail firm. The professional services firm with one billion dollars in revenue might have five thousand chargeable staff and an additional one thousand support staff, all of whom interact with the SAP estate at some level. The user population drives the FUE consumption profile that the RISE contract needs to accommodate, and the consumption profile is the largest single driver of the commercial structure of the deal.

The operating model also depends on the project as the central organising unit of the operation, with the project carrying the budget, the staffing, the time, the expense, the revenue, the billing, and the consolidated profitability. The S/4HANA project accounting functionality supports the model and the buyer team should validate that the supported configuration in the RISE edition that the negotiation targets covers the project accounting requirements of the firm.

User profile and FUE classification challenges

The user profile and FUE classification framework that SAP applies to the RISE contract maps the user types of the buyer organisation onto the FUE consumption tiers that the contract prices against. The framework distinguishes the advanced user, the core user, the self service user, and the developer user, with each tier carrying a different FUE consumption coefficient. The mapping of the professional services workforce onto the tiers is the largest single commercial question that the negotiation needs to resolve.

The partner and consultant workforce frequently maps onto the core user tier because the workforce captures time, submits expenses, and interacts with the project and engagement records. The mapping is the SAP account team preferred interpretation because it produces the highest FUE consumption. The buyer team should challenge the interpretation against the actual functional usage of each user category, with the documented usage profile supporting the reclassification of part of the workforce into the self service tier where the interaction is limited to the time and expense capture.

The support workforce frequently maps onto a mix of the core and the self service tiers depending on the functional role. The finance staff that operates the billing, the revenue recognition, and the consolidated reporting maps onto the core tier or the advanced tier. The administrative staff that supports the partner workforce maps onto the self service tier or the core tier. The IT staff that operates the SAP estate maps onto the developer tier, with the corresponding FUE consumption. The accurate mapping requires the documented user role analysis that the buyer team produces against the SAP supplied classification framework.

The classification challenge is compounded by the contractor and the secondee population that frequently flows through the professional services firm. The contractors that interact with the SAP estate consume FUE on the same basis as the employed workforce, and the contract should establish the treatment of the contractor population in a way that does not penalise the firm for the operating model that the professional services business depends on.

Project accounting and revenue recognition under RISE

The project accounting and revenue recognition under RISE need to support the engagement lifecycle that the professional services firm operates against, including the fixed fee engagement, the time and material engagement, the milestone billing engagement, the cost plus engagement, and the success fee engagement. Each engagement type carries different revenue recognition implications under the accounting framework that the firm operates against, including ASC 606 in the United States, IFRS 15 internationally, and the equivalent national frameworks.

The configuration of the project accounting in the S/4HANA Cloud Public Edition that GROW with SAP targets carries constraints that the buyer team needs to validate against the operating requirements of the firm. The Public Edition supports the standard project accounting flows that the SAP commercial proposal positions, and the buyer team needs to confirm that the supported flows cover the specific configurations that the firm operates against. The Private Edition supports the broader configuration options that the firm might require, with the corresponding implications for the deployment cost and the operating cost of the contract.

The revenue recognition under the engagement lifecycle requires the integration between the time capture, the project budget, the project actuals, the deferred revenue position, the unbilled revenue position, and the recognised revenue position. The integration carries the audit dimension that the external auditor of the firm will examine at the audit cycle, and the configuration of the integration is a structural decision that the firm should resolve during the design phase of the RISE deployment rather than at the operating point.

Multi entity and partnership accounting

The multi entity and partnership accounting structure that the professional services firm operates against typically combines the operating entities in each jurisdiction, the partnership entities that hold the equity interests of the partner workforce, the corporate entities that support the operating arrangement, and the consolidation entity that produces the group result. The structure varies across the firm types, with the large accounting firm operating a network of legal entities tied together through a network agreement, the law firm operating a partnership structure across a smaller number of jurisdictions, and the consulting firm operating a corporate structure across the regional operations.

The S/4HANA estate that supports the firm needs to accommodate the chart of accounts mapping across the entities, the inter entity transaction processing, the consolidation rules that produce the group result, and the transfer pricing arrangements that allocate the result across the entities. The configuration is a substantial undertaking and the buyer team should validate that the supported configuration in the RISE edition covers the structural requirements before the contract closes.

Negotiating the professional services edition

The negotiation of the professional services edition of the RISE contract should focus on the FUE classification framework, the project accounting configuration, the multi entity support, and the contractor population treatment. The FUE classification should be negotiated against the documented user role analysis that the buyer team produces, with the reclassification of any tier mapping that does not reflect the operating reality. The project accounting configuration should be validated against the engagement lifecycle of the firm, with the documented confirmation that the supported configuration in the selected edition covers the operating requirements. The multi entity support should be validated against the legal entity structure of the firm, with the documented confirmation that the consolidation and the transfer pricing configurations support the group reporting requirements. The contractor treatment should be negotiated as a defined provision that protects the firm against the FUE consumption that the contractor population would otherwise generate. The four dimensions together shape the commercial position of the deal and the operating model of the deployment across the seven year contract term.

Conclusion: the operating model shapes the deal

The RISE with SAP deployment for a professional services firm reflects the operating model of the firm in a way that the deployment for a manufacturer or a retailer does not. The user population is larger relative to the revenue, the project is the central organising unit of the business, the revenue recognition depends on the engagement lifecycle, and the consolidated result combines the entities across the network. The buyer team that engages with the operating model as the structuring constraint of the deal produces a contract that supports the firm across the seven year term. The buyer team that accepts the standard SAP commercial framing without the operating model overlay produces a contract that overcharges for the user population, that constrains the configuration of the project accounting, and that fails to accommodate the multi entity rollup that the firm depends on. The structuring approach is the difference between a deployment that supports the professional services business and a deployment that constrains it.