Guides

France (CII(AR)): Routing Details

Read about how to configure the values that govern how a Document is routed.

Suggest Edits

VRBL uses the following elements to determine where a Document is routed:

  • Unique Sender ID
  • Unique Receiver ID
  • Specification IDs

This topic describes how to model the first 2 of these. Specification IDs are explained in the France (CII(AR)): Specification ID topic.

Elements

Use the following:
elements to model this information:

Element (Path)CardinalityDescription
Routing Details (ApplicationResponse/UBLExtensions/UBLExtension/ExtensionContent/ ApplicationResponseExtension/RoutingDetails)1..1A group of elements providing information regarding the required routing details
Unique Sender ID (ApplicationResponse/UBLExtensions/UBLExtension/ExtensionContent/ ApplicationResponseExtension/RoutingDetails/Sender)1..1The unique sender identifier
Unique Receiver ID (ApplicationResponse/UBLExtensions/UBLExtension/ExtensionContent/ ApplicationResponseExtension/RoutingDetails/Receiver)1..1The unique receiver identifier

Example

<ubl:ApplicationResponse>
    <cec:UBLExtensions>
        <cec:UBLExtension>
            <cec:ExtensionContent>
                <vrbl:ApplicationResponseExtension>
                    <vrbl:RoutingDetails>
                        <!-- unique sender ID -->
                        <vrbl:Sender>FR10123456789</vrbl:Sender>
                        <!-- unique receiver ID -->
                        <vrbl:Receiver>GENERIC_PPF_COMPLIANCE_FR_1p0</vrbl:Receiver>
                    </vrbl:RoutingDetails>
                </vrbl:ApplicationResponseExtension>
            </cec:ExtensionContent>
        </cec:UBLExtension>
    </cec:UBLExtensions>
    <!-- unique document type id -->
    <cbc:CustomizationID>urn:vertexinc:vrbl:billing:1#ApplicationResponse#VRBL-Lifecycle-FR-1p0</cbc:CustomizationID>
    <!-- code omitted for clarity -->
</ubl:ApplicationResponse>

Updated about 18 hours ago