EAN / GLN
EAN/GLN is commonly used in Danish e-invoicing to refer to a Global Location Number that identifies a receiving organisation, department, or location. NemHandelsregistret can use EAN/GLN as a participant identifier when looking up supported receiving profiles. It identifies an endpoint or party, and is different from a CVR number; the identifier alone does not prove every invoice profile is accepted.
Why this matters when you invoice
The legal customer and the technical receiving endpoint can be identified differently. Keeping CVR and GLN separate helps route a structured invoice to the intended organisation or department without confusing business identity with delivery capability.
Where it appears
A GLN/EAN can appear in e-invoice recipient information, customer onboarding instructions, public procurement details, or recipient registries such as NemHandelsregistret.
One company, a specific receiving endpoint
A public customer gives a supplier its CVR number and a GLN for the department receiving invoices. The supplier uses CVR for company identity and checks the GLN endpoint's published receiving capability before choosing the structured invoice profile and delivery route.
Common mistakes
- Using CVR and GLN as interchangeable identifiers.
- Assuming a correctly formatted GLN supports every e-invoice profile.
- Ignoring which department or location the GLN identifies.
Check published Danish recipient support
Use the Danish recipient check instead of guessing capability from the identifier.
InvoiceCraftly does not infer recipient capability from an EAN/GLN alone; use the recipient check to inspect published support.
Official references
Sources and terminology reviewed 5 September 2026. Next evidence review: 4 December 2026.
Frequently asked questions
Is EAN/GLN the same as a CVR number?
No. CVR identifies the Danish legal unit, while GLN identifies a party, location or receiving endpoint in relevant workflows.
Does a GLN prove which e-invoice profiles are accepted?
No. Use recipient capability information to see what the endpoint has published as supported.