The GLN (Global Location Number) is a globally unique identification number that identifies companies, locations, or organizational units. It is assigned by GS1 and serves as the basis for automated data exchange between business partners. Typical use cases are:
Company identification: Unique identifier for invoicing, deliveries, or legal documents.
Location identification: Headquarters, branches, warehouses, production facilities, or delivery addresses can be precisely identified.
EDI processes (Electronic Data Interchange): Especially in B2B environments, the GLN is a standard for the automated exchange of orders, delivery notes, or invoices.
Tip
A GLN consists of 13 digits and is structured according to international standards.
Basic Principle for Using GLN
The GLN (Global Location Number) is used to uniquely identify addresses (companies, branches, warehouses). You should print it when your business partner requires it or when it is necessary for automated processing.
Typical Use Cases for GLN in B2B
Purchase orders:
Your own GLN → shows the supplier who is ordering.
Delivery address GLN → when goods are going to a warehouse or branch.
Invoices / Credit notes:
GLN of the invoice address (common for central accounting departments, shared service centers)
Sometimes mandatory when your partner uses EDI or the company has adopted GLNs as a standard
Delivery notes:
GLN of the delivery address so that goods receipt can correctly assign the delivery
Framework agreements & EDI:
Many large trading companies (e.g., in the food and retail sector) insist on GLNs because their systems cannot otherwise process data automatically.
GLN in Xentral – Usage and Variables
Xentral supports the management and printing of GLNs on documents such as invoices, sales orders, purchase orders, delivery notes, and credit notes. This allows business partners to uniquely identify documents.
Overview of GLN-Relevant Variables in Xentral: GLN in Address and Document Data
A GLN can be maintained in the address data of customers and suppliers. It is then automatically used in documents.
Important variables are:
{GLN} – GLN from the general address data: GLN of the document (general master data)
{ADRESSE_GLN} – GLN from the address master data
{LIEFERGLN} – GLN from the delivery address
{ADRESSE_RECHNUNG_GLN} – GLN from the alternative invoice address
Note
If a GLN is entered in the master data, it can be used automatically in documents.
Where do I enter what?
Address → Master data: ADRESSE_GLN (customer/supplier general)
Address → Delivery address: LIEFERGLN
Address → Alternative invoice address: ADRESSE_RECHNUNG_GLN
Document (optional): GLN (if project-specific or different per document)
Practical Implementation in Xentral
Document type | Recommended GLN variables |
Purchase order | {GLN} (own GLN), {LIEFERGLN} (delivery address) |
Invoice | {ADRESSE_GLN} (customer/invoice recipient), {ADRESSE_RECHNUNG_GLN} (alternative invoice address), {LIEFERGLN} (optional delivery address) |
Delivery note | {LIEFERGLN} (delivery address) |
Sales order/Quote | Usually not required unless the partner explicitly requests it |
Credit note | Same as invoice – often {ADRESSE_GLN} |
GLN Variables in Documents
The GLN can be integrated in various contexts. Examples:
Invoice
Note
{IF}{ADRESSE_GLN}{THEN}GLN: {ADRESSE_GLN}{ELSE}{ENDIF}
{IF}{LIEFERGLN}{THEN}Delivery GLN: {LIEFERGLN}{ELSE}{ENDIF}
Purchase order
Note
Our GLN: {GLN}
Your delivery address (GLN): {LIEFERGLN}
Delivery note
Note
{IF}{LIEFERGLN}{THEN}GLN of delivery address: {LIEFERGLN}{ELSE}{ENDIF}
Text Templates with GLN
The GLN can be integrated in Xentral text templates just like any other variable, allowing it to be displayed automatically on documents.
Example: Invoice text with GLN
Note
{ANSCHREIBEN},
thank you for your order.
{IF}{TRANSAKTIONSNUMMER}{THEN}Transaction number: {TRANSAKTIONSNUMMER}{ELSE}{ENDIF}
{IF}{LIEFERSCHEIN}{THEN}Delivery note: {LIEFERSCHEIN}{ELSE}{ENDIF}
{IF}{ADRESSE_GLN}{THEN}GLN (invoice recipient): {ADRESSE_GLN}{ELSE}{ENDIF}
{IF}{LIEFERGLN}{THEN}GLN (delivery address): {LIEFERGLN}{ELSE}{ENDIF}
Example: Purchase order with GLN
Note
Dear Sir or Madam,
we hereby order:
Our GLN: {GLN}
Our delivery address (GLN): {LIEFERGLN}
Please deliver by: {GEWUENSCHTESLIEFERDATUM}
Practical Tips for GLN
Tip
Master data maintenance: Ensure that all relevant GLNs are stored in the customer and supplier data so that they appear automatically on documents.
Use IF conditions: With {IF}{GLN}{THEN}…{ELSE}{ENDIF} you can prevent empty GLN fields from being visible.
GLN per address: Each invoice or delivery address can have its own GLN. This ensures that even complex supply chains are correctly mapped.
B2B scenarios: Especially in business with large companies and in an international context, the GLN is a mandatory component for invoices, delivery notes, or purchase orders.
FAQ - GLN
How do I ensure that my GLN is printed on all documents?
How do I ensure that my GLN is printed on all documents?
Answer: Add the variables {GLN}, {LIEFERGLN}, and {ADRESSE_RECHNUNG_GLN} to the respective text templates. Use IF conditions to hide empty values.
Can I maintain multiple GLNs for different locations?
Can I maintain multiple GLNs for different locations?
Answer: Yes, each address (invoice, delivery, alternative) has its own GLN field. This allows different locations to be uniquely identified.
When do I not need to print a GLN?
When do I not need to print a GLN?
Answer: In B2C business, the GLN is not relevant. Private customers do not have a GLN, so the field will remain empty. If your business partner does not use or require a GLN, the standard address details are usually sufficient. For internal purposes (e.g., document copies), printing it is not mandatory.