Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

X12 transaction code

EDI 844 Product Transfer Account Adjustment (X12 844)

EDI 844 is the X12 Product Transfer Account Adjustment transaction set, used when a distributor or reseller requests an account adjustment. A distributor or wholesaler sends the 844 to the manufacturer whose product it resold at contract or special pricing.

Standard
X12
Code
844
Partner references
5

At a glance

EDI 844 at a glance

What the 844 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.

X12 844 Product Transfer Account Adjustment summary
Document X12 844 Product Transfer Account Adjustment
Business record Product-transfer adjustment request
Who sends it to whom A distributor or wholesaler sends the 844 to the manufacturer whose product it resold at contract or special pricing.
When it is sent A wholesaler ships product to a contract-eligible customer at a price below its acquisition cost and claims the difference back from the manufacturer.
Match on Claim reference, product transfer and authorization
Partner references 5 trading partners in this directory
Related documents X12 845 Price Authorization Acknowledgment/Status, X12 849 Response to Product Transfer Account Adjustment, X12 867 Product Transfer and Resale Report

Key segments in an EDI 844

The business segments that appear in at least half of the 5 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
BAA Beginning Segment for Product Transfer Account Adjustment To identify the beginning of a Product Transfer Account Adjustment Transaction Set and further define the type of product account adjustment transaction set and its reference number and date. 5 of 5
N1 Name To identify a party by type of organization, name, and code. 5 of 5
CON Contract Number Detail To specify contract or reference number and status. 5 of 5
PAD Product Adjustment Detail To specify the product transfer type, and/or line item number. 5 of 5
CTT Transaction Totals To transmit a hash total for a specific element in the transaction set. 5 of 5
AMT Monetary Amount To indicate the total monetary amount. 5 of 5
LIN Item Identification To specify basic item identification data. 5 of 5
UIT Unit Detail To specify item unit data. 5 of 5
QTY Quantity To specify quantity information. 5 of 5
REF Reference Identification To specify identifying information. 5 of 5

Stacksync connects EDI documents such as the X12 844 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 844 mapping and validation

X12 844 Product Transfer Account Adjustment is used when a distributor or reseller requests an account adjustment. Preserve claim reference, product transfer and authorization so the product-transfer adjustment request 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 decisionRecord and matching IDsWhat to test
Match the business record product-transfer adjustment request

claim reference, product transfer and authorization

  • Define which combination of claim reference, product transfer and authorization identifies one business record, its lines and any later revision.
Update the receiving system Processing the product-transfer adjustment request

ID assigned by the receiving system and processing result

  • Test two claim lines against the same resale without paying the same adjustment twice.
  • Route an unknown price authorization to review instead of assuming eligibility.
Check the processing result Processing status for the product-transfer adjustment request

Original document reference and matching response

  • Reconcile the product-transfer adjustment request 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.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a distributor or reseller requests an account adjustment. Name the operational owner of the product-transfer adjustment request and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map claim reference, product transfer and authorization. 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 product-transfer adjustment request 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 product-transfer adjustment request processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 844 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic product-transfer adjustment request 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 product-transfer adjustment request without processing it twice.

Document structure

X12 844 Product Transfer Account Adjustment at the element level

The X12 844 reference contains 27 segment entries and 75 data elements; 49 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
27
Data elements
75
Mandatory elements
49
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
BAA 5 3
N1 4 1
N2 2 1
N3 1 1
CON 3 3
LIN 5 2
PID 2 1
QTY 2 1
AMT 2 2
REF 2 1
Key identifiers in 844
  • Transaction Set Purpose Code
  • Transaction Type Code
  • Date
  • Entity Identifier Code
  • Name
  • Address Information
  • Reference Identification Qualifier
  • Reference Identification

Catalog breakdown

Where X12 844 Product Transfer Account Adjustment appears in this catalog

The largest groups of classified 844 catalog entries are in building & hardware and electronics & technology.

By industry

  • building & hardware 4 channels
  • electronics & technology 1 channel

By network

  • Epicor Eclipse 3 channels

FAQ

EDI 844 questions

What is an EDI 844?

EDI 844 is the X12 Product Transfer Account Adjustment transaction set. Trading partners use it when a distributor or reseller requests an account adjustment. It carries the data for the product-transfer adjustment request, and your system matches it on claim reference, product transfer and authorization.

Who sends an EDI 844 and who receives it?

A distributor or wholesaler sends the 844 to the manufacturer whose product it resold at contract or special pricing. Your trading partner agreement confirms the direction and version for your account.

When is an EDI 844 sent?

A wholesaler ships product to a contract-eligible customer at a price below its acquisition cost and claims the difference back from the manufacturer. Your partner guide sets any deadline or schedule for the document.

What are the key segments in an EDI 844?

Across 5 partner document references listed here, the business segments that appear most often include BAA (Beginning Segment for Product Transfer Account Adjustment), N1 (Name), CON (Contract Number Detail), PAD (Product Adjustment Detail), CTT (Transaction Totals), AMT (Monetary Amount). Each partner guide sets which segments and elements your account must send.

What is the difference between EDI 844 and EDI 845?

The 844 carries the product-transfer adjustment request and is used when a distributor or reseller requests an account adjustment. The 845 carries the price authorization status and is used when an authorization is issued or its status changes.

What should I map for X12 844?

Start with claim reference, product transfer and authorization and the target product-transfer adjustment request. 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 844 error handling?

Test two claim lines against the same resale without paying the same adjustment twice. Route an unknown price authorization to review instead of assuming eligibility. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

Which partners list X12 844?

The directory on this page links 5 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.