12M+
Across the regional healthcare environment
18
Participating in one regional operating model
200K+ Month
Processed and orchestrated through the platform
10+ years
Supporting mission-critical fiscal operations since 2015
1. The Operational Challenge
A regional public healthcare authority provides shared operational infrastructure across 18 healthcare organizations, connecting national electronic-invoicing services with the accounting environments responsible for each organization.
The platform has operated continuously since 2015, when mandatory electronic invoicing introduced a new digital interaction model between suppliers, public administrations and Italy’s national e-invoicing infrastructure, SDI.
Supplier invoices enter through certified communication channels — primarily certified email, with web services providing an additional integration path. But receiving the electronic invoice is only the beginning of the fiscal operation. Every invoice must be identified and correlated with the correct healthcare organization. Business and fiscal controls determine whether it is eligible to enter accounting or must be rejected beforehand. Eligible invoices move into the appropriate accounting environment, while subsequent responses return and must be correlated with the original invoice.
Meanwhile, SDI continues producing its own notifications and statutory events. The operation therefore does not end when the XML is received, or even when the invoice reaches an ERP.
It ends when the Invoice reaches a governed fiscal outcome: rejection, explicit acceptance or statutory deadline closure.
2. Why it was complex
The challenge was not simply exchanging electronic invoices. It was maintaining one coherent fiscal lifecycle while channels, messages, accounting systems and regulatory deadlines acted asynchronously around the same invoice.
One regional model had to span 18 different accounting environments
The original architecture connected 18 healthcare organizations operating 18 different ERP and accounting products from independent technology providers. The fiscal operation had to remain consistent even though the technical integration behind each organization was different.
The invoice is more than its XML
The electronic document provides the initial fiscal content, but its operational condition continues to evolve afterwards. Receipts, delivery notifications, accounting outcomes, rejection or acceptance messages and statutory deadline events progressively complete the fiscal reality around the Invoice.
Some decisions must happen before accounting
Configured controls can determine that an incoming invoice is not eligible for further processing and must be rejected before entering the accounting environment. Invalid or non-compliant content therefore does not need to propagate into downstream systems before being detected.
One Invoice can create a distributed conversation
SDI, certified channels, Coopera, healthcare organizations and accounting systems can all interact with the same Invoice at different moments. Those messages cannot become independent technical events. They must remain attributable to one Invoice and one operational history.
The accounting landscape itself can change
Over time, the original heterogeneous environment progressively converged toward a common regional SAP model. The accounting systems changed. The operational identity and fiscal lifecycle of the Invoice did not need to change with them.
3. How Coopera holds the operation together
In this complex scenario the primary Living Busisness Object identified is the Invoice.
Invoice
Every supplier Invoice is maintained as a Living Business Object with its own persistent identity, lifecycle, current condition and operational evidence. It can keep connected: Invoice XML · Attachments · Issuing Supplier · Healthcare Organization · Validation Results · SDI Receipts · Delivery Notifications · Accounting Outcomes · Acceptance / Rejection Messages · Deadline Events · Protocol Evidence · Preservation Evidence · History.
- The XML can arrive.
- Controls can execute.
- The Invoice can be transferred to an ERP.
- The accounting system can respond later.
- SDI can subsequently produce another notification.
- A statutory deadline can expire.
The Invoice remains the persistent point of continuity throughout all of them. This distinction becomes particularly important because the messages surrounding an Invoice do not need to become independent operational cases. They remain governed content and events associated with the same Living Business Object. But they are operationally significant.
- A delivery notification confirms a new condition.
- A rejection changes the lifecycle.
- An explicit acceptance changes it again.
- Expiry of the statutory response period establishes another governed outcome.
The content around the Invoice continuously changes what has happened and what can happen next.
4. What This Looks Like in Practice
From Fiscal Reception to Accounting
Controls determine whether the Invoice can proceed. When a supplier invoice enters through the national e-invoicing environment, Coopera identifies the relevant healthcare organization and establishes the corresponding operational context.
Configured validation and business rules evaluate the Invoice before it reaches accounting. Where the required conditions are satisfied, the Invoice is transmitted to the appropriate accounting environment. Where they are not, the fiscal operation can move toward rejection without introducing invalid content into downstream accounting processes.
The accounting record is therefore not what determines whether the Invoice exists operationally. The Invoice already has a governed life before accounting begins.
Fiscal Messages Change the Invoice
Communication becomes part of operational state. Once execution has started, subsequent messages continue to change the meaning of the Invoice.
- A notification from SDI may confirm delivery.
- An ERP outcome may express acceptance or rejection.
- Another communication may indicate an error.
- A statutory deadline may expire without explicit response.
These are not merely messages to archive. Each one contributes evidence and can change the Invoice’s current fiscal condition. Content does not simply document the lifecycle. It participates in determining it.
Accounting Systems Remain Specialist
ERP execution without ERP ownership of the whole operation. Once the required conditions are satisfied, the accounting system performs the responsibilities for which it was designed. Its relevant outcomes return to Coopera, are correlated with the persistent Invoice and, where required, generate the appropriate interaction back toward SDI.
- Accounting remains accounting.
- The national infrastructure continues managing fiscal exchange.
- Certified channels continue transporting communications.
Coopera preserves the operational context connecting their individual responsibilities
From 18 ERP Systems to Regional SAP
The systems change, the Invoice model persisted. The original regional deployment had to interact with 18 different accounting products. Over time, the healthcare system progressively consolidated its accounting landscape around regional SAP. That is a major enterprise transformation. Yet the Invoice did not need to be redefined according to whichever accounting technology happened to exist at a particular moment. Its persistent identity, fiscal lifecycle, evidence and interaction model remained above those implementation changes.
- Integration changed.
- Execution participants changed.
The business object remained. This is one of the strongest aspects of the case: the operational architecture survived a major transformation of the underlying systems without requiring the operation itself to lose continuity.
5. Mission-Critical Fiscal Operations at Regional Scale
The same operating model serves 18 public healthcare organizations while preserving the fiscal and accounting context appropriate to each one.
More than 12 million supplier invoices have been processed since the platform entered production. Today, more than 200,000 invoices and related messages every month participate in the environment. At this scale, correlation is as important as transaction processing. A large number of individual messages is meaningful only because every response, notification and outcome remains associated with the Invoice that gives it business significance.
The platform therefore maintains not simply throughput, but millions of coherent fiscal histories. And it has continued doing so in production for more than a decade while the regional accounting architecture changed around it.
6. The Outcome
The regional healthcare system operates one common electronic-invoicing model across 18 organizations, independently of the accounting technology used by each organization.
Incoming invoices are automatically acquired, identified, correlated and validated. Configured rules can reject non-compliant invoices before they enter accounting, while eligible invoices continue into the appropriate ERP environment. From that point onward, the Invoice remains active.
Accounting outcomes, SDI notifications, explicit acceptance or rejection and statutory deadline events continue to update the same persistent operational context until its final fiscal condition is known. This produces a continuous and auditable history from national e-invoice reception to regulated outcome.
The model has also proved resilient to enterprise change. The original environment connected 18 different ERP products. As the regional accounting landscape progressively converged toward SAP, the operational identity and lifecycle of the Invoice remained stable.
More than 12 million invoices have now passed through the environment, and current production volumes exceed 200,000 invoices and related messages every month.
The result is not simply a regional e-invoice gateway. It is a persistent fiscal operating model in which every Invoice remains coherent while national channels, business rules, accounting systems and regulatory events progressively determine its final outcome.
5. What This Case Proves
A fiscal document can become a Living Business Object
The Invoice maintains identity, lifecycle, operational condition, relationships and evidence while systems and messages continuously act around it.
Content can directly change operational condition
Receipts, acceptance and rejection messages, accounting outcomes and statutory events do more than document what happened — they can determine what happens next.
Persistent operational context can survive system transformation
The same Invoice model operated across 18 heterogeneous ERP environments and continued as regional accounting progressively converged toward SAP.
Mission-critical orchestration can persist at scale and over time
More than 12 million invoices have been processed across more than ten years of continuous production, with over 200,000 invoice and message interactions currently handled every month.
