News
November 18, 2026

Message Level Status becomes mandatory on Peppol in 2027

Peppol replaces the Message Level Response with Message Level Status. Receiving is due 28 February 2027, sending 31 March, with service levels attached.

Two dates in early 2027 change what every Peppol Access Point owes the rest of the network. Message Level Status, or MLS, becomes a required capability for receiving by 28 February 2027 and for sending by 31 March 2027, and the Message Level Response it replaces is retired on 1 May 2027.

The reason this matters more than a specification bump is that MLS arrives with service levels attached. The obligation is not only to emit a status. It is to emit it quickly enough, often enough, and that is a different engineering problem.

A Message Level Status is how one provider tells another what happened to a document

Peppol is the interoperability framework used to exchange standardised electronic business documents, governed by OpenPeppol. It runs on a four-corner model: a sender connects to its own service provider, which exchanges the document with the receiver's service provider, which delivers it to the receiver. The two providers in the middle are the Access Points.

That architecture creates a reporting problem. When an Access Point accepts a document for transmission, the transport layer confirms only that the message arrived at the other Access Point. It says nothing about whether the receiving provider could actually process the payload, or whether it was rejected on validation at the far edge. MLS is the structured answer travelling back: a machine-readable statement of what became of a specific business document, returned to the sender's side of the network.

The dates are staged deliberately, and receiving comes first

The sequence is worth reading carefully, because the two capabilities are not symmetrical obligations arriving together.

Registering the receiving capability is the part that is easy to underestimate. It is not enough to be able to process an MLS; the Service Metadata Publisher entry has to say so, because that is where a counterparty looks before it sends anything. A provider that builds the capability and does not publish it has done the work and still cannot be reached.

    The enforceable service levels are the real change

    MLS carries service levels of 99.5% within 20 and 25 minutes. Put less abstractly: a status is not a best-effort courtesy returned when a batch job next runs. It is a timed obligation measured across a population of messages, and a provider whose status pipeline depends on an overnight process will not meet it.

    This is the part that converts a protocol change into an architecture question. Returning a status within twenty minutes means the validation result, the delivery outcome, and the processing outcome all have to be available to the status pipeline within that window, including when a downstream system is slow or unavailable. Most providers will find the constraint sits in their own back end rather than in the Peppol-facing component.

    Access Point failures are quiet, which is why dated obligations get missed

    Peppol obligations have a habit of failing in ways that look like someone else's problem. An expired message-signing certificate presents as counterparties rejecting your documents, not as an outage on your monitoring. A stale truststore leaves every counterparty untrusted while the service reports healthy. A missed discovery migration breaks resolution only for participants not already cached.

    MLS will behave the same way. A provider that misses the February date will not go offline. It will simply stop being reachable for a document type that counterparties increasingly expect, and will learn about it from a customer rather than from a dashboard. That is the argument for a small set of explicit, scheduled checks against the published obligations rather than reliance on uptime monitoring.

    If you use Peppol rather than operate it, this is a supplier question

    Most organisations on the network are not Access Points. They connect through one, which means these dates are not theirs to meet but are very much theirs to verify. The practical consequence of a provider missing them is a loss of visibility: statuses that used to come back stop coming back, or never start.

    It is also worth separating MLS from the other dated obligations in the same period, because they are frequently bundled together in conversation and they are not the same thing. Specification versions move on their own cycle, roughly twice a year, each becoming mandatory some months after publication. Certificate generations change on their own schedule. OpenPeppol's information-security requirement for service providers carries its own date in 2027. None of these substitutes for any other.

    Four questions worth putting to your provider

      Semansys operates its own Peppol Access Point and its own Service Metadata Publisher, which means these obligations bind us directly rather than through a third party. You can read more about how we handle connection, discovery, and transport and what the platform does with a document once it arrives.

      One caveat, stated rather than buried. The dates and service levels above are drawn from OpenPeppol's published specifications and policies as recorded in our own standards documentation, not read off the specification on the day of writing. Specifications move, and anyone planning a 2027 release schedule against them should confirm the current figures in the Peppol Message Level Status specification before committing to them.

      Would you like to discuss how Semansys supports secure, interoperable e-invoicing and regulatory data exchange? Book a discovery call