EDIFACT NAD segment: name and address.

The NAD segment identifies a party to the transaction and optionally provides their address. The qualifier identifies the party's role: BY=buyer, SU=supplier, DP=delivery party (ship-to), IV=invoice party (bill-to), ST=ship-to (alternate), SE=selling party, CA=carrier. Element 2 carries the party's GLN. Elements 4-8 carry the address (name, street, city, state, postcode, country).

Tag: NAD
Full name: Name and address
Part of the message: Parties
Data elements: 9

A NAD segment, explained

Hover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.

NAD+BY+9311000000123::9++EXAMPLE RETAIL PTY LTD+100 SAMPLE ST+SYDNEY+NSW+2000+AU'
NADName and address
Buyer: EXAMPLE RETAIL PTY LTD, GLN 9311000000123.
NAD
Name and address
BY
Buyer (party role)
9
GS1 (party id agency)
1 Party role BYBuyer
2.1 Party ID: ID 9311000000123
2.3 Party ID: Agency 9GS1
4 Party name EXAMPLE RETAIL PTY LTD
5 Street 100 SAMPLE ST
6 City SYDNEY
7 State NSW
8 Postcode 2000
9 Country AU
```
{
  "parties": {
    "buyer": {
      "gln": "9311000000123",
      "name": "EXAMPLE RETAIL PTY LTD",
      "address": {
        "street": "100 SAMPLE ST",
        "city": "SYDNEY",
        "state": "NSW",
        "postalCode": "2000",
        "countryCode": "AU"
      }
    }
  }
}
```
Example shape. In production the field names and structure follow your own API contract.

NAD structure

Elements are separated by + and their parts by :. Positions match the explainer, so 2.3 is the third part of the second element.

Position	Element	Parts
1	Party role	1.1 Code
2	Party ID	2.1 ID, 2.2 Code list, 2.3 Agency
3	Name and address (unstructured)	Single value
4	Party name	Single value
5	Street	Single value
6	City	Single value
7	State	Single value
8	Postcode	Single value
9	Country	Single value

Party role (1.1)

Code	Meaning
`BY`	Buyer
`SU`	Supplier
`DP`	Delivery party
`IV`	Invoicee
`ST`	Ship to
`SN`	Store
`SF`	Ship from
`UC`	Ultimate consignee
`CA`	Carrier
`CN`	Consignee
`II`	Invoice issuer
`PE`	Payee
`PR`	Payer
`OB`	Ordered by
`MF`	Manufacturer
`FW`	Freight forwarder

Party ID: Agency (2.3)

Code	Meaning
`9`	GS1
`16`	DUNS
`91`	Assigned by supplier
`92`	Assigned by buyer

Common EANCOM and UN/EDIFACT values. Your trading partner's implementation guide is the final word on which codes they send.

Questions

NAD segment FAQ

Have a real message with NAD in it? The explainer breaks down every segment and runs in your browser.

Explain my message

What is the NAD segment in EDIFACT?

NAD is the Name and Address segment. The NAD segment identifies a party to the transaction and optionally provides their address. The qualifier identifies the party's role: BY=buyer, SU=supplier, DP=delivery party (ship-to), IV=invoice party (bill-to), ST=ship-to (alternate), SE=selling party, CA=carrier. Element 2 carries the party's GLN. Elements 4-8 carry the address (name, street, city, state, postcode, country).

What are the common NAD party role codes?

BY means buyer; SU means supplier; DP means delivery party; IV means invoicee; ST means ship to; SN means store; SF means ship from; UC means ultimate consignee.

Where does NAD appear in an EDIFACT message?

NAD belongs to the parties part of a message, alongside LOC, CTA, COM.

How do I read a NAD segment in my own message?

Paste the message into the free CleanEDI explainer. It breaks every NAD segment into its elements, translates the codes and shows the JSON and XML your system would receive. Nothing you paste leaves your browser.

1	Party role	`BY`Buyer
2.1	Party ID: ID	`9311000000123`
2.3	Party ID: Agency	`9`GS1
4	Party name	`EXAMPLE RETAIL PTY LTD`
5	Street	`100 SAMPLE ST`
6	City	`SYDNEY`
7	State	`NSW`
8	Postcode	`2000`
9	Country	`AU`