Issue

Syensqo in Belgium cross charges the global divisions approx 20M EUR per year for the services of the global procurement team.

This charge is based on a calculation of  benefits this team brings to the  divisions. As this recharge reduces the tax paid globally it is audited by tax authorities to ensure it is fair and realistic.  The same benefits calculation also drives performance related pay for the buyers and this helps justify the calculation with the tax authorities. 

Currently the calculation is done in Convergence using manually entered and maintained data.

Convergence is a standalone tool and the data is estimates of savings from discounts achieved in negotiations, not actual supplier performance based on transactions in the ERP system.

Convergence is a highly customised system created by Syensqo out of SalesForce and so does not fit into the standard and simplified approach of the ERP Rebuild Project.

This document evaluates the opportunities

• to improve the buyer performance tool by using actual data and integrated tools to give a winder view of buyer performance
• to reduce manual tasks by automating the gathering of data and the calculation by taking data from S/4  
• to enable the decommissioning of this customised standalone system

Recommendation

The project recommends the organization expands the scope of the reporting and utilises S/4HANA Standard Reporting tools to add other factors beyond simple contract price reduction into the Buyer Performance Calculations, as well as tracking actual transactional data.  Syensqo should consider building a single tool to automate the calculation using a custom development in S/4.

Background & Context

There is a Purchasing Team in Belgium that provides Procurement services across the rest the company.

Their "value" of their performance and the work they do for the rest of the company is a complex calculation based on

• Cost Reductions agreed on contracts - taking into account inflation etc
• Cash impact of any increased payment terms agreed
• Spend reduction due to volume reductions

As the calculation has to be acceptable to tax authorities it requires a lot of manual effort and data entry - users have to actions they took to obtain the benefits and data has to be maintained at a commodity level.

No other metrics, such as actual performance, OTIF (In Time, In Full) delivery by suppliers against contracts, off-contract spend, etc. are tracked. 

This performance calculation is used to do two things

• The reduction is used to prove the business value that the Procurement Team are bringing to the global divisions and calculate a value to charge the divisions for the provisions of this service. This charge therefore has tax implications and may have to be justified to tax authorities.
• To calculate the Buyer Performance related pay to be paid to Buyer teams.

This data is stored in Convergence which has some weaknesses

• Its a standalone tool where the data has to be entered manually and does not integrate into any other tools
• It only estimates the value of the discounts by projecting the estimated savings from the new contracts rather than the actual savings achieved.
• Its does not take into account supplier performance (on time deliveries, correct quantities, quality adherence)
• It cannot extend its coverage and track future supplier performance on things like sustainability.

Source of data and validity

The data that is entered into Convergence based on the contracts and the associated discounts/reductions that they have setup for the coming year; this is purely forecast data looking ahead for the expected discount, and does not look at the actual lowered prices paid on the POs created against the contract, nor does it look at supplier performance.

The data is entered manually by Procurement staff but is verified by Finance staff checking the expected discounts.

The current approach evaluates supplier performance on a limited metrics - how much they were able to save on the contracts they negotiated in the current year - and neglects other metrics which could provide a more comprehensive view of performance. 

Significance and credibility of the tax reducing recharge to the global businesses

The calculation lets Syensqo charge a benefits based to the global divisions that increase their local costs and reduce the tax they have to pay. This represents a significant amount (20M EUR) and is checked and validated by tax authorities, the most recent being Germany and France. If the Convergence tool is to be replaced it must be replaced with something that will be equally or more credible to the tax authorities and likely produce a similar benefit calculation to the historical average. Using actual SAP transaction data should help with the credibility but the nature of hte calculation is complex

ERP Rebuild creates an opportunity to widen the information used on the performance evaluation

There is other data available that could be used to widen the criteria of the performance measuring adding in factors such as 

• The SAP S/4HANA system holds data on actual Supplier Performance - on time deliveries, correct quantities, quality of materials
• The SAP S/4HANA system holds data on actual prices paid
• The wider market can be used to provide benchmark data on inflation and other factors that may cause price decreases 
• Future requirements - sustainability ratings of suppliers, adherence to EHS standards 

This would tie the benefit calculation/recharge and the buyer performance pay to wider organisational goals.

Assumptions

• The Recharge Calculation to the Divisions will continue to be required, will have a tax impact, and thus need to be justifiable if questioned by tax authorities.
• The Recharge Calculation to the Divisions will continue to be used to drive performance-related pay of Buyers. 
• Other reporting tools (eg tools like the Procurement Overview Fiori App) can replace the data used in the Convergence tool using live data from the S/4HANA system based on actual transactions against the contracts. 
• We can adjust the calculation used to provide a more holistic view – including supplier performance (eg. quality & reliability of deliveries, accuracy of Invoicing etc.)

Constraints

The calculations generated from this process are used and have impact outside of the basic Procurement process and this needs to be planned for.

Changing the Buyer Performance calculation will potentially impact Buyers performance-related pay and the amount of tax paid by the global division (as its may change the cross charge back to Belgium)

With 20M EUR of recharges that could be impacted by any changes, means that moving the process to a different system should be progressed carefully. 

Impacts

Process Changes

We aim to replace the manual calculation and entry of discounts achieved in an non-integrated system with automated tools using actual data coming from SAP S/4HANA Reports/KPIs.

Ideally we would like to be able to use the supplier performance as well as discounts achieved to work out the Buyer Performance.

This would necessitate a change away from the current project model. 

Change Management

Changing the mechanics of performance related pay could result in change management effort required within the organisation to change this approach to performance related pay .

Changes to the Cross Charge to Belgium from the global divisions may trigger queries from the local tax authorities.

Business Rules

If implemented then the calculation, the factors included and their weighting would need to be clearly published and adhered to.

Options considered

SAP S/4HANA can provide this information based on transaction data – including wider supplier performance. Should we use this information to expand the remit of the report/process?

Option 1: Maintain the current process on Convergence

Maintain this As Is process on the current system – as its manually entered data that does not get integrated anywhere else it could have no impact on the S4 HANA implementation..

Advantages:

• No disruption to current operations or need for process changes.
• No potential conflict with staff re performance related pay changes.
• Consistent data approach for Tax Authorities with questions.

Disadvantages:

• Have to continue to maintain Convergence system.
• The performance data is not coming directly from system - so can be inaccurate.
• No monitoring expected performance against real performance data from actual transactions 
• Continued effort of manual entry and validation

Option 2: Maintain the current process off system

Maintain this As Is process on spreadsheets to other tools  – its manually entered data that does not get integrated anywhere and allows the retirement of Convergence..

Advantages:

• No disruption to current operations or need for process changes.
• No potential conflict with staff re performance related pay changes.
• Consistent data approach for Tax Authorities with questions.

Disadvantages:

• Have to maintain an off system process.
• The performance data is not coming directly from system - so can be inaccurate.
• No monitoring expected performance against real performance data from actual transactions 
• Continued effort of manual entry and validation

Option 3: Use SAP Standard tools/KPIs/transactions to generate the report and calculations

SAP standard reports could be used to pull the actual spend data from the system along with actual supplier performance/evaluation. This would widen the remit of the calculation to cover not just anticipated discounts but actual spend reduction, quality and timeliness of delivery and adherence to any corporate standards such as recycling targets etc. 

The following data can be pulled from standard Fiori Apps/KPIs

• Prices actually paid as per the transactional data in the backend ERP system
• OTIF (In Time, In Full) performance
• % of deliveries failing quality checks
• Price changes against wider market conditions - eg inflation rates faced by benchmark competitors
• Adherence to EHS Requirements
• Sustainability factors - eg amount of waste/packaging recycled, CO2 emissions targets, traceability of recycling/waste

To combine all of these factors into a single calculation (as is produced from Convergence) would require a custom development

Advantages:

• Links Buyer performance and value of buyers to the company to company goals, suppler effectiveness and real pricing achieved not predicted
• Allows for expansion of factors for Buyer performance into new areas in the future (eg  supplier policies for DEI, reduction in master data errors, performance in cost reduction against industry benchmarks)
• Could leverage better reporting tools in and integration with S/4HANA  to drive business benefits
• No need for manual entry and validation of data

Disadvantages:

• Some disruption to current operations or need for process changes.
• Changing the calculation for performance related pay could be controversial and may change management input.
• Changing the Cross Charge/Tax Calculation may trigger questions from local Tax Authorities.
• To gat a single tool to produce the calculation would require a custom development

Evaluation

Based on the evaluation of the options, it is recommended that the organization utilise improved reporting tools that integrate with the ERP system to add actual transaction data and other factors beyond simple contract price reduction into the Buyer Performance Calculations. 

The change and effort will be in the change management area as this has the capacity to affect Buyers performance related pay – particularly the change from a forwarding looking approach running on Predicted Savings from Contract engagement to a backward looking approach looking at Actual Savings and real-world performance.

Next Steps

• Work with the business to assess impact and buy-in needed to gat acceptance on change to performance related pay and tax calculations
• Review standard reporting options in S/4HANA and other areas then share with business to identify the need for enhancement.

See also

There are other KDDs related to the use of the Convergence tool and the possible options to improve the processes using other tools

Change log

Workflow history