B2B Business Document Definition Implementation Guide

B2B Business Document Definition Implementation Guide Invoice M&S Franchises (EANCOM INVOIC) Version 1.1, 7 th June 2011 Copyright: M&S plc 2007. Neither the whole nor any part of this Document may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photo-copying or otherwise, without the prior written permission of M&S plc

CONTENTS CONTENTS... 2 1 INTRODUCTION... 3 1.1 DOCUMENT PURPOSE & USE... 3 1.2 EDI COMMUNICATION & TRANSMISSION... 3 1.3 M&S EDI BUSINESS DOCUMENT DEFINITION... 3 1.4 EANCOM STANDARD... 4 1.5 MESSAGE FLOWS... 4 1.5.1 Franchise Trading Partner... 4 1.6 INTERFACE DEFINITIONS... 4 1.7 ASSURING YOUR IMPLEMENTATION... 5 1.8 M&S ELECTRONIC TRADING SOLUTION SUPPORT... 5 2 MESSAGE DEFINITION... 6 2.1 MESSAGE DATA FLOW SUMMARY... 6 2.2 MESSAGE USE-CASES... 6 2.3 MESSAGE SPECIFICATION REFERENCE GUIDE... 6 2.3.1 Invoice - INVOIC... 6 2.4 MESSAGE DEFINITION SUMMARY... 7 2.5 MESSAGE DEFINITION GUIDE - INVOIC... 7 2.5.1 EANCOM Interchange Header... 7 2.5.2 EANCOM Business Document Definition... 8 2.5.3 EANCOM Interchange Trailer... 16 2.5.4 SG6-TAX-MOA... 18 2.5.5 SG6-TAX-MOA / SG34-TAX-MOA Tax Rates & Tax Codes... 19 2.5.6 Tax Rates... 19 2.5.7 Mixed Rate VAT... 19 3 COMPLIANCE TESTING... 20 3.1 TEST CASES... 20 3.1.1 INVOICE_INVOIC_001... 20 4 UNDERSTANDING EDIFACT / EANCOM... 21 4.1 WHAT IS EDIFACT?... 21 4.2 EANCOM MESSAGE STRUCTURE... 21 4.2.1 s and Groups... 21 4.3 EXAMPLE EANCOM MESSAGE... 23 4.3.1 Invoice Example 1... 23 5 VERSION CONTROL... 25 M&S plc 2007 Page 2 of 25

1 INTRODUCTION 1.1 Document Purpose & Use For the implementation of the M&S EDI business documents (messages) we have provided an Implementation Guide to help you through your adoption of the M&S B2B EDI solution. Provided for you is the Implementation Guide itself detailing the EDI messages and the business context and the circumstances in which they will be passed between yourself and M&S. Also provided for you is the EDI Business Document Definition; this definition specifies the structure and content of the EDI message that M&S will exchange with you. At M&S we have adopted an Industry compliant EDI data standard to ensure ease of adoption for our Trading Partners. The standard adopted is EANCOM; it is an EDIFACT compliant data standard, and forms the basis of our Business Document Definitions. In addition we have provided a Testing Compliance Specification, along with example testing files to ensure that your implementation is successful and compliant with what M&S will expect to exchange with you. Together this information, the Implementation Guide, the Business Document Definition, and the Testing Compliance specification, will provide you with all the information you need to successfully and smoothly transition onto the M&S B2B EDI solution. 1.2 EDI Communication & Transmission The M&S B2B EDI solution will enable M&S and you as a Trading Partner of ours to implement a fully automated, end-to-end B2B EDI solution. This solution is supported for trading partners who have an existing EDI solution, or, who are transitioning to an EDI solution, and can send and receive the EDI messages into their business systems. We have partnered with GXS to provide a leading-class B2B solution that enables us to seamlessly exchange business documents with you. The following diagram provides a high-level summary to this solution: 1.3 M&S EDI Business Document Definition M&S have adopted the EDIFACT compliant EANCOM standard for its B2B EDI messages; all EDI messages sent and received must be end with this data standard as detailed in section EDI Business Document Definition. Each of the specified Business Documents (or EDI messages) is defined by the Business Document Definitions, and forms the data contract between M&S and you our Trading Partner as defined within this document. The Business Document Definition provides you with the following information: The EANCOM data object to be utilised for each Business Document The EANCOM message segments and elements within those to be transmitted as part of any data exchange Implementation rules for each of the segments and elements The business definition of each element to be used M&S plc 2007 Page 3 of 25

The elements that are mandatory and those which are optional i.e. may NOT be passed The format of the data to be passed for each element As part of your transition process onto the M&S B2B solution, GXS, our partner for this solution will assist you with any queries you may have regarding this implementation guide and Business Document Definition itself, or your implementation of those definitions.. 1.4 EANCOM Standard M&S specify that for EDI communication the EANCOM standard MUST be utilised as the supported data standard and therefore MUST be supported by the Trading Partner (either directly or through 3 rd party service). For all new EDI Trading Partners to M&S, it is expected that EANCOM will be utilised. Trading Partners whom have existing EDI with M&S these communications will continue to be supported regardless of the information standard utilised. Where the opportunity provides it these non-supported information standards MUST be migrated to the EANCOM standard. The definition of support is as follows: Any information exchange MUST relate to an EANCOM defined data model as listed by EANCOM 2002 Syntax 4 Any data model utilised MUST conform to the EANCOM definition both schematically i.e. structure and semantically i.e. data format. This includes use of mandatory segments and elements, and adhering to data types and data representations Business level responses MUST be agreed to by M&S and the each Trading Partner and will be specified as part of the MS Message Implementation Guide (this document). Where utilised they MUST align to those specified by the EANCOM standard e.g. PROINQ and PRODAT 1.5 Message Flows 1.5.1 Franchise Trading Partner As part of the M&S to Franchise trading process, as of the date of this Message Implementation Guide, M&S will utilise the following business documents for its Franchise Trading Partner transactions: Invoices Invoices for received purchase orders will be sent using the Invoice business document For Franchise suppliers, all messages will be available in EANCOM standard. 1.6 Interface Definitions The following provides reference and explanation to the interface definitions: Property Communication Direction EANCOM Version EANCON Document Name EANCOM Document EANCOM Document Version Explanation Details the direction in which the information will be transmitted: M&S to 3 rd Party M&S will be the sender of the data 3 rd Party to M&S M&S will be the receiver of the data. The version of the EANCOM standard that is to be utilised. All documents will refer to the following version: EANCOM 2002 Syntax 4 (based on UN/EDIFACT D.01B Syntax 4) The business name of the EANCOM document to be used as part of the information exchange The EANCOM short name for the business document to be used as part of the information exchange The version of the business document to be used M&S plc 2007 Page 4 of 25

Property Document Scope Transmission Frequency Data Object Definition erence Explanation The scope of the data to be passed as part of the information exchange. This will be either Full Record. All data elements associated to the business document will be passed regardless of whether those elements have changed. Changed Elements Only. Only the key elements and those which have changed will be transmitted. The frequency of when the business documents will be sent and expected to be received Real-time. A document will be sent and processed end-to-end in realtime, or near real-time Daily. Any document sent or received by M&S will be once per day. If more than 1 document is sent or received during that daily period, all documents will done so at the same time erence to the data object definition within the Information Exchange Data Definition Document. 1.7 Assuring your implementation Once you have finalised your implementation of the M&S Business Document Definition, GXS will be onhand to test both compliance of your implementation, along with ensuring that you can successfully connect to your secure mailbox. GXS will work with you to ensure your on-boarding is a success and resolve and issues you encounter with your implementation. Once these final checks and testing have been completed you will be ready to start exchanging EDI messages with M&S electronically and soon start realising the benefits of using our electronic trading solution. 1.8 M&S Electronic trading solution Support During the exchange of business documents between M&S and yourself there may be circumstances where the documents are not successfully transmitted, or the data received is not accepted / compliant to that which is expected by either of our systems. M&S plc 2007 Page 5 of 25

2 MESSAGE DEFINITION The sections that follow detail the specification of the business document that is the subject of this Message Implementation Guide that M&S will support for electronic information exchange. 2.1 Message Data Flow Summary The Invoice EDI Business Document will enable M&S to send invoices electronically to Franchise Trading Partners. As detailed by the definition in this section, the Invoice will contain: The M&S Invoice Number and Invoice issue date. The M&S VAT Registration No. erence to the originating Purchase Order number General information about the buyer and supplier including unique identifiers The items from the Purchase Order document being invoiced against erence to the Purchase Order document, and the line items Unique item identifiers The invoice quantities and price conditions. M&S will send a full Invoice document as detailed by this implementation guide. M&S will send reference only 1 Purchase Order on each Invoice document. M&S will send 1 Invoice per Invoice file / UNB segment. 2.2 Message Use-Cases The Invoice message will be used for the following: Invoice to Franchise M&S will send an Invoice to Franchise trading partner. 2.3 Message Specification erence Guide 2.3.1 Invoice - INVOIC The following table provides summary detail to this business document trading partner must ensure that the correct version of the EANCOM message template is used for its implementation. Property Communication Direction M&S to Franchise Trading Partner Value EANCOM Version EANCOM 2002 Syntax 4 EDIFACT Version erence EANCON Document Name EANCOM Document UN/EDIFACT D 2001B Syntax Invoice INVOIC EANCOM Document Version 001 M&S plc 2007 Page 6 of 25

Property Value Document Scope (Full Record/Changed Elements Only) Transmission Frequency Full Record Daily 2.4 Message Definition Summary Each Business Document Data Definition guide provides the following information: Chg Flag. The Chg Flag provides identification of any changes from version to version. Y = has changed, N = No Change. The EANCOM segment within which the field to populated exists. /Element erence. The EANCOM field name to be populated and exchanged. Business. Business description of the field / element to be used by M&S.. The number of occurrences of the field being populated. Data Type and. The data type of the field of the field being populated and the maximum length of the data that is to be expected for the specified field. Example Values. Any example values that will be populated by M&S or that M&S would expect to send in the message. 2.5 Message Definition Guide - INVOIC 2.5.1 EANCOM Interchange Header Every EANCOM message will require an EANCOM Interchange Header. The interchange MAY contain one or more EANCOM messages of the same type. This segment is used to envelope the interchange, as well as to identify both, the party to whom the interchange is sent and the party who has sent the interchange. The principle of the UNB segment is the same as a physical envelope which covers one or more letters or documents, and which details, both the address where delivery is to take place and the address from where the envelope has come. The Interchange Header is defined in the table that follows: Example Value N UNB INTERCHANGE HEADER S001 Syntax identifier N 0001 M a4 Syntax identifier UNOA Definitions the ISO encoding standard of the data. N 0002 M an1 Syntax version number 4 N UNB S002 INTERCHANGE SENDER N 0004 M an..35 Interchange sender identification 00098765 4321 Unique Company EDI GLN Identifier N 0007 C an..4 Identification N UNB S003 INTERCHANGE RECEIVER 14 EAN GLN N 0010 M an..35 Interchange recipient identification 00012345 6789 Unique Company EDI GLN Identifier M&S plc 2007 Page 7 of 25

Example Value N 0007 C an..4 Identification N UNB S004 INTERCHANGE CONTROL REFERENCE 14 EAN GLN N 0017 M an..35 Date of Interchange 0090903 CCYYMMDD N 0019 C an..4 Time of Interchange 1032 HHMM N UNB INTERCHANGE CONTROL REFERENCE N 0020 M an..14 Unique reference identifying the interchange. Created by the interchange sender. N UNB APPLICATION REFERENCE 00000000 000161 Unique message interchange identifier. N 0026 C an..14 Message identification if the interchange contains only one type of message. INVOIC erence of the EANCOM business document An example of the Interchange Header is provided for reference: UNB+UNOA:4+SENDERID:ZZZ+RECEIVERID:ZZZ+20101109:1145+00000000000137++INVOIC' 2.5.2 EANCOM Business Document Definition The Invoice message is implemented using the EANCOM INVOIC data template. Further information regarding the base template can be found at the following location: http://www.gs1.se/eancom_2002/ean02s4/experts/index.htm The M&S usage of that template is defined below: Example Value N UNH HEADER N 0062 AN 14 Message reference number N S009 MESSAGE IDENTIFIER N 0065 AN 6 Message type INVOIC N 0052 AN 3 Message version number D N 0054 AN 3 Message release number 01B N 0051 AN 3 Controlling agency, d N 0057 AN 6 Association assigned N 0110 AN 6 Code list directory version number N BGM BEGINNGING OF MESSAGE UN EAN010 M&S plc 2007 Page 8 of 25

Example Value N C002 DOCUMENT/MESSAGE NAME N 1001 AN 3 Document name 380 380 = Commercial invoice N C106 DOCUMENT/MESSAGE IDENTIFICATION N 1004 AN 35 Invoice Document erence identifier 123456789 M&S Invoice Number. N 1225 AN 3 Message function 9 9 = Original 7 = Duplicate N DTM C507 DATE/TIME/PERIOD Invoice Date N 2005 AN 3 Date or time or period function N 2380 AN 35 Invoice Date or time or period value N 2379 AN 3 Date or time or period format 137 Default = 137 (Document/message date/time) 20091225 Invoice Date 102 Default = 102 (CCYYMMDD) N PAI Payment instructions N C534 PAYMENT INSTRUCTION DETAIL N 4461 AN 3 Payment means 42 Default Entry= 42 N SG2 SG2-NAD-FII-SG3-SG5 M&S Identifier and Address Information N NAD Name and address N 3035 AN 3 Party function SU SU = Supplier N C080 PARTY NAME N 3036 AN 35 PARTY NAME Marks & Spencer PLC M&S Name N C059 Street N 3042 AN 35 Street and number or post office box identifier WATERSIDE HOUSE N 3164 AN 35 City name London N C819 COUNTRY SUB-ENTITY DETAILS N 3228 AN 70 Country sub-entity N 3251 AN 17 Postal W2 1NW N 3207 AN 3 Country name (ISO 3166 two alpha ) GB N NAD Name and address M&S plc 2007 Page 9 of 25

Example Value N 3035 AN 3 Party function IV IV = Invoicing Party N C080 PARTY NAME N 3036 AN 35 PARTY NAME Marks & Spencer PLC M&S Name N C059 Street N 3042 AN 35 Street and number or post office box identifier WATERSIDE HOUSE N 3164 AN 35 City name London N C819 COUNTRY SUB-ENTITY DETAILS N 3228 AN 70 Country sub-entity N 3251 AN 17 Postal W2 1NW N 3207 AN 3 Country name (ISO 3166 two alpha ) GB N SG 5 1-5 N CTA Contact Information N 3139 AN 3 Contact function AR Default entry = "AR" Accounts Receivables N C056 DEPARTMENT OR EMPLOYEE DETAILS N 3412 AN 35 Department or employee name N COM C076 Communication contact N 3148 AN 512 Communication address identifier Telephone Number N 3155 AN 3 Communication address N COM C076 Communication contact N 3148 AN 512 Communication address identifier Fax Number N 3155 AN 3 Communication address N COM C076 Communication contact N 3148 AN 512 Communication address identifier Email Address N 3155 AN 3 Communication address M&S Accounting clerk name 1-5 004402080567123 M&S Accounting clerk telephone TE TE=Telephone 004402080123456 M&S Accounting clerk fax FX FX=Fax N SG3 RFF N RFF C506 M&S VAT REFERENCE M&S Accounting clerk e-mail address EM EM= Electronic Mail N 1153 AN 3 VAT Registration. User Defined erence VA VA = VAT erence M&S plc 2007 Page 10 of 25

Example Value N 1154 AN 70 Supplier VAT Registration Number GB232128892 M&S VAT Registration Number N SG3 RFF N RFF C506 M&S Company Registration Number N 1153 AN 3 Company Registration Number erence XA XA= Company Registration Number erence N 1154 AN 70 Company Registration Number 4256886 M&S registration number N SG2 SG2-NAD-FII-SG3-SG5 Franchise Identifier and Address Information N NAD Name and address N 3035 AN 3 Party function N C082 PARTY IDENTIFICATION DETAILS BY BY=Buyer N 3039 AN 35 Code list responsible agency M&S Franchise Trading Partner Number Identifier N 3055 AN 3 PARTY NAME 9 9 = Franchise agency N C080 PARTY NAME N 3036 AN 35 PARTY NAME ABC LTD Franchise Trading Partner Name N C059 STREET N 3042 AN 35 Street and number or post office box identifier Kensington House Street Name N 3164 AN 35 City name LONDON City N C819 COUNTRY SUB-ENTITY DETAILS N 3228 AN 70 Country sub-entity name Greater London County N 3251 AN 17 Postal SW11 9LA Post Code N 3207 AN 3 Country name (ISO 3166 two alpha ) name GB N SG 3 RFF N RFF C506 Franchise VAT REFERENCE N 1153 AN 3 VAT Registration. User Defined erence Only present if UK VAT Registered VA VA = VAT erence M&S plc 2007 Page 11 of 25

Example Value N 1154 AN 70 Franchise VAT Registration Number GB012345678 N SG2 SG2-NAD-FII-SG3-SG5 Franchise Invoicing Address Information N NAD Name and address N 3035 AN 3 Party function N C080 PARTY IDENTIFICATION DETAILS RE RE= Party to receive commercial invoice remittance N 3036 AN 35 PARTY NAME Accounts Receivable Franchise Invoicing Department Name N 3036 AN 3 PARTY NAME Mr Jones Franchise Invoicing Accountant Name N C059 PARTY NAME N 3042 AN 35 Street and number or post office box N 3042 AN 35 Street and number or post office box STREET Accounts House Swiss Street (Optional ) N 3164 AN 35 City Name London N C819 COUNTRY SUB-ENTITY DETAILS N 3228 AN 70 Country sub-entity name N 3251 AN 17 Postal W2 1NW N 3207 AN 3 Country name (ISO 3166 two alpha ) name GB N SG 6 TAX-MOA 1-5 N TAX Duty/tax/fee details N 5283 AN 3 Duty or tax or fee function N C243 DUTY/TAX/FEE DETAIL N 5279 AN 7 Duty or tax or fee rate 7 Default value = 7 01 VAT indicator See Guidance N 5278 AN 17 Duty or tax or fee rate 0 VAT rate See Guidance N MOA Monetary amount N C516 MONETARY AMOUNT N 5025 AN 3 Monetary amount type 124 Default entry = "124" M&S plc 2007 Page 12 of 25

Example Value N 5004 N 35 Monetary amount 200.00 VAT added tax amount N SG 7 CUX-DTM 1-m N CUX Currencies N C504 CURRENCY DETAILS N 6347 AN 3 Currency usage N 6345 AN 3 Currency identification N 6343 AN 3 Currency type 2 2 = erence Currency GBP Invoice Currency 4 4 = Invoicing Currency N C504 AN 6 CURRENCY DETAILS N 6347 AN 3 Currency usage N 6345 AN 3 Currency identification N 6343 AN 3 Currency type 3 3 = M&S book currency GBP M&S book currency 4 4 = Invoicing Currency N 5402 N 12 Currency exchange rate Exchange rate N SG 8 PAT-DTM-PCD-MOA- PAI-FII N PAT Payment terms basis N 4279 A N 3 Payment terms type identifier 22 22 = Discount N C112 AN 3 PAYMENT TERMS N 2475 AN 3 Time reference 5 5 = Date of invoice N 2009 AN 3 Terms time relation 3 3 = After reference N 2151 AN 3 Period type D Day N 2152 N 3 Period count quantity Days of cash discount N PCD Percentage details N C501 PERCENTAGE DETAILS N 5245 AN 3 Percentage type 12 12 = Discount N 5482 N 10 Percentage Cash discount rate N FII Financial institution information N 3035 AN 3 Party function N C078 ACCOUNT HOLDER IDENTIFICATION N 3194 AN 35 Account holder identifier RB RB = Receiving financial institution M&S account IBAN number M&S plc 2007 Page 13 of 25

Example Value N 3192 AN 35 Account holder name Marks & Spencer M&S name PLC N C088 INSTITUTION IDENTIFICATION N 3433 AN 11 Institution name Bank SWIFT N 1131 AN 17 Code list identification 25 25 = Bank identification N 3055 AN 3 Code list responsible 17 S.W.I.F.T. agency N 3432 AN 70 Institution name Bank name N SG 26 LIN-PIA-IMD-MEA- QTY-ALI-DTM-GIN- QVR-FTX 1-N N LIN Line item N 1082 AN 6 Line item identifier 00010 Line item number Y C212 ITEM NUMBER IDENTIFICATION Y 7140 AN 35 Item identifier/upc 01234567 M&S UPC Item identifier N 7143 AN 3 Item type identification N PIA Additional product id SRV SRV = EAN.UCC Global Trade Item Number N 4347 AN 3 Product identifier 5 5 = Product identification N C212 ITEM NUMBER IDENTIFICATION N 7140 AN 35 Item identifier M&S Unique Item identifier N 7143 AN 3 Item type identification SA SA = Supplier's article number N 3055 AN 3 Code list responsible agency N IMD Item description N C273 ITEM DESCRIPTION 91 91 = Assigned by supplier or supplier's agent N 7008 AN 256 ITEM DESCRIPTION Chocolate Cake Item description N QTY Quantity N C186 QUANTITY DETAILS N 6063 AN 3 Quantity type 47 47 = Invoiced quantity N 6060 AN 35 Quantity 200 Quantity N 6411 AN 3 Measurement unit EA EA = Each N SG 26 Monetary amount 1-N M&S plc 2007 Page 14 of 25

Example Value N MOA C516 MONETARY AMOUNT N 5025 AN 3 Monetary amount type 203 Net Line item amount N 5004 N 35 Monetary amount 100.00 Monetary amount N SG 26 Monetary amount 1-N N MOA C516 MONETARY AMOUNT N 5025 AN 3 Monetary amount type 38 Invoice Item Amount N 5004 N 35 Monetary amount 100.00 Monetary amount N SG 29 PRI-APR N PRI C509 Price details N 5125 AN 3 Price AAA Calculation net N 5118 N 15 Price Amount 10.00 Price Amount N 5284 N9 Unit price basis value 1 1 = Unit price basis value N 6411 AN 3 Measurement unit EA EA = Each N SG 30 RFF-DTM N RFF C506 erence 1153 AN 3 erence identifier DQ DQ = Delivery note number 1154 AN 70 erence identifier 00000012 erence Number N SG 30 RFF-DTM N RFF C506 erence N 1153 AN 3 erence identifier VN VN = Order number N 1154 AN 70 erence identifier 001234567 erence Number N SG 30 RFF-DTM N RFF C506 erence N 1153 AN 3 erence identifier AAJ AAJ = Delivery Order Number N 1154 AN 70 erence identifier 001234567 erence Number N SG 33 LOC-QTY-DTM N LOC 3227 AN 3 Place/location identification 7 7 = Place of delivery M&S plc 2007 Page 15 of 25

Example Value N C517 LOCATION IDENTIFICATION N 3225 AN 25 Location name M&S Code for Franchise Store N 3224 AN 256 Location name M&S Name for Franchise Store Franchisee store Franchisee store name N DTM Date/time/period N C507 DATE/TIME/PERIOD N 2005 AN 3 Date or time or period function N 2380 AN 35 Date or time or period value N 2379 AN 3 Date or time or period format 35 35 = Goods receipt date 20101222 Goods receipt date 102 102 = CCYYMMDD N SG 34 TAX-MOA 1-N N TAX Duty/tax/fee details N 5283 AN 3 Duty or tax or fee function N C243 DUTY/TAX/FEE DETAIL N 5279 AN 7 Duty or tax or fee rate 7 7 = Duty or tax or fee function 01 See Guidance for all s N 5278 AN 17 Duty or tax or free rate 0 VAT Rate N MOA C516 Monetary amount See Guidance for all rates N 5025 AN 3 Monetary amount type 150 150 = Tax amount of the line N 5004 N 35 Monetary Tax amount 300.00 Tax amount of the line An example of the Interchange Detail segments is provided for in Section 4 Understanding EDIFACT / EANCOM for reference. 2.5.3 EANCOM Interchange Trailer Every EANCOM message will require an EANCOM Interchange Trailer. The UNZ segment is used to provide the trailer of an interchange. The Interchange Trailer is defined in the table that follows: M&S plc 2007 Page 16 of 25

Example Value N UNS Section control N 0081 AN 1 Section identification S Detail/summary section separation N CNT Control total 0 N C 270 Control N 6069 AN 3 Section identification 2 Default to 2 - Number of line items in message N 6066 N 18 Control total value 1 Specify the number of line items on the Invoice N SG 50 MOA-SG51 N MOA C516 Monetary amount N 5025 AN 3 Monetary amount type N 5004 N 35 Total amount of the Invoice N 6345 AN 3 Currency identification 86 86 = Invoice amount Monetary amount GBP Currency identification N MOA C516 Monetary amount N 5025 AN 3 Monetary amount type N 5004 N 35 Total Taxable / Net Amount N 6345 AN 3 Currency identification 125 125 = Taxable amount Monetary amount GBP Currency identification N MOA C516 Monetary amount N 5025 AN 3 Monetary amount type N 5004 N 35 Tax amount of the Invoice N 6345 AN 3 Currency identification 176 176 = Value added tax Monetary amount GBP Currency identification N MOA C516 Monetary amount N 5025 AN 3 Monetary amount type N 5004 N 35 Tax amount of the Invoice N 6345 AN 3 Currency identification 52 52 = Discount Amount Monetary amount GBP Currency identification N MOA C516 Monetary amount N 5025 AN 3 Monetary amount type 124 124 = Tax Amount N 5004 N 35 Tax amount of the Monetary amount M&S plc 2007 Page 17 of 25

Example Value Invoice N 6345 AN 3 Currency identification GBP Currency identification N SG 52 TAX-MOA 0 N TAX 5283 AN 3 Duty or tax or fee function N C243 DUTY/TAX/FEE DETAIL N 5279 AN 7 Duty or tax or fee rate 7 Default value = "7" 03 03 = 20% N 5278 AN 17 Duty or tax or fee rate 20 VAT rate N MOA Monetary amount 1-2 N C516 MONETARY AMOUNT N 5025 AN 3 Monetary amount type 124 Taxable amount N 5004 AN 35 Monetary amount Monetary amount N UNT INTERCHANGE TRAILER N 0074 N 10 Number of segments in a message 0062 AN 14 Message reference number N UNZ INTERCHANGE TRAILER N 0074 N 6 Number of messages or functional groups within an interchange. Total number of segments in the message is detailed here The message reference number detailed here should equal the one specified in the UNH segment 1 N 0002 AN14 Interchange control reference 00000000 000161 Identical to 0020 in UNB segment An example of the Interchange Trailer is provided for reference: UNT+0000000037+00000000000141' UNZ+000001+00000000000137' 2.5.4 SG6-TAX-MOA For each tax rate appearing on the Invoice, there will be an equivalent SG6 segment detailing the Tax Rate, and the total amount of tax applicable on the Invoice to that rate. For example, if there were two items on the invoice of differing rates, 0% and 20%, there will be two equivalent SG6 segments specifying the total amount on the invoice for the 0% tax rate, and the total amount for the 20% tax rate. M&S plc 2007 Page 18 of 25

2.5.5 SG6-TAX-MOA / SG34-TAX-MOA Tax Rates & Tax Codes The Tax Rates and Tax Codes that will be present for the SG6-5279 and SG34-5279 segments are as follows: Tax Rate (%) Tax Code 0 01 5 02 20 03 2.5.6 Tax Rates All tax rates on the invoice will be sent as detailed in the table in 2.5.5. 2.5.7 Mixed Rate VAT If item received with mixed VAT in the Purchase Order, M&S will send the of 09 and blended VAT rate. M&S plc 2007 Page 19 of 25

3 COMPLIANCE TESTING 3.1 Test Cases The following test cases are required for the testing of this EDI Business Document. 3.1.1 INVOICE_INVOIC_001 This test condition is to test ensure the implementation compliance for the Invoice creation functional use case M&S creates the invoice and submits to Trading Partner. Your implementation must be able to map the Invoice aligned to the example test file. Property Test Case erence Business Context Functional Requirement Applies To Test Case Definition Outcome INVOICE_INVOIC_001 Definition / erence Franchise receives Invoice from M&S for PO s raised with M&S. The creation by M&S of an Invoice for a Franchise goods receipted Purchase Order M&S Invoice sent from M&S to GXS and then to Franchise. Invoice contains the following information: - Franchise & M&S Name, Address and Number - Franchise & M&S VAT registration number - Invoice Number & Date, Tax and Currency - Discount Percentage Details - Financial Institution Details - Line Item Details - M&S VAT registration number - PO Number & Issue Date, Dept & Delivery Note - Product Info, Units, Price and Amount, Supplier Discount Invoice sent to Franchise Trading Partner via GXS for previously published PO s. Test File erence INVOICE_INVOIC _001.edi M&S plc 2007 Page 20 of 25

4 UNDERSTANDING EDIFACT / EANCOM 4.1 WHAT IS EDIFACT? UN/EDIFACT: United Nation's Directories for Electronic Data Interchange for Administration, Commerce and Transport. They comprise a set of internationally agreed standards, directories and guidelines for the electronic interchange of structured data, particular as related to trade in goods and services, between independent, computerised information systems. All EANCOM 2002 messages used by Marks and Spencer are based on the UN/EDIFACT directory D.01B which was released by UN/CEFACT in 2001. 4.2 EANCOM Message Structure Each EANCOM message will have the following structure: Interchange / Envelope Header (UNB) Message Header Section (UNH) Detail Section (Any) Summary Section (UNT) Interchange / Envelope Trailer (UNZ) The structure is shown the figure that follows: 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 and will contain the business data i.e. billing document etc. Summary section - Only segments containing totals or control information may occur in the summary section, e.g. invoice total amount, number of lines in a billing document 4.2.1 s and Groups The same segment type may occur in more than one of the message sections, for example 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. M&S plc 2007 Page 21 of 25

A segment group may be nested within other segment groups, provided that the inner segment group terminates before any outer segment group terminates. The following taken from the EANCOM standard itself provides reference to the message structure with segments and segment groups. A segment consists of the following: A segment tag: identifies the segment type Data element separators Simple and/or composite 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 a that gives specific meaning to the data. The data value of a is a taken from an agreed set of values. M&S plc 2007 Page 22 of 25

4.3 Example EANCOM Message 4.3.1 Invoice Example 1 The following Invoice is provided as an example only: UNB+UNOA:4+SENDERID:ZZZ+RECEIVERID:ZZZ+20110518:1254+00000000000082++INVOIC' UNH+00000000000084+INVOIC:D:01B:UN:EAN010' BGM+380+9000000184+7' DTM+137:20110228:102' PAI+::42' NAD+RE+++MARKS & SPENCER:ACCOUNTS RECEIVABLES+0+LONDON+++GB' CTA+AR+:ACCOUNTS RECEIVABLES' COM+0333 200 5510:TE' COM+0161 873 8760:FX' COM+ACCOUNTSRECEIVABLE2@MARKS-AND-SPENCER.COM:EM' NAD+IV+++MARKS AND SPENCER GROUP PLC+35 NORTH WHARF ROAD, WATERSIDE HOUS+LONDON++W2 1NW+GB' NAD+BY+0000020355::9++BP OFFSHORE+STOCKLEY PARK+UXBRIDGE++UB11 1AW+GB' RFF+VA:0' NAD+SU+++MARKS AND SPENCER GROUP PLC+35 NORTH WHARF ROAD, WATERSIDE HOU+LONDON++W2 1NW+GB' RFF+VA:GB232128892' RFF+XA:214436' TAX+7++++A2:::17.50' MOA+124:1.35' TAX+7++++A1:::5.000' MOA+124:0.29' TAX+7++++A0:::0.00' MOA+124:0' CUX+2:GBP:4+3:GBP:4+1' PAT+22++5:3:D:6' PCD+12:0' FII+RB+GB56ULSB40010620559253+ULSBGB12341:25:17::::ICICI' LIN+000010++00109628:SRV' PIA+5+000000000020004645:SA::91' IMD+++:::OUDINOT VINTAGE CHAMPGNE' QTY+47:10.000:EA' MOA+203:30.92' MOA+38:30.92' MOA+203:7.73' MOA+38:9.08' PRI+AAA:0:::0' RFF+DQ:TEST_U1' RFF+VN:1950000128' RFF+AAJ:0080000554' LOC+7+0000000012:::CHURCH VIEW TUNBRIDGE BP' M&S plc 2007 Page 23 of 25

DTM+35:20110228:102' TAX+7++++A0:::0.00' MOA+150:0' LIN+000020++00133265:SRV' PIA+5+000000000020005233:SA::91' IMD+++:::MINI POPPADUMS' QTY+47:10.000:EA' MOA+203:5.71' MOA+38:6' PRI+AAA:0:::0' RFF+DQ:TEST_U1' RFF+VN:1950000128' RFF+AAJ:0080000554' LOC+7+0000000012:::CHURCH VIEW TUNBRIDGE BP' DTM+35:20110228:102' TAX+7++++A1:::5.000' MOA+150:0.29' UNS+S' CNT+2:2' MOA+52:0:GBP' MOA+176:1.64:GBP' MOA+86:46:GBP' MOA+125:44.36:GBP' MOA+176:1.64:GBP' MOA+86:40.29:GBP' MOA+125:38.65:GBP' TAX+7++++A2:::17.50' MOA+124:1.35' TAX+7++++A1:::5.000' MOA+124:0.29' TAX+7++++A0:::0.00' MOA+124:0' UNT+71+00000000000084' UNZ+1+00000000000082' M&S plc 2007 Page 24 of 25

5 VERSION CONTROL The following versions of the document have been produced: Version Status Issue Date Author Comments 1.0 Issued 07/12/2010 M&S 1.1 Draft 07/06/2011 M&S Addition of new example file and clarification of message definition table M&S plc 2007 Page 25 of 25