EDI and B2B standards

One B2B gateway for every standard your partners use

Retailers ask for X12, European customers send EDIFACT, energy partners use NAESB and banks expect NACHA files. ECOM's B2B gateway translates and validates each of these standards and connects them to your ERP and business systems, so you do not run a separate tool for every industry.

Talk to an EDI/API Expert Request a Demo

Summary: EDI and B2B Standards

  • An EDI standard defines the structure of a business document, such as a purchase order or invoice, so two companies' systems can exchange it without manual…
  • Retailers ask for X12, European customers send EDIFACT, energy partners use NAESB and banks expect NACHA files.
  • What ECOM covers: Translation and mapping, Validation, Acknowledgments, Versions and message types.
  • What you gain: One platform, many industries, Partners keep their standard, Fewer point solutions.
  • Next step: talk to an EDI/API expert about your trading partners, documents and systems.
Discuss your standards

At a glance

  • Translation and mapping
  • Validation
  • Acknowledgments
  • Versions and message types

What is an EDI standard?

An EDI standard defines the structure of a business document, such as a purchase order or invoice, so two companies' systems can exchange it without manual re-keying. Standards bodies publish the segments, elements and codes; each trading partner then publishes an implementation guide that says which parts it requires.

Outcomes

What you can expect

01

One platform, many industries

Retail, automotive, energy, chemical, aviation and banking standards run through the same gateway, monitoring and support.

02

Partners keep their standard

Each partner exchanges the standard and version it requires, and your systems receive data in the format they expect.

03

Fewer point solutions

Consolidating standards on one gateway reduces separate translators, scripts and specialist tools to maintain.

Approach

How ECOM delivers it

  • Translation and mapping

    Documents are translated between the partner's standard and your ERP, flat file, XML or JSON formats.

  • Validation

    Inbound and outbound documents are checked against the standard and the partner's implementation guide before they move on.

  • Acknowledgments

    Functional and application acknowledgments are generated and reconciled where the standard defines them.

  • Versions and message types

    The versions and message types for each partner are confirmed during scoping and maintained as partners change them.

Cross-industry EDI

Cross-industry and regional EDI standards

The standards most trading partners use for orders, ship notices, invoices and payments.

X12 transaction guides
  • X12 EDI

    The ASC X12 standard used across North America for orders, ship notices, invoices, transportation and healthcare documents.

    X12 EDI in detail
  • UN/EDIFACT

    The United Nations standard used internationally, especially in Europe and Asia, for trade, transport and customs messages.

    UN/EDIFACT in detail
  • TRADACOMS

    The UK retail standard still used by some British retailers and their suppliers for orders and invoices.

    TRADACOMS in detail
  • ODETTE

    European automotive messages and practices from the ODETTE organization, used between vehicle makers and suppliers.

    ODETTE in detail
  • VDA

    The German automotive association's data exchange recommendations, from flat-file messages such as VDA 4905 to the EDIFACT-based VDA 4984 and 4987.

    VDA in detail
  • UCS

    The Uniform Communication Standard, an X12-based set used in the US grocery industry, including direct store delivery.

    UCS in detail
  • TDCC

    Transportation EDI standards from the Transportation Data Coordinating Committee, which preceded X12 and appear in legacy flows.

    TDCC in detail
  • CII

    The Japanese cross-industry EDI standard from the Center for the Informatization of Industry, used by Japanese trading partners.

    CII in detail

Industry standards

Industry XML and B2B standards

Standards defined for specific industries, many of them XML-based.

  • RosettaNet

    XML process standards (PIPs) used in the high-tech and electronics supply chain for forecasts, orders and shipments.

    RosettaNet in detail
  • NAESB

    Standards from the North American Energy Standards Board for exchanging data in the wholesale and retail energy markets.

    NAESB in detail
  • PIDX

    Petroleum Industry Data Exchange standards for orders, field tickets and invoices in the oil and gas industry.

    PIDX in detail
  • CIDX

    Chemical industry e-business standards (Chem eStandards) for orders, shipments and invoices between chemical companies.

    CIDX in detail
  • SPEC2000

    The aviation industry e-business specification for parts ordering, maintenance and supply chain data.

    SPEC2000 in detail
  • OAGIS

    The Open Applications Group integration specification, XML business object documents used between enterprise applications.

    OAGIS in detail

Payments and banking

Payment and banking formats

Payment files and messages exchanged with banks and financial institutions.

  • NACHA

    The ACH file format used in the United States for direct deposits, vendor payments and collections.

    NACHA in detail
  • Fedwire

    Message formats for the Federal Reserve's Fedwire Funds Service, used for high-value US dollar transfers.

    Fedwire in detail
  • CHIPS

    Message formats for the Clearing House Interbank Payments System, used for large-value US dollar payments between banks.

    CHIPS in detail

Message-level references

Every message and version, by standard

Dedicated reference pages list the messages and versions ECOM's B2B gateway handles for these standards. They sit in the Resources menu.

B2B gateway coverage
  • VDA, TRADACOMS and ODETTE

    Automotive and retail messages from Germany, the United Kingdom and the European automotive supply chain, with every message and edition listed.

  • RosettaNet, cXML and SPEC2000

    Partner Interface Processes, procurement network documents and the aviation chapters, listed by cluster, document and version.

  • CII

    The Japanese syntax rule versions and the industry message sets built on them.

Scenarios

Common scenarios

New partner in a new industry

A manufacturer adds an energy or aviation customer that requires a standard its current EDI tool does not support.

International customers

A US supplier starts shipping to European customers who send EDIFACT orders instead of X12.

Payments alongside orders

Finance teams exchange NACHA payment files with banks through the same monitored gateway as their EDI.

Frequently asked questions

Can one platform really handle X12, EDIFACT and industry XML standards?

Yes. The B2B gateway translates each standard to and from your internal formats. ECOM confirms the versions and message types each of your partners requires during scoping.

Do we need to change our ERP to support a new standard?

Usually not. The gateway converts the partner's standard into the format your ERP already accepts, such as IDocs, APIs, flat files or database tables.

Which versions of each standard are supported?

Versions vary by partner and industry. ECOM reviews each partner's implementation guide and confirms the versions and documents before building maps.

Talk to us about your partners' standards

Tell us which standards and partners you need to support. An ECOM specialist confirms the versions, documents and connection plan.