Why Partner Contract Terms Deserve Extra Attention
Buying SAP software through a partner or reseller can save you money — but it can also cost you control if the contract isn’t right. SAP customers must be extra vigilant because partner agreements often introduce new clauses, responsibilities, and risks that don’t appear in direct contracts with SAP.
In a reseller deal, you’re effectively managing two relationships: one with the partner (for the sale and commercial terms) and one with SAP (for the software rights and support). This creates a relationship triangle – Customer → Partner → SAP – that needs careful navigation.
A partner’s contract should mirror SAP’s standard terms, not replace them. Remember, even if you buy licenses indirectly, you’re still running SAP software and bound by SAP’s rules. Any contract clause that strays from SAP’s norms could undermine your protections or add hidden obligations.
The bottom line: don’t assume everything is “standard” just because it involves SAP. Approach the fine print with a slightly skeptical eye and ask, “Is this how it works in a direct SAP deal?”
Conversational Tip: “When you buy through a partner, your signature is with them — but your risks are still with SAP.”
Read our comprehensive guide to SAP partner licensing and negotiations, Negotiating with SAP Partners & Resellers: Getting the Best Deal Indirectly.
Confirming SAP’s Standard License Terms Still Apply
The most critical safeguard in any SAP partner deal is ensuring that SAP’s own license terms still govern your software usage. SAP publishes a standard Software Use Rights Agreement (SURA) or End User License Agreement (EULA) for its products.
These are the rules that define how you can use the software, how audits work, and what protections you have. In a reseller contract, you should demand that SAP’s SURA/EULA is explicitly referenced or attached. If the partner’s paperwork doesn’t clearly say “SAP’s standard license terms apply,” treat that as a red flag.
Why is this so important? If SAP’s terms are missing or overridden, you risk losing key protections. For example, SAP’s standard EULA includes clauses on permissible use, ownership of the software, and SAP’s right to audit your usage.
You want those terms to remain intact. A good partner agreement will state that all licenses are provided under SAP’s standard terms without modification. If you don’t see that, the partner might be inserting their own rules or limitations on the software – something you absolutely want to avoid.
Sample Clause: “SAP’s standard Software governs all licenses resold under this Agreement Use Rights Agreement without modification.”
Take the extra step to verify with SAP in writing that your licenses are recognized as standard. It’s not overkill to ask the partner to confirm with SAP that you (the end customer) will be listed as the licensee in SAP’s system and that SAP can audit and support you just like a direct customer. This confirmation ensures there’s no confusion about your status and rights.
- SAP license terms explicitly referenced: The contract should cite SAP’s SURA or EULA and include it as an exhibit or link.
- No custom license limitations: Ensure the partner hasn’t slipped in any clause that changes usage rights or imposes new limits beyond SAP’s standard agreement.
- SAP’s audit rights intact: Confirm that nothing in the partner’s contract restricts SAP’s normal compliance monitoring or audit processes. Ideally, SAP’s standard audit clause should still apply to you.
Conversational Tip: “If the contract doesn’t mention SAP’s license terms, assume you’ve lost them.”
How to Procure: Direct vs Reseller – Pros and Cons – Choosing the Right SAP Purchase Route.
Understanding Support and Maintenance Terms
When buying through a reseller, support and maintenance can be unclear if not clarified. Typically, SAP provides the actual support (delivering patches, updates, and helpdesk services), while the partner might handle the billing or act as a go-between. Make sure your contract spells out exactly how support will work, so you’re not left without help when you need it.
First, check that the support level is clearly stated. SAP generally offers tiers like Standard Support or Enterprise Support. Your contract should specify the level you’re getting and typically list it as a percentage of the license cost (for example, 22% of license fees annually for standard support). This percentage should match SAP’s official support pricing – a partner shouldn’t charge more for the same level of support. If a partner tries to bundle in their own support services, ensure it doesn’t degrade what you’d normally get from SAP.
Next, clarify how support fees are handled. In a normal direct deal, you pay SAP for maintenance, and SAP supports you. In a partner deal, you might pay the partner, who then passes the maintenance fee to SAP. Insist on transparency: the contract should state that the maintenance fees will be forwarded to SAP to ensure your support remains active. If the partner is keeping a portion, understand why (e.g,. are they providing any additional support?). You should still be guaranteed full access to SAP’s support portal (often referred to as OSS) and all the updates and fixes you’re entitled to.
Also, confirm your escalation path for support issues. If something is severely wrong, can you go directly to SAP? Typically, yes – enterprise customers usually can log high-priority tickets with SAP. The contract should not prevent you from contacting SAP or require all support calls to go through the partner. Ideally, it will clarify that while the partner may coordinate support, you retain direct access to SAP support resources.
- Support level and cost: The agreement specifies your support plan (Standard vs. Enterprise) and the rate (as a % of license price) so you know you’re getting the official SAP support package.
- Who delivers vs. who bills: It’s clear that SAP delivers the support services, even if the partner handles billing or initial requests. The contract might state that SAP is the “supplier” of maintenance, with the partner acting as a reseller, facilitating it.
- Escalation and portal access: You have written assurance that you can access SAP’s support portal and escalate issues to SAP if needed, just like any direct customer would.
Pro Tip: “Partners can invoice maintenance — but SAP still runs the helpdesk.”
How to get the best price, Getting Best Discounts via Partners: How to Make SAP Resellers Compete and Win on Price.
Clarifying Audit and Compliance Rights
SAP is known for its strict compliance and audit rights. These rights remain in force no matter who you buy from. An SAP partner cannot waive or alter SAP’s ability to audit your use of the software. Make sure the contract reflects this reality. Essentially, the partner should not be adding any new audit provisions of their own, and nothing should dilute SAP’s standard compliance clause.
In practice, SAP’s standard license agreement gives SAP the right to audit your software usage to ensure you’re compliant (for example, not exceeding user counts or using unlicensed components). In your partner agreement, verify that SAP retains sole audit authority.
This means only SAP (or an auditor on SAP’s behalf) will conduct license audits – not the partner. If you see any language suggesting the partner can perform audits or requires broad system access beyond what’s needed for support, push back hard. You don’t want to agree to two masters auditing your systems.
Also, be cautious about data access clauses. A partner might need some access for support or implementation assistance, but they shouldn’t have open-ended rights to review your usage data. Ensure any data access is limited to fulfilling support obligations and not for fishing expeditions on license compliance.
You control your systems; the partner doesn’t get to poke around unless it’s necessary and agreed for a specific purpose.
- SAP is the only auditor: The agreement should clearly state (or not contradict) that SAP retains the right to audit your software usage. No extra partner-driven audits should appear.
- No duplicate compliance clauses: Avoid any clause where the partner imposes their own compliance checks or penalties. Your compliance duty is ultimately to SAP under SAP’s terms, not some new scheme by the reseller.
- Limited system access: The partner’s access to your environment is restricted to what’s needed for support/services. There’s no blanket permission for the partner to review usage data or conduct audits on SAP’s behalf (unless SAP officially delegates something, which would still come through SAP’s process).
Conversational Tip: “If the partner wants audit rights, that’s not compliance — that’s overreach.”
Avoiding Reseller-Specific Fees and Hidden Costs
One reason companies go through partners is often to get a better price or additional services. However, those savings can vanish quickly if a reseller slips in extra fees. Be on the lookout for any charges in the contract that wouldn’t exist in a direct SAP purchase.
Common culprits include “administration fees,” “account management fees,” “compliance service charges,” or generic “service fees” on top of the license and maintenance costs.
Ask the partner for a full breakdown of all costs. Every line item on a quote or order form should have a clear purpose. Licenses have a cost, maintenance has a cost – beyond that, question anything else.
For instance, if there’s a line for “Reseller Service Package,” get details or have it removed if it’s not something you explicitly need. A reputable partner should not hide margins in obscure fees; they make their money from the discount SAP gives them and any legitimate services you agreed to (like consulting or training).
Also, clarify the payment routing for support fees. As mentioned earlier, if you pay maintenance to the partner, ensure that 100% of the appropriate portion is passed to SAP to prevent your support from lapsing.
The contract or invoice should ideally separate license fees, SAP maintenance fees, and any partner services. That way, you can see exactly what goes where. If a partner is bundling things together, ask for separation – you don’t want to unwittingly pay a “premium” that’s actually just extra margin for them.
Finally, lock in a principle: no additional fees at renewal or later unless agreed in advance. Sometimes a deal looks good upfront, but when the renewal comes, a partner might try adding a “processing fee” or mark up SAP’s standard maintenance increase.
Insist in the contract that renewals will be calculated per SAP’s standard policies (for example, only the official annual index increase) with no new fees added.
- Transparent pricing: The contract or quote provides a clear breakdown of costs. You know what you’re paying for licenses and support, and any separate services are listed plainly.
- No non-SAP fees: Verify that you’re not being charged any fees that SAP itself wouldn’t charge. If something looks unfamiliar (beyond license and maintenance), question it.
- Clear payment flow: It’s defined how maintenance payments are handled. Ideally, maintenance money flows to SAP to keep your support active. There should be no ambiguity in who gets paid for what.
Example Clause: “No additional reseller or administrative fees shall apply beyond SAP’s standard license and maintenance charges.”
How to switch partners, Switching SAP Resellers: How to Change Partners Without Disrupting Support or Licensing.
Defining Accountability: Who’s Responsible for What
In an SAP partner deal, responsibilities can get confusing if not explicitly defined. Never assume each party’s duties are understood – make them plain in the contract.
The partner might be your primary vendor for the transaction, but remember that SAP is the one creating the software and ultimately providing support and enforcement. To avoid finger-pointing later, lay out who is responsible for what.
Break down the roles clearly:
- Partner responsibilities: The partner is typically responsible for the commercial relationship. That includes delivering the licenses (provisioning the software or license keys), correctly invoicing you, and perhaps providing local services like implementation or training if that’s part of their offering. If the partner is also an implementation consultant, their accountability for project success should be in a services agreement. In the context of the license reseller agreement, the partner should commit to facilitating support, communicating issues to SAP, and handling any paperwork with SAP on your behalf.
- SAP responsibilities: SAP remains responsible for the product itself – the software’s performance, the patches, and updates, and honoring the license and support terms. SAP will be the party delivering fixes and responding to support tickets. SAP also holds the authority on license compliance (they decide if you’re correctly licensed or not). Ensure the contract doesn’t accidentally shift any of SAP’s obligations away. For example, if something goes wrong in the software (a bug or security issue), SAP should ultimately address it under support.
- Customer responsibilities: Your side is responsible for using the software within the agreed terms (compliance), managing your users and usage, and paying the bills on time (to the partner for licenses and maintenance). If an audit finds you out of compliance, you must rectify it – the contract should state you’ll do so under SAP’s standard compliance process.
It’s wise to insert language that if any dispute or confusion arises about licenses or support, SAP’s word is final on those matters, since they own the intellectual property.
That prevents a scenario where a partner may tell you one thing about usage rights that conflicts with SAP’s interpretation. You want it clear that SAP’s interpretation of its license terms governs.
Also, establish a clear escalation path. If you have an issue (say a serious outage or a disagreement about usage), know who to call first and how to escalate it.
For example, you might report problems to the partner initially, but if they aren’t resolved, you escalate directly to SAP. The contract can name contacts or at least specify that critical issues should be raised directly with SAP support or SAP account management.
- Roles and responsibilities documented: The agreement spells out duties – e.g., the partner will handle billing and ordering, SAP will deliver support services, and the customer will adhere to usage terms, etc. No major task is left in a gray area.
- Defined escalation contacts: It’s clear how issues are escalated. If your issue is with the software, you know how to engage SAP (even if you loop in the partner). If it’s a commercial issue (like an invoice problem), the partner is your point of contact.
- SAP referenced in disputes: The contract text might include a clause similar to the one below to reinforce SAP’s ultimate authority over its product and licensing.
Sample Wording: “In case of any license or support dispute, SAP shall remain the final authority regarding entitlement, use, and compliance.”
Conversational Tip: “Never assume the partner will handle SAP disputes — they’re your intermediary, not your advocate.”
Renewal and Transfer Clauses
When the initial purchase is done, you’ll eventually face renewals (especially for support/maintenance) and maybe changes down the road. Even through a partner, you want those future stages to follow SAP’s standard practices and preserve your flexibility.
Focus on renewal terms first. SAP typically has a predictable maintenance renewal process – usually annual, with a standard price increase tied to inflation or an index (often called CPI, Consumer Price Index, or a fixed percentage).
Your partner agreement should not impose a higher increase or a different schedule than SAP’s norm. For instance, if SAP’s policy is a maximum 3% increase per year on maintenance, the partner shouldn’t have language that allows them to hike it by 10%.
Make sure the contract either references SAP’s maintenance policy or explicitly caps increases to match SAP’s standard. This keeps your long-term costs predictable and fair.
Next, consider the flexibility to switch partners. Circumstances change – you might find another reseller offering a better deal, or your current partner might not meet expectations. You should be able to transfer your business to another authorized SAP partner or even back to SAP directly for future purchases or renewals.
Check that nothing in the contract locks you in with that specific partner. There should not be any penalty or loss of rights if, say, at renewal time, you decide to go with a different reseller.
The licenses are ultimately SAP’s, and as long as you remain compliant and continue paying maintenance, SAP will usually allow you to switch who services your account. It’s wise to get confirmation (even an email from SAP or a clause in the contract) that your status as the license owner is independent of the reseller. In other words, you own the licenses, not the partner.
Also, get it documented that SAP acknowledges you as the end customer. We mentioned this earlier, but it’s worth repeating in the context of transfer: if you ever need to change partners or if the partner goes out of business, SAP should still recognize your entitlements.
A quick way is to ask for an SAP license confirmation letter or certificate after your purchase. This document would state that you have purchased SAP licenses for X product, quantity Y, under your name.
Having this means even if the partner disappears, you have proof from SAP of what you own.
- Standard renewal pricing: The agreement aligns with SAP’s normal renewal terms (e.g., only standard CPI increases on maintenance, no surprise fees at renewal).
- Ability to switch resellers: It’s either explicitly stated or at least not prohibited that you can change your reseller or go direct without losing support or warranties. Your licenses should be portable within SAP’s authorized channels.
- License ownership confirmed: You have documentation or contract language that makes clear you are the licensee. SAP’s records will show your company as the owner of the licenses, ensuring continuity regardless of the partner’s status.
Conversational Tip: “The goal is simple — buy through a partner, but stay protected by SAP.”
5 Contract Checks Before Signing an SAP Partner Agreement
In summary, before you put pen to paper (or click to sign) on an SAP reseller agreement, run through this final checklist of critical contract terms:
- SAP license terms are intact: Confirm SAP’s standard SURA/EULA is referenced in full, with no alterations. This preserves your baseline rights and obligations exactly as if you bought from SAP.
- Support goes through SAP: Verify that support and maintenance truly flow from SAP. You should receive the same quality of support and access, even if the partner bills you.
- No extra audits or admin clauses: Remove any partner-specific audit rights or mysterious “administrative” clauses. The partner shouldn’t have any more oversight over your use than SAP does.
- Accountability is crystal clear: Clarify who handles what between SAP and the partner. You want no doubts about who to call for support, or who resolves a license issue.
- Your ownership is documented: Get in writing that you own the licenses and have renewal rights. You should be able to continue with SAP or another partner in the future without hassle.
By checking these key areas, you can enjoy the benefits of buying through a partner (like potential discounts or local support) while avoiding the common pitfalls.
It ensures that even though a reseller is involved, you remain in control and protected just as if you were dealing with SAP directly.
Read about our SAP Advisory Services
