EU Peppol Inbound MLR
Receive Peppol inbound responses (MLR / Invoice Response): parse UBL ApplicationResponse, map status to e-invoice documents, raise follow-up activities
Want EU Peppol Inbound MLR installed and configured for you? Onboarding Pack: $350 one-off
Support plans from $425 a monthEU Peppol Inbound MLR & Invoice Response
Receive, parse and act on the responses that travel back over Peppol — transport MLR and business Invoice Response — for Odoo 18, 19 & 20
Sending invoices on Peppol is only half the loop. Once an invoice is
dispatched, two documents come back: the Message Level Response (MLR)
from the receiving Access Point, and the Invoice Response the buyer
assigns (received, under query, accepted, rejected, paid). This module
receives both, parses the UBL ApplicationResponse, maps the
status onto your e-invoice document, and raises a follow-up activity when a
human needs to react.
MLR + Invoice Response parser
A real UBL 2.1 ApplicationResponse parser classifies and
reads both the transport MLR (poacc:trns:mlr:3) and the
Peppol BIS Invoice Response (poacc:trns:invoice_response:3),
extracting the response code, business status (UNCL4343), status reason
(UNCL4451), referenced invoice ids, endpoints and per-line clarifications.
Status mapping engine
Each response code is mapped onto the e-invoice document state machine (submitted, accepted, rejected, error) with an alert level and a needs-action flag. Accepted and Paid close the loop; Rejected and Under Query open a follow-up.
Automatic correlation
Inbound responses are matched to the originating customer invoice and its e-invoice document by referenced document id, and drive the document's state automatically — no manual reconciliation.
Activity alerts
When a response is rejected or under query, an idempotent To-Do activity is scheduled on the invoice and assigned to its owner, with the reason and any per-line clarifications. A red ribbon flags invoices needing attention.
Import & simulate wizard
Upload a real ApplicationResponse, paste XML, or generate a realistic sample of any status to preview exactly how a given buyer response would be mapped before you go live.
Bring your own transport
The module never connects to a network itself. Your Access Point or mail layer hands raw response XML to a single public method (or the wizard), and a scheduled action drains the queue. No invoice data leaves your database. We are a software vendor, not a Peppol Access Point or service integrator: you bring your own transport / mailbox. Email support is included, and the purchase is refundable within the Odoo Apps Store policy window.
Built for the ViDA wave
As Belgium, Poland, France, Germany, Croatia and more bring B2B Peppol mandates live across 2026–2028, the inbound response loop becomes operationally critical. This module is built on the e-Invoice Core Engine document state machine and complements any country Peppol connector. Compatible with Odoo 18.0, 19.0 and 20.0.
Screenshots
Import Simulate
Processed Inbound Notificati
Inbound Notifications List A
Support: support@pokutsoft.com
Update date: 2026-09-03
User guides (PDF)
Related modules
Claims Quantum Register
Construction claims register: entitlement events, heads of claim with prolongation, measured-mile disruption, escalation and Hudson / Emden / Eichleay quantum, cost evidence, submission versions and settlement invoicing
Price Escalation Indices
Contract price adjustment by cost indices: index catalogue with CSV import, contract formulas with fixed and weighted parts, lag, threshold and cap, monthly statements, final-index revisions and adjustment invoices
Bank Statement Import Pro (CAMT.053 / MT940 / OFX / QIF + AI)
Import bank statements from CAMT.053, MT940, OFX/QFX and QIF files with auto-format detection, reconciliation suggestions and optional bring-your-own-key AI categorization.