Croatia (Rjtn): Routing Details

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

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 Croatia (Rjtn): Specification ID topic.

Elements

Use the following elements to model this information:

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

Restrictions

For rejected e-invoicing reports, the you must specify urn:vertexinc:vrbl:billing:1#Statement#VRBL-Rejections-HR-1p0.

Example

<ubl:Statement>
    <cec:UBLExtensions>
        <cec:UBLExtension>
            <cec:ExtensionContent>
                <vrbl:StatementExtension>
                    <vrbl:RoutingDetails>
                        <!-- unique sender ID -->
                        <vrbl:Sender>HR82101375789</vrbl:Sender>
                        <!-- unique receiver ID -->
                        <vrbl:Receiver>GENERIC_AS4_HR</vrbl:Receiver>
                    </vrbl:RoutingDetails>
                </vrbl:StatementExtension>
            </cec:ExtensionContent>
        </cec:UBLExtension>
    </cec:UBLExtensions>
    <!-- unique document type id -->
    <cbc:CustomizationID>urn:vertexinc:vrbl:billing:1</cbc:CustomizationID>
    <!-- code omitted for clarity -->
</ubl:Statement>

Updated about 23 hours ago