How do I add a GLN, VAT number or customer code to a party?
Add a Party identifier
Give a Party the codes other systems and partners use for it, such as a GLN or an ERP customer code, and narrow a code to one Integration, state, country or currency if needed.
About 4 min
At the end of this guide your Party will carry a code that Supply Lens can match on incoming Documents, or send to a system that needs it.
Before you start
- The Party must exist. See Add a Party.
- Know which identifier type you need and its exact value. Ask: which system will send this code, and which system needs to receive it? See Party identifier types.
- Codes a partner uses for you, such as the supplier number a retailer has given you, go on your organisation party (the one with the building icon).
Steps
- Open Settings → Reference data → Parties.
- Click the Edit icon on the Party.
- Scroll to the Identifiers section at the bottom of the screen.
- Click + to open the Add party identifier window.
- Choose the Type from the drop-down list. It only shows types that apply to your organisation's Integrations.
- Enter the Value exactly as the other system sends or expects it.
- If needed, narrow when the identifier applies in the Advanced section (see below). Otherwise leave each setting at Any.
- Click SAVE IDENTIFIER.
| Integration state | Live or Test. Apply the identifier only when the Integration is in that state, for example a test GLN used during certification. |
|---|---|
| Country | Apply only on Documents for this country. |
| Currency | Apply only on Documents in this currency. |
| Integration Type | Apply only on Integrations of this type. Picked from a searchable list showing each type's logo and name. |
| Integration | Apply only on this one Integration. |
Check it worked
- The identifier is listed in the Party's Identifiers section, and the Identifiers count on the Parties list goes up by one. Supply Lens confirms the change was saved.
- On the next Document that names this code, the Party shows a green tick.
If something goes wrong
- The Party still isn't recognised. Check the value character for character, and check any Advanced setting matches the Document: a code scoped to the Test state won't apply on a live Integration.
- The wrong code is sent to a system. Another identifier of the same type is winning. Scope the one you want to that Integration. See How Supply Lens matches codes.
- The type you need isn't listed. The list only shows types for your Integrations. Ask Support.