This article walks you through installing the QuickBooks Online integration on iPaaS.com. You will prepare your QuickBooks company, subscribe, fill in the settings, authorize QuickBooks, set collision handling, turn on the polls and check that everything works.

Plan about an hour for setup, plus time to check your first test transactions.

Before You Begin

What you need

Item	Needed for	Notes
A QuickBooks Online company, US edition	Everything	Inventory quantities need QuickBooks inventory tracking: included in Plus and Advanced, an add-on for Simple Start and Essentials (Intuit). Other editions work for customers, items, sales receipts, invoices and payments.
A QuickBooks admin user	Authorizing the subscription	You sign in to Intuit as this user when you click Authenticate. A user without enough rights causes `QBOL-AUTZ-1001` later, and so does a Company ID that names a different company than the one you connected.
Your QuickBooks company id	The Company ID setting	QuickBooks shows it when you press Ctrl+Alt+? (Ctrl+Option+? on a Mac) on any QuickBooks Online screen. You can paste it as shown: spaces and dashes are ignored.
Your company's sales tax mode	Sales receipts and invoices FROM iPaaS.com	Manual or automated sales tax. On manual sales tax, you need the name of the tax code (or tax group) to put in Sales Tax Code. On automated sales tax, you leave Sales Tax Code blank.
Your chart of accounts names	Items created FROM iPaaS.com	New items need an income account. New Inventory items also need an expense (cost of goods sold) and an inventory asset account. The defaults are QuickBooks' standard account names.
The iPaaS.com location your stock belongs to	Inventory TO iPaaS.com only	You need its id for Inventory Location.
The list of payment methods your orders and QuickBooks use	Sales receipts and payments	Each one needs a row in the payment-method translations (see Default Mapping Collections).
A separate QuickBooks Online company for testing (recommended)	Trying the integration safely	For example a QuickBooks Online trial company, so test sales never reach your live books. See Post-Installation Verification.

The integration never emails your customers. A sales receipt, invoice or payment it creates is never sent to the customer by the integration.

Signing in to QuickBooks

QuickBooks Online only lets an app sign in through Intuit's OAuth 2.0 consent page. The integration signs in with iPaaS.com's own Intuit app, the same app for every subscriber. iPaaS.com maintains the app and its keys on the integration; they are never part of your subscription. You do not create an Intuit Developer app or copy any keys: you subscribe, fill in the settings, click Authenticate and sign in to Intuit as a QuickBooks admin.

Installation Instructions for Integration Setup

In iPaaS.com, go to Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the QuickBooks Online integration tile.
Click Subscribe.
Enter a name for the subscription. It must be unique within the company.
- Format: QuickBooks Online - [Environment/Purpose]
- Example: QuickBooks Online - Production
Select Create Default Mappings (recommended). This applies the default templates listed under Default Mapping Collections below. If you clear it, the subscription starts with no mapping collections or translations, and you build them yourself.
- The other settings start blank on this page. The defaults named in the steps below are filled in when you save the subscription.
Leave the API Url at quickbooks.api.intuit.com.
- This is the address for every QuickBooks Online company, including a trial company you use for testing.
- The sandbox address (sandbox-quickbooks.api.intuit.com) is for iPaaS.com's own testing. Intuit does not let iPaaS.com's live app connect to a sandbox company.
Fill Company ID with your QuickBooks company id. This is required: iPaaS.com does not pass the company id to the integration when you authorize. QuickBooks shows it when you press Ctrl+Alt+? (Ctrl+Option+? on a Mac) on any QuickBooks Online screen. Spaces and dashes are ignored, so you can paste it as QuickBooks shows it (for example 1234 5678 9012 3456); only the digits are kept. A value that is not a number (a company name, for example) fails with QBOL-VALD-1016.
Set Sales Tax Code.
- Manual sales tax: enter the name or id of the tax code or tax group the transactions should use, for example the one named for your state. Without it, a transaction that carries tax fails with QBOL-VALD-1014.
- Automated sales tax: leave Sales Tax Code blank, and do not map Tax Code on the transaction collections. On a company that uses QuickBooks automated sales tax, both are ignored (not sent to QuickBooks): the transaction's tax amount is kept, and QuickBooks assigns it to its own tax jurisdictions. Make sure a tax agency is set up in QuickBooks for every state you collect tax in.
Set Shipping Item.
- Default value: Shipping
- Used only when QuickBooks' own shipping field is turned off for sales forms. The shipping amount then goes on a line for this item.
Set Deposit Account (optional). This is where sales receipts and invoice payments are deposited. Leave it blank to use QuickBooks' default, Undeposited Funds.
Set Default Item Type.
- Default value: NonInventory
- The other value is Service. New items get this type unless the mapping sets one. Inventory items are created only when the mapping sets the type to Inventory.
Set Create Missing Items.
- Default value: true
- When a transaction line names an item QuickBooks does not have, the integration creates it. Set false to fail the transaction with QBOL-NFND-1006 instead.
Check the three account settings against your chart of accounts. Each takes an account name or id.
- Income Account: default Sales of Product Income. Every new item.
- Expense Account: default Cost of Goods Sold. New Inventory items.
- Inventory Asset Account: default Inventory Asset. New Inventory items.
Enter the Inventory Location (only if you bring inventory TO iPaaS.com). This is the id of the iPaaS.com location the quantities belong to (QuickBooks has no inventory locations). The default template maps it as each quantity's location and marks it required, so fill it before you turn inventory on. Left blank, every quantity TO iPaaS.com fails with NFND-1003 - Location Id: 0 does not exist or can not be found.
Leave Minor Version (75), Customer Page Size, Item Page Size, Invoice Page Size and Payment Method Page Size (100 each) at their defaults.
Set Initial Poll Days before the first poll if you want more history.
- Default value: 7
- The first poll of each kind of record brings in what changed in this many days.
Click Apply to save the settings.

See QuickBooks Online Connections and Settings for every setting in detail.

Authentication Configuration

QuickBooks Online uses OAuth 2.0. You sign in once with Authenticate; the subscription then keeps itself signed in.

The subscription can't call QuickBooks until you authorize it and fill Company ID (step 7 above).

On the subscription, click the Authenticate (lock) icon.
Intuit's sign-in page opens. Sign in as a QuickBooks admin user.
Choose the QuickBooks company to connect: the same company whose id is in Company ID.
Click Connect.
iPaaS.com shows an authorization-complete page. Close it.
Open the subscription's Persistent Data. It now shows Access Token and Refresh Token.

If Company ID is still blank, fill it now with your company id (in QuickBooks Online press Ctrl+Alt+?, or Ctrl+Option+? on a Mac, and copy the Company ID; spaces and dashes are ignored) and click Apply. iPaaS.com does not pass the company id to the integration when you authorize.

If you see	Why	What to do
`QBOL-AUTH-1001`	The integration's Intuit app keys are missing. They are iPaaS.com's, kept on the integration.	Contact your MiSP or iPaaS.com support. Nothing on the subscription needs changing.
`QBOL-AUTH-1008`	Intuit refused the authorization code.	Click Authenticate again. If it keeps failing, contact your MiSP or iPaaS.com support.
`QBOL-AUTH-1009`	Access was not granted on Intuit's page.	Click Authenticate again and choose Connect.

Each subscription connects one QuickBooks company.

Important Notes

The access token lasts an hour. The integration refreshes it with the refresh token when it lapses, or when QuickBooks refuses it.
Intuit replaces the refresh token from time to time. The integration saves the new one every time, on the subscription's Persistent Data.
A refresh token that goes unused for 100 days expires (Intuit: Authorization FAQ). If the integration is idle that long, or someone disconnects the app in QuickBooks, transfers fail (the log shows QBOL-AUTH-1003; see below). Click Authenticate again.
Do not edit Access Token or Refresh Token in Persistent Data. If they are removed, transfers fail (QBOL-AUTH-1002 in the log) until you authorize again.
The Intuit app's keys are iPaaS.com's, kept on the integration and never on the subscription. If Intuit rejects them, transfers fail (QBOL-AUTH-1005 in the log): contact your MiSP or iPaaS.com support. Nothing on the subscription needs changing.

When transfers fail with "Unable to connect to subscription"

When the integration cannot connect to QuickBooks, the transfer error in iPaaS.com reads only "Unable to process transfer. Reason: Unable to connect to subscription with id ...". The integration's own coded reason is not shown in that error. To find it, open Activity Tracker and look for the entries at the same time as the error, with the same reference id: they carry the QBOL-AUTH code.

Code in the log	What to do
`QBOL-AUTH-1004`	Fill Company ID (in QuickBooks Online press Ctrl+Alt+?, or Ctrl+Option+? on a Mac, and copy the Company ID; spaces and dashes are ignored) and click Apply.
`QBOL-VALD-1016`	Company ID is not a number. Enter the QuickBooks company id from the same Ctrl+Alt+? screen (spaces and dashes are ignored) and click Apply.
`QBOL-AUTH-1002` or `QBOL-AUTH-1003`	Click Authenticate and connect the QuickBooks company again.
`QBOL-AUTH-1001` or `QBOL-AUTH-1005`	Contact your MiSP or iPaaS.com support. Nothing on the subscription needs changing.
`QBOL-AUTH-1006`	Usually temporary. If it keeps happening, contact your MiSP or iPaaS.com support.

Then send the records that failed again.

Operational Configuration

Default Mapping Collections

A new subscription gets these collections and translations from the default templates.

Collection	Child collections	Type	Direction	Records it takes (default filter)
Add/Update QuickBooks Online Customer TO iPaaS.com	Add/Update QuickBooks Online Customer Address TO iPaaS.com	Customer	TO iPaaS.com	Active QuickBooks customers
Add/Update QuickBooks Online Customer FROM iPaaS.com	Add/Update QuickBooks Online Customer Address FROM iPaaS.com	Customer	FROM iPaaS.com	Customers with an email or a company name
Add/Update QuickBooks Online Item TO iPaaS.com	Add/Update QuickBooks Online Item Inventory TO iPaaS.com	Product, with quantity on hand	TO iPaaS.com	Items with a SKU (inactive ones arrive as Disabled)
Update QuickBooks Online Item Inventory TO iPaaS.com	None	Product Inventory	TO iPaaS.com	Every Inventory item
Add/Update QuickBooks Online Item FROM iPaaS.com	None	Product	FROM iPaaS.com	Products with a SKU
Add QuickBooks Online Sales Receipt FROM iPaaS.com	Add QuickBooks Online Sales Receipt Line FROM iPaaS.com; Add QuickBooks Online Sales Receipt Address FROM iPaaS.com; Add QuickBooks Online Sales Receipt Payment FROM iPaaS.com	Transaction	FROM iPaaS.com	Orders paid in full by captured (Completed) payments, not cancelled or draft; posted sales receipts and fully paid invoices are left as they are
Add/Update QuickBooks Online Invoice FROM iPaaS.com	Add/Update QuickBooks Online Invoice Line FROM iPaaS.com; Add/Update QuickBooks Online Invoice Address FROM iPaaS.com; Add QuickBooks Online Payment FROM iPaaS.com	Transaction	FROM iPaaS.com	Invoices, orders sold on terms (no payment) and part-paid orders, not cancelled or draft; fully paid invoices are left as they are
Update QuickBooks Online Invoice TO iPaaS.com	Add QuickBooks Online Payment TO iPaaS.com	Transaction	TO iPaaS.com	Every invoice; only invoices already linked to an iPaaS.com transaction are updated
Add/Update QuickBooks Online Payment Method TO iPaaS.com	None	Payment Method	TO iPaaS.com	Active payment methods
Add QuickBooks Online Payment Method FROM iPaaS.com	None	Payment Method	FROM iPaaS.com	Every payment method with a name

Translations:

QuickBooks Online Payment Method FROM iPaaS.com: iPaaS.com payment method → QuickBooks name (VISA → Visa, MASTERCARD → MasterCard, AMEX → American Express, DISCOVER → Discover, CASH → Cash, CHECK → Check, CreditCard-Visa → Visa, CRCARD → Visa). The rows CreditCard-Visa → Visa and CRCARD → Visa are examples of card codes a source system may send: replace them with the codes your own systems send, or delete them if yours never do. Add a row for every method your orders use: an untranslated method fails with QBOL-NFND-1007 instead of posting without one.
QuickBooks Online Payment Method TO iPaaS.com: QuickBooks name → iPaaS.com method (the reverse), plus None → Other for a payment entered in QuickBooks without a method. Add a row for every method your QuickBooks company uses: iPaaS.com refuses a payment without a method, and then the whole invoice update.
QuickBooks Online Invoice Status TO iPaaS.com: Paid → Complete; PartiallyPaid, Open and Overdue → Awaiting Payment; Voided → Cancelled (an invoice voided in QuickBooks); Credited → Complete (an invoice settled by credit memos with no payment; map it to Cancelled if you treat a full credit as a cancellation).
QuickBooks Online Payment Method Type FROM iPaaS.com: Credit Card → CREDIT_CARD; any other type becomes NON_CREDIT_CARD.
QuickBooks Online Item Type TO iPaaS.com: Inventory → Physical, NonInventory → Non-Inventory Items, Service → Service Items.
QuickBooks Online Item Type FROM iPaaS.com: Physical → NonInventory, Non-Inventory Items → NonInventory, Service Items → Service, Virtual → Service. Physical products become NonInventory on purpose: a QuickBooks Inventory item needs accounts and a start quantity, so map Inventory deliberately.

Collision Handling

Set collision handling after the subscription is created. Templates do not carry it, so set it on each collection below. When a create finds a record QuickBooks already has, Remap and Link and Update and Link both link that record, and iPaaS.com then updates it with the mapped data. Error (the setting when none is chosen) fails the transfer with a message that names the existing record.

To set it: open the subscription's Manage Mappings, click Edit on the collection, choose the Collision Handling Method, and click Apply. Collision handling is set on the parent collection only; child collections (addresses, lines, payments) follow their parent. If you can't find the setting, contact your MiSP or iPaaS.com support.

Customer FROM iPaaS.com (collection Add/Update QuickBooks Online Customer FROM iPaaS.com): set collision handling to Remap and Link. A new customer is first matched to a QuickBooks customer with the same email (by display name only when there is no email). Linking keeps one QuickBooks customer per person, including a customer a transaction created earlier. With Error, the transfer fails with QBOL-BIZL-1001. When two or more QuickBooks customers share the email, nothing is linked under any setting: the transfer fails with QBOL-BIZL-1002.
Item FROM iPaaS.com (collection Add/Update QuickBooks Online Item FROM iPaaS.com): set collision handling to Remap and Link. A new product is matched to a QuickBooks item by SKU, then by name. QuickBooks item names must be unique, so linking is how an item that already exists is used. With Error, the transfer fails with QBOL-BIZL-1004. A product is never linked to a QuickBooks category or bundle: that match fails with QBOL-BIZL-1005 under any setting.
Sales Transaction FROM iPaaS.com (collections Add QuickBooks Online Sales Receipt FROM iPaaS.com and Add/Update QuickBooks Online Invoice FROM iPaaS.com): set collision handling to Error. A transaction is matched by document number. A QuickBooks document with the same number is usually a different sale or one entered by hand, so the transfer stops with QBOL-BIZL-1006 naming it and nothing is overwritten. Choose Remap and Link only when you load transactions that already exist in QuickBooks, for example when you move from another way of posting sales.
Payment Method FROM iPaaS.com (collection Add QuickBooks Online Payment Method FROM iPaaS.com): set collision handling to Remap and Link. A method is matched by name; linking uses the QuickBooks method that already exists. With Error, the transfer fails with QBOL-BIZL-1003.
Payment Method TO iPaaS.com (collection Add/Update QuickBooks Online Payment Method TO iPaaS.com): no collision handling is needed. Before the transfer, the integration links a QuickBooks method to the iPaaS.com method with the same name, in any letter case (QuickBooks Visa and iPaaS.com VISA link), so the transfer updates that iPaaS.com method instead of creating another.

Fields to Keep Mapped

The default templates also map these fields; keep them:

IpaasTransactionId (Sales Receipt and Invoice FROM iPaaS.com), from the iPaaS.com transaction Id. An order posted as an invoice and paid later then pays the QuickBooks invoice it was itself posted as, found through its iPaaS.com link. Another QuickBooks invoice with the same number and customer is not paid: with collision handling Error, the transfer stops with QBOL-BIZL-1006 and nothing is posted or paid.
SourceStatus (Sales Receipt and Invoice FROM iPaaS.com), from the iPaaS.com transaction Status. When a sale already posted to QuickBooks is cancelled, refunded or returned at the source, the transfer stops with QBOL-BIZL-1007, naming the QuickBooks document and the reversal to enter in QuickBooks; nothing is changed in QuickBooks. Unmap it to turn the check off.
Status (Payment TO iPaaS.com), from the integration's payment Status: Completed, or Voided with amount 0 for a payment that reached iPaaS.com and was later voided or deleted in QuickBooks.
Amount (Sales Receipt Payment FROM iPaaS.com): required. A sale paid with two or more payment methods is posted as an invoice paid by one QuickBooks payment per payment, each for its own amount.

Filters

Review the filters before you go live:

Paid in full: an order whose captured payments cover its total becomes a sales receipt. A captured payment is one whose iPaaS.com Status is Completed; declined, pending and refunded payments do not count. If your source system reports captured payments with another status, change "Completed" in both transaction filters and both payment filters.
On terms or part-paid: an invoice, an order with no payment, or an order whose captured payments are less than its total becomes an invoice, with the captured payments recorded on it.
No captured payment: an order that carries payments, none of them captured, is held: neither collection posts it until a payment is captured. To post such orders as open invoices instead, see Posting an Open Invoice Instead of Holding the Order in the Add/Update QuickBooks Online Invoice FROM iPaaS.com description.
Already posted: a posted sales receipt and a fully paid invoice are left as they are. A posted document whose sale is cancelled, refunded or returned at the source is reported with QBOL-BIZL-1007; an order that was never posted is skipped.
Skipped and held orders do not appear in the error logs.

Payments are sent only for transactions that became QuickBooks invoices: a sales receipt already includes its payment.

Enable the Scopes

Changes TO iPaaS.com are found by polling. Turn on the polls for the data you want TO iPaaS.com:

Scope	Turn on	What it does
`customer/poll`	For customers TO iPaaS.com	New and changed customers. The poll also reads inactive customers, but the default customer template takes only active ones.
`item/poll`	For items TO iPaaS.com	New and changed items. Inventory items carry their quantity on hand.
`inventory/poll`	For inventory TO iPaaS.com	Quantity on hand of Inventory items.
`invoice/poll`	For invoice status and payments TO iPaaS.com	Changed invoices: status, balance, paid date and the payments applied to them.
`paymentmethod/poll`	Optional	QuickBooks' payment methods, for the payment-method translation.
`inventory/updated`	Manual only	Transfers one item's quantity on hand by its QuickBooks item id.

Create a polling event for each poll you turn on. A poll runs only on a schedule: nothing arrives TO iPaaS.com until the subscription has a polling event for that scope. Subscribing and creating the default mappings do not create these events. For each scope you turn on, go to Dashboard / Integration Monitoring / Events, add a polling event for this subscription and that scope, and set it to run every 15 minutes (see Events). Production schedules run in UTC.

Set the polling interval to 15 minutes. It keeps QuickBooks current without coming near QuickBooks' limits of 500 requests a minute for each QuickBooks company and 10 a second for each company and app (Intuit: API call limits and throttles). Each poll also uses part of an overall monthly allowance for data reads that iPaaS.com manages for its Intuit app, even when it finds nothing, so don't poll more often than you need. If rate-limit errors continue for hours, contact your Managed Integration Service Provider (MiSP), or iPaaS.com Support at support@ipaas.com (see QuickBooks Online Known Limitations).

Turn On the iPaaS.com Webhooks (FROM iPaaS.com)

Data FROM iPaaS.com (customers, items, sales receipts, invoices, payments, payment methods) is sent when iPaaS.com tells the subscription that a record changed. A new subscription has all of these webhooks off, so nothing goes to QuickBooks until you turn them on. On the subscription, open Outbound Data Flows and make these scopes Active:

Scope	Turn on	What it sends to QuickBooks
`transaction/created`, `transaction/updated`	Always	Orders and invoices, as sales receipts and invoices, with their payments. The transaction's customer and items are found or created with it.
`customer/created`, `customer/updated`	Only if customers should reach QuickBooks on their own, before they buy	Customers
`product/created`, `product/updated`	Only if products should reach QuickBooks on their own, before they sell	Items
`paymentmethod/created`, `paymentmethod/updated`	Only if new iPaaS.com payment methods should be created in QuickBooks	Payment methods

Turn on transaction/created last, after collision handling, the translations and the settings are done, because from then on every new order is posted. These webhooks are iPaaS.com's own; they have nothing to do with Intuit webhooks.

Intuit Webhooks

Intuit webhooks are not offered in this release. The integration signs in with iPaaS.com's own Intuit app, and that app sends no webhooks: Intuit sends every event of an app to one URL, which cannot tell the subscriptions apart. Changes TO iPaaS.com are found by polling (see Enable the Scopes).

The qbo.*.v1 scopes (for example qbo.customer.updated.v1) receive no events from Intuit, so don't set up webhooks for them. Their only use is a manual transfer of one record by its QuickBooks id: the Manual Sync page, then choose this subscription, the collection, the scope and the record's id.

Throttling and Concurrency

The subscription's throttle and concurrency settings are filled in when you save it. Leave them at their defaults unless rate-limit errors recur:

Setting	Default	What it controls
API Throttle Limit and API Throttle Seconds	`500` in `60` seconds	How many calls iPaaS.com sends to QuickBooks in each period, FROM iPaaS.com.
API Throttle Limit (To iPaaS) and API Throttle Seconds (To iPaaS)	`500` in `60` seconds	The same, for data TO iPaaS.com.
Concurrent Connections	`10`	How many calls run at the same time.
Concurrent Batch Executions	`10`	How many transfers run at the same time.

These settings pace iPaaS.com's own dispatch; QuickBooks applies its own limits on top (Intuit: API call limits and throttles). If rate-limit errors (QBOL-EXTN-1013) keep recurring, lower Concurrent Batch Executions. See Subscription Configuration – Edit.

Custom Fields

Sales receipts and invoices: custom fields mapped on the Sales Transaction collection are written to QuickBooks' sales form custom fields, matched by name. Each field must exist and be turned on in QuickBooks (Settings → Account and settings → Sales → Custom fields). Values are cut to 31 characters. A name QuickBooks doesn't have fails with QBOL-NFND-1008.
PO number: the PONumber field goes to a sales form custom field named P.O. Number or PO Number when the company has one. Otherwise it is added to the private note as PO {number}.
Customers and items: the integration does not read or write custom fields on them. Item custom fields are not available in the QuickBooks Online v3 API.

Post-Installation Verification

Try the integration on a separate QuickBooks Online company first, such as a QuickBooks Online trial company, so test sales never reach your live books. Create a second subscription for it (for example QuickBooks Online - Test), with its own Company ID, and authorize it with that company. Each subscription connects one QuickBooks company. On the test subscription you can leave the iPaaS.com webhooks off and send single records with Manual Sync, as below.

One customer TO iPaaS.com. Go to the Manual Sync page. Choose the subscription, the direction TO iPaaS.com, the Customer collection and the scope qbo.customer.updated.v1, and enter the id of an active QuickBooks customer (the number after nameId= in the customer's web address in QuickBooks). Click Submit. The customer appears in iPaaS.com. If the transfer fails with "Unable to connect to subscription", see When transfers fail above.
A poll. After the customer/poll event's first run, customers changed in the last Initial Poll Days days arrive in iPaaS.com. Check Dashboard / Integration Monitoring / Error Logs for errors.
A sales receipt. In iPaaS.com, create a paid test order and send it with Manual Sync (direction FROM iPaaS.com, the Sales Receipt collection, the order's iPaaS.com id). Check that a sales receipt appears in the test company with the same number, lines, tax and total, and that no email went to the customer.
An invoice and its payment. Send an unpaid test order or invoice the same way, with the Invoice collection. Check that a QuickBooks invoice appears with its balance. Then add a payment to the iPaaS.com transaction and send it again. Check that the invoice is paid and has one payment.

Every error the integration records carries a code such as QBOL-VALD-1014. Look the code up in QuickBooks Online Error Messages. A connection problem shows its code in Activity Tracker, not in the transfer error (see When transfers fail above). iPaaS.com retries every transfer that logs an error automatically, on a growing schedule, until it succeeds or the error is dismissed, so fix what the error names, or dismiss it when no change is wanted.

Codes you may meet on your first transactions:

Code	Why	What to do
`QBOL-BIZL-1002`	Two or more QuickBooks customers share the order's email, and no QuickBooks CustomerId is mapped. Nothing was written.	Link the right QuickBooks customer to the iPaaS.com customer (its id is then mapped as CustomerId), or give each QuickBooks customer its own email; then resend.
`QBOL-BIZL-1005`	A product name or SKU belongs to a QuickBooks category or bundle, which can't be sold on a line. Nothing was written.	Rename the product or the QuickBooks category or bundle, or map the line's QuickBooks Item Id; then resend.
`QBOL-BIZL-1006`	A QuickBooks sales receipt or invoice already has this document number (collision handling Error), or a paid order has the number and customer of a QuickBooks invoice that is not the invoice the order was posted as. Nothing was posted or paid.	Link the document if it is this order's; otherwise change one of the numbers. Keep the IpaasTransactionId mapping, so a paid-later order finds its own invoice.
`QBOL-VALD-1015`	A payment on an invoice has a missing, zero or negative amount. It is refused before the invoice is written, so nothing was written.	Fix the payment's Amount mapping (it must be positive), then resend.
`QBOL-BIZL-1007`	A sale already in QuickBooks was cancelled, refunded or returned at the source. Nothing was changed in QuickBooks.	Enter the reversal in QuickBooks (a refund receipt for a sales receipt; a credit memo, and a refund for money returned, for an invoice; or void an invoice that was never owed), then dismiss the error.
`QBOL-BIZL-1008`	The sales receipt or invoice was changed in QuickBooks (a line added, removed or repriced, or the document voided) since iPaaS.com last wrote it. Nothing was overwritten.	Dismiss the error to keep the QuickBooks version, or delete the "iPaaS.com sync …" mark from the document's private note in QuickBooks and resend to overwrite it.
`QBOL-INTL-1002`	The order's link to its QuickBooks invoice could not be read from iPaaS.com. Nothing was posted.	Usually nothing: iPaaS.com retries it. If it keeps failing, check the iPaaS.com status page or contact your MiSP or iPaaS.com support.

Support and Troubleshooting

Click the Help button on any iPaaS.com page to contact Support or to search our documentation.

iPaaS.com Support Portal: https://support.ipaas.com/en/
iPaaS.com Contact Information: https://ipaas.com/contact-us/
Documentation: iPaaS.com API Introduction
QuickBooks Online help: https://quickbooks.intuit.com/learn-support/en-us

QuickBooks Online Installation Instructions