Skip to main content

Suppliers / Companies

The Suppliers tab manages a directory of seller (AccountingSupplierParty) records used as defaults when the source XML omits seller-side identification or address information. Each record is keyed by an internal company code that the source XML carries (typically a company / KCO identifier from JDE, a Bukrs from SAP, etc.).

The override mechanism is described in the Overview. Default and supplier list are independently overridable.


Default supplier

FieldDescription
Default supplierThe company code applied when the source XML does not carry a recognisable seller identifier. Picked from the supplier directory below; an empty value means "no default" (the source XML is expected to carry every seller field).

When override is enabled in document mode, the default selector appears at the top of the tab; in defaults mode, it sits inside the supplier list view.


Supplier directory

The directory holds one card per company. Each card contains:

Header line

FieldUBLDescription
CodeInternal company code (e.g. 00001, MAIN, the source-system's company key). Used to match against the source XML and as the lookup key for the default selector above.
NameBT-27Legal company name.

Identifiers

FieldUBLDescription
SIRENBT-299-digit French entity identifier.
SIRETBT-2914-digit French establishment identifier.
GLNBT-29GS1 Global Location Number.
NAF (APE)French APE / NAF activity code (00.00X). Carried as additional party identification in the UBL output.
VATBT-31VAT identifier (e.g. FR00000000000).
CapitalBT-33Share capital text (e.g. Capital de 100 000 €).

Address

FieldUBLDescription
StreetBT-35Address line 1.
Street 2BT-36Address line 2 (optional).
Postal codeBT-38Postal code.
CityBT-37City.
CountryBT-40ISO 3166-1 alpha-2 country code (picked from the countries reference list).

The trash icon in the card header removes the supplier; the Add button at the bottom adds a fresh empty card.


How a supplier is resolved

source XML company / KCO code

├─ matches a supplier card? ────► fields filled from the card,
│ source-XML values still win
│ for fields the source provides

└─ no match? ────► fields filled from the
Default supplier (or empty
if no default is set)

The directory is purely a defaults layer: any field the source XML carries explicitly takes precedence over the value stored here.


Tips & best practices

  • Keep one card per legal entity. Even when several internal company codes share a single SIREN, separate cards make it easier to track which establishment (SIRET) and which address each code maps to.
  • The country code drives the default country fallback. When the source omits a postal address country, NomaUBL falls back to this card's country rather than to the global default in the Header tab. Set it to FR for French sellers; do not leave it blank.
  • Capital text appears verbatim. The Capital field is rendered as-is in the UBL output (BT-33), so include the currency mark and any wording the regulatory body expects (e.g. SAS au capital de 50 000 €).
  • Override per template only when the template ships a different seller. A subsidiary issuing invoices on its own SIREN is a legitimate override case; a one-off invoice for the main entity is not.
  • The default selector is the right place to point at the most common seller. When most invoices come from a single legal entity, set it as the default — only the exceptional records need a matching code in the source XML.