Message Implementation Guideline (MIG)...Spotlight RCTI INVOIC MIG For Buyer Created Tax Invoice 1...

© eVision Pty Ltd 2012- Commercial In Confidence

Spotlight RCTI INVOIC MIG For Buyer Created Tax Invoice

1

Message Implementation

Guideline (MIG)

SPOTLIGHT Pty Ltd

RCTI INVOIC D96A

For Buyer Created Tax Invoice

Audience: Trading Vendors Version: 1.2 Status: Review Issue Date: 08.05.12 Prepared by: eVision Pty Ltd



2

CONTENTS DOCUMENT PROPERTIES.......................................................................................................... ............... 3 Copyright .................................................................................................. ...............................................3 Change History ........................................................................................................................................ 3 OVERVIEW OF EDIFACT ........................................................................................................................... 4 Introduction &Principles ......................................................................................................................... 4 UN/EDIFACT Syntax ........................................................................................................................ ......... 4 Structure of an Interchange .................................................................................................................... 5 Envelope Segment Definitions ................................................................................................................ 8 INVOIC MESSAGE SUMMARY................................................................................................................ 12 Introduction............................................................................................................................................ 12 Message segment summary................................................................................................................... 12 Message segment details ...................................................................................................................... 14 Example ........................................................................................... 45 CONTACT DETAILS ............................................................................................................ ..................... 46 eVision - MessageXchange ......................................................................................................... ............ 46 Spotlight .................................................................................................................. ............................... 46



3

DOCUMENT PROPERTIES

Copyright

This document is the property of:

Evision Pty Ltd Pty Ltd. Level 3, 488 Bourke Street, Melbourne Vic 3000 www.eVision.com.au

This Message Implementation Guide has been created for SPOTLIGHT. Unauthorized access, copying, replication and usage for a purpose other than for which this is intended is prohibited by Copyright Laws. The holder is responsible for incorporating revisions into his copy of the document and keeping the contents up-to-date. Change History

Version Date Author Nature of Amendment

1.0 08/05/2012 Manas Sardar Initial version

1.1 24/07/2013 Manas Sardar Addition of IMD and RFF segments

1.2 19/05/2015 Anders Billeschou Addition of 8E to BGM qualifiers Addition of FTX segment Addition of AAK to RFF qualifiers on line level

http://www.evision.com.au/



4



5

OVERVIEW OF EDIFACT

Introduction &Principles This specification provides the definition of the RCTI INVOICES (INVOIC) to be used in Electronic Data

Interchange (EDI) between trading partners involved in administration, commerce and transport.

This message implementation guideline (MIG) is based on the INVOIC D96A standard.

UN/EDIFACT Syntax The UN / EDIFACT syntax rules set the standards for structuring data into segments, segments into messages,

and messages into an interchange.

Structure of an Interchange

Below is a diagram of the control segments of UN/EDIFACT format.

Segments starting with “UN” are called service segments. They constitute the envelope or the “packing” of the

EDIFACT messages. User data segments contain the information itself, in a format specific to each message

type. An Interchange may consist of the following segments:

Segment ID Segment Name Status

UNA Service String Advice Conditional

UNB Interchange Header Mandatory UNG Functional Group Header Conditional



6

UNH Message Header Mandatory

User Data Segments

UNT Message Trailer Mandatory

UNE Functional Group Trailer Conditional

UNZ Interchange Trailer Mandatory



7

STRUCTURE OF A MESSAGE

Each data segment has a specific place within the sequence of segments in the message. They may occur in any

of the following three sections of the message:

Heading section - A segment occurring in this section relates to the entire message.

Detail section - A segment occurring in this section relates to the detail information only.

Summary section - Only segments containing totals or control information may occur in the summary

section, e.g. invoice total amount, number of lines in aInvoice, etc.

The same segment type may occur in more than one of the message sections, e.g. in the header and in the

detail section, and/or more than once in the same section.

Some segments may be repeated a certain number of times at their specific location in the message. The

status, Mandatory or Conditional, and the maximum number of repetitions of segment types are indicated in

the message structure.

Within a message, specific groups of functionally related segments may be repeated; these groups are referred

to as "segment groups". The maximum number of repetitions of a particular segment group at a specific

location is included in the message definition.

A segment group may be nested within other segment groups, provided that the inner segment group

terminates before any outer segment group terminates.

SEGMENT STRUCTURE

A segment consists of:

A segment tag: identifies the segment type

Data element separators

Simple, composite, or component data elements

A segment terminator

Data elements can be defined as having a fixed or variable length.

A composite data element contains two or more component data elements.

A component data element is a simple data element used in a composite data element.

A data element can be qualified by another data element, the value of which is expressed as acode that gives

specific meaning to the data. The data value of a qualifier is a code taken froman agreed set of code values.



8

SEPARATORS

In EANCOM four service characters (extracted from UNOA) have a special meaning and act as the default

separators for EANCOM;

ASCII HEX

Apostrophe ‘ 27 Segment terminator

Decimal Point

. 2E Decimal Point

Plus sign + 2B Segment tag and data element separator

Colon : 3A Component data element separator

Question mark

? 3F Release character; immediately preceding one of the service characters; it stores their normal meaning. E.g. 10?+10=20 means 10+10=20. Question mark is represented by “??”

UN / EDIFACT DOCUMENTATION CONVENTIONS

Format and Picture of Data Elements

The following conventions apply in the present documentation:

A alphabetic characters

N numeric characters

An alpha-numeric characters

a3 3alphabetic characters, fixed length

n3 3 numeric characters, fixed length

an3 3 alpha-numeric characters, fixed length

a..3 up to 3 alphabetic characters

n..3 up to 3 numeric characters

an..3 up to 3 alpha-numeric characters

The format and picture of the data elements that will be used by SPOTLIGHT in the following EDI documents

comply with the UN/EDIFACT Standards.

STATUS INDICATORS

There are five types of status used in the following pages, whether for simple, component or composite data

elements. They are listed below and can be identified when relevant by the abbreviations.

MANDATORY M/U or >> Indicates that the entity is required and must be sent.

RECOMMENDED R Indicates that the entity is advised or recommended.

CONDITIONAL C 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/U or X Indicates that the entity is not used and should be omitted.



9

Envelope Segment Definitions

Segment: UNA Service Advice String

Position: 0001

Group:

Level: 0

Usage: Optional

Max Use: 1

Purpose: To define the characters selected for use as delimiters in the rest of the interchange that follows.

Example: UNA:+.? '

Data Element Summary

Status

Indicator

Data

Element

Component

Element

Name Attributes Data

Type

M UNA1 COMPONENT DATA ELEMENT

SEPARATOR

M an..1

M UNA2 DATA ELEMENT SEPARATOR M an..1

M UNA3 DECIMAL MARK M an..1

M UNA4 RELEASE INDICATOR M an..1

M UNA5 RESERVED FOR FUTURE USE M an..1

M UNA6 SEGMENT TERMINATOR M an..1



10

Segment: UNB Interchange Header

Position: 0002 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: To start, identify and specify an interchange.. Example: UNB+UNOA:3+SUPPLIERGLN:ZZ+ 9320136000004:ZZ+20110511:1101+902201''


Status Indicator

Data Element

Component Element

Name Attributes Data Type

M S001 SYNTAX IDENTIFIER Identification of the agency controlling the syntax and indication of syntax level.

M

0001 Syntax identifier Coded identification of the agency controlling a syntax and syntax level used in an interchange. UNOA

M an..1

0002 Syntax version number Version number of the syntax identified in the syntax identifier (0001). 3

M an..1

M S002 INTERCHANGE SENDER Identification of the sender of the interchange. SUPPLIER EDI IDENTIFIER

0004 Sender Identification Name or coded representation of the sender of a data interchange. ZZ

M an..1

0007 Partner Identification Code Qualifier referring to the source of codes for the identifiers of interchanging partners.

M an..4



11

M S003 INTERCHANGE RECICIPIENT Identification of the recipient of the interchange. Spotlight EDI GLN

0010 Recipient Identification Name or coded representation of the recipient of a data interchange. ZZ

M an..35

0007 Partner Identification Code Qualifier Qualifier referring to the source of codes for the Identifiers of interchanging partners.

M an..35

M S004 DATE/TIME OF PREPARATION Date/time of preparation of the interchange.

0017 Date Of Preparation Local date when an interchange or a functional group was prepared. YYMMDD

M an..35

0019 Time of preparation Local time of day when an interchange or a functional group was prepared. HHMM

M an..4

M 0020 INTERCHANGE CONTROL REFERENCE Unique reference assigned by the sender to an interchange.

M an..14

C 0035 TEST INDICATOR 1 indicates test Message, blank indicates production message.

C an..1



12

Segment: UNZ Interchange Trailer

Position: 2160 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: This is the last segment in the interchange Example: UNZ+1+001000062’


Status Indicator

Data Element

Component Element

Name Attributes Data Type

M 0036 INTERCHANGE CONTROL COUNT Total number of messages in this interchange.

M n..6

M 0020 INTERCHANGE CONTROL REFERENCE Unique message reference assigned by the sender. The message reference number detailed here should equal the one specified in the UNB segment.

M an..14



13

INVOIC MESSAGE SUMMARY Introduction This INVOIC message will be used by Spotlight to send Buyer Created Tax Invoices to Vendors.

Message segment summary Interchange Header:

Seg ID Name Req Des Max Use Group Repeat

C UNA Service String Advice M 1

M UNB Interchange Header M 1

Heading Section:

Seg ID Name Req Des

Max Use Group Repeat

M UNH Message Header M 1 M BGM Beginning of Message M 1 M DTM Date/Time/Period M 35 M NAD Name and Address M 1 Segment Group: Reference C 10 M RFF Reference M 1 Segment Group: Information C 5

M CUX Currencies M 1 Segment Group: TDT C 99

M PAT Payment Term Basis R 1

M DTM Payment Terms Period date

Detail Section:

Seg ID Name Req Des Max Use Group Repeat

M LIN Line Item M 1 C PIA Additional Product Id C 25 C IMD Item Description C 99 C QTY Quantity M 10



14

Segment Group: Monetary Details

M 25 M MOA Monetary Amount M 1 M PRI Price Details M 1 M RFF Reference Information M 1 R TAX Tax Invoice R 1 R MOA Monetary Amount R 1 Section Control:

Seg ID Name Req Des Max Use Group Repeat M UNS Section Control M 1

Summary Section:

Seg ID Name Req Des Max Use Group Repeat M CNT Control Total M 1 M MOA Monetary Amount M 1 R TAX Tax Invoice R 1 R MOA Monetary Amount R 1 M UNT Message Trailer M 1

Interchange Trailer:

Seg ID Name Req Des Max Use Group Repeat M UNZ Interchange Trailer M 1

General 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 Segment Description, the Base Status (M)andatory / (C)onditional indicator, the User Status, and the maximum number of occurrences. 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.



15

Segment: UNH Message Header

Position: 0010 Group: Level: 1 Usage: Mandatory Max Use: 1 Purpose: A service segment starting and uniquely identifying a message. The message type code for the INVOIC message is INVOIC. Example: UNH+22467640+INVOIC:D:96A:UN:EAN008' Data Element Summary

Data Element

Component Element

Name Attributes

M 0062

MESSAGE REFERENCE NUMBER Unique message reference assigned by the sender. Sender’s unique message reference. Sequence number of the messages in the interchange. DE 0062 in the UNT will be exactly the same. Sender generated.

M an..14

M S009

MESSAGE IDENTIFIER Identification of the type, version etc. of the message being interchanged.

M an..6

M 0065

Message type identifier Code identifying a type of message and assigned by its controlling agency. INVOIC M an..6

M 0052 Message type version number D M an..3

M 0054 Message type release number 96A M an..3

M 0051 Controlling agency UN M an..2

M 0057 Association assigned code EAN008 M an..6



16

Segment: BGM Beginning of Message

Position: 0020 Group: Level: 1 Usage: Mandatory Max Use: 1 Purpose: To indicate the type and function of a message and to transmit the identifying number. Example: BGM+389+8000245548+9'


Data Element

Component Element

Name Attributes

M/U C002

DOCUMENT/MESSAGE Identification of a type of document/message by code or name. Code preferred.

M/U 1001

Document/message name, coded Document/message identifier expressed in code. 389 – Self-billed invoice 8E – Self-billed credit note (EAN code)

C an..3

M/U 1004

DOCUMENT/MESSAGE NUMBER Unique document record ID C an..35

Spotlight Invoice Number

M/U 1225

MESSAGE FUNCTION, CODED Code indicating the function of the message. 9 – new

C an..3



17

Segment: DTM Date/Time/Period

Position: 0030 Group: Level: 1 Usage: Mandatory (Optional) Max Use: 9 Purpose: A segment specifying general dates and, when relevant, times related to the whole message. Example: DTM+137:20120804:102' - Document issue date time DTM+50:20120808:102' - Delivery date/time requested


Data Element

Component Element

Name Attributes

M C507

DATE/TIME/PERIOD Date and/or time, or period relevant to the specified date/time/period type

M

M 2005

Date/time/period qualifier

M an..3 137 – Document issue date/time 50 – Goods receipt date/time

M 2380

Date/time/period The value of a date, a date and time, a time or of a period in a specified

M an..35

M 2379

Date/time/period format qualifier Specification of the representation of a date, a date and time or of a period. 102 - CCYYMMDD

M an..3



18

Segment: IMD Item Description

Position: 0060 Group: Level: 1 Usage: Conditional (Optional) Max Use: 1

Purpose: A segment to describe an item in either an industry or free format.

Comments:

Examples: IMD+F++::: PRODUCT RECALL'


Data

Element Component

Element Name Attributes

C 7077 Item description type, coded Code indicating the format of a description. F – Freeform C - Code

C 7081 ITEM CHARACTERISTIC, CODED 8 – Product

Goods Description

C C273 ITEM DESCRIPTION Description of an item.

C 7009 Item description identification

C an..3 C an..3 C

C an..17

C 1131 Code list qualifier C an..3

C 3055 Code list responsible agency, coded C an..3 C 7008 Item description

C 7008 Item description

C an..35

C an..35



19

Segment: FTX Free Text

Position: 0070 Group: Level: 1 Usage: Conditional (Optional) Max Use: 10

Purpose: A segment to provide free form or coded text information.

Example: FTX+PMT+1++GST shown is payable by Supplier'


Data Element

Component Element

Name Attributes

M 4451 TEXT SUBJECT QUALIFIER PMT – Payment information

M an..3

M 4453 TEXT FUNCTION, CODED 1 – Text for subsequent use

C an..3

X C1007 TEXT REFERENCE

C

X 4441 Free text, coded M an..3

X 1131 Code list qualifier C an..3

X 3055 Code list responsible agency, coded C an..3

M C108 TEXT LITERAL C

M 4440 Free text M an..70

C 4440 Free text C an..70




X 3453 LANGUAGE, CODED C an..3



20

Group: NAD Segment Group 2: Name and Address

Position: 0110 Group: 2 Level: 1 Usage: Conditional (Optional) Max Use: 99 Purpose: A group of segments identifying the parties with associated information.

Segment Summary

Pos No Seg ID Name Req Des Max Use Group Repeat

M 0120 NAD Name and Address M 1

C 0150 RFF Reference Group C 1

C 0210 CTA Contact Information C 1

C 0280 CUR Currencies Group C 1



21

Segment: NAD Name and Address

Position: 0120 (Trigger Segment) Group: Segment Group 2 (Name and Address) Conditional (Optional) Level: 1 Usage: Mandatory Max Use: 1 Purpose: A segment identifying names and addresses of the parties (ship to and supplier information). Example: NAD+ST+S113++SPL LAVERTON DC+217 BOUNDARY RD+LAVERTON+VIC+3026+AU' NAD+SU+210676::92++ L3 488 Bourke Street+Melbourne+VIC+3000+ CN'


Data Element

Component Element

Name Attributes

M 3035

PARTY QUALIFIER Code giving specific meaning to a party.

M an..3 BY – Buyer ST – Ship To Party SU – Supplier

M C082 PARTY IDENTIFICATION DETAILS Identification of a transaction party by code. C

M 3039

Party id, identification Code identifying a party involved in a transaction. SAP Vendor Code

M an..35

N/U 1131 Code list qualifier Identification of a code list. C an..3

M C080 PARTY NAME Identification of a transaction party by name. C

M 3036 Party name Name of party M an..35

M C059 STREET Street Address: one to four lines C

M 3042

Street and number/p.o. box Street and number in plain language, or Post Office Box No.

M an..35



22

O 3042


M an..35

O 3042


M an..35

O 3042


M an..35

R 3164 CITY NAME C an..35

R 3229

COUNTRY SUB-ENTITY IDENTIFICATION

C an..9

R 3251 POSTAL IDENTIFICATION C an..17

R 3207 COUNTRY, CODED C an..3



23

Segment: RFF Segment Group 3: Reference

Position: 0070 Group: 3 Level: 2 Usage: Conditional (Optional) Max Use: 999 Purpose: A group of segments containing a reference and constants which apply to the entire message. Segment Summary


M 0080 RFF Reference M 999



24

Segment: RFF Reference

Position: 0080 Group: Segment Group 1 (Reference) Conditional (Optional) Level: 1 Usage: Mandatory Max Use: 1 Purpose: Contains a reference to the INVOIC. Example: RFF+AMT: 73076521161 RFF+ZZZ: 1234


Data Element

Component Element

Name Attributes

M C506 REFERENCE Identification of a reference M

M 1153

Reference qualifier Code giving specific meaning to a reference segment or a reference number. AMT-Goods and Services Tax identification

number

ZZZ- Retail authority claim number

ZZ

M an..3

M/U 1154

Reference number Purchase order number ABN of the organization in the corresponding

NAD segment. C an..35



25

Group: CUX Segment Group 7: Currencies

Position: 0280 Group: Segment Group 7 (Currencies) Level: 1 Usage: Conditional (Optional) Max Use: 10 Purpose: To specify currencies used in the transaction and relevant details for the rate of exchange.

Segment Summary


M 0290 CUX Currencies M 1



26

Segment: CUX Currencies

Position: 0290 (Trigger Segment) Group: Segment Group 7 (Currencies) Conditional (Optional) Level: 1 Usage: Mandatory Max Use: 1 Purpose: To specify currencies used in the transaction and relevant details for the rate of exchange. Example: CUX+2:AUD:4'


Data Element

Component Element

Name Attributes

C C504 CURRENCY DETAILS

The usage to which a currency relates. C

M

6347 Currency details qualifier Specification of the usage to which the currency relates.

M an..3

C

6345 Currency, coded Identification of the name or symbol of the monetary unit involved in the transaction.

C an..3

C 6343

Currency type code qualifier

4 - Invoicing currency C

an..3



27

Group: PAT Segment Group 8: Payment terms basis

Position: 0310 Group: Segment Group 8 (Payment terms basis) Level: 1 Usage: Conditional (Optional) Max Use: 10 Purpose: To specify currencies used in the transaction and relevant details for the rate of exchange.

Segment Summary


M 0320 PAT Payment terms basis M 1



28

Segment: PAT Payment terms basis

Position: 0320

Group: Segment Group 8 (Payment terms basis)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: To specify currencies used in the transaction and relevant details for the rate of exchange.

Example: PAT+ZZZ++66:3:D:45'


Data

Element Component


M 4279 Payment terms type qualifier

Code qualifying the type of payment terms. ZZZ- Mutually defined

M an..3

X C110 PAYMENT TERMS

Terms of payment code from a specified source.

C

X

4277 Terms of payment identification Identification of the terms of payment between the parties to a transaction (generic term).

C

an..17

X 1131 Code list qualifier

Code identifying a code list.

C an..3

X 3055 Code list responsible agency, coded

Code specifying the agency responsible for a code list.

C an..3

X

4276 Terms of payment Free form description of the conditions of payment between the parties to a transaction.

C

an..35

X 4276 Terms of payment

Free form description of the conditions of payment between the parties to a transaction.

C an..35



29

R C112 TERMS/TIME INFORMATION C

M 2475 Time reference code

Reference date as specified.

66-Specified date

M

R 2009

Terms time relation code

Payment terms related to time after reference date.

3-After reference

C an..3

R 2151

Period type code

Self-explanatory.

D-Day

C an..3

R 2152 Period count quantity

Number of periods for payment. C n..3



30

Segment: DTM Date/Time/Period

Position: 0330 Group: Level: 1 Usage: Mandatory (Optional) Max Use: 9 Purpose: A segment specifying general dates and, when relevant, times related to the whole message. Example: DTM+7:20120804:102' - Effective date


Data Element

Component Element

Name Attributes

M C507

DATE/TIME/PERIOD Date and/or time, or period relevant to the specified date/time/period type

M

M 2005

Date/time/period qualifier M an..3 7 Effective date/time

M 2380

Date/time/period The value of a date, a date and time, a time or of a period in a specified

M an..35

M 2379

Date/time/period format qualifier Specification of the representation of a date, a date and time or of a period. 102 - CCYYMMDD

M an..3



31

Group: LIN Segment Group 25: Line Item

Position: 0890 Group: Segment Group 28 (Line Item) Level: 1 Usage: Conditional (Optional) Max Use: 200000

Purpose: A group of segments providing details of the individual invoiced items.

Segment Summary

Pos No Seg ID Name Req Des Max Use Group

Repeat M 0900 LIN Line Item M 1

C 0910 PIA Additional Product Id C 25

C 0920 IMD Item Description C 99

C 0930 QTY Quantity C 10



32

Segment: LIN Line Item

Position: 0900 (Trigger Segment)

Group: Segment Group 28 (Line Item) Conditional(Optional)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the line item by the line number and configuration level, and

additionally, identifying the product or service invoiced. Other product identification numbers e.g. Buyer

product number, etc. can be specified within the following PIA segment.

Comments:

Notes: This segment is used to identify the item being invoiced.

The detail section of the Invoice is formed by a repeating group of segments, always starting with the LIN segment.

Example:

LIN+00100++9310001002226:EN


Data

Element

Component

Element

Name Attributes

M/U 1082 LINE ITEM NUMBER

Serial number designating each separate item

within a series of articles.

Application generated number of the count

of the invoice lines.

C n..6

D C212 ITEM NUMBER IDENTIFICATION

Goods identification for a specified source.

C

M/U 7140 Item number

Item Number EAN-13, EAN-8 or UPC-A

C an..35

M/U 7143 Item number type, coded

EN – EAN Number

C an..3



33

Segment: PIA Additional Product Id

Position: 0910 Group: Segment Group 6 (Good Item details) Conditional (Mandatory) Level: 1 Usage: Conditional Max Use: 25 Purpose: A segment providing identification codes for the item contained in the Goods Item. Example: PIA+5+000000000080000049:IN


Data Element

Component Element

Name Attributes

M 4347 PRODUCT ID. FUNCTION QUALIFIER 5 - Product identification

M an..3

C C212 ITEM NUMBER IDENTIFICATION Goods identification for a specified source.

M

M/U 7140 Item number A number allocated to a group or item.

M an..35

M/U 7143 Item number type, coded Identification of the type of item number. IN –Item Number Code SA-Supplier's article number

M an..3



34

Segment: IMD Item Description

Position: 0920 Group: Segment Group 6 (Good Item details) Conditional (Mandatory) Level: 1 Usage: Conditional (Optional) Max Use: 10

Purpose: A segment to describe an item in either an industry or free format.

Comments:

Examples: IMD+F++::: BALLERINA POPLIN, WANDS, 112CM'


Data

Element Component


C 7077 Item description type, coded Code indicating the format of a description. F – Freeform C - Code

C 7081 ITEM CHARACTERISTIC, CODED 8 – Product

Goods Description

C C273 ITEM DESCRIPTION Description of an item.

C 7009 Item description identification

C an..3 C an..3 C

C an..17

C 1131 Code list qualifier C an..3

C 3055 Code list responsible agency, coded C an..3 C 7008 Item description

C 7008 Item description

C an..35

C an..35



35

Segment: QTY Quantity

Position: 0940 Group: Segment Group 28 (Line Item) Conditional (Optional) Level: 2 Usage: Conditional (Optional) Max Use: 10 Purpose: A segment identifying the product quantities e.g. invoiced quantity. Example: QTY+21:10:MTR'


Data Element

Component Element

Name Attributes

M C186 QUANTITY DETAILS Quantity information in a transaction, qualified when relevant.

M

M 6063 Quantity qualifier Code giving specific meaning to a quantity. 21 – Total Line item Quantity.

M an..3

M 6060 Quantity Numeric value of a quantity. Total Quantity Of LIN Item

M n..15

C 6411 Measure unit Qualifier C an..3



36

Group: MOA Monetary amount

Segment Group 26: Monetary amount Position: 1040 Group: Segment Group 32 (Price Details) Level: 2 Usage: Conditional (Optional) Max Use: 25 Purpose: A group of segments identifying the relevant pricing information for the goods or services invoiced.

Segment Summary


M 1190 MOA Monetary amount M 1



37

Segment: MOA Monetary Amount

Position: 1040 (Trigger Segment) Group: Segment Group 26 (Monetary amount) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 1 (for each LIN segment) Purpose: A segment to specify the price type and amount. The price used in the calculation of the line amount will be identified as 'price'. Example: MOA+66:1654.20' Net Line Item Amount Data Element Summary

Data Element

Component Element

Name Attributes

M/U C516 Monetary Amount Specification of monetary amounts relating to the products.

C

M 5025 Monetary amount type code qualifier Net price x quantity for the line item. 66 – Goods Item Total

M an..3

M/U 5118 Monetary amount Net line item amount excluding GST.

M n..15



38

Group: PRI Price Details

Position: 1120 Group: Segment Group 28 (Price Details) Level: 2 Usage: Conditional (Optional) Max Use: 25 Purpose: A group of segments identifying the relevant pricing information for the goods or services invoiced.

Segment Summary


M 1120 PRI Price Details M 1



39

Segment: PRI Price Details

Position: 1120 (Trigger Segment) Group: Segment Group 28 (Price Details) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 2 (for each LIN segment) Purpose: A segment to specify the price type and amount. The price used in the calculation of the line amount will be identified as 'price'. Example: PRI+AAA:16.25:::12:EA Wholesale Price per 12 consumer unit is $16.25 Data Element Summary

Data Element

Component Element

Name Attributes

M/U C509 PRICE INFORMATION Identification of price type, price and related details.

C

M 5125 Price qualifier Identification of a type of price. AAA - Wholesale Price Excluding GST

M an..3

M/U 5118 Price The monetary value associated with a purchase or sale of an article, product or service.

M n..15

D 5284 Unit price basis Basis on which the unit price/rate applies. Blank assumes 1.

C n..9

D 6411 Measure unit qualifier Indication of the unit of measurement in which weight (mass), capacity, length, area, volume or other quantity is expressed.

M An..3



40

Segment: RFF Segment Group 29: Reference

Position: 1170 Group: 3 Level: 2 Usage: Conditional (Optional) Max Use: 999 Purpose: A group of segments containing a reference and constants which apply to the entire message. Segment Summary


M 1170 RFF Reference M 999



41

Segment: RFF Reference

Position: 1170 Group: Segment Group 1 (Reference) Conditional (Optional) Level: 1 Usage: Mandatory Max Use: 1 Purpose: Contains a reference to the purchase order. Example: RFF+ON: 4500002731


Data Element

Component Element

Name Attributes

M C506 REFERENCE Identification of a reference M

M 1153

Reference qualifier Code giving specific meaning to a reference segment or a reference number. ON-Order number

AAK – Despatch advice number

M an..3

M/U 1154

Reference number Purchase order number Document Reference Number. C an..35



42



43

Group: TAX Segment Group 33: Duty/tax/fee details

Position: 1320 Group: Segment Group 25 (Line item) Conditional (Optional) Level: 2 Usage: Conditional (Required) Max Use: 99 Purpose: A group of segments specifying tax related information for the line item, and when necessary, the location(s) to which that tax information relates.


M 1320 TAX Tax details M 1

O 1330 MOA Monetary amount

C 1



44

Segment: TAX Duty/tax/fee details

Position: 1320 (Trigger Segment) Group: Segment Group 33 (DUTY/TAX/FEE DETAILS) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 2 (for each LIN segment) Purpose: To specify relevant duty/tax/fee information. Example: TAX+7+GST+++:::10+S' Data Element Summary

Data Element

Component Element

Name Attributes

M 5283 DUTY OR TAX OR FEE FUNCTION CODE QUALIFIER 7-Tax Contribution levied by an authority.

C an..3

M C241 Duty/Tax/Fee Type

M

M/U 5153 Duty or tax or fee type name code GST - Goods and services tax Tax levied on the final consumption of goods and services

M n..15

R C243 DUTY/TAX/FEE DETAIL C

R 5278 Duty or tax or fee rate

The actual rate of GST.

M an..17

R 5305 DUTY OR TAX OR FEE CATEGORY CODE S-Standard rate

Code specifying the standard rate.

C an..3



45


Position: 1330 (Trigger Segment) Group: Segment Group 33 (Monetary amount) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 1 (for each LIN segment) Purpose: A segment to specify the price type and amount. The price used in the calculation of the line amount will be identified as 'price'. Example: MOA+124:165.42' Line Tax Item Amount Data Element Summary

Data Element

Component Element

Name Attributes


C

M 5025 Monetary amount type code qualifier Tax amount for the line item. 124 – Tax amount

M an..3

M/U 5118 Monetary amount The actual amount of GST for the current line item.

M n..15



46

Segment: UNS Section Control

Position: 1790 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: A service segment placed at the start of the summary section to avoid segment collision. Comments: Notes: This segment is used to separate the detail and summary sections of the INVOIC message. Example: UNS+S'


Data Element

Component Element

Name Attributes

M 0081 SECTION IDENTIFIER A character identifying the next section in a message.

M a1



47

Segment: CNT Control Total

Position: 1800 Group: Level: 1 Usage: Mandatory Max Use: 1 Purpose: A segment by which control totals may be provided by the sender for checking by the receiver. Comments: Notes: This segment is used to provide message control totals. Example: CNT+2:4' There are four LIN segments in the current message.


Data Element

Component Element

Name Attributes

M C270 CONTROL Control total for checking integrity of a message or part of a message.

M

M 6069 Control total type code qualifier Determines the source data elements in the message which forms the basis for 6066 Control value. 2 -Total Number of LIN Segments In This Message

M an..3

M 6066 Control value Control Aount Actual LIN Segment Count

M n..18



48

Group: MOA Monetary amount

Segment Group 48: Monetary amount Position: 1810 Group: Segment Group 48 (Monetary Amount) Level: 2 Usage: Conditional (Optional) Max Use: 25 Purpose: A group of segments identifying the relevant pricing information for the goods or services.

Segment Summary


M 1820 MOA Monetary amount M 1



49


Position: 1820 (Trigger Segment) Group: Segment Group 48 (Monetary amount) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 1 Purpose: A segment to specify the price type and amount. The price used in the calculation of the line amount will be identified as 'price'. Example: MOA+128:1832.60' Total Invoice Amount Excluding GST Data Element Summary

Data Element

Component Element

Name Attributes


C

M 5025 Monetary amount type code qualifier Net price x quantity for the line item. 128 –Total Invoice Amount Excluding GST

M an..3

M/U 5118 Monetary amount Total Invoice amount excluding GST.

M n..15



50

Group: TAX Segment Group 50: Duty/tax/fee details

Position: 1860 Group: Segment Group 50 (Line item) Conditional (Optional) Level: 2 Usage: Conditional (Required) Max Use: 99 Purpose: A group of segments specifying tax related information for the line item, and when necessary, the location(s) to which that tax information relates.


M 1870 TAX Tax details M 1

O 1880 MOA Monetary amount

C 1



51

Segment: TAX Duty/tax/fee details

Position: 1870 (Trigger Segment) Group: Segment Group 50 (DUTY/TAX/FEE DETAILS) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 2 (for each LIN segment) Purpose: To specify relevant duty/tax/fee information. Example: TAX+7+GST+++:::10+S' GST applied with the rate of 10% . Data Element Summary

Data Element

Component Element

Name Attributes

M 5283 DUTY OR TAX OR FEE FUNCTION CODE QUALIFIER 7-Tax Contribution levied by an authority.

C an..3

M C241 Duty/Tax/Fee Type

M

M/U 5153 Duty or tax or fee type name code GST - Goods and services tax Tax levied on the final consumption of goods and services

M n..15

R C243 DUTY/TAX/FEE DETAIL C

R 5278 Duty or tax or fee rate

The actual rate of GST.

M an..17

R 5305 DUTY OR TAX OR FEE CATEGORY CODE S-Standard rate

Code specifying the standard rate.

C an..3



52


Position: 1880 (Trigger Segment) Group: Segment Group 50 (Monetary amount) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 1 (for each LIN segment) Purpose: A segment to specify the price type and amount. The price used in the calculation of the line amount will be identified as 'price'. Example: MOA+124:165.42' Total Invoice Tax Amount Data Element Summary

Data Element

Component Element

Name Attributes


C

M 5025 Monetary amount type code qualifier Tax Amount for the invoice. 124 –Total Invoice Tax amount

M an..3

M/U 5118 Monetary amount The actual amount of GST for the invoice.

M n..15



53

Segment: UNT Message Trailer

Position: 0230 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: A service segment ending a message, giving the total number of segments in the message and the control reference number of the message. Comments: Notes: The UNT segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message. Example: UNT+48+ME00001' Data Element Summary

Data Element

Component Element

Name Attributes

M 0074 NUMBER OF SEGMENTS IN A MESSAGE Control count of number of segments in a message.

M n..6

M 0062 MESSAGE REFERENCE NUMBER Unique message reference assigned by the sender. The message reference number detailed here should equal the one specified in the UNH segment.

M an..14



54

Segment: UNZ Interchange Trailer

Position: 0240 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: This is the last segment in the interchange. Example: UNZ+1+00100002’


Data Element

Component Element

Name Attributes

M 0036 INTERCHANGE CONTROL COUNT Total number of messages in this interchange.

M n..6

M 0020 INTERCHANGE CONTROL REFERENCE Unique message reference assigned by the sender. The message reference number detailed here should equal the one specified in the UNB segment.

M an..14



55

Example INVOIC For Buyer Created Tax Invoice

UNA:+. ? ' UNB+UNOA:3+9320136000004:ZZ+99941546993':ZZ+110922:1351+41546993' UNH+41546993+INVOIC:D:96A:UN:EAN008' BGM+389+8000245548+9' DTM+137:20120422:102' DTM+50:20120425:102' IMD+F++::: PRODUCT RECALL’ NAD+ST+S113++SPL LAVERTON DC+217 BOUNDARY RD+LAVERTON+VIC+3026+AU' NAD+SU+210676::92++ L3 488 Bourke Street+Melbourne+VIC+3000+ CN' RFF+AMT: 73076521161' RFF+ZZZ: 1234' CUX+2:AUD' PAT+ZZZ++66:3:D:45' DTM+7:20120804:102' LIN+1++9334571207409:EN' PIA+5+000000000080000049:IN' IMD+F++::: BALLERINA POPLIN, WANDS, 112CM' QTY+21:10:MTR' MOA+66:1654.20' PRI+AAA:16.25:::12:EA RFF+ON: 4500002731' TAX+7+GST+++:::10+S' MOA+124:165.42' UNS+S' CNT+2:4' MOA+128:1832.60' TAX+7+GST+++:::10+S' MOA+124:165.42' UNT+44+41546993' UNZ+1+41546993'



56

CONTACT DETAILS eVision - MessageXchange 3/488 Bourke Street Melbourne, VIC Australia, 3000 P: +613 8622 0200 E:[email protected] Technical support P: 1300769414 E: [email protected] Spotlight Marie Fernandez [email protected] Spotlight Pty Ltd Level 6, 111 Cecil Street, South Melbourne 3205

mailto:E:[email protected]

mailto:[email protected]

mailto:[email protected]

Message Implementation Guideline (MIG)...Spotlight RCTI INVOIC MIG For Buyer Created Tax Invoice 1...

Documents

Transcript of Message Implementation Guideline (MIG)...Spotlight RCTI INVOIC MIG For Buyer Created Tax Invoice 1...