Standards & Information: Updated July 2000
EDS and RTF-Formatted Files

Below are latest versions of The Electronic Commerce Committee Standards (v3.1), in EDS and RTF formats.

EDS files are in the Edifecs format used to create the specifications. In order to open, view and print these files you will need to download Edifecs Specviewer v3.5.

The v3.1 810 has been revised to correct several IT1 elements. The TECC release specification date for the 810 is September 12, 2000.

If you continue to have difficulties, please contact CAB's Director of EDI Scott Lowe at (212) 508-1223 or via E-mail.

Please note that because of the size of these files, they may take some time to download.

850: Purchase Order: Original Master Orders (Network Generated)
Deal information (guarantee, guarantee guidelines, demographic labels, etc.) as well as unit information comprise the original order. Total Units, dollars and demographic audience estimates must tie back to the Deal guarantee information. This will provide the agency with a complete snapshot of the Deal which they will then be able to audit against future changes. Serialization is optional for v3.1 of the TECC standards. A serial number is an identifier for each individual unit and must be maintained throughout the life of the Deal. This number will be the key to communicating specific changes, brand allocations, copy instructions and invoice information for each unit.

• RTF file
• EDS file

855: Purchase Order Acknowledgement
The Purchase Order Acknowledgement document is transacted from the buyer to the seller to either accept or reject the 850 Purchase Order originated by the network. This transaction should be generated after the information of the 850 is reviewed and agreed upon. The document includes pertinent information such as the Deal Number, sender created date and time and a segment for a detailed message if the 850 is being rejected.

• RTF file
• EDS file

860: Purchase Order Change Request
The Purchase Order Change Request document is used by both the seller and the buyer. After the transfer of the original Deal, this document is used for schedule changes, additions to the Deal and changes to elements of a schedule such as pricing, impressions information, schedule changes, etc. The agency uses this document to transact brand allocations and copy instructions. These are the only transactions an agency will send; all other changes will be electronically generated by the network. All information included in this transaction is based upon individual serialized units. The structure of this transaction set is very similar to the structure of the 850 Purchase Order. Most of the information is identical in terms of segment usage and elements within those segments.

• RTF file
• EDS file

865: Purchase Order Change Acknowledgement
The Purchase Order Change Acknowledgement document is transacted from the buyer to the seller if the network has generated the change and from seller to buyer in the case of brand allocation or copy instructions. It is important to note that on brand allocations, the network must accept the entire brand allocation into its system in order to run brand conflict checking. This transaction is generated after the information of the 865 is reviewed and agreed upon. The document includes pertinent information such as the Deal Number, sender create date and time and a segment for a detailed message is the 865 is rejected by either party.

• RTF file
• EDS file

810: Invoice
The 810 Invoice transaction set is used to transmit invoice information from the network to the agency.  Like all of the other transaction sets, it is organized by Trading Partner, Master Order Number and serial number.

• RTF file
• EDS file