MLR & Invoice Response (BLR)

Overview

PEPPOL supports acknowledgements beyond “message left our system”:

Signal	Direction	Purpose
MLR (Message Level Response)	About a sent sales invoice	Network/access-point level accept/reject
Invoice Response (BLR)	On a received purchase invoice	You tell the vendor how you process their invoice

MLR on outbound (AR)

1. You send a sales invoice via PEPPOL.
2. The receiver’s infrastructure may return an MLR.
3. Tapr matches the MLR to the Sales Invoice (e.g. by PEPPOL reference) and updates MLR status.

Use MLR status to distinguish transport success from business/network rejection reasons.

What to do when MLR is rejected

1. Open the sales invoice in Out Docs.
2. Read the MLR reason.
3. Correct data if needed; coordinate with the customer if the issue is on their side.
4. Decide whether a corrected re-send is appropriate.

Invoice Response on inbound (AP)

From a received Purchase Invoice in Invoice Manager you can send an Invoice Response (BLR codes) to communicate acceptance, rejection, or other processing codes defined by PEPPOL BIS Invoice Response.

Before you write the response, Tapr checks whether the supplier’s Peppol ID accepts Invoice Responses. If it does not, or the lookup cannot be completed, Invoice Manager explains why and does not send.

1. Open the purchase invoice in In Docs.
2. Choose Send Invoice Response.
3. Pick the response code (and reason when required).
4. Submit — Tapr records BLR send status on the invoice.

Related topics

• PEPPOL Overview
• Reviewing & Sending Sales Invoices
• Processing Incoming Invoices