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

EDI 170 Revenue Receipts Statement

The X12 document used to report daily ticket sales for each show within a film's contract week.

Sent by
Exhibitor (cinema operator)
Received by
Film distributor
Standard
ANSI ASC X12

What is an EDI 170?

The EDI 170 Revenue Receipts Statement is the ANSI X12 transaction set used to report daily ticket sales information for each show within a contract week. A contract week normally runs from Friday through Thursday and is the period over which a film's terms apply.

Distributors are paid a share of box office revenue, so they need accurate attendance and receipts per show and day. The statement lets them calculate film rental under the terms confirmed in the 159 and track a film's performance across cinemas.

How the EDI 170 worksDiagram of the EDI 170 Revenue Receipts Statement. Exhibitor (cinema operator) sends it to film distributor. It usually follows 159. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: N1 (Party Identification) and the required THE loop with THE (Screen Theater Identification) and the required LX loop with LX (Transaction Set Line Number), REF (Reference Information) and the required DTM loop with DTM (Date/Time Reference) and BOX (Box Office Detail). 0 optional loops are listed by their first segment.How the EDI 170 worksRevenue Receipts Statement: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS159Motion Picture BookingConfirmationEDI 170SENDERExhibitor (cinemaoperator)RECEIVERFilm distributor997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code ERGS … GETransaction set 170ST … SEHEADINGN1Party IdentificationRequired loop THE · repeats up to 9,999THEScreen Theater IdentificationRequired loop LX · repeats up to 10LXTransaction Set Line NumberREFReference InformationRequired loop DTM · repeats up to 7DTMDate/Time ReferenceBOXBox Office DetailBlue 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 170. Your trading partner's implementation guide adds its own requirements.
How the EDI 170 worksDiagram of the EDI 170 Revenue Receipts Statement. Exhibitor (cinema operator) sends it to film distributor. It usually follows 159. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: N1 (Party Identification) and the required THE loop with THE (Screen Theater Identification) and the required LX loop with LX (Transaction Set Line Number), REF (Reference Information) and the required DTM loop with DTM (Date/Time Reference) and BOX (Box Office Detail). 0 optional loops are listed by their first segment.How the EDI 170 worksRevenue Receipts Statement: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS159Motion Picture Booking ConfirmationEDI 170SENDERExhibitor(cinemaoperator)RECEIVERFilm distributor997 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 ER (GS … GE)Transaction set 170 (ST … SE)HEADINGN1Party Identification+ required THE (THE)Blue 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 170. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting daily box office receipts
  • Reporting attendance by show
  • Supporting weekly film rental settlement

Where it fits in the document flow

Usually follows 159 Motion Picture Booking Confirmation
This document 170 Revenue Receipts Statement
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 170 (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
  • N1
  • THE
  • LX
  • REF
  • DTM
  • BOX
  • SE

Practical example

The 170 in practice

A cinema chain reports ticket sales for a new release to its distributor. Each day it sends a 170 with tickets sold and receipts for each show at each location. At the end of the contract week the distributor calculates its share and invoices the chain.

Implementation

Implementation considerations for the 170

  • Report by show, day and location as the distributor requires.
  • Align reporting weeks with contract weeks.
  • Reconcile reported receipts with box office systems.
  • Protect commercially sensitive box office data.

How ECOM helps

Automate the 170 with ECOM

Industry

Telecom and Media

Equipment supply chains, service billing and partner data exchange for telecom and media companies.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

EDI Integration

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

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

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 170?

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

Request a Demo Contact us