Appendix 6: UBL mapping and entry points

This section explains the rules for populating tags in the UBL 2.1 Extended (BT/BG) files with the contents of the tables generated when creating data snapshots: ESINVH, ESINVD, ESINVTRDPTY, ESINVHVAT, ESINVHSFI, and ESINVNOT.

References

  • Table dictionary, especially the SINVOICE* tables for original transactions and the SEINV* data snapshot tables
  • UBLBG0000 representation, which defines the Sage X3 data structure and the source to use when generating the XML file, which relies on classes starting with UBLBG
  • UBLBG* classes
  • The list of XSD files making up the UBL, all starting with UBL21-*
  • The France standard mapping rule in UBL21 output

Detailed mapping by node

This first table listed below shows the detailed mapping between the UBL 2.1 Extended (BT/BG) tags for France and the X3 table fields: ESINVH, ESINVD, ESINVTRDPTY, ESINVHVAT, ESINVHSFI, and ESINVNOT.

This table summarizes the primary matches for a standard electronic invoice (sales invoice, SIH/GESSIH), while considering the most common use cases.

For each UBL tag, there is:

  • BT/BG: The identifier of the UBL tag
  • Description: Business meaning
  • X3 table/field: Data source in X3
  • Loading rule: Logical or specific condition
  • Comments: Important remarks, special cases, or transcoding schema

Tables

The following information is provided for reference only. The information and applicable rules can change according to the decisions of other standard-setting organizations.

Each table below opens in a new window.

Invoice header (ESINVH)

Business partners: Seller/Buyer/Payee/Invoice (ESINVTRDPTY)

VAT: breakdown, exemption (ESINVHVAT)

Invoice lines (ESINVD)

Document discounts/charges (ESINVHSFI)

Totals (ESINVH)

Payment (ESINVH)

Notes (ESINVNOT)

Detailed mapping by BT

Each UBL tag (BT/BG) is associated with its XML Xpath and X3 source table and field, and with the main rules and constraints. This table summarizes the correspondences for the French electronic invoice, integrating the Chorus Pro extensions and EN16931 requirements.

Detailed mapping table

Entry points

Entry points are provided so that developers can modify the content of tables used for data snapshots.

Refer to the online help for specifics regarding the EINVOUTGEN script and entry points.

E-invoicing outbound data snapshot and entry points for Customer BP invoices

The workflow outlines the steps in the outbound process and the related entry points for Customer BP invoices.

The workflow outlines the steps in the outbound process and the related entry points for Customer BP invoices.

  1. Lines in LOAD_CLASS_SIL_ESID
  2. VAT in LOAD_CLASS_SIH_ESIHV
  3. Discounts and charges > lines in LOAD_CLASS_SIL_SVFSFI
  4. Third parties in LOAD_CLASS_ESI3P_* (SELLER, BUYER, OR PAYER)
  5. Notes in CREATE_SIH_ESIN

E-invoicing outbound data snapshot and entry points for Sales invoice or credit memo

This workflow

This workflow outlines the steps in the outbound process and the related entry points for sales invoices and credit memos.

  1. Lines in LOAD_CLASS_SID_ESID
  2. VAT in LOAD_CLASS_SVV_ESIHV
  3. Discounts and charges in LOAD_CLASS_SIH_SVFSFI