X12 transaction code
X12 845 Price Authorization Acknowledgment Status
X12 845 Price Authorization Acknowledgment Status: explore its business purpose, mapping identifiers, validation tests and 2 partner references across 2 listed channels.
- Standard
- X12
- Code
- 845
- Partner references
- 2
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
X12 845 questions
What is X12 845 Price Authorization Acknowledgment Status used for?
845 is used when an authorization is issued or its status changes. It carries information for the price authorization status. Match it to your business system using authorization reference, product and effective period.
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.
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.
How does 845 relate to other EDI messages?
X12 844 Product Transfer Account Adjustment; X12 849 Response To Product Transfer Account Adjustment are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 845 and 844?
845 is used when an authorization is issued or its status changes. 844 is used when a distributor or reseller requests an account adjustment. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
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.
