Uncategorized

How to Negotiate a SAP License Audit

Negotiate a SAP License Audit

How to Negotiate a SAP License Audit

After the audit data is submitted and SAP has analyzed it, you will receive the results, which may include an audit report or a compliance letter. If the outcome is that you are fully compliant, congratulations, youโ€™re done! But more often, SAP will identify some shortfall or compliance issue. This is where negotiation comes into play.

Negotiating the results of an SAP audit is a delicate process. The goal is to resolve any compliance gaps in a way that minimizes cost and operational impact for your organization, while satisfying SAPโ€™s requirements.

Remember, an audit finding is not the end of the story โ€“ itโ€™s essentially the start of a commercial discussion.

How you approach that discussion can significantly influence the financial outcome.

Hereโ€™s how to effectively negotiate a settlement or true-up with SAP after an audit:

1. Analyze and Validate the Audit Findings

Why: Knowledge is power. Before any negotiation, you must thoroughly understand what SAP is claiming and verify its accuracy. Do not assume the auditorsโ€™ calculations are 100% correctโ€‹.

  • Carefully review the audit report,ย line by line, going through the findings. Identify exactly which licenses are short (e.g., โ€œ50 Professional Users neededโ€ or โ€œEngine ABC is over by two unitsโ€) and which compliance areas are cited (indirect use, user misclassification, etc.).
  • Reproduce the Numbers: If possible, reproduce SAPโ€™s calculations with your data. For example, if SAP says you have 1,050 professional users but only 1,000 licensed, cross-check against your LAW report or internal records. See where those extra 50 are coming from. It could be a mistake, such as double-counting, or indeed a genuine gap.
  • Identify Errors or Ambiguities: Look for anything that seems out of place. Maybe SAP counted some users as Professional that you believe should be Employee licenses โ€“ note those. Or SAP included a system that was supposed to be out of scope. Perhaps an engineโ€™s usage was inflated due to a one-time spike, such as a test run. Document these potential discrepancies.
  • Internal Stakeholder Input: Discuss the findings with relevant stakeholders. IT might explain usage nuances, procurement/legal can confirm whatโ€™s contractually allowed, etc. This helps you differentiate between legitimate compliance issues and contestable items.
  • Example: SAP claims you need 100 additional โ€œLimited Professionalโ€ user licenses. Upon review, you find that 60 of those users are former employees who left but werenโ€™t locked in the system, so they should not require licenses. This is a strong point to negotiate โ€“ you can show that those users should be excluded (with evidence of their termination dates) and reduce the scope of non-compliance by 60 licenses.

By doing this homework, you arm yourself with facts. You can then approach SAP not as a passive recipient of a bill, but as a knowledgeable partner ready to discuss the findings.

2. Set Your Objectives and Team for Negotiation

Why: Going into a negotiation without a clear goal or the right people can result in concessions that you could have avoided.

Plan your negotiation strategy.

  • Determine Your Endgame: Decide what a โ€œwinโ€ looks like. Is it minimizing upfront cost? Spreading payments over time? Obtaining extra value (like new software) for the money youโ€™ll spend? For example, your primary goal might be to avoid a huge one-time expense that blows your budget, so you aim for a payment plan or a deal that includes a discount on a future purchase.
  • Know Your Limits: Establish your BATNA (Best Alternative to a Negotiated Agreement) โ€“ basically, at what point would you rather refuse SAPโ€™s offer and consider other actions (such as legal pushback or even, in extreme cases, migrating off SAP in the long run). While abandoning SAP is rarely practical, having a walk-away threshold is useful. It could be a dollar amount or a principle (e.g., โ€œWe will not pay maintenance back-charges for these 50 users because they were misclassified; going forward, we will only pay for what is due.โ€).
  • Assemble the Negotiation Team: include members from IT (to address technical points), procurement and licensing (to handle purchasing and pricing aspects), and legal (to address contract implications). If possible, also involve an independent SAP licensing expert or a consultant with negotiation experienceโ€‹. They can bolster your arguments or suggest creative solutions from past cases.
  • Executive Support: Ensure you have executive backing โ€“ for example, the CIO or CFO is aware of the situation and supports your negotiation stance. SAP may try to escalate discussions to an executive level, so align internally first.
  • Internal Unity: Decide on roles โ€“ who will lead the discussions, who will take notes, and who will speak on specific topics. A united front is important. Mixed messages to SAP (e.g., the IT guy says one thing, while procurement says another) can be exploited by the auditor or a sales representative.

Having clear objectives prevents you from being swayed by SAPโ€™s pitches during negotiation. It also helps to prioritize: maybe you can concede on a minor point to hold firm on a major one.

Read How to Prepare for a SAP License Audit.

3. Engage with SAP โ€“ Communication Strategy

Now itโ€™s time to open the negotiation dialog with SAP. Typically, after sending the audit report, SAP will either send a quote for the required licenses or request a meeting to discuss the next steps.

Hereโ€™s how to handle it:

  • Ask for a Discussion Meeting: Itโ€™s often helpful to have a meeting or call with SAPโ€™s audit team (and possibly your SAP account manager) to review the findings. In this meeting, listen first. Let SAP explain their viewpoint and proposed remediation (they might say โ€œYou need to purchase X licenses, costing $Yโ€ or โ€œWe have an offer: if you purchase these new licenses, weโ€™ll waive this and thatโ€). Take notes.
  • Present Your Analysis: Respond with your analysis, focusing on areas where you disagree or need clarification. Be factual and non-confrontational: โ€œWe reviewed the user list and found several duplicates and inactive accounts included in the count. Weโ€™d like to adjust the compliance gap from 100 users to 30 users based on this corrected dataโ€‹.โ€ Provide evidence if you have it; you can share a sanitized list or summary. By doing this, you establish that youโ€™re not blindly accepting everything โ€“ you have data to back your stanceโ€‹.
  • Emphasize Compliance Efforts: Highlight what you have done and are doing to stay compliant: โ€œWe have a governance process, and as you saw, weโ€™ve cleaned up a lot of users. These remaining gaps are ones we genuinely need to address, and we are willing to address them โ€“ but we want to do so in a way that makes sense for both sides.โ€ This sets a collaborative tone โ€“ youโ€™re not refusing to comply; youโ€™re just negotiatingย howย to do so.
  • Explore Solutions Together: Indicate youโ€™re open to different solutions. Instead of just โ€œwe wonโ€™t pay this,โ€ guide the conversation to alternatives: โ€œFor those 30 users over license, perhaps we can reclassify some as lower types and purchase a smaller number of higher-level licenses. Also, we are planning to implement the AP XYZ module next year โ€“ maybe we can factor that into this discussion.โ€ This invites SAP to think in terms of a broader commercial relationship, not just an audit fine.
  • Keep Sales and Audit Linked: Be aware that SAPโ€™s audit team often collaborates with the sales and account teams at this stage. They might offer you a deal such as: โ€œIf you sign a contract for S/4HANA migration or some cloud subscriptions, we will resolve the audit findings with minimal charges.โ€ This can be an opportunity or a pitfall. Hear it out, but donโ€™t commit right away. Get all proposals in writing.

Negotiation Tone: Stay professional, factual, and firm. Itโ€™s a negotiation โ€“ you can be friendly, but also assert your points. Suppose SAP sees you have done your homework (e.g., you cite a specific contractual clause or you have a detailed user analysis). In that case, theyโ€™ll realize youโ€™re a serious customer who canโ€™t be easily pressured into overpaying.

4. Consider Creative and Long-Term Solutions

When negotiating, donโ€™t limit the discussion to โ€œLicenses A, B, C cost $ X.โ€ Use this chance to look at the bigger picture of your SAP relationship and future needs.

  • Trade Compliance Gaps for Future Investment: SAP often prefers customers to purchase new products or upgrades (which helps SAPโ€™s sales goals) rather than just pay penalty fees. For example, suppose youโ€™re out of compliance on some licenses worth $ 1 M. In that case, SAP might be amenable to you spending $1M (or possibly less) on something like additional SAP modules, cloud services, or an S/4HANA conversion, instead of a straight-up bill. This way, you get new functionality and SAP meets revenue targets. If such a product were already on your roadmap, it could be a win-win. However, ensure the new purchase truly brings value to you and isnโ€™t just shelfware.
  • Digital Access Adoption Program (DAAP): If indirect access is a major issue in the audit, SAPโ€™s DAAP (if still available) could be leveragedโ€‹. Under DAAP, SAP offered customers a way to convert indirect usage to the digital access model, often with incentives, such as free document licenses. Negotiating to enter DAAP might resolve the immediate compliance issue and put you on a clearer path in the future. Evaluate if SAP is pushing this and whether it benefits you long-term (DAAP could reduce uncertainty around indirect access fees).
  • Bundling and Discounts: Donโ€™t hesitate to negotiate for a better price. Just because the audit report says list price for 100 licenses doesnโ€™t mean you must pay the list price. Ask for discounts or waivers, citing your history as a loyal customer or volume of existing investment. Often, the SAP account manager can approve discounts, especially if youโ€™re also buying something new. Aim to bundleย audit true-up licenses with other purchases to get a better overallย discount. For instance, โ€œWeโ€™ll purchase the 100 Professional users and also 50 cloud licenses for SuccessFactors; in exchange, we want a 30% discount off the list price on the whole package.โ€
  • Maintenance Fee Waiver: If you owe back maintenance (for the period you were underlicensed), try to negotiate it down or waive it. SAP sometimes waives maintenance or offers to start maintenance on newly purchased licenses, saving you that cost. This is a common concession customers seek.
  • Payment Terms: If the spend is substantial, negotiate more favorable payment terms. Rather than paying all in Q2, you could schedule payments over a year or align them with your fiscal year. Alternatively, consider committing to a multi-year renewal, which can help spread the costs.
  • Non-monetary Asks: You can also consider negotiating contract terms โ€“ e.g., an addendum clarifying an indirect use clause to protect you in the future, or ensuring some flexibility like a temporary license allowance for a project. During negotiations, SAP might agree to such things, since they want to close the audit issue.

Throughout these, keep in mind your leverage: SAP initiated the audit to enforce compliance, but they also want to keep you as a satisfied customer (or sell you more). If you show a willingness to become compliant (i.e., youโ€™re not refusing outright), the conversation becomes about how youโ€™ll comply in a way that works for both parties.

5. Common Pitfalls and How to Avoid Them

Be mindful of these mistakes that organizations sometimes make in audit negotiations, and take steps to avoid them:

  • Accepting SAPโ€™s First Offer Too Quickly: The initial proposal from SAP (whether itโ€™s a bill or a sales pitch) is often not the best they can do. Donโ€™t rush to agree because of fear or pressure. Negotiate methodically. Everything is negotiable.
  • Insufficient Documentation: If you go into talks without documentation, youโ€™re negotiating from a weaker position. For example, saying โ€œwe think you over-counted usersโ€ without proof wonโ€™t carry much weight. Always back up your claims with data or references, such as usage reports or contract snippetsโ€‹.
  • Over-Focusing on Short Term: Donโ€™t just aim to โ€œget the audit off our backs nowโ€ by buying something unnecessary. Consider how this settlement affects your long-term SAP strategyโ€‹. If you pay a lot now for shelfware, youโ€™ll suffer later. It might be better to invest in licenses that align with your plans.
  • Ignoring Indirect Use in Settlement: If the audit identified indirect access issues but the immediate settlement doesnโ€™t address them (e.g., SAP says โ€œjust buy 100 user licenses,โ€ which doesnโ€™t cover indirect scenarios), you could face the same issue again. Try to include a resolution for indirect use โ€“ whether via new licenses or a contractual clarification โ€“ so it doesnโ€™t haunt you next yearโ€‹.
  • Not Getting It in Writing: Once you reach a verbal understanding with SAP, ensure the final agreement (contracts, quotes, etc.) reflects everything. If SAP promised something (โ€œwe wonโ€™t charge maintenance on these licensesโ€ or โ€œwe consider the matter closed after this purchaseโ€), get that explicitly written into the agreement or email. Memories fade; paper doesnโ€™t.
  • Rushing Under Deadline:ย SAP might put time pressure (โ€œthis offer is only valid if you sign by the end of the quarterโ€). Be cautious โ€“ itโ€™s often a sales tactic. While timelines can be real, donโ€™t let arbitrary deadlines force a bad decision. If needed, ask for a short extension citing internal approval processes.

6. Finalizing the Agreement

When both you and SAP come to an acceptable solution, formalize it properly:

  • You may receive a revised audit compliance letter stating what was agreed upon (e.g., โ€œthe customer will purchase X licenses to resolve the shortfall, and SAP waives any other claims for the periodโ€). Check this wording to ensure it truly closes the audit.
  • You will get a quote or contract for any new licenses. Review it against what was negotiated โ€“ ensure correct quantities, discounts applied, and maintenance terms are accurate, etc.
  • Sign off and ensure you receive confirmation from SAP that this resolves the audit and you are now in compliance.

After itโ€™s all done, internally document the outcome and update your license inventory. If you added licenses, incorporate them into your plan. If you got special terms or exceptions, note them for future reference.

Negotiation Example: Company ABC was founded 200 years ago. It has 10,000 professional users. SAPโ€™s first approach was to buy 200 at the list price of $2M, plus back maintenance of $400K. ABC analyzed the data and found that 50 were duplicates and 50 were inactive, so the actual shortage was 100. They also knew they needed to expand an SAP module soon.

They negotiated to purchase 120 Professional users (covering the 100 and a buffer) at a 25% discount, with SAP agreeing to waive all back maintenance. Additionally, ABC committed to a pilot of an SAP cloud product.

The final cost was approximately $1.2M, down from the initially proposed $2.4M, and the deal included future-oriented value. All of this was captured in a letter of agreement. This negotiation saved ABC over $1M and left them better positioned.

Recommendations (Negotiating an SAP Audit)

  • Base Negotiations on Data: Enter talks with a solid understanding of the facts. Double-check SAPโ€™s findings against your data and be prepared to present evidence of any discrepancies. Negotiations grounded in data, such as user logs or contract language, will be far more effective than generic pleas for leniency.
  • Leverage Experts and Allies: If youโ€™re not confident, involve an SAP licensing expert or consultant in the negotiationโ€‹. Their experience can uncover negotiation angles you might miss. Also, use your SAP account manager as an ally โ€“ they often want to maintain a good relationship and can help get you a better deal internally, especially if you frame it as a long-term partnership discussion.
  • Think Beyond the Audit: Turn the Audit Settlement into an Opportunity. For example, if you were considering an S/4HANA upgrade or a new SAP module, bring it into the negotiation. You might get incentives or credits for it as part of the dealโ€‹. Aim for a resolution that not only fixes compliance now but also aligns with your future IT roadmap (so the money you spend provides future benefits).
  • Aim for a Win-Win:ย Show SAP that you’re committed to compliance, but need a solution that works for your business. Propose creative alternatives: โ€œInstead of buying 100 of Product A, which we donโ€™t use, how about 50 of A and 50 of Product B (which we plan to deploy)?โ€ This can meet SAPโ€™s revenue goal while giving you useful licensesโ€‹. A cooperative approach can yield concessions such as discounts, extended payment terms, or additional support from SAP.
  • Document the Outcome: Once you reach an agreement, ensure it is documented in writing โ€“ including what licenses will be purchased, any discounts, what issues are considered resolved, and any promises (such as waived fees or future use rights). This audit closure letter or contract amendment is your safeguard. In future audits or if personnel change, you have a record to prevent the same issue from being raised again erroneously.
  • Learn from and Prevent Recurrence:ย After negotiating, conduct an internal lessons learned review. Why did the compliance gap occur, and how can you prevent it? Consider implementing new controls for user management or investing in better license management tools. Communicate to management the value saved through negotiation (to underscore the importance of SAM efforts). Preparing and negotiating well not only saved costs in this audit but also sets a precedent for how to handle any future audits calmly and strategically.

Do you want to know more about our SAP Advisory Services?

Please enable JavaScript in your browser to complete this form.
Author
  • Fredrik Filipsson has 20 years of experience in Oracle license management, including nine years working at Oracle and 11 years as a consultant, assisting major global clients with complex Oracle licensing issues. Before his work in Oracle licensing, he gained valuable expertise in IBM, SAP, and Salesforce licensing through his time at IBM. In addition, Fredrik has played a leading role in AI initiatives and is a successful entrepreneur, co-founding Redress Compliance and several other companies.

    View all posts