Walgreens
/
Invoice Variance Notification for Distribution Center (DC) Deliveries
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Walgreens. Contact Walgreens for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Walgreens logo

X12 861 Invoice Variance Notification for Distribution Center (DC) Deliveries

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate Transaction Set (861) for use within the context of an Electronic Data Interchange (EDI) environment.
The transaction set can be used to provide for customary and established business and industry practice relative to the notification of receipt or formal acceptance of goods and services.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/walgreens/invoice-variance-notification-for-distribution-center-dc-deliveries/01H40WWGB7CHSYDSH4MJVQF538
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BRA
020
Beginning Segment for Receiving Advice or Acceptance Certificate
Max use 1
Required
REF
050
Reference Identification Internal Vendor Number
Max use 1
Required
REF
050
Reference Identification Invoice Number
Max use 1
Optional
DTM
070
Date/Time Reference Invoice Date
Max use 1
Optional
DTM
070
Date/Time Reference Posted Date
Max use 1
Required
PRF
080
Purchase Order Reference
Max use 25
Required
N1 Loop
detail
RCD Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

RC
Receiving Advice/Acceptance Certificate (861)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
861
Receiving Advice/Acceptance Certificate
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BRA
020
Heading > BRA

Beginning Segment for Receiving Advice or Acceptance Certificate

RequiredMax use 1

To indicate the beginning of a Receiving Advice or Acceptance Certificate Transaction Set and transmit an identifying number, date, and time

  • This transaction set is a Receiving Advice unless BRA04 contains a value of "8". When BRA04 contains a value of "8", the transaction set is an Acceptance Certificate and the units received is the units accepted.
Example
BRA-01
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

When generated by the future SAP system, this will be the SAP GR (Goods Received) number.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BRA02 is the date that the receiving advice transaction set is created.
Usage notes

This is the 861-RV Processing Date, not the Receiving Date

BRA-03
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

Usage notes

The SAC segment will be mandatory when the BRA03 = "5C," which indicates that the 861 is an Invoice Variance.

01
Cancellation
5C
Chargeable Resubmission

This code is used to indicate that the 861 Transaction is an Invoice Variance.

BRA-04
962
Receiving Advice or Acceptance Certificate Type Code
Required
Identifier (ID)

Code specifying type of receiving advice

2
Post Receipt Advice
REF
050
Heading > REF

Reference Identification Internal Vendor Number

RequiredMax use 1

To specify identifying information

Example
Variants (all may be used)
REFReference Identification Invoice Number
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IA
Internal Vendor Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

This field must contain your Legacy 6-digit Walgreens Marketing Vendor Number or 10-digit SAP Vendor Number, as communicated to you on the Purchase Order

REF
050
Heading > REF

Reference Identification Invoice Number

OptionalMax use 1

To specify identifying information

Usage notes

The invoice number should always be present on the Invoice Variance.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IK
Invoice Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

When the EDI-861 information is generated from an SAP activated location, the invoice number value presented in this field will be appended with one of the codes below:
K1 = Quantity Debit Note
K2 = Price Debit Note
R1 = Quantity Debit Note Reversal
R2 = Price Debit Note Reversal

DTM
070
Heading > DTM

Date/Time Reference Invoice Date

OptionalMax use 1

To specify pertinent dates and times

Usage notes

Current Walgreens implementation of the EDI-861 will only provide the Posted Date. In the future, Walgreens may also provide Receipt Date

Example
Variants (all may be used)
DTMDate/Time Reference Posted Date
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

003
Invoice
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

DTM
070
Heading > DTM

Date/Time Reference Posted Date

RequiredMax use 1

To specify pertinent dates and times

Usage notes

Current Walgreens implementation of the EDI-861 will only provide the Posted Date. In the future, Walgreens may also provide Receipt Date

Example
Variants (all may be used)
DTMDate/Time Reference Invoice Date
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

809
Posted
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

The Posting Date is when the receiving information was posted to the future SAP system. This date may be different from the creation date in BRA02.

PRF
080
Heading > PRF

Purchase Order Reference

RequiredMax use 25

To provide reference to a specific purchase order

Example
PRF-01
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

This will be either the Walgreens Legacy 8-digit DC level PO Number or the 10-digit SAP Purchase Order number, as communicated to you on the Purchase Order.

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • PRF04 is the date assigned by the purchaser to purchase order.
Usage notes

This is the Walgreens Purchase Order Date.

N1 Loop
RequiredMax 1
N1
130
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

WH
Warehouse
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

This will be either the Walgreens Legacy 13-character DUNS+4 DC number or 4-character SAP Site number, as communicated to you on the Purchase Order.

N1 Loop end
Heading end

Detail

RCD Loop
OptionalMax 200000
RCD
010
Detail > RCD Loop > RCD

Receiving Conditions

RequiredMax use 1

To report receiving conditions and specify contested quantities

Example
If either Quantity in Question (RCD-06), Composite Unit of Measure (RCD-07) or Receiving Condition Code (RCD-08) are present, then the others are required
RCD-02
663
Quantity Units Received or Accepted
Required
Decimal number (R)
Min 1Max 9

Number of Units Received or Accepted

Usage notes

Received quantity based on posted receipt at the DC.

RCD-03
C001
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
DE
Deal
EA
Each
RCD-06
667
Quantity in Question
Optional
Decimal number (R)
Min 1Max 9

Number of units contested because of physical condition or status of units

  • RCD06 through RCD20 provide for five different quantities whose condition upon receipt is under question.
Usage notes

The exception quantity will be one of the following scenarios:

  1. Overage
  2. Shortage
  3. Quantity Processed without timely matching Advance Ship Notice
RCD-07
C001
Composite Unit of Measure
OptionalMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
DE
Deal
EA
Each
RCD-08
412
Receiving Condition Code
Optional
Identifier (ID)

Code designating physical condition or status of units received in a specific shipment

02
Quantity Short
03
Quantity Over
14
Quantity Received and Processed with No Matching Ship Notice/Manifest
LIN
040
Detail > RCD Loop > LIN

Item Identification

RequiredMax use 100

To specify basic item identification data

Example
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Usage notes

Ordering Number Qualifier

EN
European Article Number (EAN) (2-5-5-1)
ND
National Drug Code (NDC)
UI
U.P.C. Consumer Package Code (1-5-5)
UK
U.P.C./EAN Shipping Container Code (1-2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
VN
Vendor's (Seller's) Item Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Walgreens' SAP Implementation will standardize on the use of "UP" (11-digit UPC plus check-digit) for all items, except in the case of EANs or GTINs.

SAC
170
Detail > RCD Loop > SAC

Service, Promotion, Allowance, or Charge Information

OptionalMax use 10

To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Usage notes

Invoice Variance - When the BRA03 = 5C, the corresponding SAC01 will be Q.

Example
If either Unit or Basis for Measurement Code (SAC-09) or Quantity (SAC-10) is present, then the other is required
SAC-01
248
Allowance or Charge Indicator
Required
Identifier (ID)

Code which indicates an allowance or charge for the service specified

  • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
Usage notes

The value N in the SAC01 indicates a price discrepancy.

C
Charge
N
No Allowance or Charge
Q
Charge Request
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Optional
Identifier (ID)

Code identifying the service, promotion, allowance, or charge

E065
Invoice Adjustment
F680
Price Deviation
SAC-05
610
Amount
Optional
Numeric (N2)
Min 1Max 15

Monetary amount

  • SAC05 is the total amount for the service, promotion, allowance, or charge.
  • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Optional
Decimal number (R)
Min 1Max 9

Rate expressed in the standard monetary denomination for the currency specified

  • SAC08 is the allowance or charge rate per unit.
SAC-09
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
DE
Deal
EA
Each
SAC-10
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
  • SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
  • In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
MAN
180
Detail > RCD Loop > MAN

Marks and Numbers

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

The values conveyed in this segment will be what was originally sent to Walgreens via the Advanced Shipment Notice (EDI-856).

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

Code specifying the application or source of Marks and Numbers (87)

  • MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
  • When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
GM
SSCC-18 and Application Identifier
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

Marks and numbers used to identify a shipment or parts of a shipment

  • When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
RCD Loop end
Detail end

Summary

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.