The agreement, the price list, the use rights, the order forms, and the true up clause. 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 four, and this is the one that makes the previous three usable. Sessions one, two and three were about counting. Named users by type, engines by business volume, and where both of those go wrong. Today we deal with the only thing that turns a count into an obligation, which is the paper. Here is the claim I want to make at the start, and then spend the next twenty eight minutes proving. Almost every expensive SAP dispute I have seen was not lost on the facts. It was lost because one side could cite a document and the other side could not. Not because they were wrong, but because they could not prove they were right, quickly, from a complete record. So today: the five kinds of document in the stack and what each one settles, the price list version and why it is the most underestimated page you own, the two clauses that decide how disputes actually end, how to read an order form properly, and the contract library that makes all of it usable. Three knowledge checks, one of them arithmetic. Let's begin.
Five things by the end. First, name the stack, in order of authority, and say what each document settles. Second, date your definitions, which means finding which price list version each of your order forms references, and understanding why that single fact decides what your metrics mean. Third, read an order form, and pull entitlement, metric, discount and special terms off the page without needing help. Fourth, locate the two clauses. The measurement clause and the true up clause. Most people in this field have never read either, and they decide the ending of every dispute. And fifth, build the library. A complete, current contract set. It is the least glamorous thing in this course and it is the cheapest leverage available to you.
Four ideas. Signed. Only signed documents create obligations. Everything else is somebody's opinion about your money, however official the formatting looks. Version. The price list version your order references defines your metrics, and it is not the current one. Definitions are dated, and the date is yours, not SAP's. Two. Two clauses decide how disputes end. What SAP may measure and how an overage gets priced. I would guess ninety percent of the people watching this have never read either of them in their own agreement. And weeks. That is how long it typically takes an enterprise to assemble its own contract set. Meanwhile SAP has all of it, indexed, in one place, before the conversation even starts. That last asymmetry is the entire point of this session, and the good news is that it is the cheapest one to fix. Let's play a clip, because this is something my colleague sees on day one of almost every engagement.
Guest analyst clip. The first thing I ask a new client for is their SAP contract. Not a summary, not a spreadsheet, the actual documents. And I want to tell you honestly what usually happens next, because it is not what people expect. In most cases it takes between two weeks and two months. Somebody eventually finds a signed agreement from two thousand and eleven in a shared drive. The order forms are scattered across procurement, legal, and the mailbox of somebody who retired. Nobody is certain they have all the amendments. And here is what that means commercially, because it is not just untidiness. SAP has all of it. Every document, indexed, in one place, available to whoever is preparing for your renewal. So when a conversation starts about what you are entitled to, one side is reading from a complete record and the other side is reconstructing history from fragments. You are not negotiating at that point. You are guessing, politely. The customers who do well have a contract library. Every agreement, every order form, every amendment, every price list version those documents reference, in one place, current. It is genuinely unglamorous work. It is also the single cheapest thing you can do that changes the balance of a negotiation, and it costs you nothing but a few weeks of somebody's attention.
You are not negotiating at that point, you are guessing politely. I would write that one down. And notice she did not say the customers who do well have better lawyers, or more leverage, or a bigger spend. She said they have a folder. That is the entire competitive advantage being described, and it is available to everybody watching this for the price of a few weeks of somebody's attention. So let's look at what belongs in the folder.
Five kinds of document. Names vary by era and by territory, so recognise the structure rather than memorising the labels. The agreement. Your framework. General terms plus the software licence agreement. It carries the definitions, the use rights baseline, the measurement and audit rights, assignment, and territory. Order forms. One per purchase. Products, quantities, metrics, discount, term, and any special conditions somebody negotiated. Add all your order forms together and that, precisely that, is what you own. The price list. SAP's list prices, and far more importantly the metric definitions. Versioned, revised regularly, incorporated by reference. Use rights. What each user type may do and how each engine is counted, also incorporated by reference, and also changing between versions. And the support and cloud schedules. Enterprise Support terms, and the subscription paper for RISE, GROW and the SaaS applications, where the renewal uplifts and the termination limits live. Anything not in that list binds nobody. Policy pages, sales decks, licensing explainers: useful for understanding what SAP intends, worthless as an obligation.
So which document settles which argument? What do we own? The order forms, added up, plus amendments. Not a summary spreadsheet, and this is where people go wrong, because the spreadsheet is easier to read and it is not evidence. What does this metric mean? The price list version your order references. People read the current definition instead of the one that binds, and that error is worth real money. What may this user do? The use rights document for the applicable version, and rights are not uniform across systems and eras, so do not assume. What can SAP ask us for? The measurement and audit clause. The common mistake there is answering the request before reading the clause, which is understandable and expensive. And what does an overage cost? The true up clause, plus your contracted discount. Accepting a list price settlement that your contract may not actually require is one of the most costly reflexes in this field. Learn this table and you will never again be told what you owe by somebody who has not cited a document. The question is always the same. Which signed paper says that, and which version of it?
First knowledge check. An account manager sends you SAP's current published definition of a chargeable document, to justify a finding. What is your first question? A, does the definition seem reasonable given how we use the system? B, which price list version does that definition come from, and is it the one our order references? C, can we get a discount applied to the resulting number? D, how did SAP measure the volume they are quoting? Pause here and pick one.
The answer is B. Definitions are dated. The version incorporated by your order form is the one that binds you, and it may be a decade old. Look at why the others lose. A argues fairness, and fairness has no contractual weight whatsoever, however reasonable you sound. C is the most common real world answer, and notice what it does: it accepts the finding and negotiates the price, which concedes the principle in exchange for a percentage. And D, how did you measure it, is actually a good question, just not the first one. Measurement only matters once you have established which definition is being measured against. Get the order right and you sometimes never need question D at all.
Let's stay with the price list, because it deserves its own slide. What people assume it is: a list of prices. What it actually is: a list of prices and the definitions of every metric you are counted on. Which one applies? People assume the current one. In fact it is the version referenced by the order form you signed, however old that is. Where does it live? Somewhere at SAP, people assume, and therefore out of reach. In fact it is incorporated into your contract by reference, which means you are entitled to a copy, and you should ask for one. And why does it matter? People think it sets what things cost. It does, but far more importantly it sets what counts, and what counts moves the number much more than the rate does. Get a copy of every price list version your order forms reference and keep it with them. It is a boring afternoon that has repeatedly turned into the strongest single argument in a settlement discussion. Let's play a clip.
Guest analyst clip. I want to spend a minute on the price list, because it is the most underestimated document in the entire relationship. People think of it as a price list. It is not. It is the document that defines your metrics. What counts as a document, what counts as an employee, how a user type is described, what a shipment means for the purposes of the engine you bought. Those definitions live there, and SAP revises the price list regularly. Now, the version that governs you is the version your order form referenced when you signed. Not the current one. And that creates two very practical consequences. The first is that you need to know which version each of your order forms points at, and you probably need to obtain a copy of it, because it may be fifteen years old. The second is that when SAP quotes a definition at you, the correct question is which version that definition comes from. I have sat in meetings where a metric definition from a current price list was being applied to a purchase made under a much older one, and the difference was worth seven figures. Nobody was being deceptive. It simply had not occurred to anyone in the room to check which document they were arguing from.
Nobody was being deceptive. It simply had not occurred to anyone in the room to check which document they were arguing from. That is the honest description of how most of this goes wrong, and it is worth holding on to, because it changes how you behave in the meeting. You are not accusing anyone of anything when you ask which version a definition comes from. You are asking a neutral, procedural question that any competent person on the other side will answer. It just happens to be the question that decides the outcome. Which brings us to what the pricing basis is actually worth.
Second knowledge check, with arithmetic. You are two hundred thousand documents over entitlement. List price is five per document. Your contracted discount on that product is sixty percent. What is the difference between a settlement priced at list and one priced at your contracted rate? A, there is no difference, overages are always at list. B, six hundred thousand, the difference between one million and four hundred thousand. C, four hundred thousand, the discounted value of the overage. D, it cannot be calculated without knowing the renewal date. Pause and work it out.
The answer is B, six hundred thousand. Two hundred thousand documents at five is one million at list, and four hundred thousand at your sixty percent discount. So the pricing basis alone, on one finding, is worth six hundred thousand. Now look at answer A, because a lot of people believe it. Overages are always at list is not a law of nature, it is a contractual question, and the answer is in your true up clause. Sometimes it says list. Sometimes it says contracted rates. Sometimes it is silent, which is its own conversation. C is the settlement value rather than the difference, so read the question. And D confuses timing with pricing basis, although timing is worth asking about separately, because from what date an overage is charged is another clause level question with real money attached.
So, the two clauses. The measurement clause. What SAP may request, how often, with what notice, and in what form. Read it before you answer a request, not afterwards, because the answering is what sets the precedent. The true up clause. Whether an overage is priced at list or at your contracted discount, from what date it is charged, and whether there is any cure period. We just priced that difference at six hundred thousand on a single finding. Both of these were negotiable, once, at signature, when there was no dispute and nobody in the room was paying attention to them. That is exactly why they were conceded. Notice and form is worth dwelling on: there is usually a gap between what the clause obliges you to provide and what an auditor asks for in practice, and that gap is yours to manage, politely and in writing. And if you ever get the chance to renegotiate the framework, these two clauses are worth more than another point of discount. Let's hear that put properly.
Guest analyst clip. There are two clauses in your SAP agreement that decide how every disagreement in this course actually ends, and most customers have never read either of them. The first is the audit or measurement clause. It says what SAP can ask for, how often, with how much notice, and in what form. That last part matters more than people realise. There is usually a meaningful difference between what the clause obliges you to provide and what an auditor asks for in practice, and the gap between those two is entirely yours to manage, politely and in writing. The second is the true up clause. This is the one that decides what happens when you are over. Does the overage get priced at list, or at your contracted discount? Is it charged from the day you exceeded, or from the day it was found? Is there a cure period? Those are not academic questions. On a large finding the difference between list and contracted pricing can be the majority of the settlement. And here is the uncomfortable part. Both of those clauses were negotiable, once, at signature, when nobody was thinking about them because there was no dispute yet. If you are ever in a position to renegotiate the framework, those two clauses are worth more than another point of discount.
Worth more than another point of discount. That is a genuinely useful way to think about negotiation priorities, and it runs against instinct, because a discount point is visible and a clause is not. A discount applies to what you buy. The true up clause applies to everything that goes wrong for the next decade, on volumes nobody has forecast yet. One is a number on this deal, the other is the pricing basis for every future surprise. Put them in that order when you decide what to spend your negotiating capital on.
Reading an order form. Four passes, in this order, and you can do it on your own largest one tonight. Pass one, what and how much. The products, the quantities, and the metric each line is counted on. That, and only that, is your entitlement. Pass two, which definitions. Find the price list version referenced and write it down, because it decides what every metric on that page actually means. Pass three, the commercials. Discount, term, currency, support basis. Note your discount specifically, because it is the number that governs any later true up conversation, as we just calculated. And pass four, the special terms. Price holds, caps on uplift, additional rights, restrictions. Pass four is the one everybody skips and it is the one that most often contains money, because rights your predecessors negotiated years ago are completely worthless if nobody currently knows they exist. I have seen customers pay for something they were already entitled to, twice, because the entitlement was in a document nobody had read since it was signed.
Five traps in the paper. One, the incomplete set. Amendments nobody kept. If you cannot prove a right exists then in practice it does not, and the burden of proof sits with you, not with SAP. Two, the undated definition. Arguing about a metric without first establishing which price list version governs. You can be completely right about the facts and still lose the argument. Three, policy quoted as contract. Guidance documents and licensing explainers presented as though they were rules. Persuasive in a meeting, worthless in the paper, and the correction costs you nothing but a polite question. Four, the forgotten protection. A price hold or an uplift cap that quietly expired, or that is still live and nobody is enforcing. Both happen, and the second one is free money you are declining. And five, signing before reading. The renewal paper that replaces your old terms with current standard ones. Always diff a renewal against what it supersedes, which brings us to the last knowledge check.
Last knowledge check. A renewal document arrives that consolidates several old agreements into one new framework. What matters most before signing? A, that the discount on the new paper is at least as good as the old. B, that every special term and protection in the old documents is carried forward explicitly. C, that the new agreement uses SAP's current standard terms, for consistency. D, that the total contract value does not increase. Pause here, and think about what a consolidation quietly replaces.
B. Every special term and protection carried forward explicitly. A consolidation replaces the documents that contained your negotiated protections, and anything not carried forward is simply gone. Not disputed, not weakened, gone. A and D are the visible numbers, and that is exactly why they absorb all the attention in the room while the thing that matters passes unexamined. C is the trap stated as a virtue, and I want you to notice how attractive it sounds. Current standard terms, for consistency. Standard terms are standard because they are the terms SAP prefers, refined over many negotiations, and consistency is a benefit to whoever wrote them. And here is the connection back to the start of this session. You cannot check any of this without a complete library. If you do not know what your old documents say, you cannot possibly know what you are giving up.
So, the library. Five characteristics, and the first one is the most important. It is a folder. Every agreement, amendment, and order form, plus a copy of each price list version those orders reference. No system, no tool, no procurement exercise. One summary sheet: what we own, under which document, on which metric, at what discount, with which special terms. One page, and it is the page you take into every meeting. Somebody owns it, and updates it when anything is signed, because a library nobody maintains is a snapshot and snapshots go stale inside a year. Completeness beats sophistication, and this matters: the awkward old documents are precisely the ones carrying your protections, so a tidy partial set is worse than a messy complete one. And it changes the tempo. Answers in an afternoon instead of a fortnight, which changes the tone of every conversation you have. One last clip on what that actually looks like.
Guest analyst clip. Let me describe what a good contract library actually looks like, because people imagine something far more elaborate than it is. It is a folder. Inside it, every signed agreement and amendment, every order form, and a copy of each price list version that those order forms reference. Alongside it, one summary sheet: what we own, under which document, on which metric, at what discount, with which special terms. That is it. No system, no tool, no project. What makes it valuable is not sophistication, it is completeness and currency. It has to include the awkward old documents, and it has to be updated when something is signed, which means somebody owns it. Two things happen once it exists. The first is speed. When a question arrives, you answer it in an afternoon instead of a fortnight, and that changes the tone of every conversation you have. The second is subtler. When you can see all of it in one place, you start noticing things. Special terms somebody negotiated in two thousand and fourteen that you have never used. A price hold nobody remembered. A cap on an uplift. I have found clauses worth six figures a year sitting in documents the customer already owned and had simply lost track of.
Clauses worth six figures a year, in documents the customer already owned. That is the part I would take to whoever controls your budget, because it reframes this from an administrative tidy up into a search for things you have already paid for. And it makes the business case trivially easy. You are not asking for a tool or a headcount. You are asking for a few weeks of somebody's time to collect documents that are already yours, in order to find out what you are entitled to. I have never seen that request refused once it was framed that way.
Three sentences. Only signed documents create obligations, and the stack has a shape: the agreement, the order forms, the price list, the use rights, and the support and cloud schedules. Definitions are dated, so the price list version your order references decides what your metrics mean, however old that version happens to be. And the measurement clause and the true up clause decide how every dispute ends, and both were negotiable at a moment when nobody was paying attention. Next session closes module one. Measuring the estate: USMM, LAW and SLAW, the self declaration engines, and the STAR classifier. How SAP actually counts you, and how you count yourself first.
Homework before session five, about an hour, and this one compounds with everything you have already collected. One, assemble what exists. Every agreement, amendment and order form you can find, in one folder, and write down what you suspect is missing. The gaps are as informative as the documents. Two, date your definitions. For each order form, note which price list version it references, and ask SAP for a copy of any you do not hold. You are entitled to it. Three, find the two clauses. Locate the measurement clause and the true up clause in your agreement and read them properly, once, with a pen. Four, do the four passes on your largest order form. What, definitions, commercials, special terms. And five, list the protections. Any price hold, uplift cap, or additional right you find, and then check two things: is it still live, and is anybody actually enforcing it. That last check has paid for a lot of people's time.
Five guides, all on redresscompliance dot com. Negotiating SAP contracts for audit protection covers the two clauses from slide eleven and the language worth asking for when the paper is open. SAP contract negotiation fundamentals explains how the stack gets used commercially and where the leverage sits in each document. The global licence agreement strategy piece is directly relevant to knowledge check three, on what a consolidation gains you and what it quietly costs. The contract negotiation playbook is the full version of all of it. And establishing an internal SAP compliance program covers where the contract library sits in a wider governance model and who should own it. That is session four, and that is the paper. Next time we close module one by looking at how SAP actually measures you. See you there.