Uses the Component:VehicleInvoiceHeaderType
Vehicle Invoice Header
Table 6.2. Fields and Components
| Name | Description | Occurrence | Type | Data Type | User Notes |
|---|---|---|---|---|---|
| DocumentDateTime |
Is the date and time the document was last created. This is not the date and time that the BOD message instance was created. | 0..1 | Field | udt:DateTimeType | |
| SecondaryPassword |
Secondary password used to validate access to the dealer information | 0..1 | Field | udt:TextType | |
| SecondaryDealerNumberID |
Identifies secondary dealer number if different than primary "Dealer Number" | 0..1 | Field | udt:IdentifierType | |
| DocumentIdentificationGroup |
A group of identifications that uniquely identifies this document | 1..1 | Component | DocumentIdentificationGroupType | |
| InvoiceDate |
Date of invoice. | 0..1 | Field | udt:DateType | |
| PayTermsString |
When payment is due and/or discounts allowed. | 0..1 | Field | qdt:StringType | |
| SoldToParty |
The party to which good or services were sold. | 0..1 | Component | PartyABIEType | |
| ShipToParty |
The party receiving the goods or services. | 0..1 | Component | PartyABIEType | |
| FinanceParty |
Represents a Finance Party | 0..* | Component | PartyABIEType | |
| ManufacturerParty |
The person or organization that manufactures an item. | 0..1 | Component | PartyABIEType | |
| VehicleInvoiceDealerCode |
An unique identifier for a dealer assigned by manuafacturer | 0..1 | Field | udt:IdentifierType | |
| VehicleInvoiceStartDate |
Beginning date for a invoice search operation | 0..1 | Field | udt:DateType | |
| VehicleInvoiceEndDate |
End date for a invoice search operation | 0..1 | Field | udt:DateType | |
| BillToParty |
The party that is receiving the bill for the goods or services. | 0..1 | Component | PartyABIEType | |
| PaymentTerms |
The PaymentTerms component represents the payment due dates and payment discount information. | 0..1 | Component | PaymentTermsType | |
| IncoTerms |
The Incoterms (international Chamber of Commerce) rules have become an essential part of the daily language of trade. They have been incorporated in contracts for the sale of goods worldwide and provide rules and guidance to importers, exporters, lawyers, transporters, insurers and students of international trade. | 0..1 | Component | IncoTermsType | |
| DocumentReferenceIdentificationGroup |
A group of identifications that uniquely identifies this document | 0..1 | Component | DocumentReferenceIdentificationGroupType | |
| Price |
Price information | 0..* | Component | PriceABIEType |
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.2. VehicleInvoiceHeader
<VehicleInvoiceHeader>
<DocumentDateTime>......</DocumentDateTime> [0..1]
<SecondaryPassword>......</SecondaryPassword> [0..1]
<SecondaryDealerNumberID>......</SecondaryDealerNumberID> [0..1]
<DocumentIdentificationGroup>......</DocumentIdentificationGroup> [1..1]
<InvoiceDate>......</InvoiceDate> [0..1]
<PayTermsString>......</PayTermsString> [0..1]
<SoldToParty>......</SoldToParty> [0..1]
<ShipToParty>......</ShipToParty> [0..1]
<FinanceParty>......</FinanceParty> [0..*]
<ManufacturerParty>......</ManufacturerParty> [0..1]
<VehicleInvoiceDealerCode>......</VehicleInvoiceDealerCode> [0..1]
<VehicleInvoiceStartDate>......</VehicleInvoiceStartDate> [0..1]
<VehicleInvoiceEndDate>......</VehicleInvoiceEndDate> [0..1]
<BillToParty>......</BillToParty> [0..1]
<PaymentTerms>......</PaymentTerms> [0..1]
<IncoTerms>......</IncoTerms> [0..1]
<DocumentReferenceIdentificationGroup>......</DocumentReferenceIdentificationGroup> [0..1]
<Price>......</Price> [0..*]
</VehicleInvoiceHeader>