Mexico (Pymnt): Invoice Series
View the Invoice Series for Mexico (Pymnt)
For Mexico CFDI this element is used to provide the series of the invoice. It is an optional element to specify the invoicing series for internal taxpayer control. This attribute accepts a string of characters and helps to distinguish between different types of transactions or locations.
| Name (Path) | Cardinality | Description |
|---|---|---|
Invoice Series (/Statement/UBLExtensions/UBLExtension/ExtensionContent/StatementExtension/InvoiceSeries) | 0..1 | To provide the series of the invoice |
Example
<ubl:Statement>
<cec:UBLExtensions>
<cec:UBLExtension>
<cec:ExtensionContent>
<vrbl:StatementExtension>
<!-- Code omitted for clarity -->
<vrbl:InvoiceSeries>FE</vrbl:InvoiceSeries>
<!-- Code omitted for clarity -->
</vrbl:StatementExtension>
</cec:ExtensionContent>
</cec:UBLExtension>
</cec:UBLExtensions>
<!-- Code omitted for clarity -->
</ubl:Statement>
Routing Details (vrbl:RoutingDetails)
VRBL messages will be used to exchange electronic compliance documents. Three elements are required to correctly route (aka 'process') messages. The elements consists of:
unique sender idunique receiver idunique document type id(provided in the Specification Identifier)
Based on these 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.
| Name (Path) | Cardinality | Description |
|---|---|---|
Routing Details (/Statement/UBLExtensions/UBLExtension/ExtensionContent/StatementExtension/RoutingDetails) | 1..1 | A group of elements providing information regarding the required routing details. |
Elements
This group contains the following elements:
| Name (Path) | Cardinality | Description |
|---|---|---|
Unique Sender ID (Sender) | 1..1 | The unique sender identifier. |
Unique Receiver ID (Receiver) | 1..1 | The unique receiver identifier. |
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 contain also 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>
Updated 9 days ago
