Mandatory Electronic Invoicing with SAP
CREATE AND GROW ACT
The Crea y Crece Law requires that SAP be adapted to issue, receive, and manage structured and traceable electronic invoices. At i3s, we define the right solution.
The Order HAC/1028/2026 , published on October 5 and effective as of October 6, 2026, establishes the timeline for transitioning to B2B electronic invoicing. The requirement will take effect on October 6, 2027, for businesses and professionals whose transaction volume exceeded 8 million euros in the previous calendar year, and on October 6, 2028, for all others.
2022
September 2022
Law 18/2022 introduces the requirement for electronic invoicing between businesses and professionals.
2026
March 31, 2026
Royal Decree 238/2026 defines the system, formats, interoperability, and invoice statuses.
OM
October 6, 2026
October 6, 2026.
Its entry into force triggers the start of the time periods.
+12
October 6, 2027
First phase
: companies with revenue exceeding 8 million euros.
+24
October 6, 2028
Second payment period :
for all other companies and professionals.
WEBINAR
E-invoicing management with SAP DRC and Business Network
Watch the recording of the webinar on managing electronic invoicing with SAP DRC and SAP Business Network.
It’s not enough to simply generate a PDF. SAP must issue and receive structured invoices, connect to exchange platforms, report statuses, and integrate compliance into its processes.
Structured Electronic Invoice
SAP must issue and receive invoices in supported formats, with complete and processable data.
Cross-platform interoperability
The system must connect to the public solution and to private platforms without interrupting the process.
Traceability and Invoice Status
Each invoice must allow for the communication of its acceptance, rejection, and payment, while maintaining a complete record of its status.
Integration with SAP processes
Compliance must be integrated into billing, accounting, and collections, thereby avoiding parallel manual tasks.
The system is hybrid. You can use the public solution, a private platform, or a combination of both. The choice affects the channel, but not the traceability and reporting requirements.
PUBLIC
Public Electronic Invoicing Solution (SPFE)
Developed and managed by the AEAT, it will be free and accessible to any business or professional. When an invoice is issued directly through this solution, it will not be necessary to send an additional copy.
PRIVATE
Private Electronic Invoicing Platform (PPFE)
It may be a proprietary solution or one provided by a third party. Its use requires ensuring interoperability and, where applicable, submitting a true copy of each invoice to the public system.
BOTH
A combination of the public solution and a private platform
The company may combine the public solution with a private platform depending on its processes. The public solution may also be used as a means of interconnecting platforms.
01
TRANSMISSION AND RECEPTION
Through the SPFE, through a PPFE, or by combining both. The company can choose the approach that best suits its processes.
02
CERTIFIED COPY
This is required when the invoice is issued through a private platform, except when the public solution serves as a means of invoicing or interconnection.
03
REPORTING OF STATUSES
Rejections and full payments must be reported to the SPFE within a maximum of four days, excluding weekends and national holidays.
Electronic Invoicing with SAP DRC and Bidalnet
SAP DRC provides the standard framework for managing electronic documents. Bidalnet adds a layer of connectivity and automation tailored to each environment.
Standard SAP DRC
The standard SAP platform for creating, processing, and monitoring electronic documents.
• Generate the eDocument from SAP invoices.
• Use the required structure and format.
• Allows you to send and receive email messages.
• Keeps the process within the standard SAP framework.
Bidalnet
An i3s acceleration layer on top of SAP DRC. It does not replace it—it complements it and adapts the process to each environment.
• Facilitates connection with the SPFE and private platforms.
• Monitors the cycle of incoming invoices and their statuses.
• It incorporates automations tailored to each company.
• It is based on the standard SAP framework.
Every company starts with a different architecture. That’s why we determine the combination of SAP DRC, Bidalnet, and integration that best fits your system and processes.
SAP DRC
For companies that already use SAP DRC or prefer to adopt SAP’s standard solution for managing electronic invoicing
Bidalnet
For companies that need to accelerate deployment, customize the connection, and manage the electronic invoicing cycle using the standard SAP framework
Integration with SAP BTP
For environments with an SAP BTP strategy that want to integrate SAP DRC or Bidalnet with their existing architecture and services
Estimated duration of 3 to 4 months, to be determined after the initial diagnosis based on each company’s starting point, scope, and integrations.
discover & prepare
We define the scope, the team, the work plan, and the starting point for the SAP environment.
Explore
We perform a fit-to-standard analysis and validate the architecture, integrations, and process requirements.
Realize
We configure the solution, make the necessary adjustments, and run end-to-end tests.
Deploy & Run
We prepare for the go-live, assist with the launch, and provide support during the initial operation.
Request an SAP assessment for electronic invoicing
Tell us where you’re starting from. We’ll analyze your system and the necessary integrations to define a realistic roadmap.