the remadv message

Transkrypt

the remadv message

THE REMADV MESSAGE EANCOM97/EDIFACT D.96A
Polska
THE REMADV MESSAGE
EANCOM97/EDIFACT D.96A
Issue 1.1, February 2009
agreed-upon by EDI Working Group of ECR Poland
The document contains only these segments and data elements that were agreed
and accepted by the members of EDI Working Group of ECR Poland Club. The
segments and data elements are used and required from commerce partners
while exchanging EDI messages.
This document is compliant to the standard REMADV EANCOM/EDIFACT
message.
February 2009, Issue 1.1
All contents copyright © Institute of Logistics and Warehousing
Page 1 of 24
Document Summary
Document Item
Current Value
Document Title
Date Last Modified
February 2009
Current Document Issue
Issue 1.1
Status
Approved
Document Description
Log of Changes in Issue 1.1
Issue No.
Date of Change
Changed By
Summary of Change
1.1
II 2009
JMD
Segment addition:
MOA+7 – charges
MOA+134 – amount after charges
Page 2 of 24
Important notices
Important: TAX SEGMENT RULE
In order to limit the redundancy of data in the documents the EDI Working Group has devised a business rule
concerning TAX segments. The rule defined that it is not correct to transmit a tax rate and exemption qualifier
in one segment.
The following examples define correct EDI segments:
TAX+7+VAT +++:::22+S'
TAX+7+VAT +++:::7+S'
TAX+7+VAT +++:::3+S'
TAX+7+VAT +++:::0+S'
TAX+7+VAT ++++E' (tax exemption)
The following are examples of incorrect segments (containing tax rate and exemption qualifier) :
TAX+7+VAT +++:::22+E'
TAX+7+VAT +++:::7+E'
TAX+7+VAT +++:::3+E'
TAX+7+VAT +++:::0+E'
Disclaimer
Whilst every effort has been made to ensure that the guidelines to use the GS1 standards contained in the
document are correct, GS1 and any other party involved in the creation of the document HEREBY STATE that
the document is provided without warranty, either expressed or implied, of accuracy or fitness for purpose, AND
HEREBY DISCLAIM any liability, direct or indirect, for damages or loss relating to the use of the document. The
document may be modified, subject to developments in technology, changes to the standards, or new legal
requirements. Several products and company names mentioned herein may be trademarks and/or registered
trademarks of their respective companies.
Page 3 of 24
Table of Contents
1.
INTRODUCTION...................................................................................................................................... 5
2.
MESSAGE STRUCTURE CHART ......................................................................................................... 6
3.
SEGMENTS LAYOUT ............................................................................................................................. 8
Page 4 of 24
1.
INTRODUCTION
REMITTANCE ADVICE MESSAGE
•
Status
MESSAGE TYPE
: REMADV
REFERENCE DIRECTORY
: D.96A
EANCOM® SUBSET VERSION : 004
•
Definition
The Remittance advice is a communication between buyer and supplier 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.
•
Principles
A Remittance Advice is a notice of 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.
The remitted amounts for the whole remittance advice, per document referenced in the
remittance advice and per line item in a document must all be expressed in the same
currency as the payment currency.
Each Remittance Advice shall relate to only one settlement date.
Page 5 of 24
2.
MESSAGE STRUCTURE CHART
Heading section
UNH
MESSAGE HEADER
BGM
BEGINNING OF MESSAGE
DTM
DATE OF THE DOCUMENT
FII
BANK ACCOUNT NUMBER (PAYER)
FII
BANK ACCOUNT NUMBER (BENEFICIARY)
SG 1 NAD
IDENTIFICATION OF THE PAYER
SG 2 NAD
IDENTIFICATION OF THE BENEFICIARY
SG 2 NAD
ADDITIONAL IDENTIFICATION OF THE BENEFICIARY (ACCORDING TO THE BUYER)
SG 3 CUX
CURRENCIES
Detail section
SG4 DOC
DOCUMENT DETAILS
SG 4 MOA
GROSS VALUE
SG 4 MOA
AGREED CHARGE
SG 4 MOA
AMOUNT AFTER CHARGES
SG 4 DTM
DATE OF THE DOCUMENT
SG 4 RFF
REFERENCE (BUYER DOCUMENT NUMBER)
Summary section
UNS
SECTION CONTROL
MOA
OVERALL VALUE
UNT
MESSAGE TRAILER
Note: The segments agreed as mandatory are written in bold.
Note: The mandatory segments that must appear either in Heading Section or in Detail
Section are written in bold italic.
Note: Underlined and bold segments are mandatory in certain business cases.
Page 6 of 24
Notes:
1.
The segments are presented in the sequence in which they appear in the message. The segment or
segment group tag is followed by the (M)andatory / (C)onditional indicator, the maximum number of
occurrences and the segment description.
2.
Reading from left to right, in column one, the data element tags and descriptions are shown, followed by in
the second column the EDIFACT status (M or C), the field format, and the picture of the data elements.
These first pieces of information constitute the original EDIFACT segment layout.
Following the EDIFACT information, EANCOM specific information is provided in the third, fourth, and fifth
columns. In the third column a status indicator for the use of (C)onditional EDIFACT data elements (see 2.1
through 2.3 below), in the fourth column the restricted indicator (see point 3 on the following page), and in
the fifth column notes and code values used for specific data elements in the message.
2.1
(M)andatory data elements in EDIFACT segments retain their status in EANCOM.
2.2
Additionally, there are five types of status for data elements with a (C)onditional EDIFACT status, whether
for simple, component or composite data elements. These are listed below and can be identified when
relevant by the following abbreviations:
-
REQUIRED
R
Indicates that the entity is required and must be sent.
-
ADVISED
A
Indicates that the entity is advised or recommended.
-
DEPENDENT
D
Indicates that the entity must be sent in certain conditions, as
defined by the relevant explanatory note.
-
OPTIONAL
O
Indicates that the entity is optional and may be sent at the
discretion of the user.
-
NOT USED
N
Indicates that the entity is not used and should be omitted.
2.3
If a composite is flagged as N, NOT USED, all data elements within that composite will have blank status
indicators assigned to them.
3.
Status indicators detailed in the fourth column which directly relate to the code values detailed in the first
column may have two values;
-
RESTRICTED
-
OPEN
*
A data element marked with an asterix (*) in the fourth column is (are)
the only codes available for use with this data element, in this segment,
in this message.
All data elements where coded representation of data is possible and a
restricted set of code values is not indicated are open (no asterix in
fourth column). The available codes are listed in the EANCOM Data
Elements and Code Sets Directory. Code values given in tables have
been agreed by the EDI Working Group. The use of other values
should be bilaterally agreed.
Page 7 of 24
3.
UNH
SEGMENTS LAYOUT
-M
Function
1:
MESSAGE HEADER
To head, identify and specify a message.
Segment number : 1
EDIFACT EAN * Description
COM
0062
Message reference number
M an..14
M
S009
MESSAGE IDENTIFIER
M
M
0065 Message type identifier
M an..6
M
* REMADV = REMITTANCE ADVICE
MESSAGE
0052 Message type version number
M an..3
M
* D = Draft directory
0054 Message type release number
M an..3
M
* 96A = Version 96A
0051 Controlling agency
M an..2
M
* UN = UN/ECE/TRADE/WP.4, United
Nations Standard Messages (UNSM)
0057 Association assigned code
C an..6
R
* EAN007 = EANCOM Version control
number.
0068
Common access reference
C an..35
N
S010
STATUS OF THE TRANSFER
C
N
0070 Sequence message transfer
number
0073 First/last sequence message
transfer indication
Sender's unique message reference.
Sequence number of messages in the
interchange. DE 0062 in UNT will have the
same value. Generated by the sender.
M n..2
Cal
Segment Notes:
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 PRICE/SALES CATALOGUE based on
the D.96A directory under the control of the United Nations.
DE 0057: Indicates that the message is the EANCOM version 005 of the UNSM PRICE/SALES CATALOGUE.
This segment is mandatory.
Example :
UNH+ME000001+REMADV:D:96A:UN:EAN004'
Page 8 of 24
BGM - M
Function
1
:
Beginning of message
To indicate the type and function of a message and to transmit the identifying
number.
Segment number : 2
COM
C002
DOCUMENT/MESSAGE NAME
C
R
1001 Document/message name, coded
C an..3
R
1131 Code list qualifier
C an..3
N
3055 Code list responsible agency,
coded
C an..3
N
1000 Document/message name
C an..35
O
1004
Document/message number
C an..35
R
1225
Message function, coded
C an..3
R
4343
Response type, coded
C an..3
N
* 481 = REMITTANCE ADVICE
9 = GS1 ( former EAN )
Message Number assigned by document
sender.
* 9 = original
Segment Notes:
This segment is used to indicate the type and function of a message and to transmit the identifying number.
DE 1004: It is recommended to limit the length of the number to 17 characters.
DE 1225: 9 = original – REMADV original transmission.
Example :
BGM+481+REM587441 +9'
Page 9 of 24
DTM
-M
Function
5:
Date/time/period
To specify date, and/or time, or period.
Segment number : 3
COM
C507
DATE/TIME/PERIOD
M
M
2005 Date/time/period qualifier
M an..3
M
2380 Date/time/period
C an..35
R
2379 Date/time/period format qualifier
C an..3
R
* 137 = Document/message date/time
102 = CCYYMMDD
718 = CCYYMMDD- CCYYMMDD
Segment Notes:
This segment is used to specify the date or period of the message.
Example :
DTM + 137 : 20030301:102'
Document date is as follows: 01.03.2003 r.
Page 10 of 24
FII
- C
Function
5:
Financial institution information
To identify an account and a related financial institution.
Segment number : 5
COM
3035
Party qualifier
M an..3
M
C078
ACCOUNT IDENTIFICATION
C
R
C an..35
R
3194 Account holder number
RB = Receiving financial institution
PB = Paying financial institution
Bank Account Number
Segment Notes.
This segment is used to indicate the payer’s and beneficiary’s bank account numbers.
Example :
FII+PB+994-3277711'
Page 11 of 24
SG1 - C
NAD - M
Function:
Segment number:
99 - NAD-SG2
1 - NAME AND ADDRESS
To specify the name/address and their related function only with DE C082 or structure
C080 to 3207.
7
EDIFACT
3035
Party qualifier
CO82
3039
PARTY IDENTIFICATION
DETAILS
Party id. identification
1131
Code list qualifier
3055
Code list responsible
agency,
coded
M
an..3
C
M
an..35
C
an..3
C
an..3
EAN
COM
M
*
DESCRIPTION
PR = payer
A
M
GS1 (former EAN )Location Number Format n13
N
R
*
9 = GS1 ( former EAN )
Segment notes:
This segment is used to identify Payer. Both parties identification is obligatory.
Element 3039: for party identification it is recommended to use GS1 codes (former EAN)
Example :
NAD+PR+5412345000013::9'
Page 12 of 24
SG1 - C
NAD - M
Function:
Segment number:
99 - NAD-SG2
C080 to 3207.
7
EDIFACT
3035
Party qualifier
CO82
3040
DETAILS
1132
Code list qualifier
3055
agency,
coded
M
an..3
C
M
an..35
C
an..3
C
an..3
EAN
COM
M
*
DESCRIPTION
BE = beneficiary
A
M
GS1 (former EAN )Location Number Format n13
N
R
*
9 = GS1 ( formerEAN )
Segment notes:
This segment is used to identify Beneficiary. Both parties identification is obligatory.
Example :
NAD+BE+5412345000013::9'
Page 13 of 24
SG1 - C
NAD - M
Function:
Segment number:
99 - NAD-SG2
C080 to 3207.
7
EDIFACT
3035
Party qualifier
CO82
3039
DETAILS
1131
Code list qualifier
3055
agency,
coded
M
an..3
C
EAN
COM
M
*
DESCRIPTION
BE = beneficiary
A
M
an..35
M
C
an..3
C
an..3
N
R
deliverer’s number in the payers
system
*
92 = Assigned by buyer or buyer's agent
Segment notes:
This segment is used to provide additional Beneficiary identification. It is used to specify the
deliverer’s number in the payers system.
Example :
NAD+BE+12345::92'
Page 14 of 24
SG7 - C
5-
CUX - DTM
CUX - M
1-
Currencies
Function
:
To specify currencies used in the transaction and relevant details for the rate of
exchange.
Segment number : 10
COM
C504 CURRENCY DETAILS
C
R
6347 Currency details qualifier
M an..3
M
6345 Currency, coded
C an..3
R
6343 Currency qualifier
C an..3
R
* 2 = Reference currency
ISO 4217 three alpha code
* 11 = Payment currency
Segment Notes:
This segment is used to specify currency information for the remittance advice.
The CUX segment is mandatory for international exchanges. It can be omitted when transaction is not
international. The code for the Polish currency is PLN according to ISO.
Example:
CUX+2:PLN:11'
Page 15 of 24
SG4– C
9999 - DOC-MOA-DTM-RFF-SG5-SG6-SG8
DOC – M
1 – Document/message details
Function:
To identify documents, either printed, electronically transferred, or referenced as
specified in message description, including, where relevant, the identification of the
type of transaction that will result from this message.
12
Segment number:
EDIFACT
M
EAN
COM
M
C an..3
D
1131 Code list qualifier
3055 Code list responsible agency,
coded
1000 Document/message name
C an..3
C an..3
N
N
C503 DOCUMENT/MESSAGE
DETAILS
1004 Document/message number
C
C002 DOCUMENT/MESSAGE
NAME
1001 Document/message name,
coded
1373 Document/message status,
coded
1366 Document/message source
3453 Language, coded
* OPIS
83 = Credit note related to financial
adjustments
84 = Debit note related to financial
adjustments
380 = Commercial invoice
381 = Credit note - goods and services
383 = Debit note - goods and services
C an..35
R
Reference number given by the issuer.
C an..3
O
5= information only
C an..35
C an..3
O
O
* ISO 639 two alpha
Segment Notes:
This segment is obligatory.
This segment is used to provide details concerning documents e.g. a group of invoices that
Remittance Advice concerns. The detail section of the REMADV message is created by
repetition of DOC segments group.
Example:
DOC+380+458011'
D attribute DE’s notes:
If remittance advice concerns a payment, that does not refer to any other previous document
or transaction the DE 1001 is not used. “Dummy” document name is stated in DE 1000 and
DE 1004 is used to provide reference number or number of “dummy” document.
Page 16 of 24
SG4– C
MOA
-M
Function
5:
Monetary amount
To specify a monetary amount.
Segment number : 13
COM
C516
MONETARY AMOUNT
M
M
5025 Monetary amount type qualifier
M an..3
M
5004 Monetary amount
C n..18
R
C an..3
D
C an..3
N
12 = Amount remitted
ISO 4217 three alpha
PLN = złoty
Segment Notes.
This segment is used to specify total gross amount with reference to the document defined in previous DOC
segment.
This segment is mandatory
Example :
MOA+12:750000:PLN'
DE with D attribute:
If DE 5025 has the value of 12 DE 6345 can be omitted if the amount of the currency is
compliant to the currency defined in CUX segment in document heading section.
For other codes the value refers to the currency of the original document. DE
6345 is then required.
Page 17 of 24
SG4– C
MOA
-M
Function
5:
Monetary amount
Segment number : 13
COM
C516
MONETARY AMOUNT
M
M
M an..3
M
C n..18
R
C an..3
D
C an..3
N
7 = Agreed charge
PLN = złoty
Segment Notes.
This segment is used to specify agreed by both parties charge amount with reference to the document defined
in previous DOC segment or resulting from it.
Example :
MOA+7:50000:PLN'
DE 6345 can be omitted if the amount of the currency is compliant to the currency defined in
CUX segment in document heading section.
Page 18 of 24
SG4– C
MOA
-M
Function
5:
Monetary amount
Segment number : 13
COM
C516
MONETARY AMOUNT
M
M
M an..3
M
C n..18
R
C an..3
D
C an..3
N
134 = Amount after charges
PLN = złoty
Segment Notes.
This segment is used to specify total amount that will be remitted with reference to the document defined in
previous DOC segment.
This segment is always used if for one DOC segment both MOA+12 and MOA+7 are used and define
values different than 0.
Example :
MOA+12:700000:PLN'
DE 6345 can be omitted if the amount of the currency is compliant to the currency defined in
CUX segment in document heading section.
Page 19 of 24
SG4– C
DTM
M
Function
5- Date/time/period
:
To specify date, and/or time, or period.
Segment number : 14
COM
C507
DATE/TIME/PERIOD
M
M
2005 Date/time/period qualifier
M an..3
M
2380 Date/time/period
C an..35
R
2379 Date/time/period format qualifier
C an..3
R
* 137 = Document/message date/time
102 = CCYYMMDD
Segment Notes:
This segment is used to specify the date of the document defined in DOC segment.
Example :
DTM + 137 : 20030301:102'
Document date is as follows: 01.03.2003 r.
Page 20 of 24
SG4– C
RFF – C
5 – Reference
Function:
Segment number:
To specify a reference.
15
EDIFACT
C506 REFERENCE
M
EAN
COM
M
1153 Reference qualifier
1154 Reference number
M an..3
C an..35
M
R
1156 Line number
C an..6
N
4000 Reference version number
C an..35
N
*
OPIS
ALK – Consignee's invoice number
Segment Notes.
This segment is used to provide references specific to the document identified in DOC
segment, e.g. Consignee's invoice number.
Example:
RFF+ALK:8306'
Page 21 of 24
UNS - M
Function
1:
SECTION CONTROL
To separate header, detail, and summary sections of a message.
Segment number : 31
COM
0081
Section identification
M a1
M
* S = Detail/summary section separation
Segment Notes.
This segment is used to separate the detail and summary sections of the message.
Example :
Page 22 of 24
MOA
-M
Function
5:
Monetary amount
Segment number : 32
COM
C516
MONETARY AMOUNT
M
M
M an..3
M
C n..18
R
C an..3
O
C an..3
O
* 12 = Amount remitted
*
Segment Notes.
This segment is used to specify total amount remitted.
This segment is mandatory
Example :
MOA+12:750000:PLN'
Page 23 of 24
UNT - M
Function
1:
MESSAGE TRAILER
To end and check the completeness of a message.
Segment number : 28
COM
0074
Number of segments in a
message
M n..6
M
The total number of segments in the
message
is detailed here.
0062
Message reference number
M an..14
M
The message reference numbered
detailed
here should equal the one specified in the
UNH segment.
Segment Notes.
This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message.
Example :
UNT+48+ME000001'
Page 24 of 24

the remadv message

Transkrypt

Podobne dokumenty

PARTY INFORMATION MESSAGE PARTIN Version 1.0 EANCOM

Untitled

sound club master

sound club hero