Skip to content

X12 transaction code

X12 895 Delivery Return Acknowledgment Or Adjustment

X12 895 Delivery Return Acknowledgment Or Adjustment: explore its business purpose, mapping identifiers, validation tests and 1 partner references across 1 listed channels.

Standard
X12
Code
895
Partner references
1

Implementation guide

X12 895 mapping and validation

X12 895 Delivery Return Acknowledgment Or Adjustment is used when delivery or return quantities are acknowledged or adjusted. Preserve original delivery, response and affected item so the delivery or return response 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 delivery or return response

original delivery, response and affected item

  • Define which combination of original delivery, response and affected item identifies one business record, its lines and any later revision.
Update the receiving system Processing the delivery or return response

ID assigned by the receiving system and processing result

  • Apply an adjustment to the correct base-record line.
  • Test multiple responses without applying the same quantity correction twice.
Check the processing result Processing status for the delivery or return response

Original document reference and matching response

  • Reconcile the delivery or return response 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 delivery or return quantities are acknowledged or adjusted. Name the operational owner of the delivery or return response and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map original delivery, response and affected item. 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 delivery or return response 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 delivery or return response processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 895 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic delivery or return response 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 delivery or return response without processing it twice.

Document structure

X12 895 Delivery Return Acknowledgment Or Adjustment at the element level

The X12 895 reference contains 15 segment entries and 65 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
15
Data elements
65
Mandatory elements
40
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
G87 6 5
LS 1 1
G89 7 1
G72 7 2
LE 1 1
G23 11 2
G85 1 1
Key identifiers in 895
  • Initiator Code
  • Credit/Debit Flag Code
  • Supplier's Delivery/Return Number
  • Integrity Check Value
  • Adjustment Number
  • Loop Identifier Code
  • Direct Store Delivery Sequence Number
  • Allowance or Charge Code

Find your trading partner for X12 895

1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 895 Delivery Return Acknowledgment Or Adjustment appears in this catalog

The largest groups of classified 895 catalog entries are in grocery & food.

By industry

  • grocery & food 1 channel
Partner entries with the most listed channels

FAQ

X12 895 questions

What is X12 895 Delivery Return Acknowledgment Or Adjustment used for?

895 is used when delivery or return quantities are acknowledged or adjusted. It carries information for the delivery or return response. Match it to your business system using original delivery, response and affected item.

Which partners list X12 895?

The directory on this page links 1 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 895?

Start with original delivery, response and affected item and the target delivery or return response. 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 895 error handling?

Apply an adjustment to the correct base-record line. Test multiple responses without applying the same quantity correction twice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 895 relate to other EDI messages?

X12 894 Delivery Return Base Record is a related document 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 895 and 894?

895 is used when delivery or return quantities are acknowledged or adjusted. 894 is used when delivery or return details establish a reconciliation baseline. 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.