Skip to main content

Invoice Responses

GoRoute does not currently offer an API for sending an Invoice Response. If you have received an invoice and want to tell the supplier that you have accepted it, rejected it, or have a question about it, there is no GoRoute endpoint that will send that message over the Peppol network for you today. This page explains what the Peppol Invoice Response is, what GoRoute does do, and what to do instead.

This page previously described a feature that does not exist

Earlier revisions of this page published a call for sending an Invoice Response, along with a request format and a set of status codes to send. None of it was ever built, and any integration written against it will fail. If you built against that page, nothing you can change in your request will make it work — see What to do instead.

What a Peppol Invoice Response is​

Peppol defines an Invoice Response message (a UBL ApplicationResponse) that lets a buyer tell a supplier what has happened to an invoice — that it has been received, accepted for payment, rejected, queried, or paid. It travels over the same network as the invoice, in the opposite direction, and it is a distinct Peppol business document with its own profile.

It is optional in most of the Peppol network. Where a country's rules require it, that requirement falls on the buyer, and it is not currently something GoRoute can carry out on your behalf.

What GoRoute does today​

Message Level Status, in the Oman flow only​

The platform generates and exchanges a Message Level Status (MLS) automatically as part of the Oman tax-reporting flow. An MLS is also a UBL ApplicationResponse, but it is a different thing from an Invoice Response: it reports what happened to the message — whether it was accepted or rejected in transit — rather than a buyer's commercial decision about the invoice.

Three things follow from that, and they are worth being blunt about:

  • It is automatic. You do not trigger it, and there is no request body for you to fill in.
  • It is Oman only. It is produced by the Oman tax-reporting pipeline, which is enabled for Oman document exchanges. An invoice sent to a Belgian, Australian or Dutch buyer has no MLS.
  • The codes are AP (accepted) and RE (rejected). These are values you read off a transaction. There is no call that lets you choose one and send it.

Reading an MLS​

Where an MLS exists, you can retrieve it in its original, unaltered form:

GET /api/v1/transactions/{transaction_id}/mls

It returns the UBL ApplicationResponse XML, and needs an API key with the transactions:read permission. A transaction can have two MLS legs, so an optional leg parameter chooses between them:

legWhich message you get
sentThe ApplicationResponse GoRoute sent on your behalf
receivedThe ApplicationResponse GoRoute received about your document
omittedThe sent leg if there is one, otherwise the received leg

Ask GET /api/v1/transactions/{transaction_id}/reporting first to see which legs exist. The MLS endpoint answers 404 when a transaction has no MLS at all — which, outside the Oman flow, is the normal case rather than an error.

import requests

API_BASE = "https://app.goroute.ai/peppol-api"


def get_mls(transaction_id: str, leg: str | None = None) -> str | None:
    """Fetch a transaction's Message Level Status as UBL XML, if it has one."""
    response = requests.get(
        f"{API_BASE}/api/v1/transactions/{transaction_id}/mls",
        params={"leg": leg} if leg else None,
        headers={"X-API-Key": "your_api_key"},
    )

    if response.status_code == 404:
        return None  # No MLS for this transaction

    response.raise_for_status()
    return response.text

Status events for invoices you sent​

If a status comes back about an invoice you sent, and it arrives through the Oman MLS flow, GoRoute raises a webhook event for it. The event name reflects the status: response.accepted when the message was accepted, response.rejected when it was rejected, and response.received when the status is anything else. Subscribe to these the same way as any other event — see Webhook Setup. They are things you are told about; they are not things you can send.

What to do instead​

If you need to accept, reject or query an invoice you have received, handle it outside the Peppol network for now:

  1. Record the decision in your own system. Your accounts payable workflow is the source of truth for whether an invoice is approved, queried or paid. See Processing Documents for the pipeline.
  2. Contact the supplier directly — email or your existing supplier portal — when you need to reject an invoice or ask about it. Give the invoice number and the specific reason, so the supplier can issue a credit note or a corrected invoice.
  3. Ask the supplier for a credit note where an invoice is wrong. A credit note is a real Peppol document, it travels the network normally, and GoRoute both sends and receives it. That is the supported way to correct an invoice that has already been exchanged.

If you need this​

Invoice Response support is not published on a roadmap, and this page does not promise it. If sending Invoice Responses over Peppol is a requirement for you — particularly if it is a regulatory requirement in a market you operate in — tell us, through Support, and say which market and which profile you need. That is the useful signal, and it is more use to us than a guess.

Next Steps​

Last updated on