A Peppol invoice response is a structured status message a buyer sends back to a supplier about one specific invoice. It reports whether the invoice was received, is in process, is under query, has been accepted or has been rejected. Because it travels over the same Peppol network as the invoice, the supplier's system can update its records without manual follow-up.
Key takeaways
- A Peppol invoice response is a coded status message that a buyer returns to a supplier about a single invoice.
- The common statuses are received, in process, under query, accepted and rejected, and each one tells the supplier something different.
- Responses only help when they are generated from the same record that finance uses, at the right moment in the approval flow.
- A rejection is only useful when it carries a reason the supplier can act on.
What does a Peppol invoice response tell the supplier?
A Peppol invoice response tells the supplier the current state of one invoice in the buyer's process, expressed as a coded status. The status is the only part of the message that the supplier's software is expected to act on, so it has to be accurate at the moment it is sent.
The Peppol BIS Invoice Response specification, published by OpenPeppol in the Peppol BIS Invoice Response documentation, defines the invoice response transaction and the status codes it can carry. The codes most teams encounter are AB for a message acknowledged as received, IP for in process, UQ for under query, AP for accepted and RE for rejected. Each response refers back to the original invoice by its identifier, which is what lets the supplier match the status to the right document.
Not every status closes the matter. AB and IP are interim signals, UQ keeps the invoice open until the buyer and supplier resolve a question, and AP or RE end the buyer's decision. A supplier that only watches for AP can wait indefinitely on an invoice that was quietly put under query, so buyers should treat UQ as a real state rather than a silent pause.
When should a buyer send each status?
Send each status when the event it describes has actually happened, not when a batch job runs. The right timing is the main difference between a response that helps the supplier and one that creates confusion.
Received and in process
Send received once the invoice has passed intake and is stored against a purchase order or cost centre. Send in process only when internal checks are running that do not need supplier input. Sending both in quick succession adds noise, so many teams send only one of them.
Under query
Send under query when the invoice cannot move forward without an answer from the supplier, such as a missing purchase order reference or a quantity that does not match a delivery note. The query should name the exact question in the message's free-text field, because a bare UQ status leaves the supplier guessing.
Accepted and rejected
Send accepted when an approver or an approval rule has released the invoice for payment. Send rejected when the invoice cannot be corrected by the supplier's answer alone, for example when the goods were never received or the invoice is a duplicate. Rejection should always state a reason.
How do responses get back into your ERP?
Responses are created most reliably from the same record that holds the invoice in your ERP or accounting system. If the response is built from a separate spreadsheet or a copy of the data, the status will drift away from what finance sees. Rui Codex offers technical implementation support for connecting these systems, as described on the integrations service page.
A typical setup has three parts: the ERP emits an event when the invoice status changes, a middleware layer maps that event to the correct Peppol status, and an access point sends the message on the network. Each part can fail separately, so logging at each step matters more than the elegance of the mapping. For teams working on ERP and CRM data flows more broadly, the ERP and CRM integration service covers the same kind of event-driven design.
The trade-off is between automation and control. Fully automatic acceptance is fast but removes the human check that catches wrong purchase orders. Fully manual responses are safe but slow and easy to forget. Most teams settle on automatic receipt and manual query or rejection, with acceptance driven by a rule that checks amounts and references.
Hypothetical examples of response handling
Here are two hypothetical scenarios:
Scenario one: a duplicate invoice
Prefer a delivered project to a scenario? Read the case study: Yirmibes Web ERP Software.
A buyer's intake step matches an incoming invoice to one already stored under the same supplier reference. The system sends RE with a reason that names the earlier invoice. The supplier can check its records and either confirm the duplicate or issue a correction, and nobody has to search through email.
Scenario two: a missing purchase order reference
An invoice arrives without a purchase order number that the buyer's rules require. The system sends UQ with the question written in plain language. When the supplier replies with a corrected invoice, the buyer sends AP on the new document and the old one is closed with a rejection that points to its replacement.
Neither scenario depends on a particular software product. The value comes from the reason text and from closing every open state. Without those two elements, both cases turn into email threads.
Where do invoice responses fail in practice?
Most failures come from identifiers, timing and missing reasons rather than from the network itself. Responses that cannot be matched to the original invoice are silently dropped or logged on the wrong record.
- The participant identifier in the response does not match the supplier's registered identifier on the network.
- The response refers to an invoice number that was altered during correction, so the reference no longer matches.
- The status is generated from a stale copy of the record, which shows the invoice as received after it was already accepted.
- A rejection carries no reason, so the supplier cannot decide whether to correct or reissue.
- Open queries are never closed, leaving the supplier with an invoice that looks unresolved indefinitely.
When a response does not arrive, check the reference data and the send log before blaming the network. In most cases the message was sent, but it could not be matched to the record that the supplier expected.
Are invoice responses required by law?
Peppol invoice responses are a messaging convention within the Peppol framework, and whether a buyer must send them depends on the contract, the sector and the national rules that apply. The European rules for electronic invoicing in public procurement are set out in Directive 2014/55/EU on electronic invoicing in public procurement, which refers to a European standard for the invoice itself rather than prescribing a response workflow. Check the specific obligation before designing your process around it. This article is general information and not legal or tax advice. Rui Codex offers technical implementation support only, not legal, tax or compliance advice.
What should you check before going live?
Before you switch on automatic responses, confirm the following items with the people who own finance, purchasing and the supplier relationship.
- Every internal approval state maps to one Peppol status, and no two states share a status.
- Each response references the exact invoice identifier that the supplier used.
- Rejections always carry a reason written for the supplier, not for internal staff.
- Every query has a named owner and a target for closing it.
- Test messages have been sent to a test participant and the status history matches the internal record.
- Send logs are kept long enough for disputes, and someone is responsible for reading them.
If you want a second pair of engineering eyes on the mapping, you can request a project consultation at the Rui Codex contact page.
Frequently Asked Questions
Is a Peppol invoice response the same as a payment confirmation?
No. A Peppol invoice response reports the processing status of an invoice, such as received, under query, accepted or rejected. It does not confirm that money has moved. Payment is handled through the normal banking process, and a buyer who wants the supplier to know about payment needs a separate arrangement. Keep the status message and the payment record separate so that a response is never read as proof of payment.
Which status should I send if I need more information before approving?
Send under query, code UQ, when the invoice is received but a question blocks approval. The supplier can then see that the invoice is open and what is expected from them. Use in process only for internal checks that do not need supplier input. Once the question is resolved, send accepted or rejected so that the supplier's record reaches a final state.
Can a rejected invoice be resubmitted under the same number?
Whether a rejected invoice can be resubmitted under the same number depends on the rules that apply to your invoices, so confirm those before acting. In practice, many suppliers issue a corrected invoice or a credit note and send a new document, which keeps a clear trail. Reusing a number can create duplicates in the buyer's system, so agree the approach with the supplier before resending.
Do I need a special integration to send invoice responses?
You need a system that can create the response message in the Peppol format, send it through an access point, and tie it to the invoice record. A manual upload can work at low volumes but cannot keep statuses synchronised. Most teams connect their ERP or accounting system to the access point so that status changes trigger responses automatically. Rui Codex offers technical implementation support for this kind of connection.
What is the most common cause of a response that never reaches the supplier?
The most common cause is an identifier mismatch, where the response is addressed to a participant identifier that does not match the one the supplier registered on the network. Other causes include a missing reference to the original invoice and a response built from a copy of the record that was never updated. Check the reference data and the send log before assuming the network failed.
Conclusion
Peppol invoice responses are simple in principle: they tell a supplier whether an invoice was received, is being checked, needs an answer, was accepted or was rejected. The difficulty lies in timing, in matching each message to the right invoice and in writing rejection reasons that someone can act on. Start by mapping your internal states to Peppol statuses, then test with a small set of invoices before you automate. If you would like to talk through your setup, request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com.
Sources
- Peppol BIS Invoice Response 3.2 documentation - OpenPeppol
- Directive 2014/55/EU on electronic invoicing in public procurement - European Union, EUR-Lex