Updated compliance on sbdh and bis identifiers

OpenPEPPOL · Oct 30, 2024 · 2e6c05e · 2e6c05e
1 parent ade3919
commit 2e6c05e
Showing 1 changed file with 10 additions and 9 deletions.
diff --git a/guides/compliance/payload.adoc b/guides/compliance/payload.adoc
@@ -1,18 +1,19 @@
-= Payload compliance to BIS
+= Enveloping compliance
 [horizontal]
 
-== Processing of rules
-* The value of the SBDH element "Sender/Identifier" MUST be equivalent to the value in the sender party's "Party/EndpointID" element and its "schemeID" attribute.
+== Enveloping of BIS message in Peppol Business Message Envelope (SBDH)
+* When a BIS message is enveloped, the value of the SBDH element *Sender/Identifier* SHALL match the *Party/EndpointID* element value of the sender party, including the value of its *schemeID* attribute.
 
-* The value of the SBDH element "Receiver/Identifier" MUST be equivalent to the value in the receiver's party "Party/EndpointID" element and its "schemeID" attribute.
+* When a BIS message is enveloped, the value of the SBDH element *Receiver/Identifier* SHALL match the *Party/EndpointID* element value of the receiver party, including the value of its *schemeID* attribute.
 
-example:
+Example:
 [attributes]
 ====
-    SBDH representation: 
-        <Identifier Authority="iso6523-actorid-upis">0088:7315458756324</Identifier>
-    UBL representation: 
+    BIS message: 
         <cbc:EndpointID schemeID="0088">7315458756324</cbc:EndpointID>
+
+    SBDH envelope: 
+        <Identifier Authority="iso6523-actorid-upis">0088:7315458756324</Identifier>
 ====
 
-See Policy for use of Identifiers
+See Policy for use of Identifiers for more information on how to represent identifiers in envelope and messages.