The German-Speaking SAP User Group in mid-August published a remarkably open post on the licensing of SAP Document and Reporting Compliance. Remarkable because it is not a panning. User companies such as Evonik and Kärcher attest to the solution's professional strength and strategic relevance. The criticism is aimed at something else: the licensing, the inconsistent middleware, and the effort involved in country rollouts.
For companies currently facing this decision, this may be the most useful reading of the past few months. Because it shifts the proper sequence of questions. Not: Which tool do we choose? But rather: What will the decision cost us over the next five years—and how certain can we even be about that figure today?
As an SAP Silver Partner and DSAG member, we have no interest in talking down SAP DRC. For a significant portion of companies, DRC is the right answer. Just not for all of them. This article outlines where the line is drawn.
What DSAG criticizes about SAP DRC – and what it explicitly does not
First, the positive aspects, as they are often lost in the discussion: The surveyed user companies view DRC as a strategic platform for electronic document exchange, in some cases even as a mandatory solution. The deep integration into the SAP standard, the avoidance of media disruptions, and the commitment to continuously adapt the solution to new local regulations are clearly cited as advantages. Furthermore, the ability to map legal reporting directly in S/4HANA is considered a genuine added value compared to traditional e-invoicing products.
The criticism focuses on three points:
First, the license metrics. They vary partially by country, are not capped, and SAP keeps introducing new licenses for individual countries. A consistently globally usable license still does not exist – which noticeably diminishes the usefulness of a platform that is actually intended to be global.
Secondly, the middleware. Depending on the country and solution channel, different technical intermediate layers are required. Country rollouts therefore do not follow the same pattern, but each bring their own setups, tools, and operational requirements. This makes scaling more difficult.
Thirdly, the implementation effort. DSAG suggests, among other things, that SAP should better support the activation of extensive note sequences—a point we will return to below because it is directly related to the cloud versus on-premise question.
To be fair, things have also moved forward. With the merger of Advanced Compliance Reporting and Electronic Document Processing into SAP DRC, reporting has been switched from a revenue-based model to an entity model. This is much easier to plan than before, and especially in the public cloud, the barriers to entry for smaller companies have been lowered as a result.
The SAP DRC license model: Quotas, minimum commitment, and no cap
The core of the problem lies in the structure, not the price tag. SAP licenses the DRC Cloud Edition via annual document quotas that are purchased in blocks. These include not only issued e-invoices, but fundamentally the transaction documents managed via the cloud service.
This results in two opposing effects, both of which are mentioned in the DSAG article:
- With a small volume of receipts are the costs per document high because a minimum purchase requirement applies. Anyone who generates a manageable number of outgoing invoices per year effectively pays for capacity that is never used.
- For large document volumes there is a missing upper limit. There is neither a cost cap nor a flat-rate model; costs continue to grow with volume without reaching saturation past a certain amount. For companies with high-volume invoicing, this can ruin the economic viability.
In between lies the problem that causes the most trouble in practice: forecasting. Contingents must be procured in advance. If a local go-live is delayed, agreed minimum purchase quantities are not met—resulting in idle costs that no one had planned for. In the DSAG article, Kärcher formulates precisely this desire: the economic risk of an unforeseeable project delay should not rest solely with the user company.
„This is the point in our conversations where silence regularly sets in,“ says Thomas Dresselhaus, Managing Director of Consult-SK GmbH. „The question is never ‚What does the license cost?‘ The question is ‚How many Documents do we have in three years?‘ — and honestly, hardly anyone has a reliable answer to that.“
When is SAP DRC worth it? The three-country rule of thumb
The DSAG article contains remarkably specific guidance, and it comes not from a provider of an alternative, but from the speaker of the DSAG Electronic Invoicing and Reporting working group: DRC demonstrates its strengths starting from about three countries with SAP systems. The initial effort is considerable, but decreases with each additional country. For merely mapping the German requirement, according to the assessment, there are better, more specialized partner solutions.
That is a useful rule of thumb, and it aligns with our project experience. Anyone operating entities in twelve countries, having to manage different reporting requirements and anyway on S/4HANA and BTP set, for him DRC is the strategic choice. Those who, on the other hand, SAP DRC only for Germany evaluated – so at its core XInvoice and ZUGFeRD wants to send and receive according to EN 16931 – is buying an international compliance platform for a national requirement.
Is SAP DRC worth it for mid-sized companies? The honest answer is: It depends less on company size than on the country structure and volume stability. A mid-sized company with subsidiaries in five EU countries can do very well with DRC. A corporation with mass invoicing at a single location, on the other hand, will predictably run into the capping problem.
Five questions to consider before choosing a tool
Before any products are even discussed, these five points should be clarified. They usually decide the matter anyway.
- In how many countries with their own reporting obligations are we active – today and in five years? Below three countries, little speaks for a global platform. From three countries upward, the balance tips Invoice.
- What is our document volume and how much does it fluctuate? Seasonal business models and companies with rapidly growing billing volumes are structurally disadvantaged when it comes to volume-based tiers.
- Is it about the exit, the entrance, or both? DRC is designed with the outcome in mind. End-to-end automated inbound processing with order matching, verification, approval, and posting generally requires a complementary solution anyway.
- What does our schedule look like? Anyone who has to fulfill the exhibition obligation in 2027 because their previous year's revenue exceeded 800,000 euros should realistically assess the initial effort. A platform project is not a four-week undertaking.
- Are we already using SAP BTP productively? If not, come to the E-bill add a platform topic – including administration and authorization processes that are not identical to existing on-premise workflows in a cloud environment.
Why we rely on cloud instead of on-premise
At this point, it is worth recalling the DSAG criticism regarding Notes activation. It describes a structural problem inherent in any compliance logic installed in a customer system: If a legal requirement changes – a new XRechnung version, an adjusted Peppol specification, a modified set of validation rules – this change must be imported, tested, and transported in every single system for every single customer. Sometimes a system version is outdated, sometimes a release window blocks the process, and sometimes the test system is missing.
That is exactly why we run our solutions for the Invoice receipt and the Outgoing invoice – the Cloud Invoice Conversion Service and the Cloud Billing Conversion Service – as cloud services instead of an on-premise installation. The regulatory logic resides centrally with us. If a requirement changes, we update it once in a single place, and all connected customers continue to work in compliance the next day. Without a transport request, without a notes sequence, and without project effort on the customer side.
„Instead of distributing the change effort fifty times, we handle it centrally once,“ says Thomas Dresselhaus. „That's not about winning a technical beauty contest, but rather the difference between a compliance requirement and a compliance project.“
The practical effect is threefold: compliance does not depend on the customer's individual system status. The effort required for regulatory changes is eliminated in internal IT planning. And costs remain predictable because there is no recurring maintenance and testing effort for each change.
SAP DRC and partner solution are not mutually exclusive
A common misconception is that it is an either-or decision. It is not. The DSAG article itself describes cases where companies switched to alternative products for individual countries because the licensing situation there was not economically viable.
It works the exact same way in the opposite direction: DRC as a strategic reporting channel for international cases, a specialized solution for the German requirement, and inbound processing. Anyone who turns the decision into an article of faith ruins precisely these combination possibilities for themselves.
What to do now
The deadlines are set. Domestic companies have already been required to receive e-invoices since the beginning of 2025. Starting January 1, 2027, the issuance obligation applies to all with more than 800,000 euros in previous-year revenue, and from 2028 for all others. And with ViDA, a cross-border reporting system is on the horizon starting in 2030, which will expand the requirements once again.
Our recommendation: Clarify the licensing and architecture questions before committing to a product. Proper upfront clarification prevents precisely the two most expensive mistakes—purchasing too many licenses and the parallel operation of redundant landscapes. And seek out dialogue with other user companies; the DSAG working group on Electronic Invoicing and Reporting is the right place for that.
If you would like a neutral assessment of your specific situation—country structure, volume, timeline, system status—get in touch with us. We will tell you that DRC is the right choice even if it is the right choice.
