X12 transaction code
EDI 845 Price Authorization Acknowledgment/Status (X12 845)
EDI 845 is the X12 Price Authorization Acknowledgment/Status transaction set, used when an authorization is issued or its status changes. A vendor or manufacturer sends the 845 to the distributors, wholesalers, or retailers that resell under its price authorizations.
- Standard
- X12
- Code
- 845
- Partner references
- 2
At a glance
EDI 845 at a glance
What the 845 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 845 Price Authorization Acknowledgment/Status |
|---|---|
| Business record | Price authorization status |
| Who sends it to whom | A vendor or manufacturer sends the 845 to the distributors, wholesalers, or retailers that resell under its price authorizations. |
| When it is sent | A manufacturer awards, renews, amends, or terminates a contract or special pricing agreement and must notify its resellers of the change in authorization status. |
| Match on | Authorization reference, product and effective period |
| Partner references | 2 trading partners in this directory |
| Related documents | X12 844 Product Transfer Account Adjustment, X12 849 Response to Product Transfer Account Adjustment |
Key segments in an EDI 845
The business segments that appear in at least half of the 2 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BPA | Beginning Segment for Price Authorization Acknowledgment/Status | To identify the beginning of a Price Authorization Acknowledgment/Status Transaction Set. | 2 of 2 |
| N1 | Name | To identify a party by type of organization, name, and code. | 2 of 2 |
| CON | Contract Number Detail | To specify contract or reference number and status. | 2 of 2 |
| REF | Reference Identification | To specify identifying information. | 2 of 2 |
| DTM | Date/Time Reference | To specify pertinent dates and times. | 2 of 2 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 2 of 2 |
| N3 | Address Information | To specify the location of the named party. | 2 of 2 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 2 of 2 |
| PAD | Product Adjustment Detail | To specify the product transfer type, and/or line item number. | 2 of 2 |
| LIN | Item Identification | To specify basic item identification data. | 2 of 2 |
Stacksync connects EDI documents such as the X12 845 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 845 mapping and validation
X12 845 Price Authorization Acknowledgment/Status is used when an authorization is issued or its status changes. Preserve authorization reference, product and effective period so the price authorization status in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | price authorization status authorization reference, product and effective period |
|
| Update the receiving system | Processing the price authorization status ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the price authorization status Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 844 Product Transfer Account Adjustment
product-transfer adjustment request: a distributor or reseller requests an account adjustment.
- X12 849 Response to Product Transfer Account Adjustment
adjustment claim response: a product-transfer adjustment is accepted or disputed.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when an authorization is issued or its status changes. Name the operational owner of the price authorization status and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map authorization reference, product and effective period. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic price authorization status data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful price authorization status processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 845 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic price authorization status data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out price authorization status without processing it twice.
Document structure
X12 845 Price Authorization Acknowledgment/Status at the element level
The X12 845 reference contains 22 segment entries and 63 data elements; 39 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 845
2 partners, 2 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 845 Price Authorization Acknowledgment/Status appears in this catalog
The largest groups of classified 845 catalog entries are in building & hardware.
By industry
- building & hardware 2 channels
By network
- Epicor Eclipse 2 channels
FAQ
EDI 845 questions
What is an EDI 845?
EDI 845 is the X12 Price Authorization Acknowledgment/Status transaction set. Trading partners use it when an authorization is issued or its status changes. It carries the data for the price authorization status, and your system matches it on authorization reference, product and effective period.
Who sends an EDI 845 and who receives it?
A vendor or manufacturer sends the 845 to the distributors, wholesalers, or retailers that resell under its price authorizations. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 845 sent?
A manufacturer awards, renews, amends, or terminates a contract or special pricing agreement and must notify its resellers of the change in authorization status. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 845?
Across 2 partner document references listed here, the business segments that appear most often include BPA (Beginning Segment for Price Authorization Acknowledgment/Status), N1 (Name), CON (Contract Number Detail), REF (Reference Identification), DTM (Date/Time Reference), CTT (Transaction Totals). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 845 and EDI 844?
The 845 carries the price authorization status and is used when an authorization is issued or its status changes. The 844 carries the product-transfer adjustment request and is used when a distributor or reseller requests an account adjustment.
What should I map for X12 845?
Start with authorization reference, product and effective period and the target price authorization status. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 845 error handling?
Test an authorization ending before a resale date. Maintain separate eligibility for two customers buying the same product. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 845?
The directory on this page links 2 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
