New Vendor EDI Development

Overview

EDI (Electronic Data Interchange) can allow Yellow Dog Inventory to automatically communicate with third-party systems via text files, typically via FTP or network folders. For our purposes, EDI file formats can include X12, CSV, A2A or any custom layout.

Yellow Dog Inventory also has the capability to import and export data manually. Please see Generic Sync for more information.

We build a new Sync for each EDI vendor. This is typically referred to as SyncYdiWithVendor.

Configuration

Support options for EDI syncs include:

Invoices/Receipts
Product Guides
Purchase Order

During the development investigation detail on which documents will be used will need to be provided. Each sync is customized per vendor and specification on file format will be requested.

Sync Approach

Files are typically published to an FTP server by the vendor and pulled by YDI. We can use a vendor's FTP account or we can provide an FTP account. Each vendor/customer should have a unique FTP account. We can use other transports, such as SFTP.

The sync can be installed from any location that has acces to the FTP location. Typically this is installed alongside the Yellow Dog client.

Sync Frequency

EDI Syncs are typically scheduled hourly but will also depend on the configuration of the vendor’s exports.

Requirements

Partner Requirements

The partner is responbsible for the following:

FIle specifications that include
- Standard File Naming
- File Format
Agreed upon transpot (FTP location)
- Yellow Dog can provide an FTP location
Export schedule
Sample Data
- Including detail on Credit Memos, Returns and Expenses

Data Exchange

Receipts / Invoices

For Receipt or Invoice consumption the following data elements are acceptable (please note that certain fields are required):

 
  DataRequiredDescription
 
  VendorYesCode or Description that uniquely identifies the vendor - This detail can also be provided in the file name if consistently provided
 
  Location/Customer NumberYesCode or Description that identifies which store the invoice is for
 
  Invoice NumberYesCode the uniquely identifies the invoice document
 
  Invoice Amount (total)YesTotal per document (each line on the same invoice will be the same)
 
  Invoice DateYesDate of Delivery
 
  Unit CostYesPurchase Cost Per Unit
 
  Item DescriptionYesDescirption of item
 
  Unit Of MeasureYesPurchased Size
 
  Inv. QtyYesLine Item Quantity
 
  UPC
 
  Vendor SKUYesCode indentifying the item unique to the vendor
 
  Due DateOptional Field for identifying payment due date
 
  ReferenceOptional Field for vendor specific notation for the invoice - not line detail
 
  FreightOptional Expense Field - This will be the total Freight Expense per document (each line on the invoice the same)
 
  Fuel SurchargeOptional Expense Field - This will be the total FuelSurcharge Expense per document (each line on the same invoice will be the same)
 
  TaxOptional Expense Field - This will be the total Tax expense per document (each line on the same invoice will be the same)
 
  Misc ExpensesOptional Expense Field - this will be the total of any other Miscellaneous Expenses per document (each line ont he same invoice will be the same)
 
  Purchase Order IDOptional Code that identifies the related purchase order

Data	Required	Description
Vendor	Yes	Code or Description that uniquely identifies the vendor - This detail can also be provided in the file name if consistently provided
Location/Customer Number	Yes	Code or Description that identifies which store the invoice is for
Invoice Number	Yes	Code the uniquely identifies the invoice document
Invoice Amount (total)	Yes	Total per document (each line on the same invoice will be the same)
Invoice Date	Yes	Date of Delivery
Unit Cost	Yes	Purchase Cost Per Unit
Item Description	Yes	Descirption of item
Unit Of Measure	Yes	Purchased Size
Inv. Qty	Yes	Line Item Quantity
UPC
Vendor SKU	Yes	Code indentifying the item unique to the vendor
Due Date		Optional Field for identifying payment due date
Reference		Optional Field for vendor specific notation for the invoice - not line detail
Freight		Optional Expense Field - This will be the total Freight Expense per document (each line on the invoice the same)
Fuel Surcharge		Optional Expense Field - This will be the total FuelSurcharge Expense per document (each line on the same invoice will be the same)
Tax		Optional Expense Field - This will be the total Tax expense per document (each line on the same invoice will be the same)
Misc Expenses		Optional Expense Field - this will be the total of any other Miscellaneous Expenses per document (each line ont he same invoice will be the same)
Purchase Order ID		Optional Code that identifies the related purchase order