Replacing MLR with MLS, A Move Toward Machine-Coordinated Commerce?

The Peppol network is gradually evolving from a document exchange framework into infrastructure capable of supporting machine-coordinated commercial processes across organizations and jurisdictions.

That may sound abstract at first.

But if we look at where the network seems to be heading, particularly through the transition from Message Level Response (MLR) to Message Level Status (MLS), an interesting picture starts to appear.

Building on existing structured business standards such as UBL and BIS process models, the network is increasingly formalizing commercial states, obligations, and process outcomes in a way machines can understand and act upon.

The Peppol network is evolving

The network is already process-aware

Peppol was never merely a document transport network. From the beginning, the architecture was built around standardized business process choreography. Invoices, orders, despatch advice, catalogues, and responses were designed to exist within structured procurement and commercial processes rather than as isolated messages.

But process-awareness alone is not the same thing as state-awareness.

• A process-aware network understands that a workflow exists.
• A state-aware network understands the current condition of that workflow.

This is where the Peppol network is evolving.

MLS signals a deeper architectural shift

One of the most interesting recent developments in the Peppol ecosystem is the transition to MLS. At first glance, this may appear to be a relatively technical specification update. In reality, it potentially signals something much larger.

OpenPeppol is no longer only standardizing document exchange and document acknowledgements. Through MLS, the network is increasingly standardizing the messaging state itself.

This distinction matters because:

• A “response” is tied to an individual document interaction.
• A “status” represents an ongoing condition within a broader process.

That change in terminology reflects a broader architectural evolution occurring across the network. The emerging MLS architecture distinguishes between protocol-level status, messaging-level status, and business-level status as distinct interoperability layers within the Peppol architecture.

This is an important conceptual shift. Historically, transport-level acknowledgements and business-level responses often overlapped conceptually. MLS introduces a clearer and more formalized state model for the network itself.

Where MLR responds to individual document exchanges, MLS introduces a broader status layer that spans the delivery lifecycle, a shift in scope that may over time point toward a state-aware network architecture.

The network is becoming state-aware

This evolution becomes even clearer when examining national CTC and e-invoicing mandates. Governments and tax authorities are no longer satisfied with simple invoice exchange. Increasingly, they expect infrastructure capable of supporting real-time reporting, lifecycle visibility, transaction traceability, and automated compliance verification.

This evolution is already becoming visible in jurisdictions such as the UAE. There, the UAE Ministry of Finance (MoF), through its Peppol-based e-invoicing framework, requires Message Level Status (MLS) mechanisms to provide greater visibility into invoice lifecycle states, Tax Data Document (TDD) processing states, and validation outcomes.

The UAE’s adoption of MLS in its e-invoicing framework illustrates how national mandates are pulling the network toward greater state-awareness through workflow stages, validation outcomes, and lifecycle progressions. This matters because state-awareness is a prerequisite for automation.

Machines cannot autonomously coordinate commercial workflows or tax reporting unless systems can consistently represent commercial states across organizations and jurisdictions. Peppol is gradually developing these capabilities through continuous incremental standardization. The emergence of MLS is one of the clearest examples of that evolution currently taking place.

The most important development in Peppol today is not only the invoice.

Future possibilities

So where might this lead us? If this trajectory continues, increasingly standardized commercial states and interoperable business semantics may create the foundation for limited agent-to-agent commercial coordination, where systems negotiate pricing, generate agreements, issue orders, coordinate delivery states, and trigger invoicing workflows with reduced human intervention.

This is not because Peppol has now been redesigned for autonomous agents or AI-driven commerce. Rather, the increasing standardization of business semantics, process states, lifecycle coordination, and interoperability frameworks gradually enable more machine-coordinated commercial interactions.

The most important development in Peppol today is not only the invoice. It is the emergence of a shared language that allows systems, platforms, tax authorities, and organizations to coordinate economic activity in a structured and interoperable way.

If this development continues, Peppol may ultimately become remembered not only as interoperability infrastructure for electronic business documents, but as one of the earliest foundations for machine-coordinated commerce.

Preparing for the Next Generation of Peppol

As Peppol evolves from document exchange toward more state-aware and process-aware infrastructure, service providers and software vendors will need technology that can support more than basic connectivity. Arratech provides the Access Point, SMP, validation, monitoring, and status infrastructure needed to build compliant Peppol services without developing and operating the full network layer internally. If you are preparing for new Peppol-based mandates or expanding your existing e-invoicing offering, speak with Arratech about how our infrastructure can support your next market.

CONTACT US