Procurement licensing, supplier fees, and the network in the middle. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back. Session twenty eight, still in module six, and today it is Ariba and the SAP Business Network. This one is structurally different from every other product in the course, and the difference is worth stating up front: there are two payers. You pay a subscription for the modules, and your suppliers above a threshold pay network fees to transact with you. That second arrangement is not your invoice and it is very much your problem. On top of that, procurement is often priced on spend rather than users, which behaves differently again. Today: both sides of the network, the spend metric, why leaving is harder here than anywhere else, and what to negotiate. Three knowledge checks. Let's begin.
Five objectives. First, separate the two sides: what you pay as a buyer and what your suppliers pay to transact with you, because both affect you and only one is your invoice. Second, read the spend metric, since procurement is often priced on spend under management, which behaves nothing like a user count. Third, anticipate supplier pushback, because supplier fees are a real friction in your onboarding programme and they land on your team rather than SAP's. Fourth, see the network effect, meaning why leaving is harder here than in any other SaaS product and what that does to your renewal. And fifth, negotiate the whole stack, because sourcing, contracts, buying, invoicing and the network are separately licensed and rarely bought together well.
Four things to frame it. You pay: a subscription for the modules, commonly scaled to spend under management or to transaction volume. They pay: suppliers above a threshold pay network fees to transact with you, which is not your invoice and very much your problem. A stack: sourcing, contracts, buying, invoicing and the network, separately licensed and often bought piecemeal. And sticky: once thousands of suppliers are onboarded, moving is a programme rather than a migration. The practical consequence is that your leverage at renewal is lower here than in any other product we have covered. Let me start with that two payer point, because it is the one people wave away.
Guest analyst clip.
A commercial arrangement you did not sign, and a delivery risk on your programme. That is the shape of it. And notice that the correct response is not to argue about whose problem it is in principle, because that argument does not help your category manager on the phone. The correct response is to plan for it: know who falls above the threshold, brief them before they hear it from somewhere else, and give the whole topic an owner. Now, what you actually license.
Four groups on your side, licensed separately. Sourcing: running events, RFx and auctions, often priced on the number of sourcing projects or on the spend you source. Contracts: the contract repository and lifecycle, usually per user, and usually a fairly small population of contract managers. Buying and invoicing: requisitions, purchase orders and invoice matching, priced on transaction volume or on spend under management. And network access: your side of the connection to suppliers, increasingly bundled, and worth confirming exactly what your tier includes. Supply chain collaboration and forecasting sit alongside those and are separate again. The practical advice is to ask for the line items rather than the bundle price, because organisations regularly discover they are paying for a sourcing module that ran four events last year, and that is completely invisible inside a single procurement figure.
Now their side. Five points. Fees above a threshold: suppliers below a volume or value threshold typically transact free, and above it they pay to stay connected to you. Charged on relationship and volume, so broadly a fee reflecting the number of customer relationships and the documents transacted, and the rates change so verify the current ones rather than quoting mine. It becomes your problem, because suppliers do not call SAP, they call your procurement team, often mid onboarding. Small suppliers resist hardest, since a fee that is trivial for a large vendor is a genuine objection for a small one, and small suppliers are usually your long tail. And plan for it in the programme, because onboarding rates fall when fees arrive as a surprise.
First knowledge check. Your suppliers object to network fees during onboarding. Whose problem is it? A, SAP's, since they charge the fee so they handle the objection. B, yours, because it lands on your team and it slows your programme. C, the supplier's, since it is a cost of doing business with you. D, nobody's, because fees are small enough to ignore. Pause here and pick an answer before you continue.
B. Commercially A and C are both perfectly defensible, and operationally they are useless to you. The supplier has no relationship with SAP and every relationship with you, so the call comes to your category manager, who now has a procurement problem instead of an onboarding task. D underestimates the long tail badly, because a fee a large vendor absorbs without comment is a real objection for a small supplier, and small suppliers are usually most of your count. So treat supplier fees as a programme risk with an owner and a communication plan, because your onboarding rate is what decides whether the whole investment pays back.
Now the spend metric, and how it actually behaves. The base is spend flowing through the platform rather than your total spend, so onboarding more categories raises the metric. Direction: it rises with adoption, which is the goal, so success on the programme increases your licence cost. Volatility: commodity prices and volumes move it, so a raw materials spike can move your licence figure. Currency: multi currency estates convert at a stated rate, so ask which rate and when it is set. And your lever is banding, caps and the definition of what counts, all of which are contract terms and all of which are negotiable before signature. I want to dwell on that second row, because it creates a real organisational problem.
Guest analyst clip.
Give the net number an owner, otherwise success starts to look like a problem. That is the thing to take from this slide, and it is a governance point rather than a licensing one. The licensing fix is banding. The organisational fix is making sure the person who reports savings also reports the licence cost, so nobody is ever incentivised to quietly stop onboarding.
Second knowledge check. Your commodity costs rise thirty percent. What happens on a spend based licence? A, nothing, since transaction volumes are unchanged. B, the metric rises, because the value flowing through rose. C, it depends on whether new suppliers were added. D, the rate falls automatically to compensate. Pause here before you continue.
B. A spend based metric measures value, so the same volume at a higher price is a higher figure, and your licence cost has just moved with a commodity market you do not control. A confuses volume with value. C is irrelevant, because your existing suppliers alone produce the increase. And D is wishful thinking. This is precisely the argument for banding: agree that the price steps at defined thresholds rather than tracking spend continuously, so that ordinary market movement does not reprice your contract. Ask for it before signature, because afterwards you are asking for a concession rather than agreeing a structure, and those are very different conversations.
So, the network effect, and four sources of switching cost, of which only the first is technical. Your integrations: the ordinary cost of moving any platform, which is real, bounded, and the smallest of the four. Supplier onboarding: every connected supplier has to be re-onboarded somewhere else, which is thousands of relationships rather than a data migration. Supplier goodwill: you asked them to join and to pay fees, so asking them to do it again on a different network costs credibility you may need elsewhere. And process embedding: approval flows, catalogues, controls, and the audit story built on top of all of it. Let me be blunt about what that adds up to.
Guest analyst clip.
A relationship cost that does not appear on any spreadsheet. And since switching cost sets renewal price, as we established in session twenty one, that makes this the agreement where the renewal mechanism is worth the most and where it is hardest to win later. So win it at the first contract, when leaving is still something you could plausibly do.
Five things to negotiate. Band the spend metric, so stepped thresholds rather than continuous tracking, and ordinary price movement stops repricing you mid term. Cap the uplift, meaning a ceiling on the annual increase regardless of what the metric does, and this is the single most valuable term in the agreement. Buy modules you will use, because sourcing, contracts and invoicing are separate, and a module bought for a future phase is shelfware with a renewal date attached. Ask about supplier fees: current rates, thresholds, and whether there is any programme to support your long tail, because it affects your adoption and therefore belongs in the commercial conversation. And settle renewal early, because switching cost here is enormous and the renewal mechanism matters more than in any other product in module six.
Five traps. Unbanded spend pricing, where the licence tracks a commodity market and your budget moves for reasons unrelated to your software estate. Ignoring supplier fees until go live, so onboarding stalls, the long tail refuses, and the business case depends on adoption you did not achieve. Buying the full stack up front, with five modules licensed and two implemented, and the other three renewing quietly for years. No renewal mechanism, which given this switching cost is the most expensive omission available anywhere in the SaaS estate. And measuring success only on savings, because if adoption raises the licence cost then somebody has to own the net number or the programme quietly stops onboarding.
Last knowledge check. Which term should you fight hardest for in an Ariba agreement? A, a larger discount on the first year subscription. B, banded pricing with a capped annual uplift. C, free supplier onboarding support. D, additional sourcing project entitlements. Pause here, and think about which one protects you when the metric moves.
B, and by now you know why the mechanism wins: it governs every year rather than one, and it protects you against a metric that moves for reasons outside your control. A is the year one number again, gone by year two. C is genuinely useful and absolutely worth asking for, and it helps your programme rather than your contract, so ask for both. D is entitlement you may well not use. The distinctive feature of Ariba is that your switching cost is the highest in the portfolio, which means the terms governing later years matter more here than anywhere else, and they have to be won at the first contract because your position only weakens from there. Let me describe what a good banding term actually looks like.
Guest analyst clip.
Converting an unpredictable line into a forecastable one. Right, five things for running the procurement estate. Track the metric monthly, so spend under management against your band, because you want to see a threshold approaching rather than arrive at it. Own the supplier fee conversation with a named person, a standard explanation, and a list of who falls above the threshold before you onboard them. Report module adoption: events run, contracts managed, invoices processed, per module, so an unused one is visible well before it renews. Net the business case, meaning savings delivered minus licence cost, because if adoption raises the licence then the programme needs the net figure in order to stay funded. And diarise the renewal eighteen months out, since the highest switching cost in the portfolio deserves the longest run up, and you want to start before the vendor does.
Three sentences. Ariba is the only two sided arrangement in this course, because you pay a subscription while your suppliers above a threshold pay network fees, and their objections arrive at your procurement team rather than at SAP. Procurement is commonly priced on spend under management, which rises when the programme succeeds and when commodity prices move, so band the metric and cap the annual uplift before signature rather than after. And switching cost here is the highest in the portfolio because it includes every supplier relationship you onboarded, which makes the renewal mechanism worth more in this agreement than in any other product in module six. Next session covers the rest of the SaaS estate: Customer Experience, Concur and Fieldglass, which are four more metrics and four more renewal cycles that rarely get read because individually they look small.
Homework before session twenty nine, about an hour. One, get the line items, meaning your procurement spend broken out by module rather than presented as one figure, and ask your account team if you cannot find it. Two, find your metric definition: what exactly counts as spend under management in your contract, and is the pricing banded or continuous? Three, count suppliers above the threshold, because how many of your connected suppliers pay fees predicts your onboarding friction quite accurately. Four, check module adoption, so for each licensed module what was actually used last quarter, and sourcing is the usual surprise there. And five, net your business case: savings attributed to the platform minus what the platform costs, because most cases only ever show the first of those two numbers.
Five guides, all on redresscompliance dot com. SAP Ariba licensing explained covers the module stack and the metrics with worked pricing examples. SAP Business Network supplier fees expands slide seven, so thresholds, rates and how to brief your suppliers properly. Spend based licensing metrics covers banding, caps and the definitions worth negotiating, which is the core of today's advice. SaaS renewal negotiation is about renewal mechanisms, and those matter most exactly where switching cost is highest. And the SAP cloud portfolio overview shows where procurement sits in the estate, which is where session twenty nine picks up.
That is session twenty eight. The thing to take away is that there are two payers, the metric moves with markets rather than with your decisions, and switching cost is the highest in the portfolio, so band the price and settle renewal early. Next time, the rest of the SaaS estate. See you then.