---
title: "Invoice Response"
canonical: https://documentation.maventa.com/integration-guide/peppol/invoice-response/
---
## What is an invoice response?
An invoice response is a message between buyer and seller that provides an efficient way to communicate the processing status of a received invoice in the Peppol network.
For example, the buyer can inform the seller whether an invoice has been rejected, is under query, has been approved, or has been paid.
For detailed use cases and the full specification, see the [Peppol BIS Invoice Response 3.2 documentation](https://docs.peppol.eu/poacc/upgrade-3/profiles/63-invoiceresponse/).
> [!NOTE]
> This page describes invoice responses in the **Peppol** network. Danish invoices can also be received over **Nemhandel**, where the buyer sends a response through a different endpoint (`POST /v1/invoices/{id}/responses/nemhandel`) that Maventa forwards to Nemhandel (Sproom) as an OIOUBL Application Response. See the [Denmark page](https://documentation.maventa.com/services-and-reach/denmark/) for the Nemhandel invoice response flow.
## Setting up invoice responses
### For a company sending invoices (seller)
When a company sends invoices, it is the seller and therefore the receiver of invoice responses from the buyer. Follow these steps to enable receiving.
#### Step 1: Register for invoice response receiving
Register a receiving profile for invoice responses in the Peppol network.
Call [POST /v1/company/profiles](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoXChange%20API#/company/postV1CompanyProfiles) with the following parameters:
- **profile**: `INVOICE_RESPONSE`
- **network**: `PEPPOL`
This is added on top of any existing Peppol registration. Send only `INVOICE_RESPONSE` — the request is processed as a single operation, so if it also includes a profile that is already registered (such as `INVOICE_AND_CREDIT_NOTE`), the entire request fails and the new profile is not added.
Once the profile is created, use [GET /v1/company/profiles](https://swagger.maventa.com/?urls.primaryName=STAGE+-+AutoXChange+API#/company/getV1CompanyProfiles) to verify that the profile has been activated for the `PEPPOL` network.
#### Step 2: Integrate with the documents endpoint
Incoming invoice responses are received through the documents endpoint. See the [document receiving](https://documentation.maventa.com/integration-guide/peppol/document-exchange/#document-receiving) section for details on listing and downloading received documents.
#### Step 3: Process the received invoice response
Parse the received XML and update your system accordingly. For details about the content and structure of invoice responses, see the [Peppol documentation](https://docs.peppol.eu/poacc/upgrade-3/profiles/63-invoiceresponse/).
### For a company receiving invoices (buyer)
When a company receives invoices, it is the buyer and therefore the sender of invoice responses to the seller. Follow these steps to enable sending.
#### Step 1: Integrate to receive invoices
Set up invoice receiving so you have invoices to respond to.
#### Step 2: Check if the seller supports invoice responses
Before sending an invoice response, check whether the seller can handle invoice response documents. Use the [GET /v1/lookup/receivers](https://swagger.maventa.com/#/lookup/getV1LookupReceivers) endpoint with the seller's identifier from the received invoice.
In a Peppol BIS 3.0 document, the seller's identifier is in the `EndpointID` element:
```xml
567
...
003751734872004
...
```
The lookup requires three parameters:
- `network` — set to `PEPPOL`
- `document_type` — set to `INVOICE_RESPONSE`
- `eia` — the seller's identifier in the format `0216:003751734872004` (taken from the received invoice)
### Request (curl)
```bash
curl -X 'GET' \
'https://ax-stage.maventa.com/v1/lookup/receivers?network=PEPPOL&eia=0216%3A003751734872004&document_type=INVOICE_RESPONSE' \
-H 'accept: application/json' \
-H 'authorization: Bearer TOKEN'
```
### Response (json)
```json
[
{
"eia": "0216:003751734872004",
"network": "PEPPOL",
"operator": "PEPPOL",
"document_types": [
{
"document_type": "INVOICE_RESPONSE",
"document_identifier": "urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2::ApplicationResponse##urn:fdc:peppol.eu:poacc:trns:invoice_response:3::2.1",
"process_identifier": "urn:fdc:peppol.eu:poacc:bis:invoice_response:3"
},
...
],
"participant": {
"name": "Seller",
"country": "FI"
}
}
]
```
If the seller is registered for invoice responses, the endpoint returns matching entries. If not, the response is an empty array.
#### Step 3: Generate and send an invoice response
Create a compliant invoice response XML document. For details about the business content and structure, see the [Peppol BIS Invoice Response specification](https://docs.peppol.eu/poacc/upgrade-3/profiles/63-invoiceresponse/).
Below is an example invoice response payload that acknowledges receipt of invoice `567` from seller `0216:003751734872004`:
```xml
urn:fdc:peppol.eu:poacc:trns:invoice_response:3
urn:fdc:peppol.eu:poacc:bis:invoice_response:3
1
2024-01-01
003751734872001
Buyer
003751734872004
Seller
AB
567
380
```
Send the invoice response XML via the [POST /v1/documents](https://swagger.maventa.com/#/documents/postV1Documents) endpoint:
```bash
curl -X 'POST' \
'https://ax-stage.maventa.com/v1/documents' \
-H 'accept: application/json' \
-H 'content-type: multipart/form-data' \
-F 'file=@response.xml;type=text/xml' \
-F 'recipient_eia=0126:003751734872004' \
-F 'recipient_operator=PEPPOL'
```
Response:
```json
{
"id": "e6c1e92b-ceba-4155-89fd-072e7ba6148f",
"type": "INVOICE_RESPONSE"
...
}
```
## Response codes
Each invoice response carries a single status code that communicates the current processing state of the invoice. The code is set in the `ResponseCode` element using the [UNCL4343 code list subset](https://docs.peppol.eu/poacc/upgrade-3/codelist/UNCL4343-T111/).
| Code | Status | Description |
|---|---|---|
| `AB` | Message acknowledgement | The invoice has been received and is ready for processing. |
| `IP` | In process | The invoice is being processed in the buyer's system. |
| `UQ` | Under query | Processing is on hold — the buyer needs additional information from the seller. |
| `CA` | Conditionally accepted | The invoice is accepted under conditions, such as pending minor corrections. |
| `RE` | Rejected | The buyer will not process the invoice. The seller typically needs to issue a corrected invoice. |
| `AP` | Accepted | The invoice has been accepted and approved for payment. |
| `PD` | Paid | The invoice has been paid in full or in part. |
Status codes follow a general progression: `AB` → `IP` → `UQ` → `CA`/`RE`/`AP` → `PD`. Not all statuses need to be used — for example, a buyer may go directly from `AB` to `AP`. The statuses `RE` and `PD` are final; no further responses should be sent after these.
> [!NOTE]
> Each invoice response message carries one status code at a time. To communicate a status change, send a new invoice response with the updated code.
## References
- [BIS Invoice Response 3.2 specification](https://docs.peppol.eu/poacc/upgrade-3/profiles/63-invoiceresponse/)