in S/4HANA
Invoices are more than just a PDF attached to an email. They are legally binding documents, triggers for payment processes, and often the starting point for electronic processing at the customer’s end. This makes it all the more important that the entire issuance process functions reliably—from channel selection to delivery. Anyone switching from ECC to SAP Cloud ERP should be aware of a few key changes.
Output Channels: From Email to Peppol
Email remains the standard channel: HTML text in the body, a PDF invoice as an attachment, optionally supplemented by additional documents. SAP Cloud ERP supports flexible, rule-based templates here instead of rigid text modules. Attachments can be automatically added based on specific criteria—such as terms and conditions, technical documents, or certificates.
For printing, the Cloud Print Manager is available to forward print jobs to local printers. This is particularly relevant in hybrid scenarios where not all recipients are digitally connected.
When it comes to electronic data exchange, SAP Cloud ERP clearly relies on modern standards. Native support is available for formats such as Peppol, XRechnung, or ZUGFeRD via SAP Document and Reporting Compliance (DRC)—often still referred to by its historical name, “eDocument,” in practice and in Fiori apps. Traditional IDoc-based EDI scenarios are still possible but should not be “forcibly” mapped through the new Output Management system. For pure IDoc communication, we recommend—depending on the system landscape—the use of established interfaces or integration components such as SAP AIF.
And what about fax? Technically, it’s still possible—for example, via “email-to-fax” services or connected output management systems. In practice, however, the transition to the cloud should be used as an opportunity to systematically phase out analog channels.
From NAST to Output Management: What's Changing Functionally
Many users are familiar with message control via NAST from ECC. In SAP Cloud ERP, however, the new S/4HANA Output Management is used instead. This brings with it several significant differences.
- Rules and Logic
Instead of condition logic and custom ABAP logic, the new Output Management uses the Fiori app “Output Parameter Determination.” In the underlying decision tables (which are technically based on BRF+), all criteria—such as document type, partner role, or country—are clearly laid out in a matrix for key users. This increases transparency and eliminates the need for hidden special logic.
- Batch Processing and Invoicing Job
In the traditional scenario, output was often triggered via technical reports such as RSNAST00 or VF31. Errors ended up in the spool—and had to be analyzed there.
In SAP Cloud ERP, scheduling is app-based. Output is decoupled from the saving process (“Fire & Forget”): If a channel is temporarily unavailable, the output is retried in the background. At the same time, a central Fiori app (“Manage Output Items”) enables direct monitoring with a status display on the document. This significantly reduces manual rework.
- Email Delivery and Content
In the past, rigid text modules (e.g., SO10) and development-based attachments dominated. Today, the focus is on modern HTML templates, which key users manage centrally via the Fiori app “Maintain Email Templates.” Here, system variables such as document numbers or customer names can be inserted, and rule-based extensions can be defined. This greatly simplifies maintenance in day-to-day work—without requiring in-depth development knowledge.
CONSILIO provided us with excellent support in redesigning the SAP SD processes and implementing the technical changes.
- The Showstopper: Form Technology
The biggest difference lies in the forms.
In the traditional NAST environment, SAPscript, SmartForms, and Adobe Forms were supported. In SAP Cloud ERP, only Adobe Forms (Adobe LiveCycle Designer) is supported.
This has direct consequences: Existing SAPscript or SmartForms layouts cannot simply be carried over. Switching to the new output management system usually means redeveloping the forms from scratch. This is not a minor detail, but a significant project and cost factor—especially for complex, internationally used invoice forms.
At the same time, Adobe Forms offers advantages: modern layout capabilities, better PDF support, and a unified technology for all output scenarios.
- EDI and Integration: API-First Instead of the Traditional Medium 6
In the old model, the IDoc (Medium 6) was directly embedded in message control. In SAP Cloud ERP, the focus shifts to service-oriented architecture: The “EDI” output channel triggers standardized SOAP or OData APIs instead of traditional tRFC connections. The actual conversion and external communication are then handled by middleware—typically the SAP Integration Suite. The SAP Application Interface Framework (AIF) serves as a central message dashboard for monitoring API messages directly in S/4HANA.
For companies, this means that the integration of EDI converters or third-party systems is undergoing a fundamental change. The architecture now strictly follows the cloud principle: standardized, API-based, and seamlessly expandable via defined interfaces.
Conclusion: Smart Invoicing Means Modernizing with a Purpose
Smart Invoicing in SAP Cloud ERP is more than just a new dispatch mechanism. It is a comprehensive approach to digital, rule-based, and monitored invoicing processes.
Companies benefit from:
- transparent decision-making rules
- stable, asynchronous processing
- centralized monitoring
- native support for modern e-invoicing standards
At the same time, the transition requires careful planning—especially when it comes to forms and existing EDI interfaces. However, those who view the migration not as a technical necessity but as an opportunity to modernize their processes lay the foundation for future-proof invoice processing in the cloud.
Those who view invoices as a strategic touchpoint can fully leverage the potential of a fully digital and rules-based payment process.
