Sovos.com Contact Support

e-invoicing

Compliance Network Implementation Guide

Inbound notifications for Belgium

When Sovos receives an inbound document from the PEPPOL network, Network Services processes it through the inbound pipeline and generates a notification to inform your systems that the document is ready for retrieval. These are the key components:

Component Role
Trade Service Receives inbound documents from the PEPPOL network.
Network Services Processes documents and generates notifications.
Compliance Service/Notifications Stores and distributes notifications through the Notifications API.

Notification delivery methods

Belgium supports two notification delivery methods.

Pull method (polling)
Your system actively retrieves notifications by calling the Compliance Service Notifications API. This method:

  • Routes notifications to the Compliance Service Notification service for client retrieval

  • Generates download URIs for accessing documents

  • Sends optional email notifications to configured recipients

  • Requires your system to poll the API at regular intervals

Push method
Sovos sends notifications to your Trade service endpoint for custom integration. This method:

  • Sends notifications directly to your configured Trade service

  • Supports real-time document processing

  • Requires endpoint setup in your ERP System Communications

Notification fields
Key notification fields:
Field Description
notificationId Unique identifier for this notification
correlationId Links notification to original data
appPrefix Application prefix (CN = Compliance Network)
metadata.productId Belgium inbound product identifier: be_invoice_inbound_1.0
metadata.transactionId ID for document processing
metadata.documentId Unique document identifier
metadata.erpSystemId ERP System ID configured on your company endpoint
metadata.processType Always 1 for inbound documents
metadata.taxId Company tax identifier
metadata.sciCloudStatusCode Document status code. 215 = Document is available to the recipient
metadata.sciResponseCode Overall compliance status. AP = Approved
content Base64-encoded UBL ApplicationResponse XML
createdDate Time stamp when notification was created
ApplicationResponse
The content field has a Base64-encoded UBL ApplicationResponse XML. Decode it to access document download links and processing status.
XML 
<?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>
Attachment types
Type Description
Integration Document in the format set up for your ERP system. The name attribute indicates the format: ALL-PEPPOLSCI-1.0-INVOICE-1.0 = SCI, ALL-PEPPOLBISUBL-3.0-INVOICE-1.0 = PEPPOL BIS3.
Legal Original PEPPOL BIS3 document as received
PDF Human-readable PDF rendering of the document

For setup steps, see Configure network page.

Belgium Compliance Network

Last updated: July 23, 2026