Tag Archive for: ANSI ASC X12 Standards

Every business knows that efficient and accurate data exchange between partners is critical. Electronic Data Interchange (EDI) X12 stands as a standardized protocol that enables organizations to automate the exchange of business documents, reducing manual errors and accelerating processes. In this article, we’ll delve into the components of EDI X12, explore its applications across different sectors, and discuss modern solutions that can help your organization harness the full potential of EDI integration.

What Is EDI X12 and How It Powers EDI Software

EDI X12 is an electronic communication protocol developed by the Accredited Standards Committee X12 under ANSI in 1979. It defines a uniform set of rules and document formats for exchanging key business transactions—such as purchase orders (EDI 850), invoices (EDI 810), and shipping notices (EDI 856) etc.

Why it matters: Standardization reduces errors and manual intervention and cutting order processing times.

EDI X12 Standards and Codes

EDI X12 is based on transaction sets – numbered templates that represent specific business documents. For example, the 850 is the Purchase Order, and the 810 is the Invoice.

Think of an X12 transaction as a standardized form that both you and your trading partner fill in electronically.

Segments = Form Sections

  • Each segment groups related information—just like a section on a paper form (e.g., a “Name” section).
  • Segments start with a three-character code (e.g., NM1 for name data, DTP for date data).

Data Elements = Form Fields

  • Inside each segment are data elements, the individual fields you complete (for example: last name, first name, middle initial).
  • Delimiters (like * or |) separate these fields, just as boxes separate fields on a paper form.

ANSI Code Lists = Dropdown Menus

  • Many fields rely on predefined code lists (think dropdown menus) to keep values consistent—state codes (CA, NY) or standardized payment terms, for example.

Automated Validation = Instant Error-Checking

  • EDI software parses each segment and data element, then compares them against the standard definitions and code lists.
  • If a field is missing, too long, or uses an invalid code, the system flags an error—ensuring every document matches exactly what both sides expect.

By structuring messages this way, EDI X12 guarantees that every “form” you send or receive is complete, correctly formatted, and immediately verifiable—eliminating guesswork and manual fixes.

If you want to learn more about the EDI X12 Transaction Set, read our article: EDI ANSI ASC X12 Standards – Technical Overview

EDI Communication Protocols

Common EDI transport methods include:

  • AS2 (Applicability Statement 2). AS2 uses HTTPS (Hypertext Transfer Protocol Secure) and other secure technologies like digital certificates and encryption to ensure the confidentiality, integrity, and authenticity of the data during transmission
  • SFTP (Secure File Transfer Protocol) is a network protocol that securely transfers files between systems over the internet. It uses SSH (Secure Shell) technology to encrypt data, making it a more secure alternative to traditional FTP, which transfers data unencrypted.EDI-communication
  • OFTP2 (Odette File Transfer Protocol version 2) is a secure file transfer protocol primarily used in the automotive industry for exchanging electronic data interchange (EDI) messages. It’s an advanced version of the OFTP protocol, designed to operate securely over the internet, offering features like data compression, file encryption, and digital certificate exchange for enhanced security.
  • HTTP‑based APIs is an Application Programming Interface (API) that uses the Hypertext Transfer Protocol (HTTP) to facilitate communication between clients and servers. It allows applications to exchange data or request services from a server over the internet.
  • VAN (Value-Added Network) it’s a secure, third-party service that facilitates the exchange of electronic data interchange (EDI) documents between businesses. VANs act as intermediaries, ensuring secure and efficient communication between trading partners.

Why it matters: Choosing the optimal protocol ensures data integrity, security, and compatibility with partner systems, minimizing delays and leveraging your existing IT stack.

EDI Message Structure

Below is a clearer breakdown of the X12 envelope structure, with authoritative sources confirming each layer and its purpose:

An X12 interchange always uses three nested envelope levels—Interchange (ISA/IEA), Functional Group (GS/GE), and Transaction Set (ST/SE)—followed by detail segments (loops) and their trailers.

Each envelope pair carries its own control numbers and delimiters to maintain data integrity. Within the transaction set, loops group related segments (like “Name” or “Address” loops), and data elements within those segments act like individual form fields, often constrained by ANSI code lists for consistency and automatic validation.

Interchange Envelope (ISA / IEA)

  • Definition: The outermost wrapper for an entire EDI transmission.
  • Segments:
    • ISA (Interchange Control Header) at the start
    • IEA (Interchange Control Trailer) at the end
  • Purpose: Identifies sender/receiver IDs, delimiters, version, and a unique control number; it can contain multiple functional groups.

Functional Group (GS / GE)

  • Definition: Groups a batch of transaction sets of the same type (e.g., all purchase orders).
  • Segments:
    • GS (Functional Group Header)
    • GE (Functional Group Trailer)
  • Purpose: Ensures all included transactions share the same document type code and version; carries its own group control number for error tracking.

Transaction Set (ST / SE)

  • Definition: The individual “document” (e.g., a single invoice or advance ship notice).
  • Segments:
    • ST (Transaction Set Header)
    • SE (Transaction Set Trailer)
  • Purpose: Marks the beginning and end of one transaction, with its own transaction control number matching between ST and SE.

Detail Segments and Loops

Loops

  • Concept: Loops group related segments that may repeat (for example, multiple “Name” segments in one document).
  • Purpose: Allows repeatable structures—such as multiple line items in an invoice—to be cleanly organized, much like subfolders in a filing cabinet.

Data Elements

  • Definition: The individual pieces of information within each segment (akin to form fields).
  • ANSI Code Lists: Many elements use standardized code lists (e.g., state codes, currency codes) to ensure consistency across trading partners.
  • Validation: EDI translators automatically check each segment and data element against the standard definitions; any missing or malformed field triggers an error immediately.

Control Numbers and Integrity

  • Control Numbers: Each envelope layer (ISA/IEA, GS/GE, ST/SE) has its own control number that must match between header and trailer.
  • Integrity: These layered control structures guarantee that every interchange, group, and transaction can be tracked, acknowledged, and audited end-to-end.

Thus, an X12 interchange always uses the ISA–IEA, GS–GE, and ST–SE envelope pairs, followed by loops of detail segments and trailers, with data elements governed by ANSI code lists.

This hierarchical structure, confirmed by multiple vendor and standards-body resources, ensures reliable, consistent, and auditable EDI exchanges across industries.

 

EDI Document Example (EDI 850)

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

Modern EDI Solutions by EDI2XML

EDI Web Services (Online EDI)

EDI2XML Web Service provides an HTTP‑based REST API that auto‑detects incoming EDI or XML messages and performs bi‑directional conversion. Developers can call a simple HTTP endpoint—no local software to install.

Online EDI reduces time‑to‑live from weeks to days, freeing IT to focus on core applications rather than translation engines.

Fully Managed EDI Service

EDI2XML’s Fully Managed Service handles end‑to‑end EDI operations—translation, communication, mapping, exception handling—on the client’s behalf. This EDI consulting model eliminates the need for in‑house EDI expertise.

Outsourcing integration ensures projects stay on time and on budget, reducing internal staffing overhead.

On‑Premises EDI

For organizations requiring tight data control, on‑premises EDI solutions run entirely within corporate firewalls. EDI2XML can deploy mapping engines on‑site to meet strict compliance and data‑sovereignty mandates.

On‑premises EDI satisfies rigorous security requirements while leveraging proven ANSI X12 standards.

Role of the EDI Service Provider

An EDI service provider bridges technical complexity and business needs. Responsibilities include project management, platform setup, map development, testing, data integration, and ongoing support. Providers also monitor standards updates to keep partners aligned with the latest X12 versions.

Partnering with experts accelerates EDI adoption, mitigates risks, and delivers visibility across your trading‑partner network.

Benefits of EDI Integration

Implementing EDI X12 as part of a robust integration strategy delivers clear ROI: automation cuts manual data‑entry errors, transaction costs and order cycle times. Uniform data standards enable real‑time visibility into supply chains, empowering leaders to make data‑driven decisions.

These efficiency gains translate to cost savings, stronger partner relationships, and the agility to scale operations rapidly.

EDI X12: A Cornerstone of Modern B2B Communication

Today, EDI X12 powers billions of transactions every day across all industries, but especially in retail, manufacturing, healthcare, finance, and logistics. Its standardized formats ensure that critical business documents such as purchase orders, invoices, and shipping notices are exchanged accurately and efficiently between trading partners.

B2B EDI solutions have evolved to meet a variety of business needs. Options range from cloud-based EDI web services that offer scalability and ease of access to fully managed EDI services that handle the complexities of EDI transactions on your behalf. For organizations that require more control, on-premises EDI systems provide a customizable solution within their own IT infrastructure.

EDI Software and Integration: What You Need to Know

Implementing EDI X12 requires three core components:

  • EDI Software to generate, translate, and send files.
  • EDI Integration to connect your internal systems (like ERP, accounting, or WMS).
  • A communications protocol (AS2, FTP, VAN) to transfer documents securely.

You can handle this in-house or partner with EDI consulting experts who offer fully managed B2B EDI solutions.

EDI- Price

Common Misconceptions

“EDI is outdated.” Wrong. EDI X12 is still the standard across supply chains, and it evolves with industry needs.

“Online EDI is only for large corporations.” Not anymore. Many cloud-based platforms make it accessible for small and mid-sized businesses.

“EDI is hard to set up.” Not if you choose the right EDI integration partner or managed EDI consulting provider.

FAQs: Quick Answers to Common Questions

What is EDI X12 used for?

It’s used to electronically exchange standard business documents (POs, invoices, shipping notices, etc.) between trading partners.

What is the difference between EDI X12 and XML?

EDI X12 uses a flat‑file, fixed‑delimiter format optimized for fast parsing, while XML relies on verbose, tag‑based markup. EDI X12 remains more compact and quicker to process.

How do I start using EDI X12?

You’ll need EDI software, trading partner agreements, and integration with your internal systems. Many businesses start with an EDI service provider.

Is EDI X12 the same as EDIFACT?

No. EDIFACT is the international counterpart; EDI X12 is primarily used in North America.

Can I use EDI without an ERP?

Yes. Online EDI  or HTTP EDI Web Service (REST API) let companies exchange documents without full ERP integration.

What are Fully Managed EDI ?

These are services from EDI Service Provider that help businesses manage their EDI needs—from document exchange to partner communication and compliance.

Can small businesses benefit from EDI X12?

Absolutely. Cloud‑based online EDI services require no upfront software investment and integrate with popular accounting and ERP platforms, making EDI solutions accessible to SMBs.

How long does it take to onboard a new trading partner?

With managed services and templated maps, onboarding can drop from months to a few weeks, depending on document complexity and partner readiness.

What security measures protect EDI transmissions?

Protocols like AS2 and SFTP offer encryption, digital signatures, and non‑repudiation, ensuring data confidentiality and integrity in transit.

Industries and Companies Using EDI X12

Electronic Data Interchange (EDI) X12 is integral to automating and streamlining business communications across multiple sectors. Below is a detailed look at key industries leveraging EDI, highlighting specific transaction sets and real-world applications.

EDI for Automotive

Major automotive manufacturers like Toyota, Ford, and General Motors (GM) rely heavily on EDI to synchronize their complex supply chains. They utilize:

  • EDI 830 Planning Schedule with Release Capability, communicating forecasted demand to suppliers.
  • EDI 862 Shipping Schedule, providing detailed shipping requirements.
  • EDI 866 Production Sequence, detailing the sequence of production.
  • EDI 856 Advance Ship Notice, offering detailed shipment information to streamline receiving processes.
  • EDI 824 Application Advice, indicating acceptance, rejection, or changes to previously transmitted documents.

This integration ensures just-in-time manufacturing and reduces inventory costs.

Retail & Consumer Goods

Retail giants such as Walmart, Target, and Home Depot use EDI to manage vast supplier networks efficiently. Key transaction sets include:

  • EDI 850 Purchase Order, initiating orders with suppliers.
  • EDI 855 Purchase Order Acknowledgment, confirming receipt and acceptance of purchase orders.
  • EDI 856 Advance Ship Notice, detailing shipment contents and logistics.
  • EDI 810 Invoice, facilitating accurate and timely billing.
  • EDI 820 Payment Order/Remittance Advice, providing payment details to suppliers.
  • EDI 832 Price/Sales Catalog, sharing product and pricing information.
  • EDI 846 Inventory Inquiry/Advice, communicating inventory levels.
  • EDI 860 Purchase Order Change Request – Buyer Initiated, requesting changes to purchase orders.
  • EDI 865 Purchase Order Change Acknowledgment/Request – Seller Initiated, responding to purchase order changes.

By automating these documents, retailers minimize errors and accelerate order fulfillment.

Logistics & Transportation

Companies like FedEx, UPS, and XPO Logistics employ EDI to enhance shipment tracking and coordination. They commonly use:

  • EDI 204 Motor Carrier Load Tender, offering detailed shipment information to carriers.
  • EDI 990 Response to a Load Tender, indicating acceptance or rejection of a shipment offer.
  • EDI 210 Motor Carrier Freight Details and Invoice, detailing charges for services rendered.
  • EDI 211 Motor Carrier Bill of Lading, providing legal documentation for shipments.
  • EDI 214 Transportation Carrier Shipment Status Message, providing real-time updates on shipment status.

This real-time data exchange improves delivery accuracy and customer satisfaction.

Healthcare

Hospitals, clinics, and insurance providers utilize EDI to comply with HIPAA regulations and streamline administrative processes. Key transactions include:

  • EDI 837 Healthcare Claim, used by providers to submit claims electronically.
  • EDI 835 Healthcare Claim Payment/Advice, detailing payment information from insurers to providers.
  • EDI 270 Eligibility, Coverage or Benefit Inquiry, requesting information on patient eligibility.
  • EDI 271 Eligibility, Coverage or Benefit Information, responding to eligibility inquiries.
  • EDI 276 Health Care Claim Status Request, inquiring about the status of submitted claims.
  • EDI 277 Health Care Claim Status Notification, providing updates on claim status.
  • EDI 278 Health Care Services Review Information, requesting authorization for services.
  • EDI 834 Benefit Enrollment and Maintenance, enrolling members in healthcare plans.
  • EDI 999: Implementation Acknowledgment, confirming receipt and acceptance of EDI transactions. It is similar to the EDI 997.

This automation reduces paperwork and accelerates reimbursement cycles.

Finance

Financial institutions and corporations use EDI to manage payments and financial reporting. Common transaction sets are:

  • EDI 820 Payment Order/Remittance Advice, facilitating electronic payments and remittance details.
  • EDI 823 Lockbox, providing detailed information about payments received.
  • EDI 821 Financial Information Reporting, sharing financial data.
  • EDI 822 Account Analysis, detailing account activity.
  • EDI 827 Financial Return Notice, reporting inability to process or modifications to payment orders.
  • EDI 828 Debit Authorization, authorizing debit transactions.
  • EDI 829 Payment Cancellation Request, requesting cancellation of payments.

These transactions enhance cash flow management and financial accuracy.

High-Tech & Manufacturing

Electronics and high-tech manufacturers depend on EDI for efficient supply chain operations. They often use:

  • EDI 846 Inventory Inquiry/Advice, sharing inventory levels between partners.
  • EDI 830 Planning Schedule with Release Capability, communicating production forecasts.
  • EDI 862 Shipping Schedule, providing detailed shipping requirements.
  • EDI 867 Product Transfer and Resale Report, detailing product movement and sales.
  • EDI 824 Application Advice, indicating acceptance, rejection, or changes to previously transmitted documents.

This data exchange supports demand planning and reduces stockouts.

The EDI 997 Functional Acknowledgment is a universally utilized transaction set across all industries that engage in Electronic Data Interchange (EDI). Its primary function is to confirm the receipt and syntactical correctness of EDI documents, ensuring that the data transmitted between trading partners has been successfully received and processed by the recipient’s EDI system.

The Bottom Line

If you’re doing business in a connected world, EDI X12 is part of the language you need to speak. Whether you’re scaling operations, improving accuracy, or speeding up supply chain flows, EDI X12 plays a central role.

It’s not about technology for technology’s sake—it’s about working smarter with the systems your partners already use.

Contact EDI2XML today for a free consultation

 

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 Envelope)

An interchange envelope is a structured data set to deliver electronic transactions to a receiving party. Interchange can include a package of groups of documents, but may also 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

EDI Segment Optionality

Segments in an 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, the 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 its 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.