TECCOM SUPPLIER GUIDE FOR CONVERTING TXML INVOICE TO CLEPA-FIGIEFA EDIFACT VERSION 1.0 10.11.2006



Similar documents
... connecting the Automotive Aftermarket. Invoice. Description of Content and Structure. Version 1.0

EDI F GROUP A/S INVOICE. Fona. Document: EDIFACT UserGuide GB-INVOIC_IBM-draft1 Date: 5/ Version: V1.0.0A Page 0 of 43. ecommerce ServiceCenter

G e r m a n y INVOIC - EANCOM 02, D.01B INVOIC - EANCOM 97, D.96A

TECCOM SUPPLIER GUIDE FOR CONVERTING TXML DESADV TO CLEPA-FIGIEFA EDIFACT VERSION

PURCHASE ORDER RESPONSE

AO BUSINESS Guidelines EDI invoices from goods suppliers. (to be published on the Suppliers Portal)

Issue 1.1, February agreed-upon by EDI Working Group of ECR Poland

EDI Guideline KION Group Orders based on EDIFACT ORDERS D.96A Version

e2b Invoice Format Message Description Version: 3.4

PRICE/SALES CATALOGUE MESSAGE PRICAT. Version 1.0. agreed-upon by EDI Working Group of ECR Poland

Media Saturn EDI Application Documentation

Issue 6.7, April agreed-upon by EDI Working Group of ECR Poland

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

T.8 USING THE INVOICE FOR BILLING AND FOR DEBIT AND CREDIT NOTES

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

PARTY INFORMATION MESSAGE. PARTIN Version 1.0. agreed-upon by EDI Working Group of ECR Poland

Bulk EDIFACT ASN MESSAGE FORMAT

EANCOM D.96A Version: 007 Print: EAN ORDERS D.96A DE

EDI in Detail CIV Superunie BA. EDI in Detail. Version 1.6 Page 1 of 33

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

EDI specifications. between. BLANCO GmbH + Co KG referred to in the following as BLANCO. and its business partners (suppliers)

Supply Chain Merchandise Logistics EANCOM Orders and DESADV Business Examples

INVENTORY REPORT MESSAGE INVRPT. Version 1.2. agreed-upon by EDI Working Group of ECR Poland

Magyar Hipermarket Kft. EDI guide PURCHASE ORDER MESSAGE ORDERS EDIFACT D.96A

Issue 1.9, April agreed-upon by EDI Working Group of ECR Poland

EANCOM INVOICES CROSS DOCK MESSAGE FORMAT A TECHNICAL GUIDE FOR SUPPLIERS

R.2 STRUCTURE OF AN EDIFACT TRANSMISSION

Grundfos EDIFACT D.96.A

Global EDI Clearing Center (GECC)

EDI Guideline Orders for configurable materials based on EDIFACT ORDERS D.96A Version

ORDERS. Purchase order message. Edition 2014

Purchase Orders Message ORDERS (EDIFACT D97A)

Hella EDIFACT ORDERS

NAF Nätverk för Affärsutveckling i Försörjningskedjan

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

Best practice Bundle products in ONIX 2.1 and EANCOM

Book Industry Communication

THE DELIVERY FORECAST MESSAGE DELFOR EDIFACT D.96A

ADOBE - EDIFACT D97A INVOIC

Payment on Receipt EDIFACT INVOIC D97.A

INVOIC Invoice message

UC San Diego Library UC San Diego

Issue 6.4, December agreed-upon by EDI Working Group of ECR Poland

Message Implementation Guideline ORDERS Purchase Order PHARMA Initiative Austria EANCOM 2002 Syntax 3 Version 1.1. Directory Version:

DELJIT D97A / CALDEL

ORDCHG Purchase Order Change Message Subject for application in the European Steel Industry

INVOIC - EANCOM 97, D.96A INVOIC - EANCOM 02, D.01B

Economic and Social Council

... connecting the Automotive Aftermarket. OrderResponse. Description of Content and Structure. Version 1.0

EANCOM- Spezifikation ORDERS D 96A (EDI-Nachrichtenstandard 2)

5.0 Detailed guidelines of purchase order response (ORDRSP Version 1 EDIFACT D 96B) usage within Volvo.

Manor EDI-Manuel. Purchase Orders ORDERS D96.A EANCOM. Manor AG EDI : Purchase Orders EINFÜHRUNG. 1. Manor Adresse Identifikation. 2.

Explanatory notes VAT invoicing rules

Hella EDIFACT INVRPT

This document is for EDI-administrators who will implement this EDI-guide to be able to receive EDIFACT orders from Bosch Rexroth AG.

Adobe - EDIFACT D97.A ORDERS

Mapping orders from your library management system to EDI

EPIC. EDI Core Standards VM

Aleph Requirements for EDI -Outgoing and Incoming Messages

INVOIC. Invoice message. Edition 2014

Furthermore remember to uninstall the old DWI client before replacing it with the new version.

Table of contents A X T E D I 2. version: AXT EDI Filter 2.0.3

ECommerce EDI Toolkit. Version September 2008

E A N C O M - MESSAGE

DOCUMENT "INVOICE" USE PROFILE

EDIFACT ORDRSP D99.B Formal Description of Segments Segment: Serial. No.: Level: Service string advice UNA Description: UNA

User Guide for international trade of building materials. Nordic ebuilding EDI guide for EDIFACT INVOIC

E-Supplier. Information for Siemens Vendors - Exchange of business transactions via EDI.

Magna IT EDI services. Supplier Implementation guideline for Electronic data interchange

Contents 1. Introduction 2. Segment description 4. Summary of segments used 13. Summary of segments not used 13. Comparison VDA 4906 => ODETTE 13

Training course, slides version 1.5. EDI for supply chain collaboration in the automotive industry

General invoice information for suppliers

ICEDIS Claim, Claim Response and Claim Cancellation Messages

GoGetSSL API Guide Version: 2.5 (stable)

Art des Dokuments Supplier Logistics Manual EDI in Procurement

EDIFACT DESADV D.97A for suppliers (Benteler Europe)

810 Invoice ANSI ASC X12 Version 4010

Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

Portland General Electric Implementation Standard

Electronic Commerce. 6. Electronic Data Interchange and XML. V Rajaraman

FREQUENTLY ASKED QUESTIONS

ODEX Enterprise. Introduction to ODEX Enterprise 3 for users of ODEX Enterprise 2

EDI Implementation Guidelines for Library Book Supply Changes, since issue 1.2

Business Document Specification Issue date: Version: 1.61 Invoice Belonging message specification: MS 35

ZF Group North American Operations. EDI Implementation Guide

I. METHOD OF INSTALLATION. II. INSTALLATION OF THE TecLocal

ORDERS Purchase Order

HOW TO SEND E-INVOICES TO University of Bergen and other companies accounted there.

How To Use Optimum Control EDI Import. EDI Invoice Import. EDI Supplier Setup General Set up

TecCom Orderer System

TABLE OF CONTENTS. 1. Message structure INVOIC BUSINESS TERMS Segment description INVOIC Example INVOIC...

SKF Requirements for Invoices and Delivery Notes

Walmart Stores, Inc. Getting Started with EDI Implementation Guideline Document version: 1.0 Published November 2011

EDI. Overview. A Practical Guide to EDI and the TrueCommerce EDI Platform

TECHNICAL WHITE PAPER COVAST OFTP ADAPTER FOR IBM WEBSPHERE PARTNER GATEWAY SEPTEMBER 2005 COPYRIGHT 2005 COVAST

What s new? Tips & Tricks

Fundamentals of Database System

Transcription:

TECCOM SUPPLIER GUIDE FOR CONVERTING TXML INVOICE TO CLEPA-FIGIEFA EDIFACT VERSION 1.0 10.11.2006

The TecConversion Center makes possible the exchange of edifact and CAP messages between trader and supplier. Traders can reach all suppliers who have TecCom. Suppliers can also send CAP and edifact messages to TecCom traders who do not use these formats or do not even have EDI systems. If the supplier sends a reverse message order response, despatch advice, invoice to a trader, the Conversion Center brings it into the format the trader has requested. This document describes the maximum data contents of a TXML invoice (version 1.0), that can be converted into Clepa-Figiefa edifact format (INVOIC Subset D.96A version 008) in the TecCom Conversion Center. In this scenario, the supplier is sending TXML invoices and the buyer is receiving invoices in Clepa-Figiefa edifact format. TecCom invoice process is asynchronous, meaning that the invoices are sent in a schedule that is independent of the preceding events, e.g. sending of an order or a despatch advice. In some cases, a supplier may not send an order response at all via TecCom but on paper. The asynchronous invoice process can be accessed with any of the supported communication methods: FTP, OFTP, ISDN and TecCom Open Messaging framework (web service). Please refer to separate documentation about these methods. The purpose of this document is to display examples of TXML invoice documents, which are compliant with the requirements of the Clepa-Figiefa specification. Since the suppliers create TXML invoice messages themselves, their contents can vary considerably. Therefore, TecCom has created some rules that the suppliers should implement in order to limit the variations in the use of the messages. E.g. there are rules with respect to field lengths, use of different elements in different situations etc. This guide should not be used alone. The overall content and structure of a TXML invoice is described in the document IFD_Invoice_10_en.doc. This supplier guide describes only a specific use scenario, i.e. when a TXML invoice is converted into Clepa-Figiefa invoice. Table 1 describes the maximum data contents of a TXML invoice message that can be transmitted via the TecCom Conversion Center to the recipient. Please note, that some recipients may not utilize all the data that a supplier is able to provide (e.g. additional product descriptions). Differences in the TXML message structure are caused by the use of TaxTreatmentCode. Tax elements are used differently with different TaxTreatmentCodes. Please refer to IFD_Invoice_10_en.doc. The conversion from TXML to Clepa-Figiefa supports the codes: NetLineLevel, NetInvoiceLevel and NoTaxApplies. The first column of table 1 depicts the maximum TXML invoice message that can be processed by the invoice converter. No error is caused, if the data contents is larger (within the limits of the invoice DTD) than what is described in table 1. This information will simply not be transported to the invoice recipient.

The second column TXML Invoice breaks the message into its constituents: elements and attributes. Attributes start with a @ character. The third column TXML multiplicity lists the syntactical rules for elements and attributes in TXML. The following rules apply for elements: 1 The element can be used only once 0..1 The element is optional, but it can be used only once 0..n The element is optional and it can be used several times 1..n The element is mandatory and it can be used several times The following rules apply for attributes: R The use of the attribute is required, if the element, within which the attribute is used, exists. O The use of the attribute is optional, if the element, within which the attribute is used, exists. The fourth column TecCom rules describes the requirements and limitations of the process applying to the TXML invoice message. The fifth column defines the maximum length of different data contents on a TXML invoice. For numerical data, the maximum amount of digits is given.

TABLE 1: Maximum contents of a TXML invoice (NetLineLevel) when converting into Clepa-Figiefa TaxTreatmentCode=NetLineLevel. Line item amounts are net amounts. Additional taxes are shown at the line item level. TXML ELEMENTS AND ATTRIBUTES TXML MULTI- PLICITY TECCOM RULES <Invoice> Invoice 1 <Document Type="Invoice" Version="1.0"/> Document 1 @Type R Type "Invoice" is equal to "380" in CF. It is not possible to map credit notes. @Version R TecCom supports currently TXML invoice version 1.0 <InvoiceHeader> InvoiceHeader 1 <InvoiceId>5491332</InvoiceId> InvoiceId 1 35 <InvoiceIssueDate> InvoiceIssueDate 1 <Date>20061004</Date> Date 1 35 </InvoiceIssueDate> <DesAdvRef> DesAdvRef 0..n At least one of the DesAdvRef or OrderRef elements must be populated. <DocumentNumber>557289</DocumentNumber> DocumentNumber 1 35 <Date>20061004</Date> Date 1 35 </DesAdvRef> 35 <OrderRef> OrderRef 0..n <SellerOrderNumber/> SellerOrderNumber 1 SellerOrderNumber is not mapped to CF at all. You can also create an empty element. <BuyerOrderNumber>258010</BuyerOrderNumber> BuyerOrderNumber 0..1 35 <Date>20061004</Date> Date 1 35 </OrderRef> MAX LENGTH

<TaxTreatmentCode Value="NetLineLevel"/> TaxTreatmentCode 1 Tax for this example invoice is calculated based on the TaxTreatmentCode NetLineLevel. Line item amounts are net amounts. Additional taxes are shown at the line item level. @Value R TecCom supports the following tax treatment methods: NetLineLevel=NLL, NetInvoiceLevel=NIL, NoTaxApplies=NTA (used for tax exemptions). <InvoiceDueDate> InvoiceDueDate 0..1 InvoiceDueDate must be filled in. <Date>20070102</Date> Date 1 35 </InvoiceDueDate> <SellerParty> SellerParty 1 <PartyNumber>DE1253222</PartyNumber> PartyNumber 1 PartyNumber is mapped to 35 RFF+API in CF. <Address> Address 1 <Name1>Deutsche Autoteile GmbH</Name1> Name1 1 35 Name2 0..1 35 <Street1>Voltastrasse 5</Street1> Street1 1 35 Street2 0..1 35 <PostalCode>30120</PostalCode> PostalCode 1 9 <City>Berlin</City> City 1 35 <CountryCode>DE</CountryCode> CountryCode 1 3 CountryName 0..1 CountryName is not mapped to CF at all. </Address> </SellerParty> <BuyerParty> BuyerParty 0..n <PartyNumber>000014070</PartyNumber> PartyNumber 1 PartyNumber is mapped to RFF+API in CF. 35 <Address> Address 1

<Name1>Teilehändler Schmidt GmbH</Name1> Name1 1 35 Name2 0..1 35 <Street1>Fokkerstrasse 12</Street1> Street1 1 35 Street2 0..1 35 <PostalCode>80120</PostalCode> PostalCode 1 9 <City>München</City> City 1 35 <CountryCode>DE</CountryCode> CountryCode 1 3 CountryName 0..1 CountryName is not mapped to CF at all. </Address> </BuyerParty> <DeliveryParty> DeliveryParty 0..n <PartyNumber>000014070</PartyNumber> PartyNumber 0..1 PartyNumber is mapped to RFF+API in CF. 35 <Address> Address 1 <Name1>Teilehändler Schmidt GmbH</Name1> Name1 1 35 Name2 0..1 35 <Street1>Fokkerstrasse 12</Street1> Street1 1 35 Street2 0..1 35 <PostalCode>80120</PostalCode> PostalCode 1 9 <City>München</City> City 1 35 <CountryCode>DE</CountryCode> CountryCode 1 3 CountryName 0..1 CountryName is not mapped to CF at all. </Address> </DeliveryParty> <InvoiceOrg> InvoiceOrg 1 <TaxRegistrationNumber>DE4311245</TaxRegistrationNumber> TaxRegistrationNumber 1 <InvoiceParty> InvoiceParty 1 PartyNumber is mapped to RFF+API in CF. <PartyNumber>000014080</PartyNumber> PartyNumber 0..1 <Address> Address 1 35 <Name1>Teilehändler Verbund GmbH</Name1> Name1 1 35 35

Name2 0..1 35 <Street1>Teilstrasse 25</Street1> Street1 1 35 Street2 0..1 9 <PostalCode>56010</PostalCode> PostalCode 1 35 <City>Dortmund</City> City 1 3 <CountryCode>DE</CountryCode> CountryCode 1 CountryName 0..1 CountryName is not mapped to CF at all. </Address> </InvoiceParty> </InvoiceOrg> <Currency>EUR</Currency> Currency 1 Must be the invoicing currency. 3 </InvoiceHeader> <InvoiceDetail> InvoiceDetail 1..n <PositionNumber>1</PositionNumber> PositionNumber 1 6 <Quantity UoM="PCE">1</Quantity> Quantity 0..1 15 @UoM R <ProductId> ProductId 1 <MakerCode/> MakerCode 1 MakerCode is not mapped to CF at all. You can also create an empty element. <ProductNumber>265-459</ProductNumber> ProductNumber 1 35 <Ean>3351642654593</Ean> Ean 0..1 35 </ProductId> <ProductDescription> ProductDescription 1 <ProductName1>KO V.W. Golf II 85-</ProductName1> ProductName1 1 35 ProductName2 0..1 35 </ProductDescription> BuyerPartyNumber 0..1 BuyerPartyNumber is not mapped to CF at all. <DeliveryPartyNumber>000014070</DeliveryPartyNumber> DeliveryPartyNumber 0..1 35 <DesAdvRef> DesAdvRef 0..1 <DocumentNumber>557289</DocumentNumber> DocumentNumber 1 35 <Date>20061004</Date> Date 1 35

</DesAdvRef> <DesAdvItemRef> DesAdvItemRef 0..1 <PositionNumber>1</PositionNumber> PositionNumber 1 6 </DesAdvItemRef> <OrderRef> OrderRef 0..1 <SellerOrderNumber/> SellerOrderNumber 1 SellerOrderNumber is not mapped to CF at all. You can also create an empty element. <BuyerOrderNumber>258010</BuyerOrderNumber> BuyerOrderNumber 0..1 35 <Date>20061004</Date> Date 1 35 </OrderRef> <OrderItemRef> 0..1 <SellerOrderItemRef/> SellerOrderItemRef 1 SellerOrderItemRef is not mapped to CF at all. You can also create an empty element. <BuyerOrderItemRef>15</BuyerOrderItemRef> BuyerOrderItemRef 0..1 6 </OrderItemRef> <AllowOrCharge> AllowOrCharge 0..n This AllowOrCharge element is used to indicate allowances or charges that refer only to one invoice line. <AllowOrChargeIdentifier Value="Allow"/> AllowOrChargeIdentifier 1 TXML values are mapped to CF in the following manner: Allow=A, Charge=C AllowOrChargeCode 0..1 TXML values are mapped to CF in the following manner: HandlingCommision=1, Brokerage=29, BankCharges=30, CourierFee=32, SWIFT=35, FixedLongTerm=60E, Temporary=61E, Standard=62E <AllowOrChargeDescription>Discount</AllowOrChargeDescription> AllowOrChargeDescription 1 All other allowances and 35 charges should be given as a free form description. <Percent>58.67</Percent> Percent 0..1 10

<Amount>5.05</Amount> Amount 0..1 18 Tax 0..n TaxCode 1 TaxCode is not mapped to CF at all. Percent 0..1 17 Amount 0..1 18 </AllowOrCharge> <Tax> Tax 0..n Tax should be given on line level only when TaxTreatmentCode is NetLineLevel or GrossLineLevel. <TaxCode>1</TaxCode> TaxCode 1 TaxCode is not mapped to CF at all. <Percent>19.00</Percent> Percent 0..1 <Amount>0.67</Amount> Amount 0..1 </Tax> <UnitPrice> UnitPrice 0..1 <Amount>3.55</Amount> Amount 1 15 </UnitPrice> <TotalPrice> TotalPrice 0..1 <Amount>8.60</Amount> Amount 1 18 </TotalPrice> <TotalValue> TotalValue 1 TotalValue is not mapped to CF at all. You can also create an empty element. <Amount/> Amount 1 </TotalValue> FreeText 0..n FreeText is not mapped to CF at all. </InvoiceDetail> <InvoiceSummary> InvoiceSummary 1 <AllowOrCharge> AllowOrCharge 0..n This AllowOrCharge element is used to indicate allowances or charges that are common to the whole invoice.

<AllowOrChargeIdentifier Value="Charge"/> AllowOrChargeIdentifier 1 TXML values are mapped to CF in the following manner: Allow=A, Charge=C <AllowOrChargeCode>HandlingCommision</AllowOrChargeCode> AllowOrChargeCode 0..1 TXML values are mapped to CF in the following manner: HandlingCommision=1, Brokerage=29, BankCharges=30, CourierFee=32, SWIFT=35, FixedLongTerm=60E, Temporary=61E, Standard=62E <AllowOrChargeDescription>HandlingCommision</AllowOrChargeDescription> AllowOrChargeDescription 1 All other allowances and 35 charges should be given as a free form description. Percent 0..1 10 <Amount>10.00</Amount> Amount 0..1 18 <Tax> Tax 0..n <TaxCode/> TaxCode 1 TaxCode is not mapped to CF at all. You can also create an empty element. <Percent>10.00</Percent> Percent 0..1 17 <Amount>1.00</Amount> Amount 0..1 18 </Tax> </AllowOrCharge> Tax 0..n Should be used only when TaxTreatmentCode is NetInvoiceLevel. TaxCode 1 TaxCode is not mapped to CF at all. Percent 0..1 17 Amount 0..1 18 <InvoiceTotals> InvoiceTotals 1 <InvoiceNetValue> InvoiceNetValue 1 <Amount>3.55</Amount> Amount 1 18 </InvoiceNetValue>

<InvoiceGrossValue> InvoiceGrossValue 1 <Amount>8.60</Amount> Amount 1 18 </InvoiceGrossValue> <InvoiceTaxAmount> InvoiceTaxAmount 0..1 <Amount>1.67</Amount> Amount 1 If the tax amount is not given in 18 the Tax element of the InvoiceSummary section, then the invoice tax amount is taken from this element. </InvoiceTaxAmount> InvoiceDiscount 0..1 InvoiceDiscount is not mapped to CF at all. InvoiceCharge 0..1 InvoiceCharge is not mapped to CF at all. <PrepaidAmount> PrepaidAmount 0..1 <Amount>0.00</Amount> Amount 1 18 </PrepaidAmount> <InvoiceAmountPayable> InvoiceAmountPayable 1 <Amount>15.22</Amount> Amount 1 18 </InvoiceAmountPayable> </InvoiceTotals> TaxTotals 0..1 TaxTotals is not mapped to CF at all. <AllowOrChargeTotals> AllowOrChargeTotals 0..1 AllowOrChargeTotals is used to sum up all AllowOrCharge elements from the line level and the InvoiceSummary. E.g. the sum of all AllowOrCharge elements, containing the AllowOrChargeCode "HandlingCommision". <AllowOrCharge> AllowOrCharge 0..n <AllowOrChargeIdentifier Value="Allow"/> AllowOrChargeIdentifier 1 TXML values are mapped to CF in the following manner: Allow=A, Charge=C

AllowOrChargeCode 0..1 TXML values are mapped to CF in the following manner: HandlingCommision=1, Brokerage=29, BankCharges=30, CourierFee=32, SWIFT=35, FixedLongTerm=60E, Temporary=61E, Standard=62E <AllowOrChargeDescription>Discount</AllowOrChargeDescription> AllowOrChargeDescription 1 All other allowances and charges should be given as a free form description. Percent 0..1 Percent should not be used, when AllowOrCharge is used within AllowOrChargeTotals. <Amount>5.05</Amount> Amount 0..1 18 Tax 0..n Tax should not be used, when AllowOrCharge is used within AllowOrChargeTotals. </AllowOrCharge> <AllowOrCharge> <AllowOrChargeIdentifier Value="Charge"/> <AllowOrChargeCode>HandlingCommision</AllowOrChargeCode> <AllowOrChargeDescription>HandlingCommision</AllowOrChargeDescription> TaxCode 1 Percent 0..1 17 Amount 0..1 18 35 10 <Amount>10.00</Amount> </AllowOrCharge> </AllowOrChargeTotals> TaxCodeDescription 0..n TaxCodeDescription is not mapped to CF at all. TaxCode 1 TaxDescription 1

</InvoiceSummary> </Invoice> FreeText 0..n FreeText is not mapped to CF at all. Here is the same invoice in Clepa-Figiefa edifact format: BGM+380+5491332+9 DTM+137:20061004:102 DTM+35:20061004:102 RFF+AAK:557289 RFF+ON:258010 NAD+SU+++Deutsche Autoteile GmbH+Voltastrasse 5+Berlin++30120+DE RFF+API:DE1253222 RFF+VA:DE4311245 NAD+BY+++Teilehändler Schmidt GmbH+Fokkerstrasse 12+München++80120+DE RFF+API:000014070 NAD+DP+++Teilehändler Schmidt GmbH+Fokkerstrasse 12+München++80120+DE RFF+API:000014070 NAD+IV+++Teilehändler Verbund GmbH+Teilstrasse 25+Dortmund++56010+DE RFF+API:000014080 TAX+7+VAT+NLL CUX+2:EUR:4 PAT+3++9 DTM+7:20070102:102 LIN+1++3351642654593:EN PIA+5+265-459:SA IMD+F++:::KO V.W. Golf II 85- QTY+46:1:PCE MOA+203:8.60 PRI+AAA:3.55:::1 RFF+AAK:557289:1 DTM+171:20061004:102

RFF+ON:258010:15 DTM+171:20061004:102 TAX+7+VAT+++:::19.00 MOA+124:0.67 NAD+DP+000014070::9 ALC+A++++:::Discount PCD+1:58.67:13 MOA+204:5.05 UNS+S MOA+9:15.22 MOA+113:0.00 MOA+128:8.60 MOA+125:3.55 TAX+7+VAT MOA+124:1.67 ALC+A++++:::Discount MOA+131:5.05 ALC+C+:1+++:::HandlingCommision MOA+131:10.00

Table 2: Example invoice where taxes are calculated on invoice level TaxTreatmentCode=NetInvoiceLevel Line amounts are net amounts. Taxes will be included in invoice summary; but they are not shown at the line item level. <Invoice> <Document Type="Invoice" Version="1.0"/> <InvoiceHeader> <InvoiceId>5491332</InvoiceId> <InvoiceIssueDate> <Date>20061004</Date> </InvoiceIssueDate> <DesAdvRef> <DocumentNumber>557289</DocumentNumber> <Date>20061004</Date> </DesAdvRef> <OrderRef> <SellerOrderNumber/> <BuyerOrderNumber>258010</BuyerOrderNumber> <Date>20061004</Date> </OrderRef> <TaxTreatmentCode Value="NetInvoiceLevel"/> <InvoiceDueDate> <Date>20070102</Date> </InvoiceDueDate> <SellerParty> <PartyNumber>DE1253222</PartyNumber> <Address> <Name1>Deutsche Autoteile GmbH</Name1> <Street1>Voltastrasse 5</Street1> <PostalCode>30120</PostalCode> <City>Berlin</City> <CountryCode>DE</CountryCode>

</Address> </SellerParty> <BuyerParty> <PartyNumber>000014070</PartyNumber> <Address> <Name1>Teilehändler Schmidt GmbH</Name1> <Street1>Fokkerstrasse 12</Street1> <PostalCode>80120</PostalCode> <City>München</City> <CountryCode>DE</CountryCode> </Address> </BuyerParty> <DeliveryParty> <PartyNumber>000014070</PartyNumber> <Address> <Name1>Teilehändler Schmidt GmbH</Name1> <Street1>Fokkerstrasse 12</Street1> <PostalCode>80120</PostalCode> <City>München</City> <CountryCode>DE</CountryCode> </Address> </DeliveryParty> <InvoiceOrg> <TaxRegistrationNumber>DE4311245</TaxRegistrationNumber> <InvoiceParty> <PartyNumber>000014080</PartyNumber> <Address> <Name1>Teilehändler Verbund GmbH</Name1> <Street1>Teilstrasse 25</Street1> <PostalCode>56010</PostalCode> <City>Dortmund</City> <CountryCode>DE</CountryCode> </Address> </InvoiceParty> </InvoiceOrg>

<Currency>EUR</Currency> </InvoiceHeader> <InvoiceDetail> <PositionNumber>1</PositionNumber> <Quantity UoM="PCE">1</Quantity> <ProductId> <MakerCode/> <ProductNumber>265-459</ProductNumber> <Ean>3351642654593</Ean> </ProductId> <ProductDescription> <ProductName1>KO V.W. Golf II 85-</ProductName1> </ProductDescription> <DeliveryPartyNumber>000014070</DeliveryPartyNumber> <DesAdvRef> <DocumentNumber>557289</DocumentNumber> <Date>20061004</Date> </DesAdvRef> <DesAdvItemRef> <PositionNumber>1</PositionNumber> </DesAdvItemRef> <OrderRef> <SellerOrderNumber/> <BuyerOrderNumber>258010</BuyerOrderNumber> <Date>20061004</Date> </OrderRef> <OrderItemRef> <SellerOrderItemRef/> <BuyerOrderItemRef>15</BuyerOrderItemRef> </OrderItemRef> <AllowOrCharge> <AllowOrChargeIdentifier Value="Allow"/> <AllowOrChargeDescription>Discount</AllowOrChargeDescription> <Percent>58.67</Percent> <Amount>5.05</Amount>

</AllowOrCharge> <UnitPrice> <Amount>3.55</Amount> </UnitPrice> <TotalPrice> <Amount>8.60</Amount> </TotalPrice> <TotalValue> <Amount/> </TotalValue> </InvoiceDetail> <InvoiceSummary> <AllowOrCharge> <AllowOrChargeIdentifier Value="Charge"/> <AllowOrChargeCode>HandlingCommision</AllowOrChargeCode> <AllowOrChargeDescription>HandlingCommision</AllowOrChargeDescription> <Amount>10.00</Amount> <Tax> <TaxCode/> <Percent>10.00</Percent> <Amount>1.00</Amount> </Tax> </AllowOrCharge> <Tax> <TaxCode/> <Percent>19.00</Percent> <Amount>0.67</Amount> </Tax> <Tax> <TaxCode/> <Percent>10.00</Percent> <Amount>1.00</Amount> </Tax> <InvoiceTotals> <InvoiceNetValue>

<Amount>3.55</Amount> </InvoiceNetValue> <InvoiceGrossValue> <Amount>8.60</Amount> </InvoiceGrossValue> <InvoiceTaxAmount> <Amount>1.67</Amount> </InvoiceTaxAmount> <PrepaidAmount> <Amount>0.00</Amount> </PrepaidAmount> <InvoiceAmountPayable> <Amount>15.22</Amount> </InvoiceAmountPayable> </InvoiceTotals> <AllowOrChargeTotals> <AllowOrCharge> <AllowOrChargeIdentifier Value="Allow"/> <AllowOrChargeDescription>Discount</AllowOrChargeDescription> <Amount>5.05</Amount> </AllowOrCharge> <AllowOrCharge> <AllowOrChargeIdentifier Value="Charge"/> <AllowOrChargeCode>HandlingCommision</AllowOrChargeCode> <AllowOrChargeDescription>HandlingCommision</AllowOrChargeDescription> <Amount>10.00</Amount> </AllowOrCharge> </AllowOrChargeTotals> </InvoiceSummary> </Invoice> Here is the same invoice in Clepa-Figiefa edifact format: BGM+380+5491332+9

DTM+137:20061004:102 DTM+35:20061004:102 RFF+AAK:557289 RFF+ON:258010 NAD+SU+++Deutsche Autoteile GmbH+Voltastrasse 5+Berlin++30120+DE RFF+API:DE1253222 RFF+VA:DE4311245 NAD+BY+++Teilehändler Schmidt GmbH+Fokkerstrasse 12+München++80120+DE RFF+API:000014070 NAD+DP+++Teilehändler Schmidt GmbH+Fokkerstrasse 12+München++80120+DE RFF+API:000014070 NAD+IV+++Teilehändler Verbund GmbH+Teilstrasse 25+Dortmund++56010+DE RFF+API:000014080 TAX+7+VAT+NIL CUX+2:EUR:4 PAT+3++9 DTM+7:20070102:102 LIN+1++3351642654593:EN PIA+5+265-459:SA IMD+F++:::KO V.W. Golf II 85- QTY+46:1:PCE MOA+203:8.60 PRI+AAA:3.55:::1 RFF+AAK:557289:1 DTM+171:20061004:102 RFF+ON:258010:15 DTM+171:20061004:102 NAD+DP+000014070::9 ALC+A++++:::Discount PCD+1:58.67:13 MOA+204:5.05 UNS+S

MOA+9:15.22 MOA+113:0.00 MOA+128:8.60 MOA+125:3.55 TAX+7+VAT+++:::19.00 MOA+124:0.67 TAX+7+VAT+++:::10.00 MOA+124:1.00 ALC+A++++:::Discount MOA+131:5.05 ALC+C+:1+++:::HandlingCommision MOA+131:10.00

Table 3: Example invoice without tax calculation Example where a tax exemption is applied. Taxes are not calculated at all. TaxTreatmentCode=NoTaxApplies <Invoice> <Document Type="Invoice" Version="1.0"/> <InvoiceHeader> <InvoiceId>5491332</InvoiceId> <InvoiceIssueDate> <Date>20061004</Date> </InvoiceIssueDate> <DesAdvRef> <DocumentNumber>557289</DocumentNumber> <Date>20061004</Date> </DesAdvRef> <OrderRef> <SellerOrderNumber/> <BuyerOrderNumber>258010</BuyerOrderNumber> <Date>20061004</Date> </OrderRef> <TaxTreatmentCode Value="NoTaxApplies"/> <InvoiceDueDate> <Date>20070102</Date> </InvoiceDueDate> <SellerParty> <PartyNumber>DE1253222</PartyNumber> <Address> <Name1>Deutsche Autoteile GmbH</Name1> <Street1>Voltastrasse 5</Street1> <PostalCode>30120</PostalCode> <City>Berlin</City> <CountryCode>DE</CountryCode> </Address>

</SellerParty> <BuyerParty> <PartyNumber>000014070</PartyNumber> <Address> <Name1>Teilehändler Schmidt GmbH</Name1> <Street1>Fokkerstrasse 12</Street1> <PostalCode>80120</PostalCode> <City>München</City> <CountryCode>DE</CountryCode> </Address> </BuyerParty> <DeliveryParty> <PartyNumber>000014070</PartyNumber> <Address> <Name1>Teilehändler Schmidt GmbH</Name1> <Street1>Fokkerstrasse 12</Street1> <PostalCode>80120</PostalCode> <City>München</City> <CountryCode>DE</CountryCode> </Address> </DeliveryParty> <InvoiceOrg> <TaxRegistrationNumber>DE4311245</TaxRegistrationNumber> <InvoiceParty> <PartyNumber>000014080</PartyNumber> <Address> <Name1>Teilehändler Verbund GmbH</Name1> <Street1>Teilstrasse 25</Street1> <PostalCode>56010</PostalCode> <City>Dortmund</City> <CountryCode>DE</CountryCode> </Address> </InvoiceParty> </InvoiceOrg> <Currency>EUR</Currency>

</InvoiceHeader> <InvoiceDetail> <PositionNumber>1</PositionNumber> <Quantity UoM="PCE">1</Quantity> <ProductId> <MakerCode/> <ProductNumber>265-459</ProductNumber> <Ean>3351642654593</Ean> </ProductId> <ProductDescription> <ProductName1>KO V.W. Golf II 85-</ProductName1> </ProductDescription> <DeliveryPartyNumber>000014070</DeliveryPartyNumber> <DesAdvRef> <DocumentNumber>557289</DocumentNumber> <Date>20061004</Date> </DesAdvRef> <DesAdvItemRef> <PositionNumber>1</PositionNumber> </DesAdvItemRef> <OrderRef> <SellerOrderNumber/> <BuyerOrderNumber>258010</BuyerOrderNumber> <Date>20061004</Date> </OrderRef> <OrderItemRef> <SellerOrderItemRef/> <BuyerOrderItemRef>15</BuyerOrderItemRef> </OrderItemRef> <AllowOrCharge> <AllowOrChargeIdentifier Value="Allow"/> <AllowOrChargeDescription>Discount</AllowOrChargeDescription> <Percent>58.67</Percent> <Amount>5.05</Amount> </AllowOrCharge>

<UnitPrice> <Amount>3.55</Amount> </UnitPrice> <TotalPrice> <Amount>8.60</Amount> </TotalPrice> <TotalValue> <Amount/> </TotalValue> </InvoiceDetail> <InvoiceSummary> <AllowOrCharge> <AllowOrChargeIdentifier Value="Charge"/> <AllowOrChargeCode>HandlingCommision</AllowOrChargeCode> <AllowOrChargeDescription>HandlingCommision</AllowOrChargeDescription> <Amount>10.00</Amount> </AllowOrCharge> <InvoiceTotals> <InvoiceNetValue> <Amount>3.55</Amount> </InvoiceNetValue> <InvoiceGrossValue> <Amount>8.60</Amount> </InvoiceGrossValue> <InvoiceTaxAmount> <Amount>0.00</Amount> </InvoiceTaxAmount> <PrepaidAmount> <Amount>0.00</Amount> </PrepaidAmount> <InvoiceAmountPayable> <Amount>13.55</Amount> </InvoiceAmountPayable> </InvoiceTotals> <AllowOrChargeTotals>

<AllowOrCharge> <AllowOrChargeIdentifier Value="Allow"/> <AllowOrChargeDescription>Discount</AllowOrChargeDescription> <Amount>5.05</Amount> </AllowOrCharge> <AllowOrCharge> <AllowOrChargeIdentifier Value="Charge"/> <AllowOrChargeCode>HandlingCommision</AllowOrChargeCode> <AllowOrChargeDescription>HandlingCommision</AllowOrChargeDescription> <Amount>10.00</Amount> </AllowOrCharge> </AllowOrChargeTotals> </InvoiceSummary> </Invoice> Here is the same invoice in Clepa-Figiefa edifact format: BGM+380+5491332+9 DTM+137:20061004:102 DTM+35:20061004:102 RFF+AAK:557289 RFF+ON:258010 NAD+SU+++Deutsche Autoteile GmbH+Voltastrasse 5+Berlin++30120+DE RFF+API:DE1253222 RFF+VA:DE4311245 NAD+BY+++Teilehändler Schmidt GmbH+Fokkerstrasse 12+München++80120+DE RFF+API:000014070 NAD+DP+++Teilehändler Schmidt GmbH+Fokkerstrasse 12+München++80120+DE RFF+API:000014070 NAD+IV+++Teilehändler Verbund GmbH+Teilstrasse 25+Dortmund++56010+DE RFF+API:000014080 TAX+7+VAT+NTA CUX+2:EUR:4

PAT+3++9 DTM+7:20070102:102 LIN+1++3351642654593:EN PIA+5+265-459:SA IMD+F++:::KO V.W. Golf II 85- QTY+46:1:PCE MOA+203:8.60 RFF+AAK:557289:1 DTM+171:20061004:102 RFF+ON:258010:15 DTM+171:20061004:102 NAD+DP+000014070::9 ALC+A++++:::Discount PCD+1:58.67:13 MOA+204:5.05 UNS+S MOA+9:13.55 MOA+113:0.00 MOA+128:8.60 MOA+125:3.55 TAX+7+VAT MOA+124:0.00 ALC+A++++:::Discount MOA+131:5.05 ALC+C+:1+++:::HandlingCommision MOA+131:10.00