d01 Remadv MX

Wal-Mart Stores, Inc.
Electronic Data Interchange Implementation Guideline

EDIFACT Version D01B
EANCOM
D
0
1
B
REMADV Message
Business Usage:
Mexico Remittance Advice
EDI Direction: From Wal-Mart
Implementation Guide Version 1.1

Published March 2006
EAN-REMA (D.01B) 1 February 3, 2006

Table of Contents
UN/EDIFACT Introduction to the REMADV Remittance advice message .................................. 3
REMADV - Wal-Mart Stores, Inc. Introduction ............................................................................ 5
REMADV Remittance Advice Message – Wal-Mart Guidelines .................................................. 6
Wal-Mart Business Example of an REMADV Document (Invoice Payment Usage): .................. 7
Wal-Mart Business Example of an REMADV Document (Credit Note Usage):......................... 10
Conventions used in this implementation guideline ..................................................................... 57
Change History ............................................................................................................................. 60

UN/EDIFACT Introduction to the REMADV Remittance
advice message
INTRODUCTION:
This specification provides the definition of the Remittance advice message (REMADV) to be used in Electronic
Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
1. SCOPE
1.1 Functional Definition

The Remittance Advice is a communication between trading partners, e.g. seller, buyer, financial
institutions, which provides a detailed accounting relative to a payment, or other form of financial
ettlement, for the provision of goods and/or services as detailed in the advice.
1.2 Field of Application

The Remittance advice message may be used for both national and international applications. It is based on
universal practice related to administration, commerce and transport, and is not dependent on the type of
business or industry.
1.3 Principles
- A Remittance Advice is a notice of a payment to be made.
- A Remittance Advice may cover one or more commercial trade transactions (and related financial
transactions), such as invoices, credit notes, debit notes, etc.
- A Remittance Advice may include a cross reference to a Payment Order.
- A single Remittance Advice may relate to both national and international settlements.
- Each Remittance Advice shall be calculated in only one currency, even though the related transaction is
denominated in different currencies.
- Each Remittance Advice shall relate to only one settlement date.
- Where remittance advice relates to a dispute, the message :

. does not necessarily relate to one settlement date
. is not necessarily a notice for a payment to be made
- A Remittance Advice may be initiated by either party according to agreements.
2. REFERENCES
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
3.1 Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1 Data Segment Clarification

This section should be read in conjunction with the segment table which indicates mandatory, conditional
and repeating requirements.
The following guidelines and principles apply to the whole message and are intended to facilitate the
understanding and implementation of the message:
All specified dates/times should be in the format 'ccyymmdd'/'hhmm' unless all parties involved in the
transaction agree that there is a functional requirement for an alternative format. Periods should be
specified as whole numbers representing the required period as indicated in the format qualifier (weeks,
months, etc.)
Where a choice of code or text is given only the code element should be used wherever possible.
Conditional data that is not required in the message should not be included.
Care must be taken that the segment qualifier in dependent segments do not conflict with the segment
qualifier of the trigger segment of a group.
Free text information within the message should be avoided as this inhibits automatic processing.

REMADV - Wal-Mart Stores, Inc. Introduction
The purpose of this section is to present and explain the application of the EANCOM standards
as they pertain to the REMADV – Remittance Advice.
The Remittance Advice is a communication between trading partners, e.g. seller, buyer, financial
institutions, which provides a detailed accounting relative to a payment, or other form of
financial settlement, for the provision of goods and/or services as detailed in the advice.
Functional Acknowledgment
A Syntax and Service Report, EANCOM message CONTRL should be sent within 24 hours of
receipt of a REMADV message to acknowledge receipt, or to notify Wal-Mart Stores of syntax
errors.

REMADV Remittance Advice Message – Wal-Mart
Guidelines
The Remittance Advice is a communication between trading partners, e.g., seller, buyer,
financial institutions, which provides a detailed accounting relative to a payment, or other form
of financial settlement, for the provision of goods and/or services as detailed in the advice.
Heading Section:
Pos. Seg. Req. Group Notes and
No. ID Name Des. Max.Use Repeat Comments
M 0010 UNH Message header M 1
M 0020 BGM Beginning of message M 1
M 0030 DTM Date/time/period M 5
0040 RFF Reference C 5
0060 PAI Payment instructions C 1
0090 Segment Group 1: NAD C 99
M 0100 NAD Name and address M 1
0170 Segment Group 4: CUX C 5

M 0180 CUX Currencies M 1
Detail Section:
0200 Segment Group 5: DOC-MOA-DTM-RFF- C 999999
NAD-SG7
M 0210 DOC Document/message details M 1
M 0220 MOA Monetary amount M 5
0230 DTM Date/time/period C 5
0240 NAD Name and address C 2
0243 Segment Group 7: AJT-MOA-RFF C 100
M 0300 AJT Adjustment details M 1
0310 MOA Monetary amount C 1
Section Control:
M 0570 UNS Section control M 1
Summary Section:
M 0620 UNT Message trailer M 1

Wal-Mart Business Example of an REMADV Document
(Invoice Payment Usage):
EDI TRANSMISSION DATA EXPLANATION
UNH+00002+REMADV:D:01B:UN:EAN005 00002 is the MESSAGE REFERENCE NUMBER

REMADV is the Message Type. “REMADV”
indicates “Remittance Advice Message”.
D is the Message Version Number. “D” indicates
“Draft Directory”.
01B is the Message Release Number. “01B” indicates
“Release 2001 - B”.
UN is the Controlling Agency, Coded. “UN” indicates
“UN/CEFACT”.
EAN005 is the Association Assigned Code.
“EAN005” indicates “EAN Version Control Number
(EAN Code)”.
BGM+481+30000000001+9 481 is the Document Name Code. “481” indicates
“Remittance Advice”.
30000000001 is the Document Identifier.
9 is the MESSAGE FUNCTION CODE. “9” indicates
“Original”.
DTM+138:20060208:102' 138 is the Date or time or period function code
qualifier. “138” indicates “Payment Date”.
20060208 is the Date or Time or Period Value.
102 is the Date or Time or Period Format Code.
“102” indicates “CCYYMMDD”.
RFF+IA:123456' IA is the Reference Code Qualifier. “IA” indicates
"Internal Vendor Number".
123456 is the Reference Identifier.
RFF+ZZZ:TIENE PROB. FACT' ZZZ is the Reference Code Qualifier.
TIENE PROB. FACT is the Reference Identifier.
PAI+1 1 is the Payment Conditions Code. “1” indicates
"Direct payment".
NAD+PE+1234567800000::9++VENDOR NAME PE is the PARTY FUNCTION CODE QUALIFIER.
“PE” indicates "Payee" (Vendor).
1234567800000 is the Party Identifier.
9 is the Code List Responsible Agency Code. “9”
indicates “EAN (International Article Numbering
association)”.
VENDOR NAME is the NAME AND ADDRESS.
NAD+PR+7507003100001::9++NVA WALMART PR is the PARTY FUNCTION CODE QUALIFIER.
DE MEXICO S. DE R. “PR” indicates "Payer" (Wal-Mart Stores, Inc.).
association)”.
NVA WALMART DE MEXICO S. DE R. is the
NAME AND ADDRESS.
CUX+2:MXN:11 2 is the Currency Usage Code Qualifier. “2” indicates
“Reference Currency”.
MXN is the Currency Code. “MXN” indicates
“Mexican Peso”.
11 is the Currency Type Code Qualifier. “11”
indicates “Payment Currency”.
DOC+83+2 83 is the Document Name Code. “83” indicates “Credit
note related to financial adjustments”.
MOA+52:-6.9 52 is the Monetary Amount Type Qualifier. “52”
indicates the “Discount amount”
-6.9 is the Monetary Amount.
DTM+137:20060208:102' 137 is the Date or Time or Period Qualifier. “137”
indicates "Payment Date".
20060208 is the Date or Time or Period.
102 is the Date or Time or Period Format Qualifier.
NAD+DP+5412345000172::9 DP is the PARTY FUNCTION CODE QUALIFIER.
“DP” indicates "Delivery Party".
5412345000172 is the Party Identifier
association)”.
AJT+ZZZ ZZZ is the ADJUSTMENT REASON
DESCRIPTION CODE. “ZZZ” Indicates “Mutually
defined”.
RFF+ZZZ:216 ZZZ is the Reference Qualifier. “ZZZ” indicates
"Mutually Defined Reference Number".
216 is the Reference Identifier. “216” indicates “EFT
Commission.
RFF+ALO+3000000713 ALO is the REFERENCE.
3000000713 is the Reference identifier. “3000000713”
is the Receiving advice number.
DOC+380+1 380 is the Document Name Code. “380” indicates
“Commercial invoice”.
MOA+12:3360 12 is the Monetary Amount Type Qualifier. “12” “12”
indicates “Amount remitted”.
3360 is the Monetary Amount.
MOA+165:3360 165 is the Monetary Amount Type Qualifier. “165”
indicates the “Adjustment amount”
MOA+52:0 52 is the Monetary Amount Type Qualifier. “52”
DTM+137:20060208:102 137 is the Date or Time or Period Qualifier. “137”
RFF+PQ:PAGO TOTAL DE FACTURA PQ is the REFERENCE.
PAGO TOTAL DE FACTURA is the Reference code
identifier. “PAGO TOTAL DE FACTURA” is the
Payment reference.
RFF+BT:208 BT is the Reference Code Qualifier. “BT” indicates
"Batch number/Lot Number".
208 is the Wal-Mart receiver number.
NAD+BY+7507003000004::9 BY is the PARTY QUALIFIER “BY” indicates
"Buyer".
association)”.
UNS+S S is the SECTION IDENTIFIER “S” indicates
detail/summary section separation
MOA+12:3353.1 12 is the Monetary Amount Type Code Qualifier.
“12” indicates "Amount remitted".
3353.1 is the Monetary Amount.
UNT+27+1 27 is the NUMBER OF SEGMENTS IN A
MESSAGE.
00001 is the MESSAGE REFERENCE NUMBER.

Wal-Mart Business Example of an REMADV Document
(Credit Note Usage):
EDI TRANSMISSION DATA EXPLANATION
UNH+ME000001+REMADV:D:01B:UN:EAN005 00001 is the MESSAGE REFERENCE NUMBER

REMADV is the Message Type. “REMADV”
indicates “Remittance Advice Message”.
D is the Message Version Number. “D” indicates
“Draft Directory”.
01B is the Message Release Number. “01B” indicates
“Release 2001 - B”.
UN is the Controlling Agency, Coded. “UN” indicates
“UN/CEFACT”.
EAN005 is the Association Assigned Code.
“EAN005” indicates “EAN Version Control Number
(EAN Code)”.
BGM+481+30005557135+9 481 is the Document Name Code. “481” indicates
“Remittance Advice”.
9 is the MESSAGE FUNCTION CODE. “9” indicates
“Original”.
DTM+138:19990208:102' 138 is the Date or time or period function code
qualifier. “138” indicates “Payment Date”.
19990208 is the Date or Time or Period Value.
102 is the Date or Time or Period Format Code.
RFF+IA:123456' IA is the Reference Code Qualifier. “IA” indicates
"Internal Vendor Number".
123456 is the Reference Identifier.
RFF+ZZZ:TIENE PROB. FACT' ZZZ is the Reference Code Qualifier.
TIENE PROB. FACT is the Reference Identifier.
PAI+1 1 is the Payment Conditions Code. “1” indicates
"Direct payment".
NAD+PE+1234567800059::9++VENDOR NAME PE is the PARTY FUNCTION CODE QUALIFIER.
“PE” indicates "Payee" (Vendor).
association)”.
NAD+PR+7507003100001::9++NVA WALMART PR is the PARTY FUNCTION CODE QUALIFIER.
DE MEXICO S. DE R. “PR” indicates "Payer" (Wal-Mart Stores, Inc.).
association)”.
NVA WALMART DE MEXICO S. DE R. is the
Name and Address
CUX+2:MXN:11 2 is the Currency Usage Code Qualifier. “2” indicates
“Reference Currency”.
MXN is the Currency Code. “MXN” indicates
“Mexican Peso”.
11 is the Currency Type Code Qualifier. “11”
indicates “Payment Currency”.
DOC+83+2 83 is the Document Name Code. “83” indicates “Credit
MOA+52:-6.9 52 is the Monetary Amount Type Qualifier. “52”
-6.9 is the Monetary Amount.
association)”.
defined”.
216 is the Reference Identifier. “216” indicates “EFT
Commission.
3000000713 is the Reference code qualifier.
“3000000713” is the Receiving advice number.
DOC+84+1 84 is the Document Name Code. “84” indicates “Debit
MOA+23:68990.06 23 is the Monetary Amount Type Qualifier. “23”
indicates the “Charge Amount”
association)”.
defined”.
208 is the Reference Identifier. “208” indicates
“Withholding payment”.
4048000756 is the Reference code qualifier.
“44048000756” is the Receiving advice number.
UNS+S S is the SECTION IDENTIFIER “S” indicates
detail/summary section separation
MOA+12:68983.16 12 is the Monetary Amount Type Code Qualifier.
“12” indicates "Amount remitted".
UNT+26+00001 26 is the NUMBER OF SEGMENTS IN A
MESSAGE.
00001 is the MESSAGE REFERENCE NUMBER.

Segment: UNH Message header
Position: 0010
Group:
Level: 0
Usage: Mandatory
Max Use: 1
Purpose: A service segment starting and uniquely identifying a message. The message type code
for the Remittance advice message is REMADV.
Note: Remittance advice messages conforming to this document must contain the
following data in segment UNH, composite S009:
Data element 0065 REMADV 0052 D 0054 01B 0051 UN
Dependency Notes:
Semantic Notes:
Comments:
Notes: Remittance Advice Heading Section
This segment is used to head, identify and specify a message.
DE's 0065, 0052, 0054, and 0051: Indicate that the message is a UNSM Remittance
Advice based on the D.01B directory under the control of the United Nations.
Example:
UNH+ME000001+REMADV:D:01B:UN:EAN005'
Data Element Summary

Data Component
Element Element Name Attributes
M 0062 MESSAGE REFERENCE NUMBER M 1 an..14
Unique message reference assigned by the sender.
Senders unique message reference. Sequence number of the messages in
the interchange. DE 0062 in the UNT will be exactly the same. Sender
generated.
M S009 MESSAGE IDENTIFIER M 1
Identification of the type, version, etc. of the message being interchanged.
M 0065 Message type M an..6
Code identifying a type of message and assigned by its controlling agency.
Notes:
1. In UNSMs (United Nations Standard Messages), the representation is a6.
REMADV Remittance advice message
A code to identify the remittance advice message.
EAN Description:
Message which provides a detailed accounting
relative to a payment, or other form of financial
settlement, on a specified date for the provision of
goods and/or services as detailed in the advice.
M 0052 Message version number M an..3
Version number of a message type.
D Draft version/UN/EDIFACT Directory
Message approved and issued as a draft message (Valid
for directories published after March 1993 and prior to
March 1997). Message approved as a standard message
(Valid for directories published after March 1997).
M 0054 Message release number M an..3
Release number within the current message version number.
01B Release 2001 – B
Message approved and issued in the second 2001 release
of the UNTDID (United Nations Trade Data Interchange
Directory).
M 0051 Controlling agency, coded M an..3

Code identifying a controlling agency.
UN UN/CEFACT
United Nations Centre for Trade Facilitation and
Electronic Business (UN/CEFACT).
EAN Description:
UN Economic Commission for Europe (UN/ECE),
Committee on the development of trade (TRADE),
Working Party on facilitation of international trade
procedures (WP.4).
R 0057 Association assigned code C an..6
Code, assigned by the association responsible for the design and maintenance
of the message type concerned, which further identifies the message.
Indicates that the message is the EANCOM version 005 of the Remittance
Advice.
EAN005 EAN version control number (EAN Code)
N 0110 Code list directory version number C an..6
Version number of the code list directory.
N 0113 Message type sub-function identification C an..6
Code identifying a sub-function of a message type.
Notes:
1. The code qualifies the message type data element (0065) to allow the
recipient to identify a specific sub-function of a message.
N 0068 COMMON ACCESS REFERENCE C 1 an..35
Reference serving as a key to relate all subsequent transfers of data to the
same business case or file.
N S010 STATUS OF THE TRANSFER C 1
Statement that the message is one in a sequence of transfers relating to the
same topic.
N 0070 Sequence of transfers M n..2
Number assigned by the sender indicating the transfer sequence of a message
related to the same topic. The message could be an addition or a change to an
earlier transfer related to the same topic.
Notes:
1. The first message in the sequence shall be assigned as number 1.
N 0073 First and last transfer C a1
Indication used for the first and last message in a sequence of messages related
to the same topic.
N S016 MESSAGE SUBSET IDENTIFICATION C 1
Identification of a message subset by its identifier, version, release and source.
N 0115 Message subset identification M an..14
Coded identification of a message subset, assigned by its controlling agency.
N 0116 Message subset version number C an..3
Version number of the message subset.
N 0118 Message subset release number C an..3
Release number within the message subset version number.
N 0051 Controlling agency, coded C an..3
N S017 MESSAGE IMPLEMENTATION GUIDELINE C 1
IDENTIFICATION
Identification of a message implementation guideline by its identifier, version,
release and source.
N 0121 Message implementation guideline identification M an..14
Coded identification of the message implementation guideline, assigned by its
controlling agency.
N 0122 Message implementation guideline version number C an..3
Version number of the message implementation guideline.
N 0124 Message implementation guideline release number C an..3
Release number within the message implementation guideline version number.
N S018 SCENARIO IDENTIFICATION C 1
Identification of a scenario.
N 0127 Scenario identification M an..14
Code identifying scenario.
N 0128 Scenario version number C an..3
Version number of a scenario.
N 0130 Scenario release number C an..3
Release number within the scenario version number.

Segment: BGM Beginning of message
Position: 0020
Group:
Level: 0
Usage: Mandatory
Max Use: 1
Purpose: A segment for unique identification of the Remittance Advice Message, the type of
Remittance Advice and its function.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to indicate the type and function of a message and to transmit
its identifying number.
All references other than the document number DE 1004 are in the RFF segment.
Example:
BGM+481+RA78305+9'

Data Component
R C002 DOCUMENT/MESSAGE NAME C 1
Identification of a type of document/message by code or name. Code preferred.
R 1001 Document name code C an..3
Code specifying the document name.
481 Remittance advice
Document/message advising of the remittance of
payment.
N 1131 Code list identification code C an..17
Code identifying a user or association maintained code list.
Notes:
1. The codes for this data element are provided by the code list responsible
agency defined in data element 3055.
N 3055 Code list responsible agency code C an..3
Code specifying the agency responsible for a code list.
N 1000 Document name C an..35
Name of a document.
R C106 DOCUMENT/MESSAGE IDENTIFICATION C 1
Identification of a document/message by its number and eventually its version
or revision.
R 1004 Document identifier C an..35
To identify a document.
Remittance Advice number assigned by the document initiator.
It is recommended that the length of document number be restricted to a

maximum of 17 characters.
N 1056 Version identifier C an..9
To identify a version.
N 1060 Revision identifier C an..6
To identify a revision.
R 1225 MESSAGE FUNCTION CODE C 1 an..3
Code indicating the function of the message.
The message function coded, is a critical data element in this segment. It
applies to all data indicated in the message. The following definitions apply
for the restricted codes:
5 = Replace - This code indicates that the current remittance advice

message is a replacement due to an error in a previous message. The
previous message should be identified in the RFF segment group 1.
9 = Original - An original transmission of a Remittance Advice.
5 Replace
Message replacing a previous message.
9 Original
Initial transmission related to a given transaction.
N 4343 RESPONSE TYPE CODE C 1 an..3
Code specifying the type of acknowledgment required or transmitted.

Segment: DTM Date/time/period
Position: 0030
Group:
Level: 1
Usage: Mandatory
Max Use: 5
Purpose: A segment specifying the dates, and when relevant, the times related to the whole
message. The segment must be specified at least once to specify the message date as
allocated by the sender.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify dates related to the complete remittance advice
message.
DE 2005: Identification of the 'Document/message date/time' (code value 137) is
mandatory in an EANCOM message.
Example:
DTM+137:20020110:102'
DTM+138:200201081245:203'

Data Component
M C507 DATE/TIME/PERIOD M 1
Date and/or time, or period relevant to the specified date/time/period type.
M 2005 Date or time or period function code qualifier M an..3
Code qualifying the function of a date, time or period.
138 Payment date
[2034] Date on which an amount due is made available to
the creditor, in accordance with the terms of payment.
R 2380 Date or time or period value C an..35
The value of a date, a date and time, a time or of a period in a specified
representation.
R 2379 Date or time or period format code C an..3
Code specifying the representation of a date, time or period.
102 CCYYMMDD
Calendar date: C = Century ; Y = Year ; M = Month ; D =
Day.

Segment: RFF Reference
Position: 0040
Group:
Level: 1
Usage: Conditional (Optional)
Max Use: 5
Purpose: A segment for referencing documents which relate to the whole message.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify any references which relate to the complete
remittance advice.
References only applying to the complete Remittance Advice should be given at this
point. References to a specific commercial document/message, e.g., Invoice,
Purchase Order or Despatch Advice are provided in the RFF segment of the detail
section per document/message identified in the DOC segment.
Example:
RFF+CT:54223'

Data Component
M C506 REFERENCE M 1
Identification of a reference.
M 1153 Reference code qualifier M an..3
Code qualifying a reference.
IA Internal vendor number
Number identifying the company-internal vending
department/unit.
This is the six digit vendor number assigned to the
payee by Wal-Mart.
R 1154 Reference identifier C an..70
Identifies a reference.
N 1156 Document line identifier C an..6
To identify a line of a document.
N 4000 Reference version identifier C an..35
To identify the version of a reference.

Position: 0040
Group:
Level: 1
Max Use: 5
Purpose: A segment for referencing documents which relate to the whole message.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify any references which relate to the complete
remittance advice.
References only applying to the complete Remittance Advice should be given at this
point. References to a specific commercial document/message, e.g., Invoice,
Purchase Order or Despatch Advice are provided in the RFF segment of the detail
section per document/message identified in the DOC segment.
Example:
RFF+CT:54223'

Data Component
ZZZ Mutually defined reference number
Number based on party agreement.
Local payment code.

Segment: PAI Payment instructions
Position: 0060
Group:
Level: 0
Max Use: 1
Purpose: A segment specifying the conditions, guarantee, method and channel of payment for the
Remittance Advice.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used by the sender of the Remittance Advice to indicate how
payment is being made.
Example:
PAI+1::42'

Data Component
M C534 PAYMENT INSTRUCTION DETAILS M 1
Indication of method of payment employed or to be employed.
O 4439 Payment conditions code C an..3
Code specifying the payment conditions.
1 Direct payment
An assigned invoice has been paid by the buyer to the
factor.
N 4431 Payment guarantee means code C an..3
Code specifying the means of payment guarantee.
N 4461 Payment means code C an..3
Code identifying a means of payment.
Notes:
N 4435 Payment channel code C an..3
Code specifying the payment channel.

Group: NAD Segment Group 1: Name and address
Position: 0090
Group:
Level: 1
Max Use: 99
Purpose: A group of segments identifying the parties involved in the transaction and, optionally the
contact points and numbers.
Notes: A group of segments identifying the parties involved in the transaction and,
optionally the contact points and numbers.
Segment Summary
Pos. Seg. Req. Max. Group:
No. ID Name Des. Use Repeat

Segment: NAD Name and address
Position: 0100 (Trigger Segment)
Group: SG1
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment to identify a party name and address, either by coded identification or in clear
form.
It is recommended that where possible only the coded form of the party ID should be
specified e.g. the Buyer and Seller are known to each other, thus only the coded ID is
required.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to identify the parties exchanging the Remittance Advice
message, and if necessary, any associated parties. The identification of the payer and
payee, and buyer and seller if different from the payer and payee, are mandatory in
the Remittance Advice message.
Example:
NAD+PR+5456789000017::9'
NAD+PE+3323456007896::9'
Dependency Notes:
The following composites and data elements are only used when a coded name and
address can not be used. The affected composites and data elements are as follows:
C080 - C059 - 3164 - C819 - 3251 - 3207

Data Component
M 3035 PARTY FUNCTION CODE QUALIFIER M 1 an..3
Code giving specific meaning to a party.
PE Payee
Identifies the credit party when other than the beneficiary.
A C082 PARTY IDENTIFICATION DETAILS C 1
Identification of a transaction party by code.
M 3039 Party identifier M an..35
Code specifying the identity of a party.
For identification of parties it is recommended to use GLN - Format n13.
Notes:
R 3055 Code list responsible agency code C an..3
9 EAN (International Article Numbering association)
EAN International, based in Belgium, is an organization
of EAN Member Organizations that jointly manages the
EAN.UCC System with the Uniform Code Council.
EAN Description:
EAN International.
N C058 NAME AND ADDRESS C 1
Unstructured name and address: one to five lines.
N 3124 Name and address description M an..35
Free form description of a name and address line.
N 3124 Name and address description C an..35
D C080 PARTY NAME C 1
Identification of a transaction party by name, one to five lines. Party name
may be formatted.
M 3036 Party name M an..35
Name of a party.
N 3036 Party name C an..35
Name of a party.
Name of a party.
Name of a party.
Name of a party.
N 3045 Party name format code C an..3
Code specifying the representation of a party name.
N C059 STREET C 1
Street address and/or PO Box number in a structured address: one to four
lines.
N 3042 Street and number or post office box identifier M an..35
To identify a street and number and/or Post Office box number.
N 3042 Street and number or post office box identifier C an..35
N 3164 CITY NAME C 1 an..35
Name of a city.
N C819 COUNTRY SUB-ENTITY DETAILS C 1
To specify a part of a country (eg county or part of a city).
N 3229 Country sub-entity name code C an..9
Code specifying the name of a country sub-entity.
Notes:
| 1. Recommended use ISO 3166-2. If not applicable, use appropriate code set
defined by appropriate national authority.
Notes:
N 3228 Country sub-entity name C an..70

Name of a country sub-entity.
N 3251 POSTAL IDENTIFICATION CODE C 1 an..17
Code specifying the postal zone or address.
Notes:
1. Use code defined by appropriate national authority.
N 3207 COUNTRY NAME CODE C 1 an..3
| Identification of the name of the country or other geographical entity as
defined in ISO 3166-1.
Notes:
| 1. Use ISO 3166-1 two alpha country code.

Group: NAD Segment Group 1: Name and address
Position: 0090
Group:
Level: 1
Max Use: 99
Purpose: A group of segments identifying the parties involved in the transaction and, optionally the
contact points and numbers.
Notes: A group of segments identifying the parties involved in the transaction and,
optionally the contact points and numbers.
Segment Summary

Group: SG1
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment to identify a party name and address, either by coded identification or in clear
form.
It is recommended that where possible only the coded form of the party ID should be
specified e.g. the Buyer and Seller are known to each other, thus only the coded ID is
required.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to identify the parties exchanging the Remittance Advice
message, and if necessary, any associated parties. The identification of the payer and
payee, and buyer and seller if different from the payer and payee, are mandatory in
the Remittance Advice message.
Example:
NAD+PR+5456789000017::9'
NAD+PE+3323456007896::9'
Dependency Notes:
C080 - C059 - 3164 - C819 - 3251 - 3207

Data Component
PR Payer
(3308) Party initiating payment.
Notes:
EAN Description:
EAN International.
may be formatted.
Name of a party.
Name of a party.
Name of a party.
Name of a party.
Name of a party.
N C059 STREET C 1
lines.
Name of a city.
Notes:
Notes:

Notes:
Notes:

Group: CUX Segment Group 4: Currencies
Position: 0170
Group:
Level: 1
Max Use: 5
Purpose: A group of segments specifying the currencies and related dates/periods valid for the
whole Remittance Advice. Currency data may be omitted in national applications but
will be required for international transactions.
Notes: A group of segments specifying the currencies and related dates/periods valid for
the whole Remittance Advice.
Segment Summary
M 0180 CUX Currencies M 1

Segment: CUX Currencies
Group: SG4
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment identifying the currencies required in the Remittance Advice. A rate of
exchange may be given to convert a reference currency into a target currency.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to indicate currency information related to the complete
remittance advice. The CUX segment may be omitted for national exchanges. The
CUX segment is mandatory for international exchanges.
A remittance advice will refer to ONLY ONE payment currency.
The CUX segment may be used also to indicate other currencies specified previously
in the transaction, such as pricing currency, invoicing currency, etc.
When specifying Reference and Target Currencies for international trade, one
occurrence of CUX is all that is required. The reference currency is identified in the
first occurrence of composite C504, with the target currency specified in the second
occurrence of C504, The rate of exchange between the two is detailed in DE 5402.
The general rule for calculating rate of exchange is as follows:
Reference Currency multiplied by Rate = Target Currency.
Example:
CUX+2:EUR:11'
CUX+2:EUR:11+3:USD:4+0.98'

Data Component
R C504 CURRENCY DETAILS C 1
The usage to which a currency relates.
M 6347 Currency usage code qualifier M an..3
Code qualifying the usage of a currency.
2 Reference currency
The currency applicable to amounts stated. It may have to
be converted.
R 6345 Currency identification code C an..3
Code specifying a monetary unit.
Notes:
1. Use ISO 4217 three alpha code.
MXN Mexican Peso
USD US Dollar
R 6343 Currency type code qualifier C an..3
Code qualifying the type of currency.
11 Payment currency
The name or symbol of the monetary unit used for
payment.
O 6348 Currency rate value C n..4
To specify the value of the multiplication factor used in expressing currency
units.
N C504 CURRENCY DETAILS C 1
The usage to which a currency relates.
N 6347 Currency usage code qualifier M an..3
Code qualifying the usage of a currency.
N 6345 Currency identification code C an..3
Notes:
N 6343 Currency type code qualifier C an..3
N 6348 Currency rate value C n..4
To specify the value of the multiplication factor used in expressing currency
units.
N 5402 CURRENCY EXCHANGE RATE C 1 n..12
To specify the rate at which one specified currency is expressed in another
specified currency.
N 6341 EXCHANGE RATE CURRENCY MARKET IDENTIFIER C 1 an..3
To identify an exchange rate currency market.

Group: DOC Segment Group 5: Document/message details
Position: 0200
Group:
Level: 1
Max Use: 999999
Purpose: A group of segments providing details of all documents, e.g. invoices, statements,
despatch advises, etc., to which the Remittance Advice refers. It includes information on
the monetary amounts for each document and on any adjustments (with an indication of
the reason for adjustments) and discounts. For information purposes an indication of the
tax element can be provided.
Notes: A group of segments providing details of all documents, e.g. invoices, statements,
despatch advices, etc, to which the Remittance Advice refers. It includes information
on the monetary amounts for each document and on any adjustments (with an
indication of the reason for adjustments) and discounts. For information purposes
an indication of the tax element can be provided.
Remittance Advice Detail Section
Segment Summary
M 0210 DOC Document/message details M 1
0230 DTM Date/time/period C 5
0240 NAD Name and address C 2
0243 Segment Group 7: Adjustment details C 100

Segment: DOC Document/message details
Group: SG5
Level: 1
Usage: Mandatory
Max Use: 1
Purpose: A segment for identifying the reference document against which payment is being made.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to provide details of the documents, e.g., a group of invoices, to
which the Remittance Advice refers. The detail section of the Remittance Advice is
formed by a repeating groups of DOC segments. Individual document line item
information is provided in the DLI segment.
Example:
DOC+380+458011'

Data Component
M C002 DOCUMENT/MESSAGE NAME M 1
Identification of a type of document/message by code or name. Code preferred.
D 1001 Document name code C an..3
Code specifying the document name.
83 Credit note related to financial adjustments
Document message for providing credit information
related to financial adjustments to the relevant party, e.g.,
bonuses.
84 Debit note related to financial adjustments
Document/message for providing debit information
related to financial adjustments to the relevant party.
380 Commercial invoice
Document/message claiming payment for goods or
services supplied under conditions agreed between seller
and buyer.
381 Credit note - goods and services
Document/message for providing credit information to the
relevant party.
383 Debit note - goods and services
Document/message for providing debit information to the
relevant party.
Notes:
N 1000 Document name C an..35
Name of a document.
O C503 DOCUMENT/MESSAGE DETAILS C 1
Identification of document/message by number, status, source and/or language.
R 1004 Document identifier C an..35
To identify a document.
N 1373 Document status code C an..3

Code specifying the status of a document.
N 1366 Document source description C an..70
Free form description of the source of a document.
N 3453 Language name code C an..3
Code specifying the language name.
Notes:
1. Use ISO 639-1988.
N 1056 Version identifier C an..9
To identify a version.
N 3153 COMMUNICATION MEDIUM TYPE CODE C 1 an..3
Code specifying the type of communication medium.
N 1220 DOCUMENT COPIES REQUIRED QUANTITY C 1 n..2
Quantity of document copies required.
N 1218 DOCUMENT ORIGINALS REQUIRED QUANTITY C 1 n..2
Quantity of document originals required.

Segment: MOA Monetary amount
Position: 0220
Group: SG5
Level: 2
Usage: Mandatory
Max Use: 5
Purpose: A segment giving the monetary amounts for the amount due and the amount to be
remitted.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to provide monetary amounts related to the document
specified in the previous DOC segment.
The specification of the amount due and amount remitted relevant to the particular
document identified in the DOC segment is mandatory.
Example:
MOA+12:75000'

Data Component
M C516 MONETARY AMOUNT M 1
Amount of goods or services stated as a monetary amount in a specified
currency.
M 5025 Monetary amount type code qualifier M an..3
Code qualifying the type of monetary amount.
12 Amount remitted
[5444] Total sum charged in respect of one or more
Invoices in accordance with the terms of delivery.
R 5004 Monetary amount C n..35
To specify a monetary amount.
Notes:
N 4405 Status description code C an..3
Code specifying a status.
Notes:
1. For transport status, use UN/ECE Recommendation 24.

Position: 0220
Group: SG5
Level: 2
Usage: Mandatory
Max Use: 5
remitted.
Dependency Notes:
Semantic Notes:
Comments:
Example:
MOA+12:75000'

Data Component
currency.
23 Charge Amount
Notes:
Notes:

Position: 0220
Group: SG5
Level: 2
Usage: Mandatory
Max Use: 5
remitted.
Dependency Notes:
Semantic Notes:
Comments:
Example:
MOA+12:75000'

Data Component
currency.
52 Discount Amount
Notes:
Notes:

Position: 0220
Group: SG5
Level: 2
Usage: Mandatory
Max Use: 5
remitted.
Dependency Notes:
Semantic Notes:
Comments:
Example:
MOA+12:75000'

Data Component
currency.
165 Adjustment Amount
Notes:
Notes:

Segment: DTM Date/time/period
Position: 0230
Group: SG5
Level: 2
Max Use: 5
Purpose: A segment to specify the date of the referenced document and to indicate any other
relevant dates applicable, e.g. Due date, Tax point date, etc.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to indicate the date of the document identified in the DOC
segment.
Example:
DTM+137:20021215:102'

Data Component
M C507 DATE/TIME/PERIOD M 1
Date and/or time, or period relevant to the specified date/time/period type.
M 2005 Date or time or period function code qualifier M an..3
Code qualifying the function of a date, time or period.
137 Document/message date/time
(2006) Date/time when a document/message is issued.
This may include authentication.
R 2380 Date or time or period value C an..35
The value of a date, a date and time, a time or of a period in a specified
representation.
R 2379 Date or time or period format code C an..3
Code specifying the representation of a date, time or period.
102 CCYYMMDD

Position: 0240
Group: SG5
Level: 2
Max Use: 5
Purpose: A segment for the inclusion of any additional references related to the reference
document.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to provide references related to the document identified in the
DOC segment.
Example:
RFF+CT:78321'

Data Component
BT Batch number/lot number
Reference number assigned by manufacturer to a series of
similar products or goods produced under similar
conditions.
Wal-Mart receiver number assigned by the
Distribution Center when they received the
merchandise.

Position: 0240
Group: SG5
Level: 2
Max Use: 5
document.
Dependency Notes:
Semantic Notes:
Comments:
DOC segment.
Example:
RFF+CT:78321'

Data Component
ON Order number (buyer)
[1022] Reference number assigned by the buyer to an
order.

Position: 0240
Group: SG5
Level: 2
Max Use: 5
document.
Dependency Notes:
Semantic Notes:
Comments:
DOC segment.
Example:
RFF+CT:78321'

Data Component
PQ Payment reference
Reference number assigned to a payment.
Free text to specify if it is a total or partial payment.

Position: 0240
Group: SG5
Level: 2
Max Use: 5
document.
Dependency Notes:
Semantic Notes:
Comments:
DOC segment.
Example:
RFF+CT:78321'

Data Component
SE Serial number
Identification number of an item which distinguishes this
specific item out of an number of identical items.
Government reference number.

Position: 0240
Group: SG5
Level: 2
Max Use: 2
Purpose: A segment to identify a party name and address, either by coded identification or in a
clear form, e.g; original seller or issuer of the document.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to identify the buyer or delivery party when different to the
buyer, for the current document.
Example:
NAD+BY+5456789000010::9'
Dependency Notes:
C080 - C059 - 3164 - C819 - 3251 - 3207

Data Component
BY Buyer
Party to whom merchandise and/or service is sold.
DP Delivery party
(3144) Party to which goods should be delivered, if not
identical with consignee.
EAN Description:
Party to which goods should be delivered, if not the
same as the buyer.
Notes:
EAN Description:
EAN International.
may be formatted.
Name of a party.
Name of a party.
Name of a party.
Name of a party.
Name of a party.
N C059 STREET C 1
lines.
Name of a city.
Notes:
Notes:

Notes:
Notes:

Group: AJT Segment Group 7: Adjustment details
Position: 0243
Group: Segment Group 5 (Document/message details) Conditional (Optional)
Level: 2
Max Use: 100
Purpose: A group of segments to indicate adjustment amounts and their referenced documents.
Notes: A group of segments to indicate adjustment amounts and their referenced
documents.
Segment Summary
M 0300 AJT Adjustment details M 1
0310 MOA Monetary amount C 1

Segment: AJT Adjustment details
Group: SG5-SG7
Level: 2
Usage: Mandatory
Max Use: 1
Purpose: A segment indicating any adjustments to the amounts originally specified in the
referenced document, and to which items such adjustments apply, with the associated
reason for adjustment.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to indicate the reason for an adjustment to the current
document.
Adjustments can be given for the referenced document identified in the DOC
segment and additionally, can be given per line item in the AJT segment in the
following DLI segment group.
DE 1082: If specific references or information to a line item number in a document
are required, then the line item number is given in the DLI segment and the
adjustment given in the AJT segment, both in segment group 10.
Example:
AJT+4'

Data Component
M 4465 ADJUSTMENT REASON DESCRIPTION CODE M 1 an..3
Code specifying the adjustment reason.
If adjustments are made due to national tax practices then code values to
identify these national practices may be allocated for use with this data
element by industrial EAN.UCC Member Organisations.
1 Agreed settlement
Self explanatory.
EAN Description:
Adjustment has been made as part of an agreed
settlement.
2 Below specification goods
Goods of inferior quality.
4 Short delivery
Self explanatory.
EAN Description:
Adjustment has been made to take into account
short delivery.
5 Price query
Self explanatory.
EAN Description:
Adjustment has been made to take into account a
price query.
6 Proof of delivery required
The buyer requires that proof of delivery be made before
payment.
EAN Description:
Adjustment because no proof of delivery was
available.
9 Invoice error
Invoice not in accordance with the order.
EAN Description:
Adjustment has been made to take into account
invoice error.
14 Wrong delivery
Delivery not according to specifications.
19 Trade discount
Trade discount deducted from payment.
20 Discount for late delivery
Penalty amount deducted for later delivery.
21 Advertising costs
Advertising costs deducted from payment.
26 Taxes
Taxes deducted from payment.
32 Goods not delivered
Buyer has not received the goods.
35 Goods returned
Buyer returned the goods to seller.
52 Wrong invoice
Invoice issued to wrong party.
ZZZ Mutually defined
A code assigned within a code list to be used on an
interim basis and as defined among trading partners until
a precise code can be assigned to the code list.
Refer to the RFF segment at the Adjustment Level
for code information.
N 1082 LINE ITEM IDENTIFIER C 1 an..6
To identify a line item.

Position: 0310
Group: SG5-SG7
Level: 3
Max Use: 1
Purpose: A segment giving the monetary amounts of the adjustments of each reference document
(e.g. original amount, discount amount, etc). The currency data elements should not be
used.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to indicate the value of the adjustment amount.
Adjustment amounts can be given for information purposes only, i.e., not for
calculation. The adjustment amount will not necessarily equal the difference
between the amount due and the amount remitted.
The adjustment amount will always be expressed in terms of the
remittance/payment currency.
Please note that negative adjustment must be explicily indicated by the minus (-)
sign.
Example:
MOA+5:5300'

Data Component
currency.
5 Adjusted amount
The amount specified is the adjusted amount.
Notes:
Notes:

Position: 0320
Group: SG5-SG7
Level: 3
Max Use: 1
document.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify any references associated to the adjustment amounts.
If specific references or information related to a line item number in a document are
required then this information is provided in the AJT segment group (group12)
contained in segment group 10.
Example:
RFF+PL:NOV199302'

Data Component
ALO Receiving advice number
A reference number to a receiving advice.

Position: 0320
Group: SG5-SG7
Level: 3
Max Use: 1
document.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to specify any references associated to the adjustment amounts.
If specific references or information related to a line item number in a document are
required then this information is provided in the AJT segment group (group12)
contained in segment group 10.
Example:
RFF+PL:NOV199302'

Data Component
ZZZ Mutually defined reference number
Number based on party agreement.
This is the internal Wal-Mart adjustment reason
code.
000 Tracking Entries
001 Invoice Amount
002 Tax on Invoice
010 Price Difference as Documented
039 Freight Cost on Backorder
042 Backhaul Pickup Allowance
050 Advertising Allowance
051 Promo/Display/Fixture Allowance
052 Volume Allowance
054 Warehouse Allowance
055 New Location Allowance
072 Labor/Handl-Ticket-Reticketing
075 Transfer of Debit Balances
077 Overpayment of Invoice Amounrt
080 Cash Discounts
087 Other Deduction
092 Merch Return/Overstock Recall
093 Merch Return/Damaged Merch
094 Merchandise Return/Defective
095 Merch Return/Wrong Item
100 Vendor Coupon Charge Backs
151 Purchase Rebate Allowance
201 Last Year Invoices
202 Profit Recovery Group
204 Tax on Invoice
205 Coupon Production
206 Re-issued check
207 Invoice Received
208 Withholding payment
209 Bill of Exchange Paid in Advance of its Due Date
210 Bill of Exchange Issued Manually
211 Bill of Exchange Paid on its Due Date
212 Fine
213 IRS Withholding
214 IVA Tax Withholding
215 IVA Tax Withholding
216 EFT Commission
217 Space Offered to Vendor in a Store
218 Vendor Communication Area
219 Company Anniversary Discount
220 WH Allow Supplies
221 Partial Discou nts
222 Discounts
223 IRS Withholding
224 Internal Supplies Correction
225 Bill of Exchange Withholding
226 Freight Tax Withholding
227 RTV Expenses
228 Third Party Discounts
229 Invoice with Payment Problems
230 Post Audit Discounts
231 RTV Expenses
232 Inmed Pay B
233 Inmed Purch B
234 Volume Allowance Without Debit Note
235 Utilities Payment
236 Appointment Discount
237 Pallet Wrapping Discount
238 Textile Lab
239 Direct Delivery Charge
240 No Interest Promotions

Segment: UNS Section control
Position: 0570
Group:
Level: 0
Usage: Mandatory
Max Use: 1
Purpose: A service segment placed at the start of the summary section to avoid segment collision.
Dependency Notes:
Semantic Notes:
Comments:
Notes: Remittance Advice Summary Section
This segment is used to separate the detail and summary sections of the Remittance
Advice message.
Example:
UNS+S'

Data Component
M 0081 SECTION IDENTIFICATION M 1 a1
Identification of the separation of sections of a message.

Position: 0580
Group:
Level: 1
Usage: Mandatory
Max Use: 99
Purpose: A segment giving the total amount of the payment to be made or other amounts. It is
taken as given, i.e. is not subject to recalculation. It may be used for check operations,
such as message validation.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is used to indicate the total amount being remitted in this remittance
advice.
The currency information for the remitted amount will already have been provided
in the CUX segment at heading level.
Example:
MOA+12:456250'

Data Component
currency.
12 Amount remitted
Amount which was remitted (see remittance advice).
Notes:
Notes:

Segment: UNT Message trailer
Position: 0620
Group:
Level: 0
Usage: Mandatory
Max Use: 1
Purpose: A service segment ending a message, giving the total number of segments in the message
(including the UNH & UNT) and the control reference number of the message.
Dependency Notes:
Semantic Notes:
Comments:
Notes: This segment is a mandatory UN/EDIFACT segment. It must always be the last
segment in the message.
Example:
UNT+37+ME000001'

Data Component
M 0074 NUMBER OF SEGMENTS IN A MESSAGE M 1 n..10
The number of segments in a message body, plus the message header segment
and message trailer segment.
The total number of segments in the message is detailed in here.
M 0062 MESSAGE REFERENCE NUMBER M 1 an..14
Unique message reference assigned by the sender.
The message reference numbered detailed here should equal the one
specified in the UNH segment.

Conventions used in this implementation guideline
1. Every data element on each segment is listed in the Data Element Summary section of the
segment documentation.
2. Every data element has the UN/EDIFACT data element ID noted.
3. Every data element has the UN/EDIFACT data element title noted.
4. Every data element has the UN/EDIFACT data element attributes noted:
4.1 data element requirement designation
• Mandatory (M) - This element must be used in either the segment or
composite data element in which it appears. (Mandatory data elements or
composites in EDIFACT segments retain their status in EANCOM and in
Wal-Mart guidelines.)
• Conditional (C) - This element is optional and may be included in the segment
at the option of the sender.
4.2 data element type and length
• a alphabetic characters
• n numeric characters
• an alpha numeric characters
• a3 3 alphabetic characters, fixed length
• n3 3 numeric characters, fixed length
• an3 3 alpha numeric characters, fixed length
• a..3 up to three alphabetic characters
• n..3 up to three numeric characters
• an..3 up to three alpha numeric characters
In data elements for which the Trade Data Elements Directory specifies variable
length and no other restrictions, non-significant character positions shall be
suppressed. In the case of non-significant characters, leading zeroes and trailing
spaces shall be suppressed. “Coded” data element values must be transmitted
precisely as they are shown in the code list where they appear.
For transmission purposes, all numeric data element values shall be regarded as
positive. Although conceptually a deduction is negative, it shall be represented by
a positive value. The application will interpret the meaning of the data. If a value
is to be represented as negative, it shall be immediately preceded by a minus sign,
e.g., -112. The minus sign shall not be counted when computing the maximum
field length of a data element.
The representation for a decimal sign is the point on the line (.). The decimal
point shall not be counted as a character when computing the maximum field
length of a data element. When a decimal point is transmitted, there shall be at
least one digit before and after the decimal point. For values represented by
integers only, neither decimal point nor decimal zeroes are used unless there is a
need to indicate the degree of precision.
Allowed: 0.5 and 2 and 2.0

Not Allowed: .5 and 2.

Triad separators shall not be used in an interchange. (Allowed: 2500000; Not
allowed: 2,500,000 or 2.500.000 or 2 500 000.)
DATA ELEMENT PRECISION
The following lengths may be used as a guideline:
NUMERIC CLASS FORMAT INTEGER DECIMAL

DIGIT DIGIT
Weights n..18 15 3
Cubes n..19 5 4
Quantities n..15 12 3
Unit Prices n..15 11 4
Amounts n..18 15 3
Currency Rates n..12 6 6
Percentages n..8 4 4
Tax Rates n..17 13 4
Rate Per Unit n..15 12 3
Unit Price Basis n..9 6 3
Percentage Range Value n..18 14 4
Other Range Value n..18 15 3
Control Values n..18 14 4
5. Wal-Mart utilizes AMECE implementation guidelines, which specify five status types for
data elements with a Conditional (C) EDIFACT status whether for simple, component or
composite data elements. The AMECE status is listed in the first column (to the left of
the Data Element Number Column). The five conditions are listed in the following table
along with the designation that is used in Wal-Mart implementation guides:
DESIGNATION CONDITION REQUIREMENT

M MANDATORY Indicates that the entity is required
and must be sent. NOTE:
Elements marked as “Mandatory”
by EDIFACT and “Mandatory” by
EANCOM will be marked as
“Mandatory”.
R REQUIRED Indicates that the entity is required
and must be sent. NOTE:
Elements marked as “Optional” by
EDIFACT and “Mandatory” by
AMECE will be marked as
“Required”.
A ADVISED Indicates that the entity is advised
or recommended.
D DEPENDENT Indicates that the entity must be
sent in certain conditions, as
defined by the relevant
explanatory note.
O OPTIONAL Indicates that the entity is optional

and may be sent at the discretion
of the user.
N NOT USED Indicates that the entity is not used

and should be omitted. NOTE:
An element will also be marked as
“Not Used” if AMECE allows its
use, but Wal-Mart does not use it.
6. Data elements utilized by Wal-Mart applications are noted in bold type.

7. Data elements ignored by Wal-Mart applications are noted in italicized type.
8. Every data element utilized by Wal-Mart applications has the UN/EDIFACT purpose noted.
9. Data elements which have associated codes will have the list of utilized values noted.
10. Wal-Mart comments relating to segments and data elements are noted in bold,
underlined text with a shaded background.
11. A data element marked with an asterisk (*) in the last column indicates that the listed codes
in column third are the only codes available for use with this data element, in this
segment, in this message.

Change History
Date Version Description of Changes
December 27th, 2004 0.1 Original Draft
June 15st, 2005 0.2 Update to Draft
March 15, 2006 1.0 Production Guide Released

March 27, 2006 1.1 Addition of Credit Note Business Example and other
changes.

d01 Remadv MX

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

d01 Remadv MX

Diunggah oleh

Hak Cipta:

Format Tersedia

Wal-Mart Stores, Inc.

Electronic Data Interchange Implementation Guideline

EDI Direction: From Wal-Mart

Implementation Guide Version 1.1

EAN-REMA (D.01B) 1 February 3, 2006

UN/EDIFACT Introduction to the REMADV Remittance advice message .................................. 3

REMADV - Wal-Mart Stores, Inc. Introduction ............................................................................ 5

REMADV Remittance Advice Message – Wal-Mart Guidelines .................................................. 6

Wal-Mart Business Example of an REMADV Document (Invoice Payment Usage): .................. 7

Wal-Mart Business Example of an REMADV Document (Credit Note Usage):......................... 10

Conventions used in this implementation guideline ..................................................................... 57

Change History ............................................................................................................................. 60

EAN-REMA (D.01B) 2 February 3, 2006

1.1 Functional Definition

1.2 Field of Application

- A Remittance Advice may include a cross reference to a Payment Order.

- Each Remittance Advice shall relate to only one settlement date.

- Where remittance advice relates to a dispute, the message :

- A Remittance Advice may be initiated by either party according to agreements.

3. TERMS AND DEFINITIONS

3.1 Standard terms and definitions

4.1 Data Segment Clarification

EAN-REMA (D.01B) 4 February 3, 2006

EAN-REMA (D.01B) 5 February 3, 2006

0170 Segment Group 4: CUX C 5

EAN-REMA (D.01B) 6 February 3, 2006

EDI TRANSMISSION DATA EXPLANATION

UNH+00002+REMADV:D:01B:UN:EAN005 00002 is the MESSAGE REFERENCE NUMBER

EAN-REMA (D.01B) 9 February 3, 2006

UNH+ME000001+REMADV:D:01B:UN:EAN005 00001 is the MESSAGE REFERENCE NUMBER

EAN-REMA (D.01B) 11 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 12 February 3, 2006

EAN-REMA (D.01B) 14 February 3, 2006

Data Element Summary

It is recommended that the length of document number be restricted to a

EAN-REMA (D.01B) 15 February 3, 2006

EAN-REMA (D.01B) 16 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 17 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 18 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 19 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 20 February 3, 2006

EAN-REMA (D.01B) 21 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 23 February 3, 2006

EAN-REMA (D.01B) 24 February 3, 2006

EAN-REMA (D.01B) 25 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 27 February 3, 2006

EAN-REMA (D.01B) 28 February 3, 2006

EAN-REMA (D.01B) 29 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 31 February 3, 2006

EAN-REMA (D.01B) 32 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 33 February 3, 2006

EAN-REMA (D.01B) 34 February 3, 2006

Data Element Summary

EAN-REMA (D.01B) 35 February 3, 2006