€1.2B+
Delegated payment operations managed across the environment.
15K+
Payment flows processed with end-to-end operational traceability.
18
Healthcare authorities, hospitals and research institutes participating.
70%+
through digitization and operational orchestration.
1. The Project
A regional public authority providing shared services across the regional healthcare system serves as the central payment authority for 18 healthcare organizations, including local health authorities, hospitals, university hospitals and research institutes, connecting their local administrative and accounting processes with the regional financial ecosystem.
Each organization remains responsible for its own upstream administrative and accounting activities. Once a payment mandate is ready for execution, however, responsibility moves into a regional delegated-payment model.
The healthcare organization transmits a complete payment package — including the mandate, delegation, supporting documentation and digital signatures — through certified communication channels. From that moment, the operation must remain coherent across a much wider environment.
The payment package has to be acquired and validated. Delegation and budget conditions must be verified. Approval and signing must take place. Payment instructions must reach the national SIOPE+ infrastructure and the treasury ecosystem. Responses and exceptions must be correlated. Evidence must return to the organization that initiated the payment, while accounting-relevant outcomes must flow back into regional SAP.
Coopera provides the operational context that holds this entire sequence together. Every month, the live environment manages more than €1.2 billion in delegated payments and over 15,000 payment flows.
2. Why it was complex
The challenge was not simply to automate payment submission. It was to maintain one coherent operation while responsibility moved across independent organizations, people, financial systems, certified channels and national payment infrastructure.
Multiple organizations
Eighteen healthcare organizations participate in the same regional model while retaining their own administrative responsibilities, documentation and accounting context.
Multiple controls
Every payment package must satisfy the conditions required for execution, including documentation, valid delegation, digital signatures, budget conditions and account availability.
Multiple systems and infrastructures
Regional SAP, SIOPE+, the Bank of Italy infrastructure, the treasury bank, certified communication channels and digital trust services each perform a different part of the operation.
The operation continues beyond submission
Sending the payment instruction is only an intermediate event. Positive and negative responses, confirmations, receipts, cash journals and other financial evidence can continue to arrive afterwards. Those events must remain connected to the original delegation until the actual business outcome is known.
This is where the problem becomes one of operational continuity, rather than simply workflow or integration.
3. How Coopera holds the operation together
At the center of the operation, Coopera maintains a Payment Delegation Case as the primary Living Business Object that represents the persistent operational context of each delegated payment.
The Case begins when the delegation package is received and remains active until the payment outcome and its resulting evidence are known. Around the same object, Coopera keeps connected: Payment Mandate · Delegation · Supporting Documents · Digital Signatures · Controls · Approvals · SIOPE+ Messages · Treasury Responses · Payment Evidence · Accounting Updates. The operation can therefore move through different systems and execution mechanisms without losing the business context that gives each interaction its meaning.
Coopera first acquires the delegated payment package and performs the required controls. It then coordinates the approval path and, once authorization conditions are satisfied, automatically applies the required XAdES digital signature to the authorized payment mandate. Execution subsequently moves into the national payment infrastructure.
Coopera manages interaction with SIOPE+ and the treasury ecosystem, correlating both positive and negative responses with the originating Payment Delegation Case rather than treating them as disconnected technical messages.
This distinction matters because the operation may evolve asynchronously. A transmitted payment may receive acknowledgements, exceptions or subsequent confirmations at different times. Payment receipts, cash journals and other messages may arrive after the original submission. Coopera keeps those events associated with the same evolving operational context until the final outcome is established.
Throughout that lifecycle, the Case preserves the connection between: State · Content · Responsibilities · History · Evidence · What can happen next. The payment evidence remains available to the healthcare organization that originated the delegation, while relevant financial outcomes are propagated back into regional SAP, supporting the continuous update of regional accounting.
The individual systems continue performing their specialist responsibilities. SAP remains the accounting environment. SIOPE+ remains the national payment infrastructure. The treasury bank performs treasury functions. Digital trust services provide legally attributable signing. Coopera keeps the payment operation coherent across all of them.
4. The Outcome
What had previously required coordination across organizational, accounting, authorization and payment boundaries now operates through a common regional execution model. Payment mandates and supporting evidence enter through certified channels and remain connected throughout validation, approval, digital signature and payment execution. Interactions with SIOPE+, the Bank of Italy infrastructure and the treasury bank no longer become isolated technical exchanges. Responses, exceptions and confirmations remain part of the same Payment Delegation Case until the financial outcome is known.
The same applies to evidence. Payment receipts, cash journals and other resulting financial information remain connected to the original delegation and can be returned to the healthcare organization that initiated the operation. Accounting-relevant outcomes are simultaneously propagated to regional SAP.
The result is not the replacement of the participating organizations or specialist systems with one centralized application. It is one persistent operational context across them.
In production, the environment processes more than 15,000 payment flows every month, representing over €1.2 billion in delegated payments, with a measured 70%+ reduction in processing time.
5. What This Case Proves
Cross-organizational operational continuity
Eighteen independent healthcare organizations can participate in one regional execution model while every payment remains connected to its originating organization, documentation and evidence.
Persistent context through fragmented execution
Certified communications, approvals, digital signatures, SAP, SIOPE+, banking infrastructure and treasury interactions can perform their individual roles without becoming separate operational realities.
Execution through the real business outcome
The operation does not end when a payment instruction is transmitted. It remains alive through responses, exceptions, confirmations and financial evidence until the outcome is established.
Mission-critical orchestration at enterprise scale
More than €1.2 billion in delegated payments and 15,000+ payment flows are managed every month in a live regional healthcare environment.
