...

When you start development or wish to validate your logic, you can exchange information with "sparing sparring partners" : the fakeCustomer and fakeSupplier. In an upcoming version of this guide, this section will elaborate on this service, that is not completely finalized yet.

...

• develop your own mock or use SOAPUI as a sparing sparring partner, using your favorite integrator's wsdl, and the information in this document.
• when the development is sufficiently advanced, test the service by sending documents to yourself through simpl.ePRIOR. You can also use the Mercurius portal to generate incoming documents - however this does not guarantee that you will see all possible document patterns.
• When this is OK, test the service in combination with other public sector entities
• eventually, organize tests involving private sector entities.

...

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
         <soapenv:Header>
            <wsse:Security soap:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
               <wsu:Timestamp wsu:Id="Timestamp-HvumButHp993jGDym7t89Q22" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
                  <wsu:Created>2018-10-03T10:07:55Z</wsu:Created>
                  <wsu:Expires>2018-10-03T10:12:55Z</wsu:Expires>
               </wsu:Timestamp>
	      <!—More elements on security and signature:-->
            </wsse:Security>          </soapenv:Header>
   <soapenv:Body>
      <v1:submitDocumentResponse>
         <!—When successful ackIndicator is true-->
         <v1:ackIndicator>true</v1:ackIndicator>
		<!—When an exception occurred ackIndicator is false-->
		<v1:ackIndicator>false</v1:ackIndicator>
		-->
      </v1:submitDocumentResponse>
   </soapenv:Body>
</soapenv:Envelope>

SOAP with attachments

In order to keep the size of xml documents small enough for middleware processing, Simpl.ePrior is using SOAP with attachments when exchanging UBL documents.

...

------=_Part_20_1065051393.1568991070704
Content-Type: text/xml; charset=UTF-8
Content-ID: <rootpart@babelway.net>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Header/>
 <soap:Body>
  <v1:retrieveDocumentResponse xmlns:v1="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
   <receivedDate xmlns="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">2019-09-20</receivedDate>
   <document xmlns="http://fsb.belgium.be/einvoicing/simpleprior/v1_00">
    <inv:Invoice xmlns:inv="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
    <cbc:UBLVersionID>2.1</cbc:UBLVersionID>
...
    <cac:AdditionalDocumentReference>
     <cbc:ID>file1</cbc:ID>
     <cac:Attachment>
      <cbc:EmbeddedDocumentBinaryObject filename="file1.txt" mimeCode="application/octet-stream"/>
     </cac:Attachment>
    </cac:AdditionalDocumentReference>
    <cac:AdditionalDocumentReference>
     <cbc:ID>file2</cbc:ID>
     <cac:Attachment>
      <cbc:EmbeddedDocumentBinaryObject filename="file2.log" mimeCode="application/octet-stream"/>
     </cac:Attachment>
    </cac:AdditionalDocumentReference>
    <cac:AdditionalDocumentReference>
     <cbc:ID>file3</cbc:ID>
     <cac:Attachment>
      <cbc:EmbeddedDocumentBinaryObject filename="file3.txt" mimeCode="application/octet-stream"/>
     </cac:Attachment>
    </cac:AdditionalDocumentReference>
...
   </inv:Invoice>
  </document>
      </v1:retrieveDocumentResponse>
   </soap:Body>
</soap:Envelope>
------=_Part_20_1065051393.1568991070704
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <file1>
Content-Disposition: attachment; filename=file1.txt

file1
------=_Part_20_1065051393.1568991070704
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <file2>
Content-Disposition: attachment; filename=file2.log

file2
------=_Part_20_1065051393.1568991070704
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <file3>
Content-Disposition: attachment; filename=file3.txt

file3
------=_Part_20_1065051393.1568991070704—

SOAP Fault

Simpl.ePrior uses standard SOAP fault, without defining substructures.

...

Please note that this list can be augmented with the error thrown by the FSB or the integrator layer.

Endpoint URL

The endpoint URLs are defined by the integrator. Once you start your on-boarding process those 'll be communicated by the integration team plus the necessary security/authorization artifacts ( certificate, credentials, ... ).

...

See "defined Document formats" for detailed format specifications.

Sequence of simpl.ePRIOR operations to apply

...

the following 2 table summarize the key information about the supported document formats.

Format specifications

...

References

Sample Code

This example is provided without any guarantee or support. It's only to help you and show you how to generate code based on the WSDL definition.

...