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
N3 — Address Information
X12 N3 segment reference: street address lines that pair with N1 party and N4 geographic segments for ship-to and remit-to routing.
N3 segment facts
- N3 only has meaning inside an N1 loop — it describes the street address of the party the preceding N1 identified.
- N3/N4 address blocks must match retailer master data when the program validates literal addresses instead of coded IDs.
- SignalEDI normalizes N1/N3/N4 blocks into structured address objects on inbound documents for downstream systems.
What the N3 segment does
N3 carries the street address lines for a party identified by the preceding N1 segment. It pairs with N4 (city/state/postal) to complete ship-to, bill-to, and remit-to addresses.
Loop: N1 loop (after N1, before N4)
Key elements
| Element | Name | Description |
|---|---|---|
| N301 | Address line 1 | Primary street address for the party in the current N1 loop. |
| N302 | Address line 2 | Optional suite, dock, or secondary address line. |
Example N3 segment
N3*100 Distribution Way*Dock 7~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common N3 errors
- N3 present without a preceding N1 party loop
- Address exceeding partner max length or charset rules
- Ship-to address not matching retailer master data for the N1 ID
Related reference
FAQ
Frequently asked questions
Many programs validate party IDs (N1/N104) rather than free-text addresses, but N3/N4 are required when partners need a literal ship-to or remit-to address.
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 on core plans, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
Supports HIPAA complianceBAA path documentedSecure API + webhooksNo per-document fees on core plans
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with handling that supports HIPAA compliance 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.”