1 EDI Source, Inc.

31875 Solon Road

Solon, OH 44139
877.334.1334
Fax: 440.542.9370
www.1EDISource.com

EDI 101

An Introductory Guide to EDI

Introduction

Page | 2

At 1 EDI Source, we have spent more than 20

years developing a deep understanding of EDI
across many industries. In that time, we have also
created a broad offering of methods, tools and
services for implementing EDI more effectively.
We hope you become one of our clients and join
the ranks of the more than 1,000 businesses,
large and small, who have partnered with 1 EDI
Source, many of whom have remained clients for
years.

With this brief guide, we also hope to share

some of our knowledge. The information that
follows is intended to provide a basic overview of
EDI. We will address terminology, benefits of
EDI, uses and methods of implementing EDI,
and more. Our goal is to take away some of the
mystery and complexity that can intimidate
people who are unfamiliar with it.
If you read this and still have questions, just let
us know. We are here to help. After all, when it
comes to EDI, youve come to the right place.

Section 1: What is EDI?

So what exactly is EDI? In this section we take a look at the basic elements of EDI, including
what it is, what it is for, and what it is made of.
A Definition of EDI
EDI is short for Electronic Data Interchange.
Technically, EDI is a set of standards that define
common formats for information in order to be
exchanged electronically between two
organizations doing business together (called
trading partners). By following these standards,
any organization can communicate electronically
with any otherbecause they essentially speak
the same language.
In practice, EDI is the act of exchanging data
through computers. Many businesses and other
organizations use EDI every day in the regular
course of doing business. This is because EDI
makes doing business together a more automated
and efficient process.
Uses for EDI
Before EDI was widely adopted, companies
conducted business with paper purchase orders,
invoices, insurance claims and other documents

were sent back and forth physically using the

mail or couriers. Even with computers and other
more modern technology, many companies today
still operate this way. Information received on
paper, by mail or by fax, must be re-keyed in to
their computer systems for processing, fulfilling
and billing orders.
EDI eliminates much of that manual processing.
In its place is an invisible, electronic flow of the
same information in packets of formatted data.
There are many different types of documents
that may be exchanged electronically with EDI,
across a wide range of industries. These include
invoices, bills of lading, advance shipping
notifications, student transcripts, healthcare
claims, and many, many more.
EDI Standards
In order for two organizations trading partners
to communicate electronically with EDI, they
have to follow the same standards for formatting
the data. This way they (or their computers)

Page | 3

know where to find the particular information

called data elements, which may include dates,
item numbers, order quantities and the like
within the message.

Is EDI New?

While EDI utilizes modern technology, it is actually not

very new. In fact, it was first developed in the 1960s.

services, processes, systems and more. An ANSI

committee, ANSI ASC X12, developed the most
common standard for EDI. The standard is
often referred to simply as ASC X12, or even
just X12.
Outside the U.S., the international EDI standard
is EDIFACT (Electronic Data Interchange for
Administration, Commerce and Transport),
developed under the United Nations.
EDI Formats

EDI standards define which pieces of

information are required and which are optional
for a particular document, and give the rules for
the structure of the document. Just as two houses
can be built to code but look different, two
EDI documents can follow the same standard
and contain different pieces of information. For
example, a clothing manufacturer might choose
to include color and size information, while a
food producer might include an expiration or
sell-by date.
In the United States, organizations traditionally
followed the ANSI standards for EDI document
formats. ANSI the American National
Standards Institute is a private, non-profit
organization that oversees the development of
voluntary consensus standards for products,

EDI transactions represent one or more

individual documents, such as a healthcare
claim. In the ASC X12 standard, each
document type is referenced by a three-digit
number, such as 837 for a healthcare claim, 810
for an invoice, and so on.
Today, EDI can include many formats of these
documents, including XML, CSV, fixedlengtheven spreadsheets. But traditionally,
EDI specifically represented one formatting
structure for data, following the industry
standard.
EDI Data Structure
An EDI file is a binary computer file that
contains data organized into groups and smaller
units. This data represents particular transactions
which replace traditional documents. How this

Page | 4

data is arranged is based on the standards

described above.
Following the ASC X12 standard, each
document represented in an EDI transaction
contains a string of individual data units called
elements (such as dates, reference numbers,
prices and the like), divided into rows that are
called segments. The data elements are
separated by a symbol, known as a separator or
delimiter. There are delimiters to distinguish
data elements, called element separators, and
delimiters to indicate the end of a segment,
called segment terminators.
Each segment of data starts with a segment
identifier which indicates what type of data is
being presented in that particular segment. A
block of segments containing related data that can
repeat is called a loop. The combination of data
that forms a single message or document is called
a transaction set, according to the X12 standard.
Multiple transaction sets can be grouped and
transmitted together in a package, called an
envelope. When the transaction sets are related
in function, the grouping is called a functional
group envelope. Functional groups that come
from the same trading partner are grouped into
an interchange envelope. Finally, a series of
interchanges from a number of different trading
partners form a Transmission.

Communications Protocols
EDI standards are generally independent of
communication methods. That is, EDI can be
transmitted using any number of methodologies,
also called protocols.

Page | 5

One of the more common methods of

communicating or exchanging EDI data is over
the Internet, using a standard called AS2

Value Added Networks (VANs)

Many companies send and receive their EDI transactions

using a VAN. These are third-party service providers who
handle the EDI transmissions on your behalf.

(Applicability Statement 2). AS2 was developed

by EDIINT (EDI over the INTernet) to
ensure the proper level of security for data
transmitted over the Internet. This standard
specifies the use of digital signatures and data
encryption, and confirmations through the use of
receipts.
EDI can also be sent via FTP (with our without
security), email, or even using a modem
(asynchronous and synchronous).

Sample EDI Data

Following is a sample of EDI data with callouts indicating the various elements:

Raw EDI Data

Sender ID

Recipient ID

Delimiters

ISA*00* *00* *12*4405197800 *12*8773341334 *100720*0132*:*00501*000000248*0*P*>

GS*PO*4405197800*8773341334*2010720*0132*248*X*005030VICS
Control Number
ST*850*0001
Element
BEG*00*SA*9399456**20110720
REF*IA*0123415
Segments
DTM*010*20110726
N1*BY*1 EDI SOURCE, INC*92*0101
PO1**48*EA*10.75**UP*00123000124
CTT*1
Quantity Price UPC Code
SE*8*0001
GE*1*248
IEA*1*000000248

Mapped EDI Data (XML Format)

XML Declaration
<?xml version="1.0"?>
<tset name="850">
XML Attribute
<partnercode>8773341334</partnercode>
<ponumber>9399456</ponumber>
Starting
Ending Tag
<podate>07/20/2011</podate>
Tag
<vendornumber>0123415</vendornumber>
<requestedship>07/26/2011</requestedship>
<shiptoname>1 EDI SOURCE, INC.</shiptoname>
<shiptoloc>0101</shiptoloc>
XML Text
<line number="1">
Quantity
<quantity>48</quantity>
<unitofmeasure>EA</unitofmeasure>
Price
<price>10.75</price>
<upc>00123000124</upc>
UPC Code
<lineitemamount>516.00</lineitemamount>
</line>
<totallineitems>1</totallineitems>
<pototalamount>516.00</pototalamount>
XML Element
</tset>

Page | 6

Section 2: Why do EDI?

Often, companies feel as though EDI is a burden placed on them by their trading partners. But
even if EDI is NOT a requirement for your business, it may be a good idea. Thats because
utilizing EDI can provide a number of tangible benefits to your business operationand your
bottom line.
EDI as a Requirement

Cost Savings

Today, your company may have little choice

about whether or not to use EDI. Thats because
using EDI is a requirement of doing business
with many larger organizations, especially big
retailers, manufacturers and government
agencies. As a result, the most significant
advantage for many companies may be the ability
to do business with these larger organizations.

Because EDI allows for information to flow

automatically, with minimal human interaction,
and without paper, there are a number of cost
savings benefits from using it.

These larger organizations have often spent time

and money developing specific requirements for
EDI transmissions, along with many other
aspects of sending and receiving information and
products. They may charge penalties if you do
not comply with these requirements. So it is not
only important to use EDI, but it must be done
well. However, once you are set up to handle
EDI effectively, it can enhance your companys
image as a technically sophisticated one.

Overhead costs can be lowered by reducing

human handling of documents, re-keying of
information and more. You might see lower cost
from printing of paper forms and even the paper
itself. And you may see a reduction in costs from
making errors that can occur when people enter
information incorrectly. Using EDI can also help
companies keep lower inventories, thus reducing
inventory carrying costs.
Those who conduct EDI effectively with retailers
may see a reduction of penalties or charge
backs. Larger retailers with specific
requirements for EDI and related processes will

Page | 7

Integration

Every time we turn around, there seems to be a new hot topic or buzzword
in the industry. EDI is no different, and today it seems everyone is talking
about integration.
What is Integration? In EDI, integration really means DATA integration.

Simply put, data integration means the act of transferring data from its source
directly and seamlessly into your back-end business or accounting software.
How does integration happen? EDI mapping software provides the

mechanism for assigning which data elements from an EDI transaction goes
where in a file format your business system can understand.
What is the benefit of integration? When data is automatically applied to

your business system, you get the greatest advantages of EDI greater
efficiency, greater accuracy and, ultimately, lower costs.

often charge their suppliers (trading partners)

penalties for errors or for not following their
guidelines properly.
Accuracy
Errors are reduced when using EDI because
manual and duplicate data entry is eliminated.
With internal integration, orders received via
EDI can flow through your entire workflow
exactly the way they were prepared because they
were never touched. That means what is
ordered is what is shipped and invoiced. That, in

turn, means fewer costly errors

and better relationships with your
trading partners.
EDI also provides a data trail, so
orders, shipments, claims, loan
applications, inventory status and
other business functions can be
easily tracked.
Efficiency
Sending information via EDI
takes minutes sometimes only
seconds. The information
received can be acted on
immediately, with less manual
work. That means more efficiency
for you and your trading partners.

Integrating EDI with your internal business or

accounting system means the entire workflow can
be more streamlined. Incoming transactions can
automatically convert to actionable items, like
orders or claims, with minimal human intervention.
Time savings can be significant, especially when
dealing with larger organizations providing multiple
transactions in a single EDI transmission.
Supply Chain Visibility
Thanks to EDI, companies may also be able to
share information with their trading partners,

Page | 8

such as product sales data, inventory status of

products or component parts, demand forecasts,
and more. The trading partners, in turn, can share
similar information with their trading partners,
and so on, all the way down the supply chain.

encourages the widespread use of EDI in the

U.S. healthcare system, to improve security and
privacy of personal health data.

The sharing of information in this way is referred

to as supply chain visibility. It allows suppliers
to plan for and respond to swings in demand, so
they can moderate their own inventory levels,
and so they can be prepared for large orders
before they arrive. In this way, EDI can also be
an important element of just-in-time production.

With the use of EDI, business management also

has a source of readily available information to
guide their decisions. It can all be accessed
electronically, rather than manually digging
through old files and folders looking for paper
documents.

Security
The exchange of critical business or personal
information can be more secure using EDI. That
is because many communications protocols for
transferring data include encryption and other
security measures such as digital signatures.
This is one reason why HIPAA, the U.S.
Federal health insurance law of 1996,

Management Information

Electronic data can be more easily compiled,

which then makes it immediately available for
further manipulation and analysis. Data can be
mined, and specific functions, transactions or
trading partners can be assessed, for trends, errors
or redundancies. In short, your historical EDI
data becomes a great source of management
information.

Page | 9

Section 3: What is the process of exchanging EDI data?

Most EDI-based transactions are the same as those you would traditionally handle manually,
with paper documents. The only real difference when handled via EDI is that the information is
all sent and received in electronic form, as a packet of data formatted according to EDI
standards. This section explains the steps in the process.
Overview
The process of doing business using EDI might
generally look like this:

Sender extracts data from a backend business or

accounting system

Sender maps that data into the proper EDI

format to be transmitted

EDI file is translated in preparation for

transmission

Sender transmits the message the outbound

data to the trading partner (the recipient)

Recipient translates the inbound data

translation and communications. Mapping

involves transforming an EDI document into
another format (such as XML, a flat file, a
delimited file, etc.) or vice versa. Translation is
the process of accepting inbound EDI data, or
preparing an outbound file for transmission.
Finally, communications refers to the transmission
of the EDI transaction.
Lets take a look at each of these three key
processes more closely.
Mapping

Inbound translated data is mapped to the

recipients internal business or accounting
system, known as system integration

Prior to sending information via EDI, that

information likely resides on a PC or mainframe,
in some software application. As long as it is
possible to import and export files from that
application, pertinent information can be
extracted and mapped to an EDI transaction.

There are effectively three major processes

involved in the exchange of EDI data: mapping,

The function of mapping outbound data

conceptually involves establishing what

Page | 10

information from the business or accounting

software (the data source) goes where in an EDI
file (the data destination). EDI software allows
you to map EDI data, and then save that map

Once inbound data is received, it must also be

converted to a format your business or
accounting system can understand. Through
system integration, the EDI data can be mapped
to automatically and seamlessly
apply into your internal system.

Communications Protocols

Translation

EDI transmissions can be sent via a number of communications protocols.

Here are some of the most common:
FTP for transferring files over a TCP-based network such as the internet
FTPs FTP secure is FTP with support for encryption protocols TLS or SSL
sFTP SSH-FTP is using FTP with the SSH (Secure Shell) security protocol
AS1 EDIINT standard for sending EDI data encapsulated within MIME email
messages (SMTP)
AS2 EDIINT standard for EDI transmissions over the internet (HTTP) with
S/MIME encryption
AS3 EDIINT standard for using FTP with S/MIME encryption

like a template to use over and over again. This

allows you to quickly convert information into
the proper EDI format for a given trading
partner every time you want to send them an
EDI transaction. You can create multiple data
maps, for particular ASC X12 standards and for
each trading partner who has its own
specifications or requirements.

In the course of sending and

receiving EDI data, software is
involved which runs through a
set of actions to verify and accept
the files. This is called
translation. This is especially
important because EDI
transmissions often come in large
batches containing many
different trading partners and
transactions.

When an inbound transmission

is received by the EDI software,
the file must be broken down (or
parsed) to identify everything it contains, and
what actions should be taken.
EDI translation software will determine what
trading partners are included in a transmission,
what individual trans-actions are included, and
whether any are duplicates. The senders of each
transaction are validated as legitimate trading

Page | 11

partners, and the file structure and individual

data fields of each are validated as proper
according to the EDI standards. If required, a
Functional Acknowledgement (FA) is sent to the
trading partner. Only then is the data mapped
and applied to your internal business system.
A similar process occurs for preparing an
outbound file for transmission, ensuring that the
data fields and file structure are valid. The
translator will prepare the transaction(s) and await
receipt of the appropriate acknowledgements.
Communications
The actual transmission, or sending of EDI data,
requires that a communications connection is
established. In general, there are two types of
connections for sending and receiving EDI data:
indirect or direct.
Indirect connections with trading partners are
done through use of a VAN. Often referred to as
the electronic post office, a VAN is a third-party
service that transmits and stores data in the
electronic mailbox until it is picked up by the
appropriate party. Since the EDI message
contains addressing information, the VAN routes
the message to the mailbox of the recipient.
Unlike using a VAN, a direct connection allows
you to pass the data straight to your trading

partner, over the internet via EDIINT

(commonly AS2), via VPN (Virtual Private
Network) or via FTP, sFTP or FTPs. You can
send EDI directly yourself with installed EDI
software or by using a web-based EDI solution,
or you can outsource with an EDI service
provider. The next section will address each of
these in more detail.

Page | 12

As mentioned previously, any number of

communications protocols may be used for the
transmission, whether it is sent directly or
indirectly. Some companies specify the use of
particular protocols. The file is then sent to
either a mailbox, FTP site or directly to the
recipient to be processed.

Sample from an EDI Implementation Guide

ISA

Interchange Control Header - MANDATORY

ISA01

Authorization Information Qualifier

00

ISA02

Authorization Information ID

Blanks

ISA03

Security Information Qualifier

00

ISA04

Security Information ID

Blanks

ISA05

Interchange Sender Qualifier

01

ISA06

Interchange Sender ID

STOREORP
(STOREORT for test)

EDI Guidelines
Individual trading partners have their sets of
rules and preferences for EDI. Their
specifications for EDI are typically laid out in a
manual called an implementation guide.
Trading partner guidelines are often based on a
given EDI standard, with some differences
additions, exceptions and changes based on

their own preferences. This is akin to local

variations in language. You both speak EDI,
but they speak it with a particular dialect that you
need to understand and accommodate.
Mapping involves not only specifying how data
will be organized according to the EDI standard,
but to the specific requirements of each trading
partner, following their Implementation Guides.

Page | 13

Section 4: What tools or services are available for implementing EDI?

Page | 14

There are a number of different solutions for implementing EDI in your organization. You can
choose to manage it yourself, in house, or contract with a service provider. Here is an overview
of each of the common EDI solutions available to you.
protocols, implementing the translation of
inbound and outbound transactions, and
reconciling transactions by sending and
receiving Functional Acknowledgements.

Installed Software
Installing and running your own EDI software
may be a good option if your company has the
resources to manage and support an internal EDI
operation. This makes sense if your company has
a larger number of trading partners, a larger
volume of transactions each month, and if full
integration with your back-end business and
accounting systems is critical. Running an EDI
operation with installed software requires an
investment in hardware and software, and the
EDI and IT personnel to manage and support it.
In general, EDI software includes three
components: data translation, data mapping and
data management. Some software solutions
handle one, two or all three of these functions.

Data translation involves managing the

trading partners and EDI standards,
supporting different communications

Data mapping properly converts a users

application data into an EDI file format and
vice versa. With outbound mapping, the
data must be properly arranged and
formatted so that it conforms to both the
EDI standards and the trading partners
rules. The mapping tool converts extracted
data into EDI using the assigned, pre-set
maps. The translator can then send it out as
an EDI file. The software can also map
inbound EDI data directly into an
application, into a readable document, into a
specific layout like fixed length or delimited
records, or a combination of these. This
direct mapping can eliminate the need for
data entry, and opens the door to full data
integration.

Determining the most appropriate solution

How do you decide which EDI solution is right for your organization? To
help you with this decision, it is important to project the following:
With how many companies (trading partners) do you anticipate

exchanging EDI?
What types of transactions do these trading partners require?

EDI functionality data translation,

mapping and management tools all
in one powerful system. For more
information, visit:
www.1EDISource.com/EDIHQ.
Outsourced Services

Paying a third party to handle a

particular function is called
partners? Daily? Weekly?
outsourcing. Companies outsource all
For each trading partner, will you need to send transactions to a single
specified location or to individual facilities?
sorts of non-core business functions,
including their customer service,
Answers to these questions can help you and your EDI Consultant to
technical support, IT services and
select the most effective solution.
more. Because running an EDI
operation with installed software
requires an investment in hardware
EDI data management tools are available
and software, and the EDI and IT personnel to
in some EDI software solutions. These tools
manage and support it, outsourcing may be a
allow you to easily search and manipulate
better option.
EDI data for reporting, analysis, tracking
and handling errors and exceptions. Better
EDI service providers host and operate EDI
EDI software solutions will also add alert
software to handle the various aspects of EDI
functions which let you know when errors,
mapping, translation and transmissions. They
exceptions or other specific activities occur.
also provide the services sometimes called
Such alerts make you aware so you can take
managed services or professional services to
appropriate action.
manage the process. This includes the day-to1 EDI Source offers a complete suite of EDI
day monitoring of routine activities, setting up
software solutions. The flagship software product
new trading partners, and ongoing support with
is EDI/HQ, the most advanced EDI software
you and your trading partners. This allows you
solution available, providing all three aspects of
to conduct business via EDI without the
How often do you expect to receive a transaction from these trading

Page | 15

investment in the infrastructure needed to

support it, so you can remain focused on your
core business.
You can outsource your EDI operation with 1
EDI Source. We can handle everything needed
to meet all of your trading partners requirements, including the hardware and security, the
software and the personnel. We also provide
complete Managed File Transfer (MFT) services
for the secure, reliable transfer of documentbased files. For more information, visit:
www.1EDISource.com/outsourcingservices.

However, they tend to be relatively inexpensive

to implement, making web-based solutions a
good option for smaller businesses or those just
getting started with EDI.
EDI WebSource from 1 EDI Source is a
premium web-based EDI solution. It is designed
to work like your email, converting EDI data
into clean, easy-to-read formats. You get support
for unlimited trading partners, integration into
accounting packages, ability to customize, and
more. For more information, visit:
www.1EDISource.com/websource.

Web Solutions

VANs

Companies seeking to meet EDI requirements in

a short time frame with minimal investment may
prefer a web-based EDI solution. There are a
number of web-based EDI solutions available at
various levels of service and functionality. In
general, web-based EDI solutions give you the
ability to manage EDI transactions in a simple
web portal, without a great deal of EDI
experience.

Value Added Networks provide the go-between

in EDI communications, receiving transactions
and routing them to the appropriate recipient.
They also provide other services, including retransmitting documents, providing audit
information, supporting various transmission
methods, and providing telecommunications
support. Because of these additional services,
some companies use VANs in conjunction with
direct connections with trading partners.

Web-based solutions may allow you to export

EDI data to a file that, in turn, can be imported
into your back-end business or accounting
system, but might not support direct system
integration. Web-based systems also typically
require a greater level of manual intervention.

When it comes to VANs, the range of possible

options is large. If this is required, the consultants at 1 EDI Source can recommend and set up
a VAN service for you.

Page | 16

Need more help?

Page | 17

We hope you found this guide useful and

informative. With this information, you can be
better informed as you navigate the EDI
landscape. There are many solutions and
methods, and a great deal of technical jargon that
can serve to confuse and frustrate someone just
being introduced to EDI.
At 1 EDI Source, we aim to remove the mystery
and complexity from EDI. You do not need to
be an expert in order to use and benefit from
EDI in your business. But it does help to have

relationships with expertsand thats where we

come in.
If you still have questions, or want to discuss any
of the concepts or solutions presented here in
more detail, call us. Our EDI Consultants are
here, ready to help and answer your questions.
We can be reached toll-free at 877-334-6950, or
send us an email at sales@1EDISource.com. You
may also find more information about our
products and services online at
www.1EDISource.com.

Glossary of EDI Terms

ANSI (American National Standards Institute): A

voluntarily committee that coordinates standards.
Its subcommittee, the ANSI Accredited Standards
Committee (ANSI ASC) recommends a standard
referred to as ANSI ASC X12 or simply X12.

ASN (Advance Ship Notice or Advance Shipping

Notification): Notification of forthcoming delivery
of product.
AS2 (Internet Applicability Statement 2): Specifies
how to transport data and the means to connect,
deliver, validate, and reply to data in a secure and
reliable manner.
AS2 Software: Software that specifically supports
transmissions using the AS2 protocol, such as AS2
Complete from 1 EDI Source.
Communications Session: The uninterrupted flow
of data from one computer system to the other.
Compliance Checking: A process for ensuring that
the EDI transmissions comply with the established
rules.
CSV File (Comma Separated Values File): File
format in which the data elements are separated
with commas. Also known as a Comma Delimited
File.

Data Element: The smallest unit of EDI

information. A data element could be a code, a
name, a quantity, or any other individual piece of
information.
Data Mapping: The method by which information
in one format is restructured to a different format.
EDIFACT (Electronic Data Interchange For
Administration, Commerce and Transport): A
standard different from X12. It is usually used in
European countries and among the automotive
industry. 12
EDIINT (EDI over the INTernet): The ability to
send EDI data directly over the Internet without
the use of a VAN.
Electronic Mailbox: Term referring to the place
(located within a third partys provider system)
where an EDI transmission is stored for pickup or
delivery.
Fixed Length: Term that describes a data field
with an established number of characters.
Flat File: A computer file that contains
alphanumeric and/or numeric data but not control
characters. It is most often used for transferring
information from one program to another.

Page | 18

Functional Acknowledgement (997): An EDI

transaction set sent from the receiver of the EDI
transmission to the sender. The 997 indicates
receipt and acceptability of data and allows the
receiver to notify the sender if problems have been
encountered within the data.
FTP (File Transfer Protocol): Standard Internet
protocol for transferring files.
FTPs (File Transfer Protocol secure): Using FTP
with support for encryption protocols TLS or SSL
to provide greater security in transferring files.
Map: The pattern in which EDI information is to
be arranged.
ODBC (Open Data Base Connectivity): A
standard software interface for injecting and
extracting data to and from computer systems, such
as business or accounting software applications.
Protocol: Rules that determine the format and
transmission of data between the sender and the
receiver.
Segment: A grouping of one or more data elements
that appears as a line of information within an
individual EDI message.

sFTP (SSH File Transfer Protocol): Using FTP

with the SSH (Secure Shell) security protocol for a
higher level of security in transferring files.
Trading Partner: The business with which you are
exchanging data.
Transaction Set: The electronic version of a
written document.
Translator: A software tool that accepts an EDI
transmission and converts the data into another
format.
GS1-128 (formerly UCC-128): Scannable barcoded label located on the outside of a shipping
carton.
VAN (Value Added Network): A third-party EDI
service provider that supplies a communication link
between companies so that they may exchange
electronic transmissions.
X12: A standard of EDI
XML (Extensible Markup Language): A simple,
very flexible text format originally designed to meet
the needs of electronic publishing.

Page | 19

Common Transaction Sets

Manufacturing/Retail

277

Health Care Claim Status Notification

810

Invoice

834

Benefit Enrollment and Maintenance

850

Purchase Order

835

Healthcare Claim Payment Advice

855

Purchase Order Acknowledgment

837

Healthcare Claim

856

Advance Ship Notice

Freight, Trucking and Logistics

864

Text Message

204

Motor Carrier Shipment Information

Procurement

210

Motor Carrier Freight Invoice

940

Warehouse Shipping Order

211

Motor Carrier Bill of Lading

943

Warehouse Stock Transfer Shipment

Advice

212

Motor Carrier Delivery Trailer Manifest

214

Transportation Carrier Shipment Status

Message

944

Warehouse Stock Transfer Receipt

Advice

945

Warehouse Shipping Advice

947

Warehouse Inventory Adjustment Advice

Other
753

Request for Routing

754

Routing Instructions

Healthcare

811

Consolidated Service Invoice/Statement

270

Eligibility, Coverage or Benefit Inquiry

812

Credit/Debit Adjustment

271

Eligibility, Coverage or Benefit

Information

820

Payment Order/Remittance Advice

997

Functional Acknowledgment

276

Health Care Claim Status Request

Page | 20

Page | 21

Your source for everything EDI.

For more than 20 years, 1 EDI Source has been focused on being the very
best source for superior, cost-effective EDI solutions. Today, we provide a
full array of data exchange, translation and integration solutions. We can
meet the need for all types of businesses in virtually any industry. We work
hard to meet the specific needs of each client, with advanced software,
superior outsourcing services, training and consultation.
Every solution from 1 EDI Source is delivered with unparalleled customer
service and support. You get a dedicated, personal Consultant focused on
the needs of you and your business, and a depth of EDI knowledge and
experience that you simply will not find anywhere else.

877.334.1334
www.1EDISource.com

Copyright 2011, 1 EDI Source, Inc. All rights reserved.