conductor-node 9.7.0 → 9.8.0

package/dist/src/integrations/qbd/qbdTypes.d.ts

@@ -2846,6 +2846,25 @@ export interface CreditMemoRet {
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
     DataExtRet?: DataExtRet | DataExtRet[];
 }
+export interface CurrencyAdd {
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** For built-in currencies, the currency code and name is the generally accepted code and name. These are based on the standard ISO 4217 code/name for a country’s currency. In most cases, the currency code is composed of the country’s two-character Internet country code plus an extra character representing the currency unit. (Hence the code for Belize Dollars is simply Belize’ two-character Internet code (“BZ”) plus a one-character currency designator (“D”). For user defined currencies, if possible, this nomenclature could be followed but it is not required. */
+    CurrencyCode: string;
+    /** The aggregate controlling the appearance of the currency with regard to comma and decimal. */
+    CurrencyFormat?: CurrencyFormat;
+}
+export interface CurrencyAddRq {
+    CurrencyAdd: CurrencyAdd;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface CurrencyAddRs {
+    CurrencyRet?: CurrencyRet;
+    ErrorRecovery?: ErrorRecovery;
+}
 export interface CurrencyFilter {
     /** One or more `ListID` values. Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`.
   
@@ -2854,12 +2873,92 @@ export interface CurrencyFilter {
     /** A list of one or more `FullName` values. `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
     FullName?: string[] | string;
 }
+export interface CurrencyFormat {
+    /** This enumerated value controls how the thousandth’s place is separated from the next thousand, for example, 1,000,000. The default is Comma, as shown, but you can replace this with one of these values: Period, Space, Apostrophe . */
+    ThousandSeparator?: ThousandSeparator;
+    /** This enumerated value controls how the display of the currency value is grouped, for example, 10,000,000. The default is `XX_XXX_XXX` but you could replace this with `X_XX_XX_XXX` */
+    ThousandSeparatorGrouping?: ThousandSeparatorGrouping;
+    /** This enumerated value controls the display of the decimal value, for example, 1.00. The default is 2 which means 2 decimals are displayed to the right of the decimal point, but you can specify 0 (zero) if you don’t want’ decimals to be displayed. */
+    DecimalPlaces?: DecimalPlaces;
+    /** This enumerated value controls the display of the decimal point, for example, 1.00 or 1,00. The default is Period but you could alternatively specify a value of Comma. */
+    DecimalSeparator?: DecimalSeparator;
+}
+export interface CurrencyMod {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name?: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** For built-in currencies, the currency code and name is the generally accepted code and name. These are based on the standard ISO 4217 code/name for a country’s currency. In most cases, the currency code is composed of the country’s two-character Internet country code plus an extra character representing the currency unit. (Hence the code for Belize Dollars is simply Belize’ two-character Internet code (“BZ”) plus a one-character currency designator (“D”). For user defined currencies, if possible, this nomenclature could be followed but it is not required. */
+    CurrencyCode?: string;
+    /** The aggregate controlling the appearance of the currency with regard to comma and decimal. */
+    CurrencyFormat?: CurrencyFormat;
+}
+export interface CurrencyModRq {
+    CurrencyMod: CurrencyMod;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface CurrencyModRs {
+    CurrencyRet?: CurrencyRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface CurrencyQueryRq {
+    /** One or more `ListID` values. Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string[] | string;
+    /** A list of one or more `FullName` values. `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName?: string[] | string;
+    /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
+    MaxReturned?: number;
+    /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
+    ActiveStatus?: ActiveStatus;
+    /** Selects objects modified on or after this date. See the note below regarding QBFC usage.For desktop versions of QuickBooks, the `FromModifiedDate` and `ToModifiedDate` must be between 1970-01-01 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (The time portion of the field was not supported in qbXML version 1.0 or 1.1.) Also, for desktop versions of QuickBooks, if `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1970-01-01T00:00:00 (1969-12-31T16:00:00-08:00 PST).For QBOE, the `FromModifiedDate` and `ToModifiedDate` must be between 1900-01-01T00:00:00 and 9999-12-31T00:00:00. If `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1900-01-01T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    FromModifiedDate?: string;
+    /** Selects objects modified on or before this date. See the note below on QBFC usage.For desktop versions of QuickBooks, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1970 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (Note that the time portion of the field was not supported in qbXML version 1.0 or 1.1.) If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST).For QBOE, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1900 and 9999-12-31T00:00:00. If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 9999-12-31T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    ToModifiedDate?: string;
+    /** Filters according to the object’s `Name`. */
+    NameFilter?: NameFilter;
+    /** Filters according to the object’s `Name`. */
+    NameRangeFilter?: NameRangeFilter;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface CurrencyQueryRs {
+    CurrencyRet: CurrencyRet[];
+}
 export interface CurrencyRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
     ListID?: string;
     /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
     FullName?: string;
 }
+export interface CurrencyRet {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string;
+    /** Time the object was created. */
+    TimeCreated?: string;
+    /** Time the object was last modified. */
+    TimeModified?: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence?: string;
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name?: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** For built-in currencies, the currency code and name is the generally accepted code and name. These are based on the standard ISO 4217 code/name for a country’s currency. In most cases, the currency code is composed of the country’s two-character Internet country code plus an extra character representing the currency unit. (Hence the code for Belize Dollars is simply Belize’ two-character Internet code (“BZ”) plus a one-character currency designator (“D”). For user defined currencies, if possible, this nomenclature could be followed but it is not required. */
+    CurrencyCode?: string;
+    /** The aggregate controlling the appearance of the currency with regard to comma and decimal. */
+    CurrencyFormat?: CurrencyFormat;
+    /** Indicates whether the currency is a built-in currency (value here would be false) or a currency created by a QuickBooks user (value here would be true). */
+    IsUserDefinedCurrency?: boolean;
+    /** The exchange rate is the market price for which this currency can be exchanged for the currency used by the QuickBooks company file as the “home” currency. The exchange rate should be considered a snapshot of the rates in effect at the `AsOfDate`. You can update the exchange rate using the exchange rate property when you add a transaction. However, you need to obtain and supply the exchange rate. If you are using USD (United States Dollars) as the home currency and are connected to the Internet, you can download the current exchange rates for all active currencies automatically in the QuickBooks UI by selecting Lists->Currency->Activities->Download latest exchange rates. (Currently, you can’t do this in the SDK.) */
+    ExchangeRate?: number;
+    /** The date when the exchange rate was last changed. */
+    AsOfDate?: string;
+}
 export interface CustomDetailReportQueryRq {
     /** The type of report being queried. */
     CustomDetailReportType: CustomDetailReportType;
@@ -2973,7 +3072,7 @@ export interface CustomerAdd {
     PreferredPaymentMethodRef?: PreferredPaymentMethodRef;
     /** Customer’s credit-card information. */
     CreditCardInfo?: CreditCardInfo;
-    /** `JobStatus` Status information about a sub-customer; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
+    /** `JobStatus` `Status` information about a sub-customer; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
     JobStatus?: JobStatus;
     /** The date on which work for a sub-customer was started; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
     JobStartDate?: string;
@@ -3080,7 +3179,7 @@ export interface CustomerMod {
     PreferredPaymentMethodRef?: PreferredPaymentMethodRef;
     /** Customer’s credit-card information. */
     CreditCardInfo?: CreditCardInfo;
-    /** `JobStatus` Status information about a sub-customer; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
+    /** `JobStatus` `Status` information about a sub-customer; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
     JobStatus?: JobStatus;
     /** The date on which work for a sub-customer was started; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
     JobStartDate?: string;
@@ -3244,7 +3343,7 @@ export interface CustomerRet {
     PreferredPaymentMethodRef?: PreferredPaymentMethodRef;
     /** Customer’s credit-card information. */
     CreditCardInfo?: CreditCardInfo;
-    /** `JobStatus` Status information about a sub-customer; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
+    /** `JobStatus` `Status` information about a sub-customer; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
     JobStatus?: JobStatus;
     /** The date on which work for a sub-customer was started; used in reports. The Job- elements (`JobDesc`, `JobEndDate`, `JobProjectedEndDate`, `JobStartDate`, and `JobStatus`) correspond to the fields in the Job Info tab of the Edit Job window in QuickBooks. */
     JobStartDate?: string;
@@ -3426,6 +3525,10 @@ export interface DataRow {
 }
 export type DataType = "AMTTYPE" | "BOOLTYPE" | "DATETIMETYPE" | "DATETYPE" | "ENUMTYPE" | "GUIDTYPE" | "IDTYPE" | "INTTYPE" | "PERCENTTYPE" | "PRICETYPE" | "QUANTYPE" | "STRTYPE" | "TIMEINTERVALTYPE";
 export type DateMacro = "All" | "LastCalendarQuarter" | "LastCalendarQuarterToDate" | "LastCalendarYear" | "LastCalendarYearToDate" | "LastFiscalQuarter" | "LastFiscalQuarterToDate" | "LastFiscalYear" | "LastFiscalYearToDate" | "LastMonth" | "LastMonthToDate" | "LastWeek" | "LastWeekToDate" | "NextCalendarQuarter" | "NextCalendarYear" | "NextFiscalQuarter" | "NextFiscalYear" | "NextFourWeeks" | "NextMonth" | "NextWeek" | "ThisCalendarQuarter" | "ThisCalendarQuarterToDate" | "ThisCalendarYear" | "ThisCalendarYearToDate" | "ThisFiscalQuarter" | "ThisFiscalQuarterToDate" | "ThisFiscalYear" | "ThisFiscalYearToDate" | "ThisMonth" | "ThisMonthToDate" | "ThisWeek" | "ThisWeekToDate" | "Today" | "Yesterday";
+/** @default: 2 */
+export type DecimalPlaces = "0" | "2";
+/** @default: Period */
+export type DecimalSeparator = "Comma" | "Period";
 export interface DepositAdd {
     /** The date of the transaction. In some cases, if you leave `TxnDate` out of an -Add message, QuickBooks will prefill `TxnDate` with the date of the last-saved transaction of the same type. */
     TxnDate?: string;
@@ -8328,6 +8431,169 @@ export interface JournalLineMod {
 }
 export type JournalLineType = "Credit" | "Debit";
 export type KeyEmployee = "No" | "Yes";
+export interface LeadAdd {
+    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName: string;
+    /** The status of the lead. */
+    Status?: Status;
+    /** The name of the QuickBooks user’s business, as specified in QuickBooks. `CompanyName` and `Address` are used on invoices, checks, and other forms. (`LegalCompanyName` and `LegalAddress`, on the other hand, are used on a company’s tax forms and pay stubs.) */
+    CompanyName?: string;
+    /** The main phone number. */
+    MainPhone?: string;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** List of locations. */
+    Locations?: Locations | Locations[];
+    /** List of lead contacts. */
+    LeadContacts?: LeadContacts | LeadContacts[];
+}
+export interface LeadAddress {
+    /** The first line of an address. */
+    Addr1?: string;
+    /** The second line of an address (if a second line is needed). */
+    Addr2?: string;
+    /** The third line of an address (if a third line is needed). */
+    Addr3?: string;
+    /** The fourth line of an address (if a fourth line is needed). */
+    Addr4?: string;
+    /** The fifth line of an address (if a fifth line is needed). */
+    Addr5?: string;
+}
+export interface LeadAddRq {
+    LeadAdd: LeadAdd;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface LeadAddRs {
+    LeadRet?: LeadRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface LeadContacts {
+    /** A formal reference, such as Mr. or Dr., that precedes a name. */
+    Salutation?: string;
+    /** The first name of a customer, vendor, employee, or person on the “other names” list. */
+    FirstName: string;
+    /** The middle name of a customer, vendor, employee, or person on the “other names” list. */
+    MiddleName?: string;
+    /** The last name of a customer, vendor, employee, or person on the “other names” list. */
+    LastName?: string;
+    /** The job title of a customer, vendor, employee, or person on the “other names” list. */
+    JobTitle?: string;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** Flag for if this is a primary contact on a lead. */
+    IsPrimaryContact?: boolean;
+}
+export interface LeadContactsMod {
+    /** `LeadContactID` is a way to identify a lead contact object. When a lead contact object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `LeadContactID`. */
+    LeadContactID: number;
+    /** A formal reference, such as Mr. or Dr., that precedes a name. */
+    Salutation?: string;
+    /** The first name of a customer, vendor, employee, or person on the “other names” list. */
+    FirstName: string;
+    /** The middle name of a customer, vendor, employee, or person on the “other names” list. */
+    MiddleName?: string;
+    /** The last name of a customer, vendor, employee, or person on the “other names” list. */
+    LastName?: string;
+    /** The job title of a customer, vendor, employee, or person on the “other names” list. */
+    JobTitle?: string;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** Flag for if this is a primary contact on a lead. */
+    IsPrimaryContact?: boolean;
+}
+export interface LeadContactsRet {
+    /** `LeadContactID` is a way to identify a lead contact object. When a lead contact object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `LeadContactID`. */
+    LeadContactID: number;
+    /** A formal reference, such as Mr. or Dr., that precedes a name. */
+    Salutation?: string;
+    /** The first name of a customer, vendor, employee, or person on the “other names” list. */
+    FirstName: string;
+    /** The middle name of a customer, vendor, employee, or person on the “other names” list. */
+    MiddleName?: string;
+    /** The last name of a customer, vendor, employee, or person on the “other names” list. */
+    LastName?: string;
+    /** The job title of a customer, vendor, employee, or person on the “other names” list. */
+    JobTitle?: string;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** Flag for if this is a primary contact on a lead. */
+    IsPrimaryContact?: boolean;
+}
+export interface LeadMod {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName: string;
+    /** The status of the lead. */
+    Status?: Status;
+    /** The name of the QuickBooks user’s business, as specified in QuickBooks. `CompanyName` and `Address` are used on invoices, checks, and other forms. (`LegalCompanyName` and `LegalAddress`, on the other hand, are used on a company’s tax forms and pay stubs.) */
+    CompanyName?: string;
+    /** The main phone number. */
+    MainPhone?: string;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** List of modified locations. */
+    LocationsMod?: LocationsMod | LocationsMod[];
+    /** List of modified lead contacts. */
+    LeadContactsMod?: LeadContactsMod | LeadContactsMod[];
+}
+export interface LeadModRq {
+    LeadMod: LeadMod;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface LeadModRs {
+    LeadRet?: LeadRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface LeadQueryRq {
+    /** One or more `ListID` values. Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string[] | string;
+    /** List of names. */
+    Name?: string[] | string;
+    /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
+    MaxReturned?: number;
+    /** Selects objects modified on or after this date. See the note below regarding QBFC usage.For desktop versions of QuickBooks, the `FromModifiedDate` and `ToModifiedDate` must be between 1970-01-01 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (The time portion of the field was not supported in qbXML version 1.0 or 1.1.) Also, for desktop versions of QuickBooks, if `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1970-01-01T00:00:00 (1969-12-31T16:00:00-08:00 PST).For QBOE, the `FromModifiedDate` and `ToModifiedDate` must be between 1900-01-01T00:00:00 and 9999-12-31T00:00:00. If `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1900-01-01T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    FromModifiedDate?: string;
+    /** Selects objects modified on or before this date. See the note below on QBFC usage.For desktop versions of QuickBooks, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1970 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (Note that the time portion of the field was not supported in qbXML version 1.0 or 1.1.) If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST).For QBOE, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1900 and 9999-12-31T00:00:00. If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 9999-12-31T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    ToModifiedDate?: string;
+    /** Filters according to the object’s `Name`. */
+    NameFilter?: NameFilter;
+    /** Filters according to the object’s `Name`. */
+    NameRangeFilter?: NameRangeFilter;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface LeadQueryRs {
+    LeadRet: LeadRet[];
+}
+export interface LeadRet {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID: string;
+    /** Time the object was created. */
+    TimeCreated: string;
+    /** Time the object was last modified. */
+    TimeModified: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName: string;
+    /** The status of the lead. */
+    Status?: Status;
+    /** The name of the QuickBooks user’s business, as specified in QuickBooks. `CompanyName` and `Address` are used on invoices, checks, and other forms. (`LegalCompanyName` and `LegalAddress`, on the other hand, are used on a company’s tax forms and pay stubs.) */
+    CompanyName?: string;
+    /** The main phone number. */
+    MainPhone?: string;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** List of returned locations. */
+    LocationsRet?: LocationsRet | LocationsRet[];
+    /** List of returned lead contacts. */
+    LeadContactsRet?: LeadContactsRet | LeadContactsRet[];
+}
 export interface LegalAddress {
     /** The first line of an address. */
     Addr1?: string;
@@ -8387,6 +8653,30 @@ export interface LinkToTxn {
     TxnLineID: string;
 }
 export type LinkType = "AMTTYPE" | "QUANTYPE";
+export interface Locations {
+    /** Where the asset is located or has been placed into service. */
+    Location: string;
+    /** Address for the lead. */
+    LeadAddress?: LeadAddress;
+}
+export interface LocationsMod {
+    /** `LocationID` is a way to identify a location object. When a location object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `LocationID`. */
+    LocationID: number;
+    /** Where the asset is located or has been placed into service. */
+    Location: string;
+    /** Address for the lead. */
+    LeadAddress?: LeadAddress;
+}
+export interface LocationsRet {
+    /** `LocationID` is a way to identify a location object. When a location object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `LocationID`. */
+    LocationID: number;
+    /** Main address for the lead. */
+    MainAddress: string;
+    /** Where the asset is located or has been placed into service. */
+    Location: string;
+    /** Address for the lead. */
+    LeadAddress?: LeadAddress;
+}
 export interface LotNumberAdjustment {
     /** The lot number of the asset. */
     LotNumber?: string;
@@ -8432,29 +8722,228 @@ export interface NameRangeFilter {
 export type OnFile = "No" | "Yes";
 export type Operator = "Equal" | "GreaterThan" | "GreaterThanEqual" | "LessThan" | "LessThanEqual";
 export type OptionForPriceRuleConflict = "BasePrice" | "Zero";
-export interface OverrideClassRef {
-    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
-    ListID?: string;
-    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
-    FullName?: string;
+export interface OtherNameAdd {
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** The name of the QuickBooks user’s business, as specified in QuickBooks. `CompanyName` and `Address` are used on invoices, checks, and other forms. (`LegalCompanyName` and `LegalAddress`, on the other hand, are used on a company’s tax forms and pay stubs.) */
+    CompanyName?: string;
+    /** A formal reference, such as Mr. or Dr., that precedes a name. */
+    Salutation?: string;
+    /** The first name of a customer, vendor, employee, or person on the “other names” list. */
+    FirstName?: string;
+    /** The middle name of a customer, vendor, employee, or person on the “other names” list. */
+    MiddleName?: string;
+    /** The last name of a customer, vendor, employee, or person on the “other names” list. */
+    LastName?: string;
+    /** If an address request fails, some combination of address fields might be too long. */
+    OtherNameAddress?: OtherNameAddress;
+    /** The telephone number. */
+    Phone?: string;
+    /** A telephone number given as an alternative to `Phone`. */
+    AltPhone?: string;
+    /** Fax number. */
+    Fax?: string;
+    /** E-mail address. */
+    Email?: string;
+    /** The name of a contact person for a customer or vendor. */
+    Contact?: string;
+    /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
+    AltContact?: string;
+    /** Account numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs. If the `IsUsingAccountNumber` preference is false (that is, if the QuickBooks user has the account numbers Preference turned off), you can still set account numbers through the SDK, but the numbers will not be visible in the user interface. */
+    AccountNumber?: string;
+    /** Additional information. */
+    Notes?: string;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
 }
-export interface OverrideItemAccountRef {
-    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
-    ListID?: string;
-    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
-    FullName?: string;
+export interface OtherNameAddress {
+    /** The first line of an address. */
+    Addr1?: string;
+    /** The second line of an address (if a second line is needed). */
+    Addr2?: string;
+    /** The third line of an address (if a third line is needed). */
+    Addr3?: string;
+    /** The fourth line of an address (if a fourth line is needed). */
+    Addr4?: string;
+    /** The fifth line of an address (if a fifth line is needed). */
+    Addr5?: string;
+    /** The city name in an address. */
+    City?: string;
+    /** The state name in an address. */
+    State?: string;
+    /** The postal code in an address. */
+    PostalCode?: string;
+    /** The country name in an address, or, in returned Host information (`HostRet` or `HostInfo`), the country for which this edition of QuickBooks was designed. (Possible values are US, CA, UK, and AU.) */
+    Country?: string;
+    /** In a `BillAddress` or `ShipAddress` aggregate, the `Note` field value is written at the bottom of the address in the form in which it appears, such as the invoice form. */
+    Note?: string;
 }
-export interface OverrideUOMSetRef {
-    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
-    ListID?: string;
-    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
-    FullName?: string;
+export interface OtherNameAddressBlock {
+    /** The first line of an address. */
+    Addr1?: string;
+    /** The second line of an address (if a second line is needed). */
+    Addr2?: string;
+    /** The third line of an address (if a third line is needed). */
+    Addr3?: string;
+    /** The fourth line of an address (if a fourth line is needed). */
+    Addr4?: string;
+    /** The fifth line of an address (if a fifth line is needed). */
+    Addr5?: string;
 }
-/** @default: All */
-export type PaidStatus = "All" | "NotPaidOnly" | "PaidOnly";
-export interface ParentRef {
-    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
-    ListID?: string;
+export interface OtherNameAddRq {
+    OtherNameAdd: OtherNameAdd;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface OtherNameAddRs {
+    OtherNameRet?: OtherNameRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface OtherNameMod {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name?: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** The name of the QuickBooks user’s business, as specified in QuickBooks. `CompanyName` and `Address` are used on invoices, checks, and other forms. (`LegalCompanyName` and `LegalAddress`, on the other hand, are used on a company’s tax forms and pay stubs.) */
+    CompanyName?: string;
+    /** A formal reference, such as Mr. or Dr., that precedes a name. */
+    Salutation?: string;
+    /** The first name of a customer, vendor, employee, or person on the “other names” list. */
+    FirstName?: string;
+    /** The middle name of a customer, vendor, employee, or person on the “other names” list. */
+    MiddleName?: string;
+    /** The last name of a customer, vendor, employee, or person on the “other names” list. */
+    LastName?: string;
+    /** If an address request fails, some combination of address fields might be too long. */
+    OtherNameAddress?: OtherNameAddress;
+    /** The telephone number. */
+    Phone?: string;
+    /** A telephone number given as an alternative to `Phone`. */
+    AltPhone?: string;
+    /** Fax number. */
+    Fax?: string;
+    /** E-mail address. */
+    Email?: string;
+    /** The name of a contact person for a customer or vendor. */
+    Contact?: string;
+    /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
+    AltContact?: string;
+    /** Account numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs. If the `IsUsingAccountNumber` preference is false (that is, if the QuickBooks user has the account numbers Preference turned off), you can still set account numbers through the SDK, but the numbers will not be visible in the user interface. */
+    AccountNumber?: string;
+    /** Additional information. */
+    Notes?: string;
+}
+export interface OtherNameModRq {
+    OtherNameMod: OtherNameMod;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface OtherNameModRs {
+    OtherNameRet?: OtherNameRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface OtherNameQueryRq {
+    /** One or more `ListID` values. Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string[] | string;
+    /** A list of one or more `FullName` values. `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName?: string[] | string;
+    /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
+    MaxReturned?: number;
+    /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
+    ActiveStatus?: ActiveStatus;
+    /** Selects objects modified on or after this date. See the note below regarding QBFC usage.For desktop versions of QuickBooks, the `FromModifiedDate` and `ToModifiedDate` must be between 1970-01-01 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (The time portion of the field was not supported in qbXML version 1.0 or 1.1.) Also, for desktop versions of QuickBooks, if `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1970-01-01T00:00:00 (1969-12-31T16:00:00-08:00 PST).For QBOE, the `FromModifiedDate` and `ToModifiedDate` must be between 1900-01-01T00:00:00 and 9999-12-31T00:00:00. If `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1900-01-01T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    FromModifiedDate?: string;
+    /** Selects objects modified on or before this date. See the note below on QBFC usage.For desktop versions of QuickBooks, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1970 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (Note that the time portion of the field was not supported in qbXML version 1.0 or 1.1.) If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST).For QBOE, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1900 and 9999-12-31T00:00:00. If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 9999-12-31T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    ToModifiedDate?: string;
+    /** Filters according to the object’s `Name`. */
+    NameFilter?: NameFilter;
+    /** Filters according to the object’s `Name`. */
+    NameRangeFilter?: NameRangeFilter;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+    /** Zero or more `OwnerID` values. `OwnerID` refers to the owner of a data extension:If `OwnerID` is 0, this is a public data extension, also known as a custom field. Custom fields appear in the QuickBooks UI.If `OwnerID` is a GUID, for example `{6B063959-81B0-4622-85D6-F548C8CCB517}`, this field is a private data extension defined by an integrated application. Private data extensions do not appear in the QuickBooks UI. Note that `OwnerID` values are not case-sensitive, meaning that if you enter an `OwnerID` value with lower-case letters, the value will be saved and returned with upper-case letters. When you share a private data extension with another application, the other application must know both the `OwnerID` and the `DataExtName`, as these together form a data extension’s unique name. */
+    OwnerID?: string[] | string;
+}
+export interface OtherNameQueryRs {
+    OtherNameRet: OtherNameRet[];
+}
+export interface OtherNameRet {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID: string;
+    /** Time the object was created. */
+    TimeCreated: string;
+    /** Time the object was last modified. */
+    TimeModified: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** The name of the QuickBooks user’s business, as specified in QuickBooks. `CompanyName` and `Address` are used on invoices, checks, and other forms. (`LegalCompanyName` and `LegalAddress`, on the other hand, are used on a company’s tax forms and pay stubs.) */
+    CompanyName?: string;
+    /** A formal reference, such as Mr. or Dr., that precedes a name. */
+    Salutation?: string;
+    /** The first name of a customer, vendor, employee, or person on the “other names” list. */
+    FirstName?: string;
+    /** The middle name of a customer, vendor, employee, or person on the “other names” list. */
+    MiddleName?: string;
+    /** The last name of a customer, vendor, employee, or person on the “other names” list. */
+    LastName?: string;
+    /** If an address request fails, some combination of address fields might be too long. */
+    OtherNameAddress?: OtherNameAddress;
+    /** The address expressed as an address block of `Addr1` through `Addr5`, depending on the number of lines in the original request that created the address. */
+    OtherNameAddressBlock?: OtherNameAddressBlock;
+    /** The telephone number. */
+    Phone?: string;
+    /** A telephone number given as an alternative to `Phone`. */
+    AltPhone?: string;
+    /** Fax number. */
+    Fax?: string;
+    /** E-mail address. */
+    Email?: string;
+    /** The name of a contact person for a customer or vendor. */
+    Contact?: string;
+    /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
+    AltContact?: string;
+    /** Account numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs. If the `IsUsingAccountNumber` preference is false (that is, if the QuickBooks user has the account numbers Preference turned off), you can still set account numbers through the SDK, but the numbers will not be visible in the user interface. */
+    AccountNumber?: string;
+    /** Additional information. */
+    Notes?: string;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
+    DataExtRet?: DataExtRet | DataExtRet[];
+}
+export interface OverrideClassRef {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string;
+    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName?: string;
+}
+export interface OverrideItemAccountRef {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string;
+    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName?: string;
+}
+export interface OverrideUOMSetRef {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string;
+    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName?: string;
+}
+/** @default: All */
+export type PaidStatus = "All" | "NotPaidOnly" | "PaidOnly";
+export interface ParentRef {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string;
     /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
     FullName?: string;
 }
@@ -10615,6 +11104,193 @@ export interface SalesTaxCodeRet {
 }
 /** @default: Canada */
 export type SalesTaxCountry = "Australia" | "Canada" | "UK" | "US";
+export interface SalesTaxPaymentCheckAdd {
+    /** Refers to a payee who is a customer, vendor, employee, or person on the “other names” list. In a request, if a `PayeeEntityRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    In a Check message, `PayeeEntityRef` refers to the person or company to whom the check is written.
+  
+    In `CreditCardCharge` and `CreditCardCredit` messages, `PayeeEntityRef` refers to the vendor or company from whom merchandise was purchased. (`PayeeEntityRef` corresponds to the choice in the Purchased From list in QuickBooks.) */
+    PayeeEntityRef: PayeeEntityRef;
+    /** The date of the transaction. In some cases, if you leave `TxnDate` out of an -Add message, QuickBooks will prefill `TxnDate` with the date of the last-saved transaction of the same type. */
+    TxnDate: string;
+    /** Refers to the account from which the funds are being drawn for this check, for example, Checking or Savings. If a `BankAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    BankAccountRef: BankAccountRef;
+    /** If `IsToBePrinted` is set to true, this transaction is on a list of forms to be printed later. The user can then choose to print all these forms at once.
+  
+    Notice that setting this field to true does not actually perform the printing. Only the QuickBooks user can do that from within QuickBooks. This cannot be done from the SDK. Setting this field to false does not prevent the QuickBooks user from printing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be printed. */
+    IsToBePrinted?: boolean;
+    /** A string of characters that refers to this transaction and that can be arbitrarily changed by the QuickBooks user.
+  
+    In a `BillPaymentCheckAdd` request, if you want to set the check number, use `RefNumber`.
+  
+    Note (especially relevant to `CheckAdd` requests): When `RefNumber` is left blank in an SDK transaction add request (that is, or ), the `RefNumber` will be left blank in QuickBooks. This behavior is new as of QBFC3. It used to select the next sequential reference number since the last one used by QuickBooks, as though no `RefNumber` had been provided. This is especially relevant to `CheckAdd` requests because with the current behavior, you will not know the number until the check is printed. */
+    RefNumber?: string;
+    /** Additional information. */
+    Memo?: string;
+    /** If an address request fails, some combination of address fields might be too long. In a Check, `BillPaymentCheck`, or `SalesTaxPaymentCheck` message, `Address` is the address that will print on the check. */
+    Address?: Address;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** A list of `ISalesTaxPaymentCheckLineRet` objects, each representing one line in the sales-tax payment check. */
+    SalesTaxPaymentCheckLineAdd: SalesTaxPaymentCheckLineAdd | SalesTaxPaymentCheckLineAdd[];
+}
+export interface SalesTaxPaymentCheckAddRq {
+    SalesTaxPaymentCheckAdd: SalesTaxPaymentCheckAdd;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address.
+  
+    The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name.
+  
+    Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface SalesTaxPaymentCheckAddRs {
+    SalesTaxPaymentCheckRet?: SalesTaxPaymentCheckRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface SalesTaxPaymentCheckLineAdd {
+    /** A sales-tax item is used to calculate a single sales tax that is collected at a specified rate and paid to a single agency. (Compare with the `ItemSalesTaxGroupAdd` message.) An `ItemSalesTaxRef` aggregate refers to an item on this list. In a request, if an `ItemSalesTaxRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    Taxes can be reflected in transaction line items
+  
+    The following information refers to invoices specifically, but it also applies to sales receipts. Generally its best to assign a tax item or tax group item to an invoice and allow QuickBooks to apply the same tax to all taxable items on the invoice. However in some situations multiple tax combinations are required, so this method doesn’t work. In this case one must use techniques to apply the taxes in the invoice itself as line items. Using lines to apply taxes isn’t always straight forward.
+  
+    When applying taxes as line items, only single tax items can be used, tax groups can only be used for the entire invoice. If you have multiple taxes which apply to all taxable items, and one or more other taxes that only apply to some of the items on an invoice its better to use a tax group which applies to the entire invoice for the taxes which applies to all taxable items and then apply the other taxes in the invoice itself. One applies a tax or tax group to an entire invoice by using the `ItemSalesTaxRef` aggregate.
+  
+    One can use subtotals to apply a single tax line to multiple items in an invoice, but the tax is only applied automatically for the first tax line after the subtotal line. Any other tax lines which need to be applied to the subtotal line must supply their own amount. If you don’t supply an amount the amount comes out as zero and the tax line is useless. When one does supply an amount, the amount of tax on the subtotal also shows up in the rate column for that tax line. There isn’t any way for the rate to show up as anything other than the amount of the tax.
+  
+    If you have a complicated tax situation where no single tax applies to all taxable items on the invoice, you must choose a zero percent tax to apply for the entire invoice. It is recommended to name such a tax item “Tax Calculated On Invoice” so that it’s clear that the tax is not being applied by QuickBooks on the entire invoice. */
+    ItemSalesTaxRef?: ItemSalesTaxRef;
+    /** A monetary amount. */
+    Amount: string;
+}
+export interface SalesTaxPaymentCheckLineRet {
+    /** Identification number of the transaction line. (`TxnLineID` is supported as of v2.0 of the SDK. With qbXML v1.0 and v1.1, `TxnLineID` is always returned as zero.)
+  
+    If you need to add a new transaction line in a transaction Mod request, you can do so by setting the `TxnLineID` to -1. */
+    TxnLineID: string;
+    /** A sales-tax item is used to calculate a single sales tax that is collected at a specified rate and paid to a single agency. (Compare with the `ItemSalesTaxGroupAdd` message.) An `ItemSalesTaxRef` aggregate refers to an item on this list. In a request, if an `ItemSalesTaxRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    Taxes can be reflected in transaction line items
+  
+    The following information refers to invoices specifically, but it also applies to sales receipts. Generally its best to assign a tax item or tax group item to an invoice and allow QuickBooks to apply the same tax to all taxable items on the invoice. However in some situations multiple tax combinations are required, so this method doesn’t work. In this case one must use techniques to apply the taxes in the invoice itself as line items. Using lines to apply taxes isn’t always straight forward.
+  
+    When applying taxes as line items, only single tax items can be used, tax groups can only be used for the entire invoice. If you have multiple taxes which apply to all taxable items, and one or more other taxes that only apply to some of the items on an invoice its better to use a tax group which applies to the entire invoice for the taxes which applies to all taxable items and then apply the other taxes in the invoice itself. One applies a tax or tax group to an entire invoice by using the `ItemSalesTaxRef` aggregate.
+  
+    One can use subtotals to apply a single tax line to multiple items in an invoice, but the tax is only applied automatically for the first tax line after the subtotal line. Any other tax lines which need to be applied to the subtotal line must supply their own amount. If you don’t supply an amount the amount comes out as zero and the tax line is useless. When one does supply an amount, the amount of tax on the subtotal also shows up in the rate column for that tax line. There isn’t any way for the rate to show up as anything other than the amount of the tax.
+  
+    If you have a complicated tax situation where no single tax applies to all taxable items on the invoice, you must choose a zero percent tax to apply for the entire invoice. It is recommended to name such a tax item “Tax Calculated On Invoice” so that it’s clear that the tax is not being applied by QuickBooks on the entire invoice. */
+    ItemSalesTaxRef?: ItemSalesTaxRef;
+    /** A monetary amount. */
+    Amount?: string;
+}
+export interface SalesTaxPaymentCheckMod {
+    /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** The date of the transaction. In some cases, if you leave `TxnDate` out of an -Add message, QuickBooks will prefill `TxnDate` with the date of the last-saved transaction of the same type. */
+    TxnDate?: string;
+    /** Refers to the account from which the funds are being drawn for this check, for example, Checking or Savings. If a `BankAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    BankAccountRef?: BankAccountRef;
+    /** If `IsToBePrinted` is set to true, this transaction is on a list of forms to be printed later. The user can then choose to print all these forms at once. Notice that setting this field to true does not actually perform the printing. Only the QuickBooks user can do that from within QuickBooks. This cannot be done from the SDK. Setting this field to false does not prevent the QuickBooks user from printing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be printed. */
+    IsToBePrinted?: boolean;
+    /** A string of characters that refers to this transaction and that can be arbitrarily changed by the QuickBooks user. In a `BillPaymentCheckAdd` request, if you want to set the check number, use `RefNumber`.`Note` (especially relevant to `CheckAdd` requests): When `RefNumber` is left blank in an SDK transaction add request (that is, or ), the `RefNumber` will be left blank in QuickBooks. This behavior is new as of QBFC3. It used to select the next sequential reference number since the last one used by QuickBooks, as though no `RefNumber` had been provided. This is especially relevant to `CheckAdd` requests because with the current behavior, you will not know the number until the check is printed. */
+    RefNumber?: string;
+    /** Additional information. */
+    Memo?: string;
+    /** If an address request fails, some combination of address fields might be too long. In a Check, `BillPaymentCheck`, or `SalesTaxPaymentCheck` message, `Address` is the address that will print on the check. */
+    Address?: Address;
+}
+export interface SalesTaxPaymentCheckModRq {
+    SalesTaxPaymentCheckMod: SalesTaxPaymentCheckMod;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface SalesTaxPaymentCheckModRs {
+    SalesTaxPaymentCheckRet?: SalesTaxPaymentCheckRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface SalesTaxPaymentCheckQueryRq {
+    /** One or more `TxnID` values. QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQuery` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID?: string[] | string;
+    /** A list of one or more `RefNumber` values. A `RefNumber` is a string of characters that refers to a transaction and that can be arbitrarily changed by the QuickBooks user. Note (especially relevant to `CheckAdd` requests): When `RefNumber` is left blank in an SDK transaction add request, the `RefNumber` will be left blank in QuickBooks. This behavior is new as of QBFC3. It used to select the next sequential reference number since the last one used by QuickBooks, as though no `RefNumber` had been provided. This is especially relevant to `CheckAdd` requests because with the current behavior, you will not know the number until the check is printed. */
+    RefNumber?: string[] | string;
+    /** A list of one or more case sensitive `RefNumber` values. A `RefNumber` is a string of characters that refers to a transaction and that can be arbitrarily changed by the QuickBooks user. You should use this case sensitive ref number list rather than the older `RefNumber` list, because it provides much better performance in certain circumstances. The older `refNumber` list provided slow performance if the `refNumber` values contained letters, not just digits. This `RefNumberCaseSensitive` list, new in SDK 4.0, eliminates this performance hit. */
+    RefNumberCaseSensitive?: string[] | string;
+    /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
+    MaxReturned?: number;
+    /** Filters according to the dates when transactions were last modified. The `ModifiedDateRangeFilter` aggregate is not required to contain any elements, but if it is empty, we recommend that you leave it out altogether. Note that the time portion of the `FromModifiedDate` and `ToModifiedDate` fields was not supported in qbXML version 1.0 or 1.1. (To filter according to the dates when transactions were deleted, use a `TxnDeletedQuery` message.) */
+    ModifiedDateRangeFilter?: ModifiedDateRangeFilter;
+    /** Filters according to the original transaction dates. */
+    TxnDateRangeFilter?: TxnDateRangeFilter;
+    /** An entity refers to a person on the QuickBooks Customer list, Vendor list, Employee list, or `Other` Names list. You can use an `EntityQuery` request to get information about all the entities that are set up in the QuickBooks file. In an `ARRefundCreditCard` query, this must be a customer/customer job. */
+    EntityFilter?: EntityFilter;
+    /** Filters according to the account name or `ListID`. If the “Use account numbers” preference is enabled in the QuickBooks company file, you can specify an account number (instead of an account name) for `FullName` and get the account you’re looking for. But if numbers have been used as account names, confusion could arise. For example, if you queried for an account named 2050, and 2050 happened to be the account number of a totally different account, the query would not return what you asked for (the account named 2050), but instead would return the account with the account number 2050. This problem will not happen if the “Use account numbers” preference is turned off in the QuickBooks file, orthe account name exactly matches the account number. (In this case, query would return the correct account either way.) To avoid this problem: Do not name an account using a number unless the number exactly matches the account’s account number. If an account name must contain a number that does not match its own account number, have the QuickBooks user change the account’s name slightly, for example `to` 2050a. */
+    AccountFilter?: AccountFilter;
+    /** Filters according to the item name or ID. You can use an `ItemQuery` request to get information about all the items that are set up in the QuickBooks file. “Items” are line items used for fast entry on sales and purchase forms. They include services and goods that a business buys and sells, as well as special items that perform calculations–for example, subtotal, discount, and sales-tax items. */
+    ItemFilter?: ItemFilter;
+    /** Filters according to `RefNumber`. */
+    RefNumberFilter?: RefNumberFilter;
+    /** Filters according to `RefNumber`. The filtering code will do a numerical comparison (if `FromRefNumber` and `ToRefNumber` only contain digits) or a lexicographical comparison (if either `FromRefNumber` or `ToRefNumber` contain any nondigit characters). In the first situation, if you need to query for a `RefNumber` that is larger than the maximum long integer value of 2147483647, one workaround is to specify a `FromRefNumber` that is less than or equal to 2147483647 without specifying a `ToRefNumber`. */
+    RefNumberRangeFilter?: RefNumberRangeFilter;
+    /** This filter allows you to omit line items from a query response to get a smaller result. The default value is false, so line items are omitted by default. Set `IncludeLineItems` to true to include line items in the response if you don’t mind getting a larger result. */
+    IncludeLineItems?: boolean;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+    /** Zero or more `OwnerID` values. `OwnerID` refers to the owner of a data extension:If `OwnerID` is 0, this is a public data extension, also known as a custom field. Custom fields appear in the QuickBooks UI.If `OwnerID` is a GUID, for example `{6B063959-81B0-4622-85D6-F548C8CCB517}`, this field is a private data extension defined by an integrated application. Private data extensions do not appear in the QuickBooks UI. Note that `OwnerID` values are not case-sensitive, meaning that if you enter an `OwnerID` value with lower-case letters, the value will be saved and returned with upper-case letters. When you share a private data extension with another application, the other application must know both the `OwnerID` and the `DataExtName`, as these together form a data extension’s unique name. */
+    OwnerID?: string[] | string;
+}
+export interface SalesTaxPaymentCheckQueryRs {
+    SalesTaxPaymentCheckRet: SalesTaxPaymentCheckRet[];
+}
+export interface SalesTaxPaymentCheckRet {
+    /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests.
+  
+    Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID: string;
+    /** Time the object was created. */
+    TimeCreated: string;
+    /** Time the object was last modified. */
+    TimeModified: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** An identifying number for this transaction. */
+    TxnNumber?: number;
+    /** Refers to a payee who is a customer, vendor, employee, or person on the “other names” list. In a request, if a `PayeeEntityRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    In a Check message, `PayeeEntityRef` refers to the person or company to whom the check is written.
+  
+    In `CreditCardCharge` and `CreditCardCredit` messages, `PayeeEntityRef` refers to the vendor or company from whom merchandise was purchased. (`PayeeEntityRef` corresponds to the choice in the Purchased From list in QuickBooks.) */
+    PayeeEntityRef?: PayeeEntityRef;
+    /** The date of the transaction. In some cases, if you leave `TxnDate` out of an -Add message, QuickBooks will prefill `TxnDate` with the date of the last-saved transaction of the same type. */
+    TxnDate: string;
+    /** Refers to the account from which the funds are being drawn for this check, for example, Checking or Savings. If a `BankAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    BankAccountRef: BankAccountRef;
+    /** A monetary amount. */
+    Amount: string;
+    /** A string of characters that refers to this transaction and that can be arbitrarily changed by the QuickBooks user.
+  
+    In a `BillPaymentCheckAdd` request, if you want to set the check number, use `RefNumber`.
+  
+    Note (especially relevant to `CheckAdd` requests): When `RefNumber` is left blank in an SDK transaction add request (that is, or ), the `RefNumber` will be left blank in QuickBooks. This behavior is new as of QBFC3. It used to select the next sequential reference number since the last one used by QuickBooks, as though no `RefNumber` had been provided. This is especially relevant to `CheckAdd` requests because with the current behavior, you will not know the number until the check is printed. */
+    RefNumber?: string;
+    /** Additional information. */
+    Memo?: string;
+    /** If an address request fails, some combination of address fields might be too long. In a Check, `BillPaymentCheck`, or `SalesTaxPaymentCheck` message, `Address` is the address that will print on the check. */
+    Address?: Address;
+    /** The address expressed as an address block of `Addr1` through `Addr5`, depending on the number of lines in the original request that created the address. */
+    AddressBlock?: AddressBlock;
+    /** If `IsToBePrinted` is set to true, this transaction is on a list of forms to be printed later. The user can then choose to print all these forms at once.
+  
+    Notice that setting this field to true does not actually perform the printing. Only the QuickBooks user can do that from within QuickBooks. This cannot be done from the SDK. Setting this field to false does not prevent the QuickBooks user from printing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be printed. */
+    IsToBePrinted?: boolean;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** A list of `ISalesTaxPaymentCheckLineRet` objects, each representing one line in the sales-tax payment check. */
+    SalesTaxPaymentCheckLineRet?: SalesTaxPaymentCheckLineRet | SalesTaxPaymentCheckLineRet[];
+    /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
+    DataExtRet?: DataExtRet | DataExtRet[];
+}
 export interface SalesTaxReturnLineRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
     ListID?: string;
@@ -10792,6 +11468,8 @@ export interface SiteFilter {
 export type SOChannel = "Blank" | "Ecommerce";
 export type SpecialAccountType = "AccountsPayable" | "AccountsReceivable" | "CondenseItemAdjustmentExpenses" | "CostOfGoodsSold" | "DirectDepositLiabilities" | "Estimates" | "ExchangeGainLoss" | "InventoryAssets" | "ItemReceiptAccount" | "OpeningBalanceEquity" | "PayrollExpenses" | "PayrollLiabilities" | "PettyCash" | "PurchaseOrders" | "ReconciliationDifferences" | "RetainedEarnings" | "SalesOrders" | "SalesTaxPayable" | "UncategorizedExpenses" | "UncategorizedIncome" | "UndepositedFunds";
 export type SpecialItemType = "FinanceCharge" | "ReimbursableExpenseGroup" | "ReimbursableExpenseSubtotal";
+/** @default: Hot */
+export type Status = "Cold" | "Hot" | "Warm";
 export interface SubscribedServices {
     /** The list of the Intuit services that the company is or has been subscribed to, for example, Intuit Payroll, QBMS. */
     Service?: Service | Service[];
@@ -10855,6 +11533,10 @@ export interface TextRow {
     /** The data in this cell of the report. */
     Value: string;
 }
+/** @default: Comma */
+export type ThousandSeparator = "Apostrophe" | "Comma" | "Period" | "Space";
+/** @default: XX_XXX_XXX */
+export type ThousandSeparatorGrouping = "X_XX_XX_XXX" | "XX_XXX_XXX";
 export interface TimeReportQueryRq {
     /** Allows you to report on time that has been recorded in a particular category. */
     TimeReportType: TimeReportType;
@@ -11351,6 +12033,177 @@ export interface ValueAdjustment {
     /** Either a positive or negative number that shows a change in the total value of the entire stock of this inventory item. */
     ValueDifference?: string;
 }
+export interface VehicleAdd {
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** A descriptive text field. */
+    Desc?: string;
+}
+export interface VehicleAddRq {
+    VehicleAdd: VehicleAdd;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface VehicleAddRs {
+    VehicleRet?: VehicleRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface VehicleMileageAdd {
+    /** A vehicle for use in `VehicleMileage` transactions. Each vehicle name must be unique. */
+    VehicleRef: VehicleRef;
+    /** The customer list includes information about the QuickBooks user’s customers and the individual jobs that are being performed for them. A `CustomerRef` aggregate refers to one of the customers (or customer jobs) on the list. In a request, if a `CustomerRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. Special cases to note:In `SalesReceipt` and `ReceivePayment` requests, `CustomerRef` refers to the customer or customer job to which the payment is credited.In a `TimeTracking` request, `CustomerRef` refers to the customer or customer job to which this time could be billed. If `IsBillable` is set to true, `CustomerRef` is required in `TimeTrackingAdd`. In an `ExpenseLineAdd` request, if `AccountRef` refers to an A/P account, `CustomerRef` must refer to a vendor (not to a customer). If `AccountRef` refers to any other type of account, the `CustomerRef` must refer to a customer. */
+    CustomerRef?: CustomerRef;
+    /** Depending on the request containing it, `ItemRef` can refer to an item on any Item list such as `ItemDiscount`, `ItemInventory`, and so forth, or it may accept only a subset of item types. For example, here are some requests that impose limits on what items `ItemRef` can refer to. For `PurchaseOrder` and Bill requests, `ItemRef` cannot refer to discount items or sales-tax `itemsFor` `VehicleMilageAdd` requests, the `ItemRef` must refer to a service item or an other charge item.For `BillingRateAdd` requests, the `ItemRef` must refer to a service item. You can use an `ItemQuery` request to get information about all the items that are set up in the QuickBooks file. “Items” are line items used for fast entry on sales and purchase forms. They include services and goods that a business buys and sells, as well as special items that perform calculations–for example, subtotal, discount, and sales-tax items. Note: In a request, if an `ItemRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ItemRef?: ItemRef;
+    /** Classes can be used to separate transactions into meaningful categories. (For example, transactions could be classified according to department, business location, or type of work.) In QuickBooks, class tracking is off by default. A `ClassRef` aggregate refers to one of these named classes. For example, in a `TimeTracking` message, `ClassRef` refers to the QuickBooks class into which the timed activity falls. If a `ClassRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In an `InvoiceAdd` request, if you specify a `ClassRef` for the whole invoice, that same `ClassRef` is automatically used in the line items. If you want to clear that (that is, have NO `ClassRef` for the line item, you can clear it in the line item by simply not specifying it in the line item. */
+    ClassRef?: ClassRef;
+    /** Date the trip began. If left blank, the current date at the time of transaction will be used. Notice that only dates are supported for vehicle mileage, so make sure you enter any datetime values with dates only, no time values. That is, 2002-02-02 will work for trip end date or start date, but 2002-02-02T12:20:20 will not work. */
+    TripStartDate?: string;
+    /** Date the trip ended. If left blank, the current date at the time of transaction will be used. Notice that only dates are supported for vehicle mileage, so make sure you enter any datetime values with dates only, no time values. That is, 2002-02-02 will work for trip end date or start date, but 2002-02-02T12:20:20 will not work. */
+    TripEndDate?: string;
+    /** Odometer reading at the start of the trip. `OdometerStart` and `OdometerEnd` must both be specified if `TotalMiles` is not specified. QuickBooks will calculate the total trip miles from these two values. If `TotalMiles` is specified, you cannot specify `OdometerStart` and `OdometerEnd`. */
+    OdometerStart: number;
+    /** Odometer reading at the end of the trip. `OdometerStart` and `OdometerEnd` must both be specified if `TotalMiles` is not specified. QuickBooks will calculate the total trip miles from these two values. If `TotalMiles` is specified, you cannot specify `OdometerStart` and `OdometerEnd`. */
+    OdometerEnd: number;
+    /** Total trip miles. If `TotalMiles` is specified, you cannot specify `OdometerStart` and `OdometerEnd`. If you use `OdometerStart` and `OdometerEnd` instead of `TotalMiles`, QuickBooks will calculate the total trip miles from these two values. */
+    TotalMiles?: number;
+    /** Additional information. */
+    Notes?: string;
+    /** The billing status of this item line or expense line. */
+    BillableStatus?: BillableStatus;
+}
+export interface VehicleMileageAddRq {
+    VehicleMileageAdd: VehicleMileageAdd;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface VehicleMileageAddRs {
+    VehicleMileageRet?: VehicleMileageRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface VehicleMileageQueryRq {
+    /** One or more `TxnID` values. QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQuery` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID?: string[] | string;
+    /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
+    MaxReturned?: number;
+    /** Filters according to the dates when transactions were last modified. The `ModifiedDateRangeFilter` aggregate is not required to contain any elements, but if it is empty, we recommend that you leave it out altogether. Note that the time portion of the `FromModifiedDate` and `ToModifiedDate` fields was not supported in qbXML version 1.0 or 1.1. (To filter according to the dates when transactions were deleted, use a `TxnDeletedQuery` message.) */
+    ModifiedDateRangeFilter?: ModifiedDateRangeFilter;
+    /** Filters according to the original transaction dates. */
+    TxnDateRangeFilter?: TxnDateRangeFilter;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface VehicleMileageQueryRs {
+    VehicleMileageRet: VehicleMileageRet[];
+}
+export interface VehicleMileageRet {
+    /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID?: string;
+    /** Time the object was created. */
+    TimeCreated?: string;
+    /** Time the object was last modified. */
+    TimeModified?: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence?: string;
+    /** A vehicle for use in `VehicleMileage` transactions. Each vehicle name must be unique. */
+    VehicleRef?: VehicleRef;
+    /** The customer list includes information about the QuickBooks user’s customers and the individual jobs that are being performed for them. A `CustomerRef` aggregate refers to one of the customers (or customer jobs) on the list. In a request, if a `CustomerRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. Special cases to note:In `SalesReceipt` and `ReceivePayment` requests, `CustomerRef` refers to the customer or customer job to which the payment is credited.In a `TimeTracking` request, `CustomerRef` refers to the customer or customer job to which this time could be billed. If `IsBillable` is set to true, `CustomerRef` is required in `TimeTrackingAdd`. In an `ExpenseLineAdd` request, if `AccountRef` refers to an A/P account, `CustomerRef` must refer to a vendor (not to a customer). If `AccountRef` refers to any other type of account, the `CustomerRef` must refer to a customer. */
+    CustomerRef?: CustomerRef;
+    /** Depending on the request containing it, `ItemRef` can refer to an item on any Item list such as `ItemDiscount`, `ItemInventory`, and so forth, or it may accept only a subset of item types. For example, here are some requests that impose limits on what items `ItemRef` can refer to. For `PurchaseOrder` and Bill requests, `ItemRef` cannot refer to discount items or sales-tax `itemsFor` `VehicleMilageAdd` requests, the `ItemRef` must refer to a service item or an other charge item.For `BillingRateAdd` requests, the `ItemRef` must refer to a service item. You can use an `ItemQuery` request to get information about all the items that are set up in the QuickBooks file. “Items” are line items used for fast entry on sales and purchase forms. They include services and goods that a business buys and sells, as well as special items that perform calculations–for example, subtotal, discount, and sales-tax items. Note: In a request, if an `ItemRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ItemRef?: ItemRef;
+    /** Classes can be used to separate transactions into meaningful categories. (For example, transactions could be classified according to department, business location, or type of work.) In QuickBooks, class tracking is off by default. A `ClassRef` aggregate refers to one of these named classes. For example, in a `TimeTracking` message, `ClassRef` refers to the QuickBooks class into which the timed activity falls. If a `ClassRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In an `InvoiceAdd` request, if you specify a `ClassRef` for the whole invoice, that same `ClassRef` is automatically used in the line items. If you want to clear that (that is, have NO `ClassRef` for the line item, you can clear it in the line item by simply not specifying it in the line item. */
+    ClassRef?: ClassRef;
+    /** Date the trip began. If left blank, the current date at the time of transaction will be used. Notice that only dates are supported for vehicle mileage, so make sure you enter any datetime values with dates only, no time values. That is, 2002-02-02 will work for trip end date or start date, but 2002-02-02T12:20:20 will not work. */
+    TripStartDate?: string;
+    /** Date the trip ended. If left blank, the current date at the time of transaction will be used. Notice that only dates are supported for vehicle mileage, so make sure you enter any datetime values with dates only, no time values. That is, 2002-02-02 will work for trip end date or start date, but 2002-02-02T12:20:20 will not work. */
+    TripEndDate?: string;
+    /** Odometer reading at the start of the trip. `OdometerStart` and `OdometerEnd` must both be specified if `TotalMiles` is not specified. QuickBooks will calculate the total trip miles from these two values. If `TotalMiles` is specified, you cannot specify `OdometerStart` and `OdometerEnd`. */
+    OdometerStart?: number;
+    /** Odometer reading at the end of the trip. `OdometerStart` and `OdometerEnd` must both be specified if `TotalMiles` is not specified. QuickBooks will calculate the total trip miles from these two values. If `TotalMiles` is specified, you cannot specify `OdometerStart` and `OdometerEnd`. */
+    OdometerEnd?: number;
+    /** Total trip miles. If `TotalMiles` is specified, you cannot specify `OdometerStart` and `OdometerEnd`. If you use `OdometerStart` and `OdometerEnd` instead of `TotalMiles`, QuickBooks will calculate the total trip miles from these two values. */
+    TotalMiles?: number;
+    /** Additional information. */
+    Notes?: string;
+    /** The billing status of this item line or expense line. */
+    BillableStatus?: BillableStatus;
+    /** The mileage rate currently allowed by the tax authority (IRS) for vehicle expenses. */
+    StandardMileageRate?: string;
+    /** Amount calculated by multiplying the total trip miles in the current vehicle mileage transaction by the standard mileage rate currently in use. */
+    StandardMileageTotalAmount?: string;
+    /** In a billable vehicle mileage transaction, refers to the rate being used to charge mileage against a customer. The rate is specified in the service item or other charge item that is referenced in the `ItemRef` field of the `VehicleMileageAdd` request. */
+    BillableRate?: string;
+    /** In a billable vehicle mileage transaction, refers to the total charge that QuickBooks calculates by multiplying the trip total mileage by the rate specified in the item referenced by the `ItemRef`. */
+    BillableAmount?: string;
+}
+export interface VehicleMod {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name?: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** A descriptive text field. */
+    Desc?: string;
+}
+export interface VehicleModRq {
+    VehicleMod: VehicleMod;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface VehicleModRs {
+    VehicleRet?: VehicleRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface VehicleQueryRq {
+    /** One or more `ListID` values. Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string[] | string;
+    /** A list of one or more `FullName` values. `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName?: string[] | string;
+    /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
+    MaxReturned?: number;
+    /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
+    ActiveStatus?: ActiveStatus;
+    /** Selects objects modified on or after this date. See the note below regarding QBFC usage.For desktop versions of QuickBooks, the `FromModifiedDate` and `ToModifiedDate` must be between 1970-01-01 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (The time portion of the field was not supported in qbXML version 1.0 or 1.1.) Also, for desktop versions of QuickBooks, if `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1970-01-01T00:00:00 (1969-12-31T16:00:00-08:00 PST).For QBOE, the `FromModifiedDate` and `ToModifiedDate` must be between 1900-01-01T00:00:00 and 9999-12-31T00:00:00. If `FromModifiedDate` includes a date but not a time (for example, if you set `FromModifiedDate` to 2003-02-14), the time is assumed to be zero (2003-02-14T00:00:00). If you omit `FromModifiedDate`, it will be set to 1900-01-01T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    FromModifiedDate?: string;
+    /** Selects objects modified on or before this date. See the note below on QBFC usage.For desktop versions of QuickBooks, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1970 and 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). (Note that the time portion of the field was not supported in qbXML version 1.0 or 1.1.) If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST).For QBOE, the `ToModifiedDate` and `FromModifiedDate` must be between 01/01/1900 and 9999-12-31T00:00:00. If `ToModifiedDate` includes a date but not a time (for example, if you set `ToModifiedDate` to 2003-02-14), the time is assumed to be the end of the day (2003-02-14T23:59:59). If you omit `ToModifiedDate` altogether, it will be set to 9999-12-31T00:00:00.`Note`: When specifying this in QBFC, you need to supply the parameter `asDateOnly`, which is a Boolean. If `asDateOnly` is true, the date value will be represented as a date only (without a time). If `asDateOnly` is false, the date value will be represented as date and time, padded with zeros if necessary, and set to the beginning of the day if no time is provided. The `asDateOnly` parameter is especially useful in the `ToModifiedDate` field of a query: If `asDateOnly` is set to true in the `ToModifiedDate` field of a query, then the query includes elements modified up to the end of the day. If `asDateOnly` is false, the query includes elements modified up to the specified time (or up to the beginning of the day if no time is included). */
+    ToModifiedDate?: string;
+    /** Filters according to the object’s `Name`. */
+    NameFilter?: NameFilter;
+    /** Filters according to the object’s `Name`. */
+    NameRangeFilter?: NameRangeFilter;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface VehicleQueryRs {
+    VehicleRet: VehicleRet[];
+}
+export interface VehicleRef {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string;
+    /** `FullName` (along with `ListID`) is a way to identify a list object. The `FullName` is the name prefixed by the names of each ancestor, for example `Jones:Kitchen:Cabinets`. `FullName` values are not case-sensitive. */
+    FullName?: string;
+}
+export interface VehicleRet {
+    /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
+    ListID?: string;
+    /** Time the object was created. */
+    TimeCreated?: string;
+    /** Time the object was last modified. */
+    TimeModified?: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence?: string;
+    /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
+    Name?: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** A descriptive text field. */
+    Desc?: string;
+}
 export interface VendorAdd {
     /** The case-insensitive name of a list object, not including the names of its ancestors. `Name` must be unique, unless it is the `Name` of a “hierarchical” list object. List objects in different hierarchies can have duplicate names because their `FullNames` will still be unique. For example, two objects could both have the `Name` kitchen, but they could have unique `FullNames`, such as Job12:kitchen and Baker:kitchen. For built-in currencies, `Name` is the internationally accepted currency name and is not editable. */
     Name: string;