| java.lang.Object | |||
| ↳ | org.mule.modules.quickbooks.windows.schema.CdmObject | ||
| ↳ | org.mule.modules.quickbooks.windows.schema.CdmBase | ||
| ↳ | org.mule.modules.quickbooks.windows.schema.Invoice | ||
Product: QBO Description: Financial transaction representing a request for payment for goods or services that have been sold. The Invoice entity represents an invoice to a customer. Invoice could be based on salesterm with invoice and due dates for payment. Invoice supports tax, but as of now shipping charges are not supported. Invoice can be printed and emailed to a customer.[br/] [br/] [br/] An invoice for QuickBooks must contain a valid customer reference in the CustomerId field and at least one line item. The referenced customer must already exist in the QuickBooks company at the desktop and any line items must also already exists in the QuickBooks company, or the attempt to sync will fail.[br/] [br/] In general, it is a good practice to specify all the QuickBooks header fields if you have the data. You should always specify the ARAccountId; otherwise a default AR account will be used and this may give you unexpected results.[/br] [br/] If you want to apply one tax to all the transaction line items, use the TaxId or TaxGroupId field. If you want to use more than one tax, you need to use Tax Line items instead.[/br] [br/] EndPoint: qbo.intuit.com Business Rules: [li] An invoice must have at least one line that describes the item. [/li][li] If an account is specified in the header, the account must be of the Accounts Receivable (AR) type. [/li][li] An invoice must have a reference to a customer in the header.[/li] Product: QBW Description: Financial transaction representing a request for payment for goods or services that have been sold.An invoice is a form that records the details of a customer's purchase, such as quantity and price of the goods or services. An invoice records the amount owed by a customer who does not pay in full at the time of purchase. If full payment is received at the time of purchase, the sale may be recorded as a sales receipt, not an invoice. See SalesReceipt. Note: You can now make Payments for Invoices that you created in the IDS cloud and simultaneously synchronize them back to QuickBooks. [br/] An invoice for QuickBooks must contain a valid customer reference in the CustomerId field and at least one line item. The referenced customer must already exist in the QuickBooks company at the desktop and any line items must also already exists in the QuickBooks company, or the attempt to sync will fail.[br/] [br/] In general, it is a good practice to specify all the QuickBooks header fields if you have the data. You should always specify the ARAccountId; otherwise a default AR account will be used and this may give you unexpected results.[/br] [br/] If you want to apply one tax to all the transaction line items, use the TaxId or TaxGroupId field. If you want to use more than one tax, you need to use Tax Line items instead.[/br] [br/] EndPoint: services.intuit.com Business Rules: [li] An invoice must have at least one line that describes the item. [/li][li] If an account is specified in the header, the account must be of the Accounts Receivable (AR) type. [/li][li] An invoice must have a reference to a customer in the header.[/li]
Java class for Invoice complex type.
The following schema fragment specifies the expected content contained within this class.
<complexType name="Invoice">
<complexContent>
<extension base="{http://www.intuit.com/sb/cdm/v2}CdmBase">
<sequence>
<element name="Header" type="{http://www.intuit.com/sb/cdm/v2}InvoiceHeader" minOccurs="0"/>
<element name="Line" type="{http://www.intuit.com/sb/cdm/v2}InvoiceLine" maxOccurs="unbounded" minOccurs="0"/>
<element name="TaxLine" type="{http://www.intuit.com/sb/cdm/v2}TaxLine" maxOccurs="unbounded" minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
| Fields | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| header | |||||||||||
| line | |||||||||||
| taxLine | |||||||||||
|
[Expand]
Inherited Fields | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.mule.modules.quickbooks.windows.schema.CdmBase
| |||||||||||
| Public Constructors | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Public Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Gets the value of the header property.
| |||||||||||
Gets the value of the line property.
| |||||||||||
Gets the value of the taxLine property.
| |||||||||||
Sets the value of the header property.
| |||||||||||
|
[Expand]
Inherited Methods | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
From class
org.mule.modules.quickbooks.windows.schema.CdmBase
| |||||||||||
From class
java.lang.Object
| |||||||||||
Gets the value of the header property.
InvoiceHeader
Gets the value of the line property.
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set method for the line property.
For example, to add a new item, do as follows:
getLine().add(newItem);
Objects of the following type(s) are allowed in the list
InvoiceLine
Gets the value of the taxLine property.
This accessor method returns a reference to the live list,
not a snapshot. Therefore any modification you make to the
returned list will be present inside the JAXB object.
This is why there is not a set method for the taxLine property.
For example, to add a new item, do as follows:
getTaxLine().add(newItem);
Objects of the following type(s) are allowed in the list
TaxLine
Sets the value of the header property.
| value | Allowed object is
InvoiceHeader
|
|---|