To start and identify an interchange of zero or more functional groups and interchange-related control segments
Granite City Electric X12 845 Price Authorization Acknowledgment/Status
X12 845 (Price Authorization Acknowledgment/Status) is the EDI transaction exchanged between Granite City Electric (Granite City Electric (via Epicor Eclipse)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 15
- Loops
- 5
- X12 845
- All partners ↗
Transaction context
Where 845 Price Authorization Acknowledgment/Status fits on Granite City Electric (via Epicor Eclipse)
- Granite City Electric channels
- 1 of 1
- Trading partners
- 2
- Channels
- 2
1 of Granite City Electric's 1 channel carries 845
partners across the Stacksync network trade 845
channels network-wide carry 845
Most common alongside 845
On Epicor Eclipse, 845 runs on 2 channels.
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.
When it fires: A manufacturer awards, renews, amends, or terminates a contract or special pricing agreement and must notify its resellers of the change in authorization status.
Common 845 rejection causes
- Contract changes transmitted with insufficient lead time before the effective date, so recipients cannot load new pricing in time and invoice at stale prices.
- Contract numbers or effective date ranges that do not match what the reseller has on file, which later surfaces as chargeback lines denied for expired or invalid contracts.
- Customer eligibility data out of sync between the partners, producing downstream claim denials for customers not covered by the contract.
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 |
Key identifiers in 845
- Transaction Set Purpose Code
- Entity Identifier Code
- Reference Identification Qualifier
- Reference Identification
- Contract Status Code
- Date/Time Qualifier
- Address Information
- Product/Service ID Qualifier
Full segment guideline — 15 segments 5 loops · X12 845 Price Authorization Acknowledgment/Status
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To identify the beginning of a Price Authorization Acknowledgment/Status Transaction Set
N1 Loop Repeat: 10,000
To identify a party by type of organization, name, and code
CON Loop Repeat: 10,000
To specify contract or reference number and status
To specify identifying information
To specify pertinent dates and times
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify the location of the named party
To specify the geographic place of the named party
PAD Loop Repeat: 1
To specify the product transfer type, and/or line item number
LIN Loop Repeat: 1
To specify basic item identification data
CTP Loop Repeat: 25
To specify pricing information
Trading partners
9+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
IN Invoice PA Payment Order Remittance Advice PR Product Transfer Account Adjustment RE Response To Product Transfer Account Adjustment PU Purchase Order PR Product Activity Data PU Purchase Order Acknowledgment SH Ship Notice Manifest PR Product Transfer And Resale Report
No trading partner matches your search.
Browse the full directory
Granite City Electric Granite City Electric (via Epicor Eclipse) EDI 845 FAQ
Common questions about 845 Price Authorization Acknowledgment/Status on the Granite City Electric (via Epicor Eclipse) channel.
What is X12 845 Price Authorization Acknowledgment/Status?
X12 845 (Price Authorization Acknowledgment/Status) is the EDI transaction set used to exchange price authorization acknowledgment/status data. Granite City Electric's Granite City Electric (via Epicor Eclipse) channel requires it from trading partners.
Does Granite City Electric Granite City Electric (via Epicor Eclipse) require 845 for trading partners?
Yes, Granite City Electric (Granite City Electric (via Epicor Eclipse)) supports X12 845 Price Authorization Acknowledgment/Status. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Granite City Electric 845 with Stacksync?
Most companies go live with Granite City Electric 845 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 845 on Granite City Electric (via Epicor Eclipse)?
On Granite City Electric (via Epicor Eclipse), X12 845 is typically exchanged alongside 850 Purchase Order, 810 Invoice, 849 Response To Product Transfer Account Adjustment, 856 Ship Notice Manifest. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Granite City Electric EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
