0% found this document useful (0 votes)
109 views15 pages

Pre-Delivery Invoice

The document is an X12 transaction set containing the format and data contents for a pre-delivery invoice (894). It includes required header and detail segments to transmit invoice information prior to product delivery, such as invoice number, purchase order number, delivery date, quantities, and item details. Loops are used to specify line item details for the delivery transaction.

Uploaded by

good hans
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
109 views15 pages

Pre-Delivery Invoice

The document is an X12 transaction set containing the format and data contents for a pre-delivery invoice (894). It includes required header and detail segments to transmit invoice information prior to product delivery, such as invoice number, purchase order number, delivery date, quantities, and item details. Loops are used to specify line item details for the delivery transaction.

Uploaded by

good hans
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

X12V4010 Pre-Delivery Invoice - 894

BeerBoard
894 Pre-Delivery Invoice
X12/V4010/894 : Pre-Delivery Invoice

Version: 1.6

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

894 Pre-Delivery Invoice


Functional Group= DX

Purpose: This X12 Transaction Set contains the format and establishes the data contents of the Pre-
Delivery Invoice Transaction Set (894) for use within the context of an Electronic Data Interchange (EDI)
environment. The EDI 894 will transmit all necessary invoice information prior to the delivery of the
product.
Note: Standard Interchange and Group Segments required.

Heading:

Id Req Segment Name Max Use Max Loop Loop ID Usage


ST Y Transaction Set Header 1 Must Use

G82 Y Delivery/Return Base Record 1 Must Use


Identifier

N9 N Header 1 Used
Detail:
LOOP ID - LS

LS N Loop Header 1 Used

LOOP ID - 0100 9999


G83 Y Segment-Line Item Detail 1 0100 Must Use

G72 N Allowance or Charge 10 Used

LE N Loop End Trailer 1 Used

Summary:
G72 N Allowance or Charge 10 Used

G84 Y Delivery/Return Record of Totals 1 Must Use

G86 Y Signature Identification 1 Must Use

G85 Y Record Integrity Check 1 Must Use

SE Y Transaction Set Trailer 1 Must Use

Data type Codes


N - Numeric, AN - Alphanumeric, (x) - X Number of Decimals, ‘x’ - use X in this field, Date(yyyyMMdd)

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: ST Transaction Set Header


Loop: N/A
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of an invoice transaction set and transmit identifying
numbers and dates

Segment Position Field Name Description Length Data Type Req?


ST 1 Transaction Set Code identifying the type of transaction 3/3 N Y
Identifier Code
CodeList Summary
(Total Codes: 318, Included: 1)

Code Name
894 Pre-delivery Notice

ST 2 Transaction This is the control number of the 4/9 AN Y


Control Number document. Same as SE_02

Semantics:
1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to
select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

BeerBoard Segment Example:


ST*894*000000001~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: G82 Delivery/Return Base Record Identifier


Loop: N/A
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To transmit identifying numbers, dates, and other basic data relating to the
transaction set

Segment Position Field Name Description Length Data Type Req?


G82 1 Credit or Debit Flag D= Debit Transaction; C = Credit 1/1 ID Y
Code Transaction

G82 2 Invoice Number Invoice Number. 1/22 AN Y

G82 3 Retailer DUNS Retailer Dun & Bradstreet 9/9 ID N


Number

G82 4 Retailer Location Retailer Location/Store Number* 4/13 AN Y


Number

G82 5 Supplier's DUNS Supplier's DUNS 9/9 ID N


Number

G82 6 Supplier’s Vendor Supplier’s Vendor Number 1/13 AN N


Number

G82 7 Physical Delivery Invoice Delivery Date 8/8 Date Y


Date (yyyyMMdd)

G82 8 Due Date Invoice/Payment Due Date 8/8 Date Y


(yyyyMMdd)

G82 9 PO Number Purchase Order Number 1/22 AN Y

G82 10 PO Date Purchase Order Date 8/8 Date Y


(yyyyMMdd)

* G8204: Store Number is expected to be a minumum length of 4, 0 filled to left as needed.

BeerBoard Segment Example:


G82*D*8596875*123456789*0854*001234567*D86592*20190411*20190414*6975324*20190410~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: N9 Header
Loop:
Level: Header
Usage: Optional
Max Use: 1
Purpose: To indicate the beginning of an invoice transaction set and transmit identifying
company information

Segment Position Field Name Description Length Data Type Req?


N9 1 Refernce Qualifier Used to determine if the N9 02 field 2/3 ID Y
Code Name
CR Customer Reference Number

N9 2 Reference Distributor's Customer ID 1/80 AN N

N9 3 Free Form Customer Company Name 1/45 AN N

Note: At least one of N902 or N903 is required.

BeerBoard Segment Example:


N9*CR*440001970*Buffal Wiad Wings #854~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: LS Loop Header


Loop:
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To indicate that the next segment begins a loop

Segment Position Field Name Description Length Data Type Req?


LS 1 Loop Identifier Code Loop Identifier; always use 0100 4/6 ‘0100’ N

BeerBoard Segment Example:


LS*0100~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: G83 Segment-Line Item Detail


Loop:
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To specify the basic, and most frequently used line item data for the delivery record
transaction

Segment Position Field Name Description Length Data Type Req?


G83 1 Transaction Count Current Transaction Count; 1 /4 N N
Incremental

G83 2 Quantity Number of Units Delivered 1/15 N Y

G83 3 Unit of Measure Unit or Basis of Measure 2/2 AN Y


Code Name
CA Case
KE Keg
EA Each

G83 4 Carrier/Pack UPC UPC Consumer Package Code 12/12 N N


(1-5-5-1)

G83 5 Product ID Qualifier Qualifying Code for Vendor 2/2 AN N


Product Number

Code Name
VN Vendor Product Number

G83 6 Product ID Vendor Product/Item Number 1/14 AN N

G83 7 Case UPC Outer Case UPC 12/14 N N

G83 8 Full Price Item List Cost 1/9 N(4) Y

G83 9 Pack Number of Inner Packs 6/6 AN N

G83 10 Product Name Product or Item Description 1/20 AN Y

G83 11 Product ID Qualifier Qualifying Code for Vendor 6/6 AN N


Product Number

Code Name
SP Supplier Product Number

G83 12 Product ID Supplier’s Product/Item Number 1/14 AN N

BeerBoard Segment Example:


G83*1*5*CA*081564354884*VN*1809*081564453877*6.8892*24*Light Beer Pfckfge*SP*705490~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: G72 Adjustment Detail


Loop:
Level: Detail
Usage: Mandatory, if charges or discounts exist
Max Use: 1
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the
amount or percentage for the service, promotion, allowance, or charge

Segment Position Field Name Description Length Data Type Req?


G72 1 Adjustment Code Code Name 1/3 ID Y
97 Discount
501 Taxes
525 Deposits
526 Beverage Tax
537 State/Province Tax
999 Other Fees

G72 2 Allowance or Charge 02 - Off Invoice 2/2 ID N


Handle Code

G72 5 Rate Allowance or Charge Rate 1/15 N(4) N

G72 6 Quantity Number of Units Charged 1/10 N N

G72 7 Unit/Basis Measure Unit of Measure 2/2 ID N


Code
Code Name
CA Case
KE Keg
EA Each

G72 8 Allowance or Charge Extended Price 1/15 N(2) Y


per Item

Note:It is suggested that with respect to representing taxes on the 894, G7201 Codes are used in the
following manner:
537 = State/County/City/Local Taxes
526 = Sugar Tax
501 = All Other Taxes

BeerBoard Segment Example:


G72*97*02***2.2500*3*CA*6.75~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: LE Loop Trailer


Loop:
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To transmit an electronic identity

Segment Position Field Name Description Length Data Type Req?


LE 1 Loop Identifier The loop ID number given on 1/12 AN N
Code the transaction set diagram is
the value for this data element
in segments LS and LE

BeerBoard Segment Example:


LE*0100*~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: G72 Adjustment Detail


Loop:
Level: Summary
Usage: Mandatory, if adjustments exist
Max Use: 1
Purpose: To request or identify a service, promotion, allowance, or charge; to specify the
amount or percentage for the service, promotion, allowance, or charge

Segment Position Field Name Description Length Data Type Req?


G72 1 Adjustment Code Code Name 1/3 ID Y
501 Tax
504 Freight/Del. Fee
514 Surcharge
526 Beverage Tax
537 State/Province Tax

G72 2 Allowance or Charge 06 - Charge to be paid by 2/2 ID Y


Handle Code Customer

G72 5 Rate Allowance or Charge Rate 1/15 N(4) N

G72 6 Quantity Number of Units Charged 1/10 AN N

G72 8 Allowance or Charge Extended Price 1/15 N(2) Y


per Item

Note:It is suggested that with respect to representing taxes on the 894, G7201 Codes are used in the
following manner:
537 = State/County/City/Local Taxes
526 = Sugar Tax
501 = All Other Taxes

BeerBoard Segment Example:


G72*504*06***1.0000***3.00~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: G84 Delivery/Return Record of Totals


Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit an electronic identity

Segment Position Field Name Description Length Data Type Req?


G84 1 Quantity Total Cases 1/15 N(4) N

G84 2 Invoice Total Total Invoice Amount 1/10 N(Assumed 2) Y

BeerBoard Segment Example:


G84*4.5000*24500*~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: G86 Signature Identification


Loop: N/A
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit an electronic identity

Segment Position Field Name Description Length Data Type Req?


G86 2 Name Distributor’s Name/DBA 1/60 AN Y

BeerBoard Segment Example:


G86**Distributlr’s Nfme~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: G86 Record Integrity Check


Loop: N/A
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To transmit an electronic identity

Segment Position Field Name Description Length Data Type Req?


Integrity Value calculated by using CRC 16
G85 1 Check Value algorithm 1/12 AN Y

If not supported by the sender, then used Value = 0000

BeerBoard Segment Example:


G85*3E17~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Segment: SE Transaction Set Trailer


Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To specify summary of total segments

Segment Position Field Name Description Length Data Type Req?


SE 1 Segment Count Current Segment Count 1/10 AN Y

SE 2 Document Control Number Document Control or Trace 4/9 AN Y


Number

BeerBoard Segment Example:


SE*12*35880001~

BeerBoard Version 1.6 10/17/2019


X12V4010 Pre-Delivery Invoice - 894

Example Test File:

ISA*00* *00* *ZZ*SenderID *ZZ*ReceiverID *050728*1252* *00401*000001949*0*P*>~


GS*DX*SenderID*ReceiverID*20190428*125200*1949*X*004010~
ST*894*19490001~
G82*D*8596875*123456789*0854*001234567*D86592*20190411*20190414*6975324*20190410~
N9*CR*440001970*Buffal Wiad Wings #854~
LS*0100~
G83*1*5*CA*081564354884*VN*1809*081564453877*6.8892*24*Light Beer Pfckfge*SP*705490~
G72*97*02***2.2500*3*CA*6.75~
LE*0100*~
G72*504*06***1.0000***3.00~
G84*4.5000*24500*~
G86**Distributlr’s Nfme~
G85*3E17~
SE*12*19490001~
GE*1*1949~
IEA*1*000001949~

Contact - [email protected]

BeerBoard Version 1.6 10/17/2019

You might also like