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 · Ordering

EDI 836 Procurement Notices

The X12 document a buyer uses to notify sellers and other parties of the award, or pending award, of a contract.

Sent by
Buyer, often a government agency
Received by
Sellers and other interested parties
Standard
ANSI ASC X12

What is an EDI 836?

The EDI 836 Procurement Notices is the ANSI X12 transaction set a buyer uses to notify the seller or other interested parties of the award or pending award of a contract. The contract may contain indefinite features, such as the delivery schedule, location or quantity.

Government agencies publish award notices so bidders and the public know who won a contract and on what terms. The 836 gives these notices a structured format that procurement systems and subcontractors can process. Notices can also announce modifications to awards.

How the EDI 836 worksDiagram of the EDI 836 Procurement Notices. Buyer, often a government agency sends it to sellers and other interested parties. It usually follows 843. It is usually followed by 850 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BCO (Beginning Segment for Procurement Notices). 3 optional loops are listed by their first segment.How the EDI 836 worksProcurement Notices: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS843Response to Request forQuotationEDI 836SENDERBuyer, often agovernment agencyRECEIVERSellers and otherinterested parties997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY850Purchase Order997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RQGS … GETransaction set 836ST … SEHEADINGBCOBeginning Segment for Procurement Notices+ 3 optional loops, starting with:N1LMPO1Blue 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 836. Your trading partner's implementation guide adds its own requirements.
How the EDI 836 worksDiagram of the EDI 836 Procurement Notices. Buyer, often a government agency sends it to sellers and other interested parties. It usually follows 843. It is usually followed by 850 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BCO (Beginning Segment for Procurement Notices). 3 optional loops are listed by their first segment.How the EDI 836 worksProcurement Notices: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS843Response to Request for QuotationEDI 836SENDERBuyer, often agovernmentagencyRECEIVERSellers andother interestedparties997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY850Purchase Order997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code RQ (GS … GE)Transaction set 836 (ST … SE)HEADINGBCOBeginning Segment forProcurement Notices+ 3 optional loops, starting with:N1LMPO1Blue 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 836. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 836, 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 836 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

  • Announcing contract awards
  • Notifying pending awards
  • Informing unsuccessful bidders

Where it fits in the document flow

Usually follows 843 Response to Request for Quotation
This document 836 Procurement Notices
Usually followed by 850 Purchase Order997 Functional Acknowledgment

Structure

Mandatory segments in the 836 (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
  • BCO
  • N1
  • LM
  • LQ
  • PO1
  • REF
  • SLN
  • SE

Practical example

The 836 in practice

A government agency completes a competition for office supplies. It sends an 836 notifying the winning supplier of the award, the contract number, ceiling value and period, and publishes the notice to other bidders. The supplier sets up the contract and awaits delivery orders.

Implementation

Implementation considerations for the 836

  • Follow the agency's procurement regulations for notices.
  • Reference the solicitation the award relates to.
  • State indefinite terms clearly, such as ceilings and periods.
  • Link the award to the orders placed under it.

How ECOM helps

Automate the 836 with ECOM

Solution

Procure-to-Pay Automation

Automate purchasing, receiving and supplier invoicing across EDI, portals and documents.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Industry

Industrial Manufacturing

Distributor, OEM customer and supplier integration for industrial manufacturers.

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

Related transactions

Related ordering documents

All 13 ordering documents

Need help with the EDI 836?

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

Request a Demo Contact us