VRBL messages will be used to exchange electronic compliance documents. Three elements are required to correctly route the messages. The three required elements are:

• unique sender id
• unique receiver id
• unique document type id (provided in the Specification Identifier)

Based on the required elements, the provider invokes actions such as message conversion from the VRBL format to the right target format or vice versa, digital signing of messages, message delivery via APIs to governmental institutions etc.

In VRBL the unique sender ID and receiver ID are provided in the following extension on the document level.

Element

This group contains the following elements:

The unique document type ID, is provided in the Specification identifier: cbc:CustomizationID.

Currently for outbound messages the content of the specification identifier must start with: urn:vertexinc:vrbl:billing:1
For inbound messages the basic value will be extended to also contain the document type and the code identifying the ruleset which applies to the document.

Example

Outbound Payments document indicating the MX Tax Authorities (SAT) as technical receiver of the document.

<ubl:Statement>
    <cec:UBLExtensions>
        <cec:UBLExtension>
            <cec:ExtensionContent>
                <vrbl:StatementExtension>
                    <vrbl:RoutingDetails>
                        <!-- unique sender ID -->
                        <vrbl:Sender>EKU9003173C9</vrbl:Sender>
                        <!-- unique receiver ID -->
                        <vrbl:Receiver>GENERIC_JSON_MX_1p0</vrbl:Receiver>
                    </vrbl:RoutingDetails>
                </vrbl:StatementExtension>
            </cec:ExtensionContent>
        </cec:UBLExtension>
    </cec:UBLExtensions>
    <!-- unique document type id -->
    <cbc:CustomizationID>urn:vertexinc:vrbl:billing:1#Statement#VRBL-Payments-MX-1p0</cbc:CustomizationID>
    <!-- code omitted for clarity -->
</ubl:Statement>