• No results found

DOCUMENT "INVOICE" USE PROFILE

N/A
N/A
Protected

Academic year: 2021

Share "DOCUMENT "INVOICE" USE PROFILE"

Copied!
6
0
0

Loading.... (view fulltext now)

Full text

(1)

DOCUMENT

"INVOICE"

USE PROFILE

Date of release: 2009-12-11

(2)

1. BUSINESS DESCRIPTION

1.1 This document

This document is a use profile of UBL Invoice 2.0 document

(http://docs.oasis-open.org/ubl/os-UBL-2.0/xsd/maindoc/UBL-Invoice-2.0.xsd) for the Textile/Clothing and Footwear industry.

1.2 Generalities

A document claiming payment for goods or services supplied under conditions agreed between the

supplier and the customer. In most cases this document describes the actual financial commitment of

goods or services ordered from the supplier.

(3)

3

2. USE PROFILE

2.1 General structure of XML document

All the business data that can be exchanged through this class of documents are shown in the following

"document structure", that provides a simplified vision of the Schema.

In particular:

- the two numbers following each element define its "cardinality" (minimum and maximum number of

occurrences); the minimum equal zero indicates that the element is optional, the minimum greater than

zero indicates that is mandatory;

- the bold character denotes the complex elements (aggregates of simple elements) that were built for the

sake of functionality and re-usability of some complex information sets. The child elements in each parent

element are easily spotted as "indented";

- the symbol "@" denotes an attribute of the preceding element; here "the usage indicator (optional,

required, ...) is shown in square brackets.

In the right column the content of each element is described.

Structure

XML Tag

Content description

Invoice

UBLVersionID 1-1 Constant: 2.0

CustomizationID 1-1 Constant: “eBIZ-TCF-v2008-1” ProfileID 1-1 Constant: “eBIZ-TCF-Invoice”

ID 1-1 Document number: an identifier for the Invoice

assigned by the issuer.

CopyIndicator 0-1 Document function: the function performed by the

present message with regards to the .

Possible values: true (the document is a copy) or

false (the document is the original).

IssueDate 1-1 Document date: the date on which the Invoice was

issued.

Note 0-1 Invoice text: free-form text (note or similar information) applying to the document.

DocumentCurrencyCode 1-1 Invoice currency: the currency that is used for prices

in the Invoice (ISO code). @listID [optional] Constant: “ISO 4217”

OrderReference 1-1

ID 1-1 Customer order number: the Order identifier

assigned by the Buyer (the reference of the Order associated to this Invoice).

SalesOrderID 1-1 Supplier order number: the Order Identifier

assigned by the Supplier (the reference of the Order associated to this Invoice).

IssueDate 0-1 Order date: the date on which the Order was issued.

CustomerReference 0-1 Customer reference number:a reference applied to the Order document by the order issuer (Buyer).

DespatchDocumentReference 0-1

ID 1-1 Despatch advice number: the identifier of the

Despatch Advice (the reference of the Despatch Advice associated to this Invoice).

IssueDate 0-1 Despatch advice date: the issue date of the

Despatch Advice.

AdditionalDocumentReference 1-1

ID 1-1 Delivery note number: the identifier of the Delivery

Note (the reference of the Delivery Note associated to this Invoice).

(4)

IssueDate 0-1 Delivery note date: the issue date of the Delivery

Note.

DocumentType 0-1 Constant: “Delivery note”

AccountingSupplierParty 1-1 Party 1-1

PhysicalLocation 1-1

ID 1-1 GLN supplier: GLN code of the place where the

Supplier’s physical location is. @schemeName [optional] Constant: “GLN”

PartyTaxScheme 1-1

CompanyID 1-1 VAT Id supplier: the identifier assigned for tax

purposes to the Supplier by the taxation authority. @schemeName [optional]

TaxScheme 1-1

ID 1-1 Identifies the tax scheme. Constant: “VAT”

AccountingCustomerParty 1-1 Party 1-1

PhysicalLocation 1-1

ID 1-1 GLN invoicee: GLN code of the place where the

physical location of the legal recipient of the Invoice is (who pays the invoice).

@schemeName [optional] Constant: “GLN”

BuyerCustomerParty 1-1 Party 1-1

PhysicalLocation 1-1

ID 1-1 GLN buyer: GLN code of the place where the Buyer’s

physical location is (the legal buyer of goods, normally the headquarter of the Buyer). @schemeName [optional] Constant: “GLN”

PartyTaxScheme 1-1

CompanyID 1-1 VAT Id buyer: the identifier assigned for tax purposes

to the Buyer by the taxation authority. @schemeName [optional]

TaxScheme 1-1

ID 1-1 Identifies the tax scheme. Constant: “VAT”

Delivery 1-1

ActualDeliveryDate 0-1 Delivery date: the date on which the goods were

delivered.

DeliveryLocation 1-1

ID 1-1 GLN delivery location: GLN code of place where the

goods have been physically brought to by the Supplier or his agent.

@schemeName [optional] Constant: “GLN”

DeliveryParty 1-1

PhysicalLocation 1-1

ID 1-1 GLN ultimate consignee: GLN code of the place

inside the property of the retailer where the goods have been finally meant for. The Supplier isn’t involved in this transport.

@schemeName [optional] Constant: “GLN”

PaymentMeans 0-1

PaymentMeansCode 1-1 Default: 1 (= “Instrument not defined”) @listID [optional] Default: “UN/ECE 4461”

PaymentDueDate 1-1 Value date: the date when the invoice is due.

AllowanceCharge 0-3 This element can be used to specify information

about:

- the “Freight costs amount”: in this case a charge is specified and the ChargeIndicator value must be

(5)

5

true and the AllowanceChargeReason must be

“Freight costs”; and/or

- the “Invoice discount amount”: in this case, a discount is specified and the ChargeIndicator value must be false and the AllowanceChargeReason must be “Invoice discount”;

and/or

- the “Minimum order charge amount”: in this case, a case a charge is specified and the ChargeIndicator value must be true and the AllowanceChargeReason must be “Minimum order charge”;

ChargeIndicator 1-1 Indicates whether the Allowance Charge is a charge (true) or a discount (false).

AllowanceChargeReason 1-1 The reason for the Allowance Charge. Possible values:

- “Freight costs”; - “Invoice discount”; - “Minimum order charge”. Amount 1-1 In case of

Freight costs amount: costs incurred by the

shipper in moving goods, by whatever means, from one place to another.

In case of

Invoice discount amount: the allowances applied

to the Invoice as a whole. In case of

Minimum order charge amount: extra charge

when the invoice amount is below a certain limit. @currencyID [required] Currency: currency of the amount (ISO code). TaxTotal 1-1

TaxAmount 1-1 Tax total: the total tax amount (it’s the same value of

TaxSubtotal/TaxAmount).

@currencyID [required] Currency: currency of the amount (ISO code). TaxSubtotal 1-1

TaxableAmount 0-1 Taxable amount: the net amount to which the tax

percent (rate) is applied to calculate the tax amount. @currencyID [required] Currency: currency of the amount (ISO code).

TaxAmount 1-1 Tax total: the total tax amount.

@currencyID [required] Currency: currency of the amount (ISO code).

Percent 1-1 Invoice tax rate: the tax rate expressed as a

percentage. TaxCategory 1-1

TaxScheme 1-1

ID 1-1 Identifies the tax scheme. Constant: “VAT”

LegalMonetaryTotal 1-1

PayableAmount 1-1 Payable amount: the total amount to be paid.

@currencyID [required] Currency: currency of the amount (ISO code). InvoiceLine 1-9999

ID 1-1 Line number: an unique identifier for the invoice

line.

InvoicedQuantity 1-1 Invoice quantity: the quantity of articles on the

invoice line.

@unitCode [optional] Measurement unit: the unit of the invoice quantity.

LineExtensionAmount 1-1 Line amount: the total amount for the invoice line,

including Allowance Charges but net of taxes. @currencyID [required] Currency line amount: the currency that is used for

(6)

the line amount.

Item 1-1

Name 1-1 Article name: a short name optionally given to an

item, such as a name from a Catalogue, as distinct from a description.

SellerItemIdentification 1-1

ID 1-1 Supplier article number: an identifier for the item

assigned by the Supplier. StandardItemIdentification 1-1

ID 1-1 GTIN: GTIN (Global Trade Item Number) article

identification code.

In case of local identification systems it is necessary to declare the issuer in the schemeName attribute and to put anyway the identifier in this element.

@schemeName [required] Default: “GTIN”

MeasurementDimension 0-1

AttributeID 1-1 Constant: “Net weight”

Measure 1-1 Net weight: the net weight of the single unit of article,

declared for transport or customs purpose. @unitCode [required] Measurement unit: the unit of the “Net weight”. OriginCountry 0-1 Country of origin: the origin country of the article.

IdentificationCode 0-1 The country name expressed as code. @listID [optional] Default: “ISO 3166-1”

Name 0-1 The country name expressed as text.

CommodityClassification 0-1

ItemClassificationCode 0-1

Customs tariff number: the product code from

harmonised system of customs authorities. @listName [required] Constant: “Custom tariff”

ManufacturerParty 0-1

PhysicalLocation 1-1

ID 1-1 GLN manufacturer: GLN code of the place where

the Manufacture’s physical location is (used only if the Manufacturer isn’t the Supplier).

@schemeName [optional] Constant: “GLN”

Price 1-1

PriceAmount 1-1 Invoice price: the price of the article specified.

@currencyID [required] Currency: the currency that is used for the invoice

price.

BaseQuantity 1-1 The actual quantity to which the price applies. Constant: 1

References

Related documents

• CCAR 2011, has been followed with CCAR 2012 and CCAR 2013 – in alignment with the Dodd Frank Act’s requirements for annual capital adequacy assessment and stress

However, other photographic sequences have shown that when a 2 mm diameter tungsten carbide sphere impacted a block of soda – lime glass at normal incidence at a velocity of 130

An analysis of the economic contribution of the software industry examined the effect of software activity on the Lebanese economy by measuring it in terms of output and value

Now we consider the various types of data that can be used as inputs to this adaptive filter structure. Real data types have been used in the early types of adaptive filters.

“Reiki Shamanism: A Guide to Out-of-Body Healing” (Findhorn Press, Scotland, 2008). I have a MySpace page, called “Clear Eyes Shaman,” dedicated for display on other MySpace

This research study examined the effectiveness of the Sistas Accessing HIV/AIDS Resources At a click (SAHARA) computer-based, behavioral prevention intervention with a population

Uniting theoretical approaches to fairness to an overview of the empirical literature, we illuminate the salient features of fairness relations in complex

Exercise is Medicine® Australia Locked Bag 102, Albion DC QLD 4010 Phone: 07 3862 4122 | Fax: 07 3862 3588 | Email: [email protected] Role of an AEP The most