conductor-node 9.1.3 → 9.2.1

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

@@ -596,6 +596,132 @@ export default class QbdIntegration extends BaseIntegration {
          */
         query: (integrationConnectionId: string, params: QbdTypes.InvoiceQueryRq) => Promise<NonNullable<QbdTypes.InvoiceQueryRs["InvoiceRet"]>>;
     };
+    itemDiscount: {
+        /**
+         * Adds a discount item. A discount item is a percentage or a fixed amount
+         * that will be subtracted from a total or subtotal. Items should be
+         * subtotaled (using an `ItemSubtotal` item) before a discount item is
+         * applied to them, because a discount only acts on the line that is
+         * directly above it. A discount item is different from a discount for early
+         * payment, which is represented as part of a `StandardTerms` object or
+         * DateDrivenTerms object. Note: When you specify an `ItemDiscount` item in
+         * any transaction (by using an `ItemRef`), do not specify a `Quantity` in
+         * the transaction. If you do, you will receive an error.
+         *
+         * Be Sharp WhenUsing Flat Discounts: Flat rate discounts are treated VERY
+         * differently vs. percentage discounts. A percentage discount only applies
+         * to the line right above it, so all of the tax implications for discounts
+         * apply ONLY to that line (Note that the story gets more complicated here
+         * for group items, subtotal lines, etc). A flat rate discount applies to
+         * EVERY line that is recorded above the discount. Thus, the $10.00 off you
+         * see is applied equally to the $100.00 Nontaxable target and the $100.00
+         * Taxable target. Thus, the sales tax for the 10.00 discount totals up to
+         * -$5.00. Therefore, for the desired behavior, the user must fill out the
+         * invoice like this: Item $100.00 Non Item $100.00 Tax Discount $20.00 Tax
+         * In this scenario, the $20.00 discount is properly distributed to be half
+         * taxed and half not taxed, so the taxable amount for the discount line is
+         * only -$10.00. The moral of the story: Non-Taxable Discounts are VERY
+         * dangerous. You should almost never use them unless discounts in your
+         * state are never applied to sales tax.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemDiscountAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemDiscountAddRq["ItemDiscountAdd"]) => Promise<NonNullable<QbdTypes.ItemDiscountAddRs["ItemDiscountRet"]>>;
+        /**
+         * Modifies a discount item. Starting with qbXML spec 7.0, you can modify
+         * the account ref, using the AccountRef aggregate and the
+         * `ApplyAccountRefToExistingTxns` boolean. You need to use the
+         * `ApplyAccountRefToExistingTxns` boolean because the QuickBooks UI
+         * displays a prompt asking whether the change should apply to existing
+         * transactions or not. Specifying True for the boolean basically dismisses
+         * this with a “Yes” answer, allowing your changes to be made and changes
+         * any existing transactions that use the item with that `AccountRef`.
+         * Specifying “False” means that the mod will not take affect if there are
+         * existing transactions. Setting this to “True” should be used with caution
+         * and normally only after some user has indicated that they want those
+         * changes made to all those existing transactions! If any affected
+         * transactions are protected by a closing date and password, the
+         * `AccountRef` changes will not be made and so the Mod request will return
+         * an error without making the requested Mod.
+         *
+         * Be Sharp When Using Flat Discounts: Flat rate discounts are treated VERY
+         * differently vs. percentage discounts. A percentage discount only applies
+         * to the line right above it, so all of the tax implications for discounts
+         * apply ONLY to that line (Note that the story gets more complicated here
+         * for group items, subtotal lines, etc). A flat rate discount applies to
+         * EVERY line that is recorded above the discount. Thus, the $10.00 off you
+         * see is applied equally to the $100.00 Nontaxable target and the $100.00
+         * Taxable target. Thus, the sales tax for the 10.00 discount totals up to
+         * -$5.00. Therefore, for the desired behavior, the user must fill out the
+         * invoice like this: Item $100.00 Non Item $100.00 Tax Discount $20.00 Tax
+         * In this scenario, the $20.00 discount is properly distributed to be half
+         * taxed and half not taxed, so the taxable amount for the discount line is
+         * only -$10.00. The moral of the story: Non-Taxable Discounts are VERY
+         * dangerous. You should almost never use them unless discounts in your
+         * state are never applied to sales tax.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemDiscountMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemDiscountModRq["ItemDiscountMod"]) => Promise<NonNullable<QbdTypes.ItemDiscountModRs["ItemDiscountRet"]>>;
+        /**
+         * Queries for the specified discount item or set of items.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemDiscountQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemDiscountQueryRq) => Promise<NonNullable<QbdTypes.ItemDiscountQueryRs["ItemDiscountRet"]>>;
+    };
+    itemFixedAsset: {
+        /**
+         * Adds a fixed-asset item. Fixed-asset items represent assets that will
+         * benefit a business for longer than one year. The purchase price of these
+         * fixed assets is typically expensed over a period of years, rather than in
+         * the year the purchase was made.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemFixedAssetAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemFixedAssetAddRq["ItemFixedAssetAdd"]) => Promise<NonNullable<QbdTypes.ItemFixedAssetAddRs["ItemFixedAssetRet"]>>;
+        /**
+         * Modifies a fixed asset item. Fixed-asset items represent assets that will
+         * benefit a business for longer than one year. The purchase price of these
+         * fixed assets is typically expensed over a period of years, rather than in
+         * the year the purchase was made.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemFixedAssetMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemFixedAssetModRq["ItemFixedAssetMod"]) => Promise<NonNullable<QbdTypes.ItemFixedAssetModRs["ItemFixedAssetRet"]>>;
+        /**
+         * Queries for the specified fixed-asset item or set of fixed asset items.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemFixedAssetQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemFixedAssetQueryRq) => Promise<NonNullable<QbdTypes.ItemFixedAssetQueryRs["ItemFixedAssetRet"]>>;
+    };
+    itemGroup: {
+        /**
+         * Adds an item group. `ItemGroup` objects represent items that are grouped
+         * together for fast entry, and an `ItemGroupRef` aggregate refers to one of
+         * these item groups. In a request, if an `ItemGroupRef` aggregate includes
+         * both `FullName` and `ListID`, `FullName` will be ignored. You can use an
+         * `ItemGroupQuery` request to get information about all the item groups
+         * that are set up in the QuickBooks file.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemGroupAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemGroupAddRq["ItemGroupAdd"]) => Promise<NonNullable<QbdTypes.ItemGroupAddRs["ItemGroupRet"]>>;
+        /**
+         * Modifies an item group.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemGroupMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemGroupModRq["ItemGroupMod"]) => Promise<NonNullable<QbdTypes.ItemGroupModRs["ItemGroupRet"]>>;
+        /**
+         * An `ItemGroupQuery` request will return information about all the item
+         * groups that are set up in the QuickBooks file.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/itemgroupquery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemGroupQueryRq) => Promise<NonNullable<QbdTypes.ItemGroupQueryRs["ItemGroupRet"]>>;
+    };
     itemInventory: {
         /**
          * Adds an inventory item. An inventory item is any merchandise or part that
@@ -643,6 +769,46 @@ export default class QbdIntegration extends BaseIntegration {
          */
         query: (integrationConnectionId: string, params: QbdTypes.ItemInventoryQueryRq) => Promise<NonNullable<QbdTypes.ItemInventoryQueryRs["ItemInventoryRet"]>>;
     };
+    itemInventoryAssembly: {
+        /**
+         * Adds an inventory assembly item, which is an item that is assembled or
+         * manufactured from other inventory items. The items and/or assemblies that
+         * make up the assembly are called components.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemInventoryAssemblyAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemInventoryAssemblyAddRq["ItemInventoryAssemblyAdd"]) => Promise<NonNullable<QbdTypes.ItemInventoryAssemblyAddRs["ItemInventoryAssemblyRet"]>>;
+        /**
+         * Modifies an inventory assembly item. If you are adding components to the
+         * assembly, remember that the component items and/or assemblies that make
+         * up the assembly are limited in number.
+         *
+         * You can modify the income account ref, using the `IncomeAccountRef`
+         * aggregate and the `ApplyIncomeAccountRefToExistingTxns` boolean. You need
+         * to use the `ApplyIncomeAccountRefToExistingTxns` boolean because the
+         * QuickBooks UI displays a prompt asking whether the change should apply to
+         * existing transactions or not. Specifying `True` for the boolean basically
+         * dismisses this with a “Yes” answer, allowing your changes to be made and
+         * changes any existing transactions that use the item with that AccountRef.
+         * Specifying “False” means that the mod will not take affect if there are
+         * existing transactions. Setting this to “True” should be used with caution
+         * and normally only after some user has indicated that they want those
+         * changes made to all those existing transactions! If any affected
+         * transactions are protected by a closing date and password, the
+         * `IncomeAccountRef` changes will not be made and so the Mod request will
+         * return an error without making the requested Mod.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemInventoryAssemblyMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemInventoryAssemblyModRq["ItemInventoryAssemblyMod"]) => Promise<NonNullable<QbdTypes.ItemInventoryAssemblyModRs["ItemInventoryAssemblyRet"]>>;
+        /**
+         * Queries for the specified inventory assembly item or set of assembly
+         * items.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemInventoryAssemblyQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemInventoryAssemblyQueryRq) => Promise<NonNullable<QbdTypes.ItemInventoryAssemblyQueryRs["ItemInventoryAssemblyRet"]>>;
+    };
     itemNonInventory: {
         /**
          * Adds a non-inventory item, which is any material or part that a business
@@ -693,6 +859,216 @@ export default class QbdIntegration extends BaseIntegration {
          */
         query: (integrationConnectionId: string, params: QbdTypes.ItemNonInventoryQueryRq) => Promise<NonNullable<QbdTypes.ItemNonInventoryQueryRs["ItemNonInventoryRet"]>>;
     };
+    itemOtherCharge: {
+        /**
+         * Adds an other charge item, which are miscellaneous charges that do not
+         * fall into the categories of service, labor, materials, or parts. Examples
+         * include delivery charges, setup fees, and service charges.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemOtherChargeAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemOtherChargeAddRq["ItemOtherChargeAdd"]) => Promise<NonNullable<QbdTypes.ItemOtherChargeAddRs["ItemOtherChargeRet"]>>;
+        /**
+         * Modifies an other charge item.
+         *
+         * About `SalesOrPurchaseMod` versus `SalesAndPurchaseMod` in an
+         * `ItemOtherChargeMod` request: You cannot change the reimbursable status
+         * of an other-charge item through the SDK. For example, if an other-charge
+         * item is marked as non-reimbursable in QuickBooks, you cannot send a
+         * modify request that includes a `SalesAndPurchaseMod` aggregate.
+         * Similarly, if you send an `ItemOtherChargeAdd` request that includes a
+         * SalesOrPurchase aggregate, you cannot later modify that item using a
+         * `SalesAndPurchaseMod` aggregate.
+         *
+         * You can modify the various account references using the appropriate
+         * account reference aggregate and the matching Apply Account
+         * `RefToExistingTxns` boolean. You need to use the boolean when you change
+         * an account ref because the QuickBooks UI displays a prompt asking whether
+         * the change should apply to existing transactions or not. Specifying
+         * `True` for the boolean basically dismisses this with a “Yes” answer,
+         * allowing your changes to be made and changes any existing transactions
+         * that use the item with that AccountRef. Specifying “False” means that the
+         * mod will not take affect if there are existing transactions. Setting this
+         * to “True” should be used with caution and normally only after some user
+         * has indicated that they want those changes made to all those existing
+         * transactions! If any affected transactions are protected by a closing
+         * date and password, the AccountRef changes will not be made and so the Mod
+         * request will return an error without making the requested Mod.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemOtherChargeMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemOtherChargeModRq["ItemOtherChargeMod"]) => Promise<NonNullable<QbdTypes.ItemOtherChargeModRs["ItemOtherChargeRet"]>>;
+        /**
+         * Queries for the specified other charge item or set of items.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemOtherChargeQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemOtherChargeQueryRq) => Promise<NonNullable<QbdTypes.ItemOtherChargeQueryRs["ItemOtherChargeRet"]>>;
+    };
+    itemPayment: {
+        /**
+         * Adds an item payment or set of payments. You can use this request to
+         * create a payment for a customer or vendor.
+         *
+         * For an `ItemPaymentAdd` request, you can “set” the “Group with
+         * undeposited funds” radio button in QuickBooks either by not specifying
+         * `DepositToAccountRef` at all, or by specifying the special
+         * UndepositedFunds account for the `DepositToAccountRef`.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemPaymentAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemPaymentAddRq["ItemPaymentAdd"]) => Promise<NonNullable<QbdTypes.ItemPaymentAddRs["ItemPaymentRet"]>>;
+        /**
+         * Modifies an item payment.
+         *
+         * For an `ItemPaymentMod` request, you can “set” the “Group with
+         * undeposited funds” radio button in QuickBooks by either attempting to
+         * clear the DepositToAccountRef, or by specifying the account whose
+         * `SpecialAccountType` is `UndepositedFunds` for the `DepositToAccountRef`.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemPaymentMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemPaymentModRq["ItemPaymentMod"]) => Promise<NonNullable<QbdTypes.ItemPaymentModRs["ItemPaymentRet"]>>;
+        /**
+         * Queries for the specified item payment or set of payments.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemPaymentQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemPaymentQueryRq) => Promise<NonNullable<QbdTypes.ItemPaymentQueryRs["ItemPaymentRet"]>>;
+    };
+    itemReceipt: {
+        /**
+         * Adds an item receipt transaction, which is a transaction entered in
+         * QuickBooks when a shipment is received from a vendor. If you use
+         * `PurchaseOrders` to order from the vendor, you can link the item receipt
+         * to purchase order to receive the items against the purchase orders to
+         * automatically update (and eventually close) the purchase orders. This
+         * linking also saves you having to re-create line items as they are pulled
+         * in automatically from the purchase order. You can do this linking only in
+         * the item receipt add, not in the mod.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemReceiptAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemReceiptAddRq["ItemReceiptAdd"]) => Promise<NonNullable<QbdTypes.ItemReceiptAddRs["ItemReceiptRet"]>>;
+        /**
+         * Modifies an existing item receipt.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemReceiptMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemReceiptModRq["ItemReceiptMod"]) => Promise<NonNullable<QbdTypes.ItemReceiptModRs["ItemReceiptRet"]>>;
+        /**
+         * An item receipt transaction is entered in QuickBooks when a shipment is
+         * received from a vendor.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemReceiptQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemReceiptQueryRq) => Promise<NonNullable<QbdTypes.ItemReceiptQueryRs["ItemReceiptRet"]>>;
+    };
+    itemSalesTax: {
+        /**
+         * Adds a sales-tax item, which is an item used to calculate a single sales
+         * tax that is collected at a specified rate and paid to a single agency.
+         * (Compare with the `ItemSalesTaxGroupAdd` message.)
+         *
+         * An `ItemSalesTaxRef` aggregate refers to an item on this list. In a
+         * request, if an `ItemSalesTaxRef` aggregate includes both `FullName` and
+         * `ListID`, `FullName` will be ignored. Taxes can be reflected in
+         * transaction line items.
+         *
+         * The following information refers to invoices specifically, but it also
+         * applies to sales receipts. Generally it's best to assign a tax item or
+         * tax group item to an invoice and allow QuickBooks to apply the same tax
+         * to all taxable items on the invoice. However in some situations multiple
+         * tax combinations are required, so this method doesn’t work. In this case
+         * one must use techniques to apply the taxes in the invoice itself as line
+         * items. Using lines to apply taxes isn’t always straight forward. When
+         * applying taxes as line items, only single tax items can be used, tax
+         * groups can only be used for the entire invoice. If you have multiple
+         * taxes which apply to all taxable items, and one or more other taxes that
+         * only apply to some of the items on an invoice its better to use a tax
+         * group which applies to the entire invoice for the taxes which applies to
+         * all taxable items and then apply the other taxes in the invoice itself.
+         * One applies a tax or tax group to an entire invoice by using the
+         * `ItemSalesTaxRef` aggregate. One can use subtotals to apply a single tax
+         * line to multiple items in an invoice, but the tax is only applied
+         * automatically for the first tax line after the subtotal line. Any other
+         * tax lines which need to be applied to the subtotal line must supply their
+         * own amount. If you don’t supply an amount the amount comes out as zero
+         * and the tax line is useless. When one does supply an amount, the amount
+         * of tax on the subtotal also shows up in the rate column for that tax
+         * line. There isn’t any way for the rate to show up as anything other than
+         * the amount of the tax. If you have a complicated tax situation where no
+         * single tax applies to all taxable items on the invoice, you must choose a
+         * zero percent tax to apply for the entire invoice. It is recommended to
+         * name such a tax item “Tax Calculated On Invoice” so that it’s clear that
+         * the tax is not being applied by QuickBooks on the entire invoice.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSalesTaxAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemSalesTaxAddRq["ItemSalesTaxAdd"]) => Promise<NonNullable<QbdTypes.ItemSalesTaxAddRs["ItemSalesTaxRet"]>>;
+        /**
+         * Modifies an existing sales-tax item.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSalesTaxMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemSalesTaxModRq["ItemSalesTaxMod"]) => Promise<NonNullable<QbdTypes.ItemSalesTaxModRs["ItemSalesTaxRet"]>>;
+        /**
+         * Queries for the specified sales-tax item or set of items.
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemSalesTaxQueryRq) => Promise<NonNullable<QbdTypes.ItemSalesTaxQueryRs["ItemSalesTaxRet"]>>;
+    };
+    itemSalesTaxGroup: {
+        /**
+         * Adds a sales-tax group item, which is an item used for calculating two or
+         * more sales taxes grouped together and applied to the same sale. For
+         * example, local and state taxes could be tracked separately but applied to
+         * a sale as one tax. (Compare with the `ItemSalesTaxAdd` message.)
+         *
+         * Taxes can be reflected in transaction line items The following
+         * information refers to invoices specifically, but it also applies to sales
+         * receipts. Generally its best to assign a tax item or tax group item to an
+         * invoice and allow QuickBooks to apply the same tax to all taxable items
+         * on the invoice. However in some situations multiple tax combinations are
+         * required, so this method doesn’t work. In this case one must use
+         * techniques to apply the taxes in the invoice itself as line items. Using
+         * lines to apply taxes isn’t always straight forward. When applying taxes
+         * as line items, only single tax items can be used, tax groups can only be
+         * used for the entire invoice. If you have multiple taxes which apply to
+         * all taxable items, and one or more other taxes that only apply to some of
+         * the items on an invoice its better to use a tax group which applies to
+         * the entire invoice for the taxes which applies to all taxable items and
+         * then apply the other taxes in the invoice itself. One applies a tax or
+         * tax group to an entire invoice by using the `ItemSalesTaxRef` aggregate.
+         * One can use subtotals to apply a single tax line to multiple items in an
+         * invoice, but the tax is only applied automatically for the first tax line
+         * after the subtotal line. Any other tax lines which need to be applied to
+         * the subtotal line must supply their own amount. If you don’t supply an
+         * amount the amount comes out as zero and the tax line is useless. When one
+         * does supply an amount, the amount of tax on the subtotal also shows up in
+         * the rate column for that tax line. There isn’t any way for the rate to
+         * show up as anything other than the amount of the tax. If you have a
+         * complicated tax situation where no single tax applies to all taxable
+         * items on the invoice, you must choose a zero percent tax to apply for the
+         * entire invoice. It is recommended to name such a tax item “Tax Calculated
+         * On Invoice” so that it’s clear that the tax is not being applied by
+         * QuickBooks on the entire invoice.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSalesTaxGroupAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemSalesTaxGroupAddRq["ItemSalesTaxGroupAdd"]) => Promise<NonNullable<QbdTypes.ItemSalesTaxGroupAddRs["ItemSalesTaxGroupRet"]>>;
+        /**
+         * Modifies an existing sales-tax group item.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSalesTaxGroupMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemSalesTaxGroupModRq["ItemSalesTaxGroupMod"]) => Promise<NonNullable<QbdTypes.ItemSalesTaxGroupModRs["ItemSalesTaxGroupRet"]>>;
+        /**
+         * Queries for the specified sales-tax group item or set of group items.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSalesTaxGroupQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemSalesTaxGroupQueryRq) => Promise<NonNullable<QbdTypes.ItemSalesTaxGroupQueryRs["ItemSalesTaxGroupRet"]>>;
+    };
     itemService: {
         /**
          * Adds a service item, which is an item that refers to services that a
@@ -748,6 +1124,48 @@ export default class QbdIntegration extends BaseIntegration {
          */
         query: (integrationConnectionId: string, params: QbdTypes.ItemServiceQueryRq) => Promise<NonNullable<QbdTypes.ItemServiceQueryRs["ItemServiceRet"]>>;
     };
+    itemSubtotal: {
+        /**
+         * Adds a subtotal item. On a sales form, a subtotal item will add up the
+         * amounts of the item lines above it, up to the previous subtotal. Items
+         * must be subtotaled before a discount is applied (using `ItemDiscount`),
+         * because a discount applies only to the line that is directly above it.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSubtotalAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.ItemSubtotalAddRq["ItemSubtotalAdd"]) => Promise<NonNullable<QbdTypes.ItemSubtotalAddRs["ItemSubtotalRet"]>>;
+        /**
+         * Modifies an existing subtotal item.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSubtotalMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.ItemSubtotalModRq["ItemSubtotalMod"]) => Promise<NonNullable<QbdTypes.ItemSubtotalModRs["ItemSubtotalRet"]>>;
+        /**
+         * Queries for the specified subtotal item or set of items.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/ItemSubtotalQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.ItemSubtotalQueryRq) => Promise<NonNullable<QbdTypes.ItemSubtotalQueryRs["ItemSubtotalRet"]>>;
+    };
+    jobType: {
+        /**
+         * Adds a job type. A job type can be used to separate jobs into any
+         * categories that are meaningful to the business.
+         *
+         * A `JobTypeRef` aggregate refers to a job type on the `JobType` list. In a
+         * request, if a `JobTypeRef` aggregate includes both `FullName` and
+         * `ListID`, `FullName` will be ignored.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/JobTypeAdd
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.JobTypeAddRq["JobTypeAdd"]) => Promise<NonNullable<QbdTypes.JobTypeAddRs["JobTypeRet"]>>;
+        /**
+         * Queries for the specified job type or set of job types.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/JobTypeQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.JobTypeQueryRq) => Promise<NonNullable<QbdTypes.JobTypeQueryRs["JobTypeRet"]>>;
+    };
     journalEntry: {
         /**
          * The debit and credit lines can be intermingled. A credit line can legally
@@ -817,56 +1235,39 @@ export default class QbdIntegration extends BaseIntegration {
          */
         query: (integrationConnectionId: string, params: QbdTypes.JournalEntryQueryRq) => Promise<NonNullable<QbdTypes.JournalEntryQueryRs["JournalEntryRet"]>>;
     };
-    timeTracking: {
+    priceLevel: {
         /**
-         * The time-tracking transactions that are returned in this query include
-         * time tracking information that was entered into QuickBooks manually or
-         * gathered using the QuickBooks “Timer” or “Stopwatch.” Note that the
-         * QuickBooks Timer application can run on its own without QuickBooks, but
-         * the QuickBooks SDK cannot access the Timer data directly. The Timer data
-         * must be imported into QuickBooks before it is accessible via the SDK.)
-         *
-         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TimeTrackingQuery
+         * Adds a price level. You can use price levels to specify custom pricing
+         * for specific customers.
+         *
+         * Once you create a price level for a customer, QuickBooks will
+         * automatically use the custom price in new invoices, sales receipts, sales
+         * orders or credit memos for that customer. You can override this automatic
+         * feature, however, when you create the invoices, sales receipts, etc.) The
+         * user can now specify a price level on line items in the following
+         * supported sales transactions: invoices, sales receipts, credit memos, and
+         * sales orders. Notice that the response data for the affected sales
+         * transaction does not list the price level that was used. The response
+         * simply lists the Rate for the item, which was set using the price level.
+         * The `CurrencyRef` should only be used with “per item” price levels.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/PriceLevelAdd
          */
-        add: (integrationConnectionId: string, params: QbdTypes.TimeTrackingAddRq["TimeTrackingAdd"]) => Promise<NonNullable<QbdTypes.TimeTrackingAddRs["TimeTrackingRet"]>>;
+        add: (integrationConnectionId: string, params: QbdTypes.PriceLevelAddRq["PriceLevelAdd"]) => Promise<NonNullable<QbdTypes.PriceLevelAddRs["PriceLevelRet"]>>;
         /**
-         * Modifies a time tracking transaction.
+         * Modifies a price level.
          *
-         * This allows you to modify time entry and mark time entered as billed.
-         * Applications using qbXML spec levels less than 6.0 aren’t able to Modify
-         * a time tracking transaction. However, those applications can achieve the
-         * results of a modify operation by deleting the time tracking transaction
-         * (using `TxnDelRq`) and then re-adding it with the desired values. You can
-         * do this only if no other downstream transactions have used that
-         * particular time tracking transaction. (Otherwise, the `TxnDel` request
-         * will fail.) This differs slightly from the UI, which allows these
-         * transactions to be edited directly. However, even in the UI, modifying a
-         * time tracking transaction does not result in changes to any downstream
-         * transactions that use it. There is no link between an invoice and the
-         * time entries. However when you do the invoicing from QuickBooks,
-         * QuickBooks does mark the time entries as “billed.” If you don’t record
-         * the time entries as billed properly, then you get into a user workflow
-         * issue where every time the user creates an invoice for a customer, QB
-         * pops up a dialog asking if they want to bill the un-billed time (which
-         * you already billed from your app). That’s why beginning with QB2007 and
-         * qbXML spec 6.0 we added support for the “BillableStatus” field *and* add
-         * `TimeTrackingMod` so that you can mark the time as billed when you create
-         * an invoice for it.
+         * The `CurrencyRef` should only be used with “per item” price levels.
          *
-         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TimeTrackingMod
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/PriceLevelMod
          */
-        mod: (integrationConnectionId: string, params: QbdTypes.TimeTrackingModRq["TimeTrackingMod"]) => Promise<NonNullable<QbdTypes.TimeTrackingModRs["TimeTrackingRet"]>>;
+        mod: (integrationConnectionId: string, params: QbdTypes.PriceLevelModRq["PriceLevelMod"]) => Promise<NonNullable<QbdTypes.PriceLevelModRs["PriceLevelRet"]>>;
         /**
-         * The time-tracking transactions that are returned in this query include
-         * time tracking information that was entered into QuickBooks manually or
-         * gathered using the QuickBooks “Timer” or “Stopwatch.” Note that the
-         * QuickBooks Timer application can run on its own without QuickBooks, but
-         * the QuickBooks SDK cannot access the Timer data directly. The Timer data
-         * must be imported into QuickBooks before it is accessible via the SDK.)
+         * Queries for the specified price level or set of price levels.
          *
-         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TimeTrackingQuery
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/PriceLevelQuery
          */
-        query: (integrationConnectionId: string, params: QbdTypes.TimeTrackingQueryRq) => Promise<NonNullable<QbdTypes.TimeTrackingQueryRs["TimeTrackingRet"]>>;
+        query: (integrationConnectionId: string, params: QbdTypes.PriceLevelQueryRq) => Promise<NonNullable<QbdTypes.PriceLevelQueryRs["PriceLevelRet"]>>;
     };
     purchaseOrder: {
         /**
@@ -909,6 +1310,57 @@ export default class QbdIntegration extends BaseIntegration {
          */
         query: (integrationConnectionId: string, params: QbdTypes.PurchaseOrderQueryRq) => Promise<NonNullable<QbdTypes.PurchaseOrderQueryRs["PurchaseOrderRet"]>>;
     };
+    timeTracking: {
+        /**
+         * The time-tracking transactions that are returned in this query include
+         * time tracking information that was entered into QuickBooks manually or
+         * gathered using the QuickBooks “Timer” or “Stopwatch.” Note that the
+         * QuickBooks Timer application can run on its own without QuickBooks, but
+         * the QuickBooks SDK cannot access the Timer data directly. The Timer data
+         * must be imported into QuickBooks before it is accessible via the SDK.)
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TimeTrackingQuery
+         */
+        add: (integrationConnectionId: string, params: QbdTypes.TimeTrackingAddRq["TimeTrackingAdd"]) => Promise<NonNullable<QbdTypes.TimeTrackingAddRs["TimeTrackingRet"]>>;
+        /**
+         * Modifies a time tracking transaction.
+         *
+         * This allows you to modify time entry and mark time entered as billed.
+         * Applications using qbXML spec levels less than 6.0 aren’t able to Modify
+         * a time tracking transaction. However, those applications can achieve the
+         * results of a modify operation by deleting the time tracking transaction
+         * (using `TxnDelRq`) and then re-adding it with the desired values. You can
+         * do this only if no other downstream transactions have used that
+         * particular time tracking transaction. (Otherwise, the `TxnDel` request
+         * will fail.) This differs slightly from the UI, which allows these
+         * transactions to be edited directly. However, even in the UI, modifying a
+         * time tracking transaction does not result in changes to any downstream
+         * transactions that use it. There is no link between an invoice and the
+         * time entries. However when you do the invoicing from QuickBooks,
+         * QuickBooks does mark the time entries as “billed.” If you don’t record
+         * the time entries as billed properly, then you get into a user workflow
+         * issue where every time the user creates an invoice for a customer, QB
+         * pops up a dialog asking if they want to bill the un-billed time (which
+         * you already billed from your app). That’s why beginning with QB2007 and
+         * qbXML spec 6.0 we added support for the “BillableStatus” field *and* add
+         * `TimeTrackingMod` so that you can mark the time as billed when you create
+         * an invoice for it.
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TimeTrackingMod
+         */
+        mod: (integrationConnectionId: string, params: QbdTypes.TimeTrackingModRq["TimeTrackingMod"]) => Promise<NonNullable<QbdTypes.TimeTrackingModRs["TimeTrackingRet"]>>;
+        /**
+         * The time-tracking transactions that are returned in this query include
+         * time tracking information that was entered into QuickBooks manually or
+         * gathered using the QuickBooks “Timer” or “Stopwatch.” Note that the
+         * QuickBooks Timer application can run on its own without QuickBooks, but
+         * the QuickBooks SDK cannot access the Timer data directly. The Timer data
+         * must be imported into QuickBooks before it is accessible via the SDK.)
+         *
+         * https://developer.intuit.com/app/developer/qbdesktop/docs/api-reference/qbdesktop/TimeTrackingQuery
+         */
+        query: (integrationConnectionId: string, params: QbdTypes.TimeTrackingQueryRq) => Promise<NonNullable<QbdTypes.TimeTrackingQueryRs["TimeTrackingRet"]>>;
+    };
     vendor: {
         /**
          * Adds a vendor.