ariba sn edifact invoic implementation guide - help.sap.com

Ariba Network, EDIFACT D98A INVOIC Guidelines

Copyright (c) 1996–2016 Ariba, Inc. All rights reserved. 1 Revised 17 February 2016

Ariba Network EDIFACT INVOIC Implementation

Guide

1 Overview

Ariba Network implements invoices with the cXML InvoiceDetailRequest document. The INVOIC implementation must

ultimately map to an InvoiceDetailRequest and conform to its rules.

INVOIC messages must strictly conform to these implementation guidelines. The INVOIC is implemented using

EDIFACT Syntax Version 3 and with Message Version D98A. DO NOT send D96A; it will not be accepted. The UNH

must read like this:

UNH+msg_reference_id+INVOIC:D:98A:UN'

There are two layout templates of invoices: Regular and Summary. A regular invoice addresses the line items of one

purchase order. A summary invoice covers many purchase orders without listing specific line items.

There are three types of invoices: Standard, Credit Memo, and Debit Memo. Only the Standard invoice can use the Regular

layout template. Credit and Debit Memos can use only the Summary layout template.

Each layout template and invoice type has particular requirements: content that must be present in order to be valid. There

are also some content requirements for INVOIC itself to be satisfied.

This document is intended to assist suppliers to start testing INVOIC messaging with the minimal requirements. It

addresses the base data content for the invoice and what must be included in an INVOIC message. This document does not

attempt to explain how every possible cXML construct is represented in the INVOIC.

Readers should consult the InvoiceDetail.dtd from the cXML specifications alongside the guidelines for INVOIC and this

document.

2 Overall Structure

InvoiceDetailRequest is defined like this:

<!ELEMENT InvoiceDetailRequest

(InvoiceDetailRequestHeader,

(InvoiceDetailOrder+ | InvoiceDetailHeaderOrder+),

InvoiceDetailSummary)>

This means that you have a header section, followed by one or more orders OR one or more summary orders, followed by a

summary section. Regular invoices use the InvoiceDetailOrder and Summary invoices use the

InvoiceDetailHeaderOrder.

Each InvoiceDetailOrder has one or more InvoiceDetailLine elements, so it is in fact three-tired. We use a

two-tiered structure with INVOIC, so only one order can be covered in a regular invoice.

3 Dates

Dates and times in cXML must be specified in a full date / time / time-zone format. Whatever date you enter must

ultimately render as CCYY-MM-DDTHH:MM:SS±HH:MM. For example, “2002-08-13T16:19:23-08:00”. In EDIFACT, it

would be represented as 20020813161923M08:304.



In EDIFACT therefore, it is preferable to use date/time syntax that includes a zone. The following format codes for

DE2379 are supported:

102 CCYYMMDD

203 CCYYMMDDHHMM

204 CCYYMMDDHHMMSS

303 CCYYMMDDHHMMZZZ

304 CCYYMMDDHHMMSSZZZ

Code 304 is recommended, because it covers everything. Anything missing has to be defaulted.

The time zone specified in ZZZ consists of a leading P or M (meaning Plus or Minus) and then two digits from 01 to 12.

For GMT, you may literally use GMT or UT. Note that UTC is slightly distinctive and renders as simply Z. For

convenience, CET has been added and is equivalent to P01.

Note that there is no support for half-hour time zones such as is used in Newfoundland. Also note that some US States

(Indiana, Arizona, Hawaii) do not follow the usual Standard/Daylight time scheme.

The complete list of supported ZZZ values is shown here:

ZZZ Code Description cXML Date/Time Suffix

CET Central European Time +01:00

GMT Greenwich Mean Time = UT (non-coordinated) +00:00

M01 -01:00 -01:00

M02 -02:00 -02:00

M03 -03:00 -03:00

M04 -04:00 (Canada Atlantic) -04:00

M05 -05:00 (US Eastern) -05:00

M06 -06:00 (US Central) -06:00

M07 -07:00 (US Mountain) -07:00

M08 -08:00 (US Pacific) -08:00

M09 -09:00 -09:00

M10 -10:00 -10:00

M11 -11:00 -11:00

M12 -12:00 -12:00

P01 +01:00 +01:00

P02 +02:00 +02:00

P03 +03:00 +03:00

P04 +04:00 +04:00

P05 +05:00 +05:00

P06 +06:00 +06:00

P07 +07:00 +07:00

P08 +08:00 +08:00

P09 +09:00 +09:00

P10 +10:00 +10:00

P11 +11:00 +11:00

P12 +12:00 +12:00

UT Universal Time (non-coordinated) = GMT +00:00

UTC Coordinated Universal Time Z

Z Coordinated Universal Time Z



4 Header Section

The InvoiceDetailRequestHeader element mandates only four things: Invoice Number, Invoice Date, Purpose,

and Operation.

This is easily done with the lead BGM segment and one DTM segment, like this:

BGM+380+INVSP248904188+9'

DTM+3:20000417092318P01:304'

Here, the 380 in BGM01 says “Commercial invoice” which is mapped as purpose=“standard”. INVSP248904188 is the

invoice number and the trailing 9 is the operation=“new”. The DTM+3 has the Invoice Date.

5 Names and Addresses

Names and addresses at the header level are rendered with Group 2 at 0200, lead by the NAD segment. In

InvoiceDetailRequestHeader, they fall into two categories depending on their qualifier. Ship-From (ST), Ship-To (ST) and

Carrier (CA) go into InvoiceDetailShipping. All others go into InvoicePartner.

InvoiceDetailShipping is optional, but if it is used, then Ship-From and Ship-To are both required.

INVOIC D98A requires at least one NAD to identify the invoice sender. The recommended qualifier is II for “Issuer of

invoice”. But SU for “Supplier is also acceptable. If you wish to specify a distinctive Remit-To, then you should include

qualifier RE.

InvoicePartner contacts also support one or more coded identifiers for account identification. This is done with the child

RFF at 0240 Group 3. For convenience, certain name qualifiers will capture the identifier in C082 in NAD as a shortcut for

a certain reference.

If you include a Carrier contact (NAD+CA), then C082 contains a carrier identifier. Remember that if you include

NAD+CA, you incur a obligation to include NAD+SF and NAD+ST.

With most NAD groups, the postal address is not required. You should include it with NAD+SF and NAD+ST. If you do

include a postal address, then one Street, the City, and the two-char ISO-3166 country code are all required. If the country

code is US or CA, then the country-sub-entity is also required and must be a valid state or province digraph.

Telephone numbers are stored in cXML separated into their components. In EDIFACT it is simply one string. So it is

essential to write it properly. You should include the country code, preceded with a plus sign (that’s the element separator,

so escape it), followed by the area or city code, optionally in parenthesis, then the local number. If there is an extension,

precede it with a lowercase ‘x’. Each component of the phone number should be separated with a dash char.

For example, the Ariba Network support number in Amsterdam, NL is +31 23 568 5777. In a COM segment, it should

appear as: COM+?+31-23-568-5777:TE'.

6 Regular Invoices

Regular Invoices address one Purchase Order (PO) and the line items of that PO. The PO itself is referenced at the header

level of the INVOIC and the LIN Group 26 is used to invoice and reference each line item of the PO.

Looking more closely at the InvoiceDetail.dtd, we see this basic structure:

InvoiceDetailRequest

InvoiceDetailRequestHeader

InvoiceDetailOrder+

InvoiceDetailOrderInfo



InvoiceDetailItem+

InvoiceDetailSummary

6.1 InvoiceDetailOrder & InvoiceDetailOrderInfo * Use 0110 Group 1: Reference

To reference one purchase order requires InvoiceDetailOrderInfo. This element contains a choice of information to

reference a particular Purchase Order and/or Master Agreement and optionally a supplier-assigned order tracking number.

We satisfy these requirements with RFF Group 1.

This table shows the RFF and DTM qualifiers to be used for this group:

Reference 0120 RFF Qualifier 0130 DTM Qualifier

Buyer's purchase order

number

ON Order number (purchase) 4 Order date/time

Master agreement identifier AJS Agreement number 126 Contract date

Supplier's order number (from

O/E)

VN Order number (vendor) 4 Order date/time1

Looking at InvoiceDetailOrderInfo, there is a choice of acceptable combinations.

<!ELEMENT InvoiceDetailOrderInfo

( (OrderReference, (MasterAgreementReference | MasterAgreementIDInfo)?,

SupplierOrderInfo?) |

(MasterAgreementReference, OrderIDInfo?, SupplierOrderInfo?) |

(MasterAgreementIDInfo, OrderIDInfo?, SupplierOrderInfo?) |

(OrderIDInfo, SupplierOrderInfo?) |

SupplierOrderInfo )>

Elements ending with "Reference" typically requires a payloadID from cXML. payloadID is not currently supported in EDI

(EDIFACT or ANSI), so the IDInfo types are actually used in mapping.

This narrows it down to three choices, of which one must be used:

a) Master Agreement Number and date, and optionally Purchase Order Number and date, and optionally Supplier

Order Number. Use this if you have a Master Agreement.

b) Purchase Order Number and date, and optionally Supplier Order Number. Use this for Purchase Orders without a

Master Agreement.

c) Supplier Order Number.

Note that in order for a particular Purchase Order in Ariba Network to be invoiced, the Purchase Order Number itself is

required.

This example:

RFF+ON:DO364'

DTM+4:20000415:102'

RFF+AJS:843-2187-5193'

DTM+126:20010903121844M05:304'

RFF+VN:ORD24185'

1 Supplier's order date - cXML does not currently capture this date, but you may include it in the INVOIC.



produces:

<MasterAgreementIDInfo agreementID="843-2187-5193" agreementDate="2001-09-

03T12:18:44-05:00"/>

<OrderIDInfo orderID="DO364" orderDate="2000-04-15T00:00:00+00:00">

<SupplierOrderInfo orderID="ORD24185">

Notice that the order date defaulted to midnight using the time zone from the supplier's profile (who happened to specify

GMT).

6.2 InvoiceDetailItem * Use 1060 Group 26: Line Item

<!ELEMENT InvoiceDetailItem (UnitOfMeasure, UnitPrice,

InvoiceDetailItemReference, SubtotalAmount?,

Tax?, InvoiceDetailLineSpecialHandling?,

InvoiceDetailLineShipping?, GrossAmount?,

InvoiceDetailDiscount?,

InvoiceItemModifications?, TotalCharges?,

TotalAllowances?, TotalAmountWithoutTax?, NetAmount?,

Distribution*, Comments?, Extrinsic*)>

<!ATTLIST InvoiceDetailItem

invoiceLineNumber %uint; #REQUIRED

quantity %r8; #REQUIRED

>

<!ELEMENT InvoiceDetailItemReference (ItemID?, Description?,

(ManufacturerPartID, ManufacturerName)?,

Country?)>

<!ATTLIST InvoiceDetailItemReference

lineNumber %uint; #REQUIRED

serialNumber %string; #IMPLIED

>

6.2.1 Minimum Requirements

To invoice a Purchase Order, at least one line item is required. To build this group, five things are required:

(1) invoiceLineNumber: 1070: LIN.01 (1082). It must be an integer. Each InvoiceDetailItem must

have a distinct invoiceLineNumber.

(2) quantity, (3) UnitOfMeasure: 1110: QTY, with C186.01 (6063) = "47" (Invoiced quantity)

(4) UnitPrice: 1210: Group 27: 1220: MOA, with C516.01 (5025) = "146" (Unit price). Every Money element

in cXML requires a currency code, so Currency is required for all MOA segments.

(5) InvoiceDetailItemReference@lineNumber: This is the line number from the Purchase Order. It

must match LIN.01 (1082) from the ORDERS message you are invoicing. For INVOIC, include C212 in either

LIN or PIA with C212.02 (7143) = "PL" (Purchaser's order line number).

6.2.2 C212: Item Number Identification

C212 is used for most of the identifiers in InvoiceDetailItemReference. In addition to the required Purchase

Order Line Number, it covers the Supplier Item ID, Manufacturer Part ID, and even the Buyer Part ID. Here is the complete

list:

Identifier 7143: Item number type,

coded

D98A Description



ItemID.SupplierPartID VN Vendor item number

ItemID.SupplierPartAuxiliaryID VS Vendor's supplemental item number

ManufacturerPartID MF Manufacturer's (producer's) article

number

serialNumber SN Serial number

Buyer Part ID (renders to Extrinsic) BP Buyer's part number

You may use the item types in any order. Only SN is allowed to repeat. With all others, only the last occurrence is captured.

In using these, there are some pairing requirements.

a) If ItemID is used, then SupplierPartID is required. SupplierPartAuxiliaryID is optional. Simply put, if you use VS,

then VN is required.

b) ManufacturerPartID requires ManufacturerName. The two are paired. So if you use MF, then you must include

1550: Group 35; 1560: NAD.01 (3035) = "MF" (Manufacturer). C058 is required, with C058.01 having the

Manufacturer's Name. Likewise, if you include the NAD with MF, then a C212 with MF is also required.

6.2.3 Serial Numbers

Multiple serial numbers are supported. You may use C212 with SN as many times as you wish. The first one renders to the

serialNumber attribute. Additional serial numbers render to Extrinsic.

6.2.4 Line Item Example

Two examples are shown here. One with only the minimum required information, and the second one demonstrating more

of the C212 usage with Manufacturer Name.

6.2.4.1 Minimal Content Example LIN+1++4:PL'

QTY+47:3:EA'

MOA+146:84.27:EUR'

This produces the following cXML code:

<InvoiceDetailItem invoiceLineNumber="1" quantity="3">

<UnitOfMeasure>EA</UnitOfMeasure>

<UnitPrice>

<Money currency="EUR">84.27</Money>

</UnitPrice>

<InvoiceDetailItemReference lineNumber="4"/>

</InvoiceDetailItem>

6.2.4.2 C212 Usage Example LIN+1++2:PL'

PIA+1+ABC456:VN+red:VS+BK4211:BP'

PIA+1+4488392813:SN+7382956188:SN+6286198724:SN'

QTY+47:2:EA'

FTX+AAI+++No tax+en'

MOA+146:21.40:EUR'






<UnitPrice>


</UnitPrice>

<InvoiceDetailItemReference lineNumber="2">

<ItemID>

<SupplierPartID>ABC456</SupplierPartID>

<SupplierPartAuxiliaryID>red</SupplierPartAuxiliaryID>

</ItemID>

<SerialNumber>4488392813</SerialNumber>



</InvoiceDetailItemReference>

<Extrinsic name="Buyer's Part ID">BK4211</Extrinsic>


6.2.4.3 Price Based Quantity Example LIN+1++4:PL'

QTY+47:3:EA'

MOA+146:84.27:EUR'

PRI+CAL’

APR+WS+10:CSD’

RNG+4+BX:3’




<UnitPrice>


</UnitPrice>

<PriceBasisQuantity quantity="3" conversionFactor="10">

<UnitOfMeasure>BX</UnitOfMeasure>

</PriceBasisQuantity>

<InvoiceDetailItemReference lineNumber="4"/>


Note: Ariba Network does not support the Description field for PriceBasisQuantity.

6.3 InvoiceDetailServiceItem Use 1060 Group 26: Line Item

cXML makes this definition for the Invoice Service Line Item. The required data is in bold.

<!ELEMENT InvoiceDetailServiceItem

( InvoiceDetailServiceItemReference, SubtotalAmount,

Period?, (UnitOfMeasure, UnitPrice)?,

Tax?, GrossAmount?, InvoiceDetailDiscount?, NetAmount?,

Distribution*, Comments?, Extrinsic*)>

<!ATTLIST InvoiceDetailServiceItem


quantity %r8; #IMPLIED

referenceDate %datetime.tz; #IMPLIED

>

<!ELEMENT InvoiceDetailServiceItemReference



(Classification*,

ItemID?,

Description?)>

<!ATTLIST InvoiceDetailServiceItemReference

lineNumber %uint; #IMPLIED

>

6.3.1 Minimum Requirements

To invoice a Purchase Order, at least one line item is required. To build this group, five things are required:

(1) invoiceLineNumber: 1070: LIN.01 (1082). It must be an integer. Each InvoiceDetailServiceItem must

have a distinct invoiceLineNumber.

(2) quantity, (3) UnitOfMeasure: 1110: QTY, with C186.01 (6063) = "47" (Invoiced quantity)

(4) UnitPrice: 1210: Group 27: 1220: MOA, with C516.01 (5025) = "146" (Unit price). Every Money element

in cXML requires a currency code, so Currency is required for all MOA segments.

(5) InvoiceDetailServiceItemReference@lineNumber: This is the line number from the Purchase

Order. It must match LIN.01 (1082) from the ORDERS message you are invoicing. For INVOIC, include C212 in

either LIN or PIA with C212.02 (7143) = "PL" (Purchaser's order line number).

6.3.2 C212: Item Number Identification

C212 is used for most of the identifiers in InvoiceDetailItemReference. In addition to the required Purchase

Order Line Number, it covers the Supplier Item ID, Manufacturer Part ID, and even the Buyer Part ID. Here is the complete

list:

Identifier 7143: Item number type,

coded

D98A Description

ItemID.SupplierPartID MP Service Item Part Number

ItemID.SupplierPartAuxiliaryID VS Vendor's supplemental item number

Classification CC Classification Id

Buyer Part ID (renders to Extrinsic) BP Buyer's part number

If there are more than one occurrence of these qualifiers, only the last occurrence is captured.

In using these, there are some pairing requirements.

c) If ItemID is used, then SupplierPartID is required. SupplierPartAuxiliaryID is optional. Simply put, if you use VS,

then MP/VN is required.

6.3.3 Line Item Example

6.3.3.1 C212 Usage Example LIN+1++4:PL'

PIA+1+ABC456:MP+red:VS+BK4211:BP'

QTY+47:3:EA'

MOA+146:84.27:EUR'


<InvoiceDetailServiceItem invoiceLineNumber="1" quantity="3">




<UnitPrice>


</UnitPrice>

<InvoiceDetailServiceItemReference lineNumber="4" serialNumber="4488392813">

<ItemID>

<SupplierPartID>ABC456</SupplierPartID>

<SupplierPartAuxiliaryID>red</SupplierPartAuxiliaryID>

</ItemID>


<Extrinsic name="Buyer's Part ID">BK4211</Extrinsic>


7 Header Invoices

Header Invoices reference one whole Purchase Order on each line item of the invoice. The line items of each Purchase

Order are not detailed. Standard Invoices can be in summary form. Credit Memos and Debit Memos must be in summary

form.

For Header Invoices, the cXML structure is:

InvoiceDetailRequest

InvoiceDetailRequestHeader

InvoiceDetailHeaderOrder+

InvoiceDetailOrderInfo

InvoiceDetailOrderSummary

InvoiceDetailSummary

7.1 InvoiceDetailHeaderOrder and InvoiceDetailOrderSummary * Use 1060 Group 26: Line Item

Each Purchase Order being covered in a Header Invoice requires an occurrence of 1060 Group 26: LIN. Each PO requires

InvoiceDetailOrderInfo and InvoiceDetailOrderSummary.

7.1.1 InvoiceDetailOrderInfo * Use 1350 Group 30: Reference

At the line item level, we simply use Group 30: Reference the same way we used the header level Group 1: Reference. The

requirements are the same.

7.1.2 InvoiceDetailOrderSummary <!ELEMENT InvoiceDetailOrderSummary (SubtotalAmount, Tax?,

InvoiceDetailLineSpecialHandling?,

InvoiceDetailLineShipping?,

GrossAmount?, InvoiceDetailDiscount?,

NetAmount?, Comments?, Extrinsic*)>

<!ATTLIST InvoiceDetailOrderSummary


>

This element requires invoiceLineNumber and SubtotalAmount.

(1) invoiceLineNumber: 1070: LIN.01 (1082). It must be an integer. Each InvoiceDetailItem must

have a distinct invoiceLineNumber. This is the same usage as in 6.2.1.

(2) SubtotalAmount: 1210: Group 27: Monetary Amount: 1220: MOA, with C516.01 (5025) = "289" (Subtotal

amount). Every Money element in cXML requires a currency code, so Currency is required for all MOA segments.



7.1.3 Minimum Content Example

Section 6.1 shows examples for using InvoiceDetailOrderInfo with its various options. It is shown here with just

an order number.

LIN+1'

MOA+289:358.82:EUR'

RFF+ON:ORDSP82778'


<InvoiceDetailHeaderOrder>

<InvoiceDetailOrderInfo>

<OrderIDInfo orderID="ORDSP82778"/>

</InvoiceDetailOrderInfo>

<InvoiceDetailOrderSummary invoiceLineNumber="1"/>

</InvoiceDetailHeaderOrder>

8 InvoiceDetailSummary <!ELEMENT InvoiceDetailSummary (SubtotalAmount, Tax, SpecialHandlingAmount?,

ShippingAmount?, GrossAmount?,

InvoiceDetailDiscount?,

InvoiceHeaderModifications?, TotalCharges?,

TotalAllowances?, TotalAmountWithoutTax?, NetAmount,

DepositAmount?, DueAmount?)>

InvoiceDetailSummary requires SubtotalAmount, Tax, and NetAmount.

(1) SubtotalAmount: 2140: Group 50: Monetary Amount: 2150 MOA, with C516.01 (5025) = "289" (Subtotal

amount).

(2) Tax: 2220: Group 53: Allowance or Charge: 2230: ALC, with ALC.01 (5463) = "C" and C214.01 (7161) =

"TX" (Tax). The Tax element requires both Money and Description. For Money, use 2250 MOA, with MOA.01 =

"24" (Charge amount). For Description, use 2260 FTX, with FTX.01 (4451) = "ALC" (Allowance/charge

information).

(3) InvoiceHeaderModifications: ALC 0710: Group 16: C214.01 (7161) corresponding to modifications. Refer

to Notes section of ALC for the code list.(4) TotalCharges: 2140: Group 50: Monetary Amount: 2150 MOA, with

C516.01 (5025) = 259

(5) TotalAllowances: 2140: Group 50: Monetary Amount: 2150 MOA, with C516.01 (5025) = 260

(6) TotalAmountWithoutTax: 2140: Group 50: Monetary Amount: 2150 MOA, with C516.01 (5025) = ZZZ

(7) NetAmount: 2140: Group 50: Monetary Amount: 2150 MOA, with C516.01 (5025) = "



9 Special Features

9.1 Using Tax Details with Value-Added Taxation (VAT) and Triangular Transactions

Ariba Invoicing supports Value-Added Tax (VAT) charges and also taxation of Triangular Transactions, which is a

requirement within Europe.

This section addresses the complex mapping required to implement such data in the INVOIC.

As mentioned earlier, all EDI data inbound to Ariba Network must ultimately be translated to cXML before it can be finally

processed by the network and routed to Ariba Buyer. INVOIC messages must translate to the

InvoiceDetailRequest. The section of elements being addressed here is Tax, TaxDetail, and

TriangularTransactionLawReference.

A Contact role of Ultimate Customer has been added to represent the party ultimately purchasing the goods. This is covered

in NAD Group 2 at 0200, where NAD01="UD". Within the NAD group, RFF with qualifier VA can be used to provide a

VAT Registration Number for partners involved in the transaction.

The top level Tax element itself requires a simple description with a total monetary amount. This is implemented with

ALC Group 16 at 0710 for the header level (invoice summary totals), and ALC Group 39 at 1670 for the line item level.

One or more TaxDetail elements can be provided within Tax to detail the tax charge breakdown. At the header level,

each occurrence of TAX Group 22 at 0920 produces one TaxDetail structure. Tax details are also supported at the line

item level with TAX Group 44 at 1860.

VAT with Triangular Transactions involves integrating four things with a Tax Detail:

1. Tax Point Date, which refers to the date on which VAT becomes due.

2. Payment Date, which indicates the date when payment must be made.

3. Triangular Transaction indicator, that this VAT tax charge represents a triangular transaction.

4. Triangular Transaction Law Reference, a text string identifying the relevant triangulation law for the transaction.

Since these data are not provided within the TAX group, they must be gathered from neighbouring segments within the

ALC group at the header level (Group 16) only. To implement this, the TAX segment must have a category of VAT.

TAX07 (3446) contains the relevant VAT Registration Number. An RFF group with qualifier VA contains a matching

VAT Registration Number. This is how the RFF group is connected to the TAX group. The RFF group contains one of both

DTM segments with qualifiers 131 and 140 to provide the dates. (Points 1 & 2 above.)

TAX03.01 (5289) may optionally contain the code "TT", which tags it as a Triangular Transaction. (Point 3 above.)

The Triangular Transaction Law Reference (Point 4 above) requires a long string that only the FTX segment at 0740 can

support. Since most of the various charges represented by the ALC group require a description string, FTX01 is usually set

to "AAI" for General information. FTX04 (C108) is usually captured for this purpose. To cover the special case of a

Triangular Transaction in the ALC Tax group (ALC05="TX"), FTX01 is set to "TXD" for Tax declaration. When this is

set, FTX is read differently. FTX03.01 (4441) is now captured as the high level Tax description (for example, "Total

Taxes"), and FTX04 provides an array of Law Reference strings. To attach a particular reference string to a TAX group we

go back to the RFF group providing the dates. If the TAX is marked as a Triangular Transaction, then RFF01.03 (1156) is

read as an index to FTX04: C108 has five (5) components, so DE1156 contains an integer value of 1, 2, 3, 4, or 5. FTX05

defines the language code for both FTX03 and FTX04. Any supported language may be used.2

Several conditions must be true in order for this to work:

2 Note that FTX qualifier TXD is not strictly reserved for this purpose. It simply alters the interpretation of FTX, moving

the total tax description from FTX04 over to FTX03, and enabling Triangulation Law Reference capture from FTX04. It is

perfectly valid to use the TXD qualifier within the ALC tax charge group whether Triangulation is applicable or not.



1. 0930 TAX segment must have a category of VAT. TAX02.01 (5153) = "VAT".

2. 0930 TAX segment must have a VAT Registration Number for the relevant party in TAX07 (3446).

3. 0760 RFF segment must have a qualifier of VA. RFF01.01 (1153) = "VA".

4. 0760 RFF segment must have a matching VAT Registration Number in RFF01.02 (1154).

These four conditions are required to associate Tax Point Date and Payment Due Date with the Tax Detail. Additionally,

the following five conditions must also be true to merge a Law Reference:

5. 0930 TAX must indicate a Triangular Transaction. TAX03.01 (5289) = "TT".

6. 0740 FTX must qualify itself as a Tax declaration. FTX01 (4451) = "TXD".

7. 0740 FTX must have the total tax description in FTX03.01 (4441).

8. 0740 FTX must provide one or more Law Reference strings in FTX04 (C108).

9. 0760 RFF must identify a string to capture from FTX's C108 in RFF01.03 (1156).

In summary, there are four levels of detail that can be implemented for a tax charge. Levels 1 and 2 are supported at both

header and line item. Levels 3 and 4 are supported only in the header.

1. Summary tax with a description and an amount.

2. Detailed breakdown of tax charges, including VAT.

3. Tax Point and Payment Due dates for VAT tax charges.

4. Triangulation Law Reference for VAT tax charges.

Four examples are given here to show how this is assembled and interpreted. Each example takes the previous example to

the next progressive level. NAD's Ultimate Customer and VAT Id are shown in the first example only. (While it is still part

of the message, the other examples take it for granted.) All positional numbers and segment groups are shown for clarity.

9.1.1 Example 1: Summary tax with a description and an amount

An invoice for Ariba's Amsterdam office has a total summary tax amount of 250 EUR. Any description can be given. 0200:SG2 (NAD)

0210: NAD+UD++Ariba Netherlands'

0240:SG3 (RFF)

0250: RFF+VA:123456789B19'

0710:SG16 (ALC)

0720: ALC+C++++TX'

0740: FTX+AAI+++Total taxes+en'

0840:SG20 (MOA)

0850: MOA+8:250:EUR'

9.1.2 Example 2: Detailed breakdown of tax charges, including VAT

A TAX group is added to show that 250 EUR as VAT related. All tax categories defined in D.98A are supported TAX02.01

(5153). Multiple TAX groups are also allowed, but the tax amounts should sum to the total given in 0850 MOA. Two other

things are being exhibited here, but are not required at this level:

FTX+TXD is being used, to show that it can be.

TAX07 contains a VAT number. The supplier's implementation is allowed to write it there, but it is neither

required nor used.



0710:SG16 (ALC)

0720: ALC+C++++TX'

0740: FTX+TXD++Total taxes++en'

0840:SG20 (MOA)

0850: MOA+8:250:EUR'

0920:SG22 (TAX-MOA)

0930: TAX+7+VAT:::Netherlands++1428.57+:::17.5++123456789B19'

0940: MOA+124:250:EUR'

Ariba Network reads this tax detail as:

Purpose: tax [TAX01]

Category: Value-Added Tax (VAT) [TAX02.01]

Location: Netherlands [TAX02.04]

Taxable Amount: 1428.57 EUR [TAX04]

Tax Rate: 17.5% [TAX05.04]

Tax Amount: 250 EUR [MOA+124]

9.1.3 Example 3: Tax Point and Payment Due dates for VAT tax charges

An RFF group is added to provide the relevant dates. Multiple TAX groups are allowed. And they do not all have to have

referential dates. TAX groups do not all have to be of category VAT. But referential date association is supported for the

VAT category only. Multiple VAT TAX groups are allowed, and each one can have its own pair of referential dates. If they

must refer to the same VAT Registration Number, then a uniquifier may be concatenated with a colon ( : ) and a unique

value. This is shown here with two VAT charges being applied to two separate charges on the invoice and referencing the

same party. The dates are different to illustrate that they can be. Note the bolded VAT numbers with unique concatenations.

0710:SG16 (ALC)

0720: ALC+C++++TX'

0740: FTX+TXD++Total taxes++en'

0750:SG17 (RFF-DTM)

0760: RFF+VA:123456789B19?:A'

0770: DTM+131:20030713080000P01:304'

0770: DTM+140:20030720170000P01:304'

0750:SG17 (RFF-DTM)

0760: RFF+VA:123456789B19?:B'

0770: DTM+131:20030714080000P01:304'

0770: DTM+140:20030721170000P01:304'

0840:SG20 (MOA)

0850: MOA+8:250:EUR'

0920:SG22 (TAX-MOA)

0930: TAX+7+VAT:::Netherlands++1257.14+:::17.5++123456789B19?:A'

0940: MOA+124:220:EUR'

0930: TAX+7+VAT:::Netherlands++171.43+:::17.5++123456789B19?:B'

0940: MOA+124:30:EUR'

Ariba Network reads these tax details as:







Tax Rate: 17.5% [TAX05.04]


Tax Point Date: July 13, 2003, at 8.00am CET

Payment Due Date: July 20, 2003, at 5.00pm CET





Tax Rate: 17.5% [TAX05.04]


Tax Point Date: July 14, 2003, at 8.00am CET

Payment Due Date: July 21, 2003, at 5.00pm CET

9.1.4 Example 4: Triangulation Law Reference for VAT tax charges

Finally, the first of the two tax charges is designated as being triangular. They could both be designated as such. And they

could even share the same Law Reference. Notice the value of 1 in RFF01.03, referencing the first component of FTX04,

and the code TT in TAX03.01, designating it as triangular.

Notice also that the law reference string is 68 characters long. The limit is 70. Because of the indexed array implementation

of FTX04 (C108) here, string concatenation across components is not currently supported. If your string is too long, then

you must abbreviate it.

0710:SG16 (ALC)

0720: ALC+C++++TX'

0740: FTX+TXD++Total taxes+Triangulation, article 28c,E paragraph 3 of the 6th EU

VAT Directive+en'

0750:SG17 (RFF-DTM)

0760: RFF+VA:123456789B19?:A:1'

0770: DTM+131:20030713080000P01:304'

0770: DTM+140:20030720170000P01:304'

0750:SG17 (RFF-DTM)

0760: RFF+VA:123456789B19?:B'

0770: DTM+131:20030714080000P01:304'

0770: DTM+140:20030721170000P01:304'

0840:SG20 (MOA)

0850: MOA+8:250:EUR'

0920:SG22 (TAX-MOA)

0930: TAX+7+VAT:::Netherlands+TT+1257.14+:::17.5++123456789B19?:A'

0940: MOA+124:220:EUR'

0930: TAX+7+VAT:::Netherlands++171.43+:::17.5++123456789B19?:B'

0940: MOA+124:30:EUR'

Ariba Network reads the first tax detail as:







Tax Rate: 17.5% [TAX05.04]


Tax Point Date: July 13, 2003, at 8.00am CET [DTM+131]

Payment Due Date: July 20, 2003, at 5.00pm CET [DTM+140]

Triangulation: yes [TAX03.01="TT"]

Triangulation Law Reference: Triangulation, article 28c,E paragraph 3 of the 6th EU VAT Directive

[FTX04.[RFF01.03]]

The second tax detail is the same as in Example 3.

This final example renders in a cXML InvoiceDetailRequest as follows:

<InvoicePartner>

<Contact role="subsequentBuyer">

<Name xml:lang="en">Ariba Netherlands</Name>

</Contact>

<IdReference identifier="123456789B19" domain="vatID"></IdReference>

</InvoicePartner>

...

<InvoiceDetailSummary>

...

<Tax>

<Money currency="EUR">250</Money>

<Description xml:lang="en">Total taxes</Description>

<TaxDetail purpose="tax" category="vat" percentageRate="17.5" taxPointDate="2003-07-

13T08:00:00+01:00" paymentDate="2003-07-20T17:00:00+01:00" isTriangularTransaction="yes">

<TaxableAmount>


</TaxableAmount>

<TaxAmount>


</TaxAmount>

<TaxLocation xml:lang="en">Netherlands</TaxLocation>

<Description xml:lang="en">Value added tax</Description>

<TriangularTransactionLawReference xml:lang="en">Triangulation, article 28c,E

paragraph 3 of the 6th EU VAT Directive

</TriangularTransactionLawReference>

</TaxDetail>

<TaxDetail purpose="tax" category="vat" percentageRate="17.5" taxPointDate="2003-07-

13T08:00:00+01:00" paymentDate="2003-07-20T17:00:00+01:00">

<TaxableAmount>


</TaxableAmount>

<TaxAmount>


</TaxAmount>


<Description xml:lang="en">Value added tax</Description>

</TaxDetail>

</Tax>

9.2 RFF Segments Support all Qualifiers The two standalone RFF groups, in the header section at 0110 (SG-1) and line item at 1350 (SG-30) support all qualifiers.

Any qualifier defined in EDIFACT D98A for DE1153 may be used. Those which are listed in this guide have specific

mappings to cXML. All others render to Extrinsic segments. Note that only the RFF segment itself is rendered. Child

segments of the RFF group, such as DTM, are not rendered as children of Extrinsic.



This is a particularly useful feature for customization. For example, a Statement Number can be sent using qualifier ADP.

RFF+ADP:6453221~

… produces

<Extrinsic name="Statement Number">6453221</Extrinsic>

The Extrinsic@name came from the EDIFACT definition. The data came from C506.02[1154].

The qualifier mapping is also available for the NAD child RFF at 0250 (SG-3 @0240). This RFF is used to produce an

IdReference element, and the DE1153 qualifier maps to the @domain attribute, and DE1154 to the identifier

@attribute. Here a cXML style value is returned.

RFF+ABO*3355864~

… produces

<IdReference domain="originatorsReference" identifier="3355864" />

The complete list of codes and their actual mappings is provided in Appendix A.

9.3 Using Ariba Invoice AP Plus Feature

Ariba Processing Plus (AP Plus) is an automated payment service offered by Ariba Network. It charges payment cards

(PCards) when suppliers submit invoices. It sends level-three (L3) accounting information to the card processor for use in

transactionreports sent to the buying organization. Both trading partners must subscribe to AP Plus before they can use it.

To use this feature in an invoice, two cXML elements must be present:

The isInformationOnly attribute of InvoiceDetailRequest must be present and set to “yes”, and a header level Extrinsic

element with its name attribute set to “action:InitiatePayment”. This example from the cXML Solutions Guide:

<InvoiceDetailRequestHeader

invoiceID="inv777"

purpose="standard"

operation="new"

invoiceDate="2001-12-03"

isInformationOnly="yes">

…

<Extrinsic name="action:InitiatePayment" />

Both of these highlighted elements can be represented from the EDIFACT INVOIC Invoice by including:

0020 BGM03="55"

0120 RFF+ZZZ:action?:InitiatePayment'

Note that BGM03 is used for the @operation attribute, where a new invoice would use BGM03=”9” to mean

@operation=”new”. Code “55” is implemented to map to both @operation=”new” and @isInformationOnly=”yes”.

RFF+ZZZ is a special extention to support this feature. It maps the name only from DE1154. The Extrinsic data is not

mapped.

The above example in INVOIC form would look like this:

BGM+380+inv777+55'

RFF+ZZZ:action?:InitiatePayment'



See the cXML Solutions Guide, Chapter 9 “Invoices” / Implementation Hints / AP Plus for more information.

10 Sample Data

Sample data shows how a complete INVOIC message should be formatted. All of them are marked as test (UNB11 = ‘1’).

The examples are all similar and lend themselves to diff type comparisons.

10.1 Line Item Detail Invoice with No Tax Details UNA:+.? '

UNB+UNOC:3+ABCMUSICSUPPLY:ZZZ+ARIBAEDI:ZZZ:AN02000012345+030910:1059+1++INVOIC++1++1'

UNH+LineItemNoTax+INVOIC:D:98A:UN'

BGM+380+DO091003TESTINV01+9'

DTM+3:20030910105920M07:304'

RFF+ON:DO091003'

DTM+4:20030910:102'

RFF+VN:DO091003'

NAD+SO++Aaron Copeland+Aaron Copeland+123 Symphony Street+San Francisco+CA+94107+US'

CTA+ZZZ+default'

[email protected]:EM'

CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'

NAD+RE++XYZ Bank+XYZ Bank+111 5th Avenue+New York+NY+10007+US'

RFF+AP:00000-11111'

RFF+RT:123456789'

CTA+ZZZ+default'


CTA+ZZZ+work'

COM+12121234567:TE'

PAT+22++5:3:D:10'

PCD+12:10:13'

PAT+22++5:3:D:20'

PCD+12:5:13'

PAT+22++5:3:D:30'

PCD+12:0:13'

PAT+20++5:3:D:40'

PCD+15:5:13'

PAT+20++5:3:D:50'

PCD+15:10:13'

ALC+C++++SAA'

MOA+8:6:USD'

ALC+C++++TX'

FTX+TXD++no tax++en'

MOA+8:0:USD'

LIN+1++1:PL'

PIA+1+ID001:VN'

IMD+F++:::Power Cord+en'

QTY+47:2:EA'

MOA+146:99.99:USD'

MOA+66:199.98:USD'

MOA+203:199.98:USD'

NAD+SF++Philadelphia++555 W. Any Street+Philadelphia+PA+19002+US'

CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'

NAD+ST++Music Insurance Co. - San Francisco+Aaron Copeland+123 Symphony Street+San

Francisco+CA+94107+US'

CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'



ALC+N+default+++AEC:175:92:ABC123456789'

FTX+ABN+++Purchasing:Production Control+en'

MOA+8:199.98:USD'

ALC+C++++SAA'

MOA+8:3:USD'

LIN+2++2:PL'

PIA+1+ID002:VN'


QTY+47:2:EA'

MOA+146:79.99:USD'

MOA+66:159.98:USD'

MOA+203:159.98:USD'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'



MOA+8:159.98:USD'

ALC+C++++SAA'

MOA+8:3:USD'

UNS+S'

MOA+289:359.96:USD'

MOA+339:365.96:USD'

MOA+340:365.96:USD'

MOA+9:365.96:USD'

UNT+86+LineItemNoTax'

UNZ+1+1'

10.2 Line Item Detail Invoice with Tax Details UNA:+.? '


UNH+LineItemWithTx+INVOIC:D:98A:UN'

BGM+380+DO091003TESTINV01TAX+9'

DTM+3:20030910105920M07:304'

RFF+ON:DO091003'

DTM+4:20030910:102'

RFF+VN:DO091003'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'


RFF+AP:00000-11111'

RFF+RT:123456789'

CTA+ZZZ+default'


CTA+ZZZ+work'

COM+12121234567:TE'

PAT+22++5:3:D:10'

PCD+12:10:13'

PAT+22++5:3:D:20'

PCD+12:5:13'

PAT+22++5:3:D:30'

PCD+12:0:13'



PAT+20++5:3:D:40'

PCD+15:5:13'

PAT+20++5:3:D:50'

PCD+15:10:13'

ALC+C++++SAA'

MOA+8:6:USD'

ALC+C++++TX'

FTX+TXD++total tax++en'

MOA+8:35.96:USD'

TAX+7+STT:::CA++359.96+:::8'

MOA+124:28.78:USD'

TAX+7+FET++359.96+:::2'

MOA+124:7.18:USD'

LIN+1++1:PL'

PIA+1+ID001:VN'


QTY+47:2:EA'

MOA+146:99.99:USD'

MOA+66:219.96:USD'

MOA+203:219.96:USD'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'

ALC+N+Buyer assigned accounting code 1+++AEC:175:92:ABC123456789'


MOA+8:219.96:USD'

ALC+C++++SAA'

MOA+8:3:USD'

ALC+C++++TX'

FTX+TXD++total item tax++en'

MOA+8:19.98:USD'

TAX+7+STT:::CA+++:::8'

MOA+124:15.99:USD'

MOA+125:199.98:USD'

TAX+7+FET+++:::2'

MOA+124:3.99:USD'

MOA+125:199.98:USD'

LIN+2++2:PL'

PIA+1+ID002:VN'


QTY+47:2:EA'

MOA+146:79.99:USD'

MOA+66:175.96:USD'

MOA+203:175.96:USD'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'

ALC+N+Buyer assigned accounting code 1+++AEC:175:92:ABC123456789'




MOA+8:175.96:USD'

ALC+C++++SAA'

MOA+8:3:USD'

ALC+C++++TX'

FTX+TXD++total item tax++en'

MOA+8:15.98:USD'

TAX+7+STT:::CA+++:::8'

MOA+124:12.79:USD'

MOA+125:159.98:USD'

TAX+7+FET+++:::2'

MOA+124:3.19:USD'

MOA+125:159.98:USD'

UNS+S'

MOA+289:359.96:USD'

MOA+339:401.92:USD'

MOA+340:401.92:USD'

MOA+9:401.92:USD'

UNT+108+LineItemWithTx'

UNZ+1+1'

10.3 Line Item Detail Invoice with taxPointDate UNA:+.? '


UNH+LineItemWithTx+INVOIC:D:98A:UN'



UNT+108+LineItemWithTx'

UNZ+1+1'

10.4 Header Level Invoice with One PO UNA:+.? '


UNH+HdrInvoice-1PO+INVOIC:D:98A:UN'

BGM+380+DO091003TESTHDRINV01+9'

DTM+3:20030910105920M07:304'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'


RFF+AP:00000-11111'

RFF+RT:123456789'

CTA+ZZZ+default'


CTA+ZZZ+work'

COM+12121234567:TE'

ALC+A++++DI'

PCD+12:10:13'

MOA+8:41.19:USD'

ALC+C++++SAA'

MOA+8:6:USD'

ALC+C++++SH'

MOA+8:10:USD'

ALC+C++++TX'


MOA+8:35.96:USD'

LIN+1'

MOA+289:359.96:USD'

MOA+38:370.73:USD'

RFF+ON:DO091003'

DTM+4:20030910:102'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'

ALC+A++++DI'

PCD+12:10:13'

MOA+8:41.19:USD'

ALC+C++++SAA'



MOA+8:6:USD'

ALC+C++++SH'

MOA+8:10:USD'

ALC+C++++TX'

FTX+TXD++tax on order++en'

MOA+8:35.96:USD'

UNS+S'

MOA+289:359.96:USD'

MOA+339:411.92:USD'

MOA+340:370.73:USD'

MOA+9:370.73:USD'

UNT+58+HdrInvoice-1PO'

UNZ+1+1'

10.5 Header Level Invoice with Two POs UNA:+.? '


UNH+HdrInvoice-2PO+INVOIC:D:98A:UN'

BGM+380+DO091003TESTHDRINV02+9'

DTM+3:20030910105920M07:304'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'


RFF+AP:00000-11111'

RFF+RT:123456789'

CTA+ZZZ+default'


CTA+ZZZ+work'

COM+12121234567:TE'

ALC+A++++DI'

PCD+12:10:13'

MOA+8:64.69:USD'

ALC+C++++SAA'

MOA+8:11:USD'

ALC+C++++SH'

MOA+8:20:USD'

ALC+C++++TX'


MOA+8:55.96:USD'

LIN+1'

MOA+289:359.96:USD'

MOA+38:370.73:USD'

RFF+ON:DO091003'

DTM+4:20030910:102'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'

ALC+A++++DI'

PCD+12:10:13'

MOA+8:41.19:USD'

ALC+C++++SAA'

MOA+8:6:USD'



ALC+C++++SH'

MOA+8:10:USD'

ALC+C++++TX'


MOA+8:35.96:USD'

LIN+2'

MOA+289:200:USD'

MOA+38:223.25:USD'

RFF+ON:DO091004'

DTM+4:20030910:102'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'

ALC+A++++DI'

PCD+12:5:13'

MOA+8:11.75:USD'

ALC+C++++SAA'

MOA+8:5:USD'

ALC+C++++SH'

MOA+8:10:USD'

ALC+C++++TX'


MOA+8:20:USD'

UNS+S'

MOA+289:559.96:USD'

MOA+339:646.92:USD'

MOA+340:582.23:USD'

MOA+9:582.23:USD'

UNT+84+HdrInvoice-2PO'

UNZ+1+1'



10.6 Credit Memo UNA:+.? '


UNH+CreditMemo+INVOIC:D:98A:UN'

BGM+381+DO091003TestCMINV01+9'

DTM+3:20030910105920M07:304'

FTX+ADU+++Item1 - We invoiced you for a qty of 2. Only 1 was shipped.+en'

ALC+C++++TX'


MOA+8:-9.99:USD'

LIN+1'

MOA+289:-99.99:USD'

RFF+ON:DO091003'

DTM+4:20030910:102'

RFF+VN:DO091003'

UNS+S'

MOA+289:-99.99:USD'

MOA+340:-109.98:USD'

MOA+9:-109.98:USD'

UNT+17+CreditMemo'

UNZ+1+1'

10.7 Bank Adapter details BGM+380+DO091003TESTINV01+9'

DTM+3:20030910105920M07:304'

RFF+ON:DO091003'

DTM+4:20030910:102'

RFF+VN:DO091003'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'


RFF+AP:00000-11111'

RFF+RT:123456789'

NAD+RB++XYZ Bank+XYZ Bank+111 5th Avenue+New York+NY+10007+US'

RFF+PY:122234'

RFF+AGE:Ganesh'

RFF+AGD:Saving'

RFF+RT:123456789'

RFF+AFN:XYZ Bank'

NAD+BF++XYZ Bank+XYZ Bank+111 5th Avenue+New York+NY+10007+US'

RFF+PY:122234'

RFF+AGE:Ganesh'

RFF+AGD:Saving'

RFF+PQ:swiftNumber001'

RFF+AGC:iban0000001'

RFF+AFN:XYZ Bank'

CTA+ZZZ+default'


CTA+ZZZ+work'

COM+12121234567:TE'

PAT+22++5:3:D:10'

PCD+12:10:13'

PAT+22++5:3:D:20'

PCD+12:5:13'

PAT+22++5:3:D:30'

PCD+12:0:13'



PAT+20++5:3:D:40'

PCD+15:5:13'

PAT+20++5:3:D:50'

PCD+15:10:13'

ALC+C++++SAA'

MOA+8:6:USD'

ALC+C++++TX'

FTX+TXD++no tax++en'

MOA+8:0:USD'

LIN+1++1:PL'

PIA+1+ID001:VN'


QTY+47:2:EA'

MOA+146:99.99:USD'

MOA+66:199.98:USD'

MOA+203:199.98:USD'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'



MOA+8:199.98:USD'

ALC+C++++SAA'

MOA+8:3:USD'

LIN+2++2:PL'

PIA+1+ID002:VN'


QTY+47:2:EA'

MOA+146:79.99:USD'

MOA+66:159.98:USD'

MOA+203:159.98:USD'


CTA+ZZZ+default'


CTA+ZZZ+work'

COM+14151234567:TE'

COM+14151112222:FX'



CTA+ZZZ+default'


COM+14151234567:TE'

COM+14151112222:FX'



MOA+8:159.98:USD'

ALC+C++++SAA'

MOA+8:3:USD'

UNS+S'

MOA+289:359.96:USD'

MOA+339:365.96:USD'

MOA+340:365.96:USD'

MOA+9:365.96:USD'

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE cXML SYSTEM "http://svcrel.ariba.com/schemas/cXML/1.2.025/InvoiceDetail.dtd">

<cXML payloadID="AN51000000425-AN02000000147-2009-07-28T02:43:25+05:30-207739178-403-



[email protected]" timestamp="2009-07-28T02:43:25+05:30" xml:lang="en">

<Header>

<From>

<Credential domain="NetworkID">

<Identity>AN02000000147</Identity>

</Credential>

</From>

<To>



</Credential>

</To>

<Sender>



<SharedSecret>welcome</SharedSecret>

</Credential>

<UserAgent>EDI Gateway</UserAgent>

</Sender>

</Header>

<Request deploymentMode="production">

<InvoiceDetailRequest>

<InvoiceDetailRequestHeader invoiceID="DO091003TESTINV01" purpose="standard"

operation="new" invoiceDate="2003-09-10T10:59:20-07:00" invoiceOrigin="supplier">

<InvoiceDetailHeaderIndicator/>

<InvoiceDetailLineIndicator isShippingInLine="yes" isAccountingInLine="yes"/>

<InvoicePartner>

<Contact role="soldTo">

<Name xml:lang="en">Aaron Copeland</Name>

<PostalAddress>

<DeliverTo>Aaron Copeland</DeliverTo>

<Street>123 Symphony Street</Street>

<City>San Francisco</City>

<State>CA</State>

<PostalCode>94107</PostalCode>

<Country isoCountryCode="US">UNITED STATES</Country>

</PostalAddress>

<Email name="default">[email protected]</Email>

<Phone name="work">

<TelephoneNumber/>

</Phone>

<Fax name="work">

<TelephoneNumber/>

</Fax>

</Contact>

</InvoicePartner>

<InvoicePartner>

<Contact role="remitTo">

<Name xml:lang="en">XYZ Bank</Name>

<PostalAddress>

<DeliverTo>XYZ Bank</DeliverTo>

<Street>111 5th Avenue</Street>

<City>New York</City>

<State>NY</State>



</PostalAddress>

</Contact>

<IdReference identifier="00000-11111" domain="accountReceivableID"/>

<IdReference identifier="123456789" domain="bankRoutingID"/>

</InvoicePartner>

<InvoicePartner>

<Contact role="receivingBank">


<PostalAddress>






<State>NY</State>



</PostalAddress>

</Contact>

<IdReference identifier="122234" domain="accountID"/>

<IdReference identifier="Ganesh" domain="accountName"/>

<IdReference identifier="Saving" domain="accountType"/>

<IdReference identifier="123456789" domain="bankRoutingID"/>

<IdReference identifier="XYZ Bank" domain="branchName"/>

</InvoicePartner>

<InvoicePartner>

<Contact role="wireReceivingBank">


<PostalAddress>




<State>NY</State>



</PostalAddress>


<Phone name="work">

<TelephoneNumber/>

</Phone>

</Contact>

<IdReference identifier="122234" domain="accountID"/>

<IdReference identifier="Ganesh" domain="accountName"/>

<IdReference identifier="Saving" domain="accountType"/>

<IdReference identifier="swiftNumber001" domain="swiftID"/>

<IdReference identifier="iban0000001" domain="ibanID"/>

<IdReference identifier="XYZ Bank" domain="branchName"/>

</InvoicePartner>

<InvoiceDetailPaymentTerm payInNumberOfDays="10" percentageRate="10"/>



<InvoiceDetailPaymentTerm payInNumberOfDays="40" percentageRate="-5"/>

<InvoiceDetailPaymentTerm payInNumberOfDays="50" percentageRate="-10"/>

<Extrinsic name="invoiceSubmissionMethod">EDI</Extrinsic>

<Extrinsic name="invoiceSourceDocument">PurchaseOrder</Extrinsic>

</InvoiceDetailRequestHeader>

<InvoiceDetailOrder>

<InvoiceDetailOrderInfo>

<OrderReference>

<DocumentReference/>

</OrderReference>

<SupplierOrderInfo orderID="DO091003"/>

</InvoiceDetailOrderInfo>



<UnitPrice>

<Money currency="USD">99.99</Money>

</UnitPrice>


<ItemID>

<SupplierPartID>ID001</SupplierPartID>

</ItemID>

<Description xml:lang="en">Power Cord</Description>


<SubtotalAmount>


</SubtotalAmount>

<InvoiceDetailLineShipping>



<InvoiceDetailShipping>

<Contact role="shipFrom">

<Name xml:lang="en">Philadelphia</Name>

<PostalAddress>

<Street>555 W. Any Street</Street>

<City>Philadelphia</City>

<State>PA</State>



</PostalAddress>


<Phone name="work">

<TelephoneNumber/>

</Phone>

<Fax name="work">

<TelephoneNumber/>

</Fax>

</Contact>

<Contact role="shipTo">

<Name xml:lang="en">Music Insurance Co. - San Francisco</Name>

<PostalAddress>



<City>SanFrancisco</City>

<State>CA</State>



</PostalAddress>


<Phone name="default">

<TelephoneNumber/>

</Phone>

<Fax name="default">

<TelephoneNumber/>

</Fax>

</Contact>

</InvoiceDetailShipping>

<Money currency="USD">3</Money>

</InvoiceDetailLineShipping>

<NetAmount>


</NetAmount>

<Distribution>

<Accounting name="default">

<AccountingSegment id="ABC123456789">

<Name xml:lang="en">Purchasing</Name>

<Description xml:lang="en">Production Control</Description>

</AccountingSegment>

</Accounting>

<Charge>


</Charge>

</Distribution>




<UnitPrice>


</UnitPrice>


<ItemID>

<SupplierPartID>ID002</SupplierPartID>

</ItemID>

<Description xml:lang="en">Power Cord</Description>


<SubtotalAmount>




</SubtotalAmount>

<InvoiceDetailLineShipping>


<Contact role="shipFrom">

<Name xml:lang="en">Philadelphia</Name>

<PostalAddress>

<Street>555 W. Any Street</Street>

<City>Philadelphia</City>

<State>PA</State>



</PostalAddress>


<Phone name="work">

<TelephoneNumber/>

</Phone>

<Fax name="work">

<TelephoneNumber/>

</Fax>

</Contact>

<Contact role="shipTo">

<Name xml:lang="en">Music Insurance Co. - San Francisco</Name>

<PostalAddress>



<City>SanFrancisco</City>

<State>CA</State>



</PostalAddress>


<Phone name="default">

<TelephoneNumber/>

</Phone>

<Fax name="default">

<TelephoneNumber/>

</Fax>

</Contact>



</InvoiceDetailLineShipping>

<NetAmount>


</NetAmount>

<Distribution>


<AccountingSegment id="ABC123456789">

<Name xml:lang="en">Purchasing</Name>

<Description xml:lang="en">Production Control</Description>


</Accounting>

<Charge>


</Charge>

</Distribution>


</InvoiceDetailOrder>


<SubtotalAmount>


</SubtotalAmount>

<Tax>


<Description xml:lang="en">no tax</Description>

</Tax>



<ShippingAmount>


</ShippingAmount>

<GrossAmount>


</GrossAmount>

<NetAmount>


</NetAmount>

<DueAmount>


</DueAmount>

</InvoiceDetailSummary>

</InvoiceDetailRequest>

</Request>

</cXML>

INVOIC Invoice Message

Introduction:

A message claiming payment for goods or services supplied under conditions agreed between the seller and the buyer.



The United Nations Standard Invoice Message, with correct data qualification, serves also as the specification for Debit

Note and Credit Note messages. Throughout this document, the reference to 'Invoice' may be interpreted as conveying the

wider meaning of 'Invoice/Credit Note/Debit Note'.

Heading Section:

Pos. Seg. Base User Group Notes and

No. ID Name Status Status Max.Use Repeat Comments 0010 UNH Message Header M M 1 0020 BGM Beginning of Message M M 1 0030 DTM Date/Time/Period M M 35 0070 FTX Free Text C O 10 0110 Segment Group 1: RFF-DTM C O 99 0120 RFF Reference M M 1 0130 DTM Date/Time/Period C O 1

0200 Segment Group 2: NAD-SG3-SG5 C M 99 0210 NAD Name and Address M M 1 0240 Segment Group 3: RFF C D 9999 0250 RFF Reference M M 1

0300 Segment Group 5: CTA-COM C O 5 0310 CTA Contact Information M M 1 0320 COM Communication Contact C M 5

0400 Segment Group 8: PAT-PCD C O 10 0410 PAT Payment Terms Basis M M 1 0430 PCD Percentage Details C M 1

0710 Segment Group 16: ALC-FTX-SG17-SG19-SG20-SG22

C M 9999

0720 ALC Allowance or Charge M M 1 0740 FTX Free Text C D 1 0750 Segment Group 17: RFF-DTM C O 5 0760 RFF Reference M M 1 0770 DTM Date/Time/Period C O 2

0810 Segment Group 19: PCD C O 1 0820 PCD Percentage Details M M 1

0840 Segment Group 20: MOA C M 2 0850 MOA Monetary Amount M M 1

0920 Segment Group 22: TAX-MOA C O 5 0930 TAX Duty/Tax/Fee Details M M 1 0940 MOA Monetary Amount C M 1

Detail Section:


No. ID Name Status Status Max.Use Repeat Comments

1060 Segment Group 26: LIN-PIA-IMD-QTY-ALI-DTM-FTX-SG27-SG30-SG35-SG39

C M 9999999

1070 LIN Line Item M M 1 1080 PIA Additional Product Id C O 25 1090 IMD Item Description C O 10 1110 QTY Quantity C D 1



1130 ALI Additional Information C O 1 1140 DTM Date/Time/Period C O 35 1190 FTX Free Text C O 5 1210 Segment Group 27: MOA C M 10 1220 MOA Monetary Amount M M 1 1290 Segment Group 29: PRI C O 1 1 1300 PRI Price Details M M 1 1320 APR Additional Price Information C M 1 1330 RNG Range Details C M 1

1350 Segment Group 30: RFF-DTM C D 10 1360 RFF Reference M M 1 1370 DTM Date/Time/Period C O 1

1550 Segment Group 35: NAD-SG36-SG38 C O 99 1560 NAD Name and Address M M 1 1580 Segment Group 36: RFF C O 5 1590 RFF Reference M M 1

1640 Segment Group 38: CTA-COM C O 5 1650 CTA Contact Information M M 1 1660 COM Communication Contact C M 5

1670 Segment Group 39: ALC-FTX-SG41-SG42-SG44

C O 30

1680 ALC Allowance or Charge M M 1 1710 FTX Free Text C D 1 1750 Segment Group 41: PCD C O 1 1760 PCD Percentage Details M M 1

1780 Segment Group 42: MOA C O 2 1790 MOA Monetary Amount M M 1

1860 Segment Group 44: TAX-MOA C O 5 1870 TAX Duty/Tax/Fee Details M M 1 1880 MOA Monetary Amount C M 2



Section Control:


No. ID Name Status Status Max.Use Repeat Comments 2120 UNS Section Control M M 1

Summary Section:


No. ID Name Status Status Max.Use Repeat Comments

2140 Segment Group 50: MOA M M 100 2150 MOA Monetary Amount M M 1

2270 UNT Message Trailer M M 1



Segment: UNH Message Header

Position: 0010

Group: Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A service segment starting and uniquely identifying a message. The message type code for the

Invoice message is INVOIC.

Note: Invoice messages conforming to this document must contain the following data in segment

UNH, composite S009:

Data element 0065 INVOIC 0052 D 0054 98A 0051 UN

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example: UNH+1+INVOIC:D:98A:UN'

Data Element Summary

Data Component Base User

Element Element Name Attributes Attributes

0062 MESSAGE REFERENCE NUMBER M an..14 M

Unique message reference assigned by the sender.

S009 MESSAGE IDENTIFIER M M

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

0065 Message type identifier M an..6 M

Code identifying a type of message and assigned by its controlling agency.

INVOIC Invoice message

A code to identify the invoice message.

0052 Message type version number M an..3 M

Version number of a message type.

D Draft version/UN/EDIFACT Directory

Message approved and issued as a draft message (Valid for

directories published after March 1993 and prior to March 1997).

Message approved as a standard message (Valid for directories

published after March 1997). 0054 Message type release number M an..3 M

Release number within the current message type version number (0052).

98A Release 1998 - A

Message approved and issued in the first 1998 release of the

UNTDID (United Nations Trade Data Interchange Directory). 0051 Controlling agency M an..2 M

Code identifying the agency controlling the specification, maintenance and publication of

the message type. UN UN/ECE/TRADE/WP.4

United Nations Economic UN Economic Commission for Europe

(UN/ECE), Committee on the development of trade (TRADE),

Working Party on facilitation of international trade procedures

(WP.4). 0057 Association assigned code C an..6 X

Code, assigned by the association responsible for the design and maintenance of the

message type concerned, which further identifies the message. 0068 COMMON ACCESS REFERENCE C an..35 X

Reference serving as a key to relate all subsequent transfers of data to the same business

case or file.



S010 STATUS OF THE TRANSFER C X

Statement that the message is one in a sequence of transfers relating to the same topic.

0070 Sequence message transfer number M n..2 X

Number assigned by the sender indicating that the message is an addition or change of a

previously sent message relating to the same topic. 0073 First/last sequence message transfer indication C a1 X

Indication used for the first and last message in a sequence of the same type of message

relating to the same topic.



Segment: BGM Beginning of Message

Position: 0020

Group: Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A segment by which the sender must uniquely identify the invoice by means of its type and

number and when necessary its function.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example:

BGM+380+INVSP248904188+9+AB'

DTM+3:20000417092318P01:304'

produces

<InvoiceDetailRequestHeader invoiceID="INVSP248904188" purpose="standard"

operation="new" invoiceDate="2000-04-17T09:23:18+01:00">




C002 DOCUMENT/MESSAGE NAME C M

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

1001 Document/message name, coded C an..3 M

Document/message identifier expressed in code.

81 Credit note related to goods or services

Document message used to provide credit information related to a

transaction for goods or services to the relevant party. Line level credit memo

In case the INVOIC is line level credit memo,

Ariba Network will default all the quantities and

amounts to a negative value.

380 Commercial invoice

Document/message claiming payment for goods or

services supplied under conditions agreed

between seller and buyer.

381 Credit note

Document/message for providing credit

information to the relevant party.

383 Debit note

Document/message for providing debit

information to the relevant party.

1131 Code list qualifier C an..3 X

Identification of a code list.

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

Code identifying the agency responsible for a code list.

1000 Document/message name C an..35 X

Plain language identifier specifying the function of a document/message.

C106 DOCUMENT/MESSAGE IDENTIFICATION C M

Identification of a document/message by its number and eventually its version or revision.

1004 Document/message number C an..35 M



Reference number assigned to the document/message by the issuer.

1056 Version C an..9 O

To specify the version number or name of an object.

1060 Revision number C an..6 O

To specify a revision number.

1225 MESSAGE FUNCTION, CODED C an..3 O

Code indicating the function of the message.

9 Original

Initial transmission related to a given transaction.

operation="new"

55 Notification only

The receiver may use the notification information for analysis only.

operation="new" and isInformationOnly="yes"

Note that code 55 implies operation="new" and also says

isInformationOnly="yes". This code is required for the AP Plus

feature. 4343 RESPONSE TYPE, CODED C an..3 X

Code specifying the type of acknowledgment required or transmitted.



Segment: DTM Date/Time/Period

Position: 0030

Group: Level: 1

Usage: Mandatory

Max Use: 35

Purpose: A segment specifying general dates and, when relevant, times related to the whole message. The

segment must be specified at least once to identify the invoice date. Examples of the use of this

DTM segment is: "shipped on date" or "delivery date".

The Date/time/period segment within other Segment groups should be used whenever the

date/time/period requires to be logically related to another specified data item e.g. Payment due

date is specified within the PAT Segment group.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example: DTM+110:200109030830CET:303'




C507 DATE/TIME/PERIOD M M

Date and/or time, or period relevant to the specified date/time/period type.

2005 Date/time/period qualifier M an..3 M

Code giving specific meaning to a date, time or period.

3 Invoice date/time

[2376] Date when a Commercial Invoice is issued.

Invoice date is always required.

110 Ship date, originally scheduled

Shipping date is used in the InvoiceDetailShipping structure. If you

include this date, then NAD+SF and NAD+ST are both required. 194 Start date/time

Date/time on which a period starts.

Used with 206 for Service Period start/end. As a pair, they form

the Period element in InvoiceDetailHeader.

Note: 194 and 206 must be used together. In case, one is used

without the other, the invoice will fail.

Example:

DTM+194:20040801:102'

DTM+206:20040901:102'

produces...

<Period startDate="2004-08-01T00:00:00+00:00" endDate="2004-

09-01T00:00:00+00:00" />

Notice that the startDate and endDate attributes in the Period

element are of type datetime.tz. So, when the time and timezones

are not specified, they are defaulted. In this example, the service is

specified for a month, beginning Aug 1 to Sep 1, 2004. If the end

date is Aug 31 with no time specified, it will default to midnight

and not include the specified day.

206 End date/time



Date/time on which a period (from - to) ends.

Used with 194 for Service Period start/end.

2380 Date/time/period C an..35 M

The value of a date, a date and time, a time or of a period in a specified representation.

2379 Date/time/period format qualifier C an..3 M

Specification of the representation of a date, a date and time or of a period.

102 CCYYMMDD

Calendar date: C = Century ; Y = Year ; M = Month ; D = Day.

203 CCYYMMDDHHMM

Calendar date including time with minutes: C=Century; Y=Year;

M=Month; D=Day; H=Hour; M=Minutes. 204 CCYYMMDDHHMMSS

Calendar date including time with seconds: C=Century;Y=Year;

M=Month;D=Day;H=Hour;M=Minute;S=Second. 303 CCYYMMDDHHMMZZZ

See 203 plus Z=Time zone.





Segment: FTX Free Text

Position: 0070

Group: Level: 1

Usage: Conditional (Optional)

Max Use: 10

Purpose: A segment with free text information, in coded or clear form, used when additional information

is needed but cannot be accommodated within other segments. In computer to computer

exchanges such text will normally require the receiver to process this segment manually.

Dependency Notes:

Semantic Notes:

Comments:

Usage Notes: Used/Optional

Notes: Examples:

Comment:

FTX+ADU+++Thank you for allowing us to meet your business needs+en'

Extrinsic:

FTX+ZZZ++Terms+Discount if you pay real fast:Penalty if you are slow'




4451 TEXT SUBJECT QUALIFIER M an..3 M

Code specifying subject of a free text.

ADU Note

Text subject is note.

ZZZ Mutually defined

Note contains information mutually defined by trading partners.

4453 TEXT FUNCTION, CODED C an..3 X

Code specifying how to handle the text.

C107 TEXT REFERENCE C D

Coded reference to a standard text and its source.

If FTX01 (4451) = "ZZZ", then FTX03 (C107) is required. If FTX01 = "ADU" then

FTX03 is not used. 4441 Free text identification M an..17 M

Free text in coded form.





C108 TEXT LITERAL C O

Free text; one to five lines.

4440 Free text M an..70 M

Free text field available to the message sender for information.

4440 Free text C an..70 O










3453 LANGUAGE, CODED C an..3 O

Code of language (ISO 639-1988).



Group: RFF Segment Group 1: Reference

Position: 0110

Group: Level: 1


Max Use: 99

Purpose: A group of segments for giving references and where necessary, their dates, related

identification numbers, locations, measurements, quantities, free text and monetary amounts,

relating to the whole message, e.g. contract information, import or export license information,

despatch advice information.


Notes: Examples:

Referencing purchase order number and date:

RFF+ON:DO364'

DTM+4:20000415:102'

Master agreement and date:

RFF+AJS:843-2187-5193'

DTM+126:20010903121844M05:304'

Supplier's order number (from order entry):

RFF+VN:ORD24185'

Group 1: Reference is used for Regular type invoices only, where one Purchase Order or

Master Agreement is being referenced at the Invoice Header Level.

Segment Summary

Pos. Seg. Req. Max. Group:

No. ID Name Des. Use Repeat M 0120 RFF Reference M 1 O 0130 DTM Date/Time/Period C 1



Segment: RFF Reference

Position: 0120 (Trigger Segment)

Group: Segment Group 1 (Reference) Conditional (Optional)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the reference by its number and where appropriate a line number within a

document.

Dependency Notes:

Semantic Notes:

Comments:




C506 REFERENCE M M

Identification of a reference.

1153 Reference qualifier M an..3 M

Code giving specific meaning to a reference segment or a reference number.

AEG Customer specification number

Retrieval number for a specification defined by customer.

This is Buyer's SystemID number.

Example: RFF+AEG+SAP01'

<Header>

...

<To>

<Credential domain="SystemID">

<Identity>RFF.C506.02</Identity>

....

</Header>

AJS Agreement number

A number specifying an agreement between

parties.

Master Agreement

IV Invoice number

[1334] Reference number assigned by the seller to a Commercial

Invoice. Example:

RFF+IV:INVSP248904179'

DTM+3:20000415103137P01:304'

Every line level credit memo needs to have an invoice reference.

This is used only for referring to an invoice. This forms the

DocumentReference element in the InvoiceDetailRequestHeader.

Inclusion of the referring invoice date is recommended. Use with

DTM+3. MA Ship notice/manifest number

Ship Notice, from earlier DESADV.

OI Previous invoice number

Reference number identifying a previously issued invoice.

Example:

RFF+OI:INVSP248904179'



DTM+384:20000415103137P01:304'

Used only for referring to a previous invoice. This forms the

DocumentReference element in the InvoiceDetailRequestHeader.

Inclusion of the referring invoice date is recommended. Use with

DTM+384. ON Order number (purchase)

[1022] Reference number assigned by the buyer to an order.

Purchase order number, from ORDERS.

VN Order number (vendor)

Reference number assigned by supplier to a buyer's purchase order.

Supplier sales-order number.

ZZZ Mutually defined reference number

Number based on party agreement.

Example:

RFF+ZZZ:action?:InitiatePayment'

produces

<Extrinsic name="action:InitiatePayment></Extrinsic>

Use RFF+ZZZ to produce a simple name-only Extrinsic, with the

name in DE1154. This can be used to implement the AP+ feature,

as shown in the example above. 1154 Reference number C an..35 M

Identification number the nature and function of which can be qualified by an entry in data

element 1153 Reference qualifier. 1156 Line number C an..6 X

Number of the line in the document/message referenced in 1154 Reference number.

4000 Reference version number C an..35 X

To uniquely identify a reference by its version number.




Position: 0130


Level: 2


Max Use: 1

Purpose: A segment specifying the date/time related to the reference.

Dependency Notes:

Semantic Notes:

Comments:









3 Invoice date/time

[2376] Date when a Commercial Invoice is issued.

It can be used only with RFF+IV. Otherwise, it will not be

captured. 4 Order date/time

[2010] Date when an order is issued.

Use with RFF+ON. It can be used with RFF+VN, but is not

captured. 111 Manifest/ship notice date

Use with RFF+MA

126 Contract date

[2326] Date when a Contract is agreed.

Use with RFF+AJS

384 Previous invoice date

Indicates the date which was allocated to a previous invoice.

Use with RFF+OI only.





102 CCYYMMDD


203 CCYYMMDDHHMM




M=Month;D=Day;H=Hour;M=Minute;S=Second.



303 CCYYMMDDHHMMZZZ






Group: NAD Segment Group 2: Name and Address

Position: 0200

Group: Level: 1

Usage: Conditional (Required)

Max Use: 99

Purpose: A group of segments identifying the parties with associated information.

Usage Notes: Mandatory

Notes: Examples:

For a carrier:

NAD+CA+WTEK:172:182+Wheel-Tek Courier'

RFF+CN:4218357491286'

produces


<CarrierIdentifier domain="SCAC">WTEK</CarrierIdentifier>

<CarrierIdentifier domain="companyName">Wheel-Tek Courier</CarrierIdentifier>

<ShipmentIdentifier>4218357491286</ShipmentIdentifier>

For a supplier:

NAD+II+4278:ZZZ:92+Supplies, Inc.'

DOC+380+:5'

produces

<InvoiceDetailRequestHeader ... isInformationOnly="yes">

...

<InvoicePartner>

<Contact role="issuerOfInvoice">

<Name xml:lang="en">Supplies, Inc.</Name>

</Contact>

<IdReference domain="accountPayableId">4278</IdReference>

INVOIC requires Group 2: Name and Address to identify the supplier or invoicer. So

NAD+II is required.

If either NAD+SF or NAD+ST is used, then the other is required. NAD+CA is also part

of the InvoiceDetailShipping set. So if NAD+CA is used, then NAD+SF and NAD+ST

are both required.

The PostalAddress portion is not required, but it is recommended for NAD+SF and

particularly NAD+ST if used. NAD04 - NAD09 are used to build the PostalAddress.

If PostalAddress is included, then the following components/elements are required: C059

(Street), DE3164 (City name), and DE3207 (Country, coded).

If DE3207 = "US" or "CA" then DE3229 is also required and must be a valid US State or

Canadian Province code, two chars in length.

Note that for DE3207, only two-char ISO-3166 country codes may be used.



Segment Summary


No. ID Name Des. Use Repeat M 0210 NAD Name and Address M 1

0240 Segment Group 3: Reference C 9999

0300 Segment Group 5: Contact Information C 5



Segment: NAD Name and Address


Group: Segment Group 2 (Name and Address) Conditional (Required)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying names and addresses of the parties, in coded or clear form, and their

functions relevant to the invoice. Identification of the seller and buyer parties is mandatory for

the invoice message. It is recommended that where possible only the coded form of the party ID

should be specified e.g. The Buyer and Seller are known to each other, thus only the coded ID is

required, but the Consignee or Delivery address may vary and would have to be clearly

specified, preferably in structured format.

Dependency Notes:

Semantic Notes:

Comments:




3035 PARTY QUALIFIER M an..3 M

Code giving specific meaning to a party.

BT Party to be billed for other than freight (bill to)

Party receiving invoice excluding freight costs.

Represents the Buyer's Accounts Payable Department - the main

recipient of an invoice.

If C082 is used with DE3055="91", then DE3039 is captured as

the Supplier-assigned customer id for the buyer, forming

<IdReference domain="accountReceivableID">.

<InvoicePartner>

<Contact role="billTo">

...

<IdReference domain="accountReceivableID">DE3039, where

DE3055="91"</IdReference>

CA Carrier

(3126) Party undertaking or arranging transport of goods between

named points. Identifies the carrier commissioned for the shipment. Its use is

optional. C082 is recommended, but is not mandatory.

If C082 is used with NAD+CA, then DE1131 must be "172" to

identify a carrier code and DE3055 must be one of 3, 9, 12, 16,

182. DE3039 is captured as a <CarrierIdentifier>.

RFF (0250) with DE1153="CN" is required and DE1154 is

captured to form <ShipmentIdentifier>.

NAD+CA is the only contact that uses RFF+CN.

If NAD+CA is used, then NAD+SF and NAD+ST are both

required.




<Contact role="carrierCorporate">

<Name>DE3124</Name>

...

</Contact>

<CarrierIdentifier

domain="companyName">DE3124</CarrierIdentifier>

<CarrierIdentifier domain=C082.DE3055

(translated)>C082.DE3039</CarrierIdentifier>

<ShipmentIdentifier>RFF.DE1154, where

RFF.DE1153="CN"</ShipmentIdentifier>

...


FR Message from

Party where the message comes from.

<InvoicePartner>

<Contact role="from">

...

II Issuer of invoice

(3028) Party issuing an invoice.

Issuer of Invoice is REQUIRED.


the Buyer-assigned vendor id for the supplier, forming

<IdReference domain="accountPayableID">.

If the invoice is for information only, such as for a prepaid order,

then one occurrence of DOC (0280) may be included attesting to

that fact. DOC (0280) may be used with NAD+II.

<InvoicePartner>

<Contact role="issuerOfInvoice">

...

<IdReference domain="accountPayableID">DE3039,

if DE3055="92"</IdReference>

PK Contact party

Party to contact.

<InvoicePartner>

<Contact role="taxRepresentative">

RE Party to receive commercial invoice remittance

Party to whom payment for a commercial invoice

or bill should be remitted.

Represents where the Buyer is expected to send the remittance.

C082 is not captured, but you may include an RFF+RT and

RFF+PY identifier for bank remittance, if desired.

<InvoicePartner>

<Contact role="remitTo">

SF Ship from

Identification of the party from where goods

will be or have been shipped.

NAD+SF and NAD+ST are used together to form

InvoiceDetailShipping.

If NAD+SF is used, then NAD+ST is required.




the addressID of the ShipFrom, forming <Contact

role="shipFrom" addressID=" ...."> SO Sold to if different than bill to

<InvoicePartner>

<Contact role="soldTo">

ST Ship to

Identification of the party to where goods

will be or have been shipped.

NAD+ST and NAD+SF are used together to form

InvoiceDetailShipping.

If NAD+ST is used, then NAD+SF is required.


the addressID of the ShipTo, forming <Contact role="shipTo"

addressID=" ....">

UD Ultimate customer

The final recipient of goods.

Used for reporting Value-Added Tax (VAT) in a "Triangular

Transaction".

This contact may be used with RFF (@0240 SG3) with qualifier

VA ("VAT registration number").

Triangular transaction VAT information is included with TAX in

the ALC group.

<InvoicePartner>

<Contact role="subsequentBuyer"> RB Receiving Bank

<InvoicePartner>

<Contact role="receivingBank"> Either NAD+RB or NAD+BF is required for banking

details. It is recommended to use with NAD+FR and

NAD+RE. See sample data 10.7 for more details

You must include these mandatory fields

Either (NAD+AGC and NAD+PQ) or NAD+RT

NAD+PY

NAD+AGD

NAD+AGE

BF Wire Receiving Bank

<InvoicePartner>

<Contact role="wireReceivingBank"> Either NAD+RB or NAD+BF is required for banking

details. It is recommended to use with NAD+FR and

NAD+RE. See sample data 10.7 for more details

You must include these mandatory fields

Either (NAD+AGC and NAD+PQ) or NAD+RT

NAD+PY

NAD+AGD

NAD+AGE

C082 PARTY IDENTIFICATION DETAILS C O

Identification of a transaction party by code.

C082 is used with InvoicePartner type contacts and with Shipping contact CA (Carrier).

InvoicePartner contacts may contain an optional IdReference code to accompany the name.



Certain identifiers are commonly associated with certain Name and Address types.

With NAD+CA, use DE1131="172" (Carrier) and DE3055 a choice of 3, 9, 12, 16, or 182.

For NAD qualifiers BT, RE, II, SO, C082 are optional. If you use it, then set

DE1131="ZZZ" and DE3055 a choice of 91 or 92. See the notes for each NAD qualifier

for which the code is captured. 3039 Party identification M an..35 M

Code identifying a party involved in a transaction.

1131 Code list qualifier C an..3 M


172 Carrier code

Used with agency codes (DE3055) 3, 9, 12, 16, and 182, and with

party qualifier (DE3035) CA only. ZZZ Mutually defined

Used with agency codes (DE3055) 91 and 92, and with party

qualifiers (DE3035) BT, RE, SO, II only. 3055 Code list responsible agency, coded C an..3 M


3 IATA (International Air Transport Association)

<CarrierIdentifier domain="IATA">(DE3039)</CarrierIdentifier>

9 EAN (International Article Numbering association)

<CarrierIdentifier domain="EAN">(DE3039)</CarrierIdentifier>

12 UIC (International union of railways)

Western and Eastern European railways association (35 networks).

UIC with its legal body (CIT) produce codes and reglementations

that are internationally recognized and accepted by all European

railways and official bodies. <CarrierIdentifier domain="UIC">(DE3039)</CarrierIdentifier>

16 DUNS (Dun & Bradstreet)

<CarrierIdentifier domain="DUNS">(DE3039)</CarrierIdentifier>

91 Assigned by seller or seller's agent

92 Assigned by buyer or buyer's agent

182 US, Standard Carrier Alpha Code (Motor)

Organisation maintaining the SCAC lists and transportation

operating in North America. <CarrierIdentifier domain="SCAC">(DE3039)</CarrierIdentifier>

C058 NAME AND ADDRESS C M

Unstructured name and address: one to five lines.

3124 Name and address line M an..35 M

Free form name and address description.

3124 Name and address line C an..35 X








C080 PARTY NAME C O

Identification of a transaction party by name, one to five lines. Party name may be

formatted.



Each DE3036 produces one <DeliverTo> in a <PostalAddress>. A maximum of five

<DeliverTo> elements can be generated.

Within a <PostalAddress>, <DeliverTo> is supposed to represent specific recipient name(s)

of a package or envelope. This may also include intra-office routing information, such as a

department, a floor, office, or cube number.

Use of <DeliverTo> is entirely optional. 3036 Party name M an..35 M

Name of a party involved in a transaction.

3036 Party name C an..35 O








3045 Party name format, coded C an..3 X

Specification of the representation of a party name.

C059 STREET C D

Street address and/or PO Box number in a structured address: one to four lines.

3042 Street and number/p.o. box M an..35 M

Street and number in plain language, or Post Office Box No.

3042 Street and number/p.o. box C an..35 O






3164 CITY NAME C an..35 D

Name of a city (a town, a village) for addressing purposes.

3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9 D

Identification of the name of sub-entities (state, province) defined by appropriate

governmental agencies. A State or Province code or abbreviation. If DE3207 = "US" or "CA", then DE3229 is

required and must be a valid two-char US State or Canadian Province code. 3251 POSTCODE IDENTIFICATION C an..9 O

Code defining postal zones or addresses.

3207 COUNTRY, CODED C an..3 D an..2

Identification of the name of a country or other geographical entity as specified in ISO

3166. Must be a valid two-char ISO-3166 Country Code.




Position: 0240


Level: 2

Usage: Conditional (Dependent)

Max Use: 9999

Purpose: A group of segment for giving references only relevant to the specified party rather than the

whole invoice.

Usage Notes: Dependant

Notes: Group 3: Reference is used with InvoicePartner type contacts. This is all NAD qualifiers

except SF, ST, and CA. Qualifier CA is an exception. The Carrier contact carries a

required ShipmentIdentifier.

Segment Summary


No. ID Name Des. Use Repeat M 0250 RFF Reference M 1





Group: Segment Group 3 (Reference) Conditional (Dependent)

Level: 2

Usage: Mandatory

Max Use: 1


document.

Dependency Notes:

Semantic Notes:

Comments:




C506 REFERENCE M M




AHP Tax registration number

The registration number by which a company/organization is

identified with the tax administration. <IdReference domain="SupplierTaxID">

This can be used only with NAD+RE.

AMT Goods and Services Tax identification number

An identification number assigned to an

organization collecting Goods and Services

Taxes (GST).

<IdReference domain="gstID">

AP Accounts receivable number

Reference number assigned by accounts receivable department to the

account of a specific debtor. <IdReference domain="accountReceivableID">

AV Account payable number

Reference number assigned by accounts payable department to the

account of a specific creditor. <IdReference domain="accountPayableID">

CN Carrier's reference number

Reference number assigned by carrier to a consignment.

<ShipmentIdentifier>

Required with NAD+CA. PY Payee's financial institution account number

Receiving company account number (ACH transfer), check, draft or

wire. <IdReference domain="accountID">

Typically used with NAD+RE and paired with RFF+RT. RT Payee's financial institution transit routing No.

RDFI Transit routing number (ACH transfer).

<IdReference domain="bankRoutingID">

Typically used with NAD+RE and paired with RFF+PY.



TL Tax exemption licence number

Number assigned by the tax authorities to a party indicating its tax

exemption authorization. This number could relate to a specified

business type, a specified local area or a class of products. <IdReference domain="taxExemptionID">

VA VAT registration number

Unique number assigned by the relevant tax authority to identify a

party for use in relation to Value Added Tax (VAT). <IdReference domain="vatID">

With a Triangular Transaction, this identifier is typically applied to

the Ultimate Customer (NAD01="UD") for VAT reporting

purposes.

AGC Account Party Bank Reference

<IdReference domain="ibanID">

This is applicable only for NAD+BF or NAD+RB. If

REF+PQ is present only then this field is

mandatory.

See sample data 10.7 for more details

AGD Agents bank Reference

<IdReference domain="accountType"> This is required for NAD+BF or NAD+RB. The value

can be Checking or Saving.


AGE Agents reference

<IdReference domain="accountName">

This is required for NAD+BF or NAD+RB.


PQ Payment reference

<IdReference domain="swiftID"> This is applicable only for NAD+BF or NAD+RB. If

REF+AGC is present only then this field is

mandatory.


AFN Account Party Reference

<IdReference domain="branchName"> This is optional element for NAD+BF or NAD+RB


1154 Reference number C an..35 M








Group: CTA Segment Group 5: Contact Information

Position: 0300


Level: 2


Max Use: 5

Purpose: A group of segments giving contact details of the specific person or department within the party

identified in the NAD segment.


Notes: Example:

CTA+ZZZ+:Help Desk'


COM+?+31-23-568-5777:TE'

CTA+ZZZ+:Billing Inquiries'

COM+?+49 89 35 874-340 x7890:TE'

[email protected]+EM'

produces...

<Email name="Help Desk">[email protected]</Email>

<Email name="Billing Inquiries">[email protected]</Email>

<Phone name="Help Desk">

<TelephoneNumber>

<CountryCode isoCountryCode="NL">31</CountryCode>

<AreaOrCityCode>23</AreaOrCityCode>

<Number>568-5777</Number>

</TelephoneNumber>

</Phone>

<Phone name="Billing Inquiries">

<TelephoneNumber>

<CountryCode isoCountryCode="DE">49</CountryCode>

<AreaOrCityCode>89</AreaOrCityCode>

<Number>35 874-340</Number>

<Extension>7890</Extension>

</TelephoneNumber>

</Phone>

Some important things need to be noted from the above example:

1. CTA groups by name and then type. cXML groups by type and then name, so they get

rearranged. A maximum of 25 communications contacts are possible. They will all be

collected and resorted.

2. Telephone numbers have to be intelligently broken. The <TelephoneNumber>

structure imposed by cXML is mandatory. Therefore, it is imperative that phone and fax

numbers be correctly written, or else the break algorithm will probably misinterpret them.

Here are some *very important* recommendations in writing out phone numbers for

correct rendering:

(a) Always start with the correct country code. NANP (North American Numbering Plan)

numbers always begin with '1'.

(b) If you dial 9 for an outside line, do not include it here. The leading digits are taken as

a country code, and 9 will be part of the country code if it is there.



(c) A leading + (plus) sign is allowed. Remember that it may need to be escaped.

(d) Separator characters, such as spaces or dashes, or brackets around the area code have

influence on the break algorithm. Separators are not required, (you may send raw digits),

but they do help to mark off the different sections.

(e) An 'x' preceding an extension has the effect of segregating the trailing text as an

extension.

(f) isoCountryCode resolution is done from the leading telephone country code. If it is 1

for NANP, then the following rules are used:

- i) If the AreaOrCityCode is known, then imply the country from that.

- ii) If NAD09 (3207) is present, then use it.

- iii) Use the supplier default country code in Ariba Network.

- iv) Default "US" if still indeterminant.

Segment Summary


No. ID Name Des. Use Repeat M 0310 CTA Contact Information M 1 M 0320 COM Communication Contact C 5



Segment: CTA Contact Information


Group: Segment Group 5 (Contact Information) Conditional (Optional)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment to identify a person or department, and their function, to whom communications

should be directed.

Dependency Notes:

Semantic Notes:

Comments:




3139 CONTACT FUNCTION, CODED C an..3 M

Code specifying the function of a contact (e.g. department or person).


C056 DEPARTMENT OR EMPLOYEE DETAILS C M

Code and/or name of a department or employee. Code preferred.

Both data elements are provided here. The elements Phone, Fax, Email, URL require a

name attribute. You may use either/or. If both are used, then DE3412 will be used. 3413 Department or employee identification C an..17 O

Internal identification code.

3412 Department or employee C an..35 O

The department or person within an organizational entity.



Segment: COM Communication Contact

Position: 0320


Level: 3


Max Use: 5

Purpose: A segment to identify a communications type and number for the contact specified in the CTA

segment.

Dependency Notes:

Semantic Notes:

Comments:





C076 COMMUNICATION CONTACT M M

Communication number of a department or employee in a specified channel.

3148 Communication number M an..512 M

The communication number.

3155 Communication channel qualifier M an..3 M

Code identifying the type of communication channel being used.

AH World Wide Web

Data exchange via the World Wide Web.

EM Electronic mail

Exchange of mail by electronic means.

FX Telefax

Device used for transmitting and reproducing fixed graphic material

(as printing) by means of signals over telephone lines or other

electronic transmission media. TE Telephone

Voice/data transmission by telephone.



Group: PAT Segment Group 8: Payment Terms Basis

Position: 0400

Group: Level: 1


Max Use: 10

Purpose: A group of segments specifying the terms of payment applicable for the whole invoice.


Notes: Examples:

PAT+22++5:3:D:10'

PCD+12:2:13'

PAT+20++5:3:D:30'

PCD+15:15:13'

produces:

<InvoiceDetailPaymentTerm payInNumberOfDays="10" percentageRate="2">

<InvoiceDetailPaymentTerm payInNumberOfDays="30" percentageRate="-15">

This means:

Payment within 10 days earns a 2% discount off the invoice amount.

Payment after 30 days costs a 15% penalty on the invoice amount.

Several occurrences of Group 8: Payment Terms Basis may be used to show multiple

graduations. Ariba Network expects supplier to send the Payment terms if there are any payment terms in PO.

This way PAT group will become mandatory if the referencing PO has any payment terms (PAT

segment in the ORDERS document).

Mapping the payment terms in cXML purchase order to EDI orders is a configurable option on

Ariba Network. If supplier wants to get payment terms in cXML purchase order to EDI orders, then

they have to enable the map payment terms check box in the EDI configuration page. For further

information, please contact Ariba technical support.

Buyer can configure their account to either allow or not allow changes to the PO payment terms in

invoice.

Segment Summary


No. ID Name Des. Use Repeat M 0410 PAT Payment Terms Basis M 1 M 0430 PCD Percentage Details C 1



Segment: PAT Payment Terms Basis


Group: Segment Group 8 (Payment Terms Basis) Conditional (Optional)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the payment terms and date/time basis.

Dependency Notes:

Semantic Notes:

Comments:




4279 PAYMENT TERMS TYPE QUALIFIER M an..3 M

Identification of the type of payment terms.

20 Penalty terms

22 Discount

C110 PAYMENT TERMS C X

Terms of payment code from a specified source.

4277 Terms of payment identification M an..17 X

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





4276 Terms of payment C an..35 X

Conditions of payment between the parties to a transaction (generic term).

4276 Terms of payment C an..35 X

Conditions of payment between the parties to a transaction (generic term).

C112 TERMS/TIME INFORMATION C M

Time details in payment terms.

2475 Payment time reference, coded M an..3 M

Code relating payment terms to the date of a specific event.

5 Date of invoice

Payment time reference is date of invoice.

2009 Time relation, coded C an..3 M

Code relating payment terms to a time before, on or after the reference date.

3 After reference

Payment terms related to time after reference date.

2151 Type of period, coded C an..3 M

Agreed or specified period of time (coded).

D Day

2152 Number of periods C n..3 M

Number of periods of the type indicated in data element 2151 Type of period, coded.



Segment: PCD Percentage Details

Position: 0430

Group: Segment Group 8 (Payment Terms Basis) Conditional (Optional)

Level: 2


Max Use: 1

Purpose: A segment specifying the discount, interest, penalty as well as installment percentage.

Dependency Notes:

Semantic Notes:

Comments:





C501 PERCENTAGE DETAILS M M

Percentage relating to a specified basis.

5245 Percentage qualifier M an..3 M

Identification of the usage of a percentage.

12 Discount

Discount expressed as a percentage.

15 Penalty percentage

5482 Percentage C n..10 M

Value expressed as a percentage of a specified amount.

5249 Percentage basis, coded C an..3 M

Indication of the application of a percentage.

13 Invoice value

Referenced percentage applies on the invoice value.







Group: ALC Segment Group 16: Allowance or Charge

Position: 0710

Group: Level: 1


Max Use: 9999

Purpose: A group of segments specifying allowances and charges for the whole invoice. The allowance

or charge specified within this Segment group may either relate to the total invoice in which case

it cannot be overridden at detail level, or it can relate to the line items as a default

allowance/charge and can be overridden by the ALC Segment group within the detail section.

Where relevant, additional information, tax and alternate currency details are to be indicated in

the TAX and MOA segments.

The basis for the calculation of the allowance/charge may be a quantity, a percentage, an amount

or a rate and one of the Segment group 15-19 should be used accordingly.


Notes: Example 1: Shipping Charge

ALC+C++++SAA'

MOA+8:10.00:EUR'

Example 2: Tax Charge

The total taxes are 10.22 Euros. Note that the tax description is required.

ALC+C++++TX'

FTX+AAI+++Total taxes+en'

MOA+8:10.22:EUR'

Example 3: Discount

In this example, a 5% discount representing 5.77 Euros is being offered.

ALC+A++++DI'

PCD+12:5:13'

MOA+8:5.77:EUR'

Used for shipping and tax charges and discount allowances at the invoice summary level.

One occurrence of Group 16 is required to state the total taxes for the invoice. This is

required even if there is no tax charge, in which case it should show an amount of zero.

Example 4: Charge

In this example, 248.19 represents charges Euros is being charged.

ALC+C++++ABK'

FTX+ABN+++Cost Centre:Office Supplies+en'

MOA+8:248.19:EUR'

Segment Summary


No. ID Name Des. Use Repeat M 0720 ALC Allowance or Charge M 1 D 0740 FTX Free Text C 1




0810 Segment Group 19: Percentage Details C 1

0840 Segment Group 20: Monetary Amount C 2

0920 Segment Group 22: Duty/Tax/Fee Details C 5



Segment: ALC Allowance or Charge


Group: Segment Group 16 (Allowance or Charge) Conditional (Required)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the charge or allowance and, where necessary, its calculation sequence.

Dependency Notes:

Semantic Notes:

Comments:

Notes: The following ALC codes will be are supported as Modification Charges:

ABK

ABP

ADI

AJ

HD

FAC

FC

IN

SC

SHP

Example:

ALC+C++++AJ'


MOA+8:248.19:EUR'

produces...

<Modification>

<AdditionalCost>


</AdditionalCost>

<ModificationDetail name="Adjustment">

<Description xml:lang="en">Cost Centre</Description>

</ModificationDetail>

</Modification>

The following ALC codes will be are supported as Modification Allowances:

ACA

CL

SF

VAB

Example:

ALC+A++++ACA'


MOA+8:248.19:EUR'

produces...

<Modification>

<AdditionalDeduction>

<DeductionAmount>


<DeductionAmount>

</AdditionalDeduction>




</Modification>






5463 ALLOWANCE OR CHARGE QUALIFIER M an..3 M

Specification of an allowance or charge for the service specified.

A Allowance

C Charge

C552 ALLOWANCE/CHARGE INFORMATION C X

Identification of allowance/charge information by number and/or code.

1230 Allowance or charge number C an..35 X

Number assigned by a party referencing an allowance, promotion, deal or charge.

5189 Charge/allowance description, coded C an..3 X

Identification of a charge or allowance.

4471 SETTLEMENT, CODED C an..3 X

Indication of how allowances or charges are to be settled.

1227 CALCULATION SEQUENCE INDICATOR,

CODED C an..3 X

Code indicating the sequence of cumulated calculations to be agreed between interchange

partners. C214 SPECIAL SERVICES IDENTIFICATION C M

Identification of a special service by a code from a specified source or by description.

7161 Special services, coded C an..3 M

Code identifying a special service.

ABK Charge

This code is supported as Modification Charge

Optional: Use with ALC01 (5463) = 'C'

ABP Carrier

This code is supported as Modification Charge


ACA Allowance

This code is supported as Modification Allowance


ADI Royalties



AJ Adjustment



CL Contract Allowance


Optional: Use with ALC01 (5463) = 'A'

DI Discount

A reduction from a usual or list price.

Optional: Use with ALC01 (5463) = 'A' and Group 19 "Percentage

Details" FAC FreightBasedOnDollarMinimum



FC Freight





HD Handling



IN Insurance



SAA Shipping and handling

Description to be provided.


SC Surcharge



SF Discount-Special



SH Special handling service



SHP Shipping



TX Tax

Contribution levied by an authority.

Required: Use with ALC01 (5463) = 'C'

VAB Volume Discount







7160 Special service C an..35 X

Description of a special service.

7160 Special service C an..35 X





Position: 0740


Level: 2


Max Use: 1

Purpose: A segment specifying a textual description of the allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:


Notes: FTX is required to supply a description for special service charge TX (Tax) only.

FTX is optional for charges SAA and SH. It is not captured in the invoice summary. Note

that FTX is REQUIRED for ALC charges SAA, SH, and TX at the line item level (Group

26).

FTX is not used with allowance DI (Discount).

When being used for tax charges FTX has a special mode of operation for providing a

VAT Triangular Taxation Law Reference. The law reference calls for a long string that

only FTX can support.






AAI General information

Normal usage. May be used with all ALC types.

FTX04 provides the description for the relevant charge in context.

FTX03 (C107) is not used. TXD Tax declaration


ALC group for taxation only (ALC+C++++TX').

Tax charges where VAT Triangular Transaction Law Reference is

required. The high level description for total taxes, which is

required, comes from FTX03.01. FTX04 (C108) holds a list of up

to five law reference strings to be associated with one or more

TAX groups, and indexed by RFF01.03.

Refer to the section titled "Using Tax Details with Value-Added

Taxation (VAT) and Triangular Transactions" for details on

implementing this advanced feature. 4453 TEXT FUNCTION, CODED C an..3 X




4441 Free text identification M an..17 M








C108 TEXT LITERAL C D












3453 LANGUAGE, CODED C an..3 M an..2


ISO-639 two char language code, must be two lowercase letters. i.e. "en", "fr", "de", etc.




Position: 0750


Level: 2


Max Use: 5

Purpose: A group of segment for giving references and where necessary, their dates relating to the

allowances or charges.


Notes: For tax charges (ALC05.01="TX"), involving VAT Triangular Transactions, the RFF

group is used to associate a VAT tax point date and payment due date with a TAX group

(SG22) designated as a VAT Triangular Transaction.

Segment Summary








Level: 2

Usage: Mandatory

Max Use: 1


document.

Dependency Notes:

Semantic Notes:

Comments:




C506 REFERENCE M M




VA VAT registration number


party for use in relation to Value Added Tax (VAT). 1154 Reference number C an..35 M


element 1153 Reference qualifier. To associate a tax point date and/or tax payment due date with a VAT Triangular

Transaction, the same VAT registration number should appear here, in RFF01.02 (with VA

qualifier) and in TAX07 (3446). The TAX segment must be specially marked as a VAT

Triangular Transaction. 1156 Line number C an..6 O


Special feature for VAT Triangular Transactions;

If FTX01 (4451) = "TXD", then RFF01.03 is taken as a 1-based index to one of the

components of FTX04 (C108) to associate a Triangular Transaction Law Reference with

the indicated TAX group. Values from 1 to 5 are allowed, where a value of 1 captures

C108.01 and a value of 5 captures C108.05.

FTX01 (4451) must = "TXD" for this special capture to be enabled. If FTX01="AAI", then

this element will be ignored.

4000 Reference version number C an..35 O


This will be captured only with the RFF+VA and only if the REF has a reference to

TAX07.

This will be generated as Tax Detail description if the RFF meets the above two conditions. Example:

ALC+C++++TX'

FTX+TXD++Total taxes+Triangular Law reference doc 45+en'

RFF+VA:123456789B19A:1:VAT in Netherlands'

DTM+131:20030713080000P01:304'

DTM+140:20030720170000P01:304'

MOA+8:250:EUR'



TAX+7+VAT:::Netherlands+TT+1257.14+:::17.5++123456789B19A'

MOA+124:220:EUR'

produces...


...

<Tax>

...

<TaxDetail purpose="tax" category="vat" ... >

...

<Description xml:lang="en">VAT in Netherlands</Description>

...

</Tax>




Position: 0770


Level: 3


Max Use: 2

Purpose: A segment specifying the date and/or time related to the reference.

Dependency Notes:

Semantic Notes:

Comments:









131 Tax point date

Date on which tax is due or calculated.

140 Payment due date

Date/time at which funds should be made available.

2380 Date/time/period C an..35 O


2379 Date/time/period format qualifier C an..3 O


Refer to D.98A Data Element Dictionary for acceptable code values.



Group: PCD Segment Group 19: Percentage Details

Position: 0810


Level: 2


Max Use: 1

Purpose: A group of segments specifying the percentage for the allowance or charge, e.g. The

allowance/charge amount is calculated as 5% of the goods value or a price reduction of 5% may

be specified if the goods quantity ordered is within the range 5 tons to 10 tons.


Notes: Optionally used only with allowance discount (ALC+A++++DI')

Segment Summary


No. ID Name Des. Use Repeat M 0820 PCD Percentage Details M 1





Group: Segment Group 19 (Percentage Details) Conditional (Optional)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the percentage and the percentage basis for the calculation of the

allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example: PCD+12:5:13'








12 Discount






13 Invoice value








Group: MOA Segment Group 20: Monetary Amount

Position: 0840


Level: 2


Max Use: 2

Purpose: A group of segments specifying a monetary amount for an allowance or charge. A range to

which the allowance or charge applies can be specified, e.g. an allowance of 5000 BEF may be

specified if goods value ordered is greater than 100000 BEF.


Notes: One occurrence of the MOA group is required to give the total charge for this one ALC

group. For the ALC group representing taxes, this is the total tax amount.

Tax charges can be broken down with the TAX-MOA group (SG22 @0920).

Segment Summary


No. ID Name Des. Use Repeat M 0850 MOA Monetary Amount M 1



Segment: MOA Monetary Amount


Group: Segment Group 20 (Monetary Amount) Conditional (Required)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the monetary amount for the allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example: MOA+8:58.23:EUR'




C516 MONETARY AMOUNT M M

Amount of goods or services stated as a monetary amount in a specified currency.

5025 Monetary amount type qualifier M an..3 M

Indication of type of amount.

8 Allowance or charge amount

[5422] Total amount of allowance or charge.

261 Alternate currency amount

MOA+261 is used to specify an alternate Amount and Currency

for tax and can be used only if MOA+8 is present.

Example:

ALC+C++++TX'


MOA+8:10.22:USD'

MOA+261:100:INR'

.....

5004 Monetary amount C n..35 M

Number of monetary units.

6345 Currency, coded C an..3 M

Identification of the name or symbol of the monetary unit involved in the transaction.

6343 Currency qualifier C an..3 X

Code giving specific meaning to data element 6345 Currency.

4405 Status, coded C an..3 X

Provides information regarding a status.



Group: TAX Segment Group 22: Duty/Tax/Fee Details

Position: 0920


Level: 2


Max Use: 5

Purpose: A group of segments specifying tax related information for the allowance or charge and, when

necessary.


Notes: This group is used for providing details of tax breakdown. It is allowed only where

ALC05.01 (7161) = "TX". The tax amounts given in tax details should add up to the

monetary tax total amount given in MOA, (SG20 @0850).

With this group it is possible to designate certain tax charges as Value-Added Tax (VAT)

related and also link date references for Triangular Transactions.

Using the Triangular Transaction VAT requires a complex mapping because of the need

to merge referential dates with the tax details. For more details, refer to the separate

section on Using Tax Details with Value-Added Taxation (VAT) and Triangular

Transactions.

Each occurrence of Group 22 (TAX-MOA) produces one occurrence of <TaxDetail>. References

and dates from Group 17 (RFF-DTM) are linked to Group 22 occurrences to designate as triangular

and merge the dates.

Segment Summary


No. ID Name Des. Use Repeat M 0930 TAX Duty/Tax/Fee Details M 1 M 0940 MOA Monetary Amount C 1



Segment: TAX Duty/Tax/Fee Details


Group: Segment Group 22 (Duty/Tax/Fee Details) Conditional (Optional)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment specifying the tax type, category and rate, or exemption, related to the allowance or

charge.

Dependency Notes:

Semantic Notes:

Comments:




5283 DUTY/TAX/FEE FUNCTION QUALIFIER M an..3 M

Code identifying the function of an duty, tax or fee information.

<TaxDetail purpose=TAX01>

5 Customs duty

Duties laid down in the Customs tariff to which goods are liable on

entering or leaving the Customs territory (CCC). TaxDetail@purpose="duty"

7 Tax


TaxDetail@purpose="tax"

C241 DUTY/TAX/FEE TYPE C M

Code and/or name identifying duty, tax or fee.

5153 Duty/tax/fee type, coded C an..3 M

Identification of the type of duty or tax or fee applicable to commodities or of tax

applicable to services. All values defined by D.98A are allowed to be used. For VAT related taxes and Triangular

Transactions you MUST use code "VAT".

If DE5153="VAT", then TAX07 (3446) is matched to RFF01.02 where RFF01.01="VAT"

for a matching VAT registration number. If a tax point date and payment date are supplied

in the RFF group, then a triangular transaction is designated and the dates are merged

accordingly.

This code does not go directly to cXML per se. TaxDetail@category

supports a short list of codes (sales, vat, gst, usage, other) to

which DE5153 maps. The definition of the code from D.98A maps to

TaxDetail.Description, and may be translated to the target language.

<TaxDetail category>

<Description>

AAA Petroleum tax

AAB Provisional countervailing duty cash

Countervailing duty paid in cash prior to a formal finding of

subsidization by Customs. AAC Provisional countervailing duty bond

Countervailing duty paid by posting a bond during an investigation

period prior to a formal decision on subsidization by Customs. AAD Tobacco tax

A tax levied on tobacco products.



ADD Anti-dumping duty

Duty applied to goods ruled to have been dumped in an import

market at a price lower than that in the exporter's domestic market. BOL Stamp duty (Imposta di Bollo)

Tax required in Italy, which may be fixed or graduated in various

circumstances (e.g. VAT exempt documents or bank receipts). CAP Agricultural levy

Levy imposed on agricultural products where there is a difference

between the selling price between trading countries. CAR Car tax

COC Paper consortium tax (Italy)


CST Commodity specific tax

Tax related to a specified commodity, e.g. illuminants, salts.

CUD Customs duty

Duties laid down in the Customs tariff, to which goods are liable on

entering or leaving the Customs territory (CCC). CVD Countervailing duty

A duty on imported goods applied for compensate for subsidies

granted to those goods in the exporting country. ENV Environmental tax

Tax assessed for funding or assuring environmental protection or

clean-up. EXC Excise duty

Customs or fiscal authorities code to identify a specific or ad

valorem levy on a specific commodity, applied either domestically

or at time of importation. EXP Agricultural export rebate

Monetary rebate given to the seller in certain circumstances when

agricultural products are exported. FET Federal excise tax

Tax levied by the federal government on the manufacture of specific

items. FRE Free

GCN General construction tax

General tax for construction.

GST Goods and services tax

Tax levied on the final consumption of goods and services

throughout the production and distribution chain. ILL Illuminants tax

Tax of illuminants.

IMP Import tax

Tax assessed on imports.

IND Individual tax

LAC Business license fee

Government assessed charge for permit to do business.

LCN Local construction tax

Local tax for construction.

LDP Light dues payable

Fee levied on a vessel to pay for port navigation lights.

LOC Local sales tax

Assessment charges on sale of goods or services by city, borough



country or other taxing authorities below state or provincial level. LST Lust tax

Tax imposed for clean-up of leaky underground storage tanks.

MCA Monetary compensatory amount

Levy on Common Agricultural Policy (European Union) goods used

to compensate for fluctuating currencies between member states. MCD Miscellaneous cash deposit

Duty paid and held on deposit, by Customs, during an investigation

period prior to a final decision being made on any aspect related to

imported goods (except valuation) by Customs. OTH Other taxes

Unspecified, miscellaneous tax charges.

PDB Provisional duty bond

Anti-dumping duty paid by posting a bond during an investigation

period prior to a formal decision on dumping by Customs. PDC Provisional duty cash

Anti-dumping duty paid in cash prior to a formal finding of dumping

by Customs. PRF Preference duty

SCN Special construction tax

Special tax for construction.

SSS Shifted social securities

Social securities share of the invoice amount to be paid directly to

the social securities collector. STT State/provincial sales tax

All applicable sale taxes by authorities at the state or provincial

level, below national level. SUP Suspended duty

Duty suspended or deferred from payment.

SUR Surtax

A tax or duty applied on and in addition to existing duties and taxes.

SWT Shifted wage tax

Wage tax share of the invoice amount to be paid directly to the tax

collector(s office). TAC Alcohol mark tax

TOT Total

TOX Turnover tax

Tax levied on the total sales/turnover of a corporation.

TTA Tonnage taxes

Tax levied based on the vessel's net tonnage.

VAD Valuation deposit

Duty paid and held on deposit, by Customs, during an investigation

period prior to a formal decision on valuation of the goods being

made. VAT Value added tax

A tax on domestic or imported goods applied to the value added at

each stage in the production/distribution cycle. 1131 Code list qualifier C an..3 X




5152 Duty/tax/fee type C an..35 O



Type of duty or tax or fee applicable to commodities or of tax applicable to services.

Location or jurisdiction associated with this tax. This is just a name.

<TaxDetail>

<Location xml:lang=default>

Optional Location is captured and taken with default language.

C533 DUTY/TAX/FEE ACCOUNT DETAIL C O

Indication of account reference for duties, taxes and/or fees.

TAX03 (C533) is only used for VAT Triangular Transactions.

5289 Duty/tax/fee account identification M an..6 M

Identification of a particular duty, tax or fee.

TT Triangular Transaction

Indicates that this tax detail represents a VAT Triangular

Transaction. This is only valid where TAX02.01 (5153) = "VAT". Setting this

flag to TT causes TAX07 (3446) to search for a matching VAT

Identification reference where RFF01.01="VA", and then

capturing a tax point date and payment due date.

<TaxDetail isTriangularTransaction="yes">





5286 DUTY/TAX/FEE ASSESSMENT BASIS C an..15 O

Value or quantity on which a duty or tax will be assessed.

Taxable amount on which the tax percentage is calculated.

<TaxDetail>

<TaxableAmount>

<Money currency=MOA01.03 (6345)>TAX04 (5286) </Money>

C243 DUTY/TAX/FEE DETAIL C O

Rate of duty/tax/fee applicable to commodities or of tax applicable to services.

TAX05 (C243) is optional in itself. If used, then C243.04 (5278) gives the percentage rate.

5279 Duty/tax/fee rate identification C an..7 O

Identification of the rate of duty or tax or fee applicable to commodities or of tax applicable

to services. Alternate Amount for Tax amount is specified. It can be present only if MOA+124 is

present.

If the alternate amount is present, then MOA+261 must also be present.

If this is not present, the alternate amount for the Tax amount is ignored

Example:

ALC+C++++TX'


MOA+8:10.22:USD'

MOA+261:100:INR'

TAX+7+VAT:::Netherlands+TT+1257.14+500:::17.5++123456789B19?:A'

MOA+124:220:EUR'



<Tax>

<Money currency="USD" alternateAmount="100"

alternateCurrency="INR">10.22</Money>


<TaxDetail purpose="tax" category="vat" percentageRate="17.5">

<TaxableAmount>


</TaxableAmount>

<TaxAmount>

<Money currency="EUR" alternateAmount="500"

alternateCurrency="INR">220</Money>

</TaxAmount>


<Description xml:lang="en">123456789B19:A</Description>

</TaxDetail>

</Tax>

Note: For ALC of type modifications, TAX.5153=TOT will be is mapped

to <Tax>, rest will be remaining is mapped to <TaxDetail>

Example:

This is an example for Adjustment charge with Tax

ALC+C++++AJ'


MOA+8:248.19:EUR'

TAX+7+TOT:::Netherlands++1257.14+:::0++123456789B19?:A'

MOA+124:220:EUR'

TAX+7+VAT:::Netherlands++1257.14+:::3++Tax Description'

MOA+124:220:EUR'

<InvoiceHeaderModifications>

<Modification>

<AdditionalCost>


</AdditionalCost>

<Tax>


<Description xml:lang="en"></Description>

<TaxDetail category="vat" percentageRate="3" purpose="tax">

<TaxableAmount>


</TaxableAmount>

<TaxAmount>


</TaxAmount>


<Description xml:lang="en">Tax Description</Description>

</TaxDetail>

</Tax>




</Modification>

</InvoiceHeaderModifications>







5278 Duty/tax/fee rate C an..17 M

Rate of duty or tax or fee applicable to commodities or of tax applicable to services.

Taken as a percentage, so 17.5% is written as "17.5".

<TaxDetail percentage=TAX05.04 (5278)>

5273 Duty/tax/fee rate basis identification C an..12 X

Identification of the various elements of tax combination to be attributed to a commodity.





5305 DUTY/TAX/FEE CATEGORY, CODED C an..3 X

Code identifying a tax/duty/fee category within a tax/duty/fee type system.

Maps to the TaxDetail@exemptDetail.

TAX+7+VAT:::Netherlands+TT+1257.14+500:::0+Z+123456789B19?:A'

produces <TaxDetail … exemptDetail=“zeroRated”>

…. <TaxDetail>

TAX+7+VAT:::Netherlands+TT+1257.14+500:::0+E+123456789B19?:A'

produces <TaxDetail … exemptDetail=“exempt”>

…. <TaxDetail>

Z Zero Tax

E Exempt Tax

3446 PARTY TAX IDENTIFICATION NUMBER C an..20 O

Number assigned to a party by a taxation authority.

Triangular Transaction:

If TAX02.01 (5153) = "VAT" and TAX03.01 (5289) = "TT", then TAX07 is used as a

matching key for an RFF group (where RFF01.01="VA") to capture a related tax point date

and payment due date for the VAT of a triangular transaction.

Custom Tax Detail description:

If supplier wants to specify custom tax detail description, then they can use TAX07 for the

same.

If TAX02.01 (5153) = "VAT" and TAX03.01 (5289) = "TT", and TAX07 is used as a

matching key for an RFF group (where RFF01.01="VA") to capture a related tax point date

and payment due date for the VAT of a triangular transaction, then supplier can specify the

Tax Detail description in RFF01.04 (4000).

For Example:

TAX+7+VAT:::Netherlands+TT+1257.14+:::17.5++VAT in Netherlands' (with no

matching RFF02..

produces..



<Tax>

...

<TaxDetail category="vat" ...>

...

<Description xml:lang="en">VAT in Netherlands</Description>

...

</TaxDetail>

<Tax>




Position: 0940


Level: 3


Max Use: 1

Purpose: A segment specifying the amount for the allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Example: MOA+124:5.16:EUR'

MOA+124 is required to specify the tax amount.








124 Tax amount

Tax imposed by government or other official authority related to the

weight/volume charge or valuation charge. 5004 Monetary amount C n..35 M










Group: LIN Segment Group 26: Line Item

Position: 1060

Group: Level: 1


Max Use: 9999999

Purpose: A group of segments providing details of the individual invoiced items. There must be at least

one occurrence of Segment group 22 within an invoice, but not necessarily in a credit note or a

debit note. This Segment group may be repeated to give sub-line details.


Notes: <InvoiceDetailItem> for Regular Invoices, or <InvoiceDetailHeaderOrder> for Summary Invoices.

Segment Summary


No. ID Name Des. Use Repeat M 1070 LIN Line Item M 1 O 1080 PIA Additional Product Id C 25 O 1090 IMD Item Description C 10 D 1110 QTY Quantity C 1 O 1130 ALI Additional Information C 1 O 1140 DTM Date/Time/Period C 35 O 1190 FTX Free Text C 5



1550 Segment Group 35: Name and Address C 99

1670 Segment Group 39: Allowance or Charge C 30



Segment: LIN Line Item


Group: Segment Group 26 (Line Item) Conditional (Required)

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.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example: LIN+1++1:PL'




1082 LINE ITEM NUMBER C an..6 M

Serial number designating each separate item within a series of articles.

Line number of the invoice document.

InvoiceDetailItem@invoiceLineNumber, for regular invoices

InvoiceDetailHeaderOrder.InvoiceDetailOrderSummary@invoiceLineNumber

, for summary invoices.

1229 ACTION REQUEST/NOTIFICATION, CODED C an..3 X

Code specifying the action to be taken or already taken.

C212 ITEM NUMBER IDENTIFICATION C D

Goods identification for a specified source.

LIN03 (C212) is required only for regular type invoices, to specify the purchase order line

number. It is not used for summary invoices. 7140 Item number C an..35 M

A number allocated to a group or item.

7143 Item number type, coded C an..3 M

Identification of the type of item number.

PL Purchaser's order line number

Reference number identifying a line entry in a customer's order for

goods or services. 1131 Code list qualifier C an..3 X




C829 SUB-LINE INFORMATION C X

To provide an indication that a segment or segment group is used to contain sub-line or

sub-line item information and to optionally enable the sub-line to be identified. 5495 Sub-line indicator, coded C an..3 X

Indication that the segment and/or segment group is used for sub-line item information.

1082 Line item number C an..6 X



Serial number designating each separate item within a series of articles.

1222 CONFIGURATION LEVEL C n..2 X

Number indicating the level of an object which is in a hierarchy.

7083 CONFIGURATION, CODED C an..3 X

Code indicating the status of the sub-line item in the configuration.



Segment: PIA Additional Product Id

Position: 1080


Level: 2


Max Use: 25

Purpose: A segment providing either additional identification to the product specified in the LIN segment

(e.g. Harmonized System number), or provides any substitute product identification.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Example: PIA+1+P3422:VN+382715387:SN'

For Service Item

Example:PIA+1+P3422:MP' Regular invoices only.

Item number identifiers may optionally be specified to indicate exactly what is being

invoiced. Item numbers may be specified in any sequence.

MF is paired with NAD+MF. They are optional, but must both be used together.

If VS is used, then VN is required. VN does not require VS.

BP renders to an Extrinsic in cXML.

SN is allowed to repeat. It is possible to have up to 125 serial numbers. This is useful for

high-priced commodities, in which a serial number must be specified for each item

shipped.

Service Item only

'CC' qualifier must be used only with 'MP'

Both 'VN' and 'MP' cannot be used together.

Example:

PIA+1+P3422:VN+382715387:MP'

If VS is used, then VN or MP is required.




4347 PRODUCT ID. FUNCTION QUALIFIER M an..3 M

Indication of the function of the product code.

1 Additional identification

Information which specifies and qualifies product identifications.



C212 ITEM NUMBER IDENTIFICATION M M


7140 Item number C an..35 M




BP Buyer's part number

Reference number assigned by the buyer to identify an article.

CC Industry commodity code

The codes given to certain commodities by an industry.

'CC' qualifier for classification details in PIA segment

Example:PIA+1+P3422:MP+ID001:CC'

cXML

<InvoiceDetailServiceItemReference>

<Classification domain="UNSPSC">ID001</Classification>

....

</InvoiceDetailServiceItemReference> MF Manufacturer's (producer's) article number

The number given to an article by its manufacturer.

MP Product/service identification number

Reference number identifying a product or service.

<InvoiceDetailServiceItem>

<InvoiceDetailServiceItemReference..

<ItemID>

<SupplierPartID> SN Serial number

Identification number of an item which distinguishes this specific

item out of a number of identical items. VN Vendor item number

Reference number assigned by a vendor/seller identifying a

product/service/article. VS Vendor's supplemental item number





C212 ITEM NUMBER IDENTIFICATION C O








MF Manufacturer's (producer's) article number


SN Serial number





















SN Serial number



















SN Serial number





















SN Serial number











Segment: IMD Item Description

Position: 1090


Level: 2


Max Use: 10

Purpose: A segment for describing the product or service being invoiced as well as product characteristic.

This segment should be used for products or services that cannot be fully identified by a product

code or article number.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Example:

IMD+F++18 inch/46 cm ruler, stainless steel, anti-skid back::en'

IMD+E++18 inch ruler::en'

produces:

<InvoiceDetailItemReference ... >

<Description xml:lang="en">18 inch/46 cm ruler, stainless steel, anti-skid back

<ShortName>18 inch ruler</ShortName>

</Description>

Here the regular and short item descriptions are both used. Neither one is required. If

multiple occurrences of IMD+F are used, they simply concatenate into the Description

element. Note that language codes cannot be mixed.




7077 ITEM DESCRIPTION TYPE, CODED C an..3 O

Code indicating the format of a description.

E Free-form short description

Short description of an item in free form.

F Free-form

C272 ITEM CHARACTERISTIC C X

To provide the characteristic of the item being described.

7081 Item characteristic, coded C an..3 X

Code specifying the item characteristic being described.





C273 ITEM DESCRIPTION C O

Description of an item.

7009 Item description identification C an..17 X

Code from an industry code list which provides specific data about a product characteristic.







7008 Item description C an..35 O

Plain language description of articles or products.

7008 Item description C an..35 O

Plain language description of articles or products.

3453 Language, coded C an..3 O


7383 SURFACE/LAYER INDICATOR, CODED C an..3 X

Code indicating the surface or layer of a product that is being described.



Segment: QTY Quantity

Position: 1110


Level: 2


Max Use: 1

Purpose: A segment identifying the product quantities e.g. invoiced quantity.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Example: QTY+47:7:EA'

Quantity is required for regular invoices and not used for summary invoices.




C186 QUANTITY DETAILS M M

Quantity information in a transaction, qualified when relevant.

6063 Quantity qualifier M an..3 M

Code giving specific meaning to a quantity.

47 Invoiced quantity

The quantity as per invoice.

For a service item, the unit of measure and unit price must occur

together.

LIN+1++1:PL'

PIA+1+09347509:MP+ID001:CC'

........

QTY+47:1:EA'

........

MOA+66:1.34:USD'

MOA+146:1.34:USD'

6060 Quantity M n..15 M

Numeric value of a quantity.

6411 Measure unit qualifier C an..3 M

Indication of the unit of measurement in which weight (mass), capacity, length, area,

volume or other quantity is expressed.



Segment: ALI Additional Information

Position: 1130


Level: 2


Max Use: 1

Purpose: A segment indicating that the line item is subject to special conditions owing to origin, customs

preference, embargo regulations or commercial factors.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Example: ALI+NL'

This would specify the country of origin of the item as Netherlands.




3239 COUNTRY OF ORIGIN, CODED C an..3 O

Country in which the goods have been produced or manufactured, according to criteria laid

down for the purposes of application of the Customs tariff, of quantitative restrictions, or of

any other measure related to trade. 9213 TYPE OF DUTY REGIME, CODED C an..3 X

Identification of the statement of the full/preferential regime according to which duty is

assessed. 4183 SPECIAL CONDITIONS, CODED C an..3 X

Indication of a specific condition.

4183 SPECIAL CONDITIONS, CODED C an..3 X











Position: 1140


Level: 2


Max Use: 35

Purpose: A segment specifying date/time/period details relating to the line item only.

Dependency Notes:

Semantic Notes:

Comments:


Notes: For Service item period DTM+194 and DTM+206 segments.

Example:

LIN+1++1:PL'

PIA+1+09347509:MP+ID001:CC'

IMD+F++:::18 inch/46 cm ruler::en'

IMD+E++:::18 inch ruler::en'

QTY+47:1:EA'

DTM+171:20040128:102'

DTM+194:20040128:102'

DTM+206:20040128:102'

DTM+194 and DTM+206 must always occur as a pair, and must be used only for service

item .

DTM+171 must be used only for service item.








171 Reference date/time

Date/time on which the reference was issued.

Used with PIA+...+MP when building

<InvoiceDetailServiceItem>.

This date will be mapped to service item referenceDate attribute.

<InvoiceDetailServiceItem .. referenceDate="..

194 Start date/time

Date/time on which a period starts.


<InvoiceDetailServiceItem>. This used in conjunction with

DTM+206.

This date will be mapped to service item period startDate.


...



...

<Period startDate=".." >

206 End date/time

Date/time on which a period (from - to) ends.


<InvoiceDetailServiceItem>. This used in conjunction with

DTM+194.

This date will be mapped to service item period endDate.


...

...

<Period startDate=".." endDate="..">

2380 Date/time/period C an..35 O


2379 Date/time/period format qualifier C an..3 O






Position: 1190


Level: 2


Max Use: 5

Purpose: A segment with free text information, in coded or clear form, used when additional information

is needed but cannot be accommodated within other segments. In computer to computer

exchanges such text will normally require the receiver to process this segment manually.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Examples:

Comment:

FTX+ADU+++Weight balanced for durability+en'

Extrinsic:

FTX+ZZZ++Colour Lot+Blue'

One comment and/or up to five extrinsics may be specified for the invoice line item in

general.






ADU Note

Text subject is note.


Note contains information mutually defined by trading partners.

4453 TEXT FUNCTION, CODED C an..3 O


2 Text replacing missing code

Text description of a coded data item for which there is no currently

available code. 3 Text for immediate use

Text must be read before actioning message.



C107 is required if FTX01="ZZZ". It is not used if FTX01="ADU".

4441 Free text identification M an..17 M






C108 TEXT LITERAL C M














3453 LANGUAGE, CODED C an..3 D an..2


Language code is required if DE4451='ADU'; not used for DE4451='ZZZ'.




Position: 1210


Level: 2


Max Use: 10

Purpose: A group of segments specifying any monetary amounts relating to the products and when

necessary a currency.


Segment Summary







Group: Segment Group 27 (Monetary Amount) Conditional (Required)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment specifying any monetary amounts relating to the product, e.g. item amount,

insurance value, customs value.

Dependency Notes:

Semantic Notes:

Comments:








38 Invoice item amount

(5068) Total sum charged in respect of a single Invoice item in

accordance with the terms of delivery. Regular Invoice: Not Used

Summary Invoice: Optional <NetAmount> <InvoiceDetailOrderSummary>

<NetAmount>

66 Goods item total

Net price x quantity for the line item.

Regular Invoice: Optional <SubtotalAmount>

Service item: Mandatory <SubtotalAmount>

Summary Invoice: Not Used

<InvoiceDetailItem>

<SubtotalAmount>

146 Unit price

(5110) Reporting monetary amount is a "per

unit" amount.

Regular Invoices: Required <UnitPrice>

Summary Invoices: Not Used <InvoiceDetailItem>

<UnitPrice>

203 Line item amount

Goods item total minus allowances plus charges

for line item. See also Code 66.

Regular Invoice: Optional <NetAmount>

Summary Invoice: Not Used <InvoiceDetailItem>

<NetAmount>

289 Subtotal amount

Total amount of money that is part of a

complete amount.

Regular Invoice: Not Used

Summary Invoice: Required <SubtotalAmount>



Group: PRI Segment Group 29: Price

Position: 1290


Level: 2


Max Use: 10

Purpose: A group of segments identifying the relevant information for the goods or services invoiced.

Usage Notes: Used

Segment Summary


No. ID Name Des. Use Repeat M 1300 PRI Price M 1 O 1320 APR Additional Price Information M 1 O 1330 RNG Range Details M 1



Segment: PRI Price


Group: Segment Group 29 (Price Details) Conditional (Used)

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'.

Dependency Notes:

Semantic Notes:

Comments:

Notes:




C509 PRICE INFORMATION C Comp Used

Description: Identification of price type, price, and related details.

5125 Price qualifier M an 1/3 Must use

Description: Identification of a type of price.

CAL Calculation Price



Segment: APR Additional Price Information

Position: 1320 (Segment)

Group: Segment Group 29 (Price Details) Conditional (Must Use)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment to identify information such as a price multiplier, class, or type of trade and

identifying the reason for any changes.

Dependency Notes:

Semantic Notes:

Comments:

Notes:




Ref Tag Element Name Status Type Min/Max Usage

4043 Class of trade, coded C an 1/3 Must use

Description: Code identifying the class of trade.

WS User

C138 PRICE MULTIPLIER INFORMATION C Comp Must use

Description: Price multiplier and its identification.

5394 Price multiplier M n 1/12 Must use

Description: Rate to be used to multiply a price.

This is mapped to conversion factor. E.g:

<PriceBasisQuantity quantity="2" conversionFactor="0.10">

5393 Price multiplier qualifier C an 1/3 Must use

Description: Type of price multiplier.

CSD Cost Markup Multiplier – Original Cost



Segment: RNG Range Details

Position: 1330 (Segment)

Group: Segment Group 29 (Price Details) Conditional (Must Use)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment to identify the ranges (quantity, amount, etc.) to which the additional price

information applies.

Dependency Notes:

Semantic Notes:

Comments:

Notes:




6167 Range type qualifier M an 1/3 Must use

Description: Identification of the type of range.

4 Quantity Range

C280 RANGE C Comp Must use

Description: Range minimum and maximum limits.

6411 Measure unit qualifier M an 1/3 Must use

Description: Indication of the unit of measurement in which weight (mass), capacity,

length, area, volume or other quantity is expressed.

This is mapped to unit of measure. E.g:

<PriceBasisQuantity> <UnitOfMeasure>BX</UnitOfMeasure>

6162 Range minimum C n 1/18 Must use

Description: Minimum of a range.

This is mapped to quantity factor. E.g:

<PriceBasisQuantity quantity="2" conversionFactor="0.10">




Position: 1350


Level: 2


Max Use: 10

Purpose: A group giving references and where necessary, their dates, relating to the line item.


Segment Summary








Level: 2

Usage: Mandatory

Max Use: 1


document.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Examples:

Referencing purchase order number and date:

RFF+ON:DO364'

DTM+4:20000415:102'

Master agreement and date:

RFF+AJS:843-2187-5193'

DTM+126:20010903121844M05:304'

Supplier's order number (from order entry):

RFF+VN:ORD24185'

For summary invoices, at least one of the references available must be specified. Any two

or all three are also allowed.

For taxPointDate:

RFF+VA:123456789B19?:B'

DTM+131:20030712080000P01:304'




C506 REFERENCE M M




AJS Agreement number

A number specifying an agreement between parties.

ON Order number (purchase)

[1022] Reference number assigned by the buyer to an order.

VN Order number (vendor)

Reference number assigned by supplier to a buyer's purchase order.

ZZZ Mutually defined reference number

Number based on party agreement.

VA VAT Registration Number


party for use in relation to Value Added Tax (VAT).



1154 Reference number C an..35 M

Identification number the nature and function of which can be qualified by an entry in

data element 1153 Reference qualifier.

Note: This Reference number must match the tax identification number in the TAX

segment - TAX07.3446 (Party Tax Identification Number.) in order to map the

taxPointDate.

1156 Line number C an..6 X







Position: 1370


Level: 3


Max Use: 1

Purpose: A segment specifying the date/time related to the reference.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Example: DTM+4:20021019:102'

Example for taxPointDate:

DTM+131:20030712080000P01:304'








4 Order date/time

[2010] Date when an order is issued.

Use with RFF+ON. It can be used with RFF+VN, but is not

captured. 126 Contract date

[2326] Date when a Contract is agreed.

Use with RFF+AJS.

131 taxPointDate

Date on which the tax is due or calculated.





102 CCYYMMDD


203 CCYYMMDDHHMM




M=Month;D=Day;H=Hour;M=Minute;S=Second. 303 CCYYMMDDHHMMZZZ






Group: NAD Segment Group 35: Name and Address

Position: 1550


Level: 2


Max Use: 99

Purpose: A group of segments identifying the parties with associated information, relevant to the line item

only.


Segment Summary


No. ID Name Des. Use Repeat M 1560 NAD Name and Address M 1


1640 Segment Group 38: Contact Information C 5



Segment: NAD Name and Address


Group: Segment Group 35 (Name and Address) Conditional (Optional)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying names and addresses of the parties, in coded or clear form, and their

functions relevant to the line item.

It is recommended that where possible only the coded form of the party ID should be specified

e.g. The Buyer and Seller are known to each other, thus only the coded ID is required, but the

Consignee or Delivery address may vary and would have to be clearly specified, preferably in

structured format.

Dependency Notes:

Semantic Notes:

Comments:




3035 PARTY QUALIFIER M an..3 M

Code giving specific meaning to a party.

CA Carrier

(3126) Party undertaking or arranging transport of goods between

named points. MF Manufacturer of goods

Party who manufactures the goods.

MF is used with regular invoices only, and is paired with MF in

C212, in LIN or PIA. They must be used together. SF Ship from

Identification of the party from where goods will be or have been

shipped. NAD+SF and NAD+ST are used together to form

InvoiceDetailLineShipping.

If NAD+SF is used, then NAD+ST is required, and SG39 ALC is

required to specify the shipping charge.


the addressID of the ShipFrom, forming <Contact

role="shipFrom" addressID=" ...."> ST Ship to

Identification of the party to where goods will be or have been

shipped. NAD+ST and NAD+SF are used together to form

InvoiceDetailLineShipping.

If NAD+ST is used, then NAD+SF is required, and SG39 ALC is

required to specify the shipping charge.


the addressID of the ShipTo, forming <Contact role="shipTo"

addressID=" ...."> C082 PARTY IDENTIFICATION DETAILS C X

Identification of a transaction party by code.



3039 Party identification M an..35 X

Code identifying a party involved in a transaction.





C058 NAME AND ADDRESS C M

Unstructured name and address: one to five lines.

3124 Name and address line M an..35 M










C080 PARTY NAME C O

Identification of a transaction party by name, one to five lines. Party name may be

formatted. 3036 Party name M an..35 M










3045 Party name format, coded C an..3 O

Specification of the representation of a party name.


C059 STREET C D

Street address and/or PO Box number in a structured address: one to four lines.

3042 Street and number/p.o. box M an..35 M








3164 CITY NAME C an..35 D

Name of a city (a town, a village) for addressing purposes.

3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9 D

Identification of the name of sub-entities (state, province) defined by appropriate

governmental agencies.



3251 POSTCODE IDENTIFICATION C an..9 O

Code defining postal zones or addresses.

3207 COUNTRY, CODED C an..3 D an..2

Identification of the name of a country or other geographical entity as specified in ISO

3166.




Position: 1580


Level: 3


Max Use: 5

Purpose: A group of segment for giving references only relevant to the specified party rather than the

whole line item.


Segment Summary


No. ID Name Des. Use Repeat M 1590 RFF Reference M 1






Level: 3

Usage: Mandatory

Max Use: 1


document.

Dependency Notes:

Semantic Notes:

Comments:




C506 REFERENCE M M




CN Carrier's reference number

Reference number assigned by carrier to a consignment.

<ShipmentIdentifier>

Required with NAD+CA. 1154 Reference number C an..35 M








Group: CTA Segment Group 38: Contact Information

Position: 1640


Level: 3


Max Use: 5

Purpose: A group of segments giving contact details of the specific person or department within the party

identified in the NAD segment.


Segment Summary


No. ID Name Des. Use Repeat M 1650 CTA Contact Information M 1 M 1660 COM Communication Contact C 5



Segment: CTA Contact Information



Level: 3

Usage: Mandatory

Max Use: 1

Purpose: A segment to identify a person or department, and their function, to whom communications

should be directed.

Dependency Notes:

Semantic Notes:

Comments:




3139 CONTACT FUNCTION, CODED C an..3 M

Code specifying the function of a contact (e.g. department or person).


C056 DEPARTMENT OR EMPLOYEE DETAILS C M

Code and/or name of a department or employee. Code preferred.

3413 Department or employee identification C an..17 O

Internal identification code.

3412 Department or employee C an..35 O

The department or person within an organizational entity.



Segment: COM Communication Contact

Position: 1660


Level: 4


Max Use: 5

Purpose: A segment to identify a communications type and number for the contact specified in the CTA

segment.

Dependency Notes:

Semantic Notes:

Comments:





C076 COMMUNICATION CONTACT M M

Communication number of a department or employee in a specified channel.

3148 Communication number M an..512 M

The communication number.

3155 Communication channel qualifier M an..3 M

Code identifying the type of communication channel being used.

AH World Wide Web

Data exchange via the World Wide Web.

EM Electronic mail

Exchange of mail by electronic means.

FX Telefax

Device used for transmitting and reproducing fixed graphic material

(as printing) by means of signals over telephone lines or other

electronic transmission media. TE Telephone

Voice/data transmission by telephone.



Group: ALC Segment Group 39: Allowance or Charge

Position: 1670


Level: 2


Max Use: 30

Purpose: A group of segments specifying allowances and charges for the line item where this is different

to or not specified within the heading section.


Notes: Used for shipping and tax charges and discount allowances at the line item level.

Tax detail breakdown (SG44 TAX) is supported here, but not the VAT Triangular

Transaction feature.

Segment Summary


No. ID Name Des. Use Repeat M 1680 ALC Allowance or Charge M 1 D 1710 FTX Free Text C 1

1750 Segment Group 41: Percentage Details C 1


1860 Segment Group 44: Duty/Tax/Fee Details C 5



Segment: ALC Allowance or Charge


Group: Segment Group 39 (Allowance or Charge) Conditional (Optional)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the charge or allowance and, where necessary its calculation sequence.

Dependency Notes:

Semantic Notes:

Comments:

Notes: The following ALC codes will be are supported as Modification Charges:

ABK

ABP

ADI

AJ

HD

FAC

FC

IN

SC

SHP

Example:

ALC+C++++AJ'


MOA+8:248.19:EUR'

produces...

<Modification>

<AdditionalCost>


</AdditionalCost>




</Modification>

The following ALC codes will be are supported as Modification Allowances:

ACA

CL

SF

VAB

Example:

ALC+A++++ACA'


MOA+8:248.19:EUR'

produces...

<Modification>

<AdditionalDeduction>

<DeductionAmount>


<DeductionAmount>

</AdditionalDeduction>




</Modification>






5463 ALLOWANCE OR CHARGE QUALIFIER M an..3 M

Specification of an allowance or charge for the service specified.

A Allowance

Used only for <InvoiceDetailDiscount>, with C214.7161="DI"

(Discount) C Charge

N No allowance or charge

No increases or reduction in price (list or stated) are included.

Used only for <Distribution>, with SAC02="B840" (Customer

Account Identification) C552 ALLOWANCE/CHARGE INFORMATION C D

Identification of allowance/charge information by number and/or code.

1230 Allowance or charge number C an..35 M

Number assigned by a party referencing an allowance, promotion, deal or charge.

5189 Charge/allowance description, coded C an..3 X

Identification of a charge or allowance.

4471 SETTLEMENT, CODED C an..3 X

Indication of how allowances or charges are to be settled.

1227 CALCULATION SEQUENCE INDICATOR,

CODED C an..3 X

Code indicating the sequence of cumulated calculations to be agreed between interchange

partners. C214 SPECIAL SERVICES IDENTIFICATION C M

Identification of a special service by a code from a specified source or by description.

7161 Special services, coded C an..3 M

Code identifying a special service.

ABK Charge

ABP Carrier

ACA Allowance

ADI Royalties

AEC Distribution

Distribution of services or items.

Optional: Use with ALC01 (5463) = 'N' (No allowance or charge)

Each occurrence of ALC+N++++AEC... creates one

<Distribution> structure, which contains the customer's cost

account information. One or two segment account structures are

supported.

Requires ALC02: C552 (1230), ALC05: C214 (1131, 3055, 7160),

FTX, MOA.

ALC+N++++AEC... is allowed to repeat. Multiple occurrences

imply split accounting. The charge amounts should add up to the

line item total.

Example:

ALC+N+default+++AEC:175:92:DX41'




MOA+8:248.19:EUR'

produces...

<Distribution>


<AccountingSegment id="DX41">

<Name xml:lang="en">Cost Center</Name>

<Description xml:lang="en">Office Supplies</Description>


</Accounting>

<Charge>


</Charge>

</Distribution>

This example uses the preferred <AccountingSegment> in order to

capture the language code. Implemented with the (deprecated)

<Segment> element, it would be as such:

<Distribution>


<Segment type="Cost Center" id="DX41" description="Office

Supplies"/>

</Accounting>

<Charge>


</Charge>

</Distribution> Mapping target:

<Distribution>

<Accounting name=ALC02.C552.01>

<AccountingSegment id=ALC05.C214.04>

<Name xml:lang=FTX05>FTX04.C108.01</Name>

<Description

xml:lang=FTX05>FTX04.C108.02</Description>


[<AccountingSegment id=ALC05.C214.05>

<Name xml:lang=FTX05>FTX04.C108.03</Name>

<Description


</AccountingSegment>]

</Accounting>

<Charge>

<Money

currency=MOA01.C516.03>MOA01.C516.02</Money>

</Charge>

</Distribution>

AJ Adjustment

CL Contract Allowance

DI Discount

A reduction from a usual or list price.


One optional occurrence of ALC+A++++DI' builds an

<InvoiceDetailDiscount> structure.

Requires: MOA+8 (@1790, Group 42)

Optional: PCD+12 (@1760, Group 41)



Example:

ALC+A++++DI'

PCD+12:5:13'

MOA+8:5.77:EUR'

produces...

<InvoiceDetailDiscount percentageRate="5">


</InvoiceDetailDiscount>

Mapping target:

<InvoiceDetailDiscount

percentageRate=PCD01.C501.02>

<Money


</InvoiceDetailDiscount>

FAC FreightBasedOnDollarMinimum

FC Freight

HD Handling

IN Insurance

SAA Shipping and handling



One optional occurrence of ALC+C++++SAA... contributes the

required <Money> to an <InvoiceDetailLineShipping> structure.

Requires: MOA (@1790, Group 42)

Example:

ALC+C++++SAA'

MOA+8:5.80:EUR'

<InvoiceDetailLineShipping> is built from several places.

ALC+C++++SAA simply contributes the monetary charge. SC Surcharge

SF Discount-Special

SH Special handling service



One optional occurrence of SAC*C*H090*... builds an

<InvoiceDetailSpecialHandling> structure.

This is for special handling charges that would not ordinarily be

included with common Shipping and Handling.

Requires MOA (@1790, Group 42)

Optional: FTX (@1710)

Example:



ALC+C++++SH'

FTX+AAI+++Fragile packaging+en'

MOA+8:5.25:EUR'

produces...

<InvoiceDetailSpecialHandling>

<Description xml:lang="en">Fragile packaging</Description>


</InvoiceDetailSpecialHandling>

Mapping target:

<InvoiceDetailSpecialHandling>

<Description


<Money


</InvoiceDetailSpecialHandling>

SHP Shipping

TX Tax



One optional occurrence of ALC+C++++TX builds a <Tax>

structure.

Requires: FTX (@1710), MOA.(@1790, Group 42)

Example:

ALC+C++++TX'

FTX+AAI+++Total line tax+en'

MOA+8:55.00:EUR'

produces...

<Tax>


<Description xml:lang="en">Total line tax</Description>

</Tax>

Mapping target:

<Tax>

<Money


<Description


</Tax>

VAB Volume Discount

1131 Code list qualifier C an..3 D


175 Account analysis codes

Account service charges list.

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




92 Assigned by buyer or buyer's agent

7160 Special service C an..35 D


Use only with C214.01 (7161) = 'AEC'. This is the first Account Segment id.

7160 Special service C an..35 O


Use only with C214.01 (7161) = 'AEC'. This is the second Account Segment id.




Position: 1710


Level: 3


Max Use: 1

Purpose: A segment specifying a textual description of the allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:


Notes: Required for ALC+N+...+++AEC (Cost account distribution) and ALC+C++++TX

(Tax).

Optional for ALC+C++++SH (Special handling charge)







4453 TEXT FUNCTION, CODED C an..3 X


C107 TEXT REFERENCE C X


4441 Free text identification M an..17 X






C108 TEXT LITERAL C M


With ALC+C++++SH and ALC+C++++TX, this is simply free text forming the

description.

With ALC+N+...+++AEC, the 4440 data elements are paired. C108.01 forms the Segment

Name and C108.02 forms the Segment Description. This combines with ALC.C214.04 as

the Segment id.

If two Segments are being used, then ALC.C214.05 is the second id, C108.03 is the second

Name and C108.04 is the second Description. C108.05 is not used.

You must pair these properly. Name and Description are both required. 4440 Free text M an..70 M


4440 Free text C an..70 D










3453 LANGUAGE, CODED C an..3 M




Group: PCD Segment Group 41: Percentage Details

Position: 1750


Level: 3


Max Use: 1

Purpose: A group of segments specifying the percentage for the allowance or charge, e.g. The

allowance/charge amount is calculated as 5% of the goods value or a price reduction of 5% may

be specified if the goods quantity ordered is within the range 5 tons to 10 tons.


Segment Summary


No. ID Name Des. Use Repeat M 1760 PCD Percentage Details M 1





Group: Segment Group 41 (Percentage Details) Conditional (Optional)

Level: 3

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the percentage and the percentage basis for the calculation of the

allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example:

PCD:12:2.25:13'

Used with discounts (ALC01='A' and ALC0501='DI') to specify a discount percentage

based on the invoice value.








12 Discount






13 Invoice value









Position: 1780


Level: 3


Max Use: 2

Purpose: A group of segments specifying a monetary amount for an allowance or charge. A range to

which the allowance or charge applies can be specified, e.g. an allowance of 5000 BEF may be

specified if goods value ordered is greater than 100000 BEF.


Segment Summary







Group: Segment Group 42 (Monetary Amount) Conditional (Optional)

Level: 3

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the monetary amount for the allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:








8 Allowance or charge amount

[5422] Total amount of allowance or charge.

261 Alternate currency amount

MOA+261 is used to specify an alternate Amount and Currency

for tax, and it can be used only when MOA+8 is present.

Example

ALC+C++++TX'


MOA+8:10.22:USD'

MOA+261:100:INR'

.....











Group: TAX Segment Group 44: Duty/Tax/Fee Details

Position: 1860


Level: 3


Max Use: 5

Purpose: A group of segments specifying tax related information for the allowance or charge and, when

necessary.


Segment Summary


No. ID Name Des. Use Repeat M 1870 TAX Duty/Tax/Fee Details M 1 M 1880 MOA Monetary Amount C 2



Segment: TAX Duty/Tax/Fee Details



Level: 3

Usage: Mandatory

Max Use: 1

Purpose: A segment specifying the tax type, category, and rate, or exemption, related to the allowance or

charge.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Example: TAX+7+LOC++25.14+:::8'

A local tax of 8% on a taxable amount of 25.14.




5283 DUTY/TAX/FEE FUNCTION QUALIFIER M an..3 M

Code identifying the function of an duty, tax or fee information.

<TaxDetail purpose=TAX01>

5 Customs duty

Duties laid down in the Customs tariff to which goods are liable on

entering or leaving the Customs territory (CCC). TaxDetail@purpose="duty"

7 Tax


TaxDetail@purpose="tax"

C241 DUTY/TAX/FEE TYPE C O

Code and/or name identifying duty, tax or fee.

5153 Duty/tax/fee type, coded C an..3 O

Identification of the type of duty or tax or fee applicable to commodities or of tax

applicable to services. Refer to D.98A Data Element Dictionary for acceptable code values.





5152 Duty/tax/fee type C an..35 O

Type of duty or tax or fee applicable to commodities or of tax applicable to services.

Location or jurisdiction associated with this tax. This is just a name.

<TaxDetail>

<Location xml:lang=default>

Optional Location is captured and taken with default language.

C533 DUTY/TAX/FEE ACCOUNT DETAIL C X

Indication of account reference for duties, taxes and/or fees.

5289 Duty/tax/fee account identification M an..6 X

Identification of a particular duty, tax or fee.







5286 DUTY/TAX/FEE ASSESSMENT BASIS C an..15 O

Value or quantity on which a duty or tax will be assessed.

Taxable amount on which the tax percentage is calculated.

This amount can also be specified in MOA @1870 with qualifier 125 (Taxable amount). If

MOA+125 is present, then TAX04 (5286) is ignored.

If MOA+125 is not used, then the currency for TAX04 will be that from MOA+124.

<TaxDetail>

<TaxableAmount>

<Money currency=MOA01.03 (6345)>TAX04 (5286) </Money>

C243 DUTY/TAX/FEE DETAIL C O

Rate of duty/tax/fee applicable to commodities or of tax applicable to services.

TAX05 (C243) is optional in itself. If used, then C243.04 (5278) gives the percentage rate.

5279 Duty/tax/fee rate identification C an..7 O

Identification of the rate of duty or tax or fee applicable to commodities or of tax applicable

to services. Alternate amount for Tax amount can be specified. It can be present only if MOA+124 is

present.

If the alternate amount is present, then MOA+261 must also be present.

If this is not present, the alternate amount for the Tax amount is ignored.

Example:

ALC+C++++TX'


MOA+8:10.22:USD'

MOA+261:100:INR'

TAX+7+VAT:::Netherlands+TT+1257.14+500:::17.5++123456789B19?:A'

MOA+124:220:EUR'

<Tax>




<TaxDetail purpose="tax" category="vat" percentageRate="17.5">

<TaxableAmount>


</TaxableAmount>

<TaxAmount>



</TaxAmount>



</TaxDetail>

</Tax>



Example with taxPointDate:

<Tax>




<TaxDetail purpose="tax" category="vat" percentageRate="17.5"

taxPointDate="2003-07-13T12:30:00+05:30">

<TaxableAmount>


</TaxableAmount>

<TaxAmount>



</TaxAmount>



</TaxDetail>

</Tax>

Note: For ALC of type modifications, TAX.5153=TOT will be mapped to

<Tax>, rest will be mapped to <TaxDetail>

Example :

This is an example for Adjustment charge with Tax

ALC+C++++AJ'


MOA+8:248.19:EUR'

TAX+7+TOT:::Netherlands++1257.14+:::0++123456789B19?:A'

MOA+124:220:EUR'

TAX+7+VAT:::Netherlands++1257.14+:::3++Tax Description'

MOA+124:220:EUR'

<InvoiceItemModifications>

<Modification>

<AdditionalCost>


</AdditionalCost>

<Tax>


<Description xml:lang="en"></Description>

<TaxDetail category="vat" percentageRate="3" purpose="tax">

<TaxableAmount>


</TaxableAmount>

<TaxAmount>


</TaxAmount>


<Description xml:lang="en">Tax Description</Description>

</TaxDetail>

</Tax>




</Modification>

</InvoiceItemModifications>







5278 Duty/tax/fee rate C an..17 O

Rate of duty or tax or fee applicable to commodities or of tax applicable to services.

Taken as a percentage, so 17.5% is written as "17.5".

<TaxDetail percentage=TAX05.04 (5278)>

5273 Duty/tax/fee rate basis identification C an..12 X

Identification of the various elements of tax combination to be attributed to a commodity.





5305 DUTY/TAX/FEE CATEGORY, CODED C an..3 X

Code identifying a tax/duty/fee category within a tax/duty/fee type system.

Maps to the TaxDetail@exemptDetail.

TAX+7+VAT:::Netherlands+TT+1257.14+500:::0+Z+123456789B19?:A'

produces <TaxDetail … exemptDetail=“zeroRated”>

…. <TaxDetail>

TAX+7+VAT:::Netherlands+TT+1257.14+500:::0+E+123456789B19?:A'

produces <TaxDetail … exemptDetail=“exempt”>

…. <TaxDetail>

Z Zero Tax

E Exempt Tax

3446 PARTY TAX IDENTIFICATION NUMBER C an..20 O

Number assigned to a party by a taxation authority.

This is to specify the custom Tax Detail description (line item level).

For example:

TAX+..+VAT+... normally produces the TaxDetail description as "Value Added Tax".

In case if supplier wants to specify their own TaxDetail description at line item level, then

they need to use TAX07 for the same.

TAX+7+LOC:::Netherlands+TT+1257.14+:::17.5++Netherlands LC'

produces..

<Tax>

...

<TaxDetail ...>

...

<Description xml:lang="en">Netherlands LC</Description>

...

</TaxDetail>

<Tax>




Position: 1880


Level: 4


Max Use: 2

Purpose: A segment specifying the amount for the allowance or charge.

Dependency Notes:

Semantic Notes:

Comments:


Notes: One occurrence of MOA is required to specify the tax amount: MOA+124.

The taxable amount may optionally be specified here as well: MOA+125. If this is

present, then the TAX04 (5286) is ignored.








124 Tax amount

Tax imposed by government or other official authority related to the

weight/volume charge or valuation charge. Required

125 Taxable amount

Optional





6343 Currency qualifier C an..3 O



4405 Status, coded C an..3 O





Segment: UNS Section Control

Position: 2120

Group: Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A mandatory service segment placed before the first user segment in the summary section to

avoid segment collision.

Dependency Notes:

Semantic Notes:

Comments:




0081 SECTION IDENTIFIER M a1 M

A character identifying the next section in a message.

S Detail/summary section separation

To qualify the segment UNS, when separating the detail from the

summary section of a message.




Position: 2140

Group: Level: 1

Usage: Mandatory

Max Use: 100

Purpose: A group of segments giving total amounts for the whole invoice and - if relevant -detailing

amounts pre-paid with relevant references and dates.

Notes: Example:

MOA+289:95.18:EUR'

MOA+339:115.40:EUR'

MOA+340:109.63:EUR'

MOA+113:20.00:EUR'

MOA+9:89.63:EUR'

MOA+259:30:EUR'

MOA+260:40:EUR'

MOA+ZZZ:100:EUR'

This assumes a line item total of €95.18 (MOA+289). The shipping, special handling and

taxes in Group 16 total €20.22, bringing the gross amount to €115.40 (MOA+339). A 5%

discount of €5.77, also in Group 16, brings the net amount to €109.63 (MOA+340).

There was a prepayment of €20.00 (MOA+113), bringing the final amount due to €89.63

(MOA+9).

In cXML, this example renders to:

(tax and other charges and allowances not shown here)


<SubtotalAmount><Money currency="EUR">95.18</Money></SubtotalAmount>

<GrossAmount><Money currency="EUR">115.40</Money></GrossAmount>

<TotalCharges><Money currency="EUR">30.00</Money></TotalCharges>

<TotalAllowances><Money currency="EUR">40.00</Money></TotalAllowances>

<TotalAmountWithoutTax>


</TotalAmountWithoutTax>

<NetAmount><Money currency="EUR">109.63</Money></NetAmount>

<DepositAmount><Money currency="EUR">20.00</Money></DepositAmount>

<DueAmount><Money currency="EUR">89.63</Money></DueAmount>

</InvoiceDetailSummary> Required for summary totals. At least three occurrences are required, with MOA01

(C516).5025 = 9, 289, 340.

Invoice totals are calculated like this:

Line item total = MOA+289 (Subtotal amount)

+ taxes, special handling charges, shipping charges, but before discounts (see Group 16:

ALC) = MOA+339 (Original invoice gross total value)

- discounts (Group 16: ALC+A++++DI') = MOA+340 (Original total net invoice value)

- MOA+113 (Prepaid amount) = MOA+9 (Amount due/amount payable)

TotalCharges:

MOA+259. Represents the sum of all charges

Note:

MOA+259 is mandatory if at least 1 ALC of type modification charge is present.

If ALC is not present but MOA+259 is present this amount will be ignored.



TotalAllowances:

MOA+260. Represents the sum of all allowances.

Note:

MOA+260 is mandatory if at least 1 ALC of type modification allowance is present.

If ALC is not present but MOA+260 is present this amount will be ignored.

TotalAmountWithoutTax:

MOA+ZZZ. Represents sum of Subtotal, Charges (including special handling charges

and shipping charges), and Allowances (including discounts). This does not include

taxes.

Segment Summary







Group: Segment Group 50 (Monetary Amount) Mandatory

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment giving the total amounts for the whole invoice message such as message monetary

amount, message line item total amount, amount subject to payment discount, amount subject to

tax, alternative currency total amount, total additional amount, sub-total amounts prepaid, total

amount prepaid.

Dependency Notes:

Semantic Notes:

Comments:








9 Amount due/amount payable

Amount to be paid.

Required

<DueAmount>

<Money currency=DE6345>DE5004</Money>

</DueAmount>

113 Prepaid amount

(5302) Amount which has been prepaid in

advance.

Optional

<DepositAmount>


</DepositAmount>

289 Subtotal amount

Total amount of money that is part of a

complete amount.

Required

<SubtotalAmount>


</SubtotalAmount>

339 Original invoice gross total value

Indicates the gross total value of an original

invoice.

Optional

<GrossAmount>


</GrossAmount>

340 Original total net invoice value

Indicates the net value of an original invoice

after deduction or addition of all allowances

or charges.

Required



<NetAmount>


</NetAmount>

259 Total Charges

Indicates the sum of all charges.

Optional

<TotalCharges>


</TotalCharges>

260 Total Allowances

Indicates the sum of all allowances.

Optional

<TotalAllowances>


</TotalAllowances>

ZZZ Total Amount Without Tax

Represents sum of Subtotal, Charges (including special handling

charges and shipping charges), and Allowances (including

discounts). This does not include taxes.

Optional

<TotalAmountWithoutTax>


</ TotalAmountWithoutTax >











Segment: UNT Message Trailer

Position: 2270

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.

Dependency Notes:

Semantic Notes:

Comments:




0074 NUMBER OF SEGMENTS IN A MESSAGE M n..6 M

Control count of number of segments in a message.

0062 MESSAGE REFERENCE NUMBER M an..14 M

Unique message reference assigned by the sender.



10.8 Appendix A: RFF Mappings for Extrinsic and IdReference

This table shows the table of RFF qualifiers and their corresponding mappings for Extrinsic and IdReference.

The Description is plainly the UN/EDIFACT published definition. The cXML code is essentially that abbreviated into

cXML style syntax, and intended for machine processing in the cXML client.

The Description column is used for Extrinsic@name when coming from RFF @0120 (SG1@0110). When RFF @0250 is

used (SG3 @0240), a child of the NAD group (SG2 @0200), any valid EDIFACT RFF qualifier may be used beyond those

printed in the guideline. When one is used, an IdReference element is produced, with the @domain element taking the

cXML code and the @identifier element taking C506.02 [1154].

Note that this is an interim mapping. At the time of this writing, Ariba Network 4.0 FT4, Extrinsic data is displayed as a

name-value pair. Hence why the Description is used. In this fall of 2005 this may be change to map the cXML code instead

of the Description to the Extrinsic@name attribute.

Note that some of the cXML codes are slightly different than their traditional definition would imply, because they are

specially used by Ariba Buyer, which expects certain particular strings in IdReference@domain.

DE1153 cXML Description

AAA acknowledgementOfOrderNumber Acknowledgement of order number

AAB proformaInvoiceNumber Proforma invoice number

AAC documentaryCreditNumber Documentary credit number

AAD contractAddendumNumber Contract addendum number

AAE goodsDeclarationNumber Goods declaration number

AAG offerNumber Offer number

AAJ deliveryOrderNumber Delivery order number

AAK despatchAdviceNumber Despatch advice number

AAL drawingNumber Drawing number

AAM waybillNumber Waybill number

AAN deliveryScheduleNumber Delivery schedule number

AAO consigneesShipmentReferenceNumber Consignee's shipment reference number

AAP partConsignmentNumber Part consignment number

AAQ unitLoadDeviceIdNumber Unit load device (e.g. container) identification number

AAS transportDocumentNumber Transport document number

AAT masterLabelNumber Master label number

AAU despatchNoteNumber Despatch note number

AAV enquiryNumber Enquiry number

AAY carriersAgentReferenceNumber Carrier's agent reference number

AAZ standardCarrierAlphaCode Standard Carrier Alpha Code (SCAC) number

ABA customsValuationDecisionNumber Customs valuation decision number

ABB endUseAuthorizationNumber End use authorization number

ABC anti-dumpingCaseNumber Anti-dumping case number

ABD customsTariffNumber Customs tariff number

ABE declarantsReferenceNumber Declarant's reference number

ABG customsDecisionRequestNumber Customs decision request number

ABH sub-houseBillOfLadingNumber Sub-house bill of lading number

ABI deferredPaymentReference Deferred payment reference

ABJ quotaNumber Quota number

ABK transitGuaranteeBondNumber Transit (onward carriage) guarantee (bond) number

ABL customsGuaranteeNumber Customs guarantee number

ABM replacingPartNumber Replacing part number



ABN sellersCatalogueNumber Seller's catalogue number

ABO originatorsReference Originator's reference

ABP declarantsCustomsIdentityNumber Declarant's Customs identity number

ABQ importerReferenceNumber Importer reference number

ABR exportClearanceInstructionReference Export clearance instruction reference number

ABS importClearanceInstructionReference Import clearance instruction reference number

ABT customsDeclarationNumber Customs declaration number

ABU articleNumber Article number

ABV intra-plantRouting Intra-plant routing

ABW stockKeepingUnitNumber Stock keeping unit number

ABX textElementIdDeletionReference Text element identifier deletion reference

ABY allotmentIdentification(air) Allotment identification (air)

ABZ vehicleLicenceNumber Vehicle licence number

AC airCargoTransferManifest Air cargo transfer manifest

ACA cargoAcceptanceOrderReferenceNumber Cargo acceptance order reference number

ACB usGovernmentAgencyNumber Us government agency number

ACC shippingUnitIdentification Shipping unit identification

ACD additionalReferenceNumber Additional reference number

ACE relatedDocumentNumber Related document number

ACF addresseeReference Addressee reference

ACG ataCarnetNumber Ata carnet number

ACH packagingUnitIdentification Packaging unit identification

ACI outerpackagingUnitIdentification Outerpackaging unit identification

ACJ customerMaterialSpecificationNumber Customer material specification number

ACK bankReference Bank reference

ACL principalReferenceNumber Principal reference number

ACM uniqueREINACReferenceNumberOfSender Unique reinac reference number of the sender

ACN adviceOfCollectionNumber Advice of collection number

ACO ironChargeNumber Iron charge number

ACP hotRollNumber Hot roll number

ACQ coldRollNumber Cold roll number

ACR railwayWagonNumber Railway wagon number

ACS uniqueCURRACReferenceNumberOfSender Unique currac reference number of the sender

ACT uniqueClaimsReferenceNumberOfSender Unique claims reference number of the sender

ACU loss/eventNumber Loss/event number

ACV estimateOrderReferenceNumber Estimate order reference number

ACW referenceNumberToPreviousMessage Reference number to previous message

ACX bankersAcceptance Banker's acceptance

ACY dutyMemoNumber Duty memo number

ACZ equipmentTransportChargeNumber Equipment transport charge number

ADA buyersItemNumber Buyer's item number

ADB maturedCertificateOfDeposit Matured certificate of deposit

ADC loan Loan

ADD analysisNumber/testNumber Analysis number/test number

ADE accountNumber Account number

ADF treatyNumber Treaty number

ADG catastropheNumber Catastrophe number

ADH pcsCatastrophe Pcs catastrophe

ADI bureauSigning(statementReference) Bureau signing (statement reference)

ADJ company/SyndicateReference1 Company / syndicate reference 1

ADK company/SyndicateReference2 Company / syndicate reference 2

ADL orderingCustomerConsignmentRef Ordering customer consignment reference number



ADM shipownersAuthorizationNumber Shipowner's authorization number

ADN inlandTransportOrderNumber Inland transport order number

ADO containerWorkOrderReferneceNumber Container work order refernece number

ADP statementNumber Statement number

ADQ uniqueMarketReference Unique market reference

ADR bureauSigning(originalFdoReference) Bureau signing (original fdo reference)

ADS originalFdoTransactionReference Original fdo transaction reference

ADT groupAccounting Group accounting

ADU brokerReference1 Broker reference 1

ADV brokerReference2 Broker reference 2

ADW lloydsClaimsOfficeReference Lloyds claims office reference

ADY reportNumber Report number

ADZ traderAccountNumber Trader account number

AE authorizationForExpense(afe)Number Authorization for expense (afe) number

AEA governmentAgencyReferenceNumber Government agency reference number

AEB assemblyNumber Assembly number

AEC symbolNumber Symbol number

AED commodityNumber Commodity number

AEE eur1CertificateNumber Eur 1 certificate number

AEF customerProcessSpecificationNumber Customer process specification number

AEG customerSpecificationNumber Customer specification number

AEH applicableInstructionsOrStandards Applicable instructions or standards

AEI registrationNumberOfPrevCustomsDecl Registration number of previous customs declaration

AEJ post-entryReference Post-entry reference

AEK paymentOrderNumber Payment order number

AEL deliveryNumber(transport) Delivery number (transport)

AEM transportRoute Transport route

AEN customersUnitInventoryNumber Customer's unit inventory number

AEO productReservationNumber Product reservation number

AEP projectNumber Project number

AEQ drawingListNumber Drawing list number

AER projectSpecificationNumber Project specification number

AES primaryReference Primary reference

AET requestForCancellationNumber Request for cancellation number

AEU suppliersControlNumber Supplier's control number

AEV shippingNoteNumber Shipping note number

AEW emptyContainerBillNumber Empty container bill number

AEX nonNegotiableMaritimeTransportDocNo Non-negotiable maritime transport document number

AEY substituteAirWaybillNumber Substitute air waybill number

AEZ despatchNoteNumberPostParcels Despatch note (post parcels) number

AF airlinesFlightIdentificationNumber Airlines flight identification number

AFA throughBillOfLadingNumber Through bill of lading number

AFB cargoManifestNumber Cargo manifest number

AFC bordereauNumber Bordereau number

AFD customsItemNumber Customs item number

AFE exportControlCommodityNumber(eccn) Export control commodity number (eccn)

AFF marking/labelReference Marking/label reference

AFG tariffNumber Tariff number

AFH replenishmentPurchaseOrderNumber Replenishment purchase order number

AFI immedTransportationNoForInBondMvmt Immediate transportation no. for in bond movement

AFJ transportationExportNoForInBondMvmt Transportation exportation no. for in bond movement

AFK immediateExportNoForInBondMovement Immediate exportation no. for in bond movement



AFL associatedInvoices Associated invoices

AFM secondaryCustomsReference Secondary customs reference

AFN accountPartysReference Account party's reference

AFO beneficiarysReference Beneficiary's reference

AFP secondBeneficiarysReference Second beneficiary's reference

AFQ applicantsBankReference Applicant's bank reference

AFR issuingBanksReference Issuing bank's reference

AFS beneficiarysBankReference Beneficiary's bank reference

AFT directPaymentValuationNumber Direct payment valuation number

AFU directPaymentValuationRequestNumber Direct payment valuation request number

AFV quantityValuationNumber Quantity valuation number

AFW quantityValuationRequestNumber Quantity valuation request number

AFX billOfQuantitiesNumber Bill of quantities number

AFY paymentValuationNumber Payment valuation number

AFZ situationNumber Situation number

AGA agreementToPayNumber Agreement to pay number

AGB contractPartyReferenceNumber Contract party reference number

AGC accountPartysBankReference Account party's bank reference

AGD agentsBankReference Agent's bank reference

AGE agentsReference Agent's reference

AGF applicantsReference Applicant's reference

AGG disputeNumber Dispute number

AGH creditRatingAgencysReferenceNumber Credit rating agency's reference number

AGI requestNumber Request number

AGJ singleTransactionSequenceNumber Single transaction sequence number

AGK applicationReferenceNumber Application reference number

AGL deliveryVerificationCertificate Delivery verification certificate

AGM numberOfTemporaryImportDocument Number of temporary importation document

AGN referenceNumberQuotedOnStatement Reference number quoted on statement

AGO sendersReferenceToTheOriginalMsg Sender's reference to the original message

AGP companyIssuedEquipmentId Company issued equipment id

AGQ domesticFlightNumber Domestic flight number

AGR internationalFlightNumber International flight number

AGS employerIdNumberOfServiceBureau Employer identification number of service bureau

AGT serviceGroupIdentificationNumber Service group identification number

AGU memberNumber Member number

AGV previousMemberNumber Previous member number

AGW scheme/planNumber Scheme/plan number

AGX previousScheme/planNumber Previous scheme/plan number

AGY receivingPartysMemberID Receiving party's member identification

AGZ payrollNumber Payroll number

AHA packagingSpecificationNumber Packaging specification number

AHB authorityIssuedEquipmentID Authority issued equipment identification

AHC trainingFlightNumber Training flight number

AHD fundCodeNumber Fund code number

AHE signalCodeNumber Signal code number

AHF majorForceProgramNumber Major force program number

AHG nominationNumber Nomination number

AHH laboratoryRegistrationNumber Laboratory registration number

AHI transportContractReferenceNumber Transport contract reference number

AHJ payeesReferenceNumber Payee's reference number

AHK payersReferenceNumber Payer's reference number



AHL creditorsReferenceNumber Creditor's reference number

AHM debtorsReferenceNumber Debtor's reference number

AHN jointVentureReferenceNumber Joint venture reference number

AHO chamberOfCommerceRegistrationNumber Chamber of commerce registration number

AHP taxRegistrationNumber Tax registration number

AHQ woolIdentificationNumber Wool identification number

AHR woolTaxReferenceNumber Wool tax reference number

AHS meatProcessingEstablishmentReg Meat processing establishment registration number

AHT quarantine/treatmentStatusReference Quarantine/treatment status reference number

AHU requestForQuoteNumber Request for quote number

AHV manualProcessingAuthorityNumber Manual processing authority number

AHW importPermitNumber Import permit number

AHX rateNoteNumber Rate note number

AHY freightForwardNumber Freight forward number

AHZ customsReleaseCode Customs release code

AIA complianceCodeNumber Compliance code number

AIB departmentOfTransportationBondNo Department of transportation bond number

AIC exportEstablishmentNumber Export establishment number

AID certificateOfConformity Certificate of conformity

AIE ministerialCertOfHomologation Ministerial certificate of homologation

AIF previousDeliveryInstructionNumber Previous delivery instruction number

AIG passportNumber Passport number

AIH commonTransactionReferenceNumber Common transaction reference number

AII banksCommonTransactionRef Bank's common transaction reference number

AIJ customersIndividualTransactionRef Customer's individual transaction reference number

AIK banksIndividualTransactionRef Bank's individual transaction reference number

AIL customersCommonTransactionRef Customer's common transaction reference number

AIM individualTransactionReferenceNo Individual transaction reference number

AIN productSourcingAgreementNumber Product sourcing agreement number

AIO customsTranshipmentNumber Customs transhipment number

AIP customsPreferenceInquiryNumber Customs preference inquiry number

AIQ packingPlantNumber Packing plant number

AIR originalCertificateNumber Original certificate number

AIS processingPlantNumber Processing plant number

AIT slaughterPlantNumber Slaughter plant number

AIU chargeCardAccountNumber Charge card account number

AIV eventReferenceNumber Event reference number

AIW transportSectionReferenceNumber Transport section reference number

AIX referredProductForMechAnalysis Referred product for mechanical analysis

AIY refferredProductForChemicalAnalysis Refferred product for chemical analysis

AIZ consolidatedInvoiceNumber Consolidated invoice number

AJA partReferenceIndicatorInDrawing Part reference indicator in drawing

AJB u.s.CodeOfFederalRegulation(cfr) U.s. code of federal regulation (cfr)

AJC purchasingActivityClauseNumber Purchasing activity clause number

AJD usDefenseFedAcquisitionRegSupp U.S. defense federal acquisition regulation supplement

AJE agencyClauseNumber Agency clause number

AJF circularPublicationNumber Circular publication number

AJG u.s.FederalAcquisitionRegulation U.s. Federal acquisition regulation

AJH usGeneralServicesAdminRegulation U.S. General services administration regulation

AJI usFedInfoResourcesMgmtRegulation U.S. Federal Information Resources Management Regulation

AJJ paragraph Paragraph

AJK specialInstructionsNumber Special instructions number



AJL siteSpecificProcsTermsAndCondsNo Site specific procedures, terms and conditions number

AJM masterSolicitatonProcsTerms&CondsNo Master solicitaton procedures, terms and conditions number

AJN usDeptVeteransAffairsAcquisitionReg U.S. Department of Veterans Affairs Acquisition Regulation

AJO militaryMIPR Military interdepartmental purchase request (mipr) number

AJP foreignMilitarySalesNumber Foreign military sales number

AJQ defensePrioritiesAlloSysPriorityRtg Defense priorities allocaiton systems priority rating

AJR wageDeterminationNumber Wage determination number

AJS agreementNumber Agreement number

AJT sicNumber Standard Industry Classification (SIC) Number

AJU endItemNumber End item number

AJV federalSupplyScheduleItemNumber Federal supply schedule item number

AJW technicalDocumentNumber Technical document number

AJX technicalOrderNumber Technical order number

AJY suffix Suffix

AJZ transportationAccountNumber Transportation account number

AKA containerDispositionOrderRefNo Container disposition order reference number

AKB containerPrefix Container prefix

AKC transportEquipmentReturnReference Transport equipment return reference

AKD transportEquipmentSurveyReference Transport equipment survey reference

AKE transportEquipmentSurveyReportNo Transport equipment survey report number

AKF transportEquipmentStuffingOrder Transport equipment stuffing order

AKG vehicleIdentificationNumber(vin) Vehicle identification number (vin)

AKH governmentBillOfLading Government bill of lading

AKI orderingCustomersSecondReferenceNo Ordering customer's second reference number

AKJ directDebitReference Direct debit reference

AKK meterReadingAtBeginningOfDelivery Meter reading at the beginning of the delivery

AKL meterReadingAtTheEndOfDelivery Meter reading at the end of delivery

AKM replenishPurchaseOrderRangeStartNo Replenishment purchase order range start number

AKN thirdBanksReference Third bank's reference

AKO actionAuthorizationNumber Action authorization number

AKP appropriationNumber Appropriation number

AKQ productChangeAuthorityNumber Product change authority number

AKR generalCargoConsignmentReferenceNo General cargo consignment reference number

AKS cadtaloqueSequenceNumber Cadtaloque sequence number

AKT forwardingOrderNumber Forwarding order number

AKU transportEquipmentSurveyReferenceNo Transport equipment survey reference number

AKV leaseContractReference Lease contract reference

AKW transportCostReferenceNumber Transport cost reference number

AKX transportEquipmentStrippingOrder Transport equipment stripping order

AKY priorPolicyNumber Prior policy number

AKZ policyNumber Policy number

ALA procurementBudgetNumber Procurement budget number

ALB domesticInventoryManagementCode Domestic inventory management code

ALC customerRefNoAssignedToPrevBalance Customer reference number assigned to previous balance

ALD previousCreditAdviceReferenceNumber Previous credit advice reference number

ALE reportingFormNumber Reporting form number

ALF authNoForExceptionToDangerousGoods Authorization number for exception to dangerous goods

ALG dangerousGoodsSecurityNumber Dangerous goods security number

ALH dangerousGoodsTransportLicenceNo Dangerous goods transport licence number

ALI previousRentalAgreementNumber Previous rental agreement number

ALJ nextRentalAgreementReasonNumber Next rental agreement reason number

ALK consigneesInvoiceNumber Consignee's invoice number



ALL messageBatchNumber Message batch number

ALM previousDeliveryScheduleNumber Previous delivery schedule number

ALN physicalInventoryRecountReferenceNo Physical inventory recount reference number

ALO receivingAdviceNumber Receiving advice number

ALP returnableContainerReferenceNumber Returnable container reference number

ALQ returnsNoticeNumber Returns notice number

ALR salesForecastNumber Sales forecast number

ALS salesReportNumber Sales report number

ALT previousTaxControlNumber Previous tax control number

ALU agerdNumber AGERD (Aerospace Ground Equipment Requirement Data) Number

ALV registeredCapitalReference Registered capital reference

ALW standardNumberOfInspectionDocument Standard number of inspection document

ALX model Model

ALY financialManagementReference Financial management reference

ALZ notificationForCollectionNumber Notification for collection number (NOTICOL)

AMA prevReqForMeteredReadingReferenceNo Previous request for metered reading reference number

AMB nextRentalAgreementNumber Next rental agreement number

AMC refNoOfARequestForMeteredReading Reference number of a request for metered reading

AMD hasteningNumber Hastening number

AME repairDataRequestNumber Repair data request number

AMF consumptionDataRequestNumber Consumption data request number

AMG profileNumber Profile number

AMH caseNumber Case number

AMI govtQualityAssuranceAndCtrlLevelNo Government quality assurance and control level number

AMJ paymentPlanReference Payment plan reference

AMK procurementBudgetNumber2 Procurement budget number

AML replenishmentPurchaseOrderRngAndNo Replenishment purchase order range and number

AMM insurerAssignedReferenceNumber Insurer assigned reference number

AMN canadianExciseEntryNumber Canadian excise entry number

AMO premiumRateTable Premium rate table

AMP adviseThroughBanksReference Advise through bank's reference

AMQ usDeptOfTransportBondSuretyCode US Department of Transportation Bond Surety Code

AMR usFDAEstablishmentIndicator US Food and Drug Administration Establishment Indicator

AMS usFCCImportCondition US Federal Communications Commission (FCC) Import Condition

AMT goodsAndServicesTaxIdentificationNo Goods and Services Tax Identification Number

AMU integratedLogisticSupportCrossRefNo Integrated logistic support cross reference number

AMV departmentNumber Department number

AMW buyersCatalogueNumber Buyer's catalogue number

AMX financialSettlementPartyReferenceNo Financial settlement party's reference number

AMY standardsVersionNumber Standard's version number

AMZ pipelineNumber Pipeline number

ANA accountServicingBanksReferenceNo Account servicing bank's reference number

ANB completedUnitsPaymentRequestRef Completed units payment request reference

ANC paymentInAdvanceRequestReference Payment in advance request reference

AND parentFile Parent file

ANE subFile Sub file

ANF cadFileLayerConversion Cad file layer conversion

ANG technicalRegulation Technical regulation

ANH plotFile Plot file

ANI fileConversionJournal File conversion journal

ANJ authorizationNumber Authorization number

ANK referenceNumberAssignedToThirdParty Reference number assigned to third party



ANM nameBanksReference Name bank's reference

ANN draweesReference Drawee's reference

ANO caseOfNeedPartysReference Case of need party's reference

ANP collectingBanksReference Collecting bank's reference

ANQ remittingBanksReference Remitting bank's reference

ANR principalsBankReference Principal's bank reference

ANS presentingBanksReference Presenting bank's reference

ANT consigneesReference Consignee's reference

ANU financialTransactionReferenceNumber Financial transaction reference number

ANV creditReferenceNumber Credit reference number

ANW receivingBanksAuthorizationNumber Receiving bank's authorization number

ANX clearingReference Clearing reference

ANY sendingBanksReferenceNumber Sending bank's reference number

ANZ directDebitReference2 Direct debit reference

AOA documentaryPaymentReference Documentary payment reference

AOB thirdBanksReference2 Third bank's reference

AOC orderingCustomers2ndReferenceNo Ordering customer's second reference number

AOD accountingFileReference Accounting file reference

AOE sendersFileReferenceNumber Sender's file reference number

AOF receiversFileReferenceNumber Receiver's file reference number

AOG sourceDocumentInternalReference Source document internal reference

AOH principalsReference Principal's reference

AOI debitReferenceNumber Debit reference number

AP accountReceivableID Accounts receivable number

ASC assumingCompany Assuming company

AU authorizationToMeetCompetitionNo Authorization to meet competition number

AV accountPayableID Account Payable number

AWA rateCodeNumber Rate code number

AWB airWaybillNumber Air waybill number

AWC documentaryCreditAmendmentNumber Documentary credit amendment number

AWD advisingBanksReference Advising bank's reference

AWE costCentre Cost centre

AWF workItemQuantityDetermination Work item quantity determination

AWG internalDataProcessNumber Internal data process number

AWH categoryOfWorkReference Category of work reference

AWI policyFormNumber Policy form number

BA beginningMeterReadingActual Beginning meter reading actual

BC buyersContractNumber Buyer's contract number

BD bidNumber Bid number

BE beginningMeterReadingEstimated Beginning meter reading estimated

BH houseBillOfLadingNumber House bill of lading number

BM billOfLadingNumber Bill of lading number

BN bookingReferenceNumber Booking reference number

BO blanketOrderNumber Blanket order number

BR brokerOrSalesOfficeNumber Broker or sales office number

BT batchNumber/lotNumber Batch number/lot number

BW blendedWithNumber Blended with number

CAS iataCargoAgentCassAddressNumber Iata cargo agent cass address number

CD creditNoteNumber Credit note number

CEC cedingCompany Ceding company

CFE consigneesFurtherOrder Consignee's further order

CFO consignorsFurtherOrder Consignor's further order



CG consigneesOrderNumber Consignee's order number

CH customerCatalogueNumber Customer catalogue number

CK chequeNumber Cheque number

CKN checkingNumber Checking number

CM creditMemoNumber Credit memo number

CMR roadConsignmentNoteNumber Road consignment note number

CN carrierShipmentID Carrier's reference number

CNO chargeNoteReferenceNumber Charge note reference number

CO buyersOrderNumber Buyers order number

COF callOffOrderNumber Call off order number

CP conditionOfPurchaseDocumentNumber Condition of purchase document number

CR customerReferenceNumber Customer reference number

CRN conveyanceReferenceNumber Conveyance reference number

CS conditionOfSaleDocumentNumber Condition of sale document number

CST teamAssignmentNumber Team assignment number

CT contractNumber Contract number

CU consignorsReferenceNumber Consignor's reference number

CV containerOperatorsReferenceNumber Container operators reference number

CW packageNumber Package number

CZ cooperationContractNumber Cooperation contract number

DA defermentApprovalNumber Deferment approval number

DAN debitAccountNumber Debit account number

DB buyersDebtorNumber Buyer's debtor number

DI distributorInvoiceNumber Distributor invoice number

DL debitNoteNumber Debit note number

DM documentNumber Document number

DQ deliveryNoteNumber Delivery note number

DR dockReceiptNumber Dock receipt number

EA endingMeterReadingActual Ending meter reading actual

EB embargoPermitNumber Embargo permit number

ED exportDeclaration Export declaration

EE endingMeterReadingEstimated Ending meter reading estimated

EI employersIdentificationNumber Employer's identification number

EN embargoNumber Embargo number

EP exportPermitNumber Export permit number

EQ equipmentNumber Equipment number

ER container/equipmentReceiptNumber Container/equipment receipt number

ERN exportersReferenceNumber Exporter's reference number

ET excessTransportationNumber Excess transportation number

EX exportLicenceNumber Export licence number

FC fiscalNumber Fiscal number

FF freightForwardersReferenceNumber Freight forwarder's reference number

FI fileLineIdentifier File line identifier

FLW flowReferenceNumber Flow reference number

FN freightBillNumber Freight bill number

FO foreignExchange Foreign exchange

FS finalSequenceNumber Final sequence number

FT freeZoneIdentifier Free zone identifier

FV fileVersionNumber File version number

FX foreignExchangeContractNumber Foreign exchange contract number

GA standardsNumber Standard's number

GC governmentContractNumber Government contract number



GD standardsCodeNumber Standard's code number

GDN generalDeclarationNumber General declaration number

GN governmentReferenceNumber Government reference number

HS harmonisedSystemNumber Harmonised system number

HWB houseWaybillNumber House waybill number

IA internalVendorNumber Internal vendor number

IB inBondNumber In bond number

ICA iataCargoAgentCodeNumber Iata cargo agent code number

ICE insuranceCertificateReferenceNumber Insurance certificate reference number

ICO insuranceContractReferenceNumber Insurance contract reference number

II initialSampleInspectionReportNumber Initial sample inspection report number

IL internalOrderNumber Internal order number

INB intermediaryBroker Intermediary broker

INN interchangeNumberNew Interchange number new

INO interchangeNumberOld Interchange number old

IP importLicenceNumber Import licence number

IS invoiceNumberSuffix Invoice number suffix

IT internalCustomerNumber Internal customer number

IV invoiceNumber Invoice number

JB jobNumber Job number

JE endingJobSequenceNumber Ending job sequence number

LA shippingLabelSerialNumber Shipping label serial number

LAN loadingAuthorizationNumber Loading authorization number

LAR lowerArticleNumberOfRange Lower article number of range

LB lockbox Lockbox

LC letterOfCreditNumber Letter of credit number

LI lineItemReferenceNumber Line item reference number

LO loadPlanningNumber Load planning number

LS barCodedLabelSerialNumber Bar coded label serial number

MA shipNoticeID Ship notice/manifest number

MB masterBillOfLadingNumber Master bill of lading number

MF manufacturersPartNumber Manufacturer's part number

MG meterUnitNumber Meter unit number

MH manufacturingOrderNumber Manufacturing order number

MR messageRecipient Message recipient

MRN mailingReferenceNumber Mailing reference number

MS messageSender Message sender

MSS manufacturerMaterialSafetyDataSheet Manufacturer's material safety data sheet number

MWB masterAirWaybillNumber Master air waybill number

NA northAmericanHazardousGoodsClassNo North American Hazardous Goods Classification Number

OH currentInvoiceNumber Current invoice number

OI previousInvoiceNumber Previous invoice number

ON purchaseOrderID Order number (purchase)

OP originalPurchaseOrder Original purchase order

OR generalOrderNumber General order number

PB payersFinancialInstitutionAccountNo Payer's financial institution account number

PC productionCode Production code

PD promotionDealNumber Promotion deal number

PE plantNumber Plant number

PF primeContractorContractNumber Prime contractor contract number

PI priceListVersionNumber Price list version number

PK packingListNumber Packing list number



PL priceListNumber Price list number

POR purchaseOrderResponseNumber Purchase order response number

PP purchaseOrderChangeNumber Purchase order change number

PQ paymentReference Payment reference

PR priceQuoteNumber Price quote number

PS purchaseOrderNumberSuffix Purchase order number suffix

PW priorPurchaseOrderNumber Prior purchase order number

PY accountID Payee's financial institution number

RA remittanceAdviceNumber Remittance advice number

RC rail/roadRoutingCode Rail/road routing code

RCN railwayConsignmentNoteNumber Railway consignment note number

RE releaseNumber Release number

REN receivedNumber Received number

RF exportReferenceNumber Export reference number

RR payerFinancialInstTransitRoutingNo Payer's Financial Institution Transit Routing No.(ACH Transfers)

RT bankRoutingID Payee's financial institution transit routing no

SA salesPersonNumber Sales person number

SB salesRegionNumber Sales region number

SD salesDepartmentNumber Sales department number

SE serialNumber Serial number

SF shipFrom Ship from

SH previousHighestScheduleNumber Previous highest schedule number

SI sid SID (Shipper's Identifying Number for Shipment)

SM salesOfficeNumber Sales office number

SN sealNumber Seal number

SP scanLine Scan line

SQ equipmentSequenceNumber Equipment sequence number

SRN shipmentReferenceNumber Shipment reference number

SS sellersReferenceNumber Sellers reference number

STA stationReferenceNumber Station reference number

SW swapOrderNumber Swap order number

SZ specificationNumber Specification number

TB truckersBillOfLading Trucker's bill of lading

TE telexMessageNumber Telex message number

TF transferNumber Transfer number

TI tirCarnetNumber Tir carnet number

TL taxExemptionID Tax exempt licence number

TN transactionReferenceNumber Transaction reference number

TP testReportNumber Test report number

UAR upperSerialNumberOfRange Upper serial number of range

UC ultimateCustomersReferenceNumber Ultimate customer's reference number

UCN uniqueConsignmentReferenceNumber Unique consignment reference number

UN undgNumber United Nations Dangerous Goods (UNDG) Number

UO ultimateCustomersOrderNumber Ultimate customer's order number

VA vatID VAT registration number

VC vendorContractNumber Vendor contract number

VM vesselIdentification Vessel identification

VN supplierOrderID Order number (vendor)

VON voyageNumber Voyage number

VP vendorProductNumber Vendor product number

VR vendorIdNumber Vendor id number

VS vendorOrderNumberSuffix Vendor order number suffix



VT motorVehicleIdentificationNumber Motor vehicle identification number

VV voucherNumber Voucher number

WE warehouseEntryNumber Warehouse entry number

WM weightAgreementNumber Weight agreement number

WN wellNumber Well number

WR warehouseReceiptNumber Warehouse receipt number

WS warehouseStorageLocationNumber Warehouse storage location number

WY railWaybillNumber Rail waybill number

XA company/placeRegistrationNumber Company/place registration number

XC cargoControlNumber Cargo control number

XP previousCargoControlNumber Previous cargo control number

ZZZ mutuallyDefined Mutually defined reference number

ariba sn edifact invoic implementation guide - help.sap.com

Documents