--- title: "EDI 845 Price Authorization Status | X12 | Stacksync" description: "EDI 845 is the X12 Price Authorization Acknowledgment/Status, used when an authorization is issued or its status changes." canonical: https://www.stacksync.com/edi/x12/845-price-authorization-acknowledgment-status last_modified: 2026-09-29 --- X12 transaction code # EDI 845 Price Authorization Acknowledgment/Status (X12 845) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md 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 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) 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. **X12 845 Price Authorization Acknowledgment/Status summary** | | | | --- | --- | | 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](https://www.stacksync.com/edi/x12/844-product-transfer-account-adjustment), [X12 849 Response to Product Transfer Account Adjustment](https://www.stacksync.com/edi/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](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/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. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **price authorization status** authorization reference, product and effective period | Define which combination of authorization reference, product and effective period identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the price authorization status** ID assigned by the receiving system and processing result | Test an authorization ending before a resale date. Maintain separate eligibility for two customers buying the same product. | | Check the processing result | **Processing status for the price authorization status** Original document reference and matching response | Reconcile the price authorization status with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### 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](https://www.stacksync.com/edi/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](https://www.stacksync.com/edi/x12/849-response-to-product-transfer-account-adjustment) **adjustment claim response:** a product-transfer adjustment is accepted or disputed. ### Implementation steps 1. #### 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. 2. #### 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. 3. #### 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. 4. #### 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. ### Related documents and resources - [X12 844 Product Transfer Account Adjustment](https://www.stacksync.com/edi/x12/844-product-transfer-account-adjustment) - [X12 849 Response to Product Transfer Account Adjustment](https://www.stacksync.com/edi/x12/849-response-to-product-transfer-account-adjustment) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) 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 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 845 2 partners, 2 channels. Choose a channel to inspect its listed document reference and implementation context. - [Granite City Electric](https://www.stacksync.com/edi/granite-city-el) [Granite City Electric (via Epicor Eclipse)](https://www.stacksync.com/edi/granite-city-el/granite-city-electric-via-epicor-eclipse/x12-845-price-authorization-acknowledgment-status) - [J.H. Larson Company](https://www.stacksync.com/edi/jh-larson-electrical) [J.H. Larson Company (via Epicor Eclipse)](https://www.stacksync.com/edi/jh-larson-electrical/j-h-larson-company-via-epicor-eclipse/x12-845-price-authorization-acknowledgment-status) 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 Partner entries with the most listed channels - [Granite City Electric](https://www.stacksync.com/edi/granite-city-el) - [J.H. Larson Company](https://www.stacksync.com/edi/jh-larson-electrical) 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)