Tag Archive for: ASC X12

This post was updated to reflect current trends and information.


Understanding the Basics of  EDI ANSI ASC X12

This article describes the EDI ANSI ASC X12 standard (American National Standards Institute Accredited Standards Committee X12).

This overview provides full information on the EDI ANSI X12 standards, including general terms (Interchange, functional group, document), description of the main components of an EDI document (segments, elements), and how an EDI document is structured.

What is meant by EDI?

EDI Electronic Data Interchange is the process of electronically exchanging business documents (in a pre-defined format) between trading partners.

The EDI ANSI ASC X12 standard has different versions (related to development standards) – 4010, 5010, 5020

In EDI X12, each document has a three-digit number identifier. For example, an Invoice is 810, an Inventory Inquiry/Advice is 846,  an Advance Ship Notice  is 856, etc. more detailed list of EDI X12 documents with its identifier you can find here: Complete List of EDI X12 Codes


ANSI (American National Standards Institute) – is a non-profit organization that oversees the development of voluntary consensus standards for products, services, processes, systems, and personnel in the United States. EDI is handled by the Accredited Standards Committee X12 (ASC X12), it develops and maintains the X12 Electronic data interchange (EDI).

EDIFACT (Electronic Data Interchange for Administration, Commerce, and Transport.) EDIFACT standard is used mainly in Europe.


EDI Terminologies:

Interchange (or Envelop)

Interchange envelope is a structured data set to deliver electronic transactions to a receiving. Interchange can include a package of groups of documents but also may contain only one group with one document.

The Interchange structure

EDI document structure

Interchange begins with the ISA segment and ends with the IEA segment (ISA / IEA Envelope).

EDI X12 – Functional Group

A functional group is a group of one or more similar transaction sets. The beginning of the functional group is determined by the GS segment and the end by the GE segment.

How does an EDI document look (example)

ISA*00*          *00*          *ZZ*A1STORES    *12*5142645505     *190510*0728*|*00403*100000013*0*P*}

GS*PO*A1STORES*5142645505*20190510*0728*1013*X*004030

ST*850*1013

BEG*00*SA*2332233**20190510

REF*IA*66910

PER*BD*Contact Name*TE*123-456-7890

FOB*DF

DTM*010*20190517

DTM*001*20190525

TD5*****Carrier Routing*******CG

N1*ST*Towner Square Schooms*92*006

N3*Williston Towner Square*2100 11th St SW

N4*Williston*ND*58701

PO1*1*4*EA*4.15**UP*066810348563*IT*WACT750SP16-BLK

CTP**RTL*7.99

PID*F*08***Nike Boy Short Black sz M

PO1*2*6*EA*5.00**UP*066810349983*IT*WACT170SP16-AMP

CTP**RTL*7.99

PID*F*08*** Reebok Boy Short Abstract Print sz M

PO1*3*4*EA*5.25**UP*066810349747*IT*WACT790SP16-BLK

CTP**RTL*9.99

PID*F*08*** Puma Boy Short Red sz M

CTT*3

SE*22*1013

GE*1*1013

IEA*1*100000013

What is an EDI envelope?

The outer envelope ISA / IEA contains one or more functional Groups (GS/GE Envelopes) that contain the data, each in a separate envelope (ST/SE Envelopes).

The ISA / IEA envelope contains the addresses of the recipient company and the sending company.

The GS / GE envelope contains information about the type of documents contained in it, they are denoted as a two-letter code. (functional ID code). For example, PO for 850 Purchase Order, IN for 810 Invoice. Such an envelope contains only documents of the same type. GS also contains sender’s and receiver’s ID code, functional Group control numbers, date and time.

Functional Group Header (GS)


Functional Group Trailer (GE)

Functional Group Trailer (GE)

EDI segments

A segment in an EDI document is a group of identical data elements that may occur several times, to provide information about a product (i.e. weight, color, size, etc.)

edi x12 Segment

Segment optionality

Segments in a EDI X12 document  can be of two types:

M (mandatory) – a mandatory segment. Such a segment contains the basic information of the document. The mandatory segment cannot be omitted from the document. Example of the mandatory segment:

BEG*00*SA*2332233**20190510

This is the (BEG) segment of the header, it contains general document information:

  • Destination (00 – Original)
  • type (SA – Stand-alone Order)
  • order number (2332233)
  • 20190510 – Mai 10, 2019

This segment identifies the document.

O is an optional segment. These are segments containing secondary information. Optional segments may not be present in the EDI document. An example of an optional segment:

PER*BD*Contact Name*TE*123-456-7890

This is a PER segment – Administrative Communications Contact, i.e. “contact information”. This segment contains the following information:

  • BD- Buyer Name or Department
  • TE – Telephone
  • The phone number itself 123-456-7890

EDI Document Structure

The initial segments of each section, is called Header, and the final segment is called Trailer:

  • ISA – Interchange Control Header – this is the segment that defines the sender and recipient.
  • GS – Functional Group Header – this segment defines the type of document(s) that are included in this group.
  • ST – Transaction Set Header – this segment starts the document and is used to assign a control number.
  • SE – Transaction Set Trailer – the segment defines the end of the document.
  • GE – Functional Group Trailer– defines the end of the data that was started by the GS segment.
  • IEA – Interchange Control Trailer – is ending the Interchange segment.

EDI document: Header, Details, and Summary

Each EDI document (i. e. an order, an invoice) is divided into three groups – Header, Details, and Summary.

EDI structure

The Header of the document contains general information such as number, contact information, dates of delivery, addresses, etc.

The details of the EDI document contain information about the ordered product (quantity, price, etc.).

The Summary contains information such as the total cost of the goods, number of goods, etc.

Using EDI in business

EDI is used in many industries, but primarily in trading, transport, and logistics.

Retailers such as Costco, Walmart, and others use EDI X12 to exchange electronic documents with their trading partners.

Typically, a retailer and suppliers exchange the following EDI documents:

EDI is the connecting suppliers and retailers and allows business partners to minimize errors, and automate processes.

Free EDI consultation

RELATED POSTS:

What is EDIFACT? | UN / EDIFACT standard overview

Electronic Data Interchange: Key Information You Need to Know

What Are the Differences Between ANSI X12 and UN/EDIFACT

A technical introduction to EDI

This post was updated to reflect current trends and information.

To exchange business documents and transactions between business partners via EDI (electronic data interchange), most companies in North America use the EDI ANSI ASC X12 Standards. This overview provides some basic information about the X12 standards for electronic data interchange (EDI).

What do ANSI, ASC, X12, and RSC mean?

The American National Standards Institute (ANSI) is a non-profit organization that controls the development of standards for processes, services, and products in the United States. ANSI also synchronizes U.S. standards with international standards so that American products can be used all over the world.

X12 Overview

Chartered by the ANSI for over 40 years, X12 develops and maintains EDI standards and XML schemas that govern business processes around the world.
X12 is comprised of thousands of experts representing over 600 companies from various industries. X12 Membership is open to any organization, company, or even individual, who directly and materially affected by X12 activities.
To facilitate the exchange of business transactions, X12 members regularly optimize the EDI standard.
X12 consists of two committees:
– Accredited Standards Committee (ASC)
– Registered Standards Committee (RSC).

Useful: What is EDI? (A technical introduction to EDI)

Accredited Standards Committee ACS

Since 1979, the Accredited Standards Committee X12 (ASC) has been developing and maintaining the X12 standard, which can be represented as US national standards or UN / EDIFACT international electronic data interchange standards.

The ASC is composed of different subcommittees:
– X12C – Communications and Controls
– X12F – Finance
– X12I – Transportation
– X12J – Technical Assessment
– X12M – Supply Chain
– X12N – Insurance

Registered Standards Committee (RSC)

The RSC is responsible for the development and support of X12 work products for various industries but is not intended to be presented as US national standards.

What is EDI ANSI ASC X12 Standards?

The ANSI ASC X12 Standards is sometimes called the EDI ASC X12, ANSI X12, ASC X12, or simply the X12 Standard. X12 is a set of standards and rules that determine a specific syntax for structuring and transferring electronically business documents between partners. There are different types of business documents in EDI, which often are called “Transaction Sets”.

ASC X12 Transaction Set

The Transaction Set – is a single business document such as a Purchase Order, Invoice, Student Educational Record (Transcript), Healthcare claim, Ship Notice (ASN). There are hundreds of Transaction Sets available in the ANSI ASC X12 standards. Each set of transaction data is identified by a 3 digits code number:

ASC X12 Transaction Set

X12 Transaction Set Structure

Many X12 transaction sets have 3 parts. The segments that can be used in each of these parts in a particular document (such as an invoice) are listed in the related tables defined in the X12 standards document. For example:

X12 Transaction Set Structure

ASC X12 Segments and Sequence

The following Purchase Order example, shows which segments can be used in the transaction set and the desired sequence of segments:

ID            TITLE

ST           Transaction Set Header

BEG        Beginning Segment for Purchase Order

CUR       Currency

REF         Reference Identification

PER        Administrative Communications Contract

TAX        Tax Reference

FOB        F.O.B. Related Information

CTP        Pricing Information

PAM      Period Amount

CSH        Sales Requirements

TC2         Commodity

Beginning and Ending ASC X12 Transaction Sets:

• A transaction in an X12 document, always begins with the Transaction Set Header (ST) segment

• A transaction in an X12 document always ends with the Transaction Set Trailer (SE) segment

X12 Structure

If you want to learn more about the structure of EDI ANSI ASC X12, please read this article: EDI ANSI ASC X12 – Technical Overview


ANSI X12 EDI document types

Since a uniform standard of EDI (electronic data interchange) ANSI X12 was developed, a huge number of companies use it in its business-to-business (B2B) operations. Although ANSI X12 standard was developed to support companies in different types of industries in North America, these days, businesses worldwide are using X12 EDI standard.

As mentioned above, there is a huge amount of ANSI X12 document types available for use. ANSI X12 standard is used in finance, transportation, healthcare, insurance, government, supply chain and other industries for performing diverse operations. The example below shows some of those EDI documents:

Communications and Control:

  • EDI 864 Text Messages
  • EDI 997 Functional Acknowledgment
  • EDI 999 Implementation Acknowledgment
  • EDI 993 Secured Receipt or Acknowledgment

Finance:

  • EDI 130 Student Educational Record (Transcript)
  • EDI 262 Real Estate Information Report
  • EDI 810 Invoice
  • EDI 812 Credit/Debit Adjustment
  • EDI 131 Student Educational Record (Transcript) Acknowledgment
  • EDI 149 Notice of Tax Adjustment or Assessment
  • EDI 150 Tax Rate Notification
  • EDI 821 Financial Information Reporting

Transportation:

  • EDI 120 Vehicle Shipping Order
  • EDI 106 Motor Carrier Rate Proposal
  • EDI 419 Advance Car Disposition
  • EDI 216 Motor Carrier Shipment Pickup Notification
  • EDI 309 Customs Manifest

Supply Chain:

Insurance:

  • EDI 270 Health Care Eligibility/Benefit Inquiry
  • EDI 271 Health Care Eligibility/Benefit Response
  • EDI 111 Individual Insurance Policy and Client Information
  • 837 Health Care Claim

EDI Outsourcing

We support all EDI standards including ANSI(ASC) X12, EDIFACT, RosettaNet, HIPAA / X12. We provide a cloud-based, fully managed EDI integration solution under our program EDI2XML Managed Services which allows our clients to interact with their business partners without implementing a complex EDI infrastructure.

Our popular managed EDI integration service, is accessible and affordable to even small- and medium-sized businesses.


Book a FREE one-on-one EDI consultation session with our in-house experts.


Benefits of fully managed EDI service:

• Time: Reduced transaction processing time and improved customer service

• Cost: Improved inventory management and minimized use of paper and physical storage

• Quality: Enhanced business relationships with your business partners, and accuracy of information

• Profit: Reduce costs

• Efficiency: Increased productivity

EDI2XML Web Services (Rest API)

EDI2XML web services, our REST API to convert X12 to XML and vice versa meant for companies who got their own technical resources to work with REST API (call and consume HTTP Rest Web services).

Benefits of EDI2XML web service:

  • Self-service solution
  • Low cost
  • Quick entry: you can be up and running in less than an hour, and it is proven
  • We offer a 15 days free trial, without any commitment.

Contact us for more information and for pricing.