The Most Important Facts at a Glance
SAP DRC licenses are a critical success factor for modern finance and e-invoicing projects. Companies face complex questions: Which metrics apply to SAP DRC licenses? What additional costs arise? And which system dependencies need to be considered?
While SAP Document and Reporting Compliance (DRC) ensures legal compliance, Vendor Invoice Management (VIM) by OpenText focuses on the operational automation of invoice processing. Together, they form the foundation for a scalable, compliance-safe, and future-ready finance architecture.
Table of Contents
- How does the SAP DRC licensing model work and which billing metrics are crucial?
- What is an “entity” in the SAP DRC licensing model and how is it calculated correctly?
- Why do I specifically need the DRC Cloud Edition (SKU 8008260)?
- What is the difference between one-time purchase vs. subscription for SAP DRC?
- What is NOT included in the DRC license?
- SAP DRC vs. Vendor Invoice Management — Clear distinction
- VIM & Capture — On-premise vs. cloud licenses in detail
- Important limitation: SAP VIM and S/4HANA GROW
- Conclusion, summary & outlook
- Useful links & sources
How does the SAP DRC licensing model work and which billing metrics are crucial?
SAP DRC includes five product lines with different deployment scenarios, metrics, and licensing models. The following table shows the complete SKU structure based on official SAP price lists (as of April 2026):
| SKU | Product | Deployment | Metric | Model |
| 7018942 | DRC On-Premise | SAP ECC (ERP on-prem) | Documents per year in blocks of 5,000 | ✓ One-time purchase |
| 7020617 | DRC for S/4HANA | S/4HANA On-Premise (HANA DB required) | Entities | ✓ One-time purchase |
| 8013668 | DRC Private Cloud | RISE with SAP (S/4HANA Cloud Private) | Entities | Subscription |
| 8013658 | DRC Public Cloud | GROW with SAP (S/4HANA Cloud Public) | Entities (included in the bundle) | SubscriptionIncluded in the GROW bundle |
| 8008260 | DRC Cloud Edition | All deployment models (transmission layer) | Documents per year in blocks of 5,000 | Subscription |
⚡ Architecture note: The DRC Cloud Edition (8008260) is the decisive transmission layer across all deployments. For ECC, S/4HANA On-Premise, and RISE, the following applies: without the Cloud Edition, there is no transmission to authorities or PEPPOL networks. For GROW, the Cloud Edition is included in the bundle.
👉 More on implementation:
E-Invoicing with SAP | PEPPOL | XInvoice | ZUGFeRD – Fink IT-Solutions
What is an “entity” in the SAP DRC licensing model and how is it calculated correctly?
In the context of SAP DRC, the entity is a central billing metric for S/4HANA-based deployments:
| Entity = Company Code × Country | Each combination is counted separately. |
Example: 3 company codes in 3 countries → 9 entities. Every expansion by a new country or a new company code increases the number of entities.
Which deployments use the entity model?
- S/4HANA On-Premise (SKU 7020617) — One-time purchase, entity-based, HANA DB required
- RISE with SAP / S/4HANA Cloud Private Edition (SKU 8013668) — Subscription, entity-based
- GROW with SAP / S/4HANA Cloud Public Edition (SKU 8013658) — included in the GROW bundle, entity-based
Only SAP ECC / ERP On-Premise (SKU 7018942) and the DRC Cloud Edition (SKU 8008260) use the document metric (blocks of 5,000).
Why do I specifically need the DRC Cloud Edition (SKU 8008260)?
The SAP DRC Cloud Edition is the most important and most frequently misunderstood component in the DRC ecosystem. It is the central gateway engine for electronic document exchange with authorities, PEPPOL networks, and national platforms.
Who needs the Cloud Edition?
- SAP ECC / ERP On-Premise: Mandatory for transmission to authorities and PEPPOL
- S/4HANA On-Premise: Mandatory for transmission
- RISE with SAP (Private Cloud): Mandatory
- GROW with SAP (Public Cloud): Already included in the bundle — no separate license required
What is included in the DRC Cloud Edition?
- Data mapping and format generation for international e-invoicing networks
- Transmission via PEPPOL AS4, KSeF (Poland), e-Factura (Romania), and other national systems
- Process orchestration, monitoring, and complete document history
- Error handling and contingency processes
- Incoming and outgoing document processing
| ⚠️ Migration note: SAP discontinued the previous “DRC Cloud Service” on 31.12.2025. All customers must have migrated to the Cloud Edition (SKU 8008260). Open migrations should be reviewed urgently. |
👉 More insights:
SAP DRC: New AI features for smart compliance
What is the difference between one-time purchase vs. subscription for SAP DRC?
The licensing model (one-time purchase vs. subscription) is determined by the deployment model:
| Product / SKU | Model | Metric | Units |
| DRC On-Premise (7018942) | One-time purchase | Documents | Block of 5,000 documents |
| DRC for S/4HANA (7020617) | One-time purchase | Entities | Entity (1–2) |
| DRC Private Cloud (8013668) | Subscription | Entities | On request (SAP) |
| DRC Public Cloud (8013658) | Included in the GROW bundle | Entities | Included in GROW |
| DRC Cloud Edition (8008260) | One-time purchase | Documents | Block of 5,000 documents |
What is NOT included in the DRC license?
The following components must be licensed separately and are not included in the standard DRC price:
- SAP BTP (Business Technology Platform) — base platform, separate license
- SAP BTP Integration Suite — for country- and channel-specific scenarios (see table below)
- Advanced analytics & AI features (e.g. Joule, Embedded AI)
- Integrated archiving — standard compliance yes, long-term archiving no (e.g. OpenText xECM required)
| ✅ Standard compliance (format generation, transmission, monitoring) is included in the DRC license. |
👉 Learn more:
Why ZUGFeRD without SAP DRC can become very expensive in the future
SAP DRC vs. Vendor Invoice Management — Clear distinction
DRC and VIM solve different problems and complement each other strategically:
| Criterion | SAP DRC | OpenText VIM (Vendor Invoice Mgmt.) |
| Focus | Legal compliance | AP process automation |
| Goal | Create & transmit e-invoices | Automatically process incoming invoices |
| Metric | Entities (S/4HANA) or documents (ECC/Cloud Edition) | Documents in blocks of 1,000 |
| Billing | Per entity or per document | Per document (not per page) |
| GROW compatible? | ✅ Yes (included in the bundle) | ❌ No — not available for GROW |
VIM & Capture — On-premise vs. cloud licenses in detail
The OpenText VIM licensing model differs significantly between on-premise and cloud operation:
| Criterion | VIM On-Premise (7020106) | VIM Private Cloud (8019399) | Capture Core Cloud (8008267) |
| Licensing model | One-time purchase | Monthly subscription | Monthly subscription |
| Metric | 1,000 docs/year (blocks) | 1,000 docs/month (blocks) | 1,000 docs/month (blocks) |
| Minimum purchase | 30 blocks = 30,000 docs/year | 30 blocks/month | 50 blocks/month |
| Maintenance | ~22 % p.a. (SSFA) | Included in the price | Included in the price |
| Minimum term | – | – | 3 years (mandatory) |
| Billing per doc. | Per document (not page) | Per document (not page) | Per document (not page) |
👉 More information:
SAP Invoice Management by OpenText – Fink IT-Solutions
SAP Invoice Management: SAP VIM explained & benefits
Important limitation: SAP VIM and S/4HANA GROW
| ❗ SAP VIM (OpenText Vendor Invoice Management) is currently NOT available on S/4HANA GROW (Public Cloud). VIM is designed as a classic on-premise/private cloud add-on and does not support the GROW multi-tenant architecture. |
Instead, SAP offers in the GROW context:
- Standard Fiori workflows for invoice processing
- SAP Central Invoice Management (CIM) — document-based, 20,000 documents in the premium bundle
- Limited automation compared to the VIM feature scope
For complex processes or high incoming invoice volumes (> 50,000 documents/year), the native GROW capabilities are often not sufficient. In these cases, a RISE deployment with VIM or an additional AP automation solution should be evaluated.
Conclusion, summary & outlook
The combination of SAP DRC & Vendor Invoice Management is crucial for a future-proof finance strategy. Companies that consider these factors early avoid cost traps and build a scalable architecture.
Checklist for licensing decisions:
- Clarify the deployment model: ECC / S/4HANA On-Premise / RISE / GROW → defines SKU and metric
- Determine the number of entities: Count all company code-country combinations completely
- Check DRC Cloud Edition: Separate license required for ECC, S/4HANA On-Prem, and RISE
- BTP Integration Suite: Check by country and channel
- VIM availability: For GROW → evaluate alternatives; for RISE → VIM fully available
- Plan archiving separately: DRC does not include long-term archiving
- Capture term: Include the mandatory minimum term of 3 years in planning
👉 Further reading:
SAP DRC Roadmap 2026: Functions, countries & architecture
🎥 In addition:
SAP DRC & SAP VIM licenses: Costs, models and key questions 2026