CORRECTING INVOICE CONFIRMATION. Message. Version 1.0 EANCOM 97/EDIFACT D.96A

Transcription

1 CORRECTING INVOICE CONFIRMATION Message Version 1.0 EAN 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland Club The document contains only those segments and data elements that were agreed upon by the members of EDI Working Group of ECR Poland Club and that will be used by them and required from trade partners while exchanging EDI messages. This document is correspondent with the EAN/EDIFACT message standard however local solutions have been implemented. January 2007

2 - 2 - I INTRODUCTION Status MESSAGE TYPE CATALOGUE :INVOIC :D.96A EAN VERSION :008 Definition The message functions as a CORRECTING INVOICE CONFIRMATION Rules The structure of this message complies with the structure of the agreed INVOICE VERSION 7.0 message. A given CORRECTING INVOICE may only refer to one INVOICE message.

3 - 3 - II. MESSAGE STRUCTURE Heading Section: UNH - message header BGM - Beginning of message DTM - message date FTX free text SG 1 RFF - number of the invoice which is corrected SG 1 DTM - date of the invoice which is corrected SG 2 NAD - identification of supplier SG 2 NAD - identification of buyer Detail Section: UNS - separator Summary section: SG 48 MOA - gross invoice amount was SG 48 MOA - gross invoice amount should be SG 48 MOA - gross invoice amount difference UNT - message trailer The segments which should always appear in a specific place in the message are written in bold. The mandatory segments that should appear either in Heading Section or in Line Item Section are written in bold italic.

4 - 4 - Notes: 1. The segments are presented in the order in which they appear in the message. Segment description consists of a tag, relevance attribute - (M)andatory / (C)onditional, the maximum number of occurrences and a description. 2. The first three columns contain the original segment description in the UN/EDIFACT standard (segment tag and name, relevance attribute, data presentation method). The fourth column and examples under the data elements description refer directly to EAN. They contain additional characteristics of conditional segments and relevance codes used in a given segment All mandatory segments in UN/EDIFACT retain their relevance status in EAN Additionally, data elements in conditional segments may have one of the five attributes listed below: REQUIRED R Indicates that the element must be sent. ADVISED A Indicates that EAN recommends the use of the element. DEPENDENT D Indicates that the element must be sent in certain conditions, as defined with the use of an additional data. OPTIONAL O Indicates that the element may or may not be sent in a message. NOT USED N Indicates that the element should be omitted If a composite data element is flagged as N, NOT USED, all its components will be omitted in the description. 3. Code values may have one of two attributes: RESTRICTED * an asterisk (*) preceding a code means that only that code may be used for specific data in a specific segment OPEN all codes in the EAN Data Elements and Code Sets Directory are available. Tables contain the codes accepted by the EDI Group. The use of other codes should be bilaterally agreed.

5 - 5 - III. DETAILED DESCRIPTION OF SEGMENTS UNH - M 1 - MESSAGE HEADER Function : To head, identify and specify a message. Segment number : Message reference number M an..14 M 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. S009 MESSAGE IDENTIFIER M M 0065 Message type identifier M an..6 M * INVOIC = Invoice 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 * EAN008 = EAN Version control number. This segment is mandatory. Example : UNH+1+INVOIC:D:96A:UN:EAN008'

6 - 6 - BGM - M 1 - Beginning of message Function : To indicate the type and function of a message and to transmit the identifying number. Segment number : 2 C002 DOCUMENT/MESSAGE NAME C R 1001 Document/message name, coded C an..3 R * 384 = CORRECTING INVOICE 1131 Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 N 1004 Document/message number C an..35 R Invoice Number assigned by document sender Message function, coded C an..3 R * 6 = confirmation Segment Notes. This segment is mandatory. Example: BGM ' This example presents the identification of a document which constitutes an original correcting invoice by the use of the 384 code. The reference number of the document is

7 - 7 - DTM - M 35 - Date/time/period Function : To specify date, and/or time, or period. Segment number : 3 C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 137 = Document/message date/time 2380 Date/time/period C an..35 R 2379 Date/time/period format qualifier C an..3 R 102 = CCYYMMDD Segment Notes. This segment is mandatory. Example : DTM+137: :102' Document date is as follows:

8 - 8 - FTX - C 10 - Free text Function : To provide free form or coded text information. Segment number : Text subject qualifier M an..3 M SUR = Suppliers reference 4453 Text function, coded C an..3 O * 1 = Text for subsequent use. The occurrence of this text does not affect message processing. C107 TEXT REFERENCE C X * 4441 Free text, coded M an..3 M 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O C108 TEXT LITERAL C X 4440 Free text M an..70 M 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 3453 Language, coded C an..3 X ISO 639 two alpha code Segment Notes: This segment is used to specify the codes and descriptions of errors that occurred in The correcting invoice message which is being confirmed with this message. 1. price 2. quantity 3. formal mistakes 4. technical mistakes Example: FTX+SUR+1++1-cena+PL'

9 - 9 - SG1 - C 99 - RFF-DTM RFF - M 1 - Reference Function : To specify a reference. Segment number : 7 C506 REFERENCE M M 1153 Reference qualifier M an..3 M IV = invoice number 1154 Reference number C an..35 R This segment is mandatory Segment notes: This segment is used to indicate the number of the invoice which is corrected by the confirmed correcting invoice. Example: RFF+IV:FAK '

10 SG1-C 10 RFF DTM DTM - C 5 - Date/time/period Function : To specify date, and/or time, or period. Segment number : 3 C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 171 = Reference date/time 2380 Date/time/period C an..35 R 2379 Date/time/period format qualifier C an..3 R 102 = CCYYMMDD Segment notes: This segment is used to indicate the date of the invoice which is being corrected. Example: DTM+171: :102'

11 SG2 - C 99 - NAD-FII-SG3-SG5 NAD - M 5 - NAME AND ADDRESS Function: To specify the name/address and their related function Segment number: 9 * DESCRIPTION 3035 Party qualifier M an..3 M SU = supplier CO82 PARTY IDENTIFICATION C A DETAILS 3039 Party id. identification M M an Code list qualifier C an..3 N 3055 Code list responsible agency, coded C058 NAME AND ADDRESS C N GS1 (former EAN) Location Number - Format n13 C an..3 R * 9 = GS1 (former EAN) (International Article Numbering Association) C080 PARTNER NAME C R 3036 Partner name M an 35 M Full or abbreviated partner name 3045 Partner name format, coded C an 3 O C059 STREET C R Street and number in a readable format 3042 Street and number M an..35 M 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3164 City C an..35 R City in a redable format 3229 Voivodship C an..9 N 3251 Postal code C an..9 R 3207 Country, coded C an..9 R Two-character code ISO3166 PL Poland Segment notes This segment is used to identify trading partners participating in the invoicing process. Identification of recipient and supplier of goods and services is obligatory in the INVOICE message. Both parties are identified by means of GS1 (former EAN) Global Location Numbers and their full or abbreviated names and addresses. This segment is mandatory. Example: NAD+SU ::9++Firma ABC::::: +ul. Baby Jagi 1::::+Poznań PL

12 SG2 - C 99 - NAD-FII-SG3-SG5 NAD - M 5 - NAME AND ADDRESS Function: To specify the name/address and their related function Segment number: 9 * DESCRIPTION 3035 Party qualifier M an..3 M BY = buyer CO82 PARTY IDENTIFICATION DETAILS 1131 Party id. identification M an Code list qualifier C an Code list responsible agency, coded C058 NAME AND ADDRESS C N C A M N GS1 (former EAN) Location Number - Format n13 C an..3 R * 9 = GS1 (former EAN) (International Article Numbering Association) C080 PARTNER NAME C R 3036 Partner name M an 35 M Full or abbreviated partner name 3045 Partner name format, coded C an 3 O C059 STREET C R Street and number in a readable format 3042 Street and number M an..35 M 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3164 City C an..35 R City in a redable format 3229 Voivodship C an..9 N 3251 Postal code C an..9 R 3207 Country, coded C an..9 R Two-character code ISO3166 PL Poland Segment notes This segment is used to identify trading partners participating in the invoicing process. Identification of recipient and supplier of goods and services is obligatory in the INVOICE message. Both parties are identified by means of GS1 (former EAN) Global Location Numbers and their full or abbreviated names and addresses. This segment is mandatory. Example: NAD+BY ::9++Firma ABC::::: +ul. Baby Jagi 1:::+Poznań PL

13 UNS - M 1 - SECTION CONTROL Function : To separate header, detail, and summary sections of a message. Segment number : Section identification M a1 M S = Detail/summary section separation Segment Notes. This segment is used to identify the break between the message detail and message trailer sections. This segment is mandatory Example : UNS+S'

14 SG48 - M MOA-SG49 MOA - M 1 - Monetary amount Function : To specify a monetary amount. Segment number : 81 C516 MONETARY AMOUNT M M 5025 Monetary amount type qualifier M an..3 M 77X = gross amount due was 77Y = gross amount due should be 77 = gross amount due (difference) 5004 Monetary amount C n..18 R Segment Notes. The first three MOA segments contain gross amounts due: was, should be and difference. The first occurrence of MOA with the qualifier 77X for DE 5025 means the total gross amount due was. The amount is the total of all amounts specified in segments SG25 MOA at a line level (in details) where DE 5025 = 9 and SG25 SG 33 MOA where DE 5025 = 369. The second occurrence of MOA with the qualifier 77Y for DE 5025 means the total gross amount due should be. The amount is the total of all amounts specified in segments SG25 MOA at a line level (in details) where DE 5025 = 66 and SG25 SG 33 MOA where DE 5025 = 124. The third occurrence of MOA with the qualifier 77 for DE 5025 means the total gross amount of the correcting invoice. The amount is the difference between the amounts specified in the previous two MOA segments. DE = DE Y DE X Example: MOA+77X:100 MOA+77Y:80 MOA+77:-20

15 UNT - M 1 - MESSAGE TRAILER Function : To end and check the completeness of a message. Segment number : Number of segments in a message M n..6 M The total number of segments in the message is detailed here 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. This segment is mandatory. Example : UNT+48+1'