Identifiers in master data
An administrator enters the identifiers of the company, customers and vendors so documents reach the right parties.
Purpose
Electronic documents identify the sender and receiver by registration number (kennitala) or GLN. The system reads the identifiers from master data when a document is sent and uses them to find the right customer or vendor when a document is received. If an identifier is missing or in the wrong field, sending stops, or a received document isn't linked to the right party.
Prerequisites
- eDoc Setup exists.
- You know which field holds the customer and vendor registration numbers.
Permissions
The user needs the EDOCS permission set and permission to edit company information, customers and vendors.
Steps
Company registration number
- Open Company Information.
- Fill in Registration No. Hyphens are removed when the value is used.
If the field is empty, document processing stops with an error saying that Registration No. must have a value.
- If the company uses a GLN, fill in GLN in Company Information. It's used as the company's identifier in EDI documents, and in TS236 documents when Use GLN as default mode of Identification is selected in the setup.
SSN fields
The system finds customers and vendors by registration number by searching the field that Customer SSN Field and Vendor SSN Field point to.
Warning
The default value is 1, which is the No. field. That only works if customer and vendor numbers are registration numbers. If the registration number is stored in another field, for example Registration No. (field 25), enter that field number in the setup.
-
Open eDoc Setup.
-
Enter the number of the field that holds the registration number in Customer SSN Field and Vendor SSN Field.

-
Make sure the registration number is stored without a hyphen in that field. The search looks for exactly 10 characters without a hyphen.
Customers
On the customer card, on the eDocs FastTab:
| Field | Effect |
|---|---|
| GLN (standard field on the card) | Received documents with a GLN find the customer first by GLN on the card and then by GLN on a ship-to address. |
| Use GLN as Default Identifier | In TS236 documents, the customer's GLN is used as the receiver identifier if it exists, otherwise the registration number. |
| Fallback E-Mail | Only supported when the delivery site's Unimaze Transfer Mode is JSON Metadata (REST), see JSON metadata. Required there. If it's empty, the standard email address is used. |
| X400 PostBox | The customer's X400 postbox in EDI documents. |
The GLN for individual ship-to addresses is entered in the customer settings.
Vendors
On the vendor card, on the eDocs FastTab:
| Field | Effect |
|---|---|
| EAN ID | The vendor's GLN. Received documents with a GLN find the vendor by this field, not by the standard GLN field. |
| Fallback E-Mail | Only supported when the delivery site's Unimaze Transfer Mode is JSON Metadata (REST), see JSON metadata. If it's empty, the standard email address is used. |
| X400 PostBox | The vendor's X400 postbox in EDI documents. |
Locations
The GLN of locations is entered in location EAN IDs.
Example: Dæmi ehf. stores registration numbers in Registration No. on customers and vendors. The administrator sets both SSN fields to 25, fills in the company's registration number and GLN, and enters the EAN ID on the vendor Prófun hf. An invoice from Prófun hf. then finds the vendor whether it's identified by registration number or GLN.
Verify
- Verify recipients. The errors below show missing identifiers.
- Receive a test document and check that the right vendor is chosen in the worksheet.
| Message | What to do |
|---|---|
| Customer identifier is missing (no valid GLN or kennitala found). | Fill in the customer's GLN or registration number and check Customer SSN Field. |
| Customer identifier is duplicated and cannot be verified uniquely. | Two customers have the same GLN or registration number. Correct or block one of them. |
| Receiver party (%1) is missing identifier (GLN or Legal Entity Company ID). | Fill in the customer's GLN or registration number. |
| Receiver party (%1) is missing Fallback E-Mail (required as fallback delivery address by Unimaze in the case of JSON metadata invoices). | Fill in the customer's Fallback E-Mail or email address. |