SAP Digital Access for IoT and Automation

SAP Digital Access for IoT and Automation

SAP’s Digital Access model shifts SAP ERP licensing from a user-based to a document-based metric. For enterprises connecting Internet of Things (IoT) devices and automated bots to SAP systems, this model has a direct impact on costs and compliance.

The key message: understand how SAP counts digital documents and plan accordingly to avoid unpredictable fees and leverage new licensing options for IoT and automation scenarios.

Digital Access Licensing: From Users to Documents

Traditionally, SAP required a named-user license for anyone or anything accessing its software. This became problematic as non-human agents (devices, APIs, RPA bots) started interacting with SAP.

The Digital Access model, introduced in 2018, is an outcome-based licensing approach that charges based on the number of documents created in SAP by indirect access.

Instead of counting individual users, organizations pay for digital documents (e.g., orders or invoices) generated by IoT sensors, customer portals, or other integrated applications. This shift was meant to provide transparency and align licensing with actual business transactions, especially in a world of machine-to-machine interactions.

Nine core document types form the basis of SAP’s digital access count. These include Sales Orders, Invoices/Billing documents, Purchase Orders, service and maintenance orders, Production/Manufacturing orders, Inventory Material movements, Quality Management records, Financial journal entries, and HR/Time management entries.

Only these categories of documents incur digital access fees – and only when created indirectly by a non-SAP external system. Read-only queries or updates that do not involve document creation do not count toward the license.

Notably, suppose one external action triggers multiple downstream documents in SAP. In that case, SAP charges only for the initial document (for example, an IoT-triggered sales order that later generates a delivery and invoice counts as one sales document).

SAP also weights certain high-volume document types less – for instance, a simple inventory or financial posting might count as only 0.2 of a document – to avoid over-penalizing very frequent low-value transactions.

IoT and Automation: Indirect Usage in Action

IoT and automation use cases can generate thousands or millions of SAP documents behind the scenes. For example:

• IoT Sensors: A network of sensors in a factory can automatically generate maintenance orders or quality inspection records in SAP when specific conditions are met (each such record is a document count).
• E-Commerce and Portals: A customer ordering via a web storefront (non-SAP) results in a sales order in SAP. Similarly, a vendor portal could create purchase orders or goods receipt documents in SAP.
• RPA Bots and Workflows: Robotic Process Automation bots posting transactions – e.g., moving inventory or logging time sheets – create SAP documents without a human user login.
• Third-Party Systems: A CRM, such as Salesforce, feeding an order into SAP or a cloud HR system sending employee time entries to SAP HR will trigger document creation indirectly.

All these scenarios mean people or devices are using SAP’s “digital core” indirectly. Under Digital Access, each of those created documents needs to be licensed.

This is especially relevant for enterprises embracing Industry 4.0, where machine-to-SAP communication is a constant occurrence.

It ensures that even if no person logs into SAP, the business value derived (such as automated transactions) is accounted for in licensing. The result is that IoT-heavy operations can drive up SAP license counts quickly if left unchecked.

Traditional vs. Digital Access Licensing

How does the new model compare to the old user-based approach?

The table below highlights key differences between named user licensing and document-based digital access:

In practice, enterprises may use both models. Employees and direct users continue to use named-user licenses, while Digital Access covers high-volume, machine-generated documents.

This hybrid approach adds complexity, but it can be optimized. For instance, you might have 500 internal users under traditional licensing and also license 100,000 documents per year for various IoT and B2B interfaces via Digital Access.

The two models coexist, so careful governance is necessary to prevent double-counting. (Notably, if an SAP-to-SAP interface is used – for example, SAP Cloud platform feeding SAP ERP – those interactions are usually covered by existing licenses and not counted as digital access.)

Pricing and Cost Considerations

SAP sells Digital Access licenses typically in packs of documents (often blocks of 1,000 documents per year). Pricing per document decreases at higher volumes – a volume discount-tiered model.

For example, the first 1,000 documents might cost more per document than, say, the 100,000th document.

SAP introduced the Digital Access Adoption Program (DAAP), offering a 90% upfront discount on document license list prices to encourage customers to transition.

Even with discounts, companies must carefully analyze volumes: underestimating document counts can lead to unexpected overage fees, while overestimating can result in unnecessary costs.

To illustrate the cost scale, consider some rough estimates (assuming a nominal list price of ~$0.20 per document, with a 90% discount applied under DAAP):

In real-world transactions, pricing can vary and be negotiated, but these figures illustrate how costs escalate with volume.

If an industrial IoT setup generates 50 million SAP documents annually, even with incentives, the company could owe millions of dollars per year just for digital access licenses.

Without the DAAP discount, the cost would be ten times higher.

This is why SAP provides tools like the Digital Access Evaluation Service (an analysis program/script) to help customers count the documents generated by their systems.

Before committing to the document model, it’s critical to run these measurements and forecast future IoT transaction growth.

Another nuance is maintenance: once you buy document licenses, they typically carry an annual maintenance fee (20% of the net price, as with other SAP licenses).

If you utilized a steep discount to buy in, be aware that after the initial contract term, SAP might not extend the same discount on additional documents, and maintenance will be calculated on the pre-discount list price value in some cases. This can lead to rising costs later if not negotiated upfront.

Compliance Risks and Real-World Examples

Ignoring or underestimating Digital Access can result in hefty compliance exposures. SAP has become vigilant about indirect usage in license audits.

A notable example is the Diageo case (2017), in which a global beverage company was found to owe over £50 million in fees for customers accessing SAP indirectly through a Salesforce integration.

This high-profile dispute was a wake-up call that indirect access is not “free.” Since then, numerous SAP customers have faced audit claims for IoT devices and third-party interfaces creating SAP records without proper licenses.

For instance, a Fortune 500 manufacturer discovered that shop-floor sensors and automation systems had generated millions of unlicensed SAP transactions — SAP’s compliance team presented an eight-figure ($$$$ millions) claim during an audit.

In another case, an insurance company was initially billed approximately $9.8 million for unlicensed indirect use, but a detailed usage analysis helped reduce the liability.

These examples underscore the financial risk: unlicensed digital access can potentially cost millions if left unaddressed.

There’s also a strategic risk: if digital access costs skyrocket, it might consume an IT budget that could have been used for innovation.

Some analysts have noted cases where projected document license costs could equal or exceed the entire original SAP license cost incurred by a company.

In a 2021 study of SAP clients, companies averaged tens of millions of digital documents per year, which translated into hundreds of thousands or even millions of dollars in fees (after discounts).

In extreme IoT-heavy scenarios, one organization had over a billion annual documents, making standard digital access fees untenable.

This has led to criticism that SAP’s model, if not negotiated properly, can penalize highly automated customers. The key is to proactively manage and negotiate these terms before an audit hits.

Managing and Negotiating Digital Access

To make SAP Digital Access workable for IoT and automation, enterprises should take a proactive stance in contract negotiations and internal management:

• Measure and Monitor: Start by accurately measuring your indirect usage. Use SAP’s auditing tools or third-party license management software to identify how many of each document type your IoT devices and systems generate. Ongoing monitoring is essential as you deploy more automation.
• Leverage DAAP and Promotions: If moving to the document model, utilize programs like DAAP to secure the largest discount possible on initial purchases. SAP’s 90% discount offering significantly lowers the entry cost, but be aware of the fine print (e.g., the duration of the discount and the maintenance implications).
• License Exchange and Credits: When negotiating, consider trading in existing SAP users or ordering licenses for credit toward digital access licenses. SAP has offered conversion programs that allow unused or underutilized licenses (such as those acquired to cover indirect use under the old model) to offset the cost of new document licenses.
• Cap and Scale Clauses: Aim to include volume flexibility in the contract. For example, consider negotiating a cap on annual document counts or a fixed fee for a high volume, to avoid runaway costs if your IoT usage grows faster than expected. You might also negotiate tiered pricing upfront (locking in discounts for higher volumes).
• Avoid Double Licensing: Ensure you’re not paying twice for the same usage. If you adopt Digital Access, you may reduce some named user licenses that were previously used only for technical integration accounts. Conversely, if you choose to stick primarily with named users, be cautious about inadvertently needing document licenses. Align your licensing approach so that one model covers a given integration scenario, rather than both.
• Consider SAP’s Own Integrations: SAP generally does not charge digital access for SAP-to-SAP scenarios. If you use SAP’s cloud extensions (like SAP IoT services or SAP-owned front-end systems) to interface with your core, those may already be licensed. This is not a solution for every case, but it highlights SAP’s incentive for customers to utilize its ecosystem. Evaluate if certain third-party use cases could be handled via SAP-provided components (though balance this against functionality and cost, as it might lead to vendor lock-in).
• Plan for Audits: As part of SAP license management, document your integrations and license assignments. If an audit occurs, having a clear mapping of IoT devices or bots to either a named user license or a document license allocation will put you in a stronger position. It’s better to address any gray areas with SAP proactively via contract language than to debate them during an audit.

By taking these steps, companies can turn digital access into a manageable cost of doing digital business rather than a nasty surprise.

The goal is to support IoT and automation innovations without blowing the IT budget on unforeseen SAP fees.

Recommendations

• Assess Indirect Usage Early: Inventory all non-human systems (IoT, automation, portals) that connect to SAP. Calculate current document volumes and project future growth to understand your exposure.
• Evaluate License Models: Compare the cost of sticking with named-user licensing (for external users/devices) versus switching to document licensing. Choose the model (or mix) that best fits your usage profile – one size does not fit all.
• Negotiate Favorable Terms: Don’t Accept SAP’s First Offer. Leverage the Digital Access Adoption Program for discounts and negotiate caps or price locks on document licenses. Seek credit for existing licenses and include flexible terms to accommodate growth or reductions in usage.
• Use Monitoring Tools: Implement SAP’s Digital Access counting tools or third-party license management software in your SAP environment. Continuously monitor the number of documents generated by integrations to stay in compliance and adjust if volumes spike unexpectedly.
• Optimize Integration Design: Work with your architects to minimize unnecessary document creation. For example, batch IoT sensor updates or filters out trivial transactions before they hit SAP. Smart design can reduce licensable events without losing business value.
• Educate Stakeholders: Ensure that IT, procurement, and business leaders understand the functionality of digital access. Incorporate the impact of licenses into the ROI analysis of new IoT or automation projects. An informed team can avoid deploying a solution that unintentionally triggers huge SAP costs.
• Plan for the Future: If you’re moving to S/4HANA or expanding your IoT capabilities, revisit your licensing strategy. Transitions are an opportunity to renegotiate and include digital access in the new contract. Don’t let legacy assumptions carry over – align your contract with your digital transformation roadmap.

FAQ

Q1: What is SAP Digital Access, and why did SAP introduce it?
A: SAP Digital Access is a licensing model where you pay for the number of certain documents created in SAP by indirect (non-human) access. SAP introduced it to address the challenge of “indirect use” as customers deploy IoT, portals, and automated systems. Under the old system, every user or device needed a license, which was hard to manage and often unclear. Digital Access ties the cost to actual business transactions (e.g., orders, invoices) created by those external systems, providing a more transparent and measurable method in theory.

Q2: How does digital document licensing work for IoT and automation scenarios?
A: If an IoT sensor, external app, or bot triggers SAP to create one of the predefined document types (such as a maintenance order or a financial entry), that counts as one digital access document. SAP licenses you for a total number of such documents per year. For example, 10,000 sales orders created by an e-commerce API in a year would consume 10,000 of your licensed documents. If you exceed your purchased document count, you need to true up by buying more. The model covers nine document categories relevant to common business processes, ensuring that even machine-generated SAP usage is licensed.

Q3: What are the nine document types counted under SAP’s Digital Access?
A: The nine core document types are Sales (sales orders, quotations at line-item level), Invoice (billing documents), Purchase (purchase orders, etc.), Service & Maintenance (service orders, maintenance notifications), Manufacturing (production orders), Quality Management (inspection lots, quality notifications), Material (inventory movements, goods issue/receipt), Financial (financial postings like accounting documents), and Time Management (HR time records). These cover the key transactions generated in SAP ERP. Only these types, when created indirectly, require a document license. Other interactions (like purely reading data or updates that don’t create a new record) are not counted.

Q4: Is adopting the Digital Access model mandatory if we have IoT integrations?
A: No, it’s not strictly mandatory – you have options. Existing SAP customers can choose to continue with their current licensing model (named users and older metrics) for indirect access, if permitted by contract. However, SAP strongly encourages switching to Digital Access, and new SAP S/4HANA contracts are generally oriented around it. You could alternatively license indirect use by ensuring that every device or external user is covered by a named-user license (the traditional approach), but this becomes impractical at scale. Most enterprises with significant IoT or third-party integrations eventually opt for Digital Access because it simplifies compliance (you don’t need to track every user or device identity, just documents). It’s wise to evaluate both approaches – in some cases, if volumes are very low, extending named user licenses may be a more cost-effective option. Ensure that your choice is documented in SAP to avoid any compliance ambiguity.

Q5: How can we estimate our Digital Access license needs and costs?
A: Start by measuring how many of each relevant document type your interfaces are creating. SAP provides the Digital Access Evaluation Service – essentially a program or notes you run in your system to count historical document creation by indirect means. Use this data to project an annual total. Then, apply SAP’s pricing (with any discounts) to estimate the cost. Work closely with your SAP account representative to understand the price tiers. For budgeting, consider a safety buffer – IoT and automation usage might grow or spike. Additionally, monitor on an ongoing basis; don’t just measure once. Some companies run quarterly checks to ensure they’re within their licensed amounts. By knowing your document count and the unit price (which may range from a few cents to a fraction of a cent per document with high-volume discounts), you can calculate your annual spend and avoid surprises.

Q6: What is the SAP Digital Access Adoption Program (DAAP), and should we use it?
A: DAAP is a limited-time incentive program SAP launched to ease the transition to Digital Access. It offers a massive discount (up to 90% off the list price) on document licenses and allows you to convert some of your existing license value into digital documents. Essentially, SAP recognized customers were wary of unknown costs, so DAAP made the initial price more palatable. If you plan to adopt Digital Access, taking advantage of DAAP (if it’s still available or extended in some form) is usually beneficial – it drastically cuts costs initially. However, you should still precisely count your usage; don’t buy far more documents than needed, even with a discount. Please be aware that after the incentive period, your maintenance fees and any additional documents will be subject to higher rates. So, yes, use DAAP if it fits, but go in with a long-term plan for managing costs when the honeymoon period ends.

Q7: How can we reduce or optimize Digital Access costs in an IoT-heavy environment?
A: There are several strategies. First, technical optimization – ensure your integrations are efficient. For example, if an IoT sensor sends data every minute that triggers a SAP document each time, consider accumulating the data and sending one consolidated update (one document) per hour, if this is business-wise acceptable. Second, periodically purge or archive unnecessary transactions; though SAP counts on creation, keeping your system lean avoids accidental extra processing. Third, negotiate a high-volume pricing deal – if you foresee massive document counts, SAP may agree to a custom pricing band or an enterprise license that covers an unlimited or very large number for a flat fee (usually as part of a broader Enterprise License Agreement, or ELA). Fourth, keep an eye on license overlap – you might reduce some other SAP licenses if Digital Access covers those scenarios (freeing the budget to reallocate). Finally, continuously review your IoT use cases: not every sensor reading requires creating an SAP record. Collaborate with business teams to determine what should be logged in SAP versus what can be handled in an edge system or aggregated before logging.

Q8: What happens if we ignore SAP’s digital access requirements?
A: In the short term, nothing – your IoT devices and systems will still function, and SAP won’t automatically stop them. But you accumulate risk. During a compliance audit or contract true-up, SAP can identify indirect usage. They have tools and audit scripts that will tally those document creations. If you haven’t licensed them, SAP may retroactively bill you for the excess, often at full list price (since incentives like DAAP are for proactive adoption, not post-audit findings). This can be an extremely costly bill that comes due all at once. Additionally, lacking proper licenses might violate your contract terms, giving SAP leverage (in the worst cases, they could terminate support agreements or pursue legal action, as seen in cases like Diageo). Most commonly, it becomes a negotiation at audit time – but you’ll be in a weaker position, possibly paying penalties or higher rates. In summary, ignoring it is playing a game of chance; the safer approach is to address it head-on through the appropriate licensing model.

Q9: Can we negotiate a custom deal with SAP for IoT usage outside of the standard model?
A: Yes, especially for large enterprises, almost everything is negotiable with SAP. If the standard digital access model doesn’t suit your situation (e.g., you expect enormous IoT transaction volumes that would be prohibitively expensive), you can negotiate a custom licensing arrangement. This might take the form of an unlimited indirect use clause for certain systems, a fixed annual fee for all IoT interactions, or a significantly reduced unit price locked in for high volumes beyond a threshold. You’ll need to build a strong business case and often engage SAP at an executive level to approve non-standard terms. It helps to demonstrate the value you’re getting from SAP and the partnership. For instance, if IoT integration with SAP is central to your digital transformation, SAP has an interest in enabling that (so they’d prefer to find a workable price rather than discourage its use). Engage your SAP account executive and consider bringing in licensing experts to craft and negotiate these terms. Keep in mind that any special deal should be documented in your contract to avoid ambiguities later.

Q10: Does using SAP cloud products or SAP’s IoT services eliminate digital access fees?
A: Using SAP’s own cloud offerings can sometimes mitigate indirect usage charges, but it depends. SAP’s policy is that SAP-to-SAP integration (such as one SAP product feeding another) does not qualify as Digital Access. For example, if you use SAP’s IoT cloud or SAP-owned front-end applications, those might be covered under their subscription and not generate billable “digital documents” in your ERP. However, this doesn’t exactly eliminate cost – it shifts it to those products’ subscription fees (which presumably include the necessary usage rights). It can be a useful approach if you are considering those solutions anyway. But you shouldn’t adopt an SAP component solely to avoid digital access fees without evaluating its own costs and fit. Sometimes, third-party IoT platforms or custom solutions are superior for your needs, even if they require document licenses. The best practice is to factor licensing into your architectural decisions, but not let it be the sole factor. If you do opt for an SAP integration, ensure your contract explicitly states that interactions between the SAP cloud service and your SAP ERP are license-compliant (SAP will typically include this provision). In summary, SAP’s ecosystem can simplify the complexity of indirect licensing, but it’s essentially an alternative method of paying for connectivity.

Read more about our SAP Advisory Services.

Schedule a meeting with us to discuss our SAP Advisory Services.

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit