| Status | |
| Owner | |
| Stakeholders | RUSNAK-ext, Peter |
Syenqso run a global buyers team from Belgium which makes a cross charge to the global businesses. This charge is based on the calculated benefit that this team brings to the global businesses.
Currently this cross charge is approx 20M EUR per year. As this cross charge reduces the tax payable in the global businesses the figure and the calculation of it is audited by local tax authorities to ensure its fair and realistic.
Currently the performance of buyers is tracked using data entered into and manually maintained in the Convergence system.
This is used to calculate:
Convergence is a standalone tool and only holds manually-entered estimated savings from discounts on the contracts, rather than looking at actual supplier performance based on actual transactions in the ERP system.
This document evaluates the opportunities for improving the measurement of buyer performance including use of actual data and integrated tools to improve Buyer Performance tracking.
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.
There is a Purchasing Team in Belgium that provides Procurement services across the rest the company. Their performance is currently measured on how much discount they have achieved on their contracts that will be active for the coming year. 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
This data is stored in Convergence which has some weaknesses
Source of data and validity
The data that is entered into Convergence based on the contracts 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 lowered prices on the POs created against the contract.
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 single metric - 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.
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
This would tie the benefit calculation/recharge and the buyer performance pay to wider organisational goals.
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)
We aim to replace the manual calculation and entry of discounts achieved in an non-integrated system with actual data coming from SAP S/4HANA Reports/KPIs.
Ideally we would like to be able to use the supplier performance as well as simple discounts to work out the Buyer Performance.
This would necessitate a change away from the current project model.
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.
If implemented then the calculation, the factors included and their weighting would need to be clearly published and adhered to.
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?
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:
Disadvantages:
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:
Disadvantages:
Examples of metrics to include based on industry best practices could be
Advantages:
Disadvantages:
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.
Option 1Maintain the current process on Convergence | Option 2Maintain the current process off system | Option 3Use SAP Standard tools/KPIs/transactions to generate the report and calculations | |
| Data integrated with actual transactions, no manual entry | NO | NO | YES |
| Can Align Buyer performance to wider organisation goals (eg Sustainability) | NO | NO | YES |
| Measures actual supplier performance, not only discount | NO | NO | YES |
| Impact on Cross Charging and tax calculations | NO | NO | YES |
| Impact on performance related pay | NO | NO | YES |
There are other KDDs related to the use of the Convergence tool and the possible options to improve the processes using other tools
| Doc Link | Doc Title |
|---|---|
| Ariba - Enhanced Contract Authoring in SAP Ariba Contracts vs Icertis | Ariba - Enhanced Contract Authoring in SAP Ariba Contracts vs Icertis |
| KDD002 - Contract Lifecycle Management in SAP Ariba Contracts vs. Convergence | Contract Lifecycle Management in Ariba Contracts vs Convergence |
| Not drafted yet | Category Management in Ariba Category Management vs Convergence |
