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
BSN — Beginning Segment for Ship Notice
X12 BSN segment in EDI 856 advance ship notices: shipment ID, ship date, and hierarchical structure entry point.
BSN segment facts
- BSN02 shipment identification is how retailers tie an ASN to a physical trailer and later to an 810 invoice.
- Late or missing 856 BSN segments are a common source of retailer chargebacks and vendor scorecard penalties.
- Inbound 856 webhooks from SignalEDI surface BSN02 and BSN03 as normalized shipmentId and shipDate JSON fields.
What the BSN segment does
BSN opens an 856 ASN. It identifies the shipment, purpose code, and ship date — the anchors retailers use to match trailers and invoices.
Loop: Once per 856
Common transaction sets: 856
Key elements
| Element | Name | Description |
|---|---|---|
| BSN01 | Transaction set purpose | 00 original, 05 replace — same pattern as BEG. |
| BSN02 | Shipment identification | Must be unique per partner; often matches BOL or PRO number. |
| BSN03 | Ship date | CCYYMMDD; late ASNs trigger retailer compliance score hits. |
Example BSN segment
BSN*00*SHIP-4421*20250609~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Related reference
FAQ
Frequently asked questions
Many retailers require alignment between BSN02, REF segments, and the carrier tracking number.
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.”