Wiresk

Wiresk

QuickBooks – Create, Update, Upsert records

Estimated reading time: 97 min

What your automation will do…

A connection to your QuickBooks account is needed so we can sync it with our platform.
Refer to QuickBooks – connection.
You can include between 1 and 255 Methods to build complex Flows.
QUICKBOOK
This unified Method is used to create various Records in a specific Entity.
 
This Method allows you to create: 
Invoice, Item, Payment, Journal Entry, Bill, Sale Receipt, Estimate, Deposit, Credit Memo, Purchase Order, Customer, Vendor, Account, Purchase, Time Activity, Refund Receipt. 

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*Create
Connection*Select your connection or create one.
Entity*
(Set of data that contain records)		Select the available Entity to create records:

Invoice, Item, Payment, Journal Entry, Bill, Sale Receipt, Estimate, Deposit, Credit Memo, Purchase Order, Customer, Vendor, Account, Purchase, Time Activity, Refund Receipt.

(*) required field

Configuration table for each Entity:

An Invoice represents a sales form where the customer pays for a product or service later.
 
Note:
▪️ Have at least one Line a sales item or inline subtotal.
▪️ The DocNumber attribute is populated automatically by the data service if not supplied.
▪️ If ShipAddr, BillAddr, or both are not provided, the appropriate customer address from the referenced Customer object is used to fill those values.
 
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Invoice API Reference. 
MAP FIELDS [+ Add Field] Select fields from a list, to configure the invoice creation.
Additional fields: Sales Term Reference, Transaction Date, Customer Memo, Transaction Tax Detail, Deposit, Line, DocNumber.
Customer Reference*A customer is a consumer of the service or product that your business offers.
Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line*
Invoice line object.
If the transaction is taxable there is a limit of 750 lines per transaction.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Invoice Line.

Detail Type*: Possible choices for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to the Detail Type.

Description: Free form text description of the line item that appears in the printed record.
Max character: 4000.

Line Number: Specifies the position of the line in the collection of transaction lines.

Sale Item Line Detail [+ Add Field] add more fields in Sale Item Line Detail:
_ Quantity: Number of items for the line.
_ Unit Price: Unit price of the subject item as referenced by ItemRef.

_ Discount Amount: Fixed discount.
_ Discount Rate: The discount rate applied to this line. If both Discount are provided, Discount Rate takes precedence and Discount Amount is recalculated by QuickBooks services based on amount of Discount Rate.

_ Item Reference: Reference to an Item object.
[+ Add Field] add more fields in Item reference:
___ Item ID: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Tax Code Reference: Reference to the Tax Code for this item.
[+ Add Field] add more fields in Tax Code Reference:
___ Value: The ID for the referenced Tax Code.
___ Name: Name derived from the field that holds the common name of that Tax Code.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Sales Term ReferenceReference to the sales term associated with the transaction.

Value: The ID for the referenced Sales Term.
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Customer Memo
Max 1000 chars.		Value: User’s message to the customer; this message is visible to the end user on their transactions.
Transaction Tax DetailThis data type provides information for taxes charged on the transaction as a whole. It captures the details sales taxes calculated for the transaction based on the tax codes referenced by the transaction.

Transaction Tax Code Reference:
_ Value: Reference to the transaction tax code.

See Global tax model for more information about this element.
DepositThe deposit made towards this invoice.
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.
Response sample from Create Invoice 
{
  "Invoice": {
    "TxnDate": "2015-07-24", 
    "domain": "QBO", 
    "PrintStatus": "NeedToPrint", 
    "TotalAmt": 100.0, 
    "Line": [
      {
        "LineNum": 1, 
        "Amount": 100.0, 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "ItemRef": {
            "name": "Services", 
            "value": "1"
          }
        }, 
        "Id": "1", 
        "DetailType": "SalesItemLineDetail"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 100.0, 
        "SubTotalLineDetail": {}
      }
    ], 
    "DueDate": "2015-08-23", 
    "ApplyTaxAfterDiscount": false, 
    "DocNumber": "1069", 
    "sparse": false, 
    "ProjectRef": {
      "value": "39298034"
    }, 
    "Deposit": 0, 
    "Balance": 100.0, 
    "CustomerRef": {
      "name": "Amy's Bird Sanctuary", 
      "value": "1"
    }, 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "SyncToken": "0", 
    "LinkedTxn": [], 
    "ShipAddr": {
      "City": "Bayshore", 
      "Line1": "4581 Finch St.", 
      "PostalCode": "94326", 
      "Lat": "INVALID", 
      "Long": "INVALID", 
      "CountrySubDivisionCode": "CA", 
      "Id": "109"
    }, 
    "EmailStatus": "NotSet", 
    "BillAddr": {
      "City": "Bayshore", 
      "Line1": "4581 Finch St.", 
      "PostalCode": "94326", 
      "Lat": "INVALID", 
      "Long": "INVALID", 
      "CountrySubDivisionCode": "CA", 
      "Id": "2"
    }, 
    "MetaData": {
      "CreateTime": "2015-07-24T10:33:39-07:00", 
      "LastUpdatedTime": "2015-07-24T10:33:39-07:00"
    }, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "Id": "238"
  }, 
  "time": "2015-07-24T10:33:39.11-07:00"
}
Expand
An item is a thing that your company buys, sells, or re-sells, such as products and services. An item is shown as a line on an invoice or other sales form. 
 
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Item API Reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Item creation.
Additional fields: Active, SKU, Unit Price, TrackQtyOnHand, QtyOnHand, AssetAccountRef, InvStartDate, ExpenseAccountRef.
Name*
Maximum of 100 chars		Name of the item. This value must be unique, at least one character in length, and cannot include tabs, new lines, or colons. Required for create.
IncomeAccountRef*Reference to the posting account, that is, the account that records the proceeds from the sale of this item. Must be an account with account type of Sales of Product Income.

Account ID*: The ID for the referenced Income Account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Type*Classification that specifies the use of this item:
Inventory - Service - Non inventory

See the description at the top of the Item entity page for details about supported item types.
ADDITIONAL FIELDS
ActiveTrue – False
Inactivating an item is achieved by setting the Active attribute to false.
SKUThe stock keeping unit (SKU) for this Item. This is a company-defined identifier for an item or product used in tracking inventory.

maximum of 100 chars.
minorVersion: 4
Unit PricePrice of the item.
TrackQtyOnHandTrue - False
QtyOnHandCurrent quantity of the Inventory items available for sale.
Not used for Service or NonInventory type items.Required for Inventory type items.
AssetAccountRefReference to the Inventory Asset account that tracks the current value of the inventory. If the same account is used for all inventory items, the current balance of this account will represent the current total value of the inventory. Must be an account with account type of Other Current Asset.

Use Account.Id and Account.Name from that object for AssetAccountRef.value and AssetAccountRef.name, respectively. Required for Inventory item types.

Account ID*: The ID for the referenced asset account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
InvStartDateDate of opening balance for the inventory transaction. Required when creating an Item.Type=Inventory. Required for Inventory item types.

Local timezone: YYYY-MM-DD UTC: YYYY-MM-DDZ Specific time zone: YYYY-MM-DD+/-HH:MM
The date format follows the XML Schema standard.
ExpenseAccountRefReference to the expense account used to pay the vendor for this item. Must be an account with account type of Cost of Goods Sold.

Account ID*: The ID for the referenced expense account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

(*) required field

Response sample from Create Item 
{
  "Item": {
    "FullyQualifiedName": "Garden Supplies", 
    "domain": "QBO", 
    "Id": "19", 
    "Name": "Garden Supplies", 
    "TrackQtyOnHand": true, 
    "UnitPrice": 0, 
    "PurchaseCost": 0, 
    "QtyOnHand": 10, 
    "IncomeAccountRef": {
      "name": "Sales of Product Income", 
      "value": "79"
    }, 
    "AssetAccountRef": {
      "name": "Inventory Asset", 
      "value": "81"
    }, 
    "Taxable": false, 
    "sparse": false, 
    "Active": true, 
    "SyncToken": "0", 
    "InvStartDate": "2015-01-01", 
    "Type": "Inventory", 
    "ExpenseAccountRef": {
      "name": "Cost of Goods Sold", 
      "value": "80"
    }, 
    "MetaData": {
      "CreateTime": "2015-12-09T11:12:39-08:00", 
      "LastUpdatedTime": "2015-12-09T11:12:41-08:00"
    }
  }, 
  "time": "2015-12-09T11:12:39.748-08:00"
}
Expand
A Payment object records a payment in QuickBooks. The payment can be applied for a particular customer against multiple Invoices and Credit Memos. It can also be created without any Invoice or Credit Memo, by just specifying an amount. 
 
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Payment API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Payment creation.
Additional fields: Currency Reference, Project Reference, Line.
Total amount*Indicates the total amount of the transaction. This includes the total of all the charges, allowances, and taxes.

If you process a linked refund transaction against a specific transaction, the totalAmt value won’t change. It will remain the same. However, voiding the linked refund will change the totalAmt value to 0.
Customer reference*Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Currency ReferenceReference to the currency in which all amounts on the associated transaction are expressed. This must be defined if multi-currency is enabled for the company. Read more about multi-currency support here.

Currency ID: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency.
Project referenceReference to the Project ID associated with this transaction.

Project ID: The ID for the referenced Project.
Name: Name derived from the field that holds the common name of that project.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line
Zero or more transactions accounting for this payment.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Payment Line can be added as elements.

Element 1: Represents the first Payment Line.

Amount*: The amount of the line item.

Linked Transaction*: Transaction to which the current entity is related. For example, a billpayment line links to the originating bill object for which the billpayment is applied.

_ Transaction ID*: Transaction id of the related transaction.
_ Transaction Type*: Possible values:
Expense
Check
Credit Card Credit
Journal Entry
Credit Memo
Invoice

(*) required field

Response sample from Create Payment 
{
  "Payment": {
    "SyncToken": "0", 
    "domain": "QBO", 
    "DepositToAccountRef": {
      "value": "4"
    }, 
    "UnappliedAmt": 25.0, 
    "TxnDate": "2014-12-30", 
    "TotalAmt": 25.0, 
    "ProjectRef": {
      "value": "39298034"
    }, 
    "ProcessPayment": false, 
    "sparse": false, 
    "Line": [], 
    "CustomerRef": {
      "name": "Red Rock Diner", 
      "value": "20"
    }, 
    "Id": "154", 
    "MetaData": {
      "CreateTime": "2014-12-30T10:26:03-08:00", 
      "LastUpdatedTime": "2014-12-30T10:26:03-08:00"
    }
  }, 
  "time": "2014-12-30T10:26:03.668-08:00"
}
Expand

Create Journal Entry Copy Link

Journal Entry is a transaction in which: 
▪️ There are at least one pair of lines, a debit and a credit, called distribution lines. 
▪️ Each distribution line has an account from the Chart of Accounts. Query the Account resource for a listing of the Chart of Accounts. 
▪️ The total of the debit column equals the total of the credit column. 
 
When you record a transaction with a JournalEntry object, the QuickBooks Online UI labels the transaction as JRNL in the register and as General Journal on reports that list transactions. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Journal Entry API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Journal Entry creation.
Additional fields: DocNumber.
Line*
Individual line items of a transaction.
There must be at least one pair of Journal Entry Line elements, representing a debit and a credit, called distribution lines.
Set Line Detail Type to Journal Entry Line for both lines.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Journal Entry Line can be added as elements.

Element 1: Represents the first Journal Entry Line.

Detail Type*: Set to Journal Entry Line Detail.

Amount*: The amount of the line item.

Journal Entry Line Detail*:
_ Posting Type*: Indicates whether this Journal Entry line is a Debit or Credit.

_ Account Reference*: Reference to the account associated with this line.
___ Value*: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
⚠️ If this account has same location as specified in the transaction by the TransactionLocationType attribute and the same VAT as in the line item TaxCodeRef attribute, then this account is used.
⚠️ If there is a mismatch, then the account from the account category list that matches the transaction location and VAT is used.
⚠️ If this account is not present in the account category list, then a new account is created with the new location, new VAT code, and all other attributes as in the default account.


Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.
ADDITIONAL FIELDS
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response sample from Create Journal Entry 
{
  "time": "2015-06-29T12:45:32.183-07:00", 
  "JournalEntry": {
    "SyncToken": "0", 
    "domain": "QBO", 
    "TxnDate": "2015-06-29", 
    "sparse": false, 
    "Line": [
      {
        "JournalEntryLineDetail": {
          "PostingType": "Debit", 
          "AccountRef": {
            "name": "Truck:Depreciation", 
            "value": "39"
          }
        }, 
        "DetailType": "JournalEntryLineDetail", 
        "Amount": 100.0, 
        "Id": "0", 
        "Description": "nov portion of rider insurance"
      }, 
      {
        "JournalEntryLineDetail": {
          "PostingType": "Credit", 
          "AccountRef": {
            "name": "Notes Payable", 
            "value": "44"
          }
        }, 
        "DetailType": "JournalEntryLineDetail", 
        "Amount": 100.0, 
        "Id": "1", 
        "Description": "nov portion of rider insurance"
      }
    ], 
    "Adjustment": false, 
    "Id": "228", 
    "TxnTaxDetail": {}, 
    "MetaData": {
      "CreateTime": "2015-06-29T12:45:32-07:00", 
      "LastUpdatedTime": "2015-06-29T12:45:32-07:00"
    }
  }
}
Expand
A Bill object is an AP transaction representing a request-for-payment from a third party for goods/services rendered, received, or both. 
  
When creating a bill, only certain transaction types can be linked. The most commonly supported transaction types include: 
▪️ BillPaymentCheck – A payment made by check to pay the bill. 
▪️ BillPaymentCreditCard – A payment made by credit card to pay the bill. 
▪️ CreditMemo – A credit memo applied to the bill. 
▪️ JournalEntry – A journal entry affecting the bill. 
 
Transactions like Invoice and Deposit are not typically linked to a bill because a bill represents an expense or liability, while invoices are accounts receivable (money owed to you, not by you). Deposits usually relate to received funds, not expenses. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Bill API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Bill creation.
Additional fields: Currency Reference, Ap Account Reference, Sales Term Reference, Linked Transaction, DocNumber.
Vendors Reference*Reference to the vendor for this transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*: Possible choices for each line:
Account Based Expense Line Detail – Item based Expense Line Detail

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to Detail Type.

Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.

Account Based Expense Line Detail:

_ Account Reference: Reference to the Expense account associated with this item.
___ Account ID: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
⚠️ If this account has same location as specified in the transaction by the TransactionLocationType attribute and the same VAT as in the line item TaxCodeRef attribute, then this account is used.
⚠️ If there is a mismatch, then the account from the account category list that matches the transaction location and VAT is used.
⚠️ If this account is not present in the account category list, then a new account is created with the new location, new VAT code, and all other attributes as in the default account.

Item based Expense Line Detail:
_ Quantity: Number of items for the line.
_ Unit Price: Unit price of the subject item.

_ Item Reference: : Reference to the Item.
___ Value: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference: Reference to a customer or job. 
___ Value: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Currency ReferenceReference to the currency in which all amounts on the associated transaction are expressed. This must be defined if multi-currency is enabled for the company. Read more about multi-currency support here.

[+ Add Field] add more fields:
Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency.
Ap Account ReferenceSpecifies to which AP account the bill is credited. 

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

⚠️ The specified account must have Account.Classification set to Liability and Account.AccountSubType set to AccountsPayable. If the company has a single AP account, the account is implied. However, it is recommended that the AP Account be explicitly specified in all cases to prevent unexpected errors when relating transactions to each other.
Sales Term ReferenceReference to the Term associated with the transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced sales term.
Name: Name derived from the field that holds the common name of that sales term.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Linked TransactionZero or more transactions linked to this Bill object.

[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Linked Transaction can be added as elements.

Element 1: Represents the first Linked Transaction.

Transaction ID: Unique identifier of the related transaction.
Transaction Type: Possible values:
BillPaymentCheck – A payment made by check to pay the bill.
BillPaymentCreditCard – A payment made by credit card to pay the bill.
CreditMemo – A credit memo applied to the bill.
JournalEntry – A journal entry affecting the bill.
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response Sample from Create Bill 
{
  "Bill": {
    "SyncToken": "0", 
    "domain": "QBO", 
    "VendorRef": {
      "name": "Bob's Burger Joint", 
      "value": "56"
    }, 
    "TxnDate": "2014-12-31", 
    "TotalAmt": 200.0, 
    "APAccountRef": {
      "name": "Accounts Payable (A/P)", 
      "value": "33"
    }, 
    "Id": "151", 
    "sparse": false, 
    "Line": [
      {
        "DetailType": "AccountBasedExpenseLineDetail", 
        "Amount": 200.0, 
        "Id": "1", 
        "AccountBasedExpenseLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "AccountRef": {
            "name": "Advertising", 
            "value": "7"
          }, 
          "BillableStatus": "NotBillable"
        }
      }
    ], 
    "Balance": 200.0, 
    "DueDate": "2014-12-31", 
    "MetaData": {
      "CreateTime": "2014-12-31T09:59:18-08:00", 
      "LastUpdatedTime": "2014-12-31T09:59:18-08:00"
    }
  }, 
  "time": "2014-12-31T09:59:17.449-08:00"
}
Expand
A Sales Receipt object represents a receipt issued to a customer upon payment for goods or services. It functions similarly to an invoice, but payment is received concurrently with the sale. 
The receipt specifies a deposit account for the received funds. If no deposit account is designated, the payment is directed to the Undeposited Account. 
 
▪️ A SalesReceipt object must have at least one line that describes an item and an amount. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Sales Receipt API reference. 
 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Sale Receipt creation.
Additional fields: DocNumber.
Line*
The minimum line item required for the request is Sales Item Line or Group Line.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type* Possible values for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

Sale Item Line Detail*:
_ Item Reference*: : Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Unit Price: Unit price of the subject item as referenced by ItemRef.

_ Quantity: Number of items for the line.

_ Tax Code Reference: Reference to the TaxCode for this item. 
[+ Add Field] add more fields:
___ Value: The ID for the referenced Tax Code.

[+ Add Field] add more fields:
Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.
ADDITIONAL FIELDS
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response Sample from Create Sale Receipt 
{
  "SalesReceipt": {
    "DocNumber": "1074", 
    "SyncToken": "0", 
    "domain": "QBO", 
    "Balance": 0, 
    "DepositToAccountRef": {
      "name": "Undeposited Funds", 
      "value": "4"
    }, 
    "TxnDate": "2015-07-29", 
    "TotalAmt": 35.0, 
    "PrintStatus": "NeedToPrint", 
    "EmailStatus": "NotSet", 
    "sparse": false, 
    "Line": [
      {
        "Description": "Pest Control Services", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 1, 
          "UnitPrice": 35, 
          "ItemRef": {
            "name": "Pest Control", 
            "value": "10"
          }
        }, 
        "LineNum": 1, 
        "Amount": 35.0, 
        "Id": "1"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 35.0, 
        "SubTotalLineDetail": {}
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "Id": "263", 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "MetaData": {
      "CreateTime": "2015-07-29T09:25:02-07:00", 
      "LastUpdatedTime": "2015-07-29T09:25:02-07:00"
    }
  }, 
  "time": "2015-07-29T09:25:04.214-07:00"
}
Expand
An Estimate is a document a business provides to a customer outlining the proposed costs for goods or services. It essentially presents a price quote for the customer’s consideration. 
 
▪️ An Estimate must have at least one line that describes an item. 
▪️ An Estimate must have a reference to a customer. 
▪️ If shipping address and billing address are not provided, the address from the referenced Customer object is used. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Estimate API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Estimate creation.
Additional fields: Shipping Address, Customer Reference, Apply Tax After Discount.
Customer Reference*Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Bill Email*Identifies the e-mail address where the estimate is sent.

Address*: An email address. The address format must follow the RFC 822 standard.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type* Possible values :
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

Sale Item Line Detail*:
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

[+ Add Field] add more fields:
_ Unit Price: Unit price of the subject item as referenced by ItemRef.
_ Quantity: Number of items for the line.
_ Tax Code Reference: Reference to the TaxCode for this item. 
[+ Add Field] add more fields:
___ Value: The ID for the referenced Tax Code.
ADDITIONAL FIELDS
Customer MemoValue*: User’s message to the customer; this message is visible to the end user on their transactions.
Max 1000 chars.
Shipping AddressThis field indicates the shipping address for the goods. If no specific shipping address is provided, QuickBooks will automatically use the default shipping address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

[+ Add Field] add more fields:
City
Line1
Postal Code
Latitude
longitude
Country Sub Division Code
Apply Tax After Discount
apply to USA.		If false or null, calculate the sales tax first, and then apply the discount. If true, subtract the discount first and then calculate the sales tax.

(*) required field

Response Sample from Create Estimate 
{
  "Estimate": {
    "DocNumber": "1001", 
    "SyncToken": "0", 
    "domain": "QBO", 
    "TxnStatus": "Pending", 
    "BillEmail": {
      "Address": "Cool_Cars@intuit.com"
    }, 
    "TxnDate": "2015-03-26", 
    "TotalAmt": 31.5, 
    "CustomerRef": {
      "name": "Cool Cars", 
      "value": "3"
    }, 
    "CustomerMemo": {
      "value": "Thank you for your business and have a great day!"
    }, 
    "ShipAddr": {
      "CountrySubDivisionCode": "CA", 
      "City": "Half Moon Bay", 
      "PostalCode": "94213", 
      "Id": "104", 
      "Line1": "65 Ocean Dr."
    }, 
    "ProjectRef": {
      "value": "39298034"
    }, 
    "PrintStatus": "NeedToPrint", 
    "BillAddr": {
      "CountrySubDivisionCode": "CA", 
      "City": "Half Moon Bay", 
      "PostalCode": "94213", 
      "Id": "103", 
      "Line1": "65 Ocean Dr."
    }, 
    "sparse": false, 
    "EmailStatus": "NotSet", 
    "Line": [
      {
        "Description": "Pest Control Services", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 1, 
          "UnitPrice": 35, 
          "ItemRef": {
            "name": "Pest Control", 
            "value": "10"
          }
        }, 
        "LineNum": 1, 
        "Amount": 35.0, 
        "Id": "1"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 35.0, 
        "SubTotalLineDetail": {}
      }, 
      {
        "DetailType": "DiscountLineDetail", 
        "Amount": 3.5, 
        "DiscountLineDetail": {
          "DiscountAccountRef": {
            "name": "Discounts given", 
            "value": "86"
          }, 
          "PercentBased": true, 
          "DiscountPercent": 10
        }
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "Id": "177", 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "MetaData": {
      "CreateTime": "2015-03-26T13:25:05-07:00", 
      "LastUpdatedTime": "2015-03-26T13:25:05-07:00"
    }
  }, 
  "time": "2015-03-26T13:25:05.473-07:00"
}
Expand
A deposit represents a transaction that combines one or more of the following: 
▪️ Customer payments previously held in the ‘Undeposited Funds’ account, now transferred to the designated Asset Account. This information is linked using the Deposit.line.LinkedTxn element. 
▪️ New direct deposits, detailed within the Deposit.Line.DepositLineDetail section. 
  
A deposit must include at least one deposit line, which can be either a direct deposit or a deposit linked to a previous transaction. 
Multiple deposit lines of different types can be included in a single request. 
 
For a direct deposit, each line must specify: 
▪️ The target account (Deposit.Line.DepositLineDetail.AccountRef). 
▪️ The overall deposit destination account (Deposit.DepositToAccountRef). 
 
For a deposit linked to a previous transaction, each line must specify: 
▪️ The linked transaction (Deposit.Line.LinkedTxn). 
▪️ The overall deposit destination account (Deposit.DepositToAccountRef). 
  
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Deposit API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Deposit creation.
Additional fields: Deposit to Account Reference.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*: Possible values : Deposit Line detail.

Amount*: The amount of the deposit.

Deposit Line Detail*:
_ Account Reference*: Account where the funds are deposited.
___ Value*: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Deposit to Account ReferenceIdentifies the account to be used for this deposit.

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

(*) required field

Response Sample from Create Deposit 
{
  "Deposit": {
    "SyncToken": "0", 
    "domain": "QBO", 
    "DepositToAccountRef": {
      "name": "Checking", 
      "value": "35"
    }, 
    "TxnDate": "2014-12-22", 
    "TotalAmt": 20.0, 
    "sparse": false, 
    "Line": [
      {
        "DetailType": "DepositLineDetail", 
        "ProjectRef": {
          "value": "42991284"
        }, 
        "LineNum": 1, 
        "Amount": 20.0, 
        "Id": "1", 
        "DepositLineDetail": {
          "AccountRef": {
            "name": "Unapplied Cash Payment Income", 
            "value": "87"
          }
        }
      }
    ], 
    "Id": "149", 
    "MetaData": {
      "CreateTime": "2014-12-22T14:46:36-08:00", 
      "LastUpdatedTime": "2014-12-22T14:46:36-08:00"
    }
  }, 
  "time": "2014-12-22T14:46:36.084-08:00"
}
Expand
A Credit Memo is a type of financial transaction used to record the return of money to a customer, typically for a prior purchase or payment. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Credit Memo API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Credit Memo creation.
Additional fields: Customer Reference, Bill Email, Customer Memo, Bill Address, Shipping Address.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*: Possible values:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the credit memo.

Sales Item Line Detail*:
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Customer Reference*Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Bill EmailIdentifies the e-mail address where the estimate is sent.

[+ Add Field] add more fields:
Address*: An email address. The address format must follow the RFC 822 standard.’
Customer Memo[+ Add Field] add more fields:
Value: User’s message to the customer; this message is visible to the end user on their transactions.
Max 1000 chars.
Bill AddressBill-to address of the credit memo. If no specific bill address is provided, QuickBooks will automatically use the default billing address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

[+ Add Field] add more fields:
Line1
Line2
Line3
Line4
Shipping AddressThis field indicates the shipping address for the goods. If no specific shipping address is provided, QuickBooks will automatically use the default shipping address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

[+ Add Field] add more fields:
Country Sub Division Code
City
Postal Code
line1

(*) required field

Response Sample from Create Credit Memo 
{
  "CreditMemo": {
    "DocNumber": "1039", 
    "SyncToken": "0", 
    "domain": "QBO", 
    "Balance": 50.0, 
    "BillAddr": {
      "City": "Half Moon Bay", 
      "Line1": "65 Ocean Dr.", 
      "PostalCode": "94213", 
      "Lat": "37.4300318", 
      "Long": "-122.4336537", 
      "CountrySubDivisionCode": "CA", 
      "Id": "4"
    }, 
    "TxnDate": "2014-12-31", 
    "TotalAmt": 50.0, 
    "CustomerRef": {
      "name": "Cool Cars", 
      "value": "3"
    }, 
    "ShipAddr": {
      "City": "Half Moon Bay", 
      "Line1": "65 Ocean Dr.", 
      "PostalCode": "94213", 
      "Lat": "37.4300318", 
      "Long": "-122.4336537", 
      "CountrySubDivisionCode": "CA", 
      "Id": "4"
    }, 
    "RemainingCredit": 50.0, 
    "PrintStatus": "NeedToPrint", 
    "ProjectRef": {
      "value": "39298034"
    }, 
    "EmailStatus": "NotSet", 
    "sparse": false, 
    "Line": [
      {
        "LineNum": 1, 
        "Amount": 50.0, 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "ItemRef": {
            "name": "Concrete", 
            "value": "3"
          }
        }, 
        "Id": "1", 
        "DetailType": "SalesItemLineDetail"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 50.0, 
        "SubTotalLineDetail": {}
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "Id": "150", 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "MetaData": {
      "CreateTime": "2014-12-31T09:44:40-08:00", 
      "LastUpdatedTime": "2014-12-31T09:44:40-08:00"
    }
  }, 
  "time": "2014-12-31T09:44:40.726-08:00"
}
Expand
The Purchase Order object is a non-posting transaction representing a request to purchase goods or services from a third party.
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference.
See Quickbooks Purchase Order API reference.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Purchase Order creation.
Additional fields: AP Account Reference, Vendor Reference, DocNumber.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*
Value: Item based Expense Line Detail, Account Based Expense Line Detail.


Amount*: amount, price of the line.

Item Based Expense Line Detail*
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference*: Reference to a customer or job.
___ Value*: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Quantity*: Number of items.

_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.

_ Billable Status: The billable status of the expense. This field is not updatable through an API request. The value automatically changes when an invoice is created.
Possible values: Billable, Not Billable, Has Been Billed

_ Unit Price: Unit price of the subject item as referenced by ItemRef.
Corresponds to the Rate column on the QuickBooks Online UI to specify either unit price, a discount, or a tax rate for item. If used for unit price, the monetary value of the service or product, as expressed in the home currency. If used for a discount or tax rate, express the percentage as a fraction. For example, specify 0.4 for 40% tax.
AP Account Reference*This field indicates the Accounts Payable (AP) account used to record the bill.

While many small businesses may only have one AP account, it’s crucial to always explicitly specify the account.
This ensures accurate record-keeping, especially for businesses with multiple AP accounts.
The specified account must be a Liability account specifically designated for Payables.
Failing to explicitly specify the AP account can lead to unexpected errors when linking transactions within your accounting system.

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Vendor Reference*Reference to the vendor for this transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response Sample from Create Purchase Order 
{
  "PurchaseOrder": {
    "DocNumber": "1007", 
    "SyncToken": "0", 
    "domain": "QBO", 
    "VendorRef": {
      "name": "Hicks Hardware", 
      "value": "41"
    }, 
    "TxnDate": "2015-07-28", 
    "TotalAmt": 25.0, 
    "APAccountRef": {
      "name": "Accounts Payable (A/P)", 
      "value": "33"
    }, 
    "EmailStatus": "NotSet", 
    "sparse": false, 
    "Line": [
      {
        "DetailType": "ItemBasedExpenseLineDetail", 
        "Amount": 25.0, 
        "ProjectRef": {
          "value": "39298034"
        }, 
        "Id": "1", 
        "ItemBasedExpenseLineDetail": {
          "ItemRef": {
            "name": "Pump", 
            "value": "11"
          }, 
          "CustomerRef": {
            "name": "Cool Cars", 
            "value": "3"
          }, 
          "Qty": 1, 
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "BillableStatus": "NotBillable", 
          "UnitPrice": 25
        }
      }
    ], 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }, 
      {
        "DefinitionId": "2", 
        "Type": "StringType", 
        "Name": "Sales Rep"
      }
    ], 
    "Id": "259", 
    "MetaData": {
      "CreateTime": "2015-07-28T16:06:03-07:00", 
      "LastUpdatedTime": "2015-07-28T16:06:03-07:00"
    }
  }, 
  "time": "2015-07-28T16:06:04.864-07:00"
}
Expand
A customer is someone who buys your products or services. 
 
Customer Relationships: Customer relationships can be complex. Some customers may have a hierarchical structure. For example: 
▪️ A team is the main customer, and its individual members are sub-customers. 
▪️ A property management company is the main customer, and the properties they manage are sub-customers. 
 
Tracking Work: You can use the system to track specific tasks or projects associated with a customer. For instance: 
▪️ A homeowner is the customer, and their kitchen remodel is the project with individual tasks. 
▪️ A car owner is the customer, and their car repairs are the projects with individual tasks. 
  
⚠️ The Display Name attribute or at least one of Title, Given Name, Middle Name, Family Name, or Suffix attributes is required during customer creation. 
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Customer  API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Customer creation.
Additional fields: Primary Email Address, Suffix, Title, Middle Name, Notes, Primary Phone, Company Name, Bill Address, Given Name.
Family Name*Family name or the last name of the person.
Display Name*The Display Name is how the person or organization is identified within the system. It must be unique within the system (across Customers, Vendors, and Employees). This field cannot be removed using sparse updates.

If not provided, the system will create one for you by combining the customer’s name components (like title, first name, last name).
ADDITIONAL FIELDS
Primary Email AddressPrimary email address.

[+ Add Field] add more fields.
Address: An email address, the format must follow the RFC 822 standard.
SuffixSuffix of the name. For example, Jr. 
TitleTitle of the person.

This tag supports i18n (localized translations of titles such as “Mr.,” “Ms.,” “Dr.,” “Prof.,” or job-related titles like “CEO” and “Manager” in different languages and cultures).
Middle NameMiddle name of the person. The person can have zero or more middle names.
Notes
Max 2000 chars.		Free form text describing the Customer.
Primary Phone
Max 30 chars.		Primary phone number.

[+ Add Field] add more fields.
Free for Number.
Company NameThe name of the company associated with the person or organization.
Bill AddressDefault billing address.

When a physical address is updated within a transaction object, the QuickBooks Online API organizes the address components differently in the transaction response compared to when it was initially created:
The Line1 and Line2 fields are now filled with the customer name and company name.
The original Line1 to Line5, along with City, SubDivisionCode (State/Province), and PostalCode, are shifted into Line3 through Line5 as free-form text.

[+ Add Field] add more fields.
Country Sub Division Code
City
Postal Code
line1
Country
Given NameGiven name or first name of a person.

(*) required field

Response Sample from Create Customer 
{
  "Customer": {
    "domain": "QBO", 
    "PrimaryEmailAddr": {
      "Address": "jdrew@myemail.com"
    }, 
    "DisplayName": "King's Groceries", 
    "CurrencyRef": {
      "name": "United States Dollar", 
      "value": "USD"
    }, 
    "DefaultTaxCodeRef": {
      "value": "2"
    }, 
    "PreferredDeliveryMethod": "Print", 
    "GivenName": "James", 
    "FullyQualifiedName": "King's Groceries", 
    "BillWithParent": false, 
    "Title": "Mr", 
    "Job": false, 
    "BalanceWithJobs": 0, 
    "PrimaryPhone": {
      "FreeFormNumber": "(555) 555-5555"
    }, 
    "Taxable": true, 
    "MetaData": {
      "CreateTime": "2015-07-23T10:58:12-07:00", 
      "LastUpdatedTime": "2015-07-23T10:58:12-07:00"
    }, 
    "BillAddr": {
      "City": "Mountain View", 
      "Country": "USA", 
      "Line1": "123 Main Street", 
      "PostalCode": "94042", 
      "CountrySubDivisionCode": "CA", 
      "Id": "112"
    }, 
    "MiddleName": "B", 
    "Notes": "Here are other details.", 
    "Active": true, 
    "Balance": 0, 
    "SyncToken": "0", 
    "Suffix": "Jr", 
    "CompanyName": "King Groceries", 
    "FamilyName": "King", 
    "PrintOnCheckName": "King Groceries", 
    "sparse": false, 
    "Id": "67"
  }, 
  "time": "2015-07-23T10:58:12.099-07:00"
}
Expand
The Vendor object represents the seller from whom your company purchases any service or product.
 
⚠️ The Display Name attribute or at least one of Title, Given Name, Middle Name, Family Name, or Suffix attributes is required during customer creation.
 
See Quickbooks Vendor  API reference.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Vendor creation.
Additional fields: Print on Check Name, Primary Email Address, Suffix, Title, Tax Identifier, Account Number, Primary Phone, Web Address, Mobile, Company Name, Bill Address, Given Name.
Family Name*Family name or the last name of the person.
Display NameThe Display Name is how the person or organization is identified within the system. It must be unique within the system (across Customers, Vendors, and Employees). This field cannot be removed using sparse updates.

If not provided, the system will create one for you by combining the customer’s name components (like title, first name, last name).
ADDITIONAL FIELDS
Print on Check NameThis field displays the name of the person or organization as it should appear on a printed check.
If you don’t provide this name, it will be automatically filled in using the DisplayName.
Primary Email AddressPrimary email address.

[+ Add Field] add more fields.
Address: Email address, the format must follow the RFC 822 standard.
SuffixSuffix of the name. For example, Jr. 
TitleTitle of the person.

This tag supports i18n (localized translations of titles such as “Mr.,” “Ms.,” “Dr.,” “Prof.,” or job-related titles like “CEO” and “Manager” in different languages and cultures).
Tax Identifier
Max 20 chars.		The tax ID of the Person or Organization.

The value is masked in responses, exposing only last four characters. For example, the ID of 123-45-6789 is returned as XXXXXXX6789.
Account Number
Max 100 chars.		Name or number of the account associated with this vendor.
Primary PhonePrimary phone number.

[+ Add Field] add more fields.
Free for Number.
Max 30 chars.
Web Address
Maximum 1000 chars.		[+ Add Field] add more fields.
URI: Uniform Resource Identifier for the web site.
Mobile
Maximum of 30 chars.		Mobile phone number.

[+ Add Field] add more fields.
Free for Number: Specifies the telephone number in free form.
Company NameThe name of the company associated with the person or organization.
Bill AddressDefault billing address.

When a physical address is updated within a transaction object, the QuickBooks Online API organizes the address components differently in the transaction response compared to when it was initially created:
The Line1 and Line2 fields are now filled with the customer name and company name.
The original Line1 to Line5, along with City, SubDivisionCode (State/Province), and PostalCode, are shifted into Line3 through Line5 as free-form text.

[+ Add Field] add more fields.
Country Sub Division Code
City
Postal Code
line1
Country
Given NameGiven name or first name of a person.

(*) required field

Response Sample from Create Vendor 
{
  "Vendor": {
    "domain": "QBO", 
    "PrimaryEmailAddr": {
      "Address": "dbradley@myemail.com"
    }, 
    "DisplayName": "Dianne's Auto Shop", 
    "CurrencyRef": {
      "name": "United States Dollar", 
      "value": "USD"
    }, 
    "GivenName": "Dianne", 
    "Title": "Ms.", 
    "PrimaryPhone": {
      "FreeFormNumber": "(650) 555-2342"
    }, 
    "Active": true, 
    "MetaData": {
      "CreateTime": "2015-07-28T12:51:21-07:00", 
      "LastUpdatedTime": "2015-07-28T12:51:21-07:00"
    }, 
    "Vendor1099": false, 
    "BillAddr": {
      "City": "Millbrae", 
      "Country": "U.S.A", 
      "Line3": "29834 Mustang Ave.", 
      "Line2": "Dianne Bradley", 
      "Line1": "Dianne's Auto Shop", 
      "PostalCode": "94030", 
      "CountrySubDivisionCode": "CA", 
      "Id": "423"
    }, 
    "Mobile": {
      "FreeFormNumber": "(650) 555-2000"
    }, 
    "WebAddr": {
      "URI": "http://DiannesAutoShop.com"
    }, 
    "Balance": 0, 
    "SyncToken": "0", 
    "Suffix": "Sr.", 
    "CompanyName": "Dianne's Auto Shop", 
    "FamilyName": "Bradley", 
    "TaxIdentifier": "99-5688293", 
    "AcctNum": "35372649", 
    "PrintOnCheckName": "Dianne's Auto Shop", 
    "sparse": false, 
    "Id": "137"
  }, 
  "time": "2015-07-28T12:51:21.326-07:00"
}
Expand
Accounts are the building blocks of your financial records. They track all your business’s financial activity:
▪️ Money coming in: Income and revenue.
▪️ Money going out: Expenses.
▪️ The value of your assets: Things your business owns like vehicles and equipment.
There are five main types of accounts: assets, liabilities, income, expenses, and equity.
All your business’s accounts are listed in your Chart of Accounts, which is a unique list created for your specific business. Accountants often refer to these accounts as “ledgers.”
The “account object” is the tool you’ll use within the QuickBooks system to manage and work with your accounts.
 
See Quickbooks Account  API reference.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Account creation.
Additional fields: Currency reference, Meta Data, Current Balance, Active, Sub Account.
Name*
Must be unique.
max 100 characters.		Name for the Account. Account.Name attribute must not contain double quotes (“) or colon (:).
Account Sub Type*The account sub-type classification and is based on the AccountType value.
Required if AccountType is not specified.

See possible values in the Account type and Account Sub Type List below.
Account Type*A detailed account classification that specifies the use of this account. The type is based on the Classification.
Required if AccountSubType is not specified.

See possible values in the Account type and Account Sub Type List below.
ADDITIONAL FIELDS
Currency referenceReference to the currency in which this account holds amounts.

[+ Add Field] add more fields:
Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency
Meta DataDescriptive information about the entity. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM
Current BalanceSpecifies the balance amount for the current Account. Valid for Balance Sheet accounts.
ActiveTrue – False

Inactive accounts can be hidden from most views and may not be used for new transactions.

(*) required field

Account Type and Account Sub Type List

ASSET ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
BankDefault
CashOnHand (default), Checking, MoneyMarket, RentsHeldInTrust, Savings, TrustAccounts, CashAndCashEquivalents, OtherEarMarkedBankAccounts
Other Current AssetDefault
AllowanceForBadDebts, DevelopmentCosts, EmployeeCashAdvances (default), OtherCurrentAssets, Inventory, Investment_MortgageRealEstateLoans, Investment_Other, Investment_TaxExemptSecurities, Investment_USGovernmentObligations, LoansToOfficers, LoansToOthers, LoansToStockholders, PrepaidExpenses, Retainage, UndepositedFunds, AssetsAvailableForSale, BalWithGovtAuthorities, CalledUpShareCapitalNotPaid, ExpenditureAuthorisationsAndLettersOfCredit, GlobalTaxDeferred, GlobalTaxRefund, InternalTransfers, OtherConsumables, ProvisionsCurrentAssets, ShortTermInvestmentsInRelatedParties, ShortTermLoansAndAdvancesToRelatedParties, TradeAndOtherReceivables
Fixed AssetDefault
AccumulatedDepletion, AccumulatedDepreciation, DepletableAssets, FixedAssetComputers, FixedAssetCopiers, FixedAssetFurniture, FixedAssetPhone, FixedAssetPhotoVideo, FixedAssetSoftware, FixedAssetOtherToolsEquipment, FurnitureAndFixtures (default), Land, LeaseholdImprovements, OtherFixedAssets, AccumulatedAmortization, Buildings, IntangibleAssets, MachineryAndEquipment, Vehicles, AssetsInCourseOfConstruction, CapitalWip, CumulativeDepreciationOnIntangibleAssets, IntangibleAssetsUnderDevelopment, LandAsset, NonCurrentAssets, ParticipatingInterests, ProvisionsFixedAssets
Other AssetDefault
LeaseBuyout, OtherLongTermAssets, SecurityDeposits, AccumulatedAmortizationOfOtherAssets, Goodwill, Licenses (default), OrganizationalCosts, AssetsHeldForSale, AvailableForSaleFinancialAssets, DeferredTax, Investments, LongTermInvestments, LongTermLoansAndAdvancesToRelatedParties, OtherIntangibleAssets, OtherLongTermInvestments, OtherLongTermLoansAndAdvances, PrepaymentsAndAccruedIncome, ProvisionsNonCurrentAssets
Accounts ReceivableDefault
Accounts Receivable

EQUITY ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
EquityDefault
OpeningBalanceEquity (default), PartnersEquity, RetainedEarnings, AccumulatedAdjustment, OwnersEquity, PaidInCapitalOrSurplus, PartnerContributions, PartnerDistributions, PreferredStock, CommonStock, TreasuryStock, EstimatedTaxes, Healthcare, PersonalIncome, PersonalExpense, AccumulatedOtherComprehensiveIncome, CalledUpShareCapital, CapitalReserves, DividendDisbursed, EquityInEarningsOfSubsidiaries, InvestmentGrants, MoneyReceivedAgainstShareWarrants, OtherFreeReserves, ShareApplicationMoneyPendingAllotment, ShareCapital, Funds

EXPENSE ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
ExpenseDefault
AdvertisingPromotional, BadDebts, BankCharges, CharitableContributions, CommissionsAndFees, Entertainment, EntertainmentMeals, EquipmentRental, FinanceCosts, GlobalTaxExpense, Insurance, InterestPaid, LegalProfessionalFees, OfficeExpenses, OfficeGeneralAdministrativeExpenses, OtherBusinessExpenses, OtherMiscellaneousServiceCost, PromotionalMeals, RentOrLeaseOfBuildings, RepairMaintenance, ShippingFreightDelivery, SuppliesMaterials, Travel (default), TravelMeals, Utilities, Auto, CostOfLabor, DuesSubscriptions, PayrollExpenses, TaxesPaid, UnappliedCashBillPaymentExpense, Utilities, AmortizationExpense, AppropriationsToDepreciation, BorrowingCost, CommissionsAndFees, DistributionCosts, ExternalServices, ExtraordinaryCharges, IncomeTaxExpense, LossOnDiscontinuedOperationsNetOfTax, ManagementCompensation, OtherCurrentOperatingCharges, OtherExternalServices, OtherRentalCosts, OtherSellingExpenses, ProjectStudiesSurveysAssessments, PurchasesRebates, ShippingAndDeliveryExpense, StaffCosts, Sundry, TravelExpensesGeneralAndAdminExpenses, TravelExpensesSellingExpense
Other ExpenseDefault
Depreciation (default), ExchangeGainOrLoss, OtherMiscellaneousExpense, PenaltiesSettlements, Amortization, GasAndFuel, HomeOffice, HomeOwnerRentalInsurance, OtherHomeOfficeExpenses, MortgageInterest, RentAndLease, RepairsAndMaintenance, ParkingAndTolls, Vehicle, VehicleInsurance, VehicleLease, VehicleLoanInterest, VehicleLoan, VehicleRegistration, VehicleRepairs, OtherVehicleExpenses, Utilities, WashAndRoadServices, DeferredTaxExpense, Depletion, ExceptionalItems, ExtraordinaryItems, IncomeTaxOtherExpense, MatCredit, PriorPeriodItems, TaxRoundoffGainOrLoss
Cost of Goods SoldDefault
EquipmentRentalCos, OtherCostsOfServiceCos, ShippingFreightDeliveryCos, SuppliesMaterialsCogs, CostOfLaborCos (default), CostOfSales, FreightAndDeliveryCost

LIABILITY ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
Accounts PayableDefault
Accounts Payable, OutstandingDuesMicroSmallEnterprise, OutstandingDuesOtherThanMicroSmallEnterprise
Credit CardDefault
Credit Card
Long Term LiabilityDefault
NotesPayable (default), OtherLongTermLiabilities, ShareholderNotesPayable, AccrualsAndDeferredIncome, AccruedLongTermLiabilities, AccruedVacationPayable, BankLoans, DebtsRelatedToParticipatingInterests, DeferredTaxLiabilities, GovernmentAndOtherPublicAuthorities, GroupAndAssociates, LiabilitiesRelatedToAssetsHeldForSale, LongTermBorrowings, LongTermDebit, LongTermEmployeeBenefitObligations, ObligationsUnderFinanceLeases, OtherLongTermProvisions, ProvisionForLiabilities, ProvisionsNonCurrentLiabilities, StaffAndRelatedLongTermLiabilityAccounts
Other Current LiabilityDefault
DirectDepositPayable, LineOfCredit, LoanPayable, GlobalTaxPayable, GlobalTaxSuspense, OtherCurrentLiabilities (default), PayrollClearing, PayrollTaxPayable, PrepaidExpensesPayable, RentsInTrustLiability, TrustAccountsLiabilities, FederalIncomeTaxPayable, InsurancePayable, SalesTaxPayable, StateLocalIncomeTaxPayable, AccruedLiabilities, CurrentLiabilities, CurrentPortionEmployeeBenefitsObligations, CurrentPortionOfObligationsUnderFinanceLeases, CurrentTaxLiability, DividendsPayable, DutiesAndTaxes, InterestPayables, ProvisionForWarrantyObligations, ProvisionsCurrentLiabilities, ShortTermBorrowings, SocialSecurityAgencies, StaffAndRelatedLiabilityAccounts, SundryDebtorsAndCreditors, TradeAndOtherPayables

REVENUE ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
IncomeDefault
NonProfitIncome, OtherPrimaryIncome (default), SalesOfProductIncome, ServiceFeeIncome, DiscountsRefundsGiven, UnappliedCashPaymentIncome, CashReceiptIncome, OperatingGrants, OtherCurrentOperatingIncome, OwnWorkCapitalized, RevenueGeneral, SalesRetail, SalesWholesale, SavingsByTaxScheme
Other IncomeDefault
DividendIncome, InterestEarned, OtherInvestmentIncome (default), OtherMiscellaneousIncome, TaxExemptInterest, GainLossOnSaleOfFixedAssets, GainLossOnSaleOfInvestments, LossOnDisposalOfAssets, OtherOperatingIncome, UnrealisedLossOnSecuritiesNetOfTax

Response Sample from Create Account 
{
  "Account": {
    "FullyQualifiedName": "MyJobs", 
    "domain": "QBO", 
    "Name": "MyJobs", 
    "Classification": "Asset", 
    "AccountSubType": "AccountsReceivable", 
    "CurrencyRef": {
      "name": "United States Dollar", 
      "value": "USD"
    }, 
    "CurrentBalanceWithSubAccounts": 0, 
    "sparse": false, 
    "MetaData": {
      "CreateTime": "2014-12-31T09:29:05-08:00", 
      "LastUpdatedTime": "2014-12-31T09:29:05-08:00"
    }, 
    "AccountType": "Accounts Receivable", 
    "CurrentBalance": 0, 
    "Active": true, 
    "SyncToken": "0", 
    "Id": "94", 
    "SubAccount": false
  }, 
  "time": "2014-12-31T09:29:05.717-08:00"
}
Expand
A Purchase object represents an expense, such as a purchase made from a vendor.  
  
To create a Purchase:  
▪️ You must specify an Account Reference for all purchases.  
▪️ The Total Amount attribute must add up to sum of Line.Amount attributes.  
  
There are three types of purchases: Cash, Check, and Credit Card.  
▪️ Cash Purchase contains information regarding a payment made in cash.  
▪️ Check Purchase contains information regarding a payment made by check.  
▪️ Credit Card Purchase contains information regarding a payment made by credit card or refunded/credited back to a credit card.  
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Purchase API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Purchase creation.
Additional fields: Account Reference, Currency Reference, Transaction Date, Print Status, Transaction Source, Global Tax Calculation, Transaction Location Type, Document Number, Private Note, Credit, Payment Method Reference, PurchaseEx, Exchange Rate, Department Reference, Entity Reference, Include In Annual TPAR.
Payment type*Payment Type can be: Cash, Check, or Credit Card
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.
Element 1: Represents the first Line.

Detail Type*
Possible values:
– Item based Expense Line Detail (This option is only available when the ‘For Purchase’ preference is activated for Products and Services).
– Account Based Expense Line Detail.

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to Detail Type.

ID: Unique identifier (ID) of the line item.
Update Operation: If a valid ID is provided, the request is treated as an update to an existing line item.
Create Operation: If no ID is provided, or the provided ID is invalid, the request is treated as a creation of a new line item.
This ID field is available in all objects that contain lines and support updates.

Item Based Expense Line Detail:
[+ Add Field] add more related fields.

_Tax Inclusive Amount: represents the total amount of the purchase, including tax if applicable.
Use TaxInclusiveAmount when the total purchase price includes tax, and QuickBooks should derive the pre-tax amount.
Do NOT use it if tax should be calculated separately based on the taxable subtotal.

_ Item Reference*: Reference to the Item.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference*: Reference to a customer or job.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Price Level Reference: Reference to the PriceLevel of the service or item for the line.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced Price Level.
___ Name: Name derived from the field that holds the common name of that price level.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Class Reference: Reference to the Class associated with the expense.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced Class.
___ Name: Name derived from the field that holds the common name of that class.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Tax Code Reference: Reference to the TaxCode for this item.
[+ Add Field] add more fields in Tax Code Reference:
___ Value: The ID for the referenced Tax Code.
___ Name: Name derived from the field that holds the common name of that Tax Code.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Markup Info: Markup information for the expense.
[+ Add Field] add more fields.
___ Price Level Reference: Reference to a PriceLevel for the markup. 
______ Value*: The ID for the referenced Price Level.
______ Name: Name derived from the field that holds the common name of that price level.
___ Percent:Markup amount expressed as a percent of charges already entered in the current transaction. To enter a rate of 10% use 10.0, not 0.01.

_Quantity*: Number of items.

_Unit Price: Unit price of the subject item as referenced by ItemRef.
Corresponds to the Rate column on the QuickBooks Online UI to specify either unit price, a discount, or a tax rate for item. If used for unit price, the monetary value of the service or product, as expressed in the home currency. If used for a discount or tax rate, express the percentage as a fraction. For example, specify 0.4 for 40% tax.

Linked Transaction: Zero or more transactions linked to this Purchase.
[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Linked Transaction can be added as elements.
Element 1: Represents the first Linked Transaction.
_Transaction ID*: Transaction Id of the related transaction.

_Transaction Type*: Bill, BillPaymentCheck, BillPaymentCreditCard, CreditCardCredit, ReimburseCharge, VendorCredit, Expense, Check, Payment

_Transaction Line ID: This field is required for Deposit and Bill entities. It specifies the line number within the linked transaction. If you include this field, you must also provide the TxnId and TxnType of the linked transaction.

Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.

Line Number: Specifies the position of the line in the collection of transaction lines.

Account Based Expense Line Detail:
[+ Add Field] add more fields.

_Account Reference*: This field indicates the account used for this purchase, depending on the payment method (e.g., bank account for checks, credit card account for credit card payments).
[+ Add Field] add more fields in account Reference:
___ Value*: The ID for the referenced account
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Tax Amount: Sales tax paid as part of the expense.
_Tax Inclusive Amount: The total amount of the line item including tax.

_Class Reference: This field specifies the class associated with the expense. Class tracking must be enabled at the line item level in your accounting preferences for this field to be available.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced Class.
___ Name: Name derived from the field that holds the common name of that class.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Tax Code Reference: Reference to the TaxCode for this expense.
[+ Add Field] add more fields in Tax Code Reference:
___ Value*: The ID for the referenced Tax Code.
___ Name: Name derived from the field that holds the common name of that Tax Code.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Markup Info: Markup information for the expense.
[+ Add Field] add more fields.
___ Price Level Reference: Reference to a PriceLevel for the markup. 
______ Value*: The ID for the referenced Price Level.
______ Name: Name derived from the field that holds the common name of that price level.
___ Percent:Markup amount expressed as a percent of charges already entered in the current transaction. To enter a rate of 10% use 10.0, not 0.01.

_Customer Reference: Reference to the Customer associated with the expense.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Account Reference*This field specifies the associated account. For checks, it must be a bank account. For credit cards, it must be a credit card account. The account reference must be valid and currently active.

[+ Add Field] add more fields.
Value*: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Currency referenceReference to the currency in which all amounts on the associated transaction are expressed. This must be defined if multi-currency is enabled for the company. Read more about multi-currency support here.

Value*: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency.
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Print StatusApplicable only for Check.  Ignored for Credit Card charge or refund.
Possible values: Not Set, Need To Print, Print Complete.
Transaction SourceUsed internally to specify originating source of a credit card transaction.
Global Tax CalculationMethod in which tax is applied. Allowed values are: Tax Excluded, Tax Inclusive, and Not Applicable.
Transaction Location Type
For France locales, only.		The account location. Valid values include:
Within France
France Overseas
Outside France With EU
Outside EU
Document Number
Maximum of 21 chars.		This field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.
Private Note
Max of 4000 chars.		User-entered, organization-private note about the transaction. This field maps to the Memo field on the Expense form in the QuickBooks UI.
CreditFalse—it represents a charge. True—it represents a refund. Valid only for Credit Card payment type and Credit Card transactions.
Payment Method ReferenceReference to a Payment Method associated with this transaction.

[+ Add Field] add more fields.
Value*: The ID for the referenced payment method.
Name: Name derived from the field that holds the common name of that payment method.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
PurchaseExFor internal use.
Extension field that allows custom data storage.
It is often used for third-party integrations that need to track extra metadata.
Exchange RateThis field represents the exchange rate, which is the number of your company’s home currency units needed to equal one unit of a different currency.

This field is only applicable if your company uses multiple currencies.
Department ReferenceThis field links the transaction to a specific department within your company. This feature is only available if the ‘Track Departments’ preference is enabled in your accounting settings.

[+ Add Field] add more fields.
Value*: The ID for the referenced department.
Name: Name derived from the field that holds the common name of that department.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Entity ReferenceThis field links an expense transaction to a specific entity.

Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate Customer, Vendor or Employee object for this reference. 

[+ Add Field] add more fields.
Reference Type*: Specifies the type of entity (Customer, Vendor, Employee).
Value*: The ID for the referenced entity.
Name: Name derived from the field that holds the common name of that entity.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Include In Annual TPARTrue – False

Include the supplier in the annual TPAR. TPAR stands for Taxable Payments Annual Report. The TPAR is mandated by ATO to get the details payments that businesses make to contractors for providing services. Some government entities also need to report the grants they have paid in a TPAR.

(*) required field

Response Sample from Create Purchase 
{
  "Purchase": {
    "SyncToken": "0", 
    "domain": "QBO", 
    "PurchaseEx": {
      "any": [
        {
          "name": "{http://schema.intuit.com/finance/v3}NameValue", 
          "nil": false, 
          "value": {
            "Name": "TxnType", 
            "Value": "54"
          }, 
          "declaredType": "com.intuit.schema.finance.v3.NameValue", 
          "scope": "javax.xml.bind.JAXBElement$GlobalScope", 
          "globalScope": true, 
          "typeSubstituted": false
        }
      ]
    }, 
    "Credit": false, 
    "TotalAmt": 10.0, 
    "PaymentType": "CreditCard", 
    "TxnDate": "2015-07-27", 
    "sparse": false, 
    "Line": [
      {
        "DetailType": "AccountBasedExpenseLineDetail", 
        "Amount": 10.0, 
        "ProjectRef": {
          "value": "42991284"
        }, 
        "Id": "1", 
        "AccountBasedExpenseLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "AccountRef": {
            "name": "Meals and Entertainment", 
            "value": "13"
          }, 
          "BillableStatus": "NotBillable"
        }
      }
    ], 
    "AccountRef": {
      "name": "Visa", 
      "value": "42"
    }, 
    "CustomField": [], 
    "Id": "247", 
    "MetaData": {
      "CreateTime": "2015-07-27T10:27:01-07:00", 
      "LastUpdatedTime": "2015-07-27T10:27:01-07:00"
    }
  }, 
  "time": "2015-07-27T10:27:01.593-07:00"
}
Expand
The Time Activity object represents a record of time worked by a vendor or employe.  
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Time Activity API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Time Activity creation.
Additional fields: Transaction Date, Description, Item Reference, Minutes, Hours, Billable Status, Hourly Rate, Taxable, Customer Reference, Meta Data.
Name of*This field specifies the type of time activity being recorded. It’s required when creating a new record and must be used in conjunction with either the EmployeeRef or VendorRef attributes.
Possible values: Vendor or Employee.
Employee ReferenceSpecifies the employee whose time is being recorded.

Value: The ID for the referenced employee.
Name: Name derived from the field that holds the common name of that employee.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Vendor ReferenceSpecifies the vendor whose time is being recorded.

Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Start Time*This field indicates the start time of the work. It’s required if the specific hours and minutes are not provided.

Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Important: Only include the hours (e.g., 9, 10, 11) without the time zone offset, as it doesn’t affect the time activity hours calculation.

If Transaction Date is provided: Use the specified Transaction Date (in YYYY-MM-DD format) and include Start Time and End Time in hours and minutes (without time zone offsets).
If Transaction Date is not provided: Use the current server date and include StartTime and EndTime in hours and minutes (with or without time zone offsets).

For historical or future transactions, always include the Transaction Date in YYYY-MM-DD format and specify StartTime and End Time in hours and minutes.
End Time*This field indicates the end time of the work. It’s required if the specific hours and minutes are not provided.

Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Important: Only include the hours (e.g., 5, 6, 7) without the time zone offset, as it doesn’t affect the time activity hours calculation.

If Transaction Date is provided: Use the specified TxnDate (in YYYY-MM-DD format) and include StartTime and EndTime in hours and minutes (without time zone offsets).
If Transaction Date is not provided: Use the current server date and include StartTime and EndTime in hours and minutes (with or without time zone offsets).

For historical or future transactions, always include the Transaction Date in YYYY-MM-DD format and specify StartTime and EndTime in hours and minutes.
ADDITIONAL FIELDS
Transaction DateThe date for the time activity. This field represents the date used for financial reporting.

If no date is provided, the current system date is used.
The default sort order for transactions is ascending by date.

If you specify the start and end times without time zone offsets, you must also provide the transaction date (TxnDate) for any past or future time activities. For example, to record a past time activity, include the TxnDate and specify the start and end times in hours (without time zone offsets).

Local timezone: YYYY-MM-DD UTC: YYYY-MM-DDZ Specific time zone: YYYY-MM-DD+/-HH:MM
The date format follows the XML Schema standard.
Description
maximum 4000 characters.		Description of work completed during time activity.
Item ReferenceReference to the service item associated with this object.

[+ Add Field] add more fields in Item reference:
___ Item ID: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.me
Minutes
Maximum of 8760 hours 59 minutes; if hours is 8760 minutes must be 0		minutes worked.
Hours
Maximum of 8760 hours 59 minutes; if hours is 8760 minutes must be 0		Hours and minutes worked. Required if StartTime and EndTime not specified
Hourly Rate
max character: 0 to 99999999999 hours.		Hourly bill rate of the employee or vendor for this time activity. Required if Billable Status is set to Billable.
TaxableTrue – False
True if the time recorded is both billable and taxable.
Customer ReferenceReference to a customer or job.

[+ Add Field] add more fields.
Value: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Meta DataDescriptive information about the object. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

(*) required field

Response Sample from Create Time Activity 
{
  "TimeActivity": {
    "TxnDate": "2015-07-28", 
    "domain": "QBO", 
    "NameOf": "Employee", 
    "sparse": false, 
    "ItemRef": {
      "name": "Hours", 
      "value": "2"
    }, 
    "ProjectRef": {
      "value": "39298034"
    }, 
    "BillableStatus": "NotBillable", 
    "StartTime": "2015-07-28T09:00:00-07:00", 
    "HourlyRate": 0, 
    "Taxable": false, 
    "EmployeeRef": {
      "name": "Emily Platt", 
      "value": "55"
    }, 
    "EndTime": "2015-07-28T18:00:00-07:00", 
    "CustomerRef": {
      "name": "Cool Cars", 
      "value": "3"
    }, 
    "Id": "6", 
    "SyncToken": "0", 
    "MetaData": {
      "CreateTime": "2015-07-28T10:26:25-07:00", 
      "LastUpdatedTime": "2015-07-28T10:26:25-07:00"
    }
  }, 
  "time": "2015-07-28T10:26:26.952-07:00"
}
Expand
A Refund Receipt must include:  
▪️ At least one line item: This details the item(s) being refunded.  
▪️ A designated deposit account: Specified by Deposit To Account Ref.  
  
If no billing address is provided, The customer’s address will be used as the billing address.  
  
Tax Code Restrictions:  
▪️ Custom Sales Tax cannot be used for Transaction Tax Code Ref.  
▪️ This tax code is reserved for transactions using the older sales tax model.  
▪️ You cannot create or update transactions that use TaxCode.CustomSalesTax.  
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Refund Receipt API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Refund Receipt creation.
Additional fields: Document Number, Balance, Payment Method Reference, Bill Address, Transaction Date, Customer Reference, Customer Memo, Shipping Address, Print Status, Bill Email, Line, Apply Tax After Discount, Custom Field, Transaction Tax Detail, Meta Data.
Deposit to Account Reference*Accounts receivable asset account from which payment money is refunded. 

_Reference Type*:
[+ Add Field] add more fields.
___ Value*: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Currency Reference Type: This field specifies the currency used for all amounts in the transaction. (Required if your company uses multiple currencies (i.e., if Preferences.MultiCurrencyEnabled is set to ‘true’).
For more information, please refer to Manage multiple currencies.

___ Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
___ Name: The full name of the currency.
Line*
The minimum line item required for the request is one of the following: Sales Item Line and Group Line.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.
Element 1: Represents the first Line.

Detail Type*: Possible choices for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Sale Item Line Detail*:
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

[+ Add Field] add more fields:
_ Unit Price: Unit price of the subject item as referenced by ItemRef.
_ Quantity: Number of items for the line.
_ Tax Code Reference: Reference to the TaxCode for this item. 
[+ Add Field] add more fields:
___ Value: The ID for the referenced Tax Code.

Amount*: The amount of the line item.

Description: Free form text description of the line item that appears in the printed record (max character: 4000).

Line Number: Specifies the position of the line in the collection of transaction lines.

ID: Unique identifier (ID) of the line item.
Update Operation: If a valid ID is provided, the request is treated as an update to an existing line item.
Create Operation: If no ID is provided, or the provided ID is invalid, the request is treated as a creation of a new line item.
This ID field is available in all objects that contain lines and support updates.
ADDITIONAL FIELDS
Document Number
Maximum of 21 chars.		This field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.
Payment Method ReferenceReference to a Payment Method associated with this transaction.

[+ Add Field] add more fields.
Value*: The ID for the referenced payment method.
Name: Name derived from the field that holds the common name of that payment method.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Bill AddressThis field specifies the billing address for the invoice.

If no billing address is provided: QuickBooks will use the default billing address associated with the customer.
For international addresses: Use the 3-letter ISO country code or the full country name.
Address Updates:

If you update the physical address within the transaction itself, the address components will be presented differently in the API response compared to the original creation: Line 1 and Line 2: Will display the customer name and company name.
Line 3 to Line 5: Will contain the original address information (Line 1-5, City, State/Province, Postal Code) as free-form text.

[+ Add Field] add more fields.
Line1
Line2
Postal Code
Latitude
longitude
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Customer ReferenceReference to a customer or job.

Value: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Customer MemoValue: User’s message to the customer; this message is visible to the end user on their transactions.
Shipping AddressThis field indicates the shipping address for the goods. If no specific shipping address is provided, QuickBooks will automatically use the default shipping address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

If you update the physical address within the transaction itself, the address components will be presented differently in the API response compared to the original creation: Line 1 and Line 2: Will display the customer name and company name.
Line 3 to Line 5: Will contain the original address information (Line 1-5, City, State/Province, Postal Code) as free-form text.

[+ Add Field] add more fields:
City
Line1
Postal Code
Latitude
longitude
Country Sub Division Code
Print StatusApplicable only for Check.  Ignored for Credit Card charge or refund.
Possible values: Not Set, Need To Print, Print Complete.
Bill EmailIdentifies the e-mail address where the estimate is sent.

[+ Add Field] add more fields
Email*: The address format must follow the RFC 822 standard.
Apply Tax After Discount
Apply to USA.		True – False

If false or null, calculate the sales tax first, and then apply the discount. If true, subtract the discount first and then calculate the sales tax.
Custom fieldThis allows you to add up to three custom fields to your transactions.

These fields are available only if they have been configured for your company in the settings:
▪️ Check “Preferences.SalesFormsPrefs.CustomField” for sales transactions.
▪️ Check “Preferences.VendorAndPurchasesPrefs.POCustomField” for purchase orders.

Click here for information on managing custom fields.

[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional custom field can be added as elements.
Element 1: Represents the first custom field.

Value
Name
Field Type
Transaction Tax DetailThis data type contains information about the taxes applied to the entire transaction.
It includes details of sales taxes calculated based on the tax codes specified within the transaction.
▪️ QuickBooks can calculate these taxes automatically.
▪️ You can also provide the tax details when adding a transaction.

Global Tax Model: Refer to the Global Tax Model documentation for more information.
Sales Tax Disabled: If sales tax is disabled in your company’s preferences (Preferences.TaxPrefs.UsingSalesTax is false), this data will be ignored and not stored.

[+ Add Field] add more fields.
Total Tax: Total tax calculated for the transaction, excluding any tax lines manually inserted into the transaction line list.
Meta DataDescriptive information about the entity. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

(*) required field

Response Sample from Create Refund Receipt 
{
  "RefundReceipt": {
    "DocNumber": "1072", 
    "SyncToken": "0", 
    "domain": "QBO", 
    "Balance": 0, 
    "DepositToAccountRef": {
      "name": "Checking", 
      "value": "35"
    }, 
    "TxnDate": "2015-07-29", 
    "TotalAmt": 420.0, 
    "PrintStatus": "NeedToPrint", 
    "PaymentRefNum": "To Print", 
    "sparse": false, 
    "Line": [
      {
        "LineNum": 1, 
        "Amount": 420.0, 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "ItemRef": {
            "name": "Garden Supplies", 
            "value": "38"
          }
        }, 
        "Id": "1", 
        "DetailType": "SalesItemLineDetail"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 420.0, 
        "SubTotalLineDetail": {}
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "Id": "261", 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "MetaData": {
      "CreateTime": "2015-07-29T08:07:43-07:00", 
      "LastUpdatedTime": "2015-07-29T08:07:43-07:00"
    }
  }, 
  "time": "2015-07-29T08:07:43.749-07:00"
}
Expand
This unified Method is used to Update records from an Entity in your Quickbooks database by specifying the Object ID.

Tip: Use Wiresk Method “List” or Trigger “Get Records by Search String” to get the IDs.
 
This Method allows you to update: 
Invoice, Item, Payment, Journal Entry, Bill, Sale Receipt, Estimate, Deposit, Credit Memo, Purchase Order, Customer, Vendor, Account, Purchase, Time Activity, Refund Receipt. 

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*Update Record
Connection*Select your connection or create one.
Entity*
(Set of data that contain records)		Select the available Entity to update the records:

Invoice, Item, Payment, Journal Entry, Bill, Sale Receipt, Estimate, Deposit, Credit Memo, Purchase Order, Customer, Vendor, Account, Purchase, Time Activity, Refund Receipt.

(*) required field

Configuration table for each Entity:

Only the elements explicitly included in the update Method are modified. Elements omitted from the request remain unchanged.

Tip: Use Wiresk Method “List” or Trigger “Get Records by Search String” to get the IDs.

See Quickbooks Invoice API reference. 
MAP FIELDS [+ Add Field] Select fields from a list, to configure the invoice update.
Additional fields: Sales Term Reference, Transaction Date, Customer Memo, Transaction Tax Detail, Deposit, Line, DocNumber.
ID*Unique identifier of the Invoice.
Customer Reference*A customer is a consumer of the service or product that your business offers.
Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line*
Invoice line object.
If the transaction is taxable there is a limit of 750 lines per transaction.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Invoice Line.

Detail Type*: Possible choices for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to the Detail Type.

Description: Free form text description of the line item that appears in the printed record.
Max character: 4000.

Line Number: Specifies the position of the line in the collection of transaction lines.

Sale Item Line Detail [+ Add Field] add more fields in Sale Item Line Detail:
_ Quantity: Number of items for the line.
_ Unit Price: Unit price of the subject item as referenced by ItemRef.

_ Discount Amount: Fixed discount.
_ Discount Rate: The discount rate applied to this line. If both Discount are provided, Discount Rate takes precedence and Discount Amount is recalculated by QuickBooks services based on amount of Discount Rate.

_ Item Reference: Reference to an Item object.
[+ Add Field] add more fields in Item reference:
___ Item ID: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Tax Code Reference: Reference to the Tax Code for this item.
[+ Add Field] add more fields in Tax Code Reference:
___ Value: The ID for the referenced Tax Code.
___ Name: Name derived from the field that holds the common name of that Tax Code.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Sales Term ReferenceReference to the sales term associated with the transaction.

Value: The ID for the referenced Sales Term.
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Customer Memo
Max 1000 chars..		Value: User’s message to the customer; this message is visible to the end user on their transactions.
Transaction Tax DetailThis data type provides information for taxes charged on the transaction as a whole. It captures the details sales taxes calculated for the transaction based on the tax codes referenced by the transaction.

Transaction Tax Code Reference:
_ Value: Reference to the transaction tax code.

See Global tax model for more information about this element.
DepositThe deposit made towards this invoice.
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response sample from Update Invoice

Update “DueDate”
“DueDate”: “2015-09-30”

{
  "Invoice": {
    "TxnDate": "2015-07-24", 
    "domain": "QBO", 
    "PrintStatus": "NeedToPrint", 
    "TotalAmt": 100.0, 
    "Line": [
      {
        "LineNum": 1, 
        "Amount": 100.0, 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "ItemRef": {
            "name": "Services", 
            "value": "1"
          }
        }, 
        "Id": "1", 
        "DetailType": "SalesItemLineDetail"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 100.0, 
        "SubTotalLineDetail": {}
      }
    ], 
    "DueDate": "2015-09-30", 
    "ApplyTaxAfterDiscount": false, 
    "DocNumber": "1069", 
    "sparse": true, 
    "ProjectRef": {
      "value": "39298045"
    }, 
    "Deposit": 0, 
    "Balance": 100.0, 
    "CustomerRef": {
      "name": "Amy's Bird Sanctuary", 
      "value": "1"
    }, 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "SyncToken": "1", 
    "LinkedTxn": [], 
    "ShipAddr": {
      "City": "Bayshore", 
      "Line1": "4581 Finch St.", 
      "PostalCode": "94326", 
      "Lat": "INVALID", 
      "Long": "INVALID", 
      "CountrySubDivisionCode": "CA", 
      "Id": "109"
    }, 
    "EmailStatus": "NotSet", 
    "BillAddr": {
      "City": "Bayshore", 
      "Line1": "4581 Finch St.", 
      "PostalCode": "94326", 
      "Lat": "INVALID", 
      "Long": "INVALID", 
      "CountrySubDivisionCode": "CA", 
      "Id": "2"
    }, 
    "MetaData": {
      "CreateTime": "2015-07-24T10:33:39-07:00", 
      "LastUpdatedTime": "2015-07-24T11:03:26-07:00"
    }, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "Id": "238"
  }, 
  "time": "2015-07-24T11:03:26.674-07:00"
}
Expand
Update any writable field of an existing item object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.
 
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Item API Reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Item update.
Additional fields: Active, SKU, Unit Price, TrackQtyOnHand, QtyOnHand, AssetAccountRef, InvStartDate, ExpenseAccountRef.
ID*Unique identifier of the Item.
Name*
Maximum of 100 chars		Name of the item. This value must be unique, at least one character in length, and cannot include tabs, new lines, or colons. Required for create.
IncomeAccountRef*Reference to the posting account, that is, the account that records the proceeds from the sale of this item. Must be an account with account type of Sales of Product Income.

Account ID*: The ID for the referenced Income Account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Type*Classification that specifies the use of this item:
Inventory - Service - Non inventory

See the description at the top of the Item entity page for details about supported item types.
ADDITIONAL FIELDS
ActiveTrue – False
Inactivating an item is achieved by setting the Active attribute to false.
SKUThe stock keeping unit (SKU) for this Item. This is a company-defined identifier for an item or product used in tracking inventory.

maximum of 100 chars.
minorVersion: 4
Unit PricePrice of the item.
TrackQtyOnHandTrue - False
QtyOnHandCurrent quantity of the Inventory items available for sale.
Not used for Service or NonInventory type items.Required for Inventory type items.
AssetAccountRefReference to the Inventory Asset account that tracks the current value of the inventory. If the same account is used for all inventory items, the current balance of this account will represent the current total value of the inventory. Must be an account with account type of Other Current Asset.

Use Account.Id and Account.Name from that object for AssetAccountRef.value and AssetAccountRef.name, respectively. Required for Inventory item types.

Account ID*: The ID for the referenced asset account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
InvStartDateDate of opening balance for the inventory transaction. Required when creating an Item.Type=Inventory. Required for Inventory item types.

Local timezone: YYYY-MM-DD UTC: YYYY-MM-DDZ Specific time zone: YYYY-MM-DD+/-HH:MM
The date format follows the XML Schema standard.
ExpenseAccountRefReference to the expense account used to pay the vendor for this item. Must be an account with account type of Cost of Goods Sold.

Account ID*: The ID for the referenced expense account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

(*) required field

Response sample from Update Item 
{
  "Item": {
    "FullyQualifiedName": "Rock Fountain", 
    "domain": "QBO", 
    "Id": "5", 
    "Name": "Rock Fountain", 
    "TrackQtyOnHand": true, 
    "Type": "Inventory", 
    "PurchaseCost": 125, 
    "QtyOnHand": 2, 
    "IncomeAccountRef": {
      "name": "Sales of Product Income", 
      "value": "79"
    }, 
    "AssetAccountRef": {
      "name": "Inventory Asset", 
      "value": "81"
    }, 
    "Taxable": true, 
    "MetaData": {
      "CreateTime": "2014-09-16T10:42:19-07:00", 
      "LastUpdatedTime": "2015-04-22T11:10:18-07:00"
    }, 
    "sparse": false, 
    "Active": true, 
    "SyncToken": "3", 
    "InvStartDate": "2014-09-19", 
    "UnitPrice": 275, 
    "ExpenseAccountRef": {
      "name": "Cost of Goods Sold", 
      "value": "80"
    }, 
    "PurchaseDesc": "Rock Fountain", 
    "Description": "New, updated description for Rock Fountain"
  }, 
  "time": "2015-04-22T11:08:31.596-07:00"
}
Expand
Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.
 
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Payment API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Payment update.
Additional fields: Currency Reference, Project Reference, Line, Private Note, Deposit to Account Reference, Exchange Rate, Transaction source, Transaction Date, Transaction Location Type, Meta Data, Payment Reference Number.
ID*Unique identifier of the Item.
Total amount*Indicates the total amount of the transaction. This includes the total of all the charges, allowances, and taxes.

If you process a linked refund transaction against a specific transaction, the totalAmt value won’t change. It will remain the same. However, voiding the linked refund will change the totalAmt value to 0.
Customer reference*Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Payment Method Reference*Reference to a Payment Method associated with this transaction.

[+ Add Field] add more fields.
Value*: The ID for the referenced payment method.
Name: Name derived from the field that holds the common name of that payment method.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Currency ReferenceReference to the currency in which all amounts on the associated transaction are expressed. This must be defined if multi-currency is enabled for the company. Read more about multi-currency support here.

Currency ID: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency.
Project referenceReference to the Project ID associated with this transaction.

Project ID: The ID for the referenced Project.
Name: Name derived from the field that holds the common name of that project.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line
Zero or more transactions accounting for this payment.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Payment Line can be added as elements.

Element 1: Represents the first Payment Line.

Amount*: The amount of the line item.

Linked Transaction*: Transaction to which the current entity is related. For example, a billpayment line links to the originating bill object for which the billpayment is applied.

_ Transaction ID*: Transaction id of the related transaction.
_ Transaction Type*: Possible values:
Expense
Check
Credit Card Credit
Journal Entry
Credit Memo
Invoice
Private Note
Max of 4000 chars.		User-entered, organization-private note about the transaction. This field maps to the Memo field on the Expense form in the QuickBooks UI.
Deposit to Account ReferenceIdentifies the account to be used for this payment.

[+ Add Field] add more fields.
Value*: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Exchange RateThis field represents the exchange rate, which is the number of your company’s home currency units needed to equal one unit of a different currency.

This field is only applicable if your company uses multiple currencies.
Transaction sourceUsed internally to specify originating source of a credit card transaction.
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Transaction Location Type
For France Only.		The account location. Valid values include:
Within France
France Overseas
Outside France With EU
Outside EU
Meta DataDescriptive information about the entity. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM
Payment Reference Number
For France Only.		Provide the reference number for the payment received. For example, use the Check number for checks and the envelope number for cash donations. This field is a mandatory requirement for transactions in France.

(*) required field

Response sample from Update Payment 
{
  "Payment": {
    "SyncToken": "1", 
    "domain": "QBO", 
    "PaymentMethodRef": {
      "value": "16"
    }, 
    "UnappliedAmt": 0, 
    "TxnDate": "2013-03-13", 
    "TotalAmt": 0, 
    "ProjectRef": {
      "value": "39298045"
    }, 
    "PaymentRefNum": "123456", 
    "sparse": false, 
    "Line": [
      {
        "Amount": 300, 
        "LinkedTxn": [
          {
            "TxnId": "67", 
            "TxnType": "Invoice"
          }
        ]
      }, 
      {
        "Amount": 300, 
        "LinkedTxn": [
          {
            "TxnId": "68", 
            "TxnType": "CreditMemo"
          }
        ]
      }
    ], 
    "CustomerRef": {
      "value": "16"
    }, 
    "Id": "69", 
    "MetaData": {
      "CreateTime": "2013-03-13T14:49:21-07:00", 
      "LastUpdatedTime": "2013-03-13T14:49:21-07:00"
    }
  }, 
  "time": "2013-03-13T14:49:41.512-07:00"
}
Expand

Update Journal Entry Copy Link

Only the elements explicitly included in the update Method are modified. Elements omitted from the request remain unchanged.
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Journal Entry API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Journal Entry creation.
Additional fields: DocNumber.
ID*Unique identifier of the Journal Entry.
Line*
Individual line items of a transaction.
There must be at least one pair of Journal Entry Line elements, representing a debit and a credit, called distribution lines.
Set Line Detail Type to Journal Entry Line for both lines.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Journal Entry Line can be added as elements.

Element 1: Represents the first Journal Entry Line.

Detail Type*: Set to Journal Entry Line Detail.

Amount*: The amount of the line item.

Journal Entry Line Detail*:
_ Posting Type*: Indicates whether this Journal Entry line is a Debit or Credit.

_ Account Reference*: Reference to the account associated with this line.
___ Value*: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
⚠️ If this account has same location as specified in the transaction by the TransactionLocationType attribute and the same VAT as in the line item TaxCodeRef attribute, then this account is used.
⚠️ If there is a mismatch, then the account from the account category list that matches the transaction location and VAT is used.
⚠️ If this account is not present in the account category list, then a new account is created with the new location, new VAT code, and all other attributes as in the default account.


Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.
ADDITIONAL FIELDS
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response sample from Update Journal Entry 
{
  "time": "2015-06-29T12:54:38.135-07:00", 
  "JournalEntry": {
    "DocNumber": "1112", 
    "SyncToken": "1", 
    "domain": "QBO", 
    "TxnDate": "2015-11-30", 
    "PrivateNote": "Revised private note via sparse update", 
    "sparse": true, 
    "Line": [
      {
        "JournalEntryLineDetail": {
          "PostingType": "Debit", 
          "AccountRef": {
            "name": "Job Expenses:Job Materials:Fountain and Garden Lighting", 
            "value": "65"
          }
        }, 
        "DetailType": "JournalEntryLineDetail", 
        "Amount": 25.54, 
        "Id": "0", 
        "Description": "Four sprinkler heads damaged"
      }, 
      {
        "JournalEntryLineDetail": {
          "PostingType": "Credit", 
          "AccountRef": {
            "name": "Notes Payable", 
            "value": "44"
          }
        }, 
        "DetailType": "JournalEntryLineDetail", 
        "Amount": 25.54, 
        "Id": "1", 
        "Description": "Sprinkler Hds - Sprinkler Hds Inventory Adjustment"
      }
    ], 
    "Adjustment": false, 
    "Id": "227", 
    "TxnTaxDetail": {}, 
    "MetaData": {
      "CreateTime": "2015-06-29T12:33:57-07:00", 
      "LastUpdatedTime": "2015-06-29T12:54:38-07:00"
    }
  }
}
Expand
Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL. 
  
Only certain transaction types can be linked to a bill. The most commonly supported transaction types include: 
▪️ BillPaymentCheck – A payment made by check to pay the bill. 
▪️ BillPaymentCreditCard – A payment made by credit card to pay the bill. 
▪️ CreditMemo – A credit memo applied to the bill. 
▪️ JournalEntry – A journal entry affecting the bill. 
 
Transactions like Invoice and Deposit are not typically linked to a bill because a bill represents an expense or liability, while invoices are accounts receivable (money owed to you, not by you). Deposits usually relate to received funds, not expenses. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Bill API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Bill update.
Additional fields: Currency Reference, Ap Account Reference, Sales Term Reference, Linked Transaction, DocNumber.
ID*Unique identifier of the Journal Entry.
Vendors Reference*Reference to the vendor for this transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*: Possible choices for each line:
Account Based Expense Line Detail – Item based Expense Line Detail

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to Detail Type.

Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.

Account Based Expense Line Detail:

_ Account Reference: Reference to the Expense account associated with this item.
___ Account ID: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
⚠️ If this account has same location as specified in the transaction by the TransactionLocationType attribute and the same VAT as in the line item TaxCodeRef attribute, then this account is used.
⚠️ If there is a mismatch, then the account from the account category list that matches the transaction location and VAT is used.
⚠️ If this account is not present in the account category list, then a new account is created with the new location, new VAT code, and all other attributes as in the default account.

Item based Expense Line Detail:
_ Quantity: Number of items for the line.
_ Unit Price: Unit price of the subject item.

_ Item Reference: : Reference to the Item.
___ Value: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference: Reference to a customer or job. 
___ Value: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Currency ReferenceReference to the currency in which all amounts on the associated transaction are expressed. This must be defined if multi-currency is enabled for the company. Read more about multi-currency support here.

[+ Add Field] add more fields:
Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency.
Ap Account ReferenceSpecifies to which AP account the bill is credited. 

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

⚠️ The specified account must have Account.Classification set to Liability and Account.AccountSubType set to AccountsPayable. If the company has a single AP account, the account is implied. However, it is recommended that the AP Account be explicitly specified in all cases to prevent unexpected errors when relating transactions to each other.
Sales Term ReferenceReference to the Term associated with the transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced sales term.
Name: Name derived from the field that holds the common name of that sales term.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Linked TransactionZero or more transactions linked to this Bill object.

[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Linked Transaction can be added as elements.

Element 1: Represents the first Linked Transaction.

Transaction ID: Unique identifier of the related transaction.
Transaction Type: Possible values:
BillPaymentCheck – A payment made by check to pay the bill.
BillPaymentCreditCard – A payment made by credit card to pay the bill.
CreditMemo – A credit memo applied to the bill.
JournalEntry – A journal entry affecting the bill.
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response Sample from update Bill 
{
  "Bill": {
    "DocNumber": "56789", 
    "SyncToken": "2", 
    "domain": "QBO", 
    "APAccountRef": {
      "name": "Accounts Payable", 
      "value": "49"
    }, 
    "VendorRef": {
      "name": "Bayshore CalOil Service", 
      "value": "81"
    }, 
    "TxnDate": "2014-04-04", 
    "TotalAmt": 200.0, 
    "CurrencyRef": {
      "name": "United States Dollar", 
      "value": "USD"
    }, 
    "PrivateNote": "This is a updated memo.", 
    "SalesTermRef": {
      "value": "12"
    }, 
    "DepartmentRef": {
      "name": "Garden Services", 
      "value": "1"
    }, 
    "DueDate": "2013-06-09", 
    "sparse": false, 
    "Line": [
      {
        "Description": "Gasoline", 
        "DetailType": "AccountBasedExpenseLineDetail", 
        "ProjectRef": {
          "value": "39298034"
        }, 
        "Amount": 200.0, 
        "Id": "1", 
        "AccountBasedExpenseLineDetail": {
          "TaxCodeRef": {
            "value": "TAX"
          }, 
          "AccountRef": {
            "name": "Automobile", 
            "value": "75"
          }, 
          "BillableStatus": "Billable", 
          "CustomerRef": {
            "name": "Blackwell, Edward", 
            "value": "20"
          }, 
          "MarkupInfo": {
            "Percent": 10
          }
        }
      }
    ], 
    "Balance": 200.0, 
    "Id": "890", 
    "MetaData": {
      "CreateTime": "2014-04-04T12:38:01-07:00", 
      "LastUpdatedTime": "2014-04-04T12:58:16-07:00"
    }
  }, 
  "time": "2014-04-04T12:58:16.491-07:00"
}
Expand
Only the elements explicitly included in the update Method are modified. Elements omitted from the request remain unchanged. 
 
▪️ A SalesReceipt object must have at least one line that describes an item and an amount. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Sales Receipt API reference. 
 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Sale Receipt update.
Additional fields: DocNumber.
ID*Unique identifier of the Sale receipt.
Line*
The minimum line item required for the request is Sales Item Line or Group Line.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type* Possible values for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

Sale Item Line Detail*:
_ Item Reference*: : Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Unit Price: Unit price of the subject item as referenced by ItemRef.

_ Quantity: Number of items for the line.

_ Tax Code Reference: Reference to the TaxCode for this item. 
[+ Add Field] add more fields:
___ Value: The ID for the referenced Tax Code.

[+ Add Field] add more fields:
Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.
ADDITIONAL FIELDS
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response Sample from Update Sale Receipt 
{
  "SalesReceipt": {
    "DocNumber": "1003", 
    "SyncToken": "2", 
    "domain": "QBO", 
    "Balance": 0, 
    "DepositToAccountRef": {
      "name": "Undeposited Funds", 
      "value": "4"
    }, 
    "TxnDate": "2015-07-29", 
    "TotalAmt": 337.5, 
    "CustomerMemo": {
      "value": "A sparsely updated customer memo."
    }, 
    "PrintStatus": "NeedToPrint", 
    "EmailStatus": "NotSet", 
    "sparse": true, 
    "Line": [
      {
        "Description": "Custom Design", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 4.5, 
          "UnitPrice": 75, 
          "ItemRef": {
            "name": "Design", 
            "value": "4"
          }
        }, 
        "LineNum": 1, 
        "Amount": 337.5, 
        "Id": "1"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 337.5, 
        "SubTotalLineDetail": {}
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "Id": "11", 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "MetaData": {
      "CreateTime": "2014-09-16T14:59:48-07:00", 
      "LastUpdatedTime": "2015-07-29T09:45:55-07:00"
    }
  }, 
  "time": "2015-07-29T09:45:39.381-07:00"
}
Expand
Only the elements explicitly included in the update Method are modified. Elements omitted from the request remain unchanged. 
 
▪️ An Estimate must have at least one line that describes an item. 
▪️ An Estimate must have a reference to a customer. 
▪️ If shipping address and billing address are not provided, the address from the referenced Customer object is used. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Estimate API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Estimate update.
Additional fields: Shipping Address, Customer Reference, Apply Tax After Discount.
ID*Unique identifier of the Estimate.
Customer Reference*Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Bill Email*Identifies the e-mail address where the estimate is sent.

Address*: An email address. The address format must follow the RFC 822 standard.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type* Possible values :
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

Sale Item Line Detail*:
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

[+ Add Field] add more fields:
_ Unit Price: Unit price of the subject item as referenced by ItemRef.
_ Quantity: Number of items for the line.
_ Tax Code Reference: Reference to the TaxCode for this item. 
[+ Add Field] add more fields:
___ Value: The ID for the referenced Tax Code.
ADDITIONAL FIELDS
Customer MemoValue*: User’s message to the customer; this message is visible to the end user on their transactions.
Max 1000 chars.
Shipping AddressThis field indicates the shipping address for the goods. If no specific shipping address is provided, QuickBooks will automatically use the default shipping address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

[+ Add Field] add more fields:
City
Line1
Postal Code
Latitude
longitude
Country Sub Division Code
Apply Tax After Discount
apply to USA.		True – False
If false or null, calculate the sales tax first, and then apply the discount. If true, subtract the discount first and then calculate the sales tax.

(*) required field

Response Sample from Update Estimate 
{
  "Estimate": {
    "TxnDate": "2014-09-07", 
    "domain": "QBO", 
    "PrintStatus": "NeedToPrint", 
    "TxnStatus": "Closed", 
    "TotalAmt": 582.5, 
    "Line": [
      {
        "Description": "Rock Fountain", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 1, 
          "UnitPrice": 275, 
          "ItemRef": {
            "name": "Rock Fountain", 
            "value": "5"
          }
        }, 
        "LineNum": 1, 
        "Amount": 275.0, 
        "Id": "1"
      }, 
      {
        "Description": "Custom Design", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 3.5, 
          "UnitPrice": 75, 
          "ItemRef": {
            "name": "Design", 
            "value": "4"
          }
        }, 
        "LineNum": 2, 
        "Amount": 262.5, 
        "Id": "2"
      }, 
      {
        "Description": "Fountain Pump", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 2, 
          "UnitPrice": 22.5, 
          "ItemRef": {
            "name": "Pump", 
            "value": "11"
          }
        }, 
        "LineNum": 3, 
        "Amount": 45.0, 
        "Id": "3"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 582.5, 
        "SubTotalLineDetail": {}
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "DocNumber": "1001", 
    "sparse": true, 
    "CustomerMemo": {
      "value": "An updated memo via full update the second time."
    }, 
    "ProjectRef": {
      "value": "39298033"
    }, 
    "CustomerRef": {
      "name": "Geeta Kalapatapu", 
      "value": "10"
    }, 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "SyncToken": "4", 
    "LinkedTxn": [
      {
        "TxnId": "103", 
        "TxnType": "Invoice"
      }
    ], 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "ShipAddr": {
      "CountrySubDivisionCode": "CA", 
      "City": "Middlefield", 
      "PostalCode": "94303", 
      "Id": "119", 
      "Line1": "1987 Main St."
    }, 
    "EmailStatus": "NotSet", 
    "BillAddr": {
      "Line3": "Middlefield, CA  94303", 
      "Id": "59", 
      "Line1": "Geeta Kalapatapu", 
      "Line2": "1987 Main St."
    }, 
    "MetaData": {
      "CreateTime": "2014-09-17T11:20:06-07:00", 
      "LastUpdatedTime": "2015-07-24T14:17:23-07:00"
    }, 
    "BillEmail": {
      "Address": "Geeta@Kalapatapu.com"
    }, 
    "Id": "41"
  }, 
  "time": "2015-07-24T14:17:23.307-07:00"
}
Expand
Only the elements explicitly included in the update Method are modified. Elements omitted from the request remain unchanged. 
  
A deposit must include at least one deposit line, which can be either a direct deposit or a deposit linked to a previous transaction. 
Multiple deposit lines of different types can be included in a single request. 
 
For a direct deposit, each line must specify: 
▪️ The target account (Deposit.Line.DepositLineDetail.AccountRef). 
▪️ The overall deposit destination account (Deposit.DepositToAccountRef). 
 
For a deposit linked to a previous transaction, each line must specify: 
▪️ The linked transaction (Deposit.Line.LinkedTxn). 
▪️ The overall deposit destination account (Deposit.DepositToAccountRef). 
  
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Deposit API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Deposit update.
Additional fields: Deposit to Account Reference.
ID*Unique identifier of the Deposit.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*: Possible values : Deposit Line detail.

Amount*: The amount of the deposit.

Deposit Line Detail*:
_ Account Reference*: Account where the funds are deposited.
___ Value*: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Deposit to Account ReferenceIdentifies the account to be used for this deposit.

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

(*) required field

Response Sample from Update Deposit 
{
  "Deposit": {
    "SyncToken": "1", 
    "domain": "QBO", 
    "DepositToAccountRef": {
      "name": "Checking", 
      "value": "35"
    }, 
    "TxnDate": "2014-12-02", 
    "TotalAmt": 20.0, 
    "sparse": true, 
    "Line": [
      {
        "LineNum": 1, 
        "Amount": 20.0, 
        "Id": "1", 
        "DepositLineDetail": {
          "AccountRef": {
            "name": "Unapplied Cash Payment Income", 
            "value": "87"
          }
        }, 
        "DetailType": "DepositLineDetail"
      }
    ], 
    "Id": "146", 
    "MetaData": {
      "CreateTime": "2014-12-10T15:24:40-08:00", 
      "LastUpdatedTime": "2014-12-22T15:13:18-08:00"
    }
  }, 
  "time": "2014-12-22T15:13:17.913-08:00"
}
Expand
Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Credit Memo API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Credit Memo update.
Additional fields: Customer Reference, Bill Email, Customer Memo, Bill Address, Shipping Address.
ID*Unique identifier of the Deposit.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*: Possible values:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the credit memo.

Sales Item Line Detail*:
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Customer Reference*Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Bill EmailIdentifies the e-mail address where the estimate is sent.

[+ Add Field] add more fields:
Address*: An email address. The address format must follow the RFC 822 standard.’
Customer Memo[+ Add Field] add more fields:
Value: User’s message to the customer; this message is visible to the end user on their transactions.
Max 1000 chars.
Bill AddressBill-to address of the credit memo. If no specific bill address is provided, QuickBooks will automatically use the default billing address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

[+ Add Field] add more fields:
Line1
Line2
Line3
Line4
Shipping AddressThis field indicates the shipping address for the goods. If no specific shipping address is provided, QuickBooks will automatically use the default shipping address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

[+ Add Field] add more fields:
Country Sub Division Code
City
Postal Code
line1

(*) required field

Response Sample from Update Credit Memo 
{
  "CreditMemo": {
    "TxnDate": "2014-09-02", 
    "domain": "QBO", 
    "PrintStatus": "NeedToPrint", 
    "TotalAmt": 100.0, 
    "RemainingCredit": 0, 
    "Line": [
      {
        "Description": "Pest Control Services", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 1, 
          "UnitPrice": 100, 
          "ItemRef": {
            "name": "Pest Control", 
            "value": "10"
          }
        }, 
        "LineNum": 1, 
        "Amount": 100.0, 
        "Id": "1"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 100.0, 
        "SubTotalLineDetail": {}
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "DocNumber": "1026", 
    "sparse": false, 
    "CustomerMemo": {
      "value": "Another memo update."
    }, 
    "ProjectRef": {
      "value": "39298045"
    }, 
    "Balance": 0, 
    "CustomerRef": {
      "name": "Amy's Bird Sanctuary", 
      "value": "1"
    }, 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "SyncToken": "5", 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "ShipAddr": {
      "CountrySubDivisionCode": "CA", 
      "City": "Bayshore", 
      "PostalCode": "94326", 
      "Id": "108", 
      "Line1": "4581 Finch St."
    }, 
    "EmailStatus": "NotSet", 
    "BillAddr": {
      "Line4": "Bayshore, CA  94326", 
      "Line3": "4581 Finch St.", 
      "Id": "79", 
      "Line1": "Amy Lauterbach", 
      "Line2": "Amy's Bird Sanctuary"
    }, 
    "MetaData": {
      "CreateTime": "2014-09-18T12:51:27-07:00", 
      "LastUpdatedTime": "2015-07-23T09:23:52-07:00"
    }, 
    "BillEmail": {
      "Address": "Birds@Intuit.com"
    }, 
    "Id": "73"
  }, 
  "time": "2015-07-23T09:23:52.115-07:00"
}
Expand
Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference.
See Quickbooks Purchase Order API reference.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Purchase Order update.
Additional fields: AP Account Reference, Vendor Reference, DocNumber.
ID*Unique identifier of the Purchase Order.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*
Value: Item based Expense Line Detail, Account Based Expense Line Detail.


Amount*: amount, price of the line.

Item Based Expense Line Detail*
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference*: Reference to a customer or job.
___ Value*: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Quantity*: Number of items.

_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.

_ Billable Status: The billable status of the expense. This field is not updatable through an API request. The value automatically changes when an invoice is created.
Possible values: Billable, Not Billable, Has Been Billed

_ Unit Price: Unit price of the subject item as referenced by ItemRef.
Corresponds to the Rate column on the QuickBooks Online UI to specify either unit price, a discount, or a tax rate for item. If used for unit price, the monetary value of the service or product, as expressed in the home currency. If used for a discount or tax rate, express the percentage as a fraction. For example, specify 0.4 for 40% tax.
AP Account Reference*This field indicates the Accounts Payable (AP) account used to record the bill.

While many small businesses may only have one AP account, it’s crucial to always explicitly specify the account.
This ensures accurate record-keeping, especially for businesses with multiple AP accounts.
The specified account must be a Liability account specifically designated for Payables.
Failing to explicitly specify the AP account can lead to unexpected errors when linking transactions within your accounting system.

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Vendor Reference*Reference to the vendor for this transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
DocNumberThis field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.

(*) required field

Response Sample from Update Purchase Order 
{
  "PurchaseOrder": {
    "DocNumber": "1005", 
    "SyncToken": "1", 
    "domain": "QBO", 
    "APAccountRef": {
      "name": "Accounts Payable (A/P)", 
      "value": "33"
    }, 
    "CurrencyRef": {
      "name": "United States Dollar", 
      "value": "USD"
    }, 
    "TxnDate": "2015-07-28", 
    "TotalAmt": 25.0, 
    "ShipAddr": {
      "Line4": "Half Moon Bay, CA  94213", 
      "Line3": "65 Ocean Dr.", 
      "Id": "121", 
      "Line1": "Grace Pariente", 
      "Line2": "Cool Cars"
    }, 
    "PrivateNote": "This is a private note added during update.", 
    "VendorAddr": {
      "Line4": "Middlefield, CA  94303", 
      "Line3": "42 Main St.", 
      "Id": "120", 
      "Line1": "Geoff Hicks", 
      "Line2": "Hicks Hardware"
    }, 
    "POStatus": "Open", 
    "sparse": false, 
    "VendorRef": {
      "name": "Hicks Hardware", 
      "value": "41"
    }, 
    "Line": [
      {
        "DetailType": "ItemBasedExpenseLineDetail", 
        "Amount": 25.0, 
        "ProjectRef": {
          "value": "39298034"
        }, 
        "Id": "1", 
        "ItemBasedExpenseLineDetail": {
          "ItemRef": {
            "name": "Garden Supplies", 
            "value": "38"
          }, 
          "CustomerRef": {
            "name": "Cool Cars", 
            "value": "3"
          }, 
          "Qty": 1, 
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "BillableStatus": "NotBillable", 
          "UnitPrice": 25
        }
      }
    ], 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }, 
      {
        "DefinitionId": "2", 
        "Type": "StringType", 
        "Name": "Sales Rep"
      }
    ], 
    "Id": "257", 
    "MetaData": {
      "CreateTime": "2015-07-28T16:01:47-07:00", 
      "LastUpdatedTime": "2015-07-28T16:17:41-07:00"
    }
  }, 
  "time": "2015-07-28T16:17:42.952-07:00"
}
Expand
Only the elements explicitly included in the update Method are modified. Elements omitted from the request remain unchanged.
 
Customer Relationships: Customer relationships can be complex. Some customers may have a hierarchical structure. For example: 
▪️ A team is the main customer, and its individual members are sub-customers. 
▪️ A property management company is the main customer, and the properties they manage are sub-customers. 
 
Tracking Work: You can use the system to track specific tasks or projects associated with a customer. For instance: 
▪️ A homeowner is the customer, and their kitchen remodel is the project with individual tasks. 
▪️ A car owner is the customer, and their car repairs are the projects with individual tasks. 
  
⚠️ The Display Name attribute or at least one of Title, Given Name, Middle Name, Family Name, or Suffix attributes is required during customer creation. 
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Customer  API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Customer update.
Additional fields: Primary Email Address, Suffix, Title, Middle Name, Notes, Primary Phone, Company Name, Bill Address, Given Name.
ID*Unique Identifier of the Customer.
Family Name*Family name or the last name of the person.
Display Name*The Display Name is how the person or organization is identified within the system. It must be unique within the system (across Customers, Vendors, and Employees). This field cannot be removed using sparse updates.

If not provided, the system will create one for you by combining the customer’s name components (like title, first name, last name).
ADDITIONAL FIELDS
Primary Email AddressPrimary email address.

[+ Add Field] add more fields.
Address: An email address, the format must follow the RFC 822 standard.
SuffixSuffix of the name. For example, Jr. 
TitleTitle of the person.

This tag supports i18n (localized translations of titles such as “Mr.,” “Ms.,” “Dr.,” “Prof.,” or job-related titles like “CEO” and “Manager” in different languages and cultures).
Middle NameMiddle name of the person. The person can have zero or more middle names.
Notes
Max 2000 chars.		Free form text describing the Customer.
Primary Phone
Max 30 chars.		Primary phone number.

[+ Add Field] add more fields.
Free for Number.
Company NameThe name of the company associated with the person or organization.
Bill AddressDefault billing address.

When a physical address is updated within a transaction object, the QuickBooks Online API organizes the address components differently in the transaction response compared to when it was initially created:
The Line1 and Line2 fields are now filled with the customer name and company name.
The original Line1 to Line5, along with City, SubDivisionCode (State/Province), and PostalCode, are shifted into Line3 through Line5 as free-form text.

[+ Add Field] add more fields.
Country Sub Division Code
City
Postal Code
line1
Country
Given NameGiven name or first name of a person.

(*) required field

Response Sample from Update Customer 
{
  "Customer": {
    "domain": "QBO", 
    "PrimaryEmailAddr": {
      "Address": "Surf@Intuit.com"
    }, 
    "DisplayName": "Bill's Windsurf Shop", 
    "PreferredDeliveryMethod": "Print", 
    "GivenName": "Bill", 
    "FullyQualifiedName": "Bill's Windsurf Shop", 
    "BillWithParent": false, 
    "Job": false, 
    "BalanceWithJobs": 85.0, 
    "PrimaryPhone": {
      "FreeFormNumber": "(415) 444-6538"
    }, 
    "Active": true, 
    "MetaData": {
      "CreateTime": "2014-09-11T16:49:28-07:00", 
      "LastUpdatedTime": "2015-07-23T11:07:55-07:00"
    }, 
    "BillAddr": {
      "City": "Half Moon Bay", 
      "Line1": "12 Ocean Dr.", 
      "PostalCode": "94213", 
      "Lat": "37.4307072", 
      "Long": "-122.4295234", 
      "CountrySubDivisionCode": "CA", 
      "Id": "3"
    }, 
    "MiddleName": "Mark", 
    "Taxable": false, 
    "Balance": 85.0, 
    "SyncToken": "1", 
    "CompanyName": "Bill's Windsurf Shop", 
    "FamilyName": "Lucchini", 
    "PrintOnCheckName": "Bill's Windsurf Shop", 
    "sparse": true, 
    "Id": "2"
  }, 
  "time": "2015-07-23T11:07:55.772-07:00"
}
Expand
Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.  
 
⚠️ The Display Name attribute or at least one of Title, Given Name, Middle Name, Family Name, or Suffix attributes is required during customer creation.
 
See Quickbooks Vendor  API reference.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Vendor update.
Additional fields: Print on Check Name, Primary Email Address, Suffix, Title, Tax Identifier, Account Number, Primary Phone, Web Address, Mobile, Company Name, Bill Address, Given Name.
ID*Unique Identifier of the Vendor.
Family Name*Family name or the last name of the person.
Display NameThe Display Name is how the person or organization is identified within the system. It must be unique within the system (across Customers, Vendors, and Employees). This field cannot be removed using sparse updates.

If not provided, the system will create one for you by combining the customer’s name components (like title, first name, last name).
ADDITIONAL FIELDS
Print on Check NameThis field displays the name of the person or organization as it should appear on a printed check.
If you don’t provide this name, it will be automatically filled in using the DisplayName.
Primary Email AddressPrimary email address.

[+ Add Field] add more fields.
Address: Email address, the format must follow the RFC 822 standard.
SuffixSuffix of the name. For example, Jr. 
TitleTitle of the person.

This tag supports i18n (localized translations of titles such as “Mr.,” “Ms.,” “Dr.,” “Prof.,” or job-related titles like “CEO” and “Manager” in different languages and cultures).
Tax Identifier
Max 20 chars.		The tax ID of the Person or Organization.

The value is masked in responses, exposing only last four characters. For example, the ID of 123-45-6789 is returned as XXXXXXX6789.
Account Number
Max 100 chars.		Name or number of the account associated with this vendor.
Primary PhonePrimary phone number.

[+ Add Field] add more fields.
Free for Number.
Max 30 chars.
Web Address
Maximum 1000 chars.		[+ Add Field] add more fields.
URI: Uniform Resource Identifier for the web site.
Mobile
Maximum of 30 chars.		Mobile phone number.

[+ Add Field] add more fields.
Free for Number: Specifies the telephone number in free form.
Company NameThe name of the company associated with the person or organization.
Bill AddressDefault billing address.

When a physical address is updated within a transaction object, the QuickBooks Online API organizes the address components differently in the transaction response compared to when it was initially created:
The Line1 and Line2 fields are now filled with the customer name and company name.
The original Line1 to Line5, along with City, SubDivisionCode (State/Province), and PostalCode, are shifted into Line3 through Line5 as free-form text.

[+ Add Field] add more fields.
Country Sub Division Code
City
Postal Code
line1
Country
Given NameGiven name or first name of a person.

(*) required field

Response Sample from Update Vendor 
{
  "Vendor": {
    "PrimaryEmailAddr": {
      "Address": "Books@Intuit.com"
    }, 
    "Vendor1099": false, 
    "domain": "QBO", 
    "GivenName": "Bessie", 
    "DisplayName": "Books by Bessie", 
    "BillAddr": {
      "City": "Palo Alto", 
      "Line1": "15 Main St.", 
      "PostalCode": "94303", 
      "Lat": "37.445013", 
      "Long": "-122.1391443", 
      "CountrySubDivisionCode": "CA", 
      "Id": "31"
    }, 
    "SyncToken": "2", 
    "PrintOnCheckName": "Books by Bessie and Joan", 
    "FamilyName": "Williams", 
    "PrimaryPhone": {
      "FreeFormNumber": "(650) 555-7745"
    }, 
    "AcctNum": "13451234", 
    "CompanyName": "Books by Bessie", 
    "WebAddr": {
      "URI": "http://www.booksbybessie.co"
    }, 
    "sparse": false, 
    "Active": true, 
    "Balance": 0, 
    "Id": "30", 
    "MetaData": {
      "CreateTime": "2014-09-12T10:07:56-07:00", 
      "LastUpdatedTime": "2015-07-28T13:37:05-07:00"
    }
  }, 
  "time": "2015-07-28T13:37:07.196-07:00"
}
Expand

Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.
 
There are five main types of accounts: assets, liabilities, income, expenses, and equity.
All your business’s accounts are listed in your Chart of Accounts, which is a unique list created for your specific business. Accountants often refer to these accounts as “ledgers.”
The “account object” is the tool you’ll use within the QuickBooks system to manage and work with your accounts.
 
See Quickbooks Account  API reference.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Account update.
Additional fields: Currency reference, Meta Data, Current Balance, Active, Sub Account.
ID*Unique Identifier of the Account.
Name*
Must be unique.
max 100 characters.		Name for the Account. Account.Name attribute must not contain double quotes (“) or colon (:).
Account Sub Type*The account sub-type classification and is based on the AccountType value.
Required if AccountType is not specified.

See possible values in the Account type and Account Sub Type List below.
Account Type*A detailed account classification that specifies the use of this account. The type is based on the Classification.
Required if AccountSubType is not specified.

See possible values in the Account type and Account Sub Type List below.
ADDITIONAL FIELDS
Currency referenceReference to the currency in which this account holds amounts.

[+ Add Field] add more fields:
Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency
Meta DataDescriptive information about the entity. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM
Current BalanceSpecifies the balance amount for the current Account. Valid for Balance Sheet accounts.
ActiveTrue – False

Inactive accounts can be hidden from most views and may not be used for new transactions.

(*) required field

Account Type and Account Sub Type List

ASSET ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
BankDefault
CashOnHand (default), Checking, MoneyMarket, RentsHeldInTrust, Savings, TrustAccounts, CashAndCashEquivalents, OtherEarMarkedBankAccounts
Other Current AssetDefault
AllowanceForBadDebts, DevelopmentCosts, EmployeeCashAdvances (default), OtherCurrentAssets, Inventory, Investment_MortgageRealEstateLoans, Investment_Other, Investment_TaxExemptSecurities, Investment_USGovernmentObligations, LoansToOfficers, LoansToOthers, LoansToStockholders, PrepaidExpenses, Retainage, UndepositedFunds, AssetsAvailableForSale, BalWithGovtAuthorities, CalledUpShareCapitalNotPaid, ExpenditureAuthorisationsAndLettersOfCredit, GlobalTaxDeferred, GlobalTaxRefund, InternalTransfers, OtherConsumables, ProvisionsCurrentAssets, ShortTermInvestmentsInRelatedParties, ShortTermLoansAndAdvancesToRelatedParties, TradeAndOtherReceivables
Fixed AssetDefault
AccumulatedDepletion, AccumulatedDepreciation, DepletableAssets, FixedAssetComputers, FixedAssetCopiers, FixedAssetFurniture, FixedAssetPhone, FixedAssetPhotoVideo, FixedAssetSoftware, FixedAssetOtherToolsEquipment, FurnitureAndFixtures (default), Land, LeaseholdImprovements, OtherFixedAssets, AccumulatedAmortization, Buildings, IntangibleAssets, MachineryAndEquipment, Vehicles, AssetsInCourseOfConstruction, CapitalWip, CumulativeDepreciationOnIntangibleAssets, IntangibleAssetsUnderDevelopment, LandAsset, NonCurrentAssets, ParticipatingInterests, ProvisionsFixedAssets
Other AssetDefault
LeaseBuyout, OtherLongTermAssets, SecurityDeposits, AccumulatedAmortizationOfOtherAssets, Goodwill, Licenses (default), OrganizationalCosts, AssetsHeldForSale, AvailableForSaleFinancialAssets, DeferredTax, Investments, LongTermInvestments, LongTermLoansAndAdvancesToRelatedParties, OtherIntangibleAssets, OtherLongTermInvestments, OtherLongTermLoansAndAdvances, PrepaymentsAndAccruedIncome, ProvisionsNonCurrentAssets
Accounts ReceivableDefault
Accounts Receivable

EQUITY ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
EquityDefault
OpeningBalanceEquity (default), PartnersEquity, RetainedEarnings, AccumulatedAdjustment, OwnersEquity, PaidInCapitalOrSurplus, PartnerContributions, PartnerDistributions, PreferredStock, CommonStock, TreasuryStock, EstimatedTaxes, Healthcare, PersonalIncome, PersonalExpense, AccumulatedOtherComprehensiveIncome, CalledUpShareCapital, CapitalReserves, DividendDisbursed, EquityInEarningsOfSubsidiaries, InvestmentGrants, MoneyReceivedAgainstShareWarrants, OtherFreeReserves, ShareApplicationMoneyPendingAllotment, ShareCapital, Funds

EXPENSE ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
ExpenseDefault
AdvertisingPromotional, BadDebts, BankCharges, CharitableContributions, CommissionsAndFees, Entertainment, EntertainmentMeals, EquipmentRental, FinanceCosts, GlobalTaxExpense, Insurance, InterestPaid, LegalProfessionalFees, OfficeExpenses, OfficeGeneralAdministrativeExpenses, OtherBusinessExpenses, OtherMiscellaneousServiceCost, PromotionalMeals, RentOrLeaseOfBuildings, RepairMaintenance, ShippingFreightDelivery, SuppliesMaterials, Travel (default), TravelMeals, Utilities, Auto, CostOfLabor, DuesSubscriptions, PayrollExpenses, TaxesPaid, UnappliedCashBillPaymentExpense, Utilities, AmortizationExpense, AppropriationsToDepreciation, BorrowingCost, CommissionsAndFees, DistributionCosts, ExternalServices, ExtraordinaryCharges, IncomeTaxExpense, LossOnDiscontinuedOperationsNetOfTax, ManagementCompensation, OtherCurrentOperatingCharges, OtherExternalServices, OtherRentalCosts, OtherSellingExpenses, ProjectStudiesSurveysAssessments, PurchasesRebates, ShippingAndDeliveryExpense, StaffCosts, Sundry, TravelExpensesGeneralAndAdminExpenses, TravelExpensesSellingExpense
Other ExpenseDefault
Depreciation (default), ExchangeGainOrLoss, OtherMiscellaneousExpense, PenaltiesSettlements, Amortization, GasAndFuel, HomeOffice, HomeOwnerRentalInsurance, OtherHomeOfficeExpenses, MortgageInterest, RentAndLease, RepairsAndMaintenance, ParkingAndTolls, Vehicle, VehicleInsurance, VehicleLease, VehicleLoanInterest, VehicleLoan, VehicleRegistration, VehicleRepairs, OtherVehicleExpenses, Utilities, WashAndRoadServices, DeferredTaxExpense, Depletion, ExceptionalItems, ExtraordinaryItems, IncomeTaxOtherExpense, MatCredit, PriorPeriodItems, TaxRoundoffGainOrLoss
Cost of Goods SoldDefault
EquipmentRentalCos, OtherCostsOfServiceCos, ShippingFreightDeliveryCos, SuppliesMaterialsCogs, CostOfLaborCos (default), CostOfSales, FreightAndDeliveryCost

LIABILITY ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
Accounts PayableDefault
Accounts Payable, OutstandingDuesMicroSmallEnterprise, OutstandingDuesOtherThanMicroSmallEnterprise
Credit CardDefault
Credit Card
Long Term LiabilityDefault
NotesPayable (default), OtherLongTermLiabilities, ShareholderNotesPayable, AccrualsAndDeferredIncome, AccruedLongTermLiabilities, AccruedVacationPayable, BankLoans, DebtsRelatedToParticipatingInterests, DeferredTaxLiabilities, GovernmentAndOtherPublicAuthorities, GroupAndAssociates, LiabilitiesRelatedToAssetsHeldForSale, LongTermBorrowings, LongTermDebit, LongTermEmployeeBenefitObligations, ObligationsUnderFinanceLeases, OtherLongTermProvisions, ProvisionForLiabilities, ProvisionsNonCurrentLiabilities, StaffAndRelatedLongTermLiabilityAccounts
Other Current LiabilityDefault
DirectDepositPayable, LineOfCredit, LoanPayable, GlobalTaxPayable, GlobalTaxSuspense, OtherCurrentLiabilities (default), PayrollClearing, PayrollTaxPayable, PrepaidExpensesPayable, RentsInTrustLiability, TrustAccountsLiabilities, FederalIncomeTaxPayable, InsurancePayable, SalesTaxPayable, StateLocalIncomeTaxPayable, AccruedLiabilities, CurrentLiabilities, CurrentPortionEmployeeBenefitsObligations, CurrentPortionOfObligationsUnderFinanceLeases, CurrentTaxLiability, DividendsPayable, DutiesAndTaxes, InterestPayables, ProvisionForWarrantyObligations, ProvisionsCurrentLiabilities, ShortTermBorrowings, SocialSecurityAgencies, StaffAndRelatedLiabilityAccounts, SundryDebtorsAndCreditors, TradeAndOtherPayables

REVENUE ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
IncomeDefault
NonProfitIncome, OtherPrimaryIncome (default), SalesOfProductIncome, ServiceFeeIncome, DiscountsRefundsGiven, UnappliedCashPaymentIncome, CashReceiptIncome, OperatingGrants, OtherCurrentOperatingIncome, OwnWorkCapitalized, RevenueGeneral, SalesRetail, SalesWholesale, SavingsByTaxScheme
Other IncomeDefault
DividendIncome, InterestEarned, OtherInvestmentIncome (default), OtherMiscellaneousIncome, TaxExemptInterest, GainLossOnSaleOfFixedAssets, GainLossOnSaleOfInvestments, LossOnDisposalOfAssets, OtherOperatingIncome, UnrealisedLossOnSecuritiesNetOfTax

Response Sample from Update Account 
{
  "Account": {
    "FullyQualifiedName": "Accounts Payable (A/P)", 
    "domain": "QBO", 
    "SubAccount": false, 
    "Description": "Description added during update.", 
    "Classification": "Liability", 
    "AccountSubType": "AccountsPayable", 
    "CurrentBalanceWithSubAccounts": -1091.23, 
    "sparse": false, 
    "MetaData": {
      "CreateTime": "2014-09-12T10:12:02-07:00", 
      "LastUpdatedTime": "2015-07-13T15:35:13-07:00"
    }, 
    "AccountType": "Accounts Payable", 
    "CurrentBalance": -1091.23, 
    "Active": true, 
    "SyncToken": "1", 
    "Id": "33", 
    "Name": "Accounts Payable (A/P)"
  }, 
  "time": "2015-07-13T15:31:25.618-07:00"
}
Expand
Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.  
  
To create a Purchase:  
▪️ You must specify an Account Reference for all purchases.  
▪️ The Total Amount attribute must add up to sum of Line.Amount attributes.  
  
There are three types of purchases: Cash, Check, and Credit Card.  
▪️ Cash Purchase contains information regarding a payment made in cash.  
▪️ Check Purchase contains information regarding a payment made by check.  
▪️ Credit Card Purchase contains information regarding a payment made by credit card or refunded/credited back to a credit card.  
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Purchase API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Purchase update.
Additional fields: Account Reference, Currency Reference, Transaction Date, Print Status, Transaction Source, Global Tax Calculation, Transaction Location Type, Document Number, Private Note, Credit, Payment Method Reference, PurchaseEx, Exchange Rate, Department Reference, Entity Reference, Include In Annual TPAR.
ID*Unique Identifier of the Purchase.
Payment type*Payment Type can be: Cash, Check, or Credit Card
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.
Element 1: Represents the first Line.

Detail Type*
Possible values:
– Item based Expense Line Detail (This option is only available when the ‘For Purchase’ preference is activated for Products and Services).
– Account Based Expense Line Detail.

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to Detail Type.

ID: Unique identifier (ID) of the line item.
Update Operation: If a valid ID is provided, the request is treated as an update to an existing line item.
Create Operation: If no ID is provided, or the provided ID is invalid, the request is treated as a creation of a new line item.
This ID field is available in all objects that contain lines and support updates.

Item Based Expense Line Detail:
[+ Add Field] add more related fields.

_Tax Inclusive Amount: represents the total amount of the purchase, including tax if applicable.
Use TaxInclusiveAmount when the total purchase price includes tax, and QuickBooks should derive the pre-tax amount.
Do NOT use it if tax should be calculated separately based on the taxable subtotal.

_ Item Reference*: Reference to the Item.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference*: Reference to a customer or job.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Price Level Reference: Reference to the PriceLevel of the service or item for the line.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced Price Level.
___ Name: Name derived from the field that holds the common name of that price level.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Class Reference: Reference to the Class associated with the expense.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced Class.
___ Name: Name derived from the field that holds the common name of that class.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Tax Code Reference: Reference to the TaxCode for this item.
[+ Add Field] add more fields in Tax Code Reference:
___ Value: The ID for the referenced Tax Code.
___ Name: Name derived from the field that holds the common name of that Tax Code.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Markup Info: Markup information for the expense.
[+ Add Field] add more fields.
___ Price Level Reference: Reference to a PriceLevel for the markup. 
______ Value*: The ID for the referenced Price Level.
______ Name: Name derived from the field that holds the common name of that price level.
___ Percent:Markup amount expressed as a percent of charges already entered in the current transaction. To enter a rate of 10% use 10.0, not 0.01.

_Quantity*: Number of items.

_Unit Price: Unit price of the subject item as referenced by ItemRef.
Corresponds to the Rate column on the QuickBooks Online UI to specify either unit price, a discount, or a tax rate for item. If used for unit price, the monetary value of the service or product, as expressed in the home currency. If used for a discount or tax rate, express the percentage as a fraction. For example, specify 0.4 for 40% tax.

Linked Transaction: Zero or more transactions linked to this Purchase.
[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Linked Transaction can be added as elements.
Element 1: Represents the first Linked Transaction.
_Transaction ID*: Transaction Id of the related transaction.

_Transaction Type*: Bill, BillPaymentCheck, BillPaymentCreditCard, CreditCardCredit, ReimburseCharge, VendorCredit, Expense, Check, Payment

_Transaction Line ID: This field is required for Deposit and Bill entities. It specifies the line number within the linked transaction. If you include this field, you must also provide the TxnId and TxnType of the linked transaction.

Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.

Line Number: Specifies the position of the line in the collection of transaction lines.

Account Based Expense Line Detail:
[+ Add Field] add more fields.

_Account Reference*: This field indicates the account used for this purchase, depending on the payment method (e.g., bank account for checks, credit card account for credit card payments).
[+ Add Field] add more fields in account Reference:
___ Value*: The ID for the referenced account
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Tax Amount: Sales tax paid as part of the expense.
_Tax Inclusive Amount: The total amount of the line item including tax.

_Class Reference: This field specifies the class associated with the expense. Class tracking must be enabled at the line item level in your accounting preferences for this field to be available.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced Class.
___ Name: Name derived from the field that holds the common name of that class.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Tax Code Reference: Reference to the TaxCode for this expense.
[+ Add Field] add more fields in Tax Code Reference:
___ Value*: The ID for the referenced Tax Code.
___ Name: Name derived from the field that holds the common name of that Tax Code.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Markup Info: Markup information for the expense.
[+ Add Field] add more fields.
___ Price Level Reference: Reference to a PriceLevel for the markup. 
______ Value*: The ID for the referenced Price Level.
______ Name: Name derived from the field that holds the common name of that price level.
___ Percent:Markup amount expressed as a percent of charges already entered in the current transaction. To enter a rate of 10% use 10.0, not 0.01.

_Customer Reference: Reference to the Customer associated with the expense.
[+ Add Field] add more fields.
___ Value*: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Account Reference*This field specifies the associated account. For checks, it must be a bank account. For credit cards, it must be a credit card account. The account reference must be valid and currently active.

[+ Add Field] add more fields.
Value*: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Currency referenceReference to the currency in which all amounts on the associated transaction are expressed. This must be defined if multi-currency is enabled for the company. Read more about multi-currency support here.

Value*: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency.
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Print StatusApplicable only for Check.  Ignored for Credit Card charge or refund.
Possible values: Not Set, Need To Print, Print Complete.
Transaction SourceUsed internally to specify originating source of a credit card transaction.
Global Tax CalculationMethod in which tax is applied. Allowed values are: Tax Excluded, Tax Inclusive, and Not Applicable.
Transaction Location Type
For France locales, only.		The account location. Valid values include:
Within France
France Overseas
Outside France With EU
Outside EU
Document Number
Maximum of 21 chars.		This field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.
Private Note
Max of 4000 chars.		User-entered, organization-private note about the transaction. This field maps to the Memo field on the Expense form in the QuickBooks UI.
CreditFalse—it represents a charge. True—it represents a refund. Valid only for Credit Card payment type and Credit Card transactions.
Payment Method ReferenceReference to a Payment Method associated with this transaction.

[+ Add Field] add more fields.
Value*: The ID for the referenced payment method.
Name: Name derived from the field that holds the common name of that payment method.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
PurchaseExFor internal use.
Extension field that allows custom data storage.
It is often used for third-party integrations that need to track extra metadata.
Exchange RateThis field represents the exchange rate, which is the number of your company’s home currency units needed to equal one unit of a different currency.

This field is only applicable if your company uses multiple currencies.
Department ReferenceThis field links the transaction to a specific department within your company. This feature is only available if the ‘Track Departments’ preference is enabled in your accounting settings.

[+ Add Field] add more fields.
Value*: The ID for the referenced department.
Name: Name derived from the field that holds the common name of that department.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Entity ReferenceThis field links an expense transaction to a specific entity.

Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate Customer, Vendor or Employee object for this reference. 

[+ Add Field] add more fields.
Reference Type*: Specifies the type of entity (Customer, Vendor, Employee).
Value*: The ID for the referenced entity.
Name: Name derived from the field that holds the common name of that entity.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Include In Annual TPARTrue – False

Include the supplier in the annual TPAR. TPAR stands for Taxable Payments Annual Report. The TPAR is mandated by ATO to get the details payments that businesses make to contractors for providing services. Some government entities also need to report the grants they have paid in a TPAR.

(*) required field

Response Sample from Update Purchase 
{
  "SyncToken": "1", 
  "domain": "QBO", 
  "PurchaseEx": {
    "any": [
      {
        "name": "{http://schema.intuit.com/finance/v3}NameValue", 
        "nil": false, 
        "value": {
          "Name": "TxnType", 
          "Value": "54"
        }, 
        "declaredType": "com.intuit.schema.finance.v3.NameValue", 
        "scope": "javax.xml.bind.JAXBElement$GlobalScope", 
        "globalScope": true, 
        "typeSubstituted": false
      }
    ]
  }, 
  "TxnDate": "2015-07-27", 
  "TotalAmt": 10.0, 
  "PrivateNote": "Added an updated private note via update.", 
  "PaymentType": "Cash", 
  "sparse": false, 
  "Line": [
    {
      "DetailType": "AccountBasedExpenseLineDetail", 
      "Amount": 10.0, 
      "ProjectRef": {
        "value": "42991284"
      }, 
      "Id": "1", 
      "AccountBasedExpenseLineDetail": {
        "TaxCodeRef": {
          "value": "NON"
        }, 
        "AccountRef": {
          "name": "Meals and Entertainment", 
          "value": "13"
        }, 
        "BillableStatus": "NotBillable"
      }
    }
  ], 
  "AccountRef": {
    "name": "Checking", 
    "value": "35"
  }, 
  "CustomField": [], 
  "Id": "252", 
  "MetaData": {
    "CreateTime": "2015-07-27T10:37:26-07:00", 
    "LastUpdatedTime": "2015-07-27T10:42:11-07:00"
  }
}
Expand
Update any writable field of an existing Payment object. Make sure to includes all fields as returned in the read response. Omitted fields will be set to NULL.  
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Time Activity API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Time Activity update.
Additional fields: Transaction Date, Description, Item Reference, Minutes, Hours, Billable Status, Hourly Rate, Taxable, Customer Reference, Meta Data.
ID*Unique Identifier of the Time Activity.
Name of*This field specifies the type of time activity being recorded. It’s required when creating a new record and must be used in conjunction with either the EmployeeRef or VendorRef attributes.
Possible values: Vendor or Employee.
Employee ReferenceSpecifies the employee whose time is being recorded.

Value: The ID for the referenced employee.
Name: Name derived from the field that holds the common name of that employee.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Vendor ReferenceSpecifies the vendor whose time is being recorded.

Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Start Time*This field indicates the start time of the work. It’s required if the specific hours and minutes are not provided.

Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Important: Only include the hours (e.g., 9, 10, 11) without the time zone offset, as it doesn’t affect the time activity hours calculation.

If Transaction Date is provided: Use the specified Transaction Date (in YYYY-MM-DD format) and include Start Time and End Time in hours and minutes (without time zone offsets).
If Transaction Date is not provided: Use the current server date and include StartTime and EndTime in hours and minutes (with or without time zone offsets).

For historical or future transactions, always include the Transaction Date in YYYY-MM-DD format and specify StartTime and End Time in hours and minutes.
End Time*This field indicates the end time of the work. It’s required if the specific hours and minutes are not provided.

Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Important: Only include the hours (e.g., 5, 6, 7) without the time zone offset, as it doesn’t affect the time activity hours calculation.

If Transaction Date is provided: Use the specified TxnDate (in YYYY-MM-DD format) and include StartTime and EndTime in hours and minutes (without time zone offsets).
If Transaction Date is not provided: Use the current server date and include StartTime and EndTime in hours and minutes (with or without time zone offsets).

For historical or future transactions, always include the Transaction Date in YYYY-MM-DD format and specify StartTime and EndTime in hours and minutes.
ADDITIONAL FIELDS
Transaction DateThe date for the time activity. This field represents the date used for financial reporting.

If no date is provided, the current system date is used.
The default sort order for transactions is ascending by date.

If you specify the start and end times without time zone offsets, you must also provide the transaction date (TxnDate) for any past or future time activities. For example, to record a past time activity, include the TxnDate and specify the start and end times in hours (without time zone offsets).

Local timezone: YYYY-MM-DD UTC: YYYY-MM-DDZ Specific time zone: YYYY-MM-DD+/-HH:MM
The date format follows the XML Schema standard.
Description
maximum 4000 characters.		Description of work completed during time activity.
Item ReferenceReference to the service item associated with this object.

[+ Add Field] add more fields in Item reference:
___ Item ID: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.me
Minutes
Maximum of 8760 hours 59 minutes; if hours is 8760 minutes must be 0		minutes worked.
Hours
Maximum of 8760 hours 59 minutes; if hours is 8760 minutes must be 0		Hours and minutes worked. Required if StartTime and EndTime not specified
Hourly Rate
max character: 0 to 99999999999 hours.		Hourly bill rate of the employee or vendor for this time activity. Required if Billable Status is set to Billable.
TaxableTrue – False
True if the time recorded is both billable and taxable.
Customer ReferenceReference to a customer or job.

[+ Add Field] add more fields.
Value: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Meta DataDescriptive information about the object. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

(*) required field

Response Sample from Update Time Activity 
{
  "TimeActivity": {
    "TxnDate": "2014-09-16", 
    "domain": "QBO", 
    "NameOf": "Employee", 
    "Description": "Updated descirption", 
    "ItemRef": {
      "name": "Design", 
      "value": "4"
    }, 
    "Minutes": 0, 
    "ProjectRef": {
      "value": "39298005"
    }, 
    "Hours": 5, 
    "BillableStatus": "Billable", 
    "sparse": false, 
    "HourlyRate": 75, 
    "Taxable": false, 
    "EmployeeRef": {
      "name": "John Johnson", 
      "value": "54"
    }, 
    "SyncToken": "1", 
    "CustomerRef": {
      "name": "Amy's Bird Sanctuary", 
      "value": "1"
    }, 
    "Id": "3", 
    "MetaData": {
      "CreateTime": "2014-09-17T11:53:15-07:00", 
      "LastUpdatedTime": "2015-07-28T11:59:41-07:00"
    }
  }, 
  "time": "2015-07-28T11:59:41.178-07:00"
}
Expand
Only the elements explicitly included in the update Method are modified. Elements omitted from the request remain unchanged.

A Refund Receipt must include:  
▪️ At least one line item: This details the item(s) being refunded.  
▪️ A designated deposit account: Specified by Deposit To Account Ref.  
  
If no billing address is provided, The customer’s address will be used as the billing address.  
  
Tax Code Restrictions:  
▪️ Custom Sales Tax cannot be used for Transaction Tax Code Ref.  
▪️ This tax code is reserved for transactions using the older sales tax model.  
▪️ You cannot create or update transactions that use TaxCode.CustomSalesTax.  
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Refund Receipt API reference. 
MAP FIELDS [+ Add Field] Select fields from list, to configure the Refund Receipt update.
Additional fields: Document Number, Balance, Payment Method Reference, Bill Address, Transaction Date, Customer Reference, Customer Memo, Shipping Address, Print Status, Bill Email, Line, Apply Tax After Discount, Custom Field, Transaction Tax Detail, Meta Data.
ID*Unique Identifier of the Refund Receipt.
Deposit to Account Reference*Accounts receivable asset account from which payment money is refunded. 

_Reference Type*:
[+ Add Field] add more fields.
___ Value*: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_Currency Reference Type: This field specifies the currency used for all amounts in the transaction. (Required if your company uses multiple currencies (i.e., if Preferences.MultiCurrencyEnabled is set to ‘true’).
For more information, please refer to Manage multiple currencies.

___ Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
___ Name: The full name of the currency.
Line*
The minimum line item required for the request is one of the following: Sales Item Line and Group Line.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.
Element 1: Represents the first Line.

Detail Type*: Possible choices for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Sale Item Line Detail*:
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

[+ Add Field] add more fields:
_ Unit Price: Unit price of the subject item as referenced by ItemRef.
_ Quantity: Number of items for the line.
_ Tax Code Reference: Reference to the TaxCode for this item. 
[+ Add Field] add more fields:
___ Value: The ID for the referenced Tax Code.

Amount*: The amount of the line item.

Description: Free form text description of the line item that appears in the printed record (max character: 4000).

Line Number: Specifies the position of the line in the collection of transaction lines.

ID: Unique identifier (ID) of the line item.
Update Operation: If a valid ID is provided, the request is treated as an update to an existing line item.
Create Operation: If no ID is provided, or the provided ID is invalid, the request is treated as a creation of a new line item.
This ID field is available in all objects that contain lines and support updates.
ADDITIONAL FIELDS
Document Number
Maximum of 21 chars.		This field stores the transaction’s reference number.
You can specify a custom value during creation. If none is provided this field is populated based on the setting of Preferences: CustomTxnNumber.

▪️ If UseCustomTxnNumbers preference is enabled: You can provide a custom DocNumber. Duplicates are not allowed.
▪️ If no custom value is given, DocNumber is null.
▪️ If UseCustomTxnNumbers is disabled: DocNumber is automatically generated by the system.

Cash/CreditCard: Duplicates always cause an error.
Check: Duplicates cause an error only if the WarnDuplicateCheckNumber preference is enabled.

Tips: Check the UseCustomTxnNumbers preference before setting DocNumber manually.
Allow Duplicates: Use the include=allowduplicatedocnum query parameter to allow duplicate DocNumber (not recommended).
Default Sort Order: Ascending order.
Payment Method ReferenceReference to a Payment Method associated with this transaction.

[+ Add Field] add more fields.
Value*: The ID for the referenced payment method.
Name: Name derived from the field that holds the common name of that payment method.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Bill AddressThis field specifies the billing address for the invoice.

If no billing address is provided: QuickBooks will use the default billing address associated with the customer.
For international addresses: Use the 3-letter ISO country code or the full country name.
Address Updates:

If you update the physical address within the transaction itself, the address components will be presented differently in the API response compared to the original creation: Line 1 and Line 2: Will display the customer name and company name.
Line 3 to Line 5: Will contain the original address information (Line 1-5, City, State/Province, Postal Code) as free-form text.

[+ Add Field] add more fields.
Line1
Line2
Postal Code
Latitude
longitude
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Customer ReferenceReference to a customer or job.

Value: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Customer MemoValue: User’s message to the customer; this message is visible to the end user on their transactions.
Shipping AddressThis field indicates the shipping address for the goods. If no specific shipping address is provided, QuickBooks will automatically use the default shipping address associated with the referenced customer in the system.

When entering international addresses, specify the country using either the 3-letter ISO code (e.g., USA, GBR) or the full country name.

If you update the physical address within the transaction itself, the address components will be presented differently in the API response compared to the original creation: Line 1 and Line 2: Will display the customer name and company name.
Line 3 to Line 5: Will contain the original address information (Line 1-5, City, State/Province, Postal Code) as free-form text.

[+ Add Field] add more fields:
City
Line1
Postal Code
Latitude
longitude
Country Sub Division Code
Print StatusApplicable only for Check.  Ignored for Credit Card charge or refund.
Possible values: Not Set, Need To Print, Print Complete.
Bill EmailIdentifies the e-mail address where the estimate is sent.

[+ Add Field] add more fields
Email*: The address format must follow the RFC 822 standard.
Apply Tax After Discount
Apply to USA.		True – False

If false or null, calculate the sales tax first, and then apply the discount. If true, subtract the discount first and then calculate the sales tax.
Custom fieldThis allows you to add up to three custom fields to your transactions.

These fields are available only if they have been configured for your company in the settings:
▪️ Check “Preferences.SalesFormsPrefs.CustomField” for sales transactions.
▪️ Check “Preferences.VendorAndPurchasesPrefs.POCustomField” for purchase orders.

Click here for information on managing custom fields.

[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional custom field can be added as elements.
Element 1: Represents the first custom field.

Value
Name
Field Type
Transaction Tax DetailThis data type contains information about the taxes applied to the entire transaction.
It includes details of sales taxes calculated based on the tax codes specified within the transaction.
▪️ QuickBooks can calculate these taxes automatically.
▪️ You can also provide the tax details when adding a transaction.

Global Tax Model: Refer to the Global Tax Model documentation for more information.
Sales Tax Disabled: If sales tax is disabled in your company’s preferences (Preferences.TaxPrefs.UsingSalesTax is false), this data will be ignored and not stored.

[+ Add Field] add more fields.
Total Tax: Total tax calculated for the transaction, excluding any tax lines manually inserted into the transaction line list.
Meta DataDescriptive information about the entity. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

(*) required field

Response Sample from Update Refund Receipt 
{
  "RefundReceipt": {
    "TxnDate": "2014-09-17", 
    "domain": "QBO", 
    "PrintStatus": "NotSet", 
    "TotalAmt": 87.5, 
    "Line": [
      {
        "Description": "Refund - Pest control was ineffective", 
        "DetailType": "SalesItemLineDetail", 
        "SalesItemLineDetail": {
          "TaxCodeRef": {
            "value": "NON"
          }, 
          "Qty": 2.5, 
          "UnitPrice": 35, 
          "ItemRef": {
            "name": "Pest Control", 
            "value": "10"
          }
        }, 
        "LineNum": 1, 
        "Amount": 87.5, 
        "Id": "1"
      }, 
      {
        "DetailType": "SubTotalLineDetail", 
        "Amount": 87.5, 
        "SubTotalLineDetail": {}
      }
    ], 
    "ApplyTaxAfterDiscount": false, 
    "DocNumber": "1020", 
    "PrivateNote": "This is a new private note added via sparse update.", 
    "sparse": true, 
    "DepositToAccountRef": {
      "name": "Checking", 
      "value": "35"
    }, 
    "CustomerMemo": {
      "value": "Thank you for your business and have a great day!"
    }, 
    "ProjectRef": {
      "value": "39298034"
    }, 
    "Balance": 0, 
    "CustomerRef": {
      "name": "Pye's Cakes", 
      "value": "15"
    }, 
    "TxnTaxDetail": {
      "TotalTax": 0
    }, 
    "SyncToken": "3", 
    "PaymentMethodRef": {
      "name": "Check", 
      "value": "2"
    }, 
    "CustomField": [
      {
        "DefinitionId": "1", 
        "Type": "StringType", 
        "Name": "Crew #"
      }
    ], 
    "ShipAddr": {
      "City": "South Orange", 
      "Line1": "350 Mountain View Dr.", 
      "PostalCode": "07079", 
      "Lat": "40.7633073", 
      "Long": "-74.2426072", 
      "CountrySubDivisionCode": "NJ", 
      "Id": "15"
    }, 
    "BillAddr": {
      "Line4": "South Orange, NJ 07079", 
      "Line3": "350 Mountain View Dr.", 
      "Id": "73", 
      "Line1": "Karen Pye", 
      "Line2": "Pye's Cakes"
    }, 
    "MetaData": {
      "CreateTime": "2014-09-17T15:35:07-07:00", 
      "LastUpdatedTime": "2015-07-29T08:59:30-07:00"
    }, 
    "BillEmail": {
      "Address": "pyescakes@intuit.com"
    }, 
    "Id": "66"
  }, 
  "time": "2015-07-29T08:59:32.061-07:00"
}
Expand
This unified Method facilitates upsert operations for diverse Entities within your QuickBooks account. The method employs matching criteria to search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information.
 
This Method allows you to upsert: 
Invoice, Item, Journal Entry, Bill, Sale Receipt, Purchase Order, Customer, Vendor, Account.

Configuration Table:

Input Options (Field Mapping):

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: Select value from a defined list or specify a fixed attribute.
  • Manual input: Set a custom value by using the Lightning Bold feature.
Name*Upsert
Connection*Select your connection or create one.
Entity*
(Set of data that contain records)		Select the available Entity to upsert records:

Invoice, Item, Journal Entry, Bill, Sale Receipt, Purchase Order, Customer, Vendor, Account.

(*) required field

Configuration table for each Entity:

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information.
 
Note:
▪️ Have at least one Line a sales item or inline subtotal.
▪️ The DocNumber attribute is populated automatically by the data service if not supplied.
▪️ If ShipAddr, BillAddr, or both are not provided, the appropriate customer address from the referenced Customer object is used to fill those values.
 
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Invoice API Reference. 
MATCHING CRITERIA
DocNumber*Equal to the Invoice DocNumber field value.
MAP FIELDS [+ Add Field] Select fields from a list, to configure the invoice upsert.
Additional fields: Sales Term Reference, Transaction Date, Customer Memo, Transaction Tax Detail, Deposit, Line.
Customer Reference*A customer is a consumer of the service or product that your business offers.
Reference to a customer or job.

Customer ID*: The ID for the referenced customer.
Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line*
Invoice line object.
If the transaction is taxable there is a limit of 750 lines per transaction.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Invoice Line.

Detail Type*: Possible choices for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to the Detail Type.

Description: Free form text description of the line item that appears in the printed record.
Max character: 4000.

Line Number: Specifies the position of the line in the collection of transaction lines.

Sale Item Line Detail [+ Add Field] add more fields in Sale Item Line Detail:
_ Quantity: Number of items for the line.
_ Unit Price: Unit price of the subject item as referenced by ItemRef.

_ Discount Amount: Fixed discount.
_ Discount Rate: The discount rate applied to this line. If both Discount are provided, Discount Rate takes precedence and Discount Amount is recalculated by QuickBooks services based on amount of Discount Rate.

_ Item Reference: Reference to an Item object.
[+ Add Field] add more fields in Item reference:
___ Item ID: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Tax Code Reference: Reference to the Tax Code for this item.
[+ Add Field] add more fields in Tax Code Reference:
___ Value: The ID for the referenced Tax Code.
___ Name: Name derived from the field that holds the common name of that Tax Code.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Sales Term ReferenceReference to the sales term associated with the transaction.

Value: The ID for the referenced Sales Term.
Transaction DateThe date entered by the user when this transaction occurred. yyyy/MM/dd is the valid date format.
For posting transactions, this is the posting date that affects the financial statements. If the date is not supplied, the current date on the server is used.
Customer Memo
Max 1000 chars..		Value: User’s message to the customer; this message is visible to the end user on their transactions.
Transaction Tax DetailThis data type provides information for taxes charged on the transaction as a whole. It captures the details sales taxes calculated for the transaction based on the tax codes referenced by the transaction.

Transaction Tax Code Reference:
_ Value: Reference to the transaction tax code.

See Global tax model for more information about this element.
DepositThe deposit made towards this invoice.

(*) required field

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
 
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Item API Reference. 
MATCHING CRITERIA
Name*
Maximum of 100 chars		Equal to the Item unique name.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Item creation.
Additional fields: Active, SKU, Unit Price, TrackQtyOnHand, QtyOnHand, AssetAccountRef, InvStartDate, ExpenseAccountRef.
IncomeAccountRef*Reference to the posting account, that is, the account that records the proceeds from the sale of this item. Must be an account with account type of Sales of Product Income.

Account ID*: The ID for the referenced Income Account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Type*Classification that specifies the use of this item:
Inventory - Service - Non inventory

See the description at the top of the Item entity page for details about supported item types.
ADDITIONAL FIELDS
ActiveTrue – False
Inactivating an item is achieved by setting the Active attribute to false.
SKUThe stock keeping unit (SKU) for this Item. This is a company-defined identifier for an item or product used in tracking inventory.

maximum of 100 chars.
minorVersion: 4
Unit PricePrice of the item.
TrackQtyOnHandTrue - False
QtyOnHandCurrent quantity of the Inventory items available for sale.
Not used for Service or NonInventory type items.Required for Inventory type items.
AssetAccountRefReference to the Inventory Asset account that tracks the current value of the inventory. If the same account is used for all inventory items, the current balance of this account will represent the current total value of the inventory. Must be an account with account type of Other Current Asset.

Use Account.Id and Account.Name from that object for AssetAccountRef.value and AssetAccountRef.name, respectively. Required for Inventory item types.

Account ID*: The ID for the referenced asset account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
InvStartDateDate of opening balance for the inventory transaction. Required when creating an Item.Type=Inventory. Required for Inventory item types.

Local timezone: YYYY-MM-DD UTC: YYYY-MM-DDZ Specific time zone: YYYY-MM-DD+/-HH:MM
The date format follows the XML Schema standard.
ExpenseAccountRefReference to the expense account used to pay the vendor for this item. Must be an account with account type of Cost of Goods Sold.

Account ID*: The ID for the referenced expense account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

(*) required field

Upsert Journal Entry Copy Link

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
 
Journal Entry is a transaction in which: 
▪️ There are at least one pair of lines, a debit and a credit, called distribution lines. 
▪️ Each distribution line has an account from the Chart of Accounts. Query the Account resource for a listing of the Chart of Accounts. 
▪️ The total of the debit column equals the total of the credit column. 
 
When you record a transaction with a JournalEntry object, the QuickBooks Online UI labels the transaction as JRNL in the register and as General Journal on reports that list transactions. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Journal Entry API reference. 
MATCHING CRITERIA
DocNumber*Equal to the Journal Entry DocNumber.
MAP FIELDS
Line*
Individual line items of a transaction.
There must be at least one pair of Journal Entry Line elements, representing a debit and a credit, called distribution lines.
Set Line Detail Type to Journal Entry Line for both lines.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Journal Entry Line can be added as elements.

Element 1: Represents the first Journal Entry Line.

Detail Type*: Set to Journal Entry Line Detail.

Amount*: The amount of the line item.

Journal Entry Line Detail*:
_ Posting Type*: Indicates whether this Journal Entry line is a Debit or Credit.

_ Account Reference*: Reference to the account associated with this line.
___ Value*: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
⚠️ If this account has same location as specified in the transaction by the TransactionLocationType attribute and the same VAT as in the line item TaxCodeRef attribute, then this account is used.
⚠️ If there is a mismatch, then the account from the account category list that matches the transaction location and VAT is used.
⚠️ If this account is not present in the account category list, then a new account is created with the new location, new VAT code, and all other attributes as in the default account.


Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.

(*) required field

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
  
When creating a bill, only certain transaction types can be linked. The most commonly supported transaction types include: 
▪️ BillPaymentCheck – A payment made by check to pay the bill. 
▪️ BillPaymentCreditCard – A payment made by credit card to pay the bill. 
▪️ CreditMemo – A credit memo applied to the bill. 
▪️ JournalEntry – A journal entry affecting the bill. 
 
Transactions like Invoice and Deposit are not typically linked to a bill because a bill represents an expense or liability, while invoices are accounts receivable (money owed to you, not by you). Deposits usually relate to received funds, not expenses. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Bill API reference. 
MATCHING CRITERIA
DocNumber*Equal to the Bill DocNumber.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Bill upsert.
Additional fields: Currency Reference, Ap Account Reference, Sales Term Reference, Linked Transaction.
Vendors Reference*Reference to the vendor for this transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*: Possible choices for each line:
Account Based Expense Line Detail – Item based Expense Line Detail

Amount*: The amount of the line item.

The [+ Add Field] button allows to add fields corresponding to Detail Type.

Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.

Account Based Expense Line Detail:

_ Account Reference: Reference to the Expense account associated with this item.
___ Account ID: The ID for the referenced account.
___ Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
⚠️ If this account has same location as specified in the transaction by the TransactionLocationType attribute and the same VAT as in the line item TaxCodeRef attribute, then this account is used.
⚠️ If there is a mismatch, then the account from the account category list that matches the transaction location and VAT is used.
⚠️ If this account is not present in the account category list, then a new account is created with the new location, new VAT code, and all other attributes as in the default account.

Item based Expense Line Detail:
_ Quantity: Number of items for the line.
_ Unit Price: Unit price of the subject item.

_ Item Reference: : Reference to the Item.
___ Value: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference: Reference to a customer or job. 
___ Value: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
ADDITIONAL FIELDS
Currency ReferenceReference to the currency in which all amounts on the associated transaction are expressed. This must be defined if multi-currency is enabled for the company. Read more about multi-currency support here.

[+ Add Field] add more fields:
Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency.
Ap Account ReferenceSpecifies to which AP account the bill is credited. 

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

⚠️ The specified account must have Account.Classification set to Liability and Account.AccountSubType set to AccountsPayable. If the company has a single AP account, the account is implied. However, it is recommended that the AP Account be explicitly specified in all cases to prevent unexpected errors when relating transactions to each other.
Sales Term ReferenceReference to the Term associated with the transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced sales term.
Name: Name derived from the field that holds the common name of that sales term.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Linked TransactionZero or more transactions linked to this Bill object.

[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Linked Transaction can be added as elements.

Element 1: Represents the first Linked Transaction.

Transaction ID: Unique identifier of the related transaction.
Transaction Type: Possible values:
BillPaymentCheck – A payment made by check to pay the bill.
BillPaymentCreditCard – A payment made by credit card to pay the bill.
CreditMemo – A credit memo applied to the bill.
JournalEntry – A journal entry affecting the bill.

(*) required field

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
 
A Sales Receipt object represents a receipt issued to a customer upon payment for goods or services. It functions similarly to an invoice, but payment is received concurrently with the sale. 
The receipt specifies a deposit account for the received funds. If no deposit account is designated, the payment is directed to the Undeposited Account. 
 
▪️ A SalesReceipt object must have at least one line that describes an item and an amount. 
 
Tip: For Any Reference fields like Customer Reference, Account Reference or Vendor Reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Sales Receipt API reference.
MATCHING CRITERIA
DocNumber*Equal to the Sale Receipt DocNumber.
MAP FIELDS
Line*
The minimum line item required for the request is Sales Item Line or Group Line.		[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type* Possible values for each line:
Sales Item Line Detail
Group Line Detail
Description Line Detail
Discount Line Detail
Subtotal Line Detail

Amount*: The amount of the line item.

Sale Item Line Detail*:
_ Item Reference*: : Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Unit Price: Unit price of the subject item as referenced by ItemRef.

_ Quantity: Number of items for the line.

_ Tax Code Reference: Reference to the TaxCode for this item. 
[+ Add Field] add more fields:
___ Value: The ID for the referenced Tax Code.

[+ Add Field] add more fields:
Description: Free form text description of the line item that appears in the printed record.
Max 4000 chars.

(*) required field

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
 
The Purchase Order object is a non-posting transaction representing a request to purchase goods or services from a third party.

Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference.

See Quickbooks Purchase Order API reference.
MATCHING CRITERIA
DocNumber*Equal to the Purchase Order DocNumber.
MAP FIELDS
Line*[⊕ Element][⊕ Map] Add fields or Map it from a Data Source. See Field Mapping.
Additional Line can be added as elements.

Element 1: Represents the first Line.

Detail Type*
Value: Item based Expense Line Detail, Account Based Expense Line Detail.


Amount*: amount, price of the line.

Item Based Expense Line Detail*
_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.
___ Name: Name derived from the field that holds the common name of that item.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Customer Reference*: Reference to a customer or job.
___ Value*: The ID for the referenced customer.
___ Name: Name derived from the field that holds the common name of that customer.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

_ Quantity*: Number of items.

_ Item Reference*: Reference to the Item.
___ Value*: The ID for the referenced item.

_ Billable Status: The billable status of the expense. This field is not updatable through an API request. The value automatically changes when an invoice is created.
Possible values: Billable, Not Billable, Has Been Billed

_ Unit Price: Unit price of the subject item as referenced by ItemRef.
Corresponds to the Rate column on the QuickBooks Online UI to specify either unit price, a discount, or a tax rate for item. If used for unit price, the monetary value of the service or product, as expressed in the home currency. If used for a discount or tax rate, express the percentage as a fraction. For example, specify 0.4 for 40% tax.
AP Account Reference*This field indicates the Accounts Payable (AP) account used to record the bill.

While many small businesses may only have one AP account, it’s crucial to always explicitly specify the account.
This ensures accurate record-keeping, especially for businesses with multiple AP accounts.
The specified account must be a Liability account specifically designated for Payables.
Failing to explicitly specify the AP account can lead to unexpected errors when linking transactions within your accounting system.

[+ Add Field] add more fields:
Value: The ID for the referenced account.
Name: Name derived from the field that holds the common name of that account.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.
Vendor Reference*Reference to the vendor for this transaction.

[+ Add Field] add more fields:
Value: The ID for the referenced vendor.
Name: Name derived from the field that holds the common name of that vendor.
For example, when referencing a Customer object, the field used is ‘Customer.DisplayName‘.

(*) required field

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
 
Customer Relationships: Customer relationships can be complex. Some customers may have a hierarchical structure. For example: 
▪️ A team is the main customer, and its individual members are sub-customers. 
▪️ A property management company is the main customer, and the properties they manage are sub-customers. 
 
Tracking Work: You can use the system to track specific tasks or projects associated with a customer. For instance: 
▪️ A homeowner is the customer, and their kitchen remodel is the project with individual tasks. 
▪️ A car owner is the customer, and their car repairs are the projects with individual tasks. 
  
⚠️ The Display Name attribute or at least one of Title, Given Name, Middle Name, Family Name, or Suffix attributes is required during customer creation. 
  
Tip: For Any Reference fields like Customer reference, Account reference or Vendor reference, etc…, get the Value ID and Name by using Wiresk Method “List” or Trigger “Get Records by Search String” to determine the appropriate object for this reference. 
 
See Quickbooks Customer  API reference. 
MATCHING CRITERIA
Display Name*Equal to Customer unique display name.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Customer upsert.
Additional fields: Primary Email Address, Suffix, Title, Middle Name, Notes, Primary Phone, Company Name, Bill Address, Given Name.
Family Name*Family name or the last name of the person.
Display Name*The Display Name is how the person or organization is identified within the system. It must be unique within the system (across Customers, Vendors, and Employees). This field cannot be removed using sparse updates.

If not provided, the system will create one for you by combining the customer’s name components (like title, first name, last name).
ADDITIONAL FIELDS
Primary Email AddressPrimary email address.

[+ Add Field] add more fields.
Address: An email address, the format must follow the RFC 822 standard.
SuffixSuffix of the name. For example, Jr. 
TitleTitle of the person.

This tag supports i18n (localized translations of titles such as “Mr.,” “Ms.,” “Dr.,” “Prof.,” or job-related titles like “CEO” and “Manager” in different languages and cultures).
Middle NameMiddle name of the person. The person can have zero or more middle names.
Notes
Max 2000 chars.		Free form text describing the Customer.
Primary Phone
Max 30 chars.		Primary phone number.

[+ Add Field] add more fields.
Free for Number.
Company NameThe name of the company associated with the person or organization.
Bill AddressDefault billing address.

When a physical address is updated within a transaction object, the QuickBooks Online API organizes the address components differently in the transaction response compared to when it was initially created:
The Line1 and Line2 fields are now filled with the customer name and company name.
The original Line1 to Line5, along with City, SubDivisionCode (State/Province), and PostalCode, are shifted into Line3 through Line5 as free-form text.

[+ Add Field] add more fields.
Country Sub Division Code
City
Postal Code
line1
Country
Given NameGiven name or first name of a person.

(*) required field

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
 
⚠️ The Display Name attribute or at least one of Title, Given Name, Middle Name, Family Name, or Suffix attributes is required during customer creation.
 
See Quickbooks Vendor  API reference.
MATCHING CRITERIA
Display Name*Equal to the Vendor unique display name.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Vendor upsert.
Additional fields: Print on Check Name, Primary Email Address, Suffix, Title, Tax Identifier, Account Number, Primary Phone, Web Address, Mobile, Company Name, Bill Address, Given Name.
Family Name*Family name or the last name of the person.
Display NameThe Display Name is how the person or organization is identified within the system. It must be unique within the system (across Customers, Vendors, and Employees). This field cannot be removed using sparse updates.

If not provided, the system will create one for you by combining the customer’s name components (like title, first name, last name).
ADDITIONAL FIELDS
Print on Check NameThis field displays the name of the person or organization as it should appear on a printed check.
If you don’t provide this name, it will be automatically filled in using the DisplayName.
Primary Email AddressPrimary email address.

[+ Add Field] add more fields.
Address: Email address, the format must follow the RFC 822 standard.
SuffixSuffix of the name. For example, Jr. 
TitleTitle of the person.

This tag supports i18n (localized translations of titles such as “Mr.,” “Ms.,” “Dr.,” “Prof.,” or job-related titles like “CEO” and “Manager” in different languages and cultures).
Tax Identifier
Max 20 chars.		The tax ID of the Person or Organization.

The value is masked in responses, exposing only last four characters. For example, the ID of 123-45-6789 is returned as XXXXXXX6789.
Account Number
Max 100 chars.		Name or number of the account associated with this vendor.
Primary PhonePrimary phone number.

[+ Add Field] add more fields.
Free for Number.
Max 30 chars.
Web Address
Maximum 1000 chars.		[+ Add Field] add more fields.
URI: Uniform Resource Identifier for the web site.
Mobile
Maximum of 30 chars.		Mobile phone number.

[+ Add Field] add more fields.
Free for Number: Specifies the telephone number in free form.
Company NameThe name of the company associated with the person or organization.
Bill AddressDefault billing address.

When a physical address is updated within a transaction object, the QuickBooks Online API organizes the address components differently in the transaction response compared to when it was initially created:
The Line1 and Line2 fields are now filled with the customer name and company name.
The original Line1 to Line5, along with City, SubDivisionCode (State/Province), and PostalCode, are shifted into Line3 through Line5 as free-form text.

[+ Add Field] add more fields.
Country Sub Division Code
City
Postal Code
line1
Country
Given NameGiven name or first name of a person.

(*) required field

The Method will search for existing records. If a match is found, the record is updated; otherwise, a new record is created using the supplied information. 
 
Accounts are the building blocks of your financial records. They track all your business’s financial activity:
▪️ Money coming in: Income and revenue.
▪️ Money going out: Expenses.
▪️ The value of your assets: Things your business owns like vehicles and equipment.
There are five main types of accounts: assets, liabilities, income, expenses, and equity.
All your business’s accounts are listed in your Chart of Accounts, which is a unique list created for your specific business. Accountants often refer to these accounts as “ledgers.”
The “account object” is the tool you’ll use within the QuickBooks system to manage and work with your accounts.
 
See Quickbooks Account  API reference.
MATCHING CRITERIA
Name*
max 100 characters.		Equal to the Account unique name.
MAP FIELDS [+ Add Field] Select fields from list, to configure the Account upsert.
Additional fields: Currency reference, Meta Data, Current Balance, Active, Sub Account.
Account Sub Type*The account sub-type classification and is based on the AccountType value.
Required if AccountType is not specified.

See possible values in the Account type and Account Sub Type List below.
Account Type*A detailed account classification that specifies the use of this account. The type is based on the Classification.
Required if AccountSubType is not specified.

See possible values in the Account type and Account Sub Type List below.
ADDITIONAL FIELDS
Currency referenceReference to the currency in which this account holds amounts.

[+ Add Field] add more fields:
Value: A three letter string representing the ISO 4217 code for the currency. For example, USD, AUD, EUR.
Name: The full name of the currency
Meta DataDescriptive information about the entity. The MetaData values are set by Data Services and are read only for all applications.

[+ Add Field] add more fields.
Create Time: Time the entity was created in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM

Last Update Time: Time the entity was last updated in the source domain.
Local time zone: YYYY-MM-DDTHH:MM:SS UTC: YYYY-MM-DDT HH :MM: SSZ Specific time zone: YYYY-MM-DDT HH :MM:SS +/- HH :MM
Current BalanceSpecifies the balance amount for the current Account. Valid for Balance Sheet accounts.
ActiveTrue – False

Inactive accounts can be hidden from most views and may not be used for new transactions.

(*) required field

Account Type and Account Sub Type List

ASSET ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
BankDefault
CashOnHand (default), Checking, MoneyMarket, RentsHeldInTrust, Savings, TrustAccounts, CashAndCashEquivalents, OtherEarMarkedBankAccounts
Other Current AssetDefault
AllowanceForBadDebts, DevelopmentCosts, EmployeeCashAdvances (default), OtherCurrentAssets, Inventory, Investment_MortgageRealEstateLoans, Investment_Other, Investment_TaxExemptSecurities, Investment_USGovernmentObligations, LoansToOfficers, LoansToOthers, LoansToStockholders, PrepaidExpenses, Retainage, UndepositedFunds, AssetsAvailableForSale, BalWithGovtAuthorities, CalledUpShareCapitalNotPaid, ExpenditureAuthorisationsAndLettersOfCredit, GlobalTaxDeferred, GlobalTaxRefund, InternalTransfers, OtherConsumables, ProvisionsCurrentAssets, ShortTermInvestmentsInRelatedParties, ShortTermLoansAndAdvancesToRelatedParties, TradeAndOtherReceivables
Fixed AssetDefault
AccumulatedDepletion, AccumulatedDepreciation, DepletableAssets, FixedAssetComputers, FixedAssetCopiers, FixedAssetFurniture, FixedAssetPhone, FixedAssetPhotoVideo, FixedAssetSoftware, FixedAssetOtherToolsEquipment, FurnitureAndFixtures (default), Land, LeaseholdImprovements, OtherFixedAssets, AccumulatedAmortization, Buildings, IntangibleAssets, MachineryAndEquipment, Vehicles, AssetsInCourseOfConstruction, CapitalWip, CumulativeDepreciationOnIntangibleAssets, IntangibleAssetsUnderDevelopment, LandAsset, NonCurrentAssets, ParticipatingInterests, ProvisionsFixedAssets
Other AssetDefault
LeaseBuyout, OtherLongTermAssets, SecurityDeposits, AccumulatedAmortizationOfOtherAssets, Goodwill, Licenses (default), OrganizationalCosts, AssetsHeldForSale, AvailableForSaleFinancialAssets, DeferredTax, Investments, LongTermInvestments, LongTermLoansAndAdvancesToRelatedParties, OtherIntangibleAssets, OtherLongTermInvestments, OtherLongTermLoansAndAdvances, PrepaymentsAndAccruedIncome, ProvisionsNonCurrentAssets
Accounts ReceivableDefault
Accounts Receivable

EQUITY ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
EquityDefault
OpeningBalanceEquity (default), PartnersEquity, RetainedEarnings, AccumulatedAdjustment, OwnersEquity, PaidInCapitalOrSurplus, PartnerContributions, PartnerDistributions, PreferredStock, CommonStock, TreasuryStock, EstimatedTaxes, Healthcare, PersonalIncome, PersonalExpense, AccumulatedOtherComprehensiveIncome, CalledUpShareCapital, CapitalReserves, DividendDisbursed, EquityInEarningsOfSubsidiaries, InvestmentGrants, MoneyReceivedAgainstShareWarrants, OtherFreeReserves, ShareApplicationMoneyPendingAllotment, ShareCapital, Funds

EXPENSE ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
ExpenseDefault
AdvertisingPromotional, BadDebts, BankCharges, CharitableContributions, CommissionsAndFees, Entertainment, EntertainmentMeals, EquipmentRental, FinanceCosts, GlobalTaxExpense, Insurance, InterestPaid, LegalProfessionalFees, OfficeExpenses, OfficeGeneralAdministrativeExpenses, OtherBusinessExpenses, OtherMiscellaneousServiceCost, PromotionalMeals, RentOrLeaseOfBuildings, RepairMaintenance, ShippingFreightDelivery, SuppliesMaterials, Travel (default), TravelMeals, Utilities, Auto, CostOfLabor, DuesSubscriptions, PayrollExpenses, TaxesPaid, UnappliedCashBillPaymentExpense, Utilities, AmortizationExpense, AppropriationsToDepreciation, BorrowingCost, CommissionsAndFees, DistributionCosts, ExternalServices, ExtraordinaryCharges, IncomeTaxExpense, LossOnDiscontinuedOperationsNetOfTax, ManagementCompensation, OtherCurrentOperatingCharges, OtherExternalServices, OtherRentalCosts, OtherSellingExpenses, ProjectStudiesSurveysAssessments, PurchasesRebates, ShippingAndDeliveryExpense, StaffCosts, Sundry, TravelExpensesGeneralAndAdminExpenses, TravelExpensesSellingExpense
Other ExpenseDefault
Depreciation (default), ExchangeGainOrLoss, OtherMiscellaneousExpense, PenaltiesSettlements, Amortization, GasAndFuel, HomeOffice, HomeOwnerRentalInsurance, OtherHomeOfficeExpenses, MortgageInterest, RentAndLease, RepairsAndMaintenance, ParkingAndTolls, Vehicle, VehicleInsurance, VehicleLease, VehicleLoanInterest, VehicleLoan, VehicleRegistration, VehicleRepairs, OtherVehicleExpenses, Utilities, WashAndRoadServices, DeferredTaxExpense, Depletion, ExceptionalItems, ExtraordinaryItems, IncomeTaxOtherExpense, MatCredit, PriorPeriodItems, TaxRoundoffGainOrLoss
Cost of Goods SoldDefault
EquipmentRentalCos, OtherCostsOfServiceCos, ShippingFreightDeliveryCos, SuppliesMaterialsCogs, CostOfLaborCos (default), CostOfSales, FreightAndDeliveryCost

LIABILITY ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
Accounts PayableDefault
Accounts Payable, OutstandingDuesMicroSmallEnterprise, OutstandingDuesOtherThanMicroSmallEnterprise
Credit CardDefault
Credit Card
Long Term LiabilityDefault
NotesPayable (default), OtherLongTermLiabilities, ShareholderNotesPayable, AccrualsAndDeferredIncome, AccruedLongTermLiabilities, AccruedVacationPayable, BankLoans, DebtsRelatedToParticipatingInterests, DeferredTaxLiabilities, GovernmentAndOtherPublicAuthorities, GroupAndAssociates, LiabilitiesRelatedToAssetsHeldForSale, LongTermBorrowings, LongTermDebit, LongTermEmployeeBenefitObligations, ObligationsUnderFinanceLeases, OtherLongTermProvisions, ProvisionForLiabilities, ProvisionsNonCurrentLiabilities, StaffAndRelatedLongTermLiabilityAccounts
Other Current LiabilityDefault
DirectDepositPayable, LineOfCredit, LoanPayable, GlobalTaxPayable, GlobalTaxSuspense, OtherCurrentLiabilities (default), PayrollClearing, PayrollTaxPayable, PrepaidExpensesPayable, RentsInTrustLiability, TrustAccountsLiabilities, FederalIncomeTaxPayable, InsurancePayable, SalesTaxPayable, StateLocalIncomeTaxPayable, AccruedLiabilities, CurrentLiabilities, CurrentPortionEmployeeBenefitsObligations, CurrentPortionOfObligationsUnderFinanceLeases, CurrentTaxLiability, DividendsPayable, DutiesAndTaxes, InterestPayables, ProvisionForWarrantyObligations, ProvisionsCurrentLiabilities, ShortTermBorrowings, SocialSecurityAgencies, StaffAndRelatedLiabilityAccounts, SundryDebtorsAndCreditors, TradeAndOtherPayables

REVENUE ACCOUNTS

ACCOUNT TYPEACCOUNT SUB TYPE
IncomeDefault
NonProfitIncome, OtherPrimaryIncome (default), SalesOfProductIncome, ServiceFeeIncome, DiscountsRefundsGiven, UnappliedCashPaymentIncome, CashReceiptIncome, OperatingGrants, OtherCurrentOperatingIncome, OwnWorkCapitalized, RevenueGeneral, SalesRetail, SalesWholesale, SavingsByTaxScheme
Other IncomeDefault
DividendIncome, InterestEarned, OtherInvestmentIncome (default), OtherMiscellaneousIncome, TaxExemptInterest, GainLossOnSaleOfFixedAssets, GainLossOnSaleOfInvestments, LossOnDisposalOfAssets, OtherOperatingIncome, UnrealisedLossOnSecuritiesNetOfTax

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.