Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 segment reference
N1 — Name
Understand the X12 N1 segment: ship-to, bill-to, and vendor party IDs with qualifier codes — critical for 850, 856, and 810 routing.
N1 segment facts
- N104 identification codes must match retailer DC enrollment — padded GLN or store IDs are a top 850 rejection cause.
- N101 entity roles differ by document: ST on 856 asserts where cartons arrive; BT on 810 drives remittance routing.
- SignalEDI partner profiles enforce required N1 loops so outbound documents fail validation before partner mailboxes.
What the N1 segment does
N1 identifies trading parties in a transaction — ship-to, bill-to, buyer, seller, remit-to. N101 entity identifier and N104 ID codes must match partner enrollment or documents reject before line items are evaluated.
Loop: N1 loop (often with N3/N4 address segments)
Key elements
| Element | Name | Description |
|---|---|---|
| N101 | Entity identifier code | ST=ship to, BT=bill to, VN=vendor, BY=buyer — partner guides specify required roles. |
| N102 | Name | Human-readable party name; may be omitted when N104 carries the authoritative ID. |
| N103 | Identification code qualifier | 92=assigned by buyer, 91=assigned by seller, ZZ=mutually defined. |
| N104 | Identification code | DC number, store ID, or GLN — must match retailer master data. |
Example N1 segment
N1*ST*RetailMart DC 01*92*0001234567890~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common N1 errors
- Ship-to ID not enrolled with retailer
- Wrong N101 role for the partner's 856 spec
- ZZ qualifier without mutual agreement
Related reference
FAQ
Frequently asked questions
Many retailers validate ship-to and vendor IDs before line items — a bad N104 fails fast with no partial acceptance.
Yes. A single 850 may include ST, BT, and VN loops; each must use the qualifiers your partner profile expects.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”