conductor-node 9.5.0 → 9.6.0

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

@@ -314,31 +314,43 @@ export interface AppliedToTxnAdd {
     DiscountAmount?: string;
     /** Refers to the account where this discount is tracked. In a request, if a `DiscountAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     DiscountAccountRef?: DiscountAccountRef;
-    /** Class reference used in the Discount object */
+    /** Class reference used in the Discount object. */
     DiscountClassRef?: DiscountClassRef;
 }
 export interface AppliedToTxnMod {
-    /** 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. */
+    /** 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;
     /** Represents the amount assigned to a particular receivable. The sum of all `PaymentAmount` elements in any given receive payment transaction must not be greater than `TotalAmount`. */
     PaymentAmount?: string;
-    /** A list of credits to set. Setting, or applying, a credit means using an available credit to lower the balance of a transaction such as an invoice or a bill. (Creating a credit, on the other hand, means making a credit available to be applied in the future.) Notice that if you use a credit (`SetCredit`) only, in your `ReceivePaymentAdd` or `BillPaymentCreditCardAdd` request, then no transaction ID is created, because, from the viewpoint of QuickBooks, there was no transaction. Setting a credit merely creates links between existing transactions (for example, between a credit memo transaction and an invoice transaction), and no information about these links will be returned to you in the response. If you need to retrieve which transactions were linked in the `SetCredit`, for Bill Payment, you must do a `BillQuery` and specify `IncludeLinkedTxns`. */
+    /** A list of credits to set. Setting, or applying, a credit means using an available credit to lower the balance of a transaction such as an invoice or a bill. (Creating a credit, on the other hand, means making a credit available to be applied in the future.)
+  
+    Notice that if you use a credit (`SetCredit`) only, in your `ReceivePaymentAdd` or `BillPaymentCreditCardAdd` request, then no transaction ID is created, because, from the viewpoint of QuickBooks, there was no transaction. Setting a credit merely creates links between existing transactions (for example, between a credit memo transaction and an invoice transaction), and no information about these links will be returned to you in the response.
+  
+    If you need to retrieve which transactions were linked in the `SetCredit`, for Bill Payment, you must do a `BillQuery` and specify `IncludeLinkedTxns`. */
     SetCredit?: SetCredit | SetCredit[];
     /** Reduces the receivable amount. */
     DiscountAmount?: string;
     /** Refers to the account where this discount is tracked. In a request, if a `DiscountAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     DiscountAccountRef?: DiscountAccountRef;
-    /** Class reference used in the Discount object */
+    /** Class reference used in the Discount object. */
     DiscountClassRef?: DiscountClassRef;
 }
 export interface AppliedToTxnRet {
-    /** 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. */
+    /** 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;
     /** The type of transaction. */
     TxnType: TxnType;
     /** 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. */
+    /** 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;
     /** The outstanding balance on this invoice. `BalanceRemaining` = (`Subtotal` + `SalesTaxTotal`) – `AppliedAmount`. */
     BalanceRemaining?: string;
@@ -348,9 +360,11 @@ export interface AppliedToTxnRet {
     DiscountAmount?: string;
     /** Refers to the account where this discount is tracked. In a request, if a `DiscountAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     DiscountAccountRef?: DiscountAccountRef;
-    /** Class reference used in the Discount object */
+    /** Class reference used in the Discount object. */
     DiscountClassRef?: DiscountClassRef;
-    /** 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. */
+    /** 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[];
 }
 export interface ApplyCheckToTxnAdd {
@@ -911,6 +925,180 @@ export interface BillRet {
     /** 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 BudgetCriterion = "Accounts" | "AccountsAndClasses" | "AccountsAndCustomers";
+export interface BudgetSummaryReportQueryRq {
+    /** The type of budget report being queried. */
+    BudgetSummaryReportType: BudgetSummaryReportType;
+    /** 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;
+    /** Specify the fiscal year of the budget to be queried. There can only be one balance sheet budget for each fiscal year, one profit and loss (P&L) by account budget per fiscal year, and one profit and loss (P&L) by account and customer budget per fiscal year. When Fiscal year is not the current year, the report returns the data for the full fiscal year. When Fiscal year is the current year, the report only returns year to date data. */
+    FiscalYear: number;
+    /** What this budget covers. */
+    BudgetCriterion?: BudgetCriterion;
+    /** 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 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;
+    /** `SummarizeBudgetColumnsBy` determines which data the report calculates and how the columns will be labeled across the top of the report. */
+    SummarizeBudgetColumnsBy?: SummarizeBudgetColumnsBy;
+    /** How you want rows to be labeled in the report. For example, if you set the value to `sbrbAccount`, the report’s row labels might be “Checking,” “Savings,” and so on. */
+    SummarizeBudgetRowsBy?: SummarizeBudgetRowsBy;
+}
+export interface BudgetSummaryReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type BudgetSummaryReportType = "BalanceSheetBudgetOverview" | "BalanceSheetBudgetVsActual" | "ProfitAndLossBudgetOverview" | "ProfitAndLossBudgetPerformance" | "ProfitAndLossBudgetVsActual";
+export interface BuildAssemblyAdd {
+    /** An inventory assembly item is one that is assembled or manufactured from inventory items. The items and/or assemblies that make up the assembly are called components. For Premier, an assembly can have a maximum of 100 components. For Enterprise, the maximum is 500 components. */
+    ItemInventoryAssemblyRef: ItemInventoryAssemblyRef;
+    /** 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;
+    /** 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;
+    /** Additional information. */
+    Memo?: string;
+    /** Specifies the number of assemblies to be built. The transaction will fail if the number specified here exceeds the number of on-hand components. */
+    QuantityToBuild: number;
+    /** Allows the build assembly to be marked pending if there are insufficient quantities to complete the build assembly. */
+    MarkPendingIfRequired?: boolean;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+}
+export interface BuildAssemblyAddRq {
+    BuildAssemblyAdd: BuildAssemblyAdd;
+    /** 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 BuildAssemblyAddRs {
+    BuildAssemblyRet?: BuildAssemblyRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface BuildAssemblyMod {
+    /** 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;
+    /** 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;
+    /** 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;
+    /** Additional information. */
+    Memo?: string;
+    /** Specifies the number of assemblies to be built. The transaction will fail if the number specified here exceeds the number of on-hand components. */
+    QuantityToBuild?: number;
+    /** Allows the build assembly to be marked pending if there are insufficient quantities to complete the build assembly. */
+    MarkPendingIfRequired?: boolean;
+    /** Changes the transaction’s pending status from Pending to non pending. In `BuildAssembly` transactions, this effectively does the build transaction. Hence, removing the Pending status will fail if there aren’t enough components on hand for the build. */
+    RemovePending?: boolean;
+}
+export interface BuildAssemblyModRq {
+    BuildAssemblyMod: BuildAssemblyMod;
+    /** 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 BuildAssemblyModRs {
+    BuildAssemblyRet?: BuildAssemblyRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface BuildAssemblyQueryRq {
+    /** 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;
+    /** Filters according to the item name or ID. You can use an `ItemQuery` request to get information about all the items that are set up in the QuickBooks file. “Items” are line items used for fast entry on sales and purchase forms. They include services and goods that a business buys and sells, as well as special items that perform calculations–for example, subtotal, discount, and sales-tax items. */
+    ItemFilter?: ItemFilter;
+    /** Filters according to `RefNumber`. */
+    RefNumberFilter?: RefNumberFilter;
+    /** Filters according to `RefNumber`. The filtering code will do a numerical comparison (if `FromRefNumber` and `ToRefNumber` only contain digits) or a lexicographical comparison (if either `FromRefNumber` or `ToRefNumber` contain any nondigit characters). In the first situation, if you need to query for a `RefNumber` that is larger than the maximum long integer value of 2147483647, one workaround is to specify a `FromRefNumber` that is less than or equal to 2147483647 without specifying a `ToRefNumber`. */
+    RefNumberRangeFilter?: RefNumberRangeFilter;
+    /** Specifies whether the transaction is pending (posted) or not. */
+    PendingStatus?: PendingStatus;
+    /** Specify “true” if component line items for each returned transaction are to be included in the returned data. Specify “false” if the line items are not be returned. */
+    IncludeComponentLineItems?: 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 BuildAssemblyQueryRs {
+    BuildAssemblyRet: BuildAssemblyRet[];
+}
+export interface BuildAssemblyRet {
+    /** 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;
+    /** An inventory assembly item is one that is assembled or manufactured from inventory items. The items and/or assemblies that make up the assembly are called components. For Premier, an assembly can have a maximum of 100 components. For Enterprise, the maximum is 500 components. */
+    ItemInventoryAssemblyRef: ItemInventoryAssemblyRef;
+    /** 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;
+    /** 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;
+    /** Additional information. */
+    Memo?: string;
+    /** If `IsPending` is set to true, the transaction in question has not been completed. Pending sales might include unpaid orders, estimates, tracked hours that have not yet been billed, or sales of back-ordered items. Within QuickBooks, you can change the `IsPending` status for a credit memo, for example, by choosing “Mark Credit `Memo` As Pending” or “Mark Credit `Memo` As Final” from the Edit menu. */
+    IsPending?: boolean;
+    /** Specifies the number of assemblies to be built. The transaction will fail if the number specified here exceeds the number of on-hand components. */
+    QuantityToBuild: number;
+    /** Indicates the number of this assembly that can be built from the parts on hand. */
+    QuantityCanBuild: number;
+    /** The number of these items in inventory. `QuantityOnHand` times `AverageCost` is `TotalValue` in an inventory item list. To change the `QuantityOnHand` for an item, you would have to use `InventoryAdjustmentAdd` not an `ItemInventoryMod`. */
+    QuantityOnHand: number;
+    /** The number of these items that have been sold (as recorded in sales orders) but not delivered to customers. */
+    QuantityOnSalesOrder: number;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** List of components in the assembly. */
+    ComponentItemLineRet?: ComponentItemLineRet | ComponentItemLineRet[];
+    /** 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 CardSecurityCodeMatch = "Fail" | "NotAvailable" | "Pass";
 export interface CashBackInfoAdd {
     /** The Account list is the company file’s list of accounts. An `AccountRef` aggregate refers to one of these accounts. (If an `AccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.) Special cases to note:In a Check message, `AccountRef` refers to the account from which the funds are being drawn for this check, for example, Checking or Savings.In an `ExpenseLineAdd` message, you must include `AccountRef` if the “Require accounts” check box is selected in the QuickBooks Accounting preferences. (It is selected by default.) In a `CreditCardCredit` message, `AccountRef` refers to the bank account or credit card account to which the credit is applied.In a `CreditCardCharge` message, `AccountRef` refers to the bank or credit card company to whom money is owed. How do you increase and decrease amounts in bank accounts? The following requests increase the balance in a bank account: Deposit Add `ReceivePaymentAdd` Journal Entry Add Sales `ReceiptAdd` The following requests decrease the balance in a bank account: `CheckAdd` Bill `PaymentCheckAdd` `JournalEntryAdd` */
@@ -1516,6 +1704,26 @@ export interface CompanyRet {
     /** 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 ComponentItemLineRet {
+    /** 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;
+    /** 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;
+    /** A descriptive text field. */
+    Desc?: string;
+    /** The number of these items in inventory. `QuantityOnHand` times `AverageCost` is `TotalValue` in an inventory item list. To change the `QuantityOnHand` for an item, you would have to use `InventoryAdjustmentAdd` not an `ItemInventoryMod`. */
+    QuantityOnHand?: number;
+    /** Indicates the number of the component part that is required in the assembly. For example, if the `ItemRef` in this component is a bolt, the quantity needed field indicates how many of these bolts are used in the assembly. */
+    QuantityNeeded?: number;
+}
 export interface Contacts {
     /** A formal reference, such as Mr. or Dr., that precedes a name. */
     Salutation?: string;
@@ -1960,6 +2168,12 @@ export interface CreditCardTxnInfo {
     /** This contains data returned in the QBMS transaction response. This information block should not be used in `CreditMemo` requests for QuickBooks 2007 and new versions. Instead, use the `ARRefundCreditCard` request. */
     CreditCardTxnResultInfo: CreditCardTxnResultInfo;
 }
+export interface CreditCardTxnInfoMod {
+    /** This contains data originally supplied in the QBMS transaction request. This information block should not be used in `CreditMemo` requests for QuickBooks 2007 and new versions. Instead, use the `ARRefundCreditCard` request. */
+    CreditCardTxnInputInfoMod?: CreditCardTxnInputInfoMod;
+    /** This contains data returned in the QBMS transaction response. This information block should not be used in `CreditMemo` requests for QuickBooks 2007 and new versions. Instead, use the `ARRefundCreditCard` request. */
+    CreditCardTxnResultInfoMod?: CreditCardTxnResultInfoMod;
+}
 export interface CreditCardTxnInputInfo {
     /** Credit-card number for this customer or this payment. Beginning with qbXML spec 6.0 and QuickBooks 2007, you must mask the credit card number with lower case “x” and no dashes. For example, xxxxxxxxxxxx1234. */
     CreditCardNumber: string;
@@ -1973,7 +2187,31 @@ export interface CreditCardTxnInputInfo {
     CreditCardAddress?: string;
     /** The postal code associated with the address for this credit card. */
     CreditCardPostalCode?: string;
-    /** This optional field is used only for Visa and Master Card commercial cards. There are three types of these cards: purchase, corporate, and business. Normally, special lower transaction fee rates apply when these cards are used and this field is filled out. If this field is left blank, then the usual (and higher) discount rate applies. */
+    /** This optional field is used only for Visa and Master Card commercial cards. There are three types of these cards: purchase, corporate, and business.
+  
+    Normally, special lower transaction fee rates apply when these cards are used and this field is filled out. If this field is left blank, then the usual (and higher) discount rate applies. */
+    CommercialCardCode?: string;
+    /** Indicates whether this transaction came from a card swipe (`tmCardPresent`) or not (`tmCardNotPresent`). */
+    TransactionMode?: TransactionMode;
+    /** Indicates the QBMS transaction from which the current transaction data originated, for example, Charge, Authorization, Capture, Refund, `VoiceAuthorization`, or Void. */
+    CreditCardTxnType?: CreditCardTxnType;
+}
+export interface CreditCardTxnInputInfoMod {
+    /** Credit-card number for this customer or this payment. Beginning with qbXML spec 6.0 and QuickBooks 2007, you must mask the credit card number with lower case “x” and no dashes. For example, xxxxxxxxxxxx1234. */
+    CreditCardNumber?: string;
+    /** The month when the credit card expires. */
+    ExpirationMonth?: number;
+    /** The year when the credit card expires. */
+    ExpirationYear?: number;
+    /** The name on the customer’s credit card. */
+    NameOnCard?: string;
+    /** The address associated with this credit card. */
+    CreditCardAddress?: string;
+    /** The postal code associated with the address for this credit card. */
+    CreditCardPostalCode?: string;
+    /** This optional field is used only for Visa and Master Card commercial cards. There are three types of these cards: purchase, corporate, and business.
+  
+    Normally, special lower transaction fee rates apply when these cards are used and this field is filled out. If this field is left blank, then the usual (and higher) discount rate applies. */
     CommercialCardCode?: string;
     /** Indicates whether this transaction came from a card swipe (`tmCardPresent`) or not (`tmCardNotPresent`). */
     TransactionMode?: TransactionMode;
@@ -1985,15 +2223,23 @@ export interface CreditCardTxnResultInfo {
     ResultCode: number;
     /** This contains the status message returned in the original QBMS transaction response. */
     ResultMessage: string;
-    /** This transaction ID is returned from the credit card processor. You should save this value for any possible QBMS SDK transaction requests that need it, for example, `CustomerCreditCardTxnVoidRq`, or `CustomerCreditCardCaptureRq`. You should also save this transaction ID and include it in the QB SDK `SalesReceiptAdd` or `ReceivePaymentAdd` requests if you are intending to save the transaction data in QuickBooks. */
+    /** This transaction ID is returned from the credit card processor. You should save this value for any possible QBMS SDK transaction requests that need it, for example, `CustomerCreditCardTxnVoidRq`, or `CustomerCreditCardCaptureRq`.
+  
+    You should also save this transaction ID and include it in the QB SDK `SalesReceiptAdd` or `ReceivePaymentAdd` requests if you are intending to save the transaction data in QuickBooks. */
     CreditCardTransID: string;
     /** This is the QBMS account number of the merchant who is running the transaction using the customer’s credit card. It is returned from the transaction request and should be stored for subsequent transactions, such as using it in the QB SDK `SalesReceiptAdd`, `ReceivePaymentAdd`, `ARRefundCreditCard` requests to save the transaction data in QuickBooks. */
     MerchantAccountNumber: string;
-    /** The authorization code is returned from the credit card processor to indicate that the charge will be paid by the card issuer. In a voice authorization request (`CustomerCreditCardVoiceAuthRq`), the authorization code is supplied by the card issuer over the telephone. */
+    /** The authorization code is returned from the credit card processor to indicate that the charge will be paid by the card issuer.
+  
+    In a voice authorization request (`CustomerCreditCardVoiceAuthRq`), the authorization code is supplied by the card issuer over the telephone. */
     AuthorizationCode?: string;
-    /** This field contains the value `avssPass` if the street address supplied in the transaction request matches the customer’s address on file at the card issuer. It contains the value `avssFail` if there is not a match, or `avssNotAvailable` if the card issuer does not support AVS. Note: This field was required in qbXML 4.1, but is optional in qbXML 5.0 and later. */
+    /** This field contains the value `avssPass` if the street address supplied in the transaction request matches the customer’s address on file at the card issuer. It contains the value `avssFail` if there is not a match, or `avssNotAvailable` if the card issuer does not support AVS.
+  
+    Note: This field was required in qbXML 4.1, but is optional in qbXML 5.0 and later. */
     AVSStreet?: AVSStreet;
-    /** This field contains the value `avszPass` if the customer postal ZIP code supplied in the transaction request matches the customer’s postal code recognized at the card issuer. It contains the value `avszFail` if there is not a match, or `avszNotAvailable` if the card issuer does not support AVS. Note: This field was required in qbXML 4.1, but is optional in qbXML 5.0 and later. */
+    /** This field contains the value `avszPass` if the customer postal ZIP code supplied in the transaction request matches the customer’s postal code recognized at the card issuer. It contains the value `avszFail` if there is not a match, or `avszNotAvailable` if the card issuer does not support AVS.
+  
+    Note: This field was required in qbXML 4.1, but is optional in qbXML 5.0 and later. */
     AVSZip?: AVSZip;
     /** This field contains the value Pass if the card security code supplied in the transaction request matches the card security code recognized for that credit card number at the card issuer. It contains the value Fail if there is not a match. */
     CardSecurityCodeMatch?: CardSecurityCodeMatch;
@@ -2010,6 +2256,44 @@ export interface CreditCardTxnResultInfo {
     /** This value is returned from QBMS transactions for future use by the QuickBooks Reconciliation feature. */
     ClientTransID?: string;
 }
+export interface CreditCardTxnResultInfoMod {
+    /** This contains the status code returned in the original QBMS transaction response. */
+    ResultCode?: number;
+    /** This contains the status message returned in the original QBMS transaction response. */
+    ResultMessage?: string;
+    /** This transaction ID is returned from the credit card processor. You should save this value for any possible QBMS SDK transaction requests that need it, for example, `CustomerCreditCardTxnVoidRq`, or `CustomerCreditCardCaptureRq`.
+  
+    You should also save this transaction ID and include it in the QB SDK `SalesReceiptAdd` or `ReceivePaymentAdd` requests if you are intending to save the transaction data in QuickBooks. */
+    CreditCardTransID?: string;
+    /** This is the QBMS account number of the merchant who is running the transaction using the customer’s credit card. It is returned from the transaction request and should be stored for subsequent transactions, such as using it in the QB SDK `SalesReceiptAdd`, `ReceivePaymentAdd`, `ARRefundCreditCard` requests to save the transaction data in QuickBooks. */
+    MerchantAccountNumber?: string;
+    /** The authorization code is returned from the credit card processor to indicate that the charge will be paid by the card issuer.
+  
+    In a voice authorization request (`CustomerCreditCardVoiceAuthRq`), the authorization code is supplied by the card issuer over the telephone. */
+    AuthorizationCode?: string;
+    /** This field contains the value `avssPass` if the street address supplied in the transaction request matches the customer’s address on file at the card issuer. It contains the value `avssFail` if there is not a match, or `avssNotAvailable` if the card issuer does not support AVS.
+  
+    Note: This field was required in qbXML 4.1, but is optional in qbXML 5.0 and later. */
+    AVSStreet?: AVSStreet;
+    /** This field contains the value `avszPass` if the customer postal ZIP code supplied in the transaction request matches the customer’s postal code recognized at the card issuer. It contains the value `avszFail` if there is not a match, or `avszNotAvailable` if the card issuer does not support AVS.
+  
+    Note: This field was required in qbXML 4.1, but is optional in qbXML 5.0 and later. */
+    AVSZip?: AVSZip;
+    /** This field contains the value Pass if the card security code supplied in the transaction request matches the card security code recognized for that credit card number at the card issuer. It contains the value Fail if there is not a match. */
+    CardSecurityCodeMatch?: CardSecurityCodeMatch;
+    /** This value is returned by QBMS from the transaction request, and is used internally by the QuickBooks/QBMS Recon (reconcile) feature. You should save this value without modification and include it in the QB SDK `SalesReceiptAdd` or `ReceivePaymentAdd` requests if you want to save the transaction data in QuickBooks. */
+    ReconBatchID?: string;
+    /** Internal code needed for the QuickBooks reconciliation feature, if integrating with QuickBooks. This value is returned in the QBMS response to a QBMS transaction request, and must be subsequently supplied by your application in the QB SDK `ReceivePaymentAdd` or `SalesReceiptAdd` request. */
+    PaymentGroupingCode?: number;
+    /** Indicates whether the transaction is known to have been successfully processed by the card issuer, with the value “`psCompleted`” indicating success. That is, there was a response sent to QBMS and from QBMS to the application indicating success. The value “`psUnknown`” indicates that such a response was not received. If “Unknown” is returned, the transaction may have been successfully or unsuccessfully processed at the card issuer: there simply was no response (possibly due to network errors). */
+    PaymentStatus?: PaymentStatus;
+    /** Timestamp indicating the time in which the card processor authorized the transaction. */
+    TxnAuthorizationTime?: string;
+    /** This value is used to support the credit card transaction Reconcile feature within QuickBooks. */
+    TxnAuthorizationStamp?: number;
+    /** This value is returned from QBMS transactions for future use by the QuickBooks Reconciliation feature. */
+    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`.
@@ -2025,6 +2309,48 @@ export interface CurrencyRef {
     /** `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;
@@ -2468,26 +2794,72 @@ export interface CustomerTypeRet {
     /** The number of ancestors. For example, The customer job with `Name` = carpets and `FullName` = Jones:Building2:carpets would have a sublevel of 2. */
     Sublevel: number;
 }
-export interface DataExt {
-    /** `OwnerID` refers to the owner of a data extension, and must be 0 or a valid GUID. (Custom fields, which are visible in the QuickBooks UI, always have an `OwnerID` of 0. )
-  
-    Usually you would keep your application’s GUID confidential to prevent other applications from accessing your data extensions. But if you want to share data extensions with another application, the applications need to use the same GUID. In this case, each application could use two GUIDs, one for shared data extensions and one for confidential data extensions. (An application can have any number of GUIDs.)
-  
-    When you share a 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;
-    /** The name of the data extension. If this is a custom field, `DataExtName` will be visible as a label in the QuickBooks user interface. Also because `OwnerID` and `DataExtName` together make the data extension unique, and because custom fields all have the same `OwnerID` of zero, the `DataExtName` must be a unique value among existing custom fields. In contrast, the `DataExtName` for private data extensions must be unique only for the specified `OwnerID` GUID. */
-    DataExtName: string;
-    /** The data in this field. The maximum length of `DataExtValue` will depend on the `DataExtType` of this data extension. For example, if `DataExtType` is `STR255TYPE`, the maximum length of `DataExtValue` is 255 characters. If `DataExtType` is `STR1024TYPE`, the maximum size of `DataExtValue` is `1KB`. */
-    DataExtValue: string;
-}
-export interface DataExtRet {
-    /** `OwnerID` refers to the owner of a data extension, and must be 0 or a valid GUID. (Custom fields, which are visible in the QuickBooks UI, always have an `OwnerID` of 0. )
-  
-    Usually you would keep your application’s GUID confidential to prevent other applications from accessing your data extensions. But if you want to share data extensions with another application, the applications need to use the same GUID. In this case, each application could use two GUIDs, one for shared data extensions and one for confidential data extensions. (An application can have any number of GUIDs.)
-  
-    When you share a 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;
-    /** The name of the data extension. If this is a custom field, `DataExtName` will be visible as a label in the QuickBooks user interface. Also because `OwnerID` and `DataExtName` together make the data extension unique, and because custom fields all have the same `OwnerID` of zero, the `DataExtName` must be a unique value among existing custom fields. In contrast, the `DataExtName` for private data extensions must be unique only for the specified `OwnerID` GUID. */
+export interface CustomSummaryReportQueryRq {
+    /** The type of report being queried. */
+    CustomSummaryReportType: CustomSummaryReportType;
+    /** 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;
+    /** `SummarizeColumnsBy` determines which data the report calculates and how the columns will be labeled across the top of the report. For example, if you set the value to `scbTwoWeek`, the report’s column labels might be “Feb 10-23, 02,” “Feb 24-Mar9, 02,” and so on. */
+    SummarizeColumnsBy: SummarizeColumnsBy;
+    /** `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;
+    /** The default value is false, which means that the report will not include any subcolumn information. To include all available types of subcolumns for this report, set `IncludeSubcolumns` to true. The SDK will not return subcolumn information for data that can be easily computed. (For example, the SDK does not return the “percent of row” column.) */
+    IncludeSubcolumns?: boolean;
+    /** Specifies the type of year that will be used for this report. */
+    ReportCalendar?: ReportCalendar;
+    /** Specifies whether you want the report to include only rows with active information, only rows with nonzero values, or all rows regardless of their content or active status. */
+    ReturnRows?: ReturnRows;
+    /** Specifies whether you want the report to include only columns with active information, only columns with nonzero values, or all columns regardless of their content or active status. */
+    ReturnColumns?: ReturnColumns;
+    /** 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 CustomSummaryReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type CustomSummaryReportType = "CustomSummary";
+export interface DataExt {
+    /** `OwnerID` refers to the owner of a data extension, and must be 0 or a valid GUID. (Custom fields, which are visible in the QuickBooks UI, always have an `OwnerID` of 0. )
+  
+    Usually you would keep your application’s GUID confidential to prevent other applications from accessing your data extensions. But if you want to share data extensions with another application, the applications need to use the same GUID. In this case, each application could use two GUIDs, one for shared data extensions and one for confidential data extensions. (An application can have any number of GUIDs.)
+  
+    When you share a 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;
+    /** The name of the data extension. If this is a custom field, `DataExtName` will be visible as a label in the QuickBooks user interface. Also because `OwnerID` and `DataExtName` together make the data extension unique, and because custom fields all have the same `OwnerID` of zero, the `DataExtName` must be a unique value among existing custom fields. In contrast, the `DataExtName` for private data extensions must be unique only for the specified `OwnerID` GUID. */
+    DataExtName: string;
+    /** The data in this field. The maximum length of `DataExtValue` will depend on the `DataExtType` of this data extension. For example, if `DataExtType` is `STR255TYPE`, the maximum length of `DataExtValue` is 255 characters. If `DataExtType` is `STR1024TYPE`, the maximum size of `DataExtValue` is `1KB`. */
+    DataExtValue: string;
+}
+export interface DataExtRet {
+    /** `OwnerID` refers to the owner of a data extension, and must be 0 or a valid GUID. (Custom fields, which are visible in the QuickBooks UI, always have an `OwnerID` of 0. )
+  
+    Usually you would keep your application’s GUID confidential to prevent other applications from accessing your data extensions. But if you want to share data extensions with another application, the applications need to use the same GUID. In this case, each application could use two GUIDs, one for shared data extensions and one for confidential data extensions. (An application can have any number of GUIDs.)
+  
+    When you share a 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;
+    /** The name of the data extension. If this is a custom field, `DataExtName` will be visible as a label in the QuickBooks user interface. Also because `OwnerID` and `DataExtName` together make the data extension unique, and because custom fields all have the same `OwnerID` of zero, the `DataExtName` must be a unique value among existing custom fields. In contrast, the `DataExtName` for private data extensions must be unique only for the specified `OwnerID` GUID. */
     DataExtName: string;
     /** The field’s data type, which corresponds to a qbXML data type. In an `IDataExtDefAdd` request object, if this is a custom field, `DataExtType` must be `detSTR255TYPE`. */
     DataExtType: DataExtType;
@@ -3922,7 +4294,107 @@ export interface FixedAssetSalesInfoMod {
     /** Any expenses that were incurred during the sale of a fixed asset. */
     SalesExpense?: string;
 }
+export interface FromInventorySiteLocationRef {
+    /** 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 FromInventorySiteRef {
+    /** 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 type Gender = "Female" | "Male";
+export interface GeneralDetailReportQueryRq {
+    /** The type of general detail report to return. (If you specify `gdrtMissingChecks`, you must also specify an account type in the account filter.) */
+    GeneralDetailReportType: GeneralDetailReportType;
+    /** 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 GeneralDetailReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type GeneralDetailReportType = "1099Detail" | "AuditTrail" | "BalanceSheetDetail" | "CheckDetail" | "CustomerBalanceDetail" | "DepositDetail" | "EstimatesByJob" | "ExpenseByVendorDetail" | "GeneralLedger" | "IncomeByCustomerDetail" | "IncomeTaxDetail" | "InventoryValuationDetail" | "JobProgressInvoicesVsEstimates" | "Journal" | "MissingChecks" | "OpenInvoices" | "OpenPOs" | "OpenPOsByJob" | "OpenSalesOrderByCustomer" | "OpenSalesOrderByItem" | "PendingSales" | "ProfitAndLossDetail" | "PurchaseByItemDetail" | "PurchaseByVendorDetail" | "SalesByCustomerDetail" | "SalesByItemDetail" | "SalesByRepDetail" | "TxnDetailByAccount" | "TxnListByCustomer" | "TxnListByDate" | "TxnListByVendor" | "UnbilledCostsByJob" | "UnpaidBillsDetail" | "VendorBalanceDetail";
+export interface GeneralSummaryReportQueryRq {
+    /** The type of general summary report being queried. The report types listed below map almost directly to named reports in QuickBooks. */
+    GeneralSummaryReportType: GeneralSummaryReportType;
+    /** 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;
+    /** `SummarizeColumnsBy` determines which data the report calculates and how the columns will be labeled across the top of the report. For example, if you set the value to `scbTwoWeek`, the report’s column labels might be “Feb 10-23, 02,” “Feb 24-Mar9, 02,” and so on. */
+    SummarizeColumnsBy?: SummarizeColumnsBy;
+    /** The default value is false, which means that the report will not include any subcolumn information. To include all available types of subcolumns for this report, set `IncludeSubcolumns` to true. The SDK will not return subcolumn information for data that can be easily computed. (For example, the SDK does not return the “percent of row” column.) */
+    IncludeSubcolumns?: boolean;
+    /** Specifies the type of year that will be used for this report. */
+    ReportCalendar?: ReportCalendar;
+    /** Specifies whether you want the report to include only rows with active information, only rows with nonzero values, or all rows regardless of their content or active status. */
+    ReturnRows?: ReturnRows;
+    /** Specifies whether you want the report to include only columns with active information, only columns with nonzero values, or all columns regardless of their content or active status. */
+    ReturnColumns?: ReturnColumns;
+    /** 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 GeneralSummaryReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type GeneralSummaryReportType = "BalanceSheetByClass" | "BalanceSheetPrevYearComp" | "BalanceSheetStandard" | "BalanceSheetSummary" | "CustomerBalanceSummary" | "ExpenseByVendorSummary" | "IncomeByCustomerSummary" | "IncomeTaxSummary" | "InventoryStockStatusByItem" | "InventoryStockStatusByVendor" | "InventoryValuationSummary" | "InventoryValuationSummaryBySite" | "LotNumberInStockBySite" | "PhysicalInventoryWorksheet" | "ProfitAndLossByClass" | "ProfitAndLossByJob" | "ProfitAndLossPrevYearComp" | "ProfitAndLossStandard" | "ProfitAndLossYTDComp" | "PurchaseByItemSummary" | "PurchaseByVendorSummary" | "SalesByCustomerSummary" | "SalesByItemSummary" | "SalesByRepSummary" | "SalesTaxLiability" | "SalesTaxRevenueSummary" | "SerialNumberInStockBySite" | "TrialBalance" | "VendorBalanceSummary";
+export type IncludeAccounts = "All" | "InUse";
+export type IncludeColumn = "Account" | "Aging" | "Amount" | "AmountDifference" | "AverageCost" | "BilledDate" | "BillingStatus" | "CalculatedAmount" | "Class" | "ClearedStatus" | "CostPrice" | "Credit" | "Currency" | "Date" | "Debit" | "DeliveryDate" | "DueDate" | "EstimateActive" | "ExchangeRate" | "FOB" | "IncomeSubjectToTax" | "Invoiced" | "Item" | "ItemDesc" | "LastModifiedBy" | "LatestOrPriorState" | "Memo" | "ModifiedTime" | "Name" | "NameAccountNumber" | "NameAddress" | "NameCity" | "NameContact" | "NameEmail" | "NameFax" | "NamePhone" | "NameState" | "NameZip" | "OpenBalance" | "OriginalAmount" | "PaidAmount" | "PaidStatus" | "PaidThroughDate" | "PaymentMethod" | "PayrollItem" | "PONumber" | "PrintStatus" | "ProgressAmount" | "ProgressPercent" | "Quantity" | "QuantityAvailable" | "QuantityOnHand" | "QuantityOnSalesOrder" | "ReceivedQuantity" | "RefNumber" | "RunningBalance" | "SalesRep" | "SalesTaxCode" | "SerialOrLotNumber" | "ShipDate" | "ShipMethod" | "SourceName" | "SplitAccount" | "SSNOrTaxID" | "TaxLine" | "TaxTableVersion" | "Terms" | "TxnID" | "TxnNumber" | "TxnType" | "UnitPrice" | "UserEdit" | "ValueOnHand" | "WageBase" | "WageBaseTips";
 export interface IncomeAccountRef {
     /** 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;
@@ -5601,6 +6073,12 @@ export interface ItemInventoryAssemblyQueryRq {
 export interface ItemInventoryAssemblyQueryRs {
     ItemInventoryAssemblyRet: ItemInventoryAssemblyRet[];
 }
+export interface ItemInventoryAssemblyRef {
+    /** 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 ItemInventoryAssemblyRet {
     /** 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;
@@ -7444,12 +7922,92 @@ export interface PaymentMethodRef {
 }
 export type PaymentStatus = "Completed" | "Unknown";
 export type PayPeriod = "Biweekly" | "Daily" | "Monthly" | "Quarterly" | "Semimonthly" | "Weekly" | "Yearly";
+export interface PayrollDetailReportQueryRq {
+    /** The type of report: `pdrtEmployeeStateTaxesDetail` lists state taxes withheld for `employeespdrtPayrollItemDetail` lists the payroll transactions on which each payroll item `appearspdrtPayrollReviewDetail` gives detailed information about how QuickBooks calculates tax amounts on employee paychecks and in year-to-date `transactionspdrtPayrollTransactionDetail` shows the line-item detail that appears on each payroll `transactionpdrtPayrollTransactionsByPayee` lists payroll transactions, grouping them by payee */
+    PayrollDetailReportType: PayrollDetailReportType;
+    /** 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;
+    /** 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;
+}
+export interface PayrollDetailReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type PayrollDetailReportType = "EmployeeStateTaxesDetail" | "PayrollItemDetail" | "PayrollReviewDetail" | "PayrollTransactionDetail" | "PayrollTransactionsByPayee";
 export interface PayrollItemWageRef {
     /** 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 PayrollSummaryReportQueryRq {
+    /** The type of payroll report: `psrtEmployeeEarningsSummary` This report shows information similar to the payroll summary report, but in a different layout. The report has a row for each employee and a column for each payroll item. `psrtPayrollLiabilityBalances` This report lists the payroll liabilities the QuickBooks company owes to various agencies, such as the federal government, your state government, insurance plan administrators, labor unions, etc. The report covers unpaid liabilities incurred during the period of time shown in the From and To fields. If the company paid a liability incurred within the date range of the report, the report omits that liability, even if the payment occurred after the ending date of the report. `psrtPayrollSummary` This report shows the total wages, taxes withheld, deductions from net pay, additions to net pay, and employer-paid taxes and contributions for each employee on the payroll. */
+    PayrollSummaryReportType: PayrollSummaryReportType;
+    /** 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;
+    /** 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;
+    /** `SummarizeColumnsBy` determines which data the report calculates and how the columns will be labeled across the top of the report. For example, if you set the value to `scbTwoWeek`, the report’s column labels might be “Feb 10-23, 02,” “Feb 24-Mar9, 02,” and so on. */
+    SummarizeColumnsBy?: SummarizeColumnsBy;
+    /** The default value is false, which means that the report will not include any subcolumn information. To include all available types of subcolumns for this report, set `IncludeSubcolumns` to true. The SDK will not return subcolumn information for data that can be easily computed. (For example, the SDK does not return the “percent of row” column.) */
+    IncludeSubcolumns?: boolean;
+    /** Specifies the type of year that will be used for this report. */
+    ReportCalendar?: ReportCalendar;
+    /** Specifies whether you want the report to include only rows with active information, only rows with nonzero values, or all rows regardless of their content or active status. */
+    ReturnRows?: ReturnRows;
+    /** Specifies whether you want the report to include only columns with active information, only columns with nonzero values, or all columns regardless of their content or active status. */
+    ReturnColumns?: ReturnColumns;
+}
+export interface PayrollSummaryReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type PayrollSummaryReportType = "EmployeeEarningsSummary" | "PayrollLiabilityBalances" | "PayrollSummary";
+/** @default: All */
+export type PendingStatus = "All" | "NotPendingOnly" | "PendingOnly";
 /** @default: None */
 export type PreferredDeliveryMethod = "Email" | "Fax" | "None";
 export interface PreferredPaymentMethodRef {
@@ -8043,26 +8601,213 @@ export interface RateHistory {
     /** Specifies the date at which the workers’ comp code and it’s related premium goes into effect. */
     EffectiveDate: string;
 }
-export interface RefNumberFilter {
-    /** The criterion to match. */
-    MatchCriterion: MatchCriterion;
+export interface ReceivePaymentAdd {
+    /** 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;
+    /** 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;
+    /** 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;
+    /** Total amount of money received. For `ReceivePaymentAdd`, the sum of the `PaymentAmount` amounts (in the `AppliedToTxnAdd` aggregates that are included) cannot be greater than the `TotalAmount`, or you will receive an error. */
+    TotalAmount?: 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;
+    /** A customer’s payment method, for example, cash, check, or Master Card. A `PaymentMethodRef` aggregate refers to an item on the `PaymentMethod` list. In a request, if a `PaymentMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. In a `SalesReceiptAdd`, `ReceivePaymentAdd`, or `ARRefundCreditCard` request that contains credit card transaction data supplied from QBMS transaction responses, you must specify the payment method, and the payment method must be a credit card type. */
+    PaymentMethodRef?: PaymentMethodRef;
+    /** The beginning of this memo will appear in reports that show details of this receive payment. */
+    Memo?: string;
+    /** Refers to the account where these funds will be (or have been) deposited. In a `ReceivePaymentAdd` request, the default is Undeposited Funds if this is not included in the request. In a request, if a `DepositToAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    DepositToAccountRef?: DepositToAccountRef;
+    /** 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;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** If `IsAutoApply` is true, QuickBooks applies `TotalAmount` to any outstanding transaction that exactly matches `TotalAmount`. If no exact match is found, the payment is applied to the customer job’s outstanding transactions, beginning with the oldest one.If `IsAutoApply` is false, QuickBooks receives the payment but does not apply it to any outstanding transaction. Instead, the amount will appear as a credit on the customer job’s next transaction. */
+    IsAutoApply?: boolean;
+    /** `AppliedToTxn` List A list of `AppliedToTxn` aggregates. */
+    AppliedToTxnAdd?: AppliedToTxnAdd | AppliedToTxnAdd[];
+}
+export interface ReceivePaymentAddRq {
+    ReceivePaymentAdd: ReceivePaymentAdd;
+    /** 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 ReceivePaymentAddRs {
+    ReceivePaymentRet?: ReceivePaymentRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface ReceivePaymentMod {
+    /** 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;
+    /** 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;
+    /** 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;
+    RefNumber?: string;
+    /** Total amount of money received. For `ReceivePaymentAdd`, the sum of the `PaymentAmount` amounts (in the `AppliedToTxnAdd` aggregates that are included) cannot be greater than the `TotalAmount`, or you will receive an error. */
+    TotalAmount?: 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;
+    /** A customer’s payment method, for example, cash, check, or Master Card. A `PaymentMethodRef` aggregate refers to an item on the `PaymentMethod` list. In a request, if a `PaymentMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    In a `SalesReceiptAdd`, `ReceivePaymentAdd`, or `ARRefundCreditCard` request that contains credit card transaction data supplied from QBMS transaction responses, you must specify the payment method, and the payment method must be a credit card type. */
+    PaymentMethodRef?: PaymentMethodRef;
+    /** The beginning of this memo will appear in reports that show details of this receive payment. */
+    Memo?: string;
+    /** Refers to the account where these funds will be (or have been) deposited. In a `ReceivePaymentAdd` request, the default is Undeposited Funds if this is not included in the request. In a request, if a `DepositToAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    DepositToAccountRef?: DepositToAccountRef;
+    /** 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. */
+    CreditCardTxnInfoMod?: CreditCardTxnInfoMod;
+    /** `AppliedToTxn` List
+  
+    A list of `AppliedToTxn` aggregates. */
+    AppliedToTxnMod?: AppliedToTxnMod | AppliedToTxnMod[];
 }
-export interface RefNumberRangeFilter {
-    /** The first `RefNumber` in the search range. If `FromRefNumber` is omitted, the range will begin with first number on the list. */
-    FromRefNumber?: string;
-    /** The final `RefNumber` in the search range. If `ToRefNumber` is omitted, the range will end with last number on the list. */
-    ToRefNumber?: string;
+export interface ReceivePaymentModRq {
+    ReceivePaymentMod: ReceivePaymentMod;
+    /** 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 type Relation = "Brother" | "Daughter" | "Father" | "Friend" | "Mother" | "Other" | "Partner" | "Sister" | "Son" | "Spouse";
-export interface ReportAccountFilter {
-    /** Allows you to report on a specific account type. */
-    AccountTypeFilter?: AccountTypeFilter;
+export interface ReceivePaymentModRs {
+    ReceivePaymentRet?: ReceivePaymentRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface ReceivePaymentQueryRq {
+    /** 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;
+    /** 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 ReceivePaymentQueryRs {
+    ReceivePaymentRet: ReceivePaymentRet[];
+}
+export interface ReceivePaymentRet {
+    /** 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;
+    /** 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;
+    /** 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;
+    /** Total amount of money received. For `ReceivePaymentAdd`, the sum of the `PaymentAmount` amounts (in the `AppliedToTxnAdd` aggregates that are included) cannot be greater than the `TotalAmount`, or you will receive an error. */
+    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;
+    /** A customer’s payment method, for example, cash, check, or Master Card. A `PaymentMethodRef` aggregate refers to an item on the `PaymentMethod` list. In a request, if a `PaymentMethodRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored.
+  
+    In a `SalesReceiptAdd`, `ReceivePaymentAdd`, or `ARRefundCreditCard` request that contains credit card transaction data supplied from QBMS transaction responses, you must specify the payment method, and the payment method must be a credit card type. */
+    PaymentMethodRef?: PaymentMethodRef;
+    /** The beginning of this memo will appear in reports that show details of this receive payment. */
+    Memo?: string;
+    /** Refers to the account where these funds will be (or have been) deposited. In a `ReceivePaymentAdd` request, the default is Undeposited Funds if this is not included in the request. In a request, if a `DepositToAccountRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
+    DepositToAccountRef?: DepositToAccountRef;
+    /** 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;
+    /** `ReceivePaymentRet` will include an unused payment in cases such as these: The sum of the `PaymentAmount` amounts is less than `TotalAmount`. A payment is received for the exact amount of an invoice, but a credit or a discount (or both) are set. */
+    UnusedPayment?: string;
+    /** `ReceivePaymentRet` will include an unused credit if the `AppliedAmount` of a `SetCredit` aggregate is less than the amount of credit available for the specified `CreditTxnID`. */
+    UnusedCredits?: string;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** `AppliedToTxn` List
+  
+    A list of `AppliedToTxn` aggregates. */
+    AppliedToTxnRet?: AppliedToTxnRet | AppliedToTxnRet[];
+    /** 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 RefNumberFilter {
+    /** The criterion to match. */
+    MatchCriterion: MatchCriterion;
+    /** 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;
+}
+export interface RefNumberRangeFilter {
+    /** The first `RefNumber` in the search range. If `FromRefNumber` is omitted, the range will begin with first number on the list. */
+    FromRefNumber?: string;
+    /** The final `RefNumber` in the search range. If `ToRefNumber` is omitted, the range will end with last number on the list. */
+    ToRefNumber?: string;
+}
+export type Relation = "Brother" | "Daughter" | "Father" | "Friend" | "Mother" | "Other" | "Partner" | "Sister" | "Son" | "Spouse";
+export interface ReportAccountFilter {
+    /** Allows you to report on a specific account type. */
+    AccountTypeFilter?: AccountTypeFilter;
     /** 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. */
@@ -8074,6 +8819,7 @@ export interface ReportAccountFilter {
 }
 /** @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;
@@ -8130,6 +8876,8 @@ export interface ReportModifiedDateRangeFilter {
     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;
@@ -8159,6 +8907,8 @@ 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;
@@ -8934,6 +9684,12 @@ export interface SiteAddressBlock {
     /** The fifth line of an address (if a fifth line is needed). */
     Addr5?: string;
 }
+export interface SiteFilter {
+    /** 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 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 {
@@ -8946,7 +9702,10 @@ export interface SubtotalRow {
     /** A list of `IColData` objects, each of which describes the data in one cell of the report. */
     ColData?: ColData | ColData[];
 }
+export type SummarizeBudgetColumnsBy = "Class" | "Customer" | "Date";
+export type SummarizeBudgetRowsBy = "Account" | "Class" | "Customer";
 export type SummarizeColumnsBy = "Account" | "BalanceSheet" | "Class" | "Customer" | "CustomerType" | "Day" | "Employee" | "FourWeek" | "HalfMonth" | "IncomeStatement" | "ItemDetail" | "ItemType" | "Month" | "Payee" | "PaymentMethod" | "PayrollItemDetail" | "PayrollYtdDetail" | "Quarter" | "SalesRep" | "SalesTaxCode" | "ShipMethod" | "Terms" | "TotalOnly" | "TwoWeek" | "Vendor" | "VendorType" | "Week" | "Year";
+export type SummarizeRowsBy = "Account" | "BalanceSheet" | "Class" | "Customer" | "CustomerType" | "Day" | "Employee" | "FourWeek" | "HalfMonth" | "IncomeStatement" | "ItemDetail" | "ItemType" | "Month" | "Payee" | "PaymentMethod" | "PayrollItemDetail" | "PayrollYtdDetail" | "Quarter" | "SalesRep" | "SalesTaxCode" | "ShipMethod" | "TaxLine" | "Terms" | "TotalOnly" | "TwoWeek" | "Vendor" | "VendorType" | "Week" | "Year";
 export interface SupervisorRef {
     /** 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;
@@ -8996,6 +9755,38 @@ export interface TextRow {
     /** The data in this cell of the report. */
     Value: string;
 }
+export interface TimeReportQueryRq {
+    /** Allows you to report on time that has been recorded in a particular category. */
+    TimeReportType: TimeReportType;
+    /** 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 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;
+    /** `SummarizeColumnsBy` determines which data the report calculates and how the columns will be labeled across the top of the report. For example, if you set the value to `scbTwoWeek`, the report’s column labels might be “Feb 10-23, 02,” “Feb 24-Mar9, 02,” and so on. */
+    SummarizeColumnsBy?: SummarizeColumnsBy;
+    /** 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[];
+    /** The default value is false, which means that the report will not include any subcolumn information. To include all available types of subcolumns for this report, set `IncludeSubcolumns` to true. The SDK will not return subcolumn information for data that can be easily computed. (For example, the SDK does not return the “percent of row” column.) */
+    IncludeSubcolumns?: boolean;
+    /** Specifies the type of year that will be used for this report. */
+    ReportCalendar?: ReportCalendar;
+    /** Specifies whether you want the report to include only rows with active information, only rows with nonzero values, or all rows regardless of their content or active status. */
+    ReturnRows?: ReturnRows;
+    /** Specifies whether you want the report to include only columns with active information, only columns with nonzero values, or all columns regardless of their content or active status. */
+    ReturnColumns?: ReturnColumns;
+}
+export interface TimeReportQueryRs {
+    ReportRet: ReportRet[];
+}
+export type TimeReportType = "TimeByItem" | "TimeByJobDetail" | "TimeByJobSummary" | "TimeByName";
 export interface TimeTrackingAdd {
     /** 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;
@@ -9121,6 +9912,18 @@ export interface TimeTrackingRet {
     /** If `IsBilled` is true, the tracked time has already been billed. */
     IsBilled?: boolean;
 }
+export interface ToInventorySiteLocationRef {
+    /** 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 ToInventorySiteRef {
+    /** 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 TotalBalanceFilter {
     /** Indicates whether to filter for amounts that are less than, equal to or less than, exactly equal to, greater than, or equal to or greater than the given `Amount`. */
     Operator: Operator;
@@ -9135,6 +9938,266 @@ export interface TotalRow {
 }
 /** @default: CardNotPresent */
 export type TransactionMode = "CardNotPresent" | "CardPresent";
+export interface TransferAdd {
+    /** 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;
+    /** Account that money will be transferred from. */
+    TransferFromAccountRef?: TransferFromAccountRef;
+    /** Account that money will be transferred to. */
+    TransferToAccountRef?: TransferToAccountRef;
+    /** 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;
+    /** Additional information. */
+    Memo?: string;
+}
+export interface TransferAddRq {
+    TransferAdd: TransferAdd;
+    /** 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 TransferAddRs {
+    TransferRet?: TransferRet;
+}
+export interface TransferFromAccountRef {
+    /** 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 TransferInventoryAdd {
+    /** 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;
+    /** Inventory site that transfer will be taken from. */
+    FromInventorySiteRef: FromInventorySiteRef;
+    /** Inventory site that transfer will be sent to. */
+    ToInventorySiteRef: ToInventorySiteRef;
+    /** Additional information. */
+    Memo?: string;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** List of lines for inventory transfers. */
+    TransferInventoryLineAdd?: TransferInventoryLineAdd | TransferInventoryLineAdd[];
+}
+export interface TransferInventoryAddRq {
+    TransferInventoryAdd: TransferInventoryAdd;
+    /** 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 TransferInventoryAddRs {
+    TransferInventoryRet?: TransferInventoryRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface TransferInventoryLineAdd {
+    /** 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;
+    /** Location within the inventory site that transfer will be taken from. */
+    FromInventorySiteLocationRef?: FromInventorySiteLocationRef;
+    /** Location within the inventory site that transfer will be sent to. */
+    ToInventorySiteLocationRef?: ToInventorySiteLocationRef;
+    /** Quantity of items transferred. */
+    QuantityToTransfer?: number;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+}
+export interface TransferInventoryLineMod {
+    /** 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;
+    /** Location within the inventory site that transfer will be taken from. */
+    FromInventorySiteLocationRef?: FromInventorySiteLocationRef;
+    /** Location within the inventory site that transfer will be sent to. */
+    ToInventorySiteLocationRef?: ToInventorySiteLocationRef;
+    /** Quantity of items transferred. */
+    QuantityToTransfer?: number;
+    /** The serial number of the asset. */
+    SerialNumber?: string;
+    /** The lot number of the asset. */
+    LotNumber?: string;
+}
+export interface TransferInventoryLineRet {
+    /** 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;
+    /** Location within the inventory site that transfer will be taken from. */
+    FromInventorySiteLocationRef?: FromInventorySiteLocationRef;
+    /** Location within the inventory site that transfer will be sent to. */
+    ToInventorySiteLocationRef?: ToInventorySiteLocationRef;
+    /** Quantity of items transferred. */
+    QuantityTransferred?: number;
+    /** 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;
+}
+export interface TransferInventoryMod {
+    /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** The date of the transaction. In some cases, if you leave `TxnDate` out of an -Add message, QuickBooks will prefill `TxnDate` with the date of the last-saved transaction of the same type. */
+    TxnDate?: string;
+    /** 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;
+    /** Inventory site that transfer will be taken from. */
+    FromInventorySiteRef?: FromInventorySiteRef;
+    /** Inventory site that transfer will be sent to. */
+    ToInventorySiteRef?: ToInventorySiteRef;
+    /** Additional information. */
+    Memo?: string;
+    /** List of lines for inventory transfers. */
+    TransferInventoryLineMod?: TransferInventoryLineMod | TransferInventoryLineMod[];
+}
+export interface TransferInventoryModRq {
+    TransferInventoryMod: TransferInventoryMod;
+    /** 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 TransferInventoryModRs {
+    TransferInventoryRet?: TransferInventoryRet;
+    ErrorRecovery?: ErrorRecovery;
+}
+export interface TransferInventoryQueryRq {
+    /** 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;
+    /** Allows you to report on Sites. */
+    SiteFilter?: SiteFilter;
+    /** This filter allows you to omit line items from a query response to get a smaller result. The default value is false, so line items are omitted by default. Set `IncludeLineItems` to true to include line items in the response if you don’t mind getting a larger result. */
+    IncludeLineItems?: boolean;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface TransferInventoryQueryRs {
+    TransferInventoryRet: TransferInventoryRet[];
+}
+export interface TransferInventoryRet {
+    /** 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 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;
+    /** Inventory site that transfer will be taken from. */
+    FromInventorySiteRef?: FromInventorySiteRef;
+    /** Inventory site that transfer will be sent to. */
+    ToInventorySiteRef?: ToInventorySiteRef;
+    /** Additional information. */
+    Memo?: string;
+    /** Allows for the attachment of a user defined GUID value. */
+    ExternalGUID?: string;
+    /** List of lines for inventory transfers. */
+    TransferInventoryLineRet?: TransferInventoryLineRet | TransferInventoryLineRet[];
+}
+export interface TransferMod {
+    /** QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. A `TxnID` returned from a request can be used to refer to the transaction in subsequent requests. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQueryRq` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID: string;
+    /** A number that the server generates and assigns to this object. Every time the object is changed, the server will change its `EditSequence` value. When you try to modify a list object, you must provide its `EditSequence`. The server compares the `EditSequence` you provide with the `EditSequence` in memory to make sure you are dealing with the latest copy of the object. If you are not, the server will reject the request and return an error. Because `EditSequence` is only used to check whether two objects match, there is no reason to interpret its value. */
+    EditSequence: string;
+    /** The date of the transaction. In some cases, if you leave `TxnDate` out of an -Add message, QuickBooks will prefill `TxnDate` with the date of the last-saved transaction of the same type. */
+    TxnDate?: string;
+    /** Account that money will be transferred from. */
+    TransferFromAccountRef?: TransferFromAccountRef;
+    /** Account that money will be transferred to. */
+    TransferToAccountRef?: TransferToAccountRef;
+    /** 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;
+    /** Additional information. */
+    Memo?: string;
+}
+export interface TransferModRq {
+    TransferMod: TransferMod;
+    /** 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 TransferModRs {
+    TransferRet?: TransferRet;
+}
+export interface TransferQueryRq {
+    /** One or more `TxnID` values. QuickBooks generates a unique `TxnID` for each transaction that is added to QuickBooks. Notice that you cannot supply the `TxnID` of a `TimeTracking` transaction to `TransactionQuery` requests. If you do, you get an error stating that no such record could be found, even though the transaction is in QuickBooks. This behavior reflects the behavior in the QuicKBooks UI in the Find window. */
+    TxnID?: string[] | string;
+    /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
+    MaxReturned?: number;
+    /** Filters according to the dates when transactions were last modified. The `ModifiedDateRangeFilter` aggregate is not required to contain any elements, but if it is empty, we recommend that you leave it out altogether. Note that the time portion of the `FromModifiedDate` and `ToModifiedDate` fields was not supported in qbXML version 1.0 or 1.1. (To filter according to the dates when transactions were deleted, use a `TxnDeletedQuery` message.) */
+    ModifiedDateRangeFilter?: ModifiedDateRangeFilter;
+    /** Filters according to the original transaction dates. */
+    TxnDateRangeFilter?: TxnDateRangeFilter;
+    /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
+    IncludeRetElement?: string[] | string;
+}
+export interface TransferQueryRs {
+    TransferRet: TransferRet[];
+}
+export interface TransferRet {
+    /** 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 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;
+    /** Account that money will be transferred from. */
+    TransferFromAccountRef?: TransferFromAccountRef;
+    /** Balance for the from account. */
+    FromAccountBalance?: string;
+    /** Account that money will be transferred to. */
+    TransferToAccountRef?: TransferToAccountRef;
+    /** Balance for the to account. */
+    ToAccountBalance?: 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;
+    /** Additional information. */
+    Memo?: string;
+}
+export interface TransferToAccountRef {
+    /** 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 TxnDateRangeFilter {
     /** Selects transactions created on or after this date. Both `FromTxnDate` and `ToTxnDate` must be between 01/01/1901 and 12/31/9999.