Document counting under RISE Digital Access.

Digital Access is the SAP framework for licensing indirect use of SAP through document counts rather than through user counts. Under RISE with SAP, Digital Access is bundled into the commercial model in ways that can be advantageous or punitive depending on how the buyer's document profile is measured and contracted. The buyer who measures their document footprint before SAP measures it for them is in a position to negotiate. The buyer who waits for the SAP measurement tool to produce the answer is in a position to absorb whatever number SAP produces. This article walks through the discipline that turns Digital Access from a black box into a contractual line item.

Understand the document categories that count

Digital Access licensing applies to nine document types under the standard SAP framework. Sales documents, purchase documents, invoice documents, manufacturing documents, quality management documents, time management documents, financial documents, material documents, and service documents. Each document, when created through an indirect channel, contributes to the document count that determines the Digital Access license obligation.

The buyer side discipline is to understand which document types exist in the buyer's estate, which integration channels create them indirectly, and which volumes flow through those channels. The exercise is uncomfortable because it produces a number, and the number is sometimes much larger than the buyer expected. The discomfort is the point. The number that SAP eventually quotes will be informed by the same data, and the buyer who has the number first negotiates from a stronger position.

Not every document counts in every contract. The original DAAP, the Digital Access Adoption Programme, included specific carve outs and discount structures that varied by document type. RISE proposals often replicate the DAAP structure inside the contract. The buyer should understand the carve outs that apply, the document types that are most exposed in their specific estate, and the relative price per document across the nine categories.

Measure the baseline before SAP measures it

The most consequential moment in any Digital Access conversation is the baseline measurement. The baseline is the document count that the contract is sized against, and once the baseline is in the contract, every subsequent year compares against it. A baseline that is too low forces the buyer into expensive uplift conversations year on year. A baseline that is too high overcharges the buyer from day one and burns negotiation capital that could have been used elsewhere.

The buyer side discipline is to measure the baseline independently of SAP. SAP provides a measurement tool that produces a number. The number is honest in its own terms, but it is also a number SAP produces for SAP purposes, and the buyer should not treat it as the only data point. An independent measurement, using the buyer's own audit of integration channels and document creation patterns, gives the buyer a second number to anchor the negotiation against.

The two numbers, the SAP number and the buyer number, are rarely identical. The difference is the negotiation space. Buyers who run the parallel measurement find that the difference is sometimes ten to twenty percent of the document count, which translates into a corresponding share of the Digital Access cost. The discipline of measuring in parallel is one of the highest return activities in a Digital Access conversation.

Predict the growth profile over seven years

Document volumes change over time. Business growth produces more documents. New integration channels produce more documents. Acquisitions and divestitures change the document profile. Process changes that automate previously manual flows convert direct documents into indirect documents and increase the count. The buyer who predicts the seven year profile, rather than locking into a static baseline, gets a contract that scales sensibly.

The prediction is not a forecast. It is a set of scenarios. A low growth scenario, a base case scenario, and a high growth scenario, each translated into a document count by year over the seven year horizon. The scenarios produce a band, and the band is the input to the commercial conversation about how the contract handles document growth.

Three contractual mechanisms are useful in handling growth. A defined uplift band, where document growth inside the band incurs no incremental charge. A defined true up mechanism, with predictable price per document above the band. An anniversary review, where significant changes in the business profile, including acquisitions and divestitures, trigger a renegotiation rather than an automatic uplift. The right combination of the three depends on the volatility of the buyer's business.

Negotiate the price per document explicitly

The standard SAP Digital Access price list publishes a price per document by document type. The list is the starting point, not the endpoint. Inside RISE, the Digital Access pricing is often bundled with the rest of the proposal, which can either hide a good price or hide a bad one. The buyer who unbundles the Digital Access pricing from the rest of the RISE proposal can see what they are actually paying for documents.

The unbundling exercise often reveals that the per document price in the RISE proposal is higher than the public DAAP price. The premium is the bundling cost, and the buyer who surfaces it can negotiate it down. Buyers who do not unbundle find the per document price is opaque, and the price they are paying is whichever number the proposal asserted.

The negotiation should also address the price escalation over the contract term. Many RISE proposals quote a flat price for the term, then introduce escalation in renewal. Buyers who write the renewal price into the original contract, with defined escalation caps, get protection that the standard renewal conversation does not provide. The protection matters more than the original price level, because the renewal is where SAP captures the increase that the original contract held flat.

Address the audit mechanics in the contract

Digital Access audits are how SAP measures actual document creation against the contractual envelope. The audit mechanics, the audit frequency, the right to challenge audit findings, and the dispute resolution process are all contractual terms that determine how disputes are resolved. Buyers who write the audit mechanics into the contract have a defined process. Buyers who do not write them in find that SAP defines the process at the moment of audit.

Specific audit terms that have proven valuable in past engagements include defined audit windows, with reasonable notice. Buyer right to participate in the audit, with named contacts on both sides. A documented methodology for counting documents, with reference to the integration patterns the buyer operates. A defined dispute resolution process, with escalation to senior leadership before any commercial demand is enforced.

The audit terms should also address remediation. If the audit finds a higher document count than the contractual envelope, the contract should define the remediation path. Some patterns include a defined uplift price per excess document, a defined catch up period for the buyer to bring the count back within the envelope, or an option to convert from document counting to user counting for specific document categories. The right pattern depends on the buyer's specific document profile.

Consider the alternatives to Digital Access

Digital Access is the SAP framework for licensing indirect use, but it is not the only commercial structure available. Some buyers find that user based licensing produces a lower total cost for specific document categories. Others find that named user packages, applied to specific external user populations, are more economical than counting the documents those users create. The choice between the two approaches is a contract design decision that the buyer should make consciously.

The analysis is sensitive to the integration topology. Buyers with a small number of high volume integrations often favour Digital Access because the document volume is high and the named user count is impractical. Buyers with a large number of low volume integrations often favour user based licensing because the per user cost is contained and the document count is unpredictable.

The conversation should also address the hybrid pattern. Some buyers run Digital Access for the high volume document categories and user based licensing for the low volume categories. The hybrid pattern requires more contractual specification, but it can produce a lower total cost than either pattern alone. The discipline is to model both alternatives explicitly, not to default into the SAP nominated structure.

Conclusion

Digital Access document counting is the most opaque indirect access lever in the RISE with SAP commercial model, and it is the lever where buyer side preparation produces the largest measurable savings. Buyers who understand the document categories, measure the baseline independently, predict the seven year growth profile, negotiate the price per document explicitly, address the audit mechanics in the contract, and consider the alternatives to Digital Access arrive at a contract that is contractually clean and commercially defensible. Buyers who treat Digital Access as a line item the SAP account team has already calculated find that the calculation is rarely in their favour, and the cost of reopening it after signature is much larger than the cost of getting it right the first time.