Skip to content

Commit

Permalink
Editorial
Browse files Browse the repository at this point in the history
  • Loading branch information
MartinForsberg-Ecru committed Oct 28, 2024
1 parent 13cf4c1 commit 710b0ae
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions guide/compliance/payload.adoc
Original file line number Diff line number Diff line change
@@ -1,19 +1,20 @@
= Enveloping compliance to BIS
= Enveloping compliance
[horizontal]

== Enveloping of BIS message in Peppol Business Message Envelope (SBDH)
* When a BIS message is enveloped, the value of the SBDH element *Sender/Identifier* MUST match the *Party/EndpointID* element value of the sender party, including the value of its *schemeID* attribute
* 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.

* When a BIS message is enveloped, the value of the SBDH element *Receiver/Identifier* MUST match the *Party/EndpointID* element value of the receiver party, including the value of 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:
[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 for more information how to represent identifiers in envelope and messages
See Policy for use of Identifiers for more information on how to represent identifiers in envelope and messages.

0 comments on commit 710b0ae

Please sign in to comment.