972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Communications

EDI 892 Trading Partner Performance Measurement

The X12 document trading partners use to state desired or achieved service levels for agreed performance objectives.

Sent by
Trading partner (often a retailer or buyer)
Received by
Trading partner (often a supplier)
Standard
ANSI ASC X12

What is an EDI 892?

The EDI 892 Trading Partner Performance Measurement is the ANSI X12 transaction set that lets a trading partner indicate a level of service desired or achieved for specified performance objectives in a trading partner relationship. It supports any business relationship where performance is measured.

Retailers measure suppliers on metrics such as on-time delivery, order fill rate and ASN accuracy. Sharing targets and results in a structured form lets suppliers see their scores, compare them with targets and focus improvement where it matters.

How the EDI 892 worksDiagram of the EDI 892 Trading Partner Performance Measurement. Trading partner (often a retailer or buyer) sends it to trading partner (often a supplier). It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required CRT loop with CRT (Contractor Report Type), DTM (Date/Time Reference) and PMP (Performance Measures). 2 optional loops are listed by their first segment.How the EDI 892 worksTrading Partner Performance Measurement: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 892SENDERTrading partner (oftena retailer or buyer)RECEIVERTrading partner (oftena supplier)997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code WGGS … GETransaction set 892ST … SEHEADINGBGNBeginning Segment+ 1 optional loop, starting with:N1DETAILRequired loop CRT · repeats many timesCRTContractor Report TypeDTMDate/Time ReferencePMPPerformance Measures+ 1 optional loop, starting with:LSCBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 892. Your trading partner's implementation guide adds its own requirements.
How the EDI 892 worksDiagram of the EDI 892 Trading Partner Performance Measurement. Trading partner (often a retailer or buyer) sends it to trading partner (often a supplier). It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and detail: the required CRT loop with CRT (Contractor Report Type), DTM (Date/Time Reference) and PMP (Performance Measures). 2 optional loops are listed by their first segment.How the EDI 892 worksTrading Partner Performance Measurement:who sends it, where it fits and what thestandard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 892SENDERTrading partner(often a retaileror buyer)RECEIVERTrading partner(often asupplier)997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code WG (GS … GE)Transaction set 892 (ST … SE)HEADINGBGNBeginning Segment+ 1 optional loop, starting with:N1DETAILRequired loop CRT · repeatsmany timesCRTContractor Report TypeDTMDate/Time ReferencePMPPerformance Measures+ 1 optional loop, starting with:LSCBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 892. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 892, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 892 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Sharing supplier scorecards
  • Setting performance targets
  • Reporting achieved service levels

Where it fits in the document flow

This document 892 Trading Partner Performance Measurement
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 892 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • N1
  • CRT
  • DTM
  • PMP
  • LSC
  • SE

Practical example

The 892 in practice

A retailer measures its suppliers monthly. It sends each supplier an 892 with the targets and achieved results for on-time delivery, fill rate and advance ship notice accuracy. A supplier sees that its ASN accuracy fell below target and investigates its labeling process.

Implementation

Implementation considerations for the 892

  • Agree metric definitions and calculation methods.
  • Use measurement periods both parties can reproduce.
  • Link results to the transactions behind them.
  • Use the data for improvement, not only for penalties.

How ECOM helps

Automate the 892 with ECOM

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related communications documents

All 16 communications documents

Need help with the EDI 892?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us