conductor-node 3.6.0 → 3.7.0

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

@@ -41,7 +41,7 @@ export interface AccountAddRq {
     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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface AccountAddRs {
     AccountRet?: AccountRet;
@@ -51,9 +51,9 @@ export interface AccountFilter {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Allows you to filter for data that relates to the specified object and its descendants. */
     ListIDWithChildren?: string;
     /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
@@ -106,7 +106,7 @@ export interface AccountModRq {
     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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface AccountModRs {
     AccountRet?: AccountRet;
@@ -116,9 +116,9 @@ export interface AccountQueryRq {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
     MaxReturned?: number;
     /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
@@ -144,7 +144,7 @@ export interface AccountQueryRq {
     /** Filters according to the object’s `Name`. */
     NameRangeFilter?: NameRangeFilter;
     /** A list of QuickBooks account types. */
-    AccountType?: AccountType | AccountType[];
+    AccountType?: AccountType | [AccountType, ...AccountType[]];
     /** Filters by the specified currency. */
     CurrencyFilter?: CurrencyFilter;
     /** 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.
@@ -152,16 +152,16 @@ export interface AccountQueryRq {
     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;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface AccountQueryRs {
-    AccountRet?: AccountRet | AccountRet[];
+    AccountRet: [AccountRet, ...AccountRet[]];
 }
 export interface AccountRef {
     /** 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. */
@@ -223,7 +223,7 @@ export interface AccountRet {
     When used with `PriceLevels`, the `CurrencyRef` should only be used with “per item” price levels. */
     CurrencyRef?: CurrencyRef;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export declare type AccountType = "AccountsPayable" | "AccountsReceivable" | "Bank" | "CostOfGoodsSold" | "CreditCard" | "Equity" | "Expense" | "FixedAsset" | "Income" | "LongTermLiability" | "NonPosting" | "OtherAsset" | "OtherCurrentAsset" | "OtherCurrentLiability" | "OtherExpense" | "OtherIncome";
 export declare type AccrualPeriod = "BeginningOfYear" | "EveryHourOnPaycheck" | "EveryPaycheck";
@@ -299,7 +299,7 @@ export interface AppliedToTxnAdd {
     /** 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`. */
-    SetCredit?: SetCredit | SetCredit[];
+    SetCredit?: 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. */
@@ -313,7 +313,7 @@ export interface AppliedToTxnMod {
     /** 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`. */
-    SetCredit?: SetCredit | SetCredit[];
+    SetCredit?: 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. */
@@ -341,7 +341,7 @@ export interface AppliedToTxnRet {
     /** 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. */
-    LinkedTxn?: LinkedTxn | LinkedTxn[];
+    LinkedTxn?: LinkedTxn | [LinkedTxn, ...LinkedTxn[]];
 }
 export interface ApplyCheckToTxnAdd {
     /** 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. */
@@ -406,9 +406,9 @@ export interface BillAdd {
     /** The `LinkToTxnID` aggregate allows to link an entire transaction. If you want to link individual lines in a transaction, use the `LinkToTxn` aggregate.
   
     You can use both `LinkToTxnID` and `LinkToTxn` aggregates in the same request, as long as these aggregates do NOT link to the same `TxnID`. If both aggregates are used and do link to the same `TxnID`, you receive an error 3000. Also, if you attempt to invoke `LinkToTxnID` with the same `TxnID`, more than once, you get an error 3177. If the transaction specified by `LinkToTxnID` is already closed or fully received and the `ItemReceiptAdd` request does not contain any other lines, you get error 3180 for attempting to save an empty transaction. You get a warning if you attempt to link to a transaction that’s already closed. */
-    LinkToTxnID?: string[] | string;
+    LinkToTxnID?: string | [string, ...string[]];
     /** A list of `IExpenseLine` objects, each representing one line in this expense. */
-    ExpenseLineAdd?: ExpenseLineAdd | ExpenseLineAdd[];
+    ExpenseLineAdd?: ExpenseLineAdd | [ExpenseLineAdd, ...ExpenseLineAdd[]];
     /** An `ItemLine` is used to track any portion of a transaction that represents the purchase of an “item.” If `ItemLineAdd` does not specify an `Amount`, `Cost`, or `Quantity`, then QuickBooks will calculate `Amount` based on a `Quantity` of 1 and the suggested `Cost`. */
     ItemLineAdd?: ItemLineAdd;
     /** Refers to items that are grouped together in QuickBooks for fast entry. */
@@ -453,7 +453,7 @@ export interface BillAddRq {
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface BillAddRs {
     BillRet?: BillRet;
@@ -509,7 +509,7 @@ export interface BillMod {
     /** Set `ClearExpenseLines` to true to clear all the expense lines. To modify individual lines, use `ExpenseLineMod`. */
     ClearExpenseLines?: boolean;
     /** A list of `IExpenseLine` objects, each representing one line in this expense. */
-    ExpenseLineMod?: ExpenseLineMod | ExpenseLineMod[];
+    ExpenseLineMod?: ExpenseLineMod | [ExpenseLineMod, ...ExpenseLineMod[]];
     /** Set `ClearItemLines` to true to clear all the item lines. To modify individual lines, use `ItemLineMod`. */
     ClearItemLines?: boolean;
     /** An `ItemLine` is used to track any portion of a transaction that represents the purchase of an “item.” If `ItemLineAdd` does not specify an `Amount`, `Cost`, or `Quantity`, then QuickBooks will calculate `Amount` based on a `Quantity` of 1 and the suggested `Cost`. */
@@ -524,7 +524,7 @@ export interface BillModRq {
     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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface BillModRs {
     BillRet?: BillRet;
@@ -550,12 +550,12 @@ export interface BillPaymentCheckAdd {
     /** Allows for the attachment of a user defined GUID value. */
     ExternalGUID?: string;
     /** `AppliedToTxn` List A list of `AppliedToTxn` aggregates. */
-    AppliedToTxnAdd: AppliedToTxnAdd | AppliedToTxnAdd[];
+    AppliedToTxnAdd: AppliedToTxnAdd | [AppliedToTxnAdd, ...AppliedToTxnAdd[]];
 }
 export interface BillPaymentCheckAddRq {
     BillPaymentCheckAdd: BillPaymentCheckAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface BillPaymentCheckAddRs {
     BillPaymentCheckRet?: BillPaymentCheckRet;
@@ -581,12 +581,12 @@ export interface BillPaymentCheckMod {
     /** Additional information. */
     Memo?: string;
     /** `AppliedToTxn` List A list of `AppliedToTxn` aggregates. */
-    AppliedToTxnMod?: AppliedToTxnMod | AppliedToTxnMod[];
+    AppliedToTxnMod?: AppliedToTxnMod | [AppliedToTxnMod, ...AppliedToTxnMod[]];
 }
 export interface BillPaymentCheckModRq {
     BillPaymentCheckMod: BillPaymentCheckMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface BillPaymentCheckModRs {
     BillPaymentCheckRet?: BillPaymentCheckRet;
@@ -594,11 +594,11 @@ export interface BillPaymentCheckModRs {
 }
 export interface BillPaymentCheckQueryRq {
     /** 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;
+    TxnID?: string | [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;
+    RefNumber?: string | [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;
+    RefNumberCaseSensitive?: string | [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.) */
@@ -618,12 +618,12 @@ export interface BillPaymentCheckQueryRq {
     /** 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;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface BillPaymentCheckQueryRs {
-    BillPaymentCheckRet?: BillPaymentCheckRet | BillPaymentCheckRet[];
+    BillPaymentCheckRet: [BillPaymentCheckRet, ...BillPaymentCheckRet[]];
 }
 export interface BillPaymentCheckRet {
     /** 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. */
@@ -665,23 +665,23 @@ export interface BillPaymentCheckRet {
     /** Allows for the attachment of a user defined GUID value. */
     ExternalGUID?: string;
     /** `AppliedToTxn` List A list of `AppliedToTxn` aggregates. */
-    AppliedToTxnRet?: AppliedToTxnRet | AppliedToTxnRet[];
+    AppliedToTxnRet?: 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[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export interface BillQueryRq {
     /** 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;
+    TxnID?: string | [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;
+    RefNumber?: string | [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;
+    RefNumberCaseSensitive?: string | [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.
@@ -721,16 +721,16 @@ export interface BillQueryRq {
     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;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface BillQueryRs {
-    BillRet?: BillRet | BillRet[];
+    BillRet: [BillRet, ...BillRet[]];
 }
 export interface BillRet {
     /** 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.
@@ -794,9 +794,9 @@ export interface BillRet {
     /** 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[];
+    LinkedTxn?: LinkedTxn | [LinkedTxn, ...LinkedTxn[]];
     /** A list of `IExpenseLine` objects, each representing one line in this expense. */
-    ExpenseLineRet?: ExpenseLineRet | ExpenseLineRet[];
+    ExpenseLineRet?: ExpenseLineRet | [ExpenseLineRet, ...ExpenseLineRet[]];
     /** An `ItemLine` is used to track any portion of a transaction that represents the purchase of an “item.” If `ItemLineAdd` does not specify an `Amount`, `Cost`, or `Quantity`, then QuickBooks will calculate `Amount` based on a `Quantity` of 1 and the suggested `Cost`. */
     ItemLineRet?: ItemLineRet;
     /** Refers to items that are grouped together in QuickBooks for fast entry. */
@@ -804,7 +804,7 @@ export interface BillRet {
     /** Indicates the amount that is still owed. `AmountDue` minus any credits or discounts equals the `OpenAmount`. */
     OpenAmount?: string;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export declare type CashFlowClassification = "Financing" | "Investing" | "None" | "NotApplicable" | "Operating";
 export interface CheckAdd {
@@ -831,9 +831,9 @@ export interface CheckAdd {
     /** Allows for the attachment of a user defined GUID value. */
     ExternalGUID?: string;
     /** Allows you to specify a transaction to be paid by this check. */
-    ApplyCheckToTxnAdd?: ApplyCheckToTxnAdd | ApplyCheckToTxnAdd[];
+    ApplyCheckToTxnAdd?: ApplyCheckToTxnAdd | [ApplyCheckToTxnAdd, ...ApplyCheckToTxnAdd[]];
     /** A list of `IExpenseLine` objects, each representing one line in this expense. */
-    ExpenseLineAdd?: ExpenseLineAdd | ExpenseLineAdd[];
+    ExpenseLineAdd?: ExpenseLineAdd | [ExpenseLineAdd, ...ExpenseLineAdd[]];
     /** An `ItemLine` is used to track any portion of a transaction that represents the purchase of an “item.” If `ItemLineAdd` does not specify an `Amount`, `Cost`, or `Quantity`, then QuickBooks will calculate `Amount` based on a `Quantity` of 1 and the suggested `Cost`. */
     ItemLineAdd?: ItemLineAdd;
     /** Refers to items that are grouped together in QuickBooks for fast entry. */
@@ -842,7 +842,7 @@ export interface CheckAdd {
 export interface CheckAddRq {
     CheckAdd: CheckAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface CheckAddRs {
     CheckRet?: CheckRet;
@@ -874,11 +874,11 @@ export interface CheckMod {
     /** The exchange rate is the market price for which this currency can be exchanged for the currency used by the QuickBooks company file as the “home” currency. The exchange rate should be considered a snapshot of the rates in effect at the `AsOfDate`. You can update the exchange rate using the exchange rate property when you add a transaction. However, you need to obtain and supply the exchange rate. If you are using USD (United States Dollars) as the home currency and are connected to the Internet, you can download the current exchange rates for all active currencies automatically in the QuickBooks UI by selecting Lists->Currency->Activities->Download latest exchange rates. (Currently, you can’t do this in the SDK.) */
     ExchangeRate?: number;
     /** Allows you to specify a transaction to be paid by this check. */
-    ApplyCheckToTxnMod?: ApplyCheckToTxnMod | ApplyCheckToTxnMod[];
+    ApplyCheckToTxnMod?: ApplyCheckToTxnMod | [ApplyCheckToTxnMod, ...ApplyCheckToTxnMod[]];
     /** Set `ClearExpenseLines` to true to clear all the expense lines. To modify individual lines, use `ExpenseLineMod`. */
     ClearExpenseLines?: boolean;
     /** A list of `IExpenseLine` objects, each representing one line in this expense. */
-    ExpenseLineMod?: ExpenseLineMod | ExpenseLineMod[];
+    ExpenseLineMod?: ExpenseLineMod | [ExpenseLineMod, ...ExpenseLineMod[]];
     /** Set `ClearItemLines` to true to clear all the item lines. To modify individual lines, use `ItemLineMod`. */
     ClearItemLines?: boolean;
     /** An `ItemLine` is used to track any portion of a transaction that represents the purchase of an “item.” If `ItemLineAdd` does not specify an `Amount`, `Cost`, or `Quantity`, then QuickBooks will calculate `Amount` based on a `Quantity` of 1 and the suggested `Cost`. */
@@ -889,7 +889,7 @@ export interface CheckMod {
 export interface CheckModRq {
     CheckMod: CheckMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface CheckModRs {
     CheckRet?: CheckRet;
@@ -897,11 +897,11 @@ export interface CheckModRs {
 }
 export interface CheckQueryRq {
     /** 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;
+    TxnID?: string | [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;
+    RefNumber?: string | [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;
+    RefNumberCaseSensitive?: string | [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.) */
@@ -923,12 +923,12 @@ export interface CheckQueryRq {
     /** If you set `IncludeLinkedTxns` to true, then the returned object will include a list of all the transactions linked to the queried object. (This list is similar to the History view of a transaction in the user interface, but not identical, as the SDK list contains only linked transactions, not items.) Each linked transaction will be represented by a `LinkedTxn` aggregate. If no linked transactions exist, no `LinkedTxn` aggregates will be returned. */
     IncludeLinkedTxns?: boolean;
     /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
-    IncludeRetElement?: string[] | string;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface CheckQueryRs {
-    CheckRet?: CheckRet | CheckRet[];
+    CheckRet: [CheckRet, ...CheckRet[]];
 }
 export interface CheckRet {
     /** 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. */
@@ -972,15 +972,15 @@ export interface CheckRet {
     /** Allows for the attachment of a user defined GUID value. */
     ExternalGUID?: string;
     /** If the `IncludeLinkedTxns` flag is set to true in a query, or if you create an item receipt that links to other transactionsthen the returned object will include a list of linked transactions, if any exist. If no linked transactions exist, the `ILinkedTxnList` object will be empty. The list of linked transactions is similar to the History view of a transaction in the user interface, but not identical, as the SDK list contains only linked transactions, not items. */
-    LinkedTxn?: LinkedTxn | LinkedTxn[];
+    LinkedTxn?: LinkedTxn | [LinkedTxn, ...LinkedTxn[]];
     /** A list of `IExpenseLine` objects, each representing one line in this expense. */
-    ExpenseLineRet?: ExpenseLineRet | ExpenseLineRet[];
+    ExpenseLineRet?: ExpenseLineRet | [ExpenseLineRet, ...ExpenseLineRet[]];
     /** An `ItemLine` is used to track any portion of a transaction that represents the purchase of an “item.” If `ItemLineAdd` does not specify an `Amount`, `Cost`, or `Quantity`, then QuickBooks will calculate `Amount` based on a `Quantity` of 1 and the suggested `Cost`. */
     ItemLineRet?: ItemLineRet;
     /** Refers to items that are grouped together in QuickBooks for fast entry. */
     ItemGroupLineRet?: ItemGroupLineRet;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export interface ClassAdd {
     /** The case-insensitive name of the class, not including the names of its ancestors. */
@@ -993,7 +993,7 @@ export interface ClassAdd {
 export interface ClassAddRq {
     ClassAdd: ClassAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface ClassAddRs {
     ClassRet?: ClassRet;
@@ -1001,9 +1001,9 @@ export interface ClassAddRs {
 }
 export interface ClassFilter {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Allows you to filter for data that relates to the specified object and its descendants. */
     ListIDWithChildren?: string;
     /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
@@ -1024,7 +1024,7 @@ export interface ClassMod {
 export interface ClassModRq {
     ClassMod: ClassMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface ClassModRs {
     ClassRet?: ClassRet;
@@ -1032,9 +1032,9 @@ export interface ClassModRs {
 }
 export interface ClassQueryRq {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
     MaxReturned?: number;
     /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
@@ -1048,10 +1048,10 @@ export interface ClassQueryRq {
     /** Filters according to the object’s `Name`. */
     NameRangeFilter?: NameRangeFilter;
     /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
-    IncludeRetElement?: string[] | string;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface ClassQueryRs {
-    ClassRet?: ClassRet | ClassRet[];
+    ClassRet: [ClassRet, ...ClassRet[]];
 }
 export interface ClassRef {
     /** 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. */
@@ -1091,7 +1091,7 @@ export interface Contacts {
     /** The job title of a customer, vendor, employee, or person on the “other names” list. */
     JobTitle?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
 }
 export interface ContactsMod {
     /** 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. */
@@ -1109,7 +1109,7 @@ export interface ContactsMod {
     /** The job title of a customer, vendor, employee, or person on the “other names” list. */
     JobTitle?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
 }
 export interface ContactsRet {
     /** 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. */
@@ -1133,7 +1133,7 @@ export interface ContactsRet {
     /** The job title of a customer, vendor, employee, or person on the “other names” list. */
     JobTitle?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
 }
 export interface CreditCardInfo {
     /** 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. */
@@ -1153,9 +1153,9 @@ export interface CurrencyFilter {
     /** One or more `ListID` values. Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`.
   
     A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
-    ListID?: string[] | string;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
 }
 export interface CurrencyRef {
     /** Along with `FullName`, `ListID` is a way to identify a list object. When a list object is added to QuickBooks through the SDK or through the QuickBooks user interface, the server assigns it a `ListID`. A `ListID` is not unique across lists, but it is unique across each particular type of list. For example, two customers could not have the same `ListID`, and a customer could not have the same `ListID` as an employee (because Customer and Employee are both name lists). But a customer could have the same `ListID` as a non-inventory item. */
@@ -1189,7 +1189,7 @@ export interface CustomerAdd {
     /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
     ShipAddress?: ShipAddress;
     /** List of ship to addresses. */
-    ShipToAddress?: ShipToAddress | ShipToAddress[];
+    ShipToAddress?: ShipToAddress | [ShipToAddress, ...ShipToAddress[]];
     /** The telephone number. */
     Phone?: string;
     /** A telephone number given as an alternative to `Phone`. */
@@ -1205,9 +1205,9 @@ export interface CustomerAdd {
     /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
     AltContact?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** A list of contact records. */
-    Contacts?: Contacts | Contacts[];
+    Contacts?: Contacts | [Contacts, ...Contacts[]];
     /** Customer types allow business owners to categorize customers in ways that are meaningful for their businesses. For example, a customer type might indicate which industry a customer represents, or which part of the country a customer is in. A `CustomerTypeRef` aggregate refers to one of the types on the `CustomerType` list. In a request, if a `CustomerTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     CustomerTypeRef?: CustomerTypeRef;
     /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
@@ -1249,7 +1249,7 @@ export interface CustomerAdd {
     /** Not supported. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotes?: AdditionalNotes | AdditionalNotes[];
+    AdditionalNotes?: AdditionalNotes | [AdditionalNotes, ...AdditionalNotes[]];
     /** Preference for how invoices are delivered. */
     PreferredDeliveryMethod?: PreferredDeliveryMethod;
     /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
@@ -1264,7 +1264,7 @@ export interface CustomerAdd {
 export interface CustomerAddRq {
     CustomerAdd: CustomerAdd;
     /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
-    IncludeRetElement?: string[] | string;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface CustomerAddRs {
     CustomerRet?: CustomerRet;
@@ -1300,7 +1300,7 @@ export interface CustomerMod {
     /** Whatever address you specify in this aggregate must not result in an address greater than 5 lines, otherwise you’ll get a runtime error, because QuickBooks doesn’t support addresses more than 5 lines. There are two ways to specify an address within this aggregate: Using `Addr1` through `Addr3` along with the other possible aggregate elements, such as `City`, `State`, Postalcode.Using `Addr1`, `Addr2`, `Addr3`, `Addr4`, and `Addr5` to fully specify the address. If you use this so called “address block” approach, you cannot use any other address elements, such as `City`, `State`, etc. (Note: this approach is not valid for `EmployeeAdd`/Mod/Query) If you use the address block approach above, the lines `Addr1`…`Addr5` are each printed as a separate line on the transaction, and the values are returned in the Ret object under the aggregate `ShipAddressBlock` or `BillAddressBlock`. */
     ShipAddress?: ShipAddress;
     /** List of ship to addresses. */
-    ShipToAddress?: ShipToAddress | ShipToAddress[];
+    ShipToAddress?: ShipToAddress | [ShipToAddress, ...ShipToAddress[]];
     /** The telephone number. */
     Phone?: string;
     /** A telephone number given as an alternative to `Phone`. */
@@ -1316,9 +1316,9 @@ export interface CustomerMod {
     /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
     AltContact?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** A list of contact records. */
-    ContactsMod?: ContactsMod | ContactsMod[];
+    ContactsMod?: ContactsMod | [ContactsMod, ...ContactsMod[]];
     /** Customer types allow business owners to categorize customers in ways that are meaningful for their businesses. For example, a customer type might indicate which industry a customer represents, or which part of the country a customer is in. A `CustomerTypeRef` aggregate refers to one of the types on the `CustomerType` list. In a request, if a `CustomerTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     CustomerTypeRef?: CustomerTypeRef;
     /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
@@ -1356,7 +1356,7 @@ export interface CustomerMod {
     /** Not supported. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotesMod?: AdditionalNotesMod | AdditionalNotesMod[];
+    AdditionalNotesMod?: AdditionalNotesMod | [AdditionalNotesMod, ...AdditionalNotesMod[]];
     /** Preference for how invoices are delivered. */
     PreferredDeliveryMethod?: PreferredDeliveryMethod;
     /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
@@ -1369,7 +1369,7 @@ export interface CustomerMod {
 export interface CustomerModRq {
     CustomerMod: CustomerMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface CustomerModRs {
     CustomerRet?: CustomerRet;
@@ -1377,9 +1377,9 @@ export interface CustomerModRs {
 }
 export interface CustomerQueryRq {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
     MaxReturned?: number;
     /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
@@ -1399,12 +1399,12 @@ export interface CustomerQueryRq {
     /** Filter according to class. */
     ClassFilter?: ClassFilter;
     /** 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;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface CustomerQueryRs {
-    CustomerRet?: CustomerRet | CustomerRet[];
+    CustomerRet: [CustomerRet, ...CustomerRet[]];
 }
 export interface CustomerRef {
     /** 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. */
@@ -1454,7 +1454,7 @@ export interface CustomerRet {
     /** The address expressed as an address block of `Addr1` through `Addr5`, depending on the number of lines in the original request that created the address. */
     ShipAddressBlock?: ShipAddressBlock;
     /** List of ship to addresses. */
-    ShipToAddress?: ShipToAddress | ShipToAddress[];
+    ShipToAddress?: ShipToAddress | [ShipToAddress, ...ShipToAddress[]];
     /** The telephone number. */
     Phone?: string;
     /** A telephone number given as an alternative to `Phone`. */
@@ -1470,9 +1470,9 @@ export interface CustomerRet {
     /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
     AltContact?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** A list of contact records. */
-    ContactsRet?: ContactsRet | ContactsRet[];
+    ContactsRet?: ContactsRet | [ContactsRet, ...ContactsRet[]];
     /** Customer types allow business owners to categorize customers in ways that are meaningful for their businesses. For example, a customer type might indicate which industry a customer represents, or which part of the country a customer is in. A `CustomerTypeRef` aggregate refers to one of the types on the `CustomerType` list. In a request, if a `CustomerTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     CustomerTypeRef?: CustomerTypeRef;
     /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
@@ -1514,7 +1514,7 @@ export interface CustomerRet {
     /** Not supported. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotesRet?: AdditionalNotesRet | AdditionalNotesRet[];
+    AdditionalNotesRet?: AdditionalNotesRet | [AdditionalNotesRet, ...AdditionalNotesRet[]];
     /** Preference for how invoices are delivered. */
     PreferredDeliveryMethod?: PreferredDeliveryMethod;
     /** You can use price levels to specify custom pricing for specific customers. Once you create a price level for a customer, QuickBooks will automatically use the custom price in new invoices, sales receipts, sales orders or credit memos for that customer. You can override this automatic feature, however, when you create the invoices, sales receipts, etc.) The user can now specify a price level on line items in the following supported sales transactions: invoices, sales receipts, credit memos, and sales orders. Notice that the response data for the affected sales transaction does not list the price level that was used. The response simply lists the `Rate` for the item, which was set using the price level. */
@@ -1526,7 +1526,7 @@ export interface CustomerRet {
     /** 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;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export interface CustomerTypeRef {
     /** 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. */
@@ -1631,7 +1631,7 @@ export interface EmployeeAdd {
     /** E-mail address. */
     Email?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** Emergency `Contact` information for the employee. */
     EmergencyContacts?: EmergencyContacts;
     /** `EmployeeType` can affect payroll taxes for an employee. A statutory employee is a person who is defined as an employee by statute. Usually an owner or partner will be on the Other Names list, but if they are on the Employee list, their `EmployeeType` will be Owner. */
@@ -1675,7 +1675,7 @@ export interface EmployeeAdd {
     /** Additional information. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotes?: AdditionalNotes | AdditionalNotes[];
+    AdditionalNotes?: AdditionalNotes | [AdditionalNotes, ...AdditionalNotes[]];
     /** Billing rates are used to override the service item rate in a time transaction (`TimeTrackingAdd`) based on the employee or vendor performing the work. Billing rates are assigned to an employee or a vendor to specify overrides to service items. */
     BillingRateRef?: BillingRateRef;
     /** Pay information for this employee. */
@@ -1698,7 +1698,7 @@ export interface EmployeeAddress {
 export interface EmployeeAddRq {
     EmployeeAdd: EmployeeAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface EmployeeAddRs {
     EmployeeRet?: EmployeeRet;
@@ -1748,7 +1748,7 @@ export interface EmployeeMod {
     /** E-mail address. */
     Email?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** Emergency `Contact` information for the employee. */
     EmergencyContacts?: EmergencyContacts;
     /** `EmployeeType` can affect payroll taxes for an employee. A statutory employee is a person who is defined as an employee by statute. Usually an owner or partner will be on the Other Names list, but if they are on the Employee list, their `EmployeeType` will be Owner. */
@@ -1790,7 +1790,7 @@ export interface EmployeeMod {
     /** Additional information. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotesMod?: AdditionalNotesMod | AdditionalNotesMod[];
+    AdditionalNotesMod?: AdditionalNotesMod | [AdditionalNotesMod, ...AdditionalNotesMod[]];
     /** Billing rates are used to override the service item rate in a time transaction (`TimeTrackingAdd`) based on the employee or vendor performing the work. Billing rates are assigned to an employee or a vendor to specify overrides to service items. */
     BillingRateRef?: BillingRateRef;
     /** Pay information for this employee. */
@@ -1799,7 +1799,7 @@ export interface EmployeeMod {
 export interface EmployeeModRq {
     EmployeeMod: EmployeeMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface EmployeeModRs {
     EmployeeRet?: EmployeeRet;
@@ -1813,7 +1813,7 @@ export interface EmployeePayrollInfo {
     /** If `ClearEarnings` is set to true, the earnings will be deleted for this employee. */
     ClearEarnings?: boolean;
     /** A list of `IEarnings` aggregate objects. If an `EmployeeMod` request does not include any `IEarnings` objects, the earnings table for that employee will not change. If `EmployeeMod` includes at least one `IEarnings` object, all existing earnings information will be deleted for that employee, and all the earnings information in the -Mod request will be added. (To delete all the earnings information, set the `ClearEarnings` field to true in an `EmployeeMod` request.) */
-    Earnings?: Earnings | Earnings[];
+    Earnings?: Earnings | [Earnings, ...Earnings[]];
     /** Indicates whether or not paychecks are generated from time-tracking data. If you include a blank `IsUsingTimeDataToCreatePaychecks` element in an `EmployeeMod` message, you’ll receive an error. */
     IsUsingTimeDataToCreatePaychecks?: boolean;
     /** Indicates whether time data is used to create paychecks for this employee. */
@@ -1831,7 +1831,7 @@ export interface EmployeePayrollInfoMod {
     /** If `ClearEarnings` is set to true, the earnings will be deleted for this employee. */
     ClearEarnings?: boolean;
     /** A list of `IEarnings` aggregate objects. If an `EmployeeMod` request does not include any `IEarnings` objects, the earnings table for that employee will not change. If `EmployeeMod` includes at least one `IEarnings` object, all existing earnings information will be deleted for that employee, and all the earnings information in the -Mod request will be added. (To delete all the earnings information, set the `ClearEarnings` field to true in an `EmployeeMod` request.) */
-    Earnings?: Earnings | Earnings[];
+    Earnings?: Earnings | [Earnings, ...Earnings[]];
     /** Indicates whether or not paychecks are generated from time-tracking data. If you include a blank `IsUsingTimeDataToCreatePaychecks` element in an `EmployeeMod` message, you’ll receive an error. */
     IsUsingTimeDataToCreatePaychecks?: boolean;
     /** Indicates whether time data is used to create paychecks for this employee. */
@@ -1843,9 +1843,9 @@ export interface EmployeePayrollInfoMod {
 }
 export interface EmployeeQueryRq {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
     MaxReturned?: number;
     /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
@@ -1859,12 +1859,12 @@ export interface EmployeeQueryRq {
     /** Filters according to the object’s `Name`. */
     NameRangeFilter?: NameRangeFilter;
     /** You use this if you want to limit the data that will be returned in the response. In this list, you specify the name of each top-level element or aggregate that you want to be returned in the response to the request. You cannot specify fields within an aggregate, for example, you cannot specify a `City` within an `Address`: you must specify `Address` and will get the entire address. The names specified in the list are not parsed, so you must be especially careful to supply valid names, properly cased. No error is returned in the status code if you specify an invalid name. Notice that if you want to return custom data or private data extensions, you must specify the `DataExtRet` element and you must supply the `OwnerID` set to either a value of 0 (custom data) or the GUID for the private data. */
-    IncludeRetElement?: string[] | string;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface EmployeeQueryRs {
-    EmployeeRet?: EmployeeRet | EmployeeRet[];
+    EmployeeRet: [EmployeeRet, ...EmployeeRet[]];
 }
 export interface EmployeeRet {
     /** 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. */
@@ -1918,7 +1918,7 @@ export interface EmployeeRet {
     /** E-mail address. */
     Email?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** Emergency `Contact` information for the employee. */
     EmergencyContacts?: EmergencyContacts;
     /** `EmployeeType` can affect payroll taxes for an employee. A statutory employee is a person who is defined as an employee by statute. Usually an owner or partner will be on the Other Names list, but if they are on the Employee list, their `EmployeeType` will be Owner. */
@@ -1962,7 +1962,7 @@ export interface EmployeeRet {
     /** Additional information. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotesRet?: AdditionalNotesRet | AdditionalNotesRet[];
+    AdditionalNotesRet?: AdditionalNotesRet | [AdditionalNotesRet, ...AdditionalNotesRet[]];
     /** Billing rates are used to override the service item rate in a time transaction (`TimeTrackingAdd`) based on the employee or vendor performing the work. Billing rates are assigned to an employee or a vendor to specify overrides to service items. */
     BillingRateRef?: BillingRateRef;
     /** Pay information for this employee. */
@@ -1970,7 +1970,7 @@ export interface EmployeeRet {
     /** Allows for the attachment of a user defined GUID value. */
     ExternalGUID?: string;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 /** @default: Regular */
 export declare type EmployeeType = "Officer" | "Owner" | "Regular" | "Statutory";
@@ -1978,9 +1978,9 @@ export interface EntityFilter {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Allows you to filter for data that relates to the specified object and its descendants. */
     ListIDWithChildren?: string;
     /** Allows you to filter for data that relates to the specified object and its descendants. For names that do not have children, `FullNameWithChildren` is exactly the same as `FullName`. */
@@ -2066,7 +2066,7 @@ export interface ExpenseLineAdd {
     /** A sales representative must be on the Employee, Vendor, or Other Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     SalesRepRef?: SalesRepRef;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExt?: DataExt | DataExt[];
+    DataExt?: DataExt | [DataExt, ...DataExt[]];
 }
 export interface ExpenseLineMod {
     /** 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.)
@@ -2172,7 +2172,7 @@ export interface ExpenseLineRet {
     /** A sales representative must be on the Employee, Vendor, or Other Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     SalesRepRef?: SalesRepRef;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export declare type Gender = "Female" | "Male";
 export interface IncomeAccountRef {
@@ -2205,7 +2205,7 @@ export interface ItemGroupLineAdd {
     /** Location within the Inventory Site. */
     InventorySiteLocationRef?: InventorySiteLocationRef;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExt?: DataExt | DataExt[];
+    DataExt?: DataExt | [DataExt, ...DataExt[]];
 }
 export interface ItemGroupLineMod {
     /** 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.)
@@ -2221,7 +2221,7 @@ export interface ItemGroupLineMod {
     /** When you modify a transaction line to change the unit of measure used in that line, you use this aggregate to specify the UOM set within which you are choosing an available unit of measure. The “override” here refers to the unit within the set, not the UOM Set itself, which you cannot change or override–the UOM set that can be set or changed only in the item itself via an Item Mod request. */
     OverrideUOMSetRef?: OverrideUOMSetRef;
     /** A list of `IItemLineRet` objects, each representing one line of the item. Each item line is used to track a portion of a transaction that represents the purchase of an “item.” */
-    ItemLineMod?: ItemLineMod | ItemLineMod[];
+    ItemLineMod?: ItemLineMod | [ItemLineMod, ...ItemLineMod[]];
 }
 export interface ItemGroupLineRet {
     /** 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.)
@@ -2241,9 +2241,9 @@ export interface ItemGroupLineRet {
     /** Total amount of money paid or received. In a receive payment add transaction that has payment amount elements (such as `AppliedToTxnAdd` lines) you must supply a `TotalAmount` and the sum of all the `PaymentAmount` elements must not be greater than the `TotalAmount`. */
     TotalAmount: string;
     /** A list of `IItemLineRet` objects, each representing one line of the item. Each item line is used to track a portion of a transaction that represents the purchase of an “item.” */
-    ItemLineRet?: ItemLineRet | ItemLineRet[];
+    ItemLineRet?: ItemLineRet | [ItemLineRet, ...ItemLineRet[]];
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExt?: DataExt | DataExt[];
+    DataExt?: DataExt | [DataExt, ...DataExt[]];
 }
 export interface ItemGroupRef {
     /** 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. */
@@ -2299,7 +2299,7 @@ export interface ItemLineAdd {
     /** A sales representative must be on the Employee, Vendor, or Other Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     SalesRepRef?: SalesRepRef;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExt?: DataExt | DataExt[];
+    DataExt?: DataExt | [DataExt, ...DataExt[]];
 }
 export interface ItemLineMod {
     /** 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.)
@@ -2407,7 +2407,7 @@ export interface ItemLineRet {
     /** A sales representative must be on the Employee, Vendor, or Other Names list within QuickBooks. Sales representative’s names and initials appear on the Rep drop-down list on QuickBooks sales forms. A `SalesRepRef` refers to a person on the `SalesRep` list. In a request, if a `SalesRepRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     SalesRepRef?: SalesRepRef;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export interface ItemRef {
     /** 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. */
@@ -2448,7 +2448,7 @@ export interface ItemServiceAdd {
 export interface ItemServiceAddRq {
     ItemServiceAdd: ItemServiceAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface ItemServiceAddRs {
     ItemServiceRet?: ItemServiceRet;
@@ -2485,7 +2485,7 @@ export interface ItemServiceMod {
 export interface ItemServiceModRq {
     ItemServiceMod: ItemServiceMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface ItemServiceModRs {
     ItemServiceRet?: ItemServiceRet;
@@ -2493,9 +2493,9 @@ export interface ItemServiceModRs {
 }
 export interface ItemServiceQueryRq {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
     MaxReturned?: number;
     /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
@@ -2511,12 +2511,12 @@ export interface ItemServiceQueryRq {
     /** Filters according to the object’s class. */
     ClassFilter?: ClassFilter;
     /** 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;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface ItemServiceQueryRs {
-    ItemServiceRet?: ItemServiceRet | ItemServiceRet[];
+    ItemServiceRet: [ItemServiceRet, ...ItemServiceRet[]];
 }
 export interface ItemServiceRef {
     /** 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. */
@@ -2560,7 +2560,7 @@ export interface ItemServiceRet {
     /** Allows for the attachment of a user defined GUID value. */
     ExternalGUID?: string;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 /** @default: None */
 export declare type JobStatus = "Awarded" | "Closed" | "InProgress" | "None" | "NotAwarded" | "Pending";
@@ -2631,7 +2631,7 @@ export interface JournalEntryAdd {
 export interface JournalEntryAddRq {
     JournalEntryAdd: JournalEntryAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface JournalEntryAddRs {
     JournalEntryRet?: JournalEntryRet;
@@ -2655,12 +2655,12 @@ export interface JournalEntryMod {
     /** 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;
     /** `IORJournalLineList` The list of journal lines in a `JournalMod` request – note that in a mod request, inclding one line means that you must include all lines, modified or not. */
-    JournalLineMod?: JournalLineMod | JournalLineMod[];
+    JournalLineMod?: JournalLineMod | [JournalLineMod, ...JournalLineMod[]];
 }
 export interface JournalEntryModRq {
     JournalEntryMod: JournalEntryMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface JournalEntryModRs {
     JournalEntryRet?: JournalEntryRet;
@@ -2668,11 +2668,11 @@ export interface JournalEntryModRs {
 }
 export interface JournalEntryQueryRq {
     /** 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;
+    TxnID?: string | [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;
+    RefNumber?: string | [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;
+    RefNumberCaseSensitive?: string | [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.) */
@@ -2692,12 +2692,12 @@ export interface JournalEntryQueryRq {
     /** 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;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface JournalEntryQueryRs {
-    JournalEntryRet?: JournalEntryRet | JournalEntryRet[];
+    JournalEntryRet: [JournalEntryRet, ...JournalEntryRet[]];
 }
 export interface JournalEntryRet {
     /** 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. */
@@ -2731,7 +2731,7 @@ export interface JournalEntryRet {
     /** If no amount is included in the first credit line (or debit line) of a journal entry in the QuickBooks user interface, then subsequent SDK queries on that `JournalEntry` object will fail XML validation. */
     JournalCreditLine?: JournalCreditLine;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export interface JournalLineMod {
     /** 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. */
@@ -3145,7 +3145,7 @@ export interface TimeTrackingAdd {
 export interface TimeTrackingAddRq {
     TimeTrackingAdd: TimeTrackingAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface TimeTrackingAddRs {
     TimeTrackingRet?: TimeTrackingRet;
@@ -3153,9 +3153,9 @@ export interface TimeTrackingAddRs {
 }
 export interface TimeTrackingEntityFilter {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
 }
 export interface TimeTrackingMod {
     /** 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. */
@@ -3184,7 +3184,7 @@ export interface TimeTrackingMod {
 export interface TimeTrackingModRq {
     TimeTrackingMod: TimeTrackingMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface TimeTrackingModRs {
     TimeTrackingRet?: TimeTrackingRet;
@@ -3192,7 +3192,7 @@ export interface TimeTrackingModRs {
 }
 export interface TimeTrackingQueryRq {
     /** 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;
+    TxnID?: string | [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.) */
@@ -3202,10 +3202,10 @@ export interface TimeTrackingQueryRq {
     /** Allows you to query for one or more names on the QuickBooks Vendor list, Employee list, or Other Names list. */
     TimeTrackingEntityFilter?: TimeTrackingEntityFilter;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface TimeTrackingQueryRs {
-    TimeTrackingRet?: TimeTrackingRet | TimeTrackingRet[];
+    TimeTrackingRet: [TimeTrackingRet, ...TimeTrackingRet[]];
 }
 export interface TimeTrackingRet {
     /** 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. */
@@ -3329,9 +3329,9 @@ export interface VendorAdd {
     /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
     AltContact?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** A list of contact records. */
-    Contacts?: Contacts | Contacts[];
+    Contacts?: Contacts | [Contacts, ...Contacts[]];
     /** The vendor’s name as it will appear on checks sent to the vendor. (Corresponds in the QuickBooks user interface to the “Print on Check as” field of the Edit Vendor and New Vendor windows.) */
     NameOnCheck?: string;
     /** Account numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs. If the `IsUsingAccountNumber` preference is false (that is, if the QuickBooks user has the account numbers Preference turned off), you can still set account numbers through the SDK, but the numbers will not be visible in the user interface. */
@@ -3339,7 +3339,7 @@ export interface VendorAdd {
     /** Additional information about this vendor. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotes?: AdditionalNotes | AdditionalNotes[];
+    AdditionalNotes?: AdditionalNotes | [AdditionalNotes, ...AdditionalNotes[]];
     /** Vendor types allow business owners to categorize vendors in ways that are meaningful for their businesses. For example, a vendor type might indicate which industry a vendor represents, or which part of the country a vendor is in. A `VendorTypeRef` aggregate refers to one of the types on the `VendorType` list. In a request, if a `VendorTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     VendorTypeRef?: VendorTypeRef;
     /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
@@ -3381,7 +3381,7 @@ export interface VendorAdd {
     /** For vendor in CA or UK, is there tax charged on top of tax. */
     IsTaxOnTax?: boolean;
     /** Expense account to prefill when you enter bills for this vendor. */
-    PrefillAccountRef?: PrefillAccountRef | PrefillAccountRef[];
+    PrefillAccountRef?: PrefillAccountRef | [PrefillAccountRef, ...PrefillAccountRef[]];
     /** 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;
 }
@@ -3422,7 +3422,7 @@ export interface VendorAddressBlock {
 export interface VendorAddRq {
     VendorAdd: VendorAdd;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface VendorAddRs {
     VendorRet?: VendorRet;
@@ -3470,9 +3470,9 @@ export interface VendorMod {
     /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
     AltContact?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** A list of contact records. */
-    ContactsMod?: ContactsMod | ContactsMod[];
+    ContactsMod?: ContactsMod | [ContactsMod, ...ContactsMod[]];
     /** The vendor’s name as it will appear on checks sent to the vendor. (Corresponds in the QuickBooks user interface to the “Print on Check as” field of the Edit Vendor and New Vendor windows.) */
     NameOnCheck?: string;
     /** Account numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs. If the `IsUsingAccountNumber` preference is false (that is, if the QuickBooks user has the account numbers Preference turned off), you can still set account numbers through the SDK, but the numbers will not be visible in the user interface. */
@@ -3480,7 +3480,7 @@ export interface VendorMod {
     /** Additional information about this vendor. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotesMod?: AdditionalNotesMod | AdditionalNotesMod[];
+    AdditionalNotesMod?: AdditionalNotesMod | [AdditionalNotesMod, ...AdditionalNotesMod[]];
     /** Vendor types allow business owners to categorize vendors in ways that are meaningful for their businesses. For example, a vendor type might indicate which industry a vendor represents, or which part of the country a vendor is in. A `VendorTypeRef` aggregate refers to one of the types on the `VendorType` list. In a request, if a `VendorTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     VendorTypeRef?: VendorTypeRef;
     /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
@@ -3516,14 +3516,14 @@ export interface VendorMod {
     /** For vendor in CA or UK, is there tax charged on top of tax. */
     IsTaxOnTax?: boolean;
     /** Expense account to prefill when you enter bills for this vendor. */
-    PrefillAccountRef?: PrefillAccountRef | PrefillAccountRef[];
+    PrefillAccountRef?: PrefillAccountRef | [PrefillAccountRef, ...PrefillAccountRef[]];
     /** The currency object contains all of the information needed by QuickBooks to display and use. For built-in currencies, the name and currency code values are internationally accepted values and thus are not editable. The comma format is editable, as is the `IsActive` status. For user-defined currencies, every value in the object is editable including name and currency code. When used with `PriceLevels`, the `CurrencyRef` should only be used with “per item” price levels. */
     CurrencyRef?: CurrencyRef;
 }
 export interface VendorModRq {
     VendorMod: VendorMod;
     /** 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;
+    IncludeRetElement?: string | [string, ...string[]];
 }
 export interface VendorModRs {
     VendorRet?: VendorRet;
@@ -3531,9 +3531,9 @@ export interface VendorModRs {
 }
 export interface VendorQueryRq {
     /** 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;
+    ListID?: string | [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;
+    FullName?: string | [string, ...string[]];
     /** Limits the number of objects that a query returns. (To get a count of how many objects could possibly be returned, use the `metaData` query attribute.) If you include a `MaxReturned` value, it must be at least 1. */
     MaxReturned?: number;
     /** Used in filters to select list objects based on whether or not they are currently enabled for use by QuickBooks. The default value is `asActiveOnly`, which selects only list objects that are active. */
@@ -3553,12 +3553,12 @@ export interface VendorQueryRq {
     /** Filter according to class. */
     ClassFilter?: ClassFilter;
     /** 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;
+    IncludeRetElement?: string | [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;
+    OwnerID?: string | [string, ...string[]];
 }
 export interface VendorQueryRs {
-    VendorRet?: VendorRet | VendorRet[];
+    VendorRet: [VendorRet, ...VendorRet[]];
 }
 export interface VendorRef {
     /** 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. */
@@ -3616,9 +3616,9 @@ export interface VendorRet {
     /** The name of an alternate contact person for a vendor, customer, or “other name” entry. */
     AltContact?: string;
     /** List of additional contacts. */
-    AdditionalContactRef?: AdditionalContactRef | AdditionalContactRef[];
+    AdditionalContactRef?: AdditionalContactRef | [AdditionalContactRef, ...AdditionalContactRef[]];
     /** A list of contact records. */
-    ContactsRet?: ContactsRet | ContactsRet[];
+    ContactsRet?: ContactsRet | [ContactsRet, ...ContactsRet[]];
     /** The vendor’s name as it will appear on checks sent to the vendor. (Corresponds in the QuickBooks user interface to the “Print on Check as” field of the Edit Vendor and New Vendor windows.) */
     NameOnCheck?: string;
     /** Account numbers appear in the QuickBooks chart of accounts, Account fields, and reports and graphs. If the `IsUsingAccountNumber` preference is false (that is, if the QuickBooks user has the account numbers Preference turned off), you can still set account numbers through the SDK, but the numbers will not be visible in the user interface. */
@@ -3626,7 +3626,7 @@ export interface VendorRet {
     /** Additional information about this vendor. */
     Notes?: string;
     /** List of notes. */
-    AdditionalNotesRet?: AdditionalNotesRet | AdditionalNotesRet[];
+    AdditionalNotesRet?: AdditionalNotesRet | [AdditionalNotesRet, ...AdditionalNotesRet[]];
     /** Vendor types allow business owners to categorize vendors in ways that are meaningful for their businesses. For example, a vendor type might indicate which industry a vendor represents, or which part of the country a vendor is in. A `VendorTypeRef` aggregate refers to one of the types on the `VendorType` list. In a request, if a `VendorTypeRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
     VendorTypeRef?: VendorTypeRef;
     /** Refers to the payment terms associated with this entity. (This will be an item on the `DateDrivenTerms` or `StandardTerms` list.) If a `TermsRef` aggregate includes both `FullName` and `ListID`, `FullName` will be ignored. */
@@ -3666,11 +3666,11 @@ export interface VendorRet {
     /** For vendor in CA or UK, is there tax charged on top of tax. */
     IsTaxOnTax?: boolean;
     /** Expense account to prefill when you enter bills for this vendor. */
-    PrefillAccountRef?: PrefillAccountRef | PrefillAccountRef[];
+    PrefillAccountRef?: PrefillAccountRef | [PrefillAccountRef, ...PrefillAccountRef[]];
     /** 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;
     /** A list of `IDataExtRet` objects, each of which represents a field that has been added to QuickBooks as a data extension. */
-    DataExtRet?: DataExtRet | DataExtRet[];
+    DataExtRet?: DataExtRet | [DataExtRet, ...DataExtRet[]];
 }
 export interface VendorTypeRef {
     /** 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. */