Step 1: Supplier creates Standard Business Document

Each invoice sent to Sovos must be part of a Standard Business Document . This document includes a Standard Business Document Header (SBDH) and a Sovos Document node, which in turn includes a Sovos Canonical Invoice (SCI). To create the SBD, follow the detailed instructions in the SBDH, Sovos Document, and SCI pages. The following section explains some of the most important elements that you should include in the SBD and the invoice.

SBDH - Invoice / Lifecycle

The SBDH must be created using the following values:

Note:

Include all the required nodes as specified in the SBDH schema. If the information cannot be provided, and the respective required node has not been mentioned on the current page, for example, the receiver.identifier, the node can be left empty but must still be included in the SBDH.

Node	Required	Attributes	Value
StandardBusinessDocumentHeader.Sender.Identifier	Yes	Authority="BE"	Supplier's VAT Number
StandardBusinessDocumentHeader.Receiver.Identifier	Yes	Authority="BE"	Buyer's VAT Number
StandardBusinessDocumentHeader.DocumentIdentification.Standard	Yes		urn:oasis:names:specification:ubl:schema:xsd:Invoice-2
StandardBusinessDocumentHeader.DocumentIdentification.TypeVersion	Yes		2.1
StandardBusinessDocumentHeader.DocumentIdentification.Type	Yes		Invoice
StandardBusinessDocumentHeader.BusinessScope.Scope (with child nodes)	Yes		Child node Type: Country Child node Identifier: BE
StandardBusinessDocumentHeader.BusinessScope.Scope (with child nodes)	Yes		Child node Type: ProcessType Child node Identifier: Outbound
StandardBusinessDocumentHeader.BusinessScope.Scope (with child nodes)	Yes		Child node Type: CompanyCode Child node Identifier: Supplier's VAT Number
StandardBusinessDocumentHeader.BusinessScope.Scope (with child nodes)	Yes		Child node Type: SenderDocumentId Child node Identifier: A unique document ID. We recommend the ERP document ID.
StandardBusinessDocumentHeader.BusinessScope.Scope (with child nodes)	Yes		Child node Type: SenderSystemId Child node Identifier: The definition of formats, protocols, and integration rules with our system is now incorporated into ERP System Communications through the setup of these configurations on top of a predefined ERP System ID. The value must be defined by you and configured by SOVOS support.
StandardBusinessDocumentHeader.BusinessScope.Scope (with child nodes)	Yes		Child node Type: BusinessCategory Child node Identifier: B2B
StandardBusinessDocumentHeader.BusinessScope.Scope (with child nodes)	Yes		Child node Type: Mapping.InputSchema Child node Identifier: One of: ALL-PEPPOLBISUBL-3.0-INVOICE-1.0 ALL-PEPPOLSCI-1.0-INVOICE-1.0
StandardBusinessDocumentHeader.BusinessScope.Scope BusinessService.BusinessServiceName	Yes		Default
SovosDocument.SovosCanonicalInvoice.Invoice	*Yes (only if document type is ALL-PEPPOLSCI-1.0-INVOICE-1.0)		SCI
SovosDocument.SovosLegalDocument.Base64Document	*Yes (for document types: ALL-PEPPOLBISUBL-3.0-INVOICE-1.0)		Other supported formats

Step 2: Supplier sends SBD to Sovos

The supplier sends a POST request to the /documents endpoint.

The request must include the following request body parameters:

Request sample

curl --location --request POST ' https://api-test.sovos.com/v1/documents' \
--header 'x-correlationId: SET-TO-UNIQUE-VALUE' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw ' {
   "data": "base64_invoice_data",
   " dataEncoding": "base64",
}'

Response sample

{
	"status": 202,
	"message": "Accepted",
	"success": true,
	"timestamp": 1672405631469,
	"data": {
		"documentId": "DOCUMENT-ID",
         "transactionId": "TRANSACTION-ID"
	}
}

Response sample - failure

{
  "success": false,
  "status": 400,
  "message": "Bad Request",
  "timestamp": 1601666692,
  "errors": [
    {
      "subCode": " XSD_SYNTAX_ERROR",
      "message": " An XML comment cannot contain '--', and '-' cannot be the last character. Line 276, position 11. "
    }
  ]
}

Step 3: Sovos validates the document

Sovos performs the necessary semantic, syntactic, and legal checks, and verifies that the XML file matches the official schema. If validation fails, the application returns an error message.

The application generates a response with validation results and status codes:

Step 4: Mapping

Once the XML passes Sovos validation, Sovos converts the document to the appropriate PEPPOL format (BIS3 or PINT). The conversion depends on the recipient's capabilities as published in the PEPPOL SMP.

Step 5: Sovos generates and transmits the document

Sovos generates the document and transmits it to the buyer's PEPPOL Access Point (AP).

Step 6: Buyer's Access Point receives the document

The buyer's access point validates the received document and makes it available to the buyer.

Step 7: Buyer sends the invoice response through PEPPOL

If Sovos issuer wants to receive status updates from the buyer, the issuer must associate the lifecycle to the corresponding endpoint. If the buyer can send invoice response documents, the issuer receives an application response with the corresponding codes:

Step 8: Supplier retrieves the application responses

Attachments configuration

There are three ways you can access your attachments:

• As binary data, so the file is embedded in the Base64-encoded application response.

• As open download links, in which the response contains a public URL to download the file.

• As secure download links, in which you need to use the Indirect Tax API's bearer token to download the attachment.

By default, Sovos configures your attachments as open download links to avoid potential size limitations when retrieving responses. To improve security, you should configure them as secure links. Then, make a GET call to the secure link returned by the Indirect Tax API, and include the API token. Sample request:

curl --location 'https://einvoicing-api.sovos.com/download/api/v1/download/JqYyqliXiJFKhXshnBQZfW3qpfwATVGE5Q73T41JUynNLJD8zHy5VH__9qzL9No-Kia9olSw3_lNX3KmaA9Je89Xx--vk5pQjyKx0iT_4CwPSABD0Yg7uxXZ8SNiliEhFY-4TOX7m1TV5FwwfqntehbGaiGMI2JVYu18VBDiC_0/plain%27 \
--header 'Authorization: Bearer TOKEN'Y

As a response to the initial sending of the document, the client receives a JSON response message with an HTTP status code of 202 (asynchronous transaction). This means that the supplier must retrieve the application responses that become available during the transaction.

To retrieve the application responses, the supplier can use the following API methods:

• GET /notifications/BE

• GET /documents/BE/{documentId}/notifications

GET /notifications/BE

The supplier can send a GET request to the /notifications/BE endpoint to retrieve application responses that match the set search criteria. To make this request, set the following query parameters:

Name	Type	Required	Default	Description
taxId	string	No		Include only notifications related to the specified taxId. This value is related to the CompanyCode in the SBDH. It's important to note that once a request doesn't include this parameter it will return all notifications related to the country and sourceSystemId.
page	integer	No		To specify the page to be returned, enter a value between 1 and 10.
includeAcknowledged	boolean	No	false	Use "true" to include previously acknowledged notifications, within 24 hours of acknowledgment, in the response.
perPage	integer	No		To specify the number of results for the returned page, use a value between 1 and 100.
sourceSystemId	string	Yes		Include only notifications related to documents that originate from the given source system. This value is related to the SenderSystemId in the SBDH. Note: Document routing configuration The system determines document routing based on the following priority: With configured endpoint: Use the ERP System ID value configured on the endpoint Without a configured endpoint: Use the ERP System ID value from the document's SBDH.
processType	string	No		Use "0" to only include notifications related to outbound documents.

Request sample

curl --location --request GET ' https://api-test.sovos.com/v1/notifications/BE?page=1&perPage=2&taxId={taxId}&sourceSystemId={sourceSystemId}&processType=0' \
--header 'x-correlationId: SET-TO-UNIQUE-VALUE' \
--header 'Authorization: Bearer TOKEN'

Response sample

{
 "status": 200,
"message": "Notifications Listed",
"success": true,
"timestamp": 1724063214026,
"data": {
    "pageState": {
        "page": 1,
        "perPage": 10,
        "totalEntries": 2,
        "totalPages": 1
    },
    "notifications": [
        {
            "notificationId": "8e807567-..-e1f9524a76b7",
            "correlationId": "6dc9ef7c-..-3b9c6b413fd9",
            "appPrefix": "CN",
            "metadata": {
                "productId": "be_invoice_outbound_1.0",
                "documentId": "f6bba4ff-..-e2f9524a76b7",
                "erpSystemId": "Outbound_ERPSystemID",
                "processType": "0",
                "taxId": "123456789",
                "sciCloudStatusCode": "214"
            },
            "content": "PD94..jYXRpb25SZXNwb25zZT4=",
            "createdDate": 1724059702440

      }
    ]
  }

GET /documents/BE/{documentId}/notifications

The supplier can send a GET request to the /documents/BE/{documentId}/notifications endpoint to retrieve application responses related to a single document. To make this request, set the following parameter:

Name	Type	Required	Description
documentId	string	Yes	The document ID from step 2

Request sample

curl --location --request GET ' https://api-test.sovos.com/v1/notifications/BE/{documentId}/notifications' \
--header 'x-correlationId: SET-TO-UNIQUE-VALUE' \
--header 'Authorization: Bearer TOKEN'

Response sample

{
	"status": 200,
	"message": " Notifications Listed",
	"success": true,
	"timestamp": 1672405631469,
	"data": {
		"pageState": { … },
		"notifications":[{ … }],
	}
}

Step 9: Supplier marks application response as acknowledged

After retrieving application responses, the supplier must process them and mark them as acknowledged. To do this, send a PUT request to the /notifications/BE endpoint.

To make this request, set the following request body parameters:

Request sample

curl --location --request PUT ' https://api-test.sovos.com/v1/notifications/BE' \
--header 'x-correlationId: SET-TO-UNIQUE-VALUE' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw ' {
   "status": "read",
   " notificationId": "NOTIFICATION-ID",
}'

Response sample

{
	"status": 200,
	"message": "Notifications acknowledged successfully.",
	"success": true,
	"timestamp": 1672405631469 
}

Step 1: Supplier registers company endpoints

To receive invoices through PEPPOL, you must register your company endpoints before Sovos can route inbound documents to your system. Endpoints define your PEPPOL participant identifier and link incoming documents to your ERP system for notification routing.

Register the mandatory 0208 endpoint first. Attempting to register any optional scheme before 0208 exists returns error BELMA-204.

The IDENTIFIER value must be your 10-digit CBE number without the "BE" prefix. For format requirements, see PEPPOL Participant Identifiers.

Step 2: Sovos receives and validates the document

When a buyer sends an invoice through their Access Point, Sovos receives and validates the document through a comprehensive validation pipeline.

When validation fails, the system creates an error transaction with:

• Rule ID (such as PEPPOL-EN16931-R120)

• Error description

• Location in the document where the error occurred

• Specific data that caused the failure

Step 3: Sovos makes the document available to the buyer

After the document passes syntactic and semantic validations, Sovos maps the document from the PEPPOL format (BIS3/PINT) to the buyer's integration format. Buyers can then retrieve the mapped document.

Step 4: Buyer retrieves the application responses

To retrieve the application responses, use the following API endpoint:

GET /notifications/BE

The supplier can send a GET request to the /notifications/BE endpoint to retrieve application responses that match the set search criteria. To make this request, set the following query parameters:

Name	Type	Required	Default	Description
taxId	string	No		Include only notifications related to the specified taxId. This value is related to the CompanyCode in the SBDH. Note: If a request does not include this parameter, it returns all of the notifications related to the country and sourceSystemId.
page	integer	No		To specify the page to be returned, use a value between 1 and 10.
perPage	integer	No		To specify the number of results for the returned page, use a value between 1 and 100.
sourceSystemId	string	Yes		Include only notifications related to documents that originate from the given source system. This value is related to the ERP System ID configured on the company endpoint.
includeAcknowledged	boolean	No	false	Use "true" to include previously acknowledged notifications in the result.
processType	string	No		Use "1" to only include notifications related to inbound documents.

Request sample

curl --location --request GET \
'https://api-test.sovos.com/v1/notifications/BE?page=1&perPage=2&taxId={taxId}&sourceSystemId={sourceSystemId}&processType=0' \
--header ' x-correlationId: developer-guide' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json'

Response sample

{
 "status": 200,
"message": "Notifications Listed",
"success": true,
"timestamp": 1724063214026,
"data": {
    "pageState": {
        "page": 1,
        "perPage": 10,
        "totalEntries": 2,
        "totalPages": 1
    },
    "notifications": [
        {
            "notificationId": "8e807567-..-e1f9524a76b7",
            "correlationId": "6dc9ef7c-..-3b9c6b413fd9",
            "appPrefix": "CN",
            "metadata": {
                "productId": "be_invoice_inbound_1.0",
                "documentId": "f6bba4ff-..-e2f9524a76b7",
                "erpSystemId": "Inbound_ERPSystemID ",
                "processType": "1",
                "taxId": "123456789",
                "sciCloudStatusCode": "215"
            },
            "content": "PD94..jYXRpb25SZXNwb25zZT4=",
            "createdDate": 1724059702440

      }
    ]
  }
}

The content field contains a Base64-encoded UBL ApplicationResponse XML. Decode it to access document download links and processing status.

Decoded ApplicationResponse

<?xml version="1.0" encoding="utf-8"?>
<ApplicationResponse xmlns="urn:oasis:names:specification:ubl:schema:xsd:ApplicationResponse-2">
  <cbc:ID>07f079a8-4a7c-4725-8fc6-8479abaed15c</cbc:ID>
  <cbc:IssueDate>2026-01-26</cbc:IssueDate>
  <cac:ReceiverParty>
    <cbc:EndpointID schemeID="0208">6185204901</cbc:EndpointID>
  </cac:ReceiverParty>
  <cac:DocumentResponse>
    <cac:Response>
      <cbc:ResponseCode listID="SCIResponseCode">AP</cbc:ResponseCode>
    </cac:Response>
    <cac:DocumentReference>
      <cbc:DocumentTypeCode name="ALL-PEPPOLSCI-1.0-INVOICE-1.0">Integration</cbc:DocumentTypeCode>
      <cac:Attachment>
        <cac:ExternalReference>
          <cbc:URI schemeID="Integration">https://xxxx.sovos.com/download/....</cbc:URI>
        </cac:ExternalReference>
      </cac:Attachment>
    </cac:DocumentReference>
    <cac:DocumentReference>
      <cbc:DocumentTypeCode name="ALL-PEPPOLBISUBL-3.0-INVOICE-1.0">Legal</cbc:DocumentTypeCode>
      <cac:Attachment>
        <cac:ExternalReference>
          <cbc:URI schemeID="Legal">https://xxxx.sovos.com/download/....</cbc:URI>
        </cac:ExternalReference>
      </cac:Attachment>
    </cac:DocumentReference>
    <cac:DocumentReference>
      <cbc:DocumentTypeCode>PDF</cbc:DocumentTypeCode>
      <cac:Attachment>
        <cac:ExternalReference>
          <cbc:URI schemeID="PDF">https://xxxx.sovos.com/download/....</cbc:URI>
        </cac:ExternalReference>
      </cac:Attachment>
    </cac:DocumentReference>
  </cac:DocumentResponse>
</ApplicationResponse>

Step 5: Supplier marks application response as acknowledged

After retrieving application responses, the supplier must process them and mark them as acknowledged. Send a PUT request to the /notifications/BE endpoint.

To make this request, set the following request body parameters:

Request sample

curl --location --request PUT 'https://api-test.sovos.com/v1/notifications/BE' \
--header ' x-correlationId: developer-guide' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '[
	"status": "read",
	"notificationId": "NOTIFICATION-ID",
]'

Response sample

{
	"status": 200,
	"message": "Notifications acknowledged successfully.",
	"success": true,
	"timestamp": 1672405631469 
}