Telecom and Media integration
AT&T supplier EDI integration
A guide for suppliers connecting with AT&T, covering order-cycle documents, invoice matching and ERP integration.
At a glance
AT&T integration, in three pictures
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific AT&T program or a customer relationship.
Talk to an EDI/API Expert about AT&T
Tell us which documents you exchange with AT&T, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with AT&T.
- Review of AT&T's requirements with you, once you have them
- EDI and API integration with your ERP and warehouse systems
- Monitoring and managed service after go-live, if you want it
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
How AT&T integration fits your systems
- ConfirmConfirm your AT&T program, role and the documents it requires.
- MapMap each document to your ERP fields and business rules.
- ConnectConfigure the connection and security the program needs.
- TestTest against the applicable specifications and acknowledgments.
- Go liveGo live with monitoring, alerts and exception handling.
Overview
Understanding AT&T integration
Who this is for: Equipment, device, accessory and materials suppliers selling to AT&T.
Scope: This guide describes typical practice for this kind of trading relationship; AT&T's own program details are confirmed during onboarding.
AT&T buys network equipment, devices, accessories and materials from many suppliers and exchanges order-cycle documents with them electronically.
Invoice accuracy is a recurring theme. When invoices do not match, payment can be delayed.
AT&T provides its specifications to suppliers directly. Suppliers should confirm the document set and versions for their relationship, and note that some catalogs list separate legacy and current AT&T identifiers.
As general practice for suppliers to large telecom companies, purchase orders arrive by EDI, suppliers acknowledge them, send ship notices before deliveries arrive and invoice against the original purchase order. Invoices that match the order and ship notice line by line are the easiest to pay, so integration usually starts with the ERP's order and invoice data. Specifications and identifiers can differ between business units, so confirm the current set with AT&T before mapping.
Workflows
Typical AT&T business workflows
General guidance: typical flows in this industry, not AT&T's published process.
AT&T order cycle
- 1Receive 850 purchase order
- 2Send 855 acknowledgment
- 3Send 856 ship notice
- 4Send 810 invoice
- 5Review 824 application advice
Documents and APIs
AT&T documents by program
General guidance. We could not verify AT&T's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not AT&T's confirmed requirements. Confirm the list, versions and programs with AT&T.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| 850 | Purchase Order | From AT&T | Not stated | General guidance | AT&T orders products from suppliers. |
| 855 | Purchase Order Acknowledgment | To AT&T | Not stated | General guidance | The supplier confirms the order. |
| 856 | Advance Ship Notice | To AT&T | Not stated | General guidance | Describes each shipment. |
| 810 | Invoice | To AT&T | Not stated | General guidance | Bills AT&T and must align with the order and shipment. |
| 824 | Application Advice | From AT&T | Not stated | General guidance | Reports errors in submitted documents. |
| 754 | Routing Instructions | From AT&T | Not stated | General guidance | Provides shipment routing where used. |
Connectivity
How companies connect
EDI per AT&T specifications
Suppliers exchange documents according to specifications provided by AT&T.
General guidance
Current and legacy identifiers
AT&T has not published this in a source we could verify.
General guidance
Challenges
Common integration challenges
Three-way matching
Invoices must align with the purchase order and ship notice to avoid payment delays.
Acting on application advice
Errors reported on 824 documents need prompt correction.
Obtaining official specifications
Specifications come from AT&T directly, so onboarding depends on AT&T contacts.
Automation options for AT&T suppliers
Four ways to automate. One foundation.
ECOM helps you automate them, meet AT&T's labeling and ship notice requirements, and see what needs action. AT&T sets its program's rules; ECOM confirms which options fit yours.
-
Fully Automated EDI/API
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/API -
WebEDI
Receive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDI -
SmartConvert
Convert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvert -
WebConnect
Automate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnect
PRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Compliance and actionable visibility
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
Connect AT&T documents to your ERP
ECOM integrates AT&T order-cycle documents with your ERP so invoices reference the original order exactly and errors reach the right team quickly.
Telecom and Media
See how ECOM supports telecom supply chains.
ProductPRISM-SCV
Monitor invoice matches and application advice for AT&T orders.
General EDI flow
How EDI with AT&T typically works
The documents, their order and the timing are AT&T's to set; this is the general sequence most programs of this kind follow.
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.
Next step
Get help with your AT&T program
Each request goes to an ECOM EDI specialist with AT&T's name attached, so the reply starts from your program.
-
Review AT&T's requirements
Send us AT&T's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements review -
Connect AT&T to your ERP
Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integration -
Testing and certification
Build, test and certify each AT&T document, then go live with monitoring from the first file.
Plan testing and certification -
Shipping labels and ASNs
Labels and ship notices that match AT&T's rules, to help avoid receiving problems and compliance deductions.
Review shipping compliance
AT&T integration FAQs
Which EDI documents does AT&T use with suppliers?
The 850, 855, 856, 810, 824 and 754 are commonly used in this industry, but AT&T has not published its list in a source we could verify, so confirm it with AT&T.
Why do AT&T invoices get rejected?
Common causes include purchase order references that do not match exactly and invoices that do not align with the order and ship notice.
Where do suppliers get AT&T specifications?
Directly from AT&T, through its supplier onboarding contacts. Request the current specification for each document before you build maps.
Is ECOM an AT&T partner?
This page is an integration guide and does not indicate a partnership with AT&T. ECOM builds integrations to published requirements.
Sources and accuracy
This guide summarizes publicly available information as of October 2026. AT&T sets its own requirements and can change them at any time; your AT&T implementation guide, supplier portal or account contact is the authoritative source for your program.
- Stacksync, AT&T EDI Third-party source
AT&T is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
More telecom and media integration guides
Vodafone EDI
How EDI and API integration with Vodafone typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Vodafone.
Vyve Broadband EDI
How EDI, file and API integration with Vyve Broadband typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Vyve Broadband.
Warner Bros. Discovery EDI
How EDI and API integration with Warner Bros. Discovery typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Warner Bros. Discovery.
Warner Music Group EDI
How EDI and API integration with Warner Music Group typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Warner Music Group.
Windstream EDI
How EDI and API integration with Windstream typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Windstream.
YouTube EDI
How EDI and API integration with YouTube typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with YouTube.
Request AT&T integration assistance
Tell us about your AT&T program, documents and ERP. We will outline the connection, mapping and testing plan.