EDI​​ File​​ Type

EDI​​ File​​ Type

810​​ -​​ Invoice​​ 

The​​ EDI​​ 810​​ Invoice​​ transaction​​ set​​ is​​ the​​ electronic​​ version​​ of​​ the​​ paper-based​​ invoice​​ document.​​ It​​ is​​ typically​​ sent​​ in​​ response​​ to​​ an​​ EDI​​ 850​​ Purchase​​ Order​​ as​​ a​​ request​​ for​​ payment​​ once​​ the​​ goods​​ have​​ shipped​​ or​​ services​​ are​​ provided.

 

820​​ -​​ Payment​​ Order/Remittance​​ Advice​​ 

The​​ X12​​ 820​​ transaction​​ set​​ provides​​ the​​ EDI​​ format​​ for​​ transmitting​​ information​​ relating​​ to​​ payments.​​ It​​ is​​ typically​​ used​​ in​​ conjunction​​ with​​ an​​ electronic​​ transfer​​ of​​ funds​​ for​​ payment​​ of​​ goods,​​ insurance​​ premiums​​ or​​ other​​ transactions.​​ The​​ actual​​ funds​​ transfer​​ is​​ often​​ coordinated​​ through​​ the​​ Automated​​ Clearinghouse​​ (ACH)​​ system,​​ and​​ an​​ 820​​ may​​ be​​ effectively​​ wrapped​​ in​​ an​​ ACH​​ banking​​ transaction.

 

832​​ -​​ Price/Sales​​ Catalog​​ 

The​​ EDI​​ 832​​ Price/Sales​​ Catalog​​ transaction​​ set​​ is​​ used​​ to​​ electronically​​ request​​ or​​ provide​​ the​​ prices​​ of​​ goods​​ or​​ services​​ in​​ the​​ form​​ of​​ a​​ catalog.​​ The​​ 832​​ replaces​​ the​​ paper​​ catalog,​​ and​​ is​​ used​​ by​​ manufacturers​​ to​​ provide​​ detailed​​ product​​ information​​ to​​ their​​ supply​​ chain,​​ including​​ retailers,​​ distributors,​​ dealers​​ and​​ the​​ like.

 

846​​ -​​ Inventory​​ Inquiry/Advice

The​​ EDI​​ 846​​ Inventory​​ Inquiry/Advice​​ transaction​​ set​​ is​​ used​​ to​​ communicate​​ inventory​​ information​​ between​​ manufacturers,​​ their​​ suppliers​​ and​​ resellers.​​ It​​ is​​ used​​ in​​ a​​ number​​ of​​ ways.

 

850​​ -​​ Purchase​​ Order​​ 

The​​ EDI​​ 850​​ is​​ a​​ Purchase​​ Order​​ transaction​​ set,​​ used​​ to​​ place​​ an​​ order​​ for​​ goods​​ or​​ services.​​ The​​ 850​​ generally​​ provides​​ the​​ same​​ information​​ you​​ would​​ find​​ in​​ a​​ paper​​ Purchase​​ Order​​ (PO)​​ document.​​ 

 

855​​ -​​ Purchase​​ Order​​ Acknowledgment​​ 

The​​ X12​​ 855​​ transaction​​ set​​ is​​ a​​ Purchase​​ Order​​ Acknowledgement.​​ It​​ is​​ used​​ by​​ sellers​​ to​​ confirm​​ the​​ receipt​​ of​​ a​​ purchase​​ order​​ (an​​ EDI​​ 850​​ transaction)​​ from​​ a​​ buyer,​​ eliminating​​ the​​ need​​ to​​ call​​ or​​ fax​​ a​​ confirmation.​​ 

The​​ 855​​ also​​ communicates​​ whether​​ the​​ PO​​ was​​ accepted​​ or​​ rejected,​​ or​​ what​​ changes​​ may​​ have​​ been​​ made​​ to​​ accepted​​ orders​​ by​​ the​​ seller.​​ Thus,​​ like​​ many​​ acknowledgement​​ transactions,​​ the​​ 855​​ can​​ indicate​​ that​​ the​​ order​​ was​​ accepted,​​ rejected​​ or​​ accepted​​ with​​ changes.​​ 

 

856​​ -​​ Ship​​ Notice/Manifest​​ 

The​​ EDI​​ 856​​ transaction​​ is​​ more​​ commonly​​ called​​ the​​ Advance​​ Ship​​ Notice​​ or​​ ASN.​​ It​​ is​​ utilized​​ to​​ electronically​​ communicate​​ the​​ contents​​ of​​ a​​ shipment​​ to​​ another​​ trading​​ partner.​​ It​​ is​​ sent​​ in​​ advance​​ of​​ a​​ shipment​​ arriving​​ at​​ the​​ other​​ trading​​ partner’s​​ facility.

 

860​​ -​​ Purchase​​ Order​​ Change​​ Request​​ -​​ Buyer​​ Initiated​​ 

The​​ EDI​​ 860​​ transaction​​ set​​ represents​​ the​​ electronic​​ Purchase​​ Order​​ Change​​ Request.​​ It​​ is​​ used​​ by​​ buyers​​ to​​ request​​ a​​ change​​ to​​ a​​ purchase​​ order​​ (EDI​​ 850)​​ they​​ previously​​ submitted.​​ The​​ 860​​ may​​ also​​ be​​ used​​ by​​ buyers​​ to​​ confirm​​ their​​ acceptance​​ of​​ changes​​ to​​ purchase​​ orders​​ made​​ by​​ the​​ sellers.

 

870​​ -​​ Order​​ Status​​ Report

The​​ EDI​​ 870​​ Order​​ Status​​ Report​​ transaction​​ set​​ is​​ commonly​​ used​​ by​​ vendors​​ to​​ report​​ the​​ current​​ status​​ of​​ a​​ customer’s​​ order.​​ Each​​ Status​​ Report​​ transaction​​ refers​​ to​​ a​​ single​​ order​​ from​​ the​​ customer,​​ though​​ this​​ may​​ involve​​ multiple​​ previously-sent​​ purchase​​ orders.

 

940​​ -​​ Warehouse​​ Shipping​​ Order

The​​ EDI​​ 940​​ Warehouse​​ Shipping​​ Order​​ transaction​​ set​​ is​​ used​​ to​​ instruct​​ remote​​ warehouses​​ to​​ ship​​ orders.​​ It​​ is​​ commonly​​ used​​ by​​ a​​ seller,​​ such​​ as​​ a​​ manufacturer​​ or​​ wholesaler,​​ to​​ authorize​​ a​​ warehouse​​ to​​ make​​ a​​ shipment​​ to​​ a​​ buyer,​​ such​​ as​​ a​​ retailer.​​ The​​ 940​​ may​​ also​​ be​​ used​​ to​​ confirm​​ a​​ shipment,​​ modify​​ a​​ shipment​​ or​​ cancel​​ a​​ previous​​ shipping​​ order.

 

945​​ -​​ Warehouse​​ Shipping​​ Advice

The​​ EDI​​ 945​​ transaction​​ set,​​ referred​​ to​​ as​​ Warehouse​​ Shipping​​ Advice​​ transaction,​​ provides​​ confirmation​​ of​​ a​​ shipment.​​ This​​ transaction​​ is​​ used​​ by​​ a​​ warehouse​​ to​​ notify​​ a​​ trading​​ partner​​ that​​ a​​ shipment​​ was​​ made.

 

997​​ -​​ Functional​​ Acknowledgment​​ 

The​​ EDI​​ 997​​ transaction​​ set,​​ known​​ as​​ the​​ Functional​​ Acknowledgment​​ or​​ FA,​​ is​​ sent​​ as​​ a​​ response​​ to​​ other​​ EDI​​ transactions​​ received.​​ An​​ EDI​​ 997​​ serves​​ as​​ a​​ receipt,​​ to​​ acknowledge​​ that​​ an​​ EDI​​ transaction,​​ or​​ a​​ group​​ of​​ transactions,​​ was​​ received​​ by​​ the​​ remote​​ party.

    • Related Articles

    • EDI​​ Flow

      EDI 관련 System Option upc_assign 123456 assigned upc # upc_fix 6 fixed 6 digit for upc upc_increase 1 increasing value UPC_Internal_Use N Y= UPC is used internal only, and so there is not NRF check. upc_startno 00000 UPC start no. EDI_850_SO_Status ...
    • EDI file transmission status

    • Send EDI 810 file to CIT

    • EDI​​​​ Setup

      1. EDI Customer Setup  INTERTRADE 2. EDI Folder Path 3. UPC Prefix Setup Under Nvlt_upc_companycode 4. Upload EDI Mapping 5. Update Nvlt_system   upc_assign 123456 assigned upc # upc_fix 6 fixed 6 digit for upc upc_increase 1 increasing value ...
    • EDI Manual

      I. Receive EDI Files Go to N41, EDI, EDI File Manager Click “Register EDI file Received by FTP” II. Create and Send 997 N41 should automatically create 997 Go to N41, EDI, EDI File Manager III. Import 850 a. EDI Customer Item# (You can skip this step ...