Skip to main content

Scheme IDs

Every party identifier in a UBL document carries a schemeID attribute that names the registry the value belongs to (ISO 6523 organisation identifiers, EAS electronic-address scheme, etc.). The Scheme IDs tab pins which scheme code NomaUBL writes for each kind of identifier.

The override mechanism is described in the Overview.

Scheme IDs​

FieldUBLTypical valueRegistry
SIRENBT-29 / BT-300002French SIREN registry (INSEE).
SIRETBT-290009French SIRET registry (INSEE).
GLNBT-290088GS1 Global Location Number.
EndpointBT-34 / BT-490225EAS — electronic address scheme used by the French PPF.
Delivery locationBT-71(varies)Identifier scheme of the delivery location.

Each field is populated from the scheme-ids reference list (see Configuration → Reference Lists). Pick the value that matches the registry the underlying identifier belongs to.

Buyer electronic address by transaction type​

The buyer electronic address (BT-49) can be set independently of the seller's (BT-34) and can differ by transaction type — B2B, B2G, B2C and B2B international. For each type you pick the scheme and where the value comes from: a source tag the template already maps (for example the buyer's contact email) plus a fallback constant used when that tag is empty.

This lets B2C and international invoices — which have no SIRET-based electronic address — carry an email address (scheme EM) instead, while domestic B2B / B2G invoices keep their usual endpoint routing. Types you don't list keep the default scheme (0225) and the current endpoint value. The Scheme IDs list carries an Email (EM) entry for this.

Tips & best practices​

  • Use 0225 for the BT-49 endpoint in France. The Plateforme Agréée recognises 0225 as the EAS code for the French e-invoicing endpoint registry. Other values are rejected by the addressing check (REJ_ADR).
  • 0002 (SIREN) and 0009 (SIRET) are not interchangeable. They reference different registries (entity vs establishment). Pick the one that matches the identifier length and source — never carry a 14-digit SIRET under 0002.
  • Override per template only when a customer requires a deviating scheme. The defaults file is correct for almost every deployment; document overrides are reserved for genuine exceptions (e.g. a single template emitting GLN-keyed identifiers).
  • Add missing scheme codes to the reference list, not here. If a target value does not appear in a dropdown, edit the scheme-ids reference list in Configuration → Reference Lists — that change propagates to every dropdown on this tab.