conductor-node 9.6.1 → 9.7.0

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

@@ -2295,234 +2295,785 @@ export interface CreditCardTxnResultInfoMod {
     ClientTransID?: string;
 }
 export type CreditCardTxnType = "Authorization" | "Capture" | "Charge" | "Refund" | "VoiceAuthorization";
-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`.
-  
-    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;
-}
-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 CustomDetailReportQueryRq {
-    /** The type of report being queried. */
-    CustomDetailReportType: CustomDetailReportType;
-    /** Set `DisplayReport` to true to display this report within the QuickBooks UI. (Default is false.) If you want the request to display the report without returning any data to your application, set the `responseData` attribute to `includeNone`. */
-    DisplayReport?: boolean;
-    /** If you omit both `ToReportDate` and `FromReportDate`, the report will cover the current fiscal year to date. */
-    ReportPeriod?: ReportPeriod;
-    /** The time period covered by this report. */
-    ReportDateMacro?: ReportDateMacro;
-    /** Allows you to query for a specified account type or for specific list elements. */
-    ReportAccountFilter?: ReportAccountFilter;
-    /** Allows you to query for a specified name type (customer, employee, vendor, or other) or query for specific list elements. */
-    ReportEntityFilter?: ReportEntityFilter;
-    /** Allows you to query for a specified item type (for example, discount, inventory, or non-inventory) or query for specific list elements. */
-    ReportItemFilter?: ReportItemFilter;
-    /** Allows you to query for a specified class. 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. */
-    ReportClassFilter?: ReportClassFilter;
-    /** Allows you to report on specific transaction types (for example, charge, check, deposit, or estimate). */
-    ReportTxnTypeFilter?: ReportTxnTypeFilter;
-    /** Returns reports that were modified between these two dates (inclusive). The range of acceptable dates for both `FromReportModifiedDate` and `ToReportModifiedDate` is 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
-    ReportModifiedDateRangeFilter?: ReportModifiedDateRangeFilter;
-    /** The time period covered by this report. */
-    ReportModifiedDateRangeMacro?: ReportModifiedDateRangeMacro;
-    /** The level of detail to include in the report. */
-    ReportDetailLevelFilter?: ReportDetailLevelFilter;
-    /** Allows you to query for posting reports, non-posting reports, or reports that are either one. */
-    ReportPostingStatusFilter?: ReportPostingStatusFilter;
-    /** `SummarizeRowsBy` (along with `IncludeColumnList`, in most cases) determines what data is calculated for this report and controls how the rows are organized and labeled. For example, if you set the value to `srbAccount`, the report’s row labels might be “Checking,” “Savings,” and so on. */
-    SummarizeRowsBy: SummarizeRowsBy;
-    /** A list of enum values showing which columns you want the report to return. (The report won’t return columns other than the ones you specify here.) */
-    IncludeColumn: IncludeColumn | IncludeColumn[];
-    /** Indicates whether this report should include all accounts or just those that are currently in use. */
-    IncludeAccounts?: IncludeAccounts;
-    /** The report will return open balance information up to the `ReportOpenBalanceAsOf` date. */
-    ReportOpenBalanceAsOf?: ReportOpenBalanceAsOf;
-    /** If `ReportBasis` is `rbCash`, the report bases income and expenses on the dates when money changed hands.`rbAccrual`, the report bases income on the dates when customers were invoiced and bases expenses on the dates when bills were entered.`rbNone`, the report uses the default `ReportBasis`, which is either the QuickBooks Preference setting or the QuickBooks default for a given type of report. In a report response, the SDK returns `rbNone` for reports that do not support `ReportBasis`. (The 1099 report, for example, has its own basis for generation.) */
-    ReportBasis?: ReportBasis;
-}
-export interface CustomDetailReportQueryRs {
-    ReportRet: ReportRet[];
-}
-export type CustomDetailReportType = "CustomTxnDetail";
-export interface CustomerAdd {
-    /** 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;
+export interface CreditMemoAdd {
+    /** 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;
     /** 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;
-    /** A reference to the list object that is one level above this one. For example, an inventory item with the `FullName` of `GermanCars`:Mercedes-Benz:`CL500I99AA` might have a parent object with the `FullName` of `GermanCars`:Mercedes-Benz.In a request, if a `ParentRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    ParentRef?: ParentRef;
-    /** 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;
-    /** The job title of a customer, vendor, employee, or person on the “other names” list. */
-    JobTitle?: string;
+    /** Refers to an accounts receivable account in the QuickBooks file. (The `AccountType` of this account will be `AccountsReceivable`.) If an `ARAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. If this field is in a transaction that links to other transactions, make sure this `ARAccountRef` matches the `ARAccountRef` used in the other transactions. For example, in an `ARRefundCreditCard` transaction, the `ARAccountRef` of the credit card refund transaction must match the `ARAccountRef` used in each of the linked credit transactions. */
+    ARAccountRef?: ARAccountRef;
+    /** QuickBooks templates specify how to print certain transactions. A template query returns the names of all templates that have been defined in QuickBooks. A `TemplateRef` element refers to one of these templates. */
+    TemplateRef?: TemplateRef;
+    /** 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;
+    /** 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;
     /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
     BillAddress?: BillAddress;
     /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
     ShipAddress?: ShipAddress;
-    /** List of ship to addresses. */
-    ShipToAddress?: ShipToAddress | ShipToAddress[];
-    /** 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;
-    /** Email address that would be carbon copied or CC. */
-    Cc?: 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;
-    /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
-    /** A list of contact records. */
-    Contacts?: Contacts | Contacts[];
-    /** Customer types allow business owners to categorize customers in ways that are meaningful for their businesses. For example, a customer type might indicate which industry a customer represents, or which part of the country a customer is in. A `CustomerTypeRef` aggregate refers to one of the types on the `CustomerType` list. In a request, if a `CustomerTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    CustomerTypeRef?: CustomerTypeRef;
+    /** If `IsPending` is set to true, the credit memo has not been completed. Within QuickBooks, you can change the `IsPending` status for a credit memo by choosing “Mark Credit `Memo` As Pending” or “Mark Credit `Memo` As Final” from the Edit menu. */
+    IsPending?: boolean;
+    /** Purchase order number. */
+    PONumber?: string;
     /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     TermsRef?: TermsRef;
+    /** The date on which payment is due. */
+    DueDate?: string;
     /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     SalesRepRef?: SalesRepRef;
-    /** The opening balance of this customer’s account. A positive number indicates money owed by the customer. */
-    OpenBalance?: string;
-    /** The date of the opening balance for this customer. */
-    OpenBalanceDate?: string;
-    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
-    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** QuickBooks uses the term `FOB`, “freight on board,” to indicate the place from which the product is shipped. The `FOB` has no accounting implications. */
+    FOB?: string;
+    /** The date when the product was, or will be, shipped. */
+    ShipDate?: string;
+    /** A shipping method, for example, standard mail or overnight delivery. A `ShipMethodRef` aggregate refers to an item on the `ShipMethod` list. In a request, if a `ShipMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ShipMethodRef?: ShipMethodRef;
     /** 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;
-    /** Country that sales tax is collected for. */
-    SalesTaxCountry?: SalesTaxCountry;
-    /** The customer’s resale number, if they have one. This number will not affect reports or sales tax calculations. */
-    ResaleNumber?: 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;
-    /** Set and returned as a positive number that indicates a customer’s or vendor’s credit limit. If no value has been defined, there is no credit limit. */
-    CreditLimit?: string;
-    /** Refers to a `PaymentMethod` object. In a request, if a `PreferredPaymentMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    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?: 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;
-    /** The date on which work for a sub-customer is expected to be complete; 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. */
-    JobProjectedEndDate?: string;
-    /** The date on which work for a sub-customer was completed; 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. */
-    JobEndDate?: string;
-    /** A short job description for 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. */
-    JobDesc?: string;
-    /** Job type can be used to separate jobs into any categories that are meaningful to the business. A `JobTypeRef` aggregate refers to a job type on the `JobType` list. In a request, if a `JobTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    JobTypeRef?: JobTypeRef;
-    /** Not supported. */
-    Notes?: string;
-    /** List of notes. */
-    AdditionalNotes?: AdditionalNotes | AdditionalNotes[];
-    /** Preference for how invoices are delivered. */
-    PreferredDeliveryMethod?: PreferredDeliveryMethod;
-    /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
-    PriceLevelRef?: PriceLevelRef;
+    /** The memo does not print on the credit memo, but does appear in the account register and the customer register. */
+    Memo?: string;
+    /** A standard message such as “Thank you for your business,” or “Please sign and return this estimate to indicate your approval.” A customer message can be included at the bottom of a form. A `CustomerMsgRef` aggregate refers to one of the messages on the `CustomerMsg` list. In a request, if a `CustomerMsgRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerMsgRef?: CustomerMsgRef;
+    /** 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;
+    /** If this is set to true, at runtime the customer referenced in this transaction will be checked for a valid email address. If there is no valid email address, the request will fail. If there is a valid email address currently in QuickBooks for the customer, and the request succeeds, the transaction will be added to `QuickBook`’s list of forms to be emailed, possibly in a batch. Notice that setting this field to true does not actually perform the emailing. 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 emailing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be emailed. */
+    IsToBeEmailed?: boolean;
+    /** For future use with international versions of QuickBooks. */
+    IsTaxIncluded?: boolean;
+    /** Refers to the sales-tax code for sales related to this customer. (That is, it refers to a member of the `SalesTaxCode` list.) The sales-tax code indicates whether an item is taxable or non-taxable, and why. In a request, if a `CustomerSalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerSalesTaxCodeRef?: CustomerSalesTaxCodeRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other?: string;
+    /** 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;
     /** Allows for the attachment of a user defined GUID value. */
     ExternalGUID?: string;
-    /** Tax registration number used in CA and UK. */
-    TaxRegistrationNumber?: string;
-    /** The currency object contains all of the information needed by QuickBooks to display and use. For built-in currencies, the name and currency code values are internationally accepted values and thus are not editable. The comma format is editable, as is the `IsActive` status. For user-defined currencies, every value in the object is editable including name and currency code. When used with `PriceLevels`, the `CurrencyRef` should only be used with “per item” price levels. */
-    CurrencyRef?: CurrencyRef;
+    /** Represents one line in the credit memo. Compare with `CreditMemoGroupLine`, which represents a previously defined group of lines in the credit memo. */
+    CreditMemoLineAdd?: CreditMemoLineAdd | CreditMemoLineAdd[];
+    /** Represents a previously defined group of lines in the credit memo. Compare with `CreditMemoLine`, which represents just one line in the credit memo. */
+    CreditMemoLineGroupAdd?: CreditMemoLineGroupAdd | CreditMemoLineGroupAdd[];
 }
-export interface CustomerAddRq {
-    CustomerAdd: CustomerAdd;
+export interface CreditMemoAddRq {
+    CreditMemoAdd: CreditMemoAdd;
     /** 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 CustomerAddRs {
-    CustomerRet?: CustomerRet;
+export interface CreditMemoAddRs {
+    CreditMemoRet?: CreditMemoRet;
     ErrorRecovery?: ErrorRecovery;
 }
-export interface CustomerMod {
-    /** 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;
+export interface CreditMemoLineAdd {
+    /** 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;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** If you specify both `Rate` and `Amount` in a request, the `Rate` you provide will be ignored, and you will receive a warning. If you specify both `Quantity` and `Amount` in an Add request, QuickBooks will use them to calculate `Rate`. (Rate, `Amount`, and `Quantity` cannot be cleared.) */
+    Rate?: string;
+    /** Indicates the price of something as a percent. */
+    RatePercent?: string;
+    /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
+    PriceLevelRef?: PriceLevelRef;
     /** 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;
-    /** A reference to the list object that is one level above this one. For example, an inventory item with the `FullName` of `GermanCars`:Mercedes-Benz:`CL500I99AA` might have a parent object with the `FullName` of `GermanCars`:Mercedes-Benz.In a request, if a `ParentRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    ParentRef?: ParentRef;
-    /** 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;
-    /** The job title of a customer, vendor, employee, or person on the “other names” list. */
-    JobTitle?: string;
-    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
-    BillAddress?: BillAddress;
-    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
-    ShipAddress?: ShipAddress;
-    /** List of ship to addresses. */
-    ShipToAddress?: ShipToAddress | ShipToAddress[];
-    /** 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;
-    /** Email address that would be carbon copied or CC. */
-    Cc?: 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;
-    /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
-    /** A list of contact records. */
-    ContactsMod?: ContactsMod | ContactsMod[];
-    /** Customer types allow business owners to categorize customers in ways that are meaningful for their businesses. For example, a customer type might indicate which industry a customer represents, or which part of the country a customer is in. A `CustomerTypeRef` aggregate refers to one of the types on the `CustomerType` list. In a request, if a `CustomerTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    CustomerTypeRef?: CustomerTypeRef;
-    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    TermsRef?: TermsRef;
-    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    SalesRepRef?: SalesRepRef;
-    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
-    SalesTaxCodeRef?: SalesTaxCodeRef;
-    /** 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;
-    /** The country that sales tax is collected for. */
-    SalesTaxCountry?: SalesTaxCountry;
-    /** The customer’s resale number, if they have one. This number will not affect reports or sales tax calculations. */
-    ResaleNumber?: 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;
+    /** A monetary amount. */
+    Amount?: string;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+    /** Indicates the date on which the QuickBooks user performs the service for the customer. */
+    ServiceDate?: string;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** Refers to a QuickBooks account. If you are using QB Online edition, you cannot specify an accounts receivable account here. If an `OverrideItemAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    OverrideItemAccountRef?: OverrideItemAccountRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other1?: string;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other2?: string;
+    /** Contains data from the credit card transaction used in the payment. This data originates from a previous `qbmsXML` credit card transaction. The data following the element `CreditCardTxnInputInfo`” data is the data from the original `qbmsXML` request. The “`CreditCardTxnResultInfo`” is the data from the original `qbmsXML` response. */
+    CreditCardTxnInfo?: CreditCardTxnInfo;
+    /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
+    DataExt?: DataExt | DataExt[];
+}
+export interface CreditMemoLineGroupAdd {
+    /** `ItemGroup` objects represent items that are grouped together for fast entry, and an `ItemGroupRef` aggregate refers to one of these item groups. In a request, if an `ItemGroupRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. You can use an `ItemGroupQuery` request to get information about all the item groups that are set up in the QuickBooks file. */
+    ItemGroupRef: ItemGroupRef;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
+    DataExt?: DataExt | DataExt[];
+}
+export interface CreditMemoLineGroupMod {
+    /** 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;
+    /** `ItemGroup` objects represent items that are grouped together for fast entry, and an `ItemGroupRef` aggregate refers to one of these item groups. In a request, if an `ItemGroupRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. You can use an `ItemGroupQuery` request to get information about all the item groups that are set up in the QuickBooks file. */
+    ItemGroupRef?: ItemGroupRef;
+    /** Quantity For transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** A list of `ICreditMemoLineRet` objects, each representing one line in the credit memo. */
+    CreditMemoLineMod?: CreditMemoLineMod | CreditMemoLineMod[];
+}
+export interface CreditMemoLineGroupRet {
+    /** 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;
+    /** `ItemGroup` objects represent items that are grouped together for fast entry, and an `ItemGroupRef` aggregate refers to one of these item groups. In a request, if an `ItemGroupRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. You can use an `ItemGroupQuery` request to get information about all the item groups that are set up in the QuickBooks file. */
+    ItemGroupRef: ItemGroupRef;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** If true, a list of this group’s individual items their amounts will appear on printed forms. */
+    IsPrintItemsInGroup: boolean;
+    /** Total amount of money paid or received. In a receive payment add transaction that has payment amount elements (such as `AppliedToTxnAdd` lines) you must supply a `TotalAmount` and the sum of all the `PaymentAmount` elements must not be greater than the `TotalAmount`. */
+    TotalAmount: string;
+    /** A list of `ICreditMemoLineRet` objects, each representing one line in the credit memo. */
+    CreditMemoLineRet?: CreditMemoLineRet | CreditMemoLineRet[];
+    /** 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 CreditMemoLineMod {
+    /** 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;
+    /** 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 items For `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;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** Quantity For transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** If you specify both `Rate` and `Amount` in a request, the `Rate` you provide will be ignored, and you will receive a warning. If you specify both `Quantity` and `Amount` in an Add request, QuickBooks will use them to calculate `Rate`. (Rate, `Amount`, and `Quantity` cannot be cleared.) */
+    Rate?: string;
+    /** Indicates the price of something as a percent. */
+    RatePercent?: string;
+    /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.)
+  
+    The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
+    PriceLevelRef?: PriceLevelRef;
+    /** 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;
+    /** A monetary amount. */
+    Amount?: string;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+    /** Indicates the date on which the QuickBooks user performs the service for the customer. */
+    ServiceDate?: string;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default: Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false) Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true)
+  
+    A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** Refers to a QuickBooks account. If you are using QB Online edition, you cannot specify an accounts receivable account here. If an `OverrideItemAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    OverrideItemAccountRef?: OverrideItemAccountRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it.
+  
+    The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other1?: string;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it.
+  
+    The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other2?: string;
+}
+export interface CreditMemoLineRet {
+    /** 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;
+    /** 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 items For `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;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** If you specify both `Rate` and `Amount` in a request, the `Rate` you provide will be ignored, and you will receive a warning. If you specify both `Quantity` and `Amount` in an Add request, QuickBooks will use them to calculate `Rate`. (Rate, `Amount`, and `Quantity` cannot be cleared.) */
+    Rate?: string;
+    /** Indicates the price of something as a percent. */
+    RatePercent?: string;
+    /** 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;
+    /** A monetary amount. */
+    Amount?: string;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+    /** The expiration date of the inventory serial/lot number. Expiration `Date` is supported from QB Desktop 2023 version 3 (USA & Canada) and SDK 16.0. */
+    ExpirationDateForSerialLotNumber?: string;
+    /** Indicates the date on which the QuickBooks user performs the service for the customer. */
+    ServiceDate?: string;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default: Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false) Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true)
+  
+    A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it.
+  
+    The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other1?: string;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it.
+  
+    The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other2?: string;
+    /** Contains data from the credit card transaction used in the payment. This data originates from a previous `qbmsXML` credit card transaction. The data following the element `CreditCardTxnInputInfo`” data is the data from the original `qbmsXML` request. The “`CreditCardTxnResultInfo`” is the data from the original `qbmsXML` response. */
+    CreditCardTxnInfo?: CreditCardTxnInfo;
+    /** 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 CreditMemoMod {
+    /** 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 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;
+    /** 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;
+    /** Refers to an accounts receivable account in the QuickBooks file. (The `AccountType` of this account will be `AccountsReceivable`.) If an `ARAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    If this field is in a transaction that links to other transactions, make sure this `ARAccountRef` matches the `ARAccountRef` used in the other transactions. For example, in an `ARRefundCreditCard` transaction, the `ARAccountRef` of the credit card refund transaction must match the `ARAccountRef` used in each of the linked credit transactions. */
+    ARAccountRef?: ARAccountRef;
+    /** QuickBooks templates specify how to print certain transactions. A template query returns the names of all templates that have been defined in QuickBooks. A `TemplateRef` element refers to one of these templates. */
+    TemplateRef?: TemplateRef;
+    /** 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;
+    /** 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;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines.
+  
+    There are two ways to specify an address within this aggregate:
+  
+    Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode. Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query)
+  
+    If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    BillAddress?: BillAddress;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines.
+  
+    There are two ways to specify an address within this aggregate:
+  
+    Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode. Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query)
+  
+    If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    ShipAddress?: ShipAddress;
+    /** If `IsPending` is set to true, the credit memo has not been completed. Within QuickBooks, you can change the `IsPending` status for a credit memo by choosing “Mark Credit `Memo` As Pending” or “Mark Credit `Memo` As Final” from the Edit menu. */
+    IsPending?: boolean;
+    /** Purchase order number. */
+    PONumber?: string;
+    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    TermsRef?: TermsRef;
+    /** The date on which payment is due. */
+    DueDate?: string;
+    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    SalesRepRef?: SalesRepRef;
+    /** QuickBooks uses the term `FOB`, “freight on board,” to indicate the place from which the product is shipped. The `FOB` has no accounting implications. */
+    FOB?: string;
+    /** The date when the product was, or will be, shipped. */
+    ShipDate?: string;
+    /** A shipping method, for example, standard mail or overnight delivery. A `ShipMethodRef` aggregate refers to an item on the `ShipMethod` list. In a request, if a `ShipMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ShipMethodRef?: ShipMethodRef;
+    /** 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;
+    /** The memo does not print on the credit memo, but does appear in the account register and the customer register. */
+    Memo?: string;
+    /** A standard message such as “Thank you for your business,” or “Please sign and return this estimate to indicate your approval.” A customer message can be included at the bottom of a form. A `CustomerMsgRef` aggregate refers to one of the messages on the `CustomerMsg` list. In a request, if a `CustomerMsgRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerMsgRef?: CustomerMsgRef;
+    /** 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;
+    /** If this is set to true, at runtime the customer referenced in this transaction will be checked for a valid email address. If there is no valid email address, the request will fail. If there is a valid email address currently in QuickBooks for the customer, and the request succeeds, the transaction will be added to `QuickBook`’s list of forms to be emailed, possibly in a batch.
+  
+    Notice that setting this field to true does not actually perform the emailing. 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 emailing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be emailed. */
+    IsToBeEmailed?: boolean;
+    /** For future use with international versions of QuickBooks. */
+    IsTaxIncluded?: boolean;
+    /** Refers to the sales-tax code for sales related to this customer. (That is, it refers to a member of the `SalesTaxCode` list.) The sales-tax code indicates whether an item is taxable or non-taxable, and why. In a request, if a `CustomerSalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerSalesTaxCodeRef?: CustomerSalesTaxCodeRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it.
+  
+    The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other?: string;
+    /** 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;
+    /** Represents one line in the credit memo. Compare with `CreditMemoGroupLine`, which represents a previously defined group of lines in the credit memo. */
+    CreditMemoLineMod?: CreditMemoLineMod;
+    /** Represents a previously defined group of lines in the credit memo. Compare with `CreditMemoLine`, which represents just one line in the credit memo. */
+    CreditMemoLineGroupMod?: CreditMemoLineGroupMod;
+}
+export interface CreditMemoModRq {
+    CreditMemoMod: CreditMemoMod;
+    /** 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 CreditMemoModRs {
+    CreditMemoRet?: CreditMemoRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface CreditMemoQueryRq {
+    /** 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 `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;
+    /** Filters by the specified currency. */
+    CurrencyFilter?: CurrencyFilter;
+    /** 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;
+    /** If you set `IncludeLinkedTxns` to true, then the returned object will include a list of all the transactions linked to the queried object. (This list is similar to the History view of a transaction in the user interface, but not identical, as the SDK list contains only linked transactions, not items.) Each linked transaction will be represented by a `LinkedTxn` aggregate. If no linked transactions exist, no `LinkedTxn` aggregates will be returned. */
+    IncludeLinkedTxns?: 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 CreditMemoQueryRs {
+    CreditMemoRet: CreditMemoRet[];
+}
+export interface CreditMemoRet {
+    /** 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;
+    /** 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;
+    /** 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;
+    /** Refers to an accounts receivable account in the QuickBooks file. (The `AccountType` of this account will be `AccountsReceivable`.) If an `ARAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    If this field is in a transaction that links to other transactions, make sure this `ARAccountRef` matches the `ARAccountRef` used in the other transactions. For example, in an `ARRefundCreditCard` transaction, the `ARAccountRef` of the credit card refund transaction must match the `ARAccountRef` used in each of the linked credit transactions. */
+    ARAccountRef?: ARAccountRef;
+    /** QuickBooks templates specify how to print certain transactions. A template query returns the names of all templates that have been defined in QuickBooks. A `TemplateRef` element refers to one of these templates. */
+    TemplateRef?: TemplateRef;
+    /** 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;
+    /** 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;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines.
+  
+    There are two ways to specify an address within this aggregate:
+  
+    Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode. Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query)
+  
+    If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    BillAddress?: BillAddress;
+    /** 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. */
+    BillAddressBlock?: BillAddressBlock;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines.
+  
+    There are two ways to specify an address within this aggregate:
+  
+    Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode. Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query)
+  
+    If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    ShipAddress?: ShipAddress;
+    /** 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. */
+    ShipAddressBlock?: ShipAddressBlock;
+    /** If `IsPending` is set to true, the credit memo has not been completed. Within QuickBooks, you can change the `IsPending` status for a credit memo by choosing “Mark Credit `Memo` As Pending” or “Mark Credit `Memo` As Final” from the Edit menu. */
+    IsPending?: boolean;
+    /** Purchase order number. */
+    PONumber?: string;
+    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    TermsRef?: TermsRef;
+    /** The date on which payment is due. */
+    DueDate?: string;
+    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    SalesRepRef?: SalesRepRef;
+    /** QuickBooks uses the term `FOB`, “freight on board,” to indicate the place from which the product is shipped. The `FOB` has no accounting implications. */
+    FOB?: string;
+    /** The date when the product was, or will be, shipped. */
+    ShipDate?: string;
+    /** A shipping method, for example, standard mail or overnight delivery. A `ShipMethodRef` aggregate refers to an item on the `ShipMethod` list. In a request, if a `ShipMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ShipMethodRef?: ShipMethodRef;
+    /** The total of all the credit-memo lines, before taxes are applied. (By contrast, a subtotal item (an `ItemSubtotal` object) gives only the total of the amounts in the lines that appear above it.) */
+    Subtotal?: 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;
+    /** The percentage charged for sales tax. */
+    SalesTaxPercentage?: string;
+    /** The total amount of sales tax charged. */
+    SalesTaxTotal?: string;
+    /** Subtotal plus `SalesTaxTotal`. */
+    TotalAmount?: string;
+    /** Available credit. */
+    CreditRemaining?: string;
+    /** The currency object contains all of the information needed by QuickBooks to display and use. For built-in currencies, the name and currency code values are internationally accepted values and thus are not editable. The comma format is editable, as is the `IsActive` status. For user-defined currencies, every value in the object is editable including name and currency code.
+  
+    When used with `PriceLevels`, the `CurrencyRef` should only be used with “per item” price levels. */
+    CurrencyRef?: CurrencyRef;
+    /** 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 amount of the remaining credit, expressed in units of the current home currency. */
+    CreditRemainingInHomeCurrency?: string;
+    /** The memo does not print on the credit memo, but does appear in the account register and the customer register. */
+    Memo?: string;
+    /** A standard message such as “Thank you for your business,” or “Please sign and return this estimate to indicate your approval.” A customer message can be included at the bottom of a form. A `CustomerMsgRef` aggregate refers to one of the messages on the `CustomerMsg` list. In a request, if a `CustomerMsgRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerMsgRef?: CustomerMsgRef;
+    /** 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;
+    /** If this is set to true, at runtime the customer referenced in this transaction will be checked for a valid email address. If there is no valid email address, the request will fail. If there is a valid email address currently in QuickBooks for the customer, and the request succeeds, the transaction will be added to `QuickBook`’s list of forms to be emailed, possibly in a batch.
+  
+    Notice that setting this field to true does not actually perform the emailing. 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 emailing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be emailed. */
+    IsToBeEmailed?: boolean;
+    /** For future use with international versions of QuickBooks. */
+    IsTaxIncluded?: boolean;
+    /** Refers to the sales-tax code for sales related to this customer. (That is, it refers to a member of the `SalesTaxCode` list.) The sales-tax code indicates whether an item is taxable or non-taxable, and why. In a request, if a `CustomerSalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerSalesTaxCodeRef?: CustomerSalesTaxCodeRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it.
+  
+    The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other?: string;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** If the `IncludeLinkedTxns` flag is set to true in a query, or if you create an item receipt that links to other transactionsthen the returned object will include a list of linked transactions, if any exist. If no linked transactions exist, the `ILinkedTxnList` object will be empty.
+  
+    The list of linked transactions is similar to the History view of a transaction in the user interface, but not identical, as the SDK list contains only linked transactions, not items. */
+    LinkedTxn?: LinkedTxn | LinkedTxn[];
+    /** Represents one line in the credit memo. Compare with `CreditMemoGroupLine`, which represents a previously defined group of lines in the credit memo. */
+    CreditMemoLineRet?: CreditMemoLineRet;
+    /** Represents a previously defined group of lines in the credit memo. Compare with `CreditMemoLine`, which represents just one line in the credit memo. */
+    CreditMemoLineGroupRet?: CreditMemoLineGroupRet;
+    /** 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 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`.
+  
+    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;
+}
+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 CustomDetailReportQueryRq {
+    /** The type of report being queried. */
+    CustomDetailReportType: CustomDetailReportType;
+    /** Set `DisplayReport` to true to display this report within the QuickBooks UI. (Default is false.) If you want the request to display the report without returning any data to your application, set the `responseData` attribute to `includeNone`. */
+    DisplayReport?: boolean;
+    /** If you omit both `ToReportDate` and `FromReportDate`, the report will cover the current fiscal year to date. */
+    ReportPeriod?: ReportPeriod;
+    /** The time period covered by this report. */
+    ReportDateMacro?: ReportDateMacro;
+    /** Allows you to query for a specified account type or for specific list elements. */
+    ReportAccountFilter?: ReportAccountFilter;
+    /** Allows you to query for a specified name type (customer, employee, vendor, or other) or query for specific list elements. */
+    ReportEntityFilter?: ReportEntityFilter;
+    /** Allows you to query for a specified item type (for example, discount, inventory, or non-inventory) or query for specific list elements. */
+    ReportItemFilter?: ReportItemFilter;
+    /** Allows you to query for a specified class. 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. */
+    ReportClassFilter?: ReportClassFilter;
+    /** Allows you to report on specific transaction types (for example, charge, check, deposit, or estimate). */
+    ReportTxnTypeFilter?: ReportTxnTypeFilter;
+    /** Returns reports that were modified between these two dates (inclusive). The range of acceptable dates for both `FromReportModifiedDate` and `ToReportModifiedDate` is 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
+    ReportModifiedDateRangeFilter?: ReportModifiedDateRangeFilter;
+    /** The time period covered by this report. */
+    ReportModifiedDateRangeMacro?: ReportModifiedDateRangeMacro;
+    /** The level of detail to include in the report. */
+    ReportDetailLevelFilter?: ReportDetailLevelFilter;
+    /** Allows you to query for posting reports, non-posting reports, or reports that are either one. */
+    ReportPostingStatusFilter?: ReportPostingStatusFilter;
+    /** `SummarizeRowsBy` (along with `IncludeColumnList`, in most cases) determines what data is calculated for this report and controls how the rows are organized and labeled. For example, if you set the value to `srbAccount`, the report’s row labels might be “Checking,” “Savings,” and so on. */
+    SummarizeRowsBy: SummarizeRowsBy;
+    /** A list of enum values showing which columns you want the report to return. (The report won’t return columns other than the ones you specify here.) */
+    IncludeColumn: IncludeColumn | IncludeColumn[];
+    /** Indicates whether this report should include all accounts or just those that are currently in use. */
+    IncludeAccounts?: IncludeAccounts;
+    /** The report will return open balance information up to the `ReportOpenBalanceAsOf` date. */
+    ReportOpenBalanceAsOf?: ReportOpenBalanceAsOf;
+    /** If `ReportBasis` is `rbCash`, the report bases income and expenses on the dates when money changed hands.`rbAccrual`, the report bases income on the dates when customers were invoiced and bases expenses on the dates when bills were entered.`rbNone`, the report uses the default `ReportBasis`, which is either the QuickBooks Preference setting or the QuickBooks default for a given type of report. In a report response, the SDK returns `rbNone` for reports that do not support `ReportBasis`. (The 1099 report, for example, has its own basis for generation.) */
+    ReportBasis?: ReportBasis;
+}
+export interface CustomDetailReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type CustomDetailReportType = "CustomTxnDetail";
+export interface CustomerAdd {
+    /** 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;
+    /** 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;
+    /** A reference to the list object that is one level above this one. For example, an inventory item with the `FullName` of `GermanCars`:Mercedes-Benz:`CL500I99AA` might have a parent object with the `FullName` of `GermanCars`:Mercedes-Benz.In a request, if a `ParentRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ParentRef?: ParentRef;
+    /** 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;
+    /** The job title of a customer, vendor, employee, or person on the “other names” list. */
+    JobTitle?: string;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    BillAddress?: BillAddress;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    ShipAddress?: ShipAddress;
+    /** List of ship to addresses. */
+    ShipToAddress?: ShipToAddress | ShipToAddress[];
+    /** 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;
+    /** Email address that would be carbon copied or CC. */
+    Cc?: 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;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** A list of contact records. */
+    Contacts?: Contacts | Contacts[];
+    /** Customer types allow business owners to categorize customers in ways that are meaningful for their businesses. For example, a customer type might indicate which industry a customer represents, or which part of the country a customer is in. A `CustomerTypeRef` aggregate refers to one of the types on the `CustomerType` list. In a request, if a `CustomerTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerTypeRef?: CustomerTypeRef;
+    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    TermsRef?: TermsRef;
+    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    SalesRepRef?: SalesRepRef;
+    /** The opening balance of this customer’s account. A positive number indicates money owed by the customer. */
+    OpenBalance?: string;
+    /** The date of the opening balance for this customer. */
+    OpenBalanceDate?: string;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** 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;
+    /** Country that sales tax is collected for. */
+    SalesTaxCountry?: SalesTaxCountry;
+    /** The customer’s resale number, if they have one. This number will not affect reports or sales tax calculations. */
+    ResaleNumber?: 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;
+    /** Set and returned as a positive number that indicates a customer’s or vendor’s credit limit. If no value has been defined, there is no credit limit. */
+    CreditLimit?: string;
+    /** Refers to a `PaymentMethod` object. In a request, if a `PreferredPaymentMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    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?: 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;
+    /** The date on which work for a sub-customer is expected to be complete; 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. */
+    JobProjectedEndDate?: string;
+    /** The date on which work for a sub-customer was completed; 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. */
+    JobEndDate?: string;
+    /** A short job description for 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. */
+    JobDesc?: string;
+    /** Job type can be used to separate jobs into any categories that are meaningful to the business. A `JobTypeRef` aggregate refers to a job type on the `JobType` list. In a request, if a `JobTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    JobTypeRef?: JobTypeRef;
+    /** Not supported. */
+    Notes?: string;
+    /** List of notes. */
+    AdditionalNotes?: AdditionalNotes | AdditionalNotes[];
+    /** Preference for how invoices are delivered. */
+    PreferredDeliveryMethod?: PreferredDeliveryMethod;
+    /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
+    PriceLevelRef?: PriceLevelRef;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** Tax registration number used in CA and UK. */
+    TaxRegistrationNumber?: string;
+    /** The currency object contains all of the information needed by QuickBooks to display and use. For built-in currencies, the name and currency code values are internationally accepted values and thus are not editable. The comma format is editable, as is the `IsActive` status. For user-defined currencies, every value in the object is editable including name and currency code. When used with `PriceLevels`, the `CurrencyRef` should only be used with “per item” price levels. */
+    CurrencyRef?: CurrencyRef;
+}
+export interface CustomerAddRq {
+    CustomerAdd: CustomerAdd;
+    /** 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 CustomerAddRs {
+    CustomerRet?: CustomerRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface CustomerMod {
+    /** 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;
+    /** 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;
+    /** A reference to the list object that is one level above this one. For example, an inventory item with the `FullName` of `GermanCars`:Mercedes-Benz:`CL500I99AA` might have a parent object with the `FullName` of `GermanCars`:Mercedes-Benz.In a request, if a `ParentRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ParentRef?: ParentRef;
+    /** 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;
+    /** The job title of a customer, vendor, employee, or person on the “other names” list. */
+    JobTitle?: string;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    BillAddress?: BillAddress;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    ShipAddress?: ShipAddress;
+    /** List of ship to addresses. */
+    ShipToAddress?: ShipToAddress | ShipToAddress[];
+    /** 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;
+    /** Email address that would be carbon copied or CC. */
+    Cc?: 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;
+    /** List of additional contacts. */
+    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    /** A list of contact records. */
+    ContactsMod?: ContactsMod | ContactsMod[];
+    /** Customer types allow business owners to categorize customers in ways that are meaningful for their businesses. For example, a customer type might indicate which industry a customer represents, or which part of the country a customer is in. A `CustomerTypeRef` aggregate refers to one of the types on the `CustomerType` list. In a request, if a `CustomerTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerTypeRef?: CustomerTypeRef;
+    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    TermsRef?: TermsRef;
+    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    SalesRepRef?: SalesRepRef;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** 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;
+    /** The country that sales tax is collected for. */
+    SalesTaxCountry?: SalesTaxCountry;
+    /** The customer’s resale number, if they have one. This number will not affect reports or sales tax calculations. */
+    ResaleNumber?: 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;
     /** Set and returned as a positive number that indicates a customer’s or vendor’s credit limit. If no value has been defined, there is no credit limit. */
     CreditLimit?: string;
     /** Refers to a `PaymentMethod` object. In a request, if a `PreferredPaymentMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
@@ -6860,6 +7411,12 @@ export interface ItemPaymentRet {
     /** 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 ItemPurchaseTaxRef {
+    /** 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 ItemReceiptAdd {
     /** A vendor is any person or company from whom a small business owner buys goods and services. (Banks and tax agencies usually are included on the vendor list.) A company’s vendor list contains information such as account balance and contact information about each vendor. A `VendorRef` aggregate refers to one of the vendors on the list. In a request, if a `VendorRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     VendorRef: VendorRef;
@@ -8817,144 +9374,591 @@ export interface ReportAccountFilter {
     /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
     FullNameWithChildren?: string;
 }
-/** @default: None */
-export type ReportBasis = "Accrual" | "Cash" | "None";
-export type ReportCalendar = "CalendarYear" | "FiscalYear" | "TaxYear";
-export interface ReportClassFilter {
-    /** 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;
-    /** Allows you to filter for data that relates to the specified object and its descendants. */
-    ListIDWithChildren?: string;
-    /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
-    FullNameWithChildren?: string;
+/** @default: None */
+export type ReportBasis = "Accrual" | "Cash" | "None";
+export type ReportCalendar = "CalendarYear" | "FiscalYear" | "TaxYear";
+export interface ReportClassFilter {
+    /** 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;
+    /** Allows you to filter for data that relates to the specified object and its descendants. */
+    ListIDWithChildren?: string;
+    /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
+    FullNameWithChildren?: string;
+}
+export interface ReportData {
+    /** A data row contains the actual data for each column. */
+    DataRow?: DataRow | DataRow[];
+    /** A text row contains only text and is used mainly for headings. */
+    TextRow?: TextRow | TextRow[];
+    /** A row that contains a calculated subtotal of the data in all the rows since the last `SubTotalRow` and, usually, a single underline. There can be multiple `SubTotalRow` aggregates in a report. */
+    SubtotalRow?: SubtotalRow | SubtotalRow[];
+    /** A row that contains a calculated total of all the data that has come before and a double underline. There will only be one `TotalRow` per report. If `TotalRow` does not include any numerical values, the columns required to show the total values are not part of the report. These columns were not included when the report was customized. */
+    TotalRow?: TotalRow;
+}
+export type ReportDateMacro = "All" | "LastMonth" | "LastMonthToDate" | "LastQuarter" | "LastQuarterToDate" | "LastWeek" | "LastWeekToDate" | "LastYear" | "LastYearToDate" | "NextFourWeeks" | "NextMonth" | "NextQuarter" | "NextWeek" | "NextYear" | "ThisMonth" | "ThisMonthToDate" | "ThisQuarter" | "ThisQuarterToDate" | "ThisWeek" | "ThisWeekToDate" | "ThisYear" | "ThisYearToDate" | "Today" | "Yesterday";
+/** @default: All */
+export type ReportDetailLevelFilter = "All" | "AllExceptSummary" | "SummaryOnly";
+export interface ReportEntityFilter {
+    /** Allows you to report on a specific name type. */
+    EntityTypeFilter?: EntityTypeFilter;
+    /** 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;
+    /** Allows you to filter for data that relates to the specified object and its descendants. */
+    ListIDWithChildren?: string;
+    /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
+    FullNameWithChildren?: string;
+}
+/** @default: Quarterly */
+export type ReportingPeriod = "Monthly" | "Quarterly";
+export interface ReportItemFilter {
+    /** Allows you to report on a specific item type. */
+    ItemTypeFilter?: ItemTypeFilter;
+    /** 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;
+    /** Allows you to filter for data that relates to the specified object and its descendants. */
+    ListIDWithChildren?: string;
+    /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
+    FullNameWithChildren?: string;
+}
+export interface ReportModifiedDateRangeFilter {
+    /** Selects information from this date and later. The range of acceptable dates is 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
+    FromReportModifiedDate?: string;
+    /** Selects information created on this date or earlier. The range of acceptable dates is 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
+    ToReportModifiedDate?: string;
+}
+export type ReportModifiedDateRangeMacro = "All" | "LastMonth" | "LastMonthToDate" | "LastQuarter" | "LastQuarterToDate" | "LastWeek" | "LastWeekToDate" | "LastYear" | "LastYearToDate" | "NextFourWeeks" | "NextMonth" | "NextQuarter" | "NextWeek" | "NextYear" | "ThisMonth" | "ThisMonthToDate" | "ThisQuarter" | "ThisQuarterToDate" | "ThisWeek" | "ThisWeekToDate" | "ThisYear" | "ThisYearToDate" | "Today" | "Yesterday";
+/** @default: Today */
+export type ReportOpenBalanceAsOf = "ReportEndDate" | "Today";
+export interface ReportPeriod {
+    /** Selects information from this date and later. The range of acceptable `FromReportDate` and `ToReportDate` values depends on how the report dates are determined. If the report dates are based on the dates of transactions, the range is 01/01/1901 to 12/31/9999. If the report dates are based on modification dates, the range will be 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). If you omit `FromReportDate`, it will be set to 1970-01-01T00:00:00 (1969-12-31T16:00:00-08:00 PST). */
+    FromReportDate?: string;
+    /** Selects information created on this date or earlier. The range of acceptable `ToReportDate` and `FromReportDate` values depends on how the report dates are determined. If the report dates are based on the dates of transactions, the range is 01/01/1901 to 12/31/9999. If the report dates are based on modification dates, the range will be 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). If you omit `ToReportDate`, it will be set to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
+    ToReportDate?: string;
+}
+export type ReportPostingStatusFilter = "Either" | "NonPosting" | "Posting";
+export interface ReportRet {
+    /** The main title for this report. */
+    ReportTitle: string;
+    /** The subtitle for this report. */
+    ReportSubtitle: string;
+    /** If `ReportBasis` is `rbCash`, the report bases income and expenses on the dates when money changed hands.`rbAccrual`, the report bases income on the dates when customers were invoiced and bases expenses on the dates when bills were entered.`rbNone`, the report uses the default `ReportBasis`, which is either the QuickBooks Preference setting or the QuickBooks default for a given type of report. In a report response, the SDK returns `rbNone` for reports that do not support `ReportBasis`. (The 1099 report, for example, has its own basis for generation.) */
+    ReportBasis?: ReportBasis;
+    /** The number of rows in the report. */
+    NumRows: number;
+    /** The number of columns in the report. */
+    NumColumns: number;
+    /** The number of rows to allocate for column titles. Although this number is usually 1, with some reports it is 2 or 3. (For an example of column titles that span multiple rows, look at a `ProfitAndLossByJob` report in QuickBooks.) */
+    NumColTitleRows: number;
+    /** A list of `IColDesc` objects, each of which identifies one column in the report. Each column is identified by a `colID` (the position of the column in the report), a title, and a type. If the report contains any data, it is given row-by-row in an `IReportData` object. */
+    ColDesc: ColDesc | ColDesc[];
+    /** If the report contains any data, it is given row-by-row in a `ReportData` aggregate. */
+    ReportData?: ReportData;
+}
+export interface ReportTxnTypeFilter {
+    /** A list of the transaction types you want the report to cover. */
+    TxnTypeFilter: TxnTypeFilter | TxnTypeFilter[];
+}
+export type ReturnColumns = "ActiveOnly" | "All" | "NonZero";
+export type ReturnRows = "ActiveOnly" | "All" | "NonZero";
+export interface RowData {
+    /** An enumerated value that shows the type of data that this row contains. Values: account class customer `customerMessage` `customerType` employee item `jobType` label `memorizedTxn` `memorizedReport` name `otherName` `paymentMethod` `payrollItem` `salesRep` `salesTaxCode` `shipMethod` state style terms `toDo` vendor `vendorType` */
+    RowType: RowType;
+    /** The data in this cell of the report. */
+    Value: string;
+}
+export type RowType = "account" | "class" | "customer" | "customerMessage" | "customerType" | "employee" | "item" | "jobType" | "label" | "memorizedReport" | "memorizedTxn" | "name" | "otherName" | "paymentMethod" | "payrollItem" | "salesRep" | "salesTaxCode" | "shipMethod" | "state" | "style" | "terms" | "toDo" | "vendor" | "vendorType";
+export interface SalesAndPurchase {
+    /** Appears in the `Description` column of a sales form when the QuickBooks user sells this item. For a fixed asset, describes the sale of the asset (for accounting purposes). */
+    SalesDesc?: string;
+    /** Price charged for this item. */
+    SalesPrice?: string;
+    /** Refers to an income account. If an `IncomeAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    IncomeAccountRef?: IncomeAccountRef;
+    /** Description that appears in the `Description` column of checks, bills, credit card charges, and item receipts (when an item is reordered). For a fixed asset, a description of the item as it was when it was purchased. */
+    PurchaseDesc?: string;
+    /** Amount that the QuickBooks user expects to pay when ordering or buying this item, or the amount that was actually paid for this item. */
+    PurchaseCost?: string;
+    /** Account used for taxes on purchases in CA or UK. */
+    PurchaseTaxCodeRef?: PurchaseTaxCodeRef;
+    /** Refers to an expense account. If an `ExpenseAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ExpenseAccountRef?: ExpenseAccountRef;
+    /** The preferred vendor for this item. If a `PrefVendorRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    PrefVendorRef?: PrefVendorRef;
+}
+export interface SalesAndPurchaseMod {
+    /** Appears in the `Description` column of a sales form when the QuickBooks user sells this item. For a fixed asset, describes the sale of the asset (for accounting purposes). */
+    SalesDesc?: string;
+    /** Price charged for this item. */
+    SalesPrice?: string;
+    /** Refers to an income account. If an `IncomeAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    IncomeAccountRef?: IncomeAccountRef;
+    /** Used to support changing the `AccountRef` in the Mod request. When you do this, the QuickBooks UI normally displays a prompt asking whether the change should apply to existing transactions or not. Specifying False basically dismisses this with a “No” answer; specifying True dismisses it with a “Yes” answer and then changes the existing transactions that use the item with that `AccountRef`. Setting this to “True” should be used with caution and normally only after some user has indicated that they want those changes made to all those existing transactions! If any affected transactions are protected by a closing date and password, the `AccountRef` changes will not be made and so the Mod request will return an error without making the requested Mod. */
+    ApplyIncomeAccountRefToExistingTxns?: boolean;
+    /** Description that appears in the `Description` column of checks, bills, credit card charges, and item receipts (when an item is reordered). For a fixed asset, a description of the item as it was when it was purchased. */
+    PurchaseDesc?: string;
+    /** Amount that the QuickBooks user expects to pay when ordering or buying this item, or the amount that was actually paid for this item. */
+    PurchaseCost?: string;
+    /** Account used for taxes on purchases in CA or UK. */
+    PurchaseTaxCodeRef?: PurchaseTaxCodeRef;
+    /** Refers to an expense account. If an `ExpenseAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ExpenseAccountRef?: ExpenseAccountRef;
+    /** Used to support changing the `AccountRef` in the Mod request. When you do this, the QuickBooks UI normally displays a prompt asking whether the change should apply to existing transactions or not. Specifying False basically dismisses this with a “No” answer; specifying True dismisses it with a “Yes” answer and then changes the existing transactions that use the item with that `AccountRef`. Setting this to “True” should be used with caution and normally only after some user has indicated that they want those changes made to all those existing transactions! If any affected transactions are protected by a closing date and password, the `AccountRef` changes will not be made and so the Mod request will return an error without making the requested Mod. */
+    ApplyExpenseAccountRefToExistingTxns?: boolean;
+    /** The preferred vendor for this item. If a `PrefVendorRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    PrefVendorRef?: PrefVendorRef;
+}
+export interface SalesOrderAdd {
+    /** 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;
+    /** 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;
+    /** QuickBooks templates specify how to print certain transactions. A template query returns the names of all templates that have been defined in QuickBooks. A `TemplateRef` element refers to one of these templates. */
+    TemplateRef?: TemplateRef;
+    /** 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;
+    /** 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;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    BillAddress?: BillAddress;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    ShipAddress?: ShipAddress;
+    /** Purchase order number. */
+    PONumber?: string;
+    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    TermsRef?: TermsRef;
+    /** The date on which payment is due. */
+    DueDate?: string;
+    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    SalesRepRef?: SalesRepRef;
+    /** QuickBooks uses the term `FOB`, “freight on board,” to indicate the place from which the product is shipped. The `FOB` has no accounting implications. */
+    FOB?: string;
+    /** The date when the product was, or will be, shipped. */
+    ShipDate?: string;
+    /** A shipping method, for example, standard mail or overnight delivery. A `ShipMethodRef` aggregate refers to an item on the `ShipMethod` list. In a request, if a `ShipMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ShipMethodRef?: ShipMethodRef;
+    /** 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;
+    /** If `IsManuallyClosed` is true, this sales order has been closed, even if some line items within it have not been invoiced. */
+    IsManuallyClosed?: boolean;
+    /** Additional information. */
+    Memo?: string;
+    /** A standard message such as “Thank you for your business,” or “Please sign and return this estimate to indicate your approval.” A customer message can be included at the bottom of a form. A `CustomerMsgRef` aggregate refers to one of the messages on the `CustomerMsg` list. In a request, if a `CustomerMsgRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerMsgRef?: CustomerMsgRef;
+    /** 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;
+    /** If this is set to true, at runtime the customer referenced in this transaction will be checked for a valid email address. If there is no valid email address, the request will fail. If there is a valid email address currently in QuickBooks for the customer, and the request succeeds, the transaction will be added to `QuickBook`’s list of forms to be emailed, possibly in a batch. Notice that setting this field to true does not actually perform the emailing. 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 emailing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be emailed. */
+    IsToBeEmailed?: boolean;
+    /** For future use with international versions of QuickBooks. */
+    IsTaxIncluded?: boolean;
+    /** Refers to the sales-tax code for sales related to this customer. (That is, it refers to a member of the `SalesTaxCode` list.) The sales-tax code indicates whether an item is taxable or non-taxable, and why. In a request, if a `CustomerSalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerSalesTaxCodeRef?: CustomerSalesTaxCodeRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other?: string;
+    /** 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;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** Represents one line in the sales order. Compare with `SalesOrderLineGroup`, which represents a previously defined group of lines in the sales order. */
+    SalesOrderLineAdd?: SalesOrderLineAdd | SalesOrderLineAdd[];
+    /** Represents a previously defined group of lines in the sales order. Compare with `SalesOrderLine`, which represents just one line in the sales order. */
+    SalesOrderLineGroupAdd?: SalesOrderLineGroupAdd | SalesOrderLineGroupAdd[];
+    /** The Sales Channel `Name` */
+    SOChannel?: SOChannel;
+    /** The Sales Store `Name` */
+    StoreName?: string;
+    /** The Sales Store type */
+    StoreType?: string;
+}
+export interface SalesOrderAddRq {
+    SalesOrderAdd: SalesOrderAdd;
+    /** 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 SalesOrderAddRs {
+    SalesOrderRet?: SalesOrderRet;
+    ErrorRecovery?: ErrorRecovery;
 }
-export interface ReportData {
-    /** A data row contains the actual data for each column. */
-    DataRow?: DataRow | DataRow[];
-    /** A text row contains only text and is used mainly for headings. */
-    TextRow?: TextRow | TextRow[];
-    /** A row that contains a calculated subtotal of the data in all the rows since the last `SubTotalRow` and, usually, a single underline. There can be multiple `SubTotalRow` aggregates in a report. */
-    SubtotalRow?: SubtotalRow | SubtotalRow[];
-    /** A row that contains a calculated total of all the data that has come before and a double underline. There will only be one `TotalRow` per report. If `TotalRow` does not include any numerical values, the columns required to show the total values are not part of the report. These columns were not included when the report was customized. */
-    TotalRow?: TotalRow;
+export interface SalesOrderLineAdd {
+    /** 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;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** If you specify both `Rate` and `Amount` in a request, the `Rate` you provide will be ignored, and you will receive a warning. If you specify both `Quantity` and `Amount` in an Add request, QuickBooks will use them to calculate `Rate`. (Rate, `Amount`, and `Quantity` cannot be cleared.) */
+    Rate?: string;
+    /** Indicates the price of something as a percent. */
+    RatePercent?: string;
+    /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
+    PriceLevelRef?: PriceLevelRef;
+    /** 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;
+    /** A monetary amount. */
+    Amount?: string;
+    /** Flag to override price rule conflict. */
+    OptionForPriceRuleConflict?: OptionForPriceRuleConflict;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** If `IsManuallyClosed` is true, this line of the sales order has been closed even if it has not been invoiced. */
+    IsManuallyClosed?: boolean;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other1?: string;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other2?: string;
+    /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
+    DataExt?: DataExt | DataExt[];
 }
-export type ReportDateMacro = "All" | "LastMonth" | "LastMonthToDate" | "LastQuarter" | "LastQuarterToDate" | "LastWeek" | "LastWeekToDate" | "LastYear" | "LastYearToDate" | "NextFourWeeks" | "NextMonth" | "NextQuarter" | "NextWeek" | "NextYear" | "ThisMonth" | "ThisMonthToDate" | "ThisQuarter" | "ThisQuarterToDate" | "ThisWeek" | "ThisWeekToDate" | "ThisYear" | "ThisYearToDate" | "Today" | "Yesterday";
-/** @default: All */
-export type ReportDetailLevelFilter = "All" | "AllExceptSummary" | "SummaryOnly";
-export interface ReportEntityFilter {
-    /** Allows you to report on a specific name type. */
-    EntityTypeFilter?: EntityTypeFilter;
-    /** 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;
-    /** Allows you to filter for data that relates to the specified object and its descendants. */
-    ListIDWithChildren?: string;
-    /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
-    FullNameWithChildren?: string;
+export interface SalesOrderLineGroupAdd {
+    /** `ItemGroup` objects represent items that are grouped together for fast entry, and an `ItemGroupRef` aggregate refers to one of these item groups. In a request, if an `ItemGroupRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. You can use an `ItemGroupQuery` request to get information about all the item groups that are set up in the QuickBooks file. */
+    ItemGroupRef: ItemGroupRef;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
+    DataExt?: DataExt | DataExt[];
 }
-/** @default: Quarterly */
-export type ReportingPeriod = "Monthly" | "Quarterly";
-export interface ReportItemFilter {
-    /** Allows you to report on a specific item type. */
-    ItemTypeFilter?: ItemTypeFilter;
-    /** 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;
-    /** Allows you to filter for data that relates to the specified object and its descendants. */
-    ListIDWithChildren?: string;
-    /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
-    FullNameWithChildren?: string;
+export interface SalesOrderLineGroupMod {
+    /** 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;
+    /** `ItemGroup` objects represent items that are grouped together for fast entry, and an `ItemGroupRef` aggregate refers to one of these item groups. In a request, if an `ItemGroupRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. You can use an `ItemGroupQuery` request to get information about all the item groups that are set up in the QuickBooks file. */
+    ItemGroupRef?: ItemGroupRef;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** A list of `SalesOrderLineRet` objects, each representing one line in the sales order. */
+    SalesOrderLineMod?: SalesOrderLineMod | SalesOrderLineMod[];
 }
-export interface ReportModifiedDateRangeFilter {
-    /** Selects information from this date and later. The range of acceptable dates is 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
-    FromReportModifiedDate?: string;
-    /** Selects information created on this date or earlier. The range of acceptable dates is 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
-    ToReportModifiedDate?: string;
+export interface SalesOrderLineGroupRet {
+    /** 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;
+    /** `ItemGroup` objects represent items that are grouped together for fast entry, and an `ItemGroupRef` aggregate refers to one of these item groups. In a request, if an `ItemGroupRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. You can use an `ItemGroupQuery` request to get information about all the item groups that are set up in the QuickBooks file. */
+    ItemGroupRef: ItemGroupRef;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** If true, a list of this group’s individual items their amounts will appear on printed forms. */
+    IsPrintItemsInGroup: boolean;
+    /** Total amount of money paid or received. In a receive payment add transaction that has payment amount elements (such as `AppliedToTxnAdd` lines) you must supply a `TotalAmount` and the sum of all the `PaymentAmount` elements must not be greater than the `TotalAmount`. */
+    TotalAmount: string;
+    /** A list of `SalesOrderLineRet` objects, each representing one line in the sales order. */
+    SalesOrderLineRet?: SalesOrderLineRet | SalesOrderLineRet[];
+    /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
+    DataExtRet?: DataExtRet | DataExtRet[];
+    /** The Sales Channel `Name`. */
+    SOChannel?: SOChannel;
+    /** The Sales Store `Name`. */
+    StoreName?: string;
+    /** The Sales Store type. */
+    StoreType?: string;
+}
+export interface SalesOrderLineMod {
+    /** 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;
+    /** 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;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** If you specify both `Rate` and `Amount` in a request, the `Rate` you provide will be ignored, and you will receive a warning. If you specify both `Quantity` and `Amount` in an Add request, QuickBooks will use them to calculate `Rate`. (Rate, `Amount`, and `Quantity` cannot be cleared.) */
+    Rate?: string;
+    /** Indicates the price of something as a percent. */
+    RatePercent?: string;
+    /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
+    PriceLevelRef?: PriceLevelRef;
+    /** 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;
+    /** A monetary amount. */
+    Amount?: string;
+    /** Flag to override price rule conflict. */
+    OptionForPriceRuleConflict?: OptionForPriceRuleConflict;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** If `IsManuallyClosed` is true, this line of the sales order has been closed even if it has not been invoiced. */
+    IsManuallyClosed?: boolean;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other1?: string;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other2?: string;
 }
-export type ReportModifiedDateRangeMacro = "All" | "LastMonth" | "LastMonthToDate" | "LastQuarter" | "LastQuarterToDate" | "LastWeek" | "LastWeekToDate" | "LastYear" | "LastYearToDate" | "NextFourWeeks" | "NextMonth" | "NextQuarter" | "NextWeek" | "NextYear" | "ThisMonth" | "ThisMonthToDate" | "ThisQuarter" | "ThisQuarterToDate" | "ThisWeek" | "ThisWeekToDate" | "ThisYear" | "ThisYearToDate" | "Today" | "Yesterday";
-/** @default: Today */
-export type ReportOpenBalanceAsOf = "ReportEndDate" | "Today";
-export interface ReportPeriod {
-    /** Selects information from this date and later. The range of acceptable `FromReportDate` and `ToReportDate` values depends on how the report dates are determined. If the report dates are based on the dates of transactions, the range is 01/01/1901 to 12/31/9999. If the report dates are based on modification dates, the range will be 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). If you omit `FromReportDate`, it will be set to 1970-01-01T00:00:00 (1969-12-31T16:00:00-08:00 PST). */
-    FromReportDate?: string;
-    /** Selects information created on this date or earlier. The range of acceptable `ToReportDate` and `FromReportDate` values depends on how the report dates are determined. If the report dates are based on the dates of transactions, the range is 01/01/1901 to 12/31/9999. If the report dates are based on modification dates, the range will be 1970-01-01 to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). If you omit `ToReportDate`, it will be set to 2038-01-19T03:14:07 (2038-01-18T19:14:07-08:00 PST). */
-    ToReportDate?: string;
+export interface SalesOrderLineRet {
+    /** 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;
+    /** 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;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** `QuantityFor` transactions: If an item line add on a transaction request specifies `Quantity` and `Amount` but not `Rate`, QuickBooks will use `Quantity` and `Amount` to calculate `Rate`. Likewise, if a request specifies `Quantity` and `Rate` but not `Amount`, QuickBooks will calculate the `Amount`. If a transaction add request includes a reference to an `ItemDiscount` item, do not include a `Quantity` element as well, or you will get an error. For Item requests: `Quantity` indicates how many of this item there are. */
+    Quantity?: number;
+    /** In a transaction line item, the name of the unit of measure selected from within the item’s available units. If the company file is enabled only for single unit of measure per item, this must be the base unit! */
+    UnitOfMeasure?: string;
+    /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
+    OverrideUOMSetRef?: OverrideUOMSetRef;
+    /** If you specify both `Rate` and `Amount` in a request, the `Rate` you provide will be ignored, and you will receive a warning. If you specify both `Quantity` and `Amount` in an Add request, QuickBooks will use them to calculate `Rate`. (Rate, `Amount`, and `Quantity` cannot be cleared.) */
+    Rate?: string;
+    /** Indicates the price of something as a percent. */
+    RatePercent?: string;
+    /** 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;
+    /** A monetary amount. */
+    Amount?: string;
+    /** Site where inventory is located. */
+    InventorySiteRef?: InventorySiteRef;
+    /** Location within the Inventory Site. */
+    InventorySiteLocationRef?: InventorySiteLocationRef;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+    /** The expiration date of the inventory serial/lot number. Expiration `Date` is supported from QB Desktop 2023 version 3 (USA & Canada) and SDK 16.0. */
+    ExpirationDateForSerialLotNumber?: string;
+    /** Each item on a sales form is assigned a sales-tax code that indicates whether the item is taxable or non-taxable, and why. Two general codes, which can be modified but not deleted, appear on the sales-tax code list by default:Non-taxable (`Name` = NON; `Desc` = Non-Taxable; `IsTaxable` = false)Taxable (`Name` = TAX; `Desc` = Taxable; `IsTaxable` = true) A sales-tax code can be deleted only if it is no longer associated with any customer, item, or transaction. If the “Do You Charge Sales Tax?” preference within QuickBooks is set to No, QuickBooks will assign the default non-taxable sales-tax code to all sales. A `SalesTaxCodeRef` aggregate refers to a sales-tax code on the list. In a request, if a `SalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a Customer message, `SalesTaxCodeRef` refers to the sales-tax code that will be used for items related to this customer. In an `ItemInventory` message, `SalesTaxCodeRef` refers to the type of sales tax that will be charged for this item, if it is a taxable item and if sales tax is set up within QuickBooks. */
+    SalesTaxCodeRef?: SalesTaxCodeRef;
+    /** The amount of this sales order line that has been invoiced. */
+    Invoiced?: number;
+    /** If `IsManuallyClosed` is true, this line of the sales order has been closed even if it has not been invoiced. */
+    IsManuallyClosed?: boolean;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other1?: string;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other2?: 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 type ReportPostingStatusFilter = "Either" | "NonPosting" | "Posting";
-export interface ReportRet {
-    /** The main title for this report. */
-    ReportTitle: string;
-    /** The subtitle for this report. */
-    ReportSubtitle: string;
-    /** If `ReportBasis` is `rbCash`, the report bases income and expenses on the dates when money changed hands.`rbAccrual`, the report bases income on the dates when customers were invoiced and bases expenses on the dates when bills were entered.`rbNone`, the report uses the default `ReportBasis`, which is either the QuickBooks Preference setting or the QuickBooks default for a given type of report. In a report response, the SDK returns `rbNone` for reports that do not support `ReportBasis`. (The 1099 report, for example, has its own basis for generation.) */
-    ReportBasis?: ReportBasis;
-    /** The number of rows in the report. */
-    NumRows: number;
-    /** The number of columns in the report. */
-    NumColumns: number;
-    /** The number of rows to allocate for column titles. Although this number is usually 1, with some reports it is 2 or 3. (For an example of column titles that span multiple rows, look at a `ProfitAndLossByJob` report in QuickBooks.) */
-    NumColTitleRows: number;
-    /** A list of `IColDesc` objects, each of which identifies one column in the report. Each column is identified by a `colID` (the position of the column in the report), a title, and a type. If the report contains any data, it is given row-by-row in an `IReportData` object. */
-    ColDesc: ColDesc | ColDesc[];
-    /** If the report contains any data, it is given row-by-row in a `ReportData` aggregate. */
-    ReportData?: ReportData;
+export interface SalesOrderMod {
+    /** 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 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;
+    /** 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;
+    /** QuickBooks templates specify how to print certain transactions. A template query returns the names of all templates that have been defined in QuickBooks. A `TemplateRef` element refers to one of these templates. */
+    TemplateRef?: TemplateRef;
+    /** 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;
+    /** 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;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    BillAddress?: BillAddress;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    ShipAddress?: ShipAddress;
+    /** Purchase order number. */
+    PONumber?: string;
+    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    TermsRef?: TermsRef;
+    /** The date on which payment is due. */
+    DueDate?: string;
+    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    SalesRepRef?: SalesRepRef;
+    /** QuickBooks uses the term `FOB`, “freight on board,” to indicate the place from which the product is shipped. The `FOB` has no accounting implications. */
+    FOB?: string;
+    /** The date when the product was, or will be, shipped. */
+    ShipDate?: string;
+    /** A shipping method, for example, standard mail or overnight delivery. A `ShipMethodRef` aggregate refers to an item on the `ShipMethod` list. In a request, if a `ShipMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ShipMethodRef?: ShipMethodRef;
+    /** 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;
+    /** If `IsManuallyClosed` is true, this sales order has been closed, even if some line items within it have not been invoiced. */
+    IsManuallyClosed?: boolean;
+    /** Additional information. */
+    Memo?: string;
+    /** A standard message such as “Thank you for your business,” or “Please sign and return this estimate to indicate your approval.” A customer message can be included at the bottom of a form. A `CustomerMsgRef` aggregate refers to one of the messages on the `CustomerMsg` list. In a request, if a `CustomerMsgRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerMsgRef?: CustomerMsgRef;
+    /** 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;
+    /** If this is set to true, at runtime the customer referenced in this transaction will be checked for a valid email address. If there is no valid email address, the request will fail. If there is a valid email address currently in QuickBooks for the customer, and the request succeeds, the transaction will be added to `QuickBook`’s list of forms to be emailed, possibly in a batch. Notice that setting this field to true does not actually perform the emailing. 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 emailing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be emailed. */
+    IsToBeEmailed?: boolean;
+    /** For future use with international versions of QuickBooks. */
+    IsTaxIncluded?: boolean;
+    /** Refers to the sales-tax code for sales related to this customer. (That is, it refers to a member of the `SalesTaxCode` list.) The sales-tax code indicates whether an item is taxable or non-taxable, and why. In a request, if a `CustomerSalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerSalesTaxCodeRef?: CustomerSalesTaxCodeRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other?: string;
+    /** 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;
+    /** Represents one line in the sales order. Compare with `SalesOrderLineGroup`, which represents a previously defined group of lines in the sales order. */
+    SalesOrderLineMod?: SalesOrderLineMod;
+    /** Represents a previously defined group of lines in the sales order. Compare with `SalesOrderLine`, which represents just one line in the sales order. */
+    SalesOrderLineGroupMod?: SalesOrderLineGroupMod;
+    /** The Sales Channel `Name`. */
+    SOChannel?: SOChannel;
+    /** The Sales Store `Name`. */
+    StoreName?: string;
+    /** The Sales Store type. */
+    StoreType?: string;
+}
+export interface SalesOrderModRq {
+    SalesOrderMod: SalesOrderMod;
+    /** 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 ReportTxnTypeFilter {
-    /** A list of the transaction types you want the report to cover. */
-    TxnTypeFilter: TxnTypeFilter | TxnTypeFilter[];
+export interface SalesOrderModRs {
+    SalesOrderRet?: SalesOrderRet;
+    ErrorRecovery?: ErrorRecovery;
 }
-export type ReturnColumns = "ActiveOnly" | "All" | "NonZero";
-export type ReturnRows = "ActiveOnly" | "All" | "NonZero";
-export interface RowData {
-    /** An enumerated value that shows the type of data that this row contains. Values: account class customer `customerMessage` `customerType` employee item `jobType` label `memorizedTxn` `memorizedReport` name `otherName` `paymentMethod` `payrollItem` `salesRep` `salesTaxCode` `shipMethod` state style terms `toDo` vendor `vendorType` */
-    RowType: RowType;
-    /** The data in this cell of the report. */
-    Value: string;
+export interface SalesOrderQueryRq {
+    /** 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 `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;
+    /** Filters by the specified currency. */
+    CurrencyFilter?: CurrencyFilter;
+    /** 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;
+    /** If you set `IncludeLinkedTxns` to true, then the returned object will include a list of all the transactions linked to the queried object. (This list is similar to the History view of a transaction in the user interface, but not identical, as the SDK list contains only linked transactions, not items.) Each linked transaction will be represented by a `LinkedTxn` aggregate. If no linked transactions exist, no `LinkedTxn` aggregates will be returned. */
+    IncludeLinkedTxns?: 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 type RowType = "account" | "class" | "customer" | "customerMessage" | "customerType" | "employee" | "item" | "jobType" | "label" | "memorizedReport" | "memorizedTxn" | "name" | "otherName" | "paymentMethod" | "payrollItem" | "salesRep" | "salesTaxCode" | "shipMethod" | "state" | "style" | "terms" | "toDo" | "vendor" | "vendorType";
-export interface SalesAndPurchase {
-    /** Appears in the `Description` column of a sales form when the QuickBooks user sells this item. For a fixed asset, describes the sale of the asset (for accounting purposes). */
-    SalesDesc?: string;
-    /** Price charged for this item. */
-    SalesPrice?: string;
-    /** Refers to an income account. If an `IncomeAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    IncomeAccountRef?: IncomeAccountRef;
-    /** Description that appears in the `Description` column of checks, bills, credit card charges, and item receipts (when an item is reordered). For a fixed asset, a description of the item as it was when it was purchased. */
-    PurchaseDesc?: string;
-    /** Amount that the QuickBooks user expects to pay when ordering or buying this item, or the amount that was actually paid for this item. */
-    PurchaseCost?: string;
-    /** Account used for taxes on purchases in CA or UK. */
-    PurchaseTaxCodeRef?: PurchaseTaxCodeRef;
-    /** Refers to an expense account. If an `ExpenseAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    ExpenseAccountRef?: ExpenseAccountRef;
-    /** The preferred vendor for this item. If a `PrefVendorRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    PrefVendorRef?: PrefVendorRef;
+export interface SalesOrderQueryRs {
+    SalesOrderRet: SalesOrderRet[];
 }
-export interface SalesAndPurchaseMod {
-    /** Appears in the `Description` column of a sales form when the QuickBooks user sells this item. For a fixed asset, describes the sale of the asset (for accounting purposes). */
-    SalesDesc?: string;
-    /** Price charged for this item. */
-    SalesPrice?: string;
-    /** Refers to an income account. If an `IncomeAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    IncomeAccountRef?: IncomeAccountRef;
-    /** Used to support changing the `AccountRef` in the Mod request. When you do this, the QuickBooks UI normally displays a prompt asking whether the change should apply to existing transactions or not. Specifying False basically dismisses this with a “No” answer; specifying True dismisses it with a “Yes” answer and then changes the existing transactions that use the item with that `AccountRef`. Setting this to “True” should be used with caution and normally only after some user has indicated that they want those changes made to all those existing transactions! If any affected transactions are protected by a closing date and password, the `AccountRef` changes will not be made and so the Mod request will return an error without making the requested Mod. */
-    ApplyIncomeAccountRefToExistingTxns?: boolean;
-    /** Description that appears in the `Description` column of checks, bills, credit card charges, and item receipts (when an item is reordered). For a fixed asset, a description of the item as it was when it was purchased. */
-    PurchaseDesc?: string;
-    /** Amount that the QuickBooks user expects to pay when ordering or buying this item, or the amount that was actually paid for this item. */
-    PurchaseCost?: string;
-    /** Account used for taxes on purchases in CA or UK. */
-    PurchaseTaxCodeRef?: PurchaseTaxCodeRef;
-    /** Refers to an expense account. If an `ExpenseAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    ExpenseAccountRef?: ExpenseAccountRef;
-    /** Used to support changing the `AccountRef` in the Mod request. When you do this, the QuickBooks UI normally displays a prompt asking whether the change should apply to existing transactions or not. Specifying False basically dismisses this with a “No” answer; specifying True dismisses it with a “Yes” answer and then changes the existing transactions that use the item with that `AccountRef`. Setting this to “True” should be used with caution and normally only after some user has indicated that they want those changes made to all those existing transactions! If any affected transactions are protected by a closing date and password, the `AccountRef` changes will not be made and so the Mod request will return an error without making the requested Mod. */
-    ApplyExpenseAccountRefToExistingTxns?: boolean;
-    /** The preferred vendor for this item. If a `PrefVendorRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
-    PrefVendorRef?: PrefVendorRef;
+export interface SalesOrderRet {
+    /** 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;
+    /** 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;
+    /** 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;
+    /** QuickBooks templates specify how to print certain transactions. A template query returns the names of all templates that have been defined in QuickBooks. A `TemplateRef` element refers to one of these templates. */
+    TemplateRef?: TemplateRef;
+    /** 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;
+    /** 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;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    BillAddress?: BillAddress;
+    /** 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. */
+    BillAddressBlock?: BillAddressBlock;
+    /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
+    ShipAddress?: ShipAddress;
+    /** 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. */
+    ShipAddressBlock?: ShipAddressBlock;
+    /** Purchase order number. */
+    PONumber?: string;
+    /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    TermsRef?: TermsRef;
+    /** The date on which payment is due. */
+    DueDate?: string;
+    /** A sales representative must be on the Employee, Vendor, or `Other` Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    SalesRepRef?: SalesRepRef;
+    /** QuickBooks uses the term `FOB`, “freight on board,” to indicate the place from which the product is shipped. The `FOB` has no accounting implications. */
+    FOB?: string;
+    /** The date when the product was, or will be, shipped. */
+    ShipDate?: string;
+    /** A shipping method, for example, standard mail or overnight delivery. A `ShipMethodRef` aggregate refers to an item on the `ShipMethod` list. In a request, if a `ShipMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    ShipMethodRef?: ShipMethodRef;
+    /** The total of the amounts in all the lines of an invoice, estimate, sales receipt, or credit memo before taxes or payments are applied. (By contrast, a subtotal item (an `ItemSubtotal` object) gives only the total of the amounts in the lines that appear above it.) */
+    Subtotal?: 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;
+    /** The percentage charged for sales tax. */
+    SalesTaxPercentage?: string;
+    /** The total amount of sales tax charged. */
+    SalesTaxTotal?: string;
+    /** Total amount of money paid or received. In a receive payment add transaction that has payment amount elements (such as `AppliedToTxnAdd` lines) you must supply a `TotalAmount` and the sum of all the `PaymentAmount` elements must not be greater than the `TotalAmount`. */
+    TotalAmount?: string;
+    /** The currency object contains all of the information needed by QuickBooks to display and use. For built-in currencies, the name and currency code values are internationally accepted values and thus are not editable. The comma format is editable, as is the `IsActive` status. For user-defined currencies, every value in the object is editable including name and currency code. When used with `PriceLevels`, the `CurrencyRef` should only be used with “per item” price levels. */
+    CurrencyRef?: CurrencyRef;
+    /** 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;
+    /** Total amount of money paid or received in the home currency. */
+    TotalAmountInHomeCurrency?: string;
+    /** If `IsManuallyClosed` is true, this sales order has been closed, even if some line items within it have not been invoiced. */
+    IsManuallyClosed?: boolean;
+    /** If `IsFullyInvoiced` is true, all the items in the sales order have been invoiced. */
+    IsFullyInvoiced?: boolean;
+    /** Additional information. */
+    Memo?: string;
+    /** A standard message such as “Thank you for your business,” or “Please sign and return this estimate to indicate your approval.” A customer message can be included at the bottom of a form. A `CustomerMsgRef` aggregate refers to one of the messages on the `CustomerMsg` list. In a request, if a `CustomerMsgRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerMsgRef?: CustomerMsgRef;
+    /** 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;
+    /** If this is set to true, at runtime the customer referenced in this transaction will be checked for a valid email address. If there is no valid email address, the request will fail. If there is a valid email address currently in QuickBooks for the customer, and the request succeeds, the transaction will be added to `QuickBook`’s list of forms to be emailed, possibly in a batch. Notice that setting this field to true does not actually perform the emailing. 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 emailing the transaction later. It simply results in the transaction NOT being placed in the list of transactions to be emailed. */
+    IsToBeEmailed?: boolean;
+    /** For future use with international versions of QuickBooks. */
+    IsTaxIncluded?: boolean;
+    /** Refers to the sales-tax code for sales related to this customer. (That is, it refers to a member of the `SalesTaxCode` list.) The sales-tax code indicates whether an item is taxable or non-taxable, and why. In a request, if a `CustomerSalesTaxCodeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    CustomerSalesTaxCodeRef?: CustomerSalesTaxCodeRef;
+    /** Other, `Other1`, and `Other2` are standard QuickBooks custom fields available to transactions. The `Other` field is a transaction-level field, like the `FOB` field, PO Number field, and so forth. This field appears only once for the transaction: you can write to it and modify it. The `Other1` and `Other2` fields exist at the line item level; each line item has them, and you can write or modify the value in each line. These custom fields are available for immediate use: you don’t need to enable these in the transaction template to be able to access them via SDK. (However, those `Other`, `Other1`, `Other2` fields and their values are viewable and printable in QuickBooks only if the transaction template has these enabled!) `Note`: you cannot use `DataExtDef` to define `Other`, `Other1`, `Other2` for the transaction. There is no need to in any case. Those are automatically available. Notice that the `Other`, `Other1`, and `Other2` names are the real SDK names for those custom fields: that is, their `DataExtName` value will always be `Other`, `Other1`, or `Other2`. Even if the user has re-labelled those custom fields to something else, such as “Barracks Number”, or “`Max` Headroom”, or even “Pleni Potentiary”. This re-labelling has no effect on the SDK. You’ll always write to them or modify them as `Other`, `Other1`, or `Other2`. */
+    Other?: string;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** If the `IncludeLinkedTxns` flag is set to true in a query, or if you create an item receipt that links to other transactionsthen the returned object will include a list of linked transactions, if any exist. If no linked transactions exist, the `ILinkedTxnList` object will be empty. The list of linked transactions is similar to the History view of a transaction in the user interface, but not identical, as the SDK list contains only linked transactions, not items. */
+    LinkedTxn?: LinkedTxn | LinkedTxn[];
+    /** Represents one line in the sales order. Compare with `SalesOrderLineGroup`, which represents a previously defined group of lines in the sales order. */
+    SalesOrderLineRet?: SalesOrderLineRet;
+    /** Represents a previously defined group of lines in the sales order. Compare with `SalesOrderLine`, which represents just one line in the sales order. */
+    SalesOrderLineGroupRet?: SalesOrderLineGroupRet;
+    /** 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 SalesOrPurchase {
     /** A descriptive text field. */
@@ -9508,12 +10512,107 @@ export interface SalesRepRet {
     /** Refers to the sales representative’s full information on the Employee, Vendor, or `OtherName` list. In a request, if a `SalesRepEntityRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. Notice that you cannot supply a customer name here. */
     SalesRepEntityRef: SalesRepEntityRef;
 }
+export interface SalesTaxCodeAdd {
+    /** Short name that will appear on sales forms to identify the tax status of an item. The `Desc` element gives a longer explanation of `Name`. `Name` must be unique, and it is not case-sensitive. */
+    Name: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** Indicates whether this sales-tax code is tracking taxable sales. For any particular sales-tax code, `IsTaxable` cannot be modified once the sales-tax code has been used in a transaction. If the “Do You Charge Sales Tax?” preference is set to Yes within QuickBooks, the default value of `IsTaxable` is true. If the “Do You Charge Sales Tax?” preference is set to No, the default value of `IsTaxable` is false. */
+    IsTaxable: boolean;
+    /** Desc gives a longer explanation of `Name`. */
+    Desc?: string;
+    /** For future use with international versions of QuickBooks. */
+    ItemPurchaseTaxRef?: ItemPurchaseTaxRef;
+    /** 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;
+}
+export interface SalesTaxCodeAddRq {
+    SalesTaxCodeAdd: SalesTaxCodeAdd;
+    /** 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 SalesTaxCodeAddRs {
+    SalesTaxCodeRet?: SalesTaxCodeRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface SalesTaxCodeMod {
+    /** 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;
+    /** Short name that will appear on sales forms to identify the tax status of an item. The `Desc` element gives a longer explanation of `Name`. `Name` must be unique, and it is not case-sensitive. */
+    Name?: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** Indicates whether this sales-tax code is tracking taxable sales. For any particular sales-tax code, `IsTaxable` cannot be modified once the sales-tax code has been used in a transaction. If the “Do You Charge Sales Tax?” preference is set to Yes within QuickBooks, the default value of `IsTaxable` is true. If the “Do You Charge Sales Tax?” preference is set to No, the default value of `IsTaxable` is false. */
+    IsTaxable?: boolean;
+    /** Desc gives a longer explanation of `Name`. */
+    Desc?: string;
+    /** For future use with international versions of QuickBooks. */
+    ItemPurchaseTaxRef?: ItemPurchaseTaxRef;
+    /** 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;
+}
+export interface SalesTaxCodeModRq {
+    SalesTaxCodeMod: SalesTaxCodeMod;
+    /** 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 SalesTaxCodeModRs {
+    SalesTaxCodeRet?: SalesTaxCodeRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface SalesTaxCodeQueryRq {
+    /** 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 SalesTaxCodeQueryRs {
+    SalesTaxCodeRet: SalesTaxCodeRet[];
+}
 export interface SalesTaxCodeRef {
     /** 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 SalesTaxCodeRet {
+    /** 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;
+    /** Short name that will appear on sales forms to identify the tax status of an item. The `Desc` element gives a longer explanation of `Name`. `Name` must be unique, and it is not case-sensitive. */
+    Name: string;
+    /** If `IsActive` is true, this object is currently enabled for use by QuickBooks. The default value is true. */
+    IsActive?: boolean;
+    /** Indicates whether this sales-tax code is tracking taxable sales. For any particular sales-tax code, `IsTaxable` cannot be modified once the sales-tax code has been used in a transaction. If the “Do You Charge Sales Tax?” preference is set to Yes within QuickBooks, the default value of `IsTaxable` is true. If the “Do You Charge Sales Tax?” preference is set to No, the default value of `IsTaxable` is false. */
+    IsTaxable: boolean;
+    /** Desc gives a longer explanation of `Name`. */
+    Desc?: string;
+    /** For future use with international versions of QuickBooks. */
+    ItemPurchaseTaxRef?: ItemPurchaseTaxRef;
+    /** 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;
+}
 /** @default: Canada */
 export type SalesTaxCountry = "Australia" | "Canada" | "UK" | "US";
 export interface SalesTaxReturnLineRef {
@@ -9690,6 +10789,7 @@ export interface SiteFilter {
     /** 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 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";
 export interface SubscribedServices {