Invoice

Uses the Component:InvoiceType

Vehicle Invoice Header

Fields and Components

Table 6.37. Fields and Components

Name Description Occurrence Type Data Type User Notes
InvoiceNumberString

Invoice number

0..1Field qdt:StringType  
InvoiceTotalAmount

Invoice Total

0..1Field udt:AmountType  
LoadNumberString

Shipment carrier-assigned load number

0..1Field qdt:StringType  
BorderCrossingIndicator

BorderCrossing Indicator

0..1Field udt:IndicatorType  
PortOfEntry

Port of Entry

0..1Field udt:TextType  
ETADate

Estimated time of arrival

0..1Field udt:DateType  
CarrierID

Carrier Code

0..1Field udt:IdentifierType  
WarehouseID

Warehouse Number

0..1Field udt:IdentifierType  
OrderDate

Date order originally placed

0..1Field udt:DateType  
VehicleInvoiceVehicleLineItem

Detail information regarding a vehicle for a particular invoice.

0..*ComponentVehicleInvoiceVehicleLineItemType 
Tax

The Tax component represents information about a particular tax including information about the type of tax and the amount of the tax.

0..*ComponentTaxType 
DealerAssignedNumberString

The number given to an order by a dealer

0..1Field qdt:StringType  
StatusDate

The date the current status was recorded

0..1Field udt:DateType  
TargetBuildDate

The date the OEM expects to build the vehicle

0..1Field udt:DateType  
RejectCode

A code representing a reject reason

0..1Field udt:CodeType  
OptionRestrictionStatements

Information about option restrictions on the vehicle

0..1Field udt:TextType  
HoldCodeIndicator

Representing hold status

0..1Field udt:IndicatorType  
RejectResponsibilityCode

A code indicating who has action to take to address a reject

0..1Field udt:CodeType  
VehicleInvoiceTypeCode

A code indicating the invoice type. Valid values are Retail-Stock, Fleet, Sold.

0..1Field udt:CodeType  
InvoiceDocText

Response message that shows the Invoice document in the XML contains tag to start and stop Invoice document text.

0..1Field udt:TextType  

Sample XML

The XML Sample provided here is an approximation of the generated XML for this component. Not all of the fields are required for implementation.

Example 6.37. Invoice

<Invoice>
     <InvoiceNumberString>......</InvoiceNumberString>     [0..1]
     <InvoiceTotalAmount>......</InvoiceTotalAmount>     [0..1]
     <LoadNumberString>......</LoadNumberString>     [0..1]
     <BorderCrossingIndicator>......</BorderCrossingIndicator>     [0..1]
     <PortOfEntry>......</PortOfEntry>     [0..1]
     <ETADate>......</ETADate>     [0..1]
     <CarrierID>......</CarrierID>     [0..1]
     <WarehouseID>......</WarehouseID>     [0..1]
     <OrderDate>......</OrderDate>     [0..1]
     <VehicleInvoiceVehicleLineItem>......</VehicleInvoiceVehicleLineItem>     [0..*]
     <Tax>......</Tax>     [0..*]
     <DealerAssignedNumberString>......</DealerAssignedNumberString>     [0..1]
     <StatusDate>......</StatusDate>     [0..1]
     <TargetBuildDate>......</TargetBuildDate>     [0..1]
     <RejectCode>......</RejectCode>     [0..1]
     <OptionRestrictionStatements>......</OptionRestrictionStatements>     [0..1]
     <HoldCodeIndicator>......</HoldCodeIndicator>     [0..1]
     <RejectResponsibilityCode>......</RejectResponsibilityCode>     [0..1]
     <VehicleInvoiceTypeCode>......</VehicleInvoiceTypeCode>     [0..1]
     <InvoiceDocText>......</InvoiceDocText>     [0..1]
</Invoice>