Departments > EDI > Implementation Guide > Why, What and How

What is EDI?

Electronic Data Interchange is computer to computer exchange of standard business documents…

Purchase orders (850) Invoices (810) Load Tender (204)
Inventory Status (852) Supply and Demand Projections (830) Response to Load Tender (990)
Checks/Payments (820) Transportation/Shipping (856) Shipment Status Message (214)
Application Advice (824) Functional Acknowledgement (997)  

EDI makes this all possible by standardizing the format of business documents. The ANSI Commission (American National Standards Institute) is responsible for formatting EDI standards. ANSI periodically reviews and updates the standards in newer ANSI versions.

Electronic Purchase Orders (ANSI 850)
Over 2700 vendors are currently using our electronic purchase order application. This application:

  • Shortens your order lead time. Suppliers have the ability to access Ace Purchase Orders the same day they are created.
  • Provides a direct interface with your order processing system.
  • Improves order accuracy by eliminating manual entry problems.

Electronic Invoices (ANSI 810)
There are plenty of opportunities for both Ace and vendors in this application. Let’s look at the benefits to you, the vendor.

  • Improved Cash Flow
  • Transmitting invoices to us ensures timely processing and payment. EDI allows you to eliminate mail and payment delays because your invoices are no longer lost in transit or misdirected.
  • We process your invoices the day you transmit them and provide you with a transmission acknowledgment.
  • Improved Accuracy
  • Ace edits the information in your transmission to ensure that the data is accurate, complete and ready for the automatic processing. Our front-end editing includes:
    • Your vendor number and complete remittance address.
    • Your standard cash terms and the payment due date.
    • Our dealer’s store number, address and zip code.
    • Our RSC address.
    • Our purchase order number.
  • Elimination of Entry and Calculation Errors
  • All manual key entry and calculations are performed by our system. We automatically process and calculate:
  • Standard payment due dates.
  • Show specials or dating due dates.
  • Cash discounts.

We even recalculate and add your invoice lines to verify the invoice totals.

All of the above benefits translate into one huge benefit to you - Accurate, timely payments!

And one additional advantage - once we have you up and running on our EDI invoice application, we then have the mechanism in place to start transmitting our payments to you via EFT.

Electronic Payments and Remittances (ANSI 820)
The cash flow benefits to electronic payments are obvious. With payments via EFT, the exact date that funds are available in your bank account is guaranteed. You no longer have to rely on the postal service or be concerned that our check is lost in transit.

We also provide for the electronic transmission of remittance data directly to you. Now here’s a real time saver for you - take our remittance data, incorporate it into you receivables system and eliminate any mutual cash application.

Ace’s ability to pay electronically is limited to those vendors transmitting electronic 810 invoice information. So, if you’re not already transmitting invoices, start today!

Application Advice (824)
Ace sends Electronic Funds Transfer data to a bank. The bank in turn sends Ace an Application Advice document to let us know how their application systems processed the EFT data. This report lets Ace know about any content problems that the bank encountered, such as missing ABA numbers or incorrect payment dates.

Advanced Shipping (ANSI 856)
Advance Ship Notices are a key component to our overall Quick Response Program. Transmission of Advance Shipping Notices allows Ace to:

  • Preprint receiving documents based on what is actually shipped. This allows us to place your product in a salable position faster and more efficiently.
  • Provides essential expediting information to our merchandising staff eliminating phone calls and freeing up your Customer Service department.

Stock Status (ANSI 852)
This application provides you with daily, weekly or monthly on-hand, on-order and demand information for your products in our 15 retail support centers. This application is also useful for production planning within your organization.

Scheduling / Forecasting (ANSI 830)
Ace can provide you with quantities we are projecting to sell from our retail support centers within a six or 12 month window. This information is available to you on either an annual or semi-annual basis.

Motor Carrier Load Tender (ANSI 204)
This EDI document enables Ace to electronically offer a shipment to a transportation carrier. The Load Tender includes scheduling information, equipment requirements and shipping instructions.

Response to a Load Tender (ANSI 990)
The carrier uses this document to notify Ace of their acceptance of a Load Tender.

Shipment Status Message (ANSI 214)
Enables a carrier to provide Ace with a status of a shipment in terms of dates, times, locations, route and conveyance.

BASIC EDI TRANSMISSION STRUCTURE

An EDI transmission can contain one or more transactions (documents) going to one trading partner. These transaction sets are enclosed in three different EDI "envelopes". Like an envelope for paper correspondence these EDI envelopes (headers/trailers) are "addressed" with sender/receiver IDs, content information, totals, tracking "control" numbers and summary information.

INTERCHANGE HEADER (ISA)

FUNCTIONAL GROUP HEADER (GS)

TRANSACTION SET HEADER (ST)

(Purchase Order)
TRANSACTION SET

TRANSACTION SET TRAILER (SE)

FUNCTIONAL GROUP TRAILER (GE)

FUNCTIONAL GROUP HEADER (GS)

TRANSACTION SET HEADER (ST)

(Purchase Order)
TRANSACTION SET

TRANSACTION SET TRAILER (SE)

FUNCTIONAL GROUP TRAILER (GE)

INTERCHANGE CONTROL TRAILER (IEA)

1. Interchange Envelope ISA/IEA:
- Sender/Receiver
- Matching control numbers
- Function Group count

2. Functional Group Envelope GS/GE:
- Sender/Receiver of GS
- EDI version used
- Matching control numbers
- Transaction Set count (how many documents).

3. Transaction Set Envelope ST/SE:
- Type of data in envelope (PO, invoice, etc).
- Matching control numbers
- Segment count

4. Transaction Set contains:
- Header
- Detail
- Summary (one complete business document).

 

 

ISA¬00¬ ¬00¬ ¬01¬006928311 ¬01¬999999999 ¬040315¬

     1037¬U¬00400¬000000160¬0¬T¬| NL

GS¬PS¬006928311¬999999999¬20040315¬1037¬3¬X¬004010 NL

ST¬830¬0001 NL

BFR¬00¬01¬¬SH¬A¬20040701¬20040101¬20040630 NL

N1¬RL¬¬9¬0069283110001 NL

LIN¬¬IN¬12345¬UP¬123456789012¬VN¬A-123¬ZZ¬10 NL

UIT¬EA NL

SDP¬N¬F NL

FST¬10¬D¬M¬20040701 NL

FST¬15¬D¬M¬20040801 NL

FST¬10¬D¬M¬20040901 NL

FST¬25¬D¬M¬20041001 NL

FST¬50¬D¬M¬20041101 NL

FST¬10¬D¬M¬20041201 NL

CTT¬1 NL

SE¬14¬0001 NL

GE¬1¬3 NL

IEA¬1¬000000160 NL

 

DATA ELEMENT
  - A variable length field.

DATA ELEMENT DELIMITER
  - Separates data elements.

DATA SEGMENT
  - A variable length record.

DATA SEGMENT DELIMITER
  - Separates data segments.

Above is an example of an actual EDI transmission. Notice the ISA/IEA, GS/GE and ST/SE envelopes as shown on the EDI Basic Structure (page 1-3). The actual document (transaction set) starts for the 830 with the BFR data segment record. Each DATA SEGMENT, such as BFR, is separated by a DATA SEGMENT DELIMITER, shown here as NL. Each data segment always starts with the name of the segment which corresponds to the information that record will contain. For example, BFR = Beginning Segment for Planning Schedule, or LIN = Item Identification. Each segment contains many different fields of information called DATA ELEMENTS. These are separated by a DATA ELEMENT DELIMITER, shown here as ¬.