Trading partner network

Telecom and Media EDI and API integration

Network operators, broadband and wireless providers, broadcasters, studios and streaming platforms. ECOM connects your business with telecom and media companies through EDI, APIs, managed file transfer and portal automation, integrated with your ERP.

Trading partner network

Telecom and media companies we connect with

Through its network, ECOM can connect your business with 3.1M+ trading partners. The 78 telecom and media companies below are highlights, by name and business segment. Companies with an integration guide link to it, and each guide says whether it rests on the company’s own documents or on typical industry practice.

How the exchange works

How telecom and media companies exchange business documents

Network operators buy equipment, devices and installation services from manufacturers and distributors, often with serial numbers tracked from shipment to installation. Service providers also send consolidated service invoices to large business customers.

Common documents with telecom and media companies
DocumentWhat it does in this relationship
EDI 850Purchase Order Orders for network equipment, devices and services.
EDI 855Purchase Order Acknowledgment Confirmation of quantities, prices and delivery dates.
EDI 856Advance Ship Notice Ship notices, often with serial numbers for each device.
EDI 810Invoice Invoices for equipment and services.
EDI 811Consolidated Service Invoice/Statement The consolidated service invoice or statement for telecom and utility services.

What onboarding a new telecom and media partner usually involves

  1. Agree how serial numbers, part numbers and site or project references are carried.
  2. For service invoices, agree the account and charge structure the customer needs to audit the bill.
  3. Test orders, partial shipments and invoice adjustments before replacing portal or spreadsheet exchange.

Integration guides

Telecom and Media integration guides

Detailed guides covering documents, workflows, connectivity and ERP options for specific companies. A selection is shown here; search all 77 telecom and media companies guides in the directory above.

Amazon MGM Studios EDI integration

How EDI and API integration with Amazon MGM Studios typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Amazon MGM Studios.

Read the guide

América Móvil EDI integration

How EDI and API integration with América Móvil typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with América Móvil.

Read the guide

AT&T EDI integration

A guide for suppliers connecting with AT&T, covering order-cycle documents, invoice matching and ERP integration.

Read the guide

Bell Canada EDI integration

How EDI and API integration with Bell Canada typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Bell Canada.

Read the guide

Brightspeed EDI integration

How EDI and API integration with Brightspeed typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Brightspeed.

Read the guide

BT Group EDI integration

How EDI and API integration with BT Group typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with BT Group.

Read the guide

Charter Communications EDI integration

How EDI and API integration with Charter Communications typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Charter Communications.

Read the guide

China Mobile EDI integration

How EDI and API integration with China Mobile typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with China Mobile.

Read the guide

China Telecom EDI integration

How EDI and API integration with China Telecom typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with China Telecom.

Read the guide

China Unicom EDI integration

How EDI and API integration with China Unicom typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with China Unicom.

Read the guide

Comcast EDI integration

How EDI and API integration with Comcast typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Comcast.

Read the guide

Consolidated Communications EDI integration

How EDI and API integration with Consolidated Communications typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Consolidated Communications.

Read the guide

General EDI flow

How EDI with your trading partner typically works

Many trading partners do not publish their EDI or API specifications. This is the general sequence most programs of this kind follow.

  1. 850 Purchase order

    From your trading partner

    The buyer sends the order: items, quantities, prices, ship-to and requested dates.

  2. 855 Order acknowledgment

    From you to your trading partner

    You confirm, change or reject the order, where the partner asks for it.

  3. 856 Advance ship notice

    From you to your trading partner

    You tell the buyer what is on the shipment, with the carton and label details the buyer needs to receive it.

  4. 810 Invoice

    From you to your trading partner

    You bill for what shipped, in the format the buyer's payables system expects.

  5. 997 Functional acknowledgment

    Both directions

    Each side confirms that every file it received was readable. A rejected file is corrected and resent.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Connecting with a telecom and media partner not listed here?

ECOM connects businesses with partners of every size using their published EDI, API or file requirements.