X12 transaction code
X12 845 Price Authorization Acknowledgment Status
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 845
- Trading partners
- 2
Specification summary
X12 845 Price Authorization Acknowledgment Status at the element level
The X12 845 specification defines 22 segments carrying 63 data elements, 39 of which are mandatory.
- Segments
- 22
- Data elements
- 63
- Mandatory elements
- 39
| Segment | Elements | Mandatory |
|---|---|---|
| BPA | 1 | 1 |
| N1 | 4 | 1 |
| CON | 3 | 3 |
| REF | 2 | 1 |
| DTM | 2 | 1 |
| N3 | 2 | 1 |
| LIN | 7 | 2 |
| CTT | 1 | 1 |
- Transaction Set Purpose Code
- Entity Identifier Code
- Reference Identification Qualifier
- Reference Identification
- Contract Status Code
- Date/Time Qualifier
- Address Information
- Product/Service ID Qualifier
Trading partners that support X12 845
2 partners, 2 channels. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 845 Price Authorization Acknowledgment Status
845 is used most heavily in building & hardware.
The 845 transmits the status of, or changes to, outstanding price authorizations: contract or reference numbers, authorized prices and modifications, effective dates, eligible parties, and terms. In manufacturer-distributor relationships, especially pharmaceutical distribution, it keeps the reseller's contract records aligned with the manufacturer's so that contract sales price correctly. Partners require it because misaligned contract data surfaces later as denied chargeback claims and pricing disputes. Sent by a vendor or manufacturer to the distributors, wholesalers, or retailers that resell under its price authorizations. A manufacturer awards, renews, amends, or terminates a contract or special pricing agreement and must notify its resellers of the change in authorization status.
By industry
- building & hardware 2 channels
By network
- Epicor Eclipse 2 channels
FAQ
X12 845 questions
What is X12 845 Price Authorization Acknowledgment Status?
X12 845 (Price Authorization Acknowledgment Status) is an EDI transaction set defined by ANSI ASC X12 for exchanging price authorization acknowledgment status between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 2 Stacksync trading partners support this code across 2 channels.
Which trading partners use X12 845?
2 Stacksync partners accept X12 845: Granite City Electric, J.H. Larson Company. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 845 with my ERP?
Stacksync handles the full X12 845 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
