The SOAP Header element contains application-specific information; it must be the first child element of the Envelope element. The required SOAP Body element contains the actual XML document intended for the ultimate endpoint of the message. Immediate child elements of the SOAP Body element may be namespace-qualified. The child element "endpoints" is mandatory since it contains identifiers for the trading partners as the sender respectively receiver of the business document in the payload of the SOAP message. The "properties" element contains important document properties as an unique messageID (/Envelope/Header/properties/identity) generated by the sender and used to check for duplicates received in IBX Connect. The third child element "process" is optional and may contain process dependent properties such as a correlationid and relatedDocid. In case the payload document is of type orderresponse, changeorder, invoice etc. the correlationid is supposed to be the messageID of the underlying purchase order document while the relatedDocid is supposed to hold its ordernumber. None of the ID’s in this element are used for any business logic or mapping of documents within the IBX OnDemand platform though. The existence of the whole process element in outbound SOAP messages from IBX Connect is due to historical reasons and depends on whether inbound documents from customers are containing this. It´s not recommended to base any processing logic on the content of this optional tag. If the SOAP envelope is embedded in a MIME structure including at least one attachment then the child element manifest becomes mandatory.