Skip to main content

QuickBooks Online Error Messages

Catalog of the errors the iPaaS.com QuickBooks Online integration records, with what causes each one and what to do about it.

Overview

This article lists the errors the QuickBooks Online integration can record in iPaaS.com. Each error starts with a stable code you can search for on this page. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Some resolutions refer to your Managed Integration Service Provider (MiSP): the partner who set up and manages your iPaaS.com integration.

Each error in iPaaS.com reads as its code, a dash, and the message. The integration's codes start with QBOL; errors raised by iPaaS.com itself have two-part codes, such as VALD-1002, and are explained in the article above.

iPaaS.com retries every transfer that logs an error automatically, on a growing schedule, until it succeeds or the error is dismissed. A temporary problem (a rate limit, a network problem or a QuickBooks outage) usually clears on a retry, with nothing for you to do. Every other error fails again on each retry until you fix what its resolution names, then resend the record; or, when nothing should be sent, dismiss the error. The errors raised when you click Authenticate are not transfers and are not retried: click Authenticate again.

When QuickBooks refuses a request, the error quotes QuickBooks' own message and code, what the integration was doing (for example "creating Invoice 1031"), and Intuit's id for the request (intuit_tid). Give the intuit_tid to your MiSP, or to Intuit support, if you need to escalate. Some QuickBooks answers are expected and are not errors. A "not found" answer when the integration is only reading a record (for example, a customer deleted in QuickBooks before a queued transfer read it) is treated as "nothing to transfer" and raises no error.

Supported Flows

  • Authorization and sign-in (any call)

  • Any QuickBooks call

  • Calls to iPaaS.com, and internal errors

  • Customer FROM iPaaS.com

  • Item FROM iPaaS.com, and items for transaction lines

  • Payment Method FROM iPaaS.com

  • Sales receipt and invoice FROM iPaaS.com, with invoice payments

Error Collection

Authorization and sign-in

Where to find these codes. QBOL-AUTH-1001 to QBOL-AUTH-1006, and QBOL-AUTH-1008, stop a transfer before it connects to QuickBooks. iPaaS.com then shows the transfer error only as "Unable to process transfer. Reason: Unable to connect to subscription with id ...", without the code. QBOL-AUTH-1002 and QBOL-AUTH-1003 can also appear in the transfer error itself, when QuickBooks refuses the sign-in partway through a transfer, for example soon after the app is disconnected in QuickBooks. Open iPaaS.com's Activity Tracker and look for the entries at the same time as the error, with the same reference id: they carry the code and the message below. The most common one on a new subscription is QBOL-AUTH-1004 (fill Company ID); after a long pause or a disconnect it is QBOL-AUTH-1003 (click Authenticate).

Intuit app keys missing

QBOL-AUTH-1001 - The QuickBooks Online integration is not configured: its Intuit app keys are missing. Contact iPaaS.com support; nothing on the subscription needs changing.

  • Description: The integration signs in with iPaaS.com's own Intuit app, whose keys iPaaS.com keeps on the integration, never on the subscription. The keys are missing, so no call is made. It can appear when you click Authenticate or on any transfer; iPaaS.com retries a failed transfer until the keys are restored or the error is dismissed.

  • Resolution: Contact iPaaS.com support. Nothing on the subscription needs changing, and there are no keys for you to enter.

Not authorized yet

QBOL-AUTH-1002 - This subscription has no QuickBooks sign-in yet (or it was removed). Click Authenticate (the lock icon) on the subscription and connect the QuickBooks company.

  • Description: The subscription's Persistent Data has no Refresh Token. The subscription was never authorized, or the token was removed.

  • Resolution: Click the Authenticate (lock) icon on the subscription, sign in to Intuit as a QuickBooks admin, choose the company and click Connect.

Sign-in refused

QBOL-AUTH-1003 - QuickBooks refused the saved sign-in (it was revoked, expired after 100 days unused, or replaced). Click Authenticate (the lock icon) on the subscription to connect QuickBooks again.

  • Description: Intuit refused the saved refresh token (invalid_grant), even after the integration re-read it in case another transfer had just replaced it. The app was disconnected in QuickBooks, the token went unused for 100 days, or a newer sign-in replaced it.

  • Resolution: Click Authenticate on the subscription and connect the company again.

No company linked

QBOL-AUTH-1004 - No QuickBooks company is set for this subscription. Fill the Company ID setting. In QuickBooks Online press Ctrl+Alt+? (Ctrl+Option+? on a Mac) and copy the Company ID; enter the digits without spaces.

  • Description: The Company ID setting is blank. iPaaS.com does not pass the QuickBooks company id to the integration when you authorize, so the setting must be filled.

  • Resolution: Fill Company ID with the id QuickBooks shows when you press Ctrl+Alt+? (Ctrl+Option+? on a Mac) on any QuickBooks Online screen, click Apply, then send the record again. The id can be pasted as QuickBooks shows it: spaces and dashes are ignored.

Company ID is not a number

QBOL-AUTH-1008 - The Company ID setting must be QuickBooks' company id, digits only (got '{value}'). In QuickBooks Online press Ctrl+Alt+? (Ctrl+Option+? on a Mac) and copy the Company ID.

  • Description: The Company ID setting holds something other than the QuickBooks company id, for example letters or the company name. Spaces and dashes are accepted and ignored; anything else that is not a digit is refused before any QuickBooks call.

  • Resolution: Enter the QuickBooks company id: press Ctrl+Alt+? (Ctrl+Option+? on a Mac) on any QuickBooks Online screen and copy the Company ID. Click Apply, then send the record again.

Intuit app keys rejected

QBOL-AUTH-1005 - Intuit rejected the integration's app keys. Contact iPaaS.com support; nothing on the subscription needs changing.

  • Description: Intuit's token endpoint answered invalid_client: it did not accept the keys of iPaaS.com's Intuit app, which the integration signs in with.

  • Resolution: Contact iPaaS.com support. Nothing on the subscription needs changing. Once iPaaS.com corrects the keys on the integration, the next transfer reads them again.

Token endpoint gave no token

QBOL-AUTH-1006 - Intuit's token endpoint did not return an access token ({Intuit's error or HTTP status}). The transfer will be retried.

  • Description: Intuit's token endpoint failed for a reason other than a refused token or refused keys, or could not be reached. This is usually temporary.

  • Resolution: None needed at first: iPaaS.com retries the transfer. If it keeps happening, your MiSP can check the error Intuit returned.

Access token refused

QBOL-AUTH-1007 - QuickBooks refused the access token while {action}. Check that the Company ID setting is the company you connected; if it is, click Authenticate (the lock icon) on the subscription to connect QuickBooks again.

  • Description: QuickBooks answered 401 even after the integration refreshed the token and retried.

  • Resolution: Click Authenticate on the subscription and connect the company again.

User not allowed

QBOL-AUTZ-1001 - The connected QuickBooks user may not do this ({action}): {QuickBooks' message}. Check that the Company ID setting is the company you connected, and sign in as a QuickBooks admin when you authorize.

  • Description: QuickBooks answered 403. The user who authorized does not have the rights this call needs.

  • Resolution: Click Authenticate again and sign in as a QuickBooks admin user.

Authorization code refused

QBOL-AUTH-1009 - Intuit refused the authorization code ({Intuit's error or HTTP status}). Click Authenticate again; if it keeps failing, contact iPaaS.com support (the Intuit app's keys or redirect URIs).

  • Description: After you connected on Intuit's page, Intuit would not exchange the code for tokens. If it happens every time, the cause is on iPaaS.com's side: the keys or the redirect URIs of iPaaS.com's Intuit app.

  • Resolution: Click Authenticate again. If it keeps failing, contact iPaaS.com support. Nothing on the subscription needs changing.

Access not granted

QBOL-AUTH-1010 - Intuit did not grant access ({Intuit's error}). Click Authenticate again and choose Connect on Intuit's page.

  • Description: Intuit returned an error instead of a code, for example because access was declined on its page.

  • Resolution: Click Authenticate again and choose Connect.

No authorization code

QBOL-AUTH-1011 - Intuit's callback had no authorization code. Click Authenticate again.

  • Description: Intuit's callback reached iPaaS.com without a code.

  • Resolution: Click Authenticate again.

Company id not passed

QBOL-AUTH-1012 - Signed in. iPaaS.com did not pass the QuickBooks company id: fill the Company ID setting. In QuickBooks Online press Ctrl+Alt+? (Ctrl+Option+? on a Mac) and copy the Company ID; enter the digits without spaces.

  • Description: Signing in succeeded and the sign-in is saved, but iPaaS.com did not pass the QuickBooks company id with it. This is a log entry, not a failed transfer. When the Company ID setting is already filled, the message ends "the Company ID setting is used." and nothing needs doing.

  • Resolution: Fill the Company ID setting with the id QuickBooks shows when you press Ctrl+Alt+? (Ctrl+Option+? on a Mac) on any QuickBooks Online screen, unless it is already filled. Spaces and dashes are ignored.

Any QuickBooks call

QuickBooks refused the data

QBOL-EXTN-1001 - QuickBooks refused the request while {action}: {Message}: {Detail} (code {code}, field {element}, intuit_tid {id}).

  • Description: A ValidationFault with a code not listed below, for example a business rule. The field is named when QuickBooks names it.

  • Resolution: Fix the mapped value in iPaaS.com or in the source system, then resend the record.

Accounting period closed (6210)

QBOL-EXTN-1001 - QuickBooks refused the request while {action}: Account Period Closed, Cannot Update Through Services API: {Detail} (code 6210, intuit_tid {id}).

  • Description: QuickBooks' books are closed for the document's date. QuickBooks refuses any change to a document dated on or before the closing date, and any new document dated in that period. iPaaS.com retries the transfer, and it fails the same way while the period stays closed. A new payment on an invoice in the closed period does not cause this error: it is recorded in the open period (see QBOL-BIZL-1012 when the invoice was also changed).

  • Resolution: Make the change in QuickBooks, dated in the open period, for example by entering a late order as a new document. Then dismiss the error. See QuickBooks Online Known Limitations, section 25.

Value too long (2050)

QBOL-EXTN-1007 - QuickBooks refused the request while {action}: {Message}: {Detail} (code 2050, field {element}, intuit_tid {id}).

  • Description: A value is longer than QuickBooks allows for the field the message names.

  • Resolution: Shorten the value in the mapping, for example with a formula, then resend.

Record changed in QuickBooks (5010)

QBOL-EXTN-1008 - QuickBooks refused the request while {action}: {Message}: {Detail} (code 5010, ..., intuit_tid {id}).

  • Description: The record was saved in QuickBooks between the integration's read and its update. The integration already read it again and retried once; it changed again.

  • Resolution: None needed at first: iPaaS.com retries the transfer, which reads the record again. If the error stays, resend the record once nobody is editing it in QuickBooks.

Duplicate document number (6140)

QBOL-EXTN-1009 - QuickBooks refused the request while {action}: {Message}: {Detail} (code 6140, ..., intuit_tid {id}).

  • Description: Another transaction already has this document number.

  • Resolution: Check QuickBooks for the transaction. Link it, or change the document number in the mapping.

Duplicate name (6240)

QBOL-EXTN-1010 - QuickBooks refused the request while {action}: {Message}: {Detail} (code 6240, ..., intuit_tid {id}).

  • Description: The name is already used. Customer display names must be unique across customers, vendors and employees; item and payment method names must be unique. A customer with an email is retried once with the email added to the display name, on a create and on an update, and a customer saved that way keeps that name on later updates. For a customer, this error therefore means it has no email.

  • Resolution: Make the name unique in the mapping, or link the existing record, then resend.

Record not found (404)

QBOL-NFND-1001 - QuickBooks could not find the record while {action}.

  • Description: QuickBooks answered 404 with no Fault. Reads that expect a record may be gone do not raise this.

  • Resolution: Check the record in QuickBooks. If it was deleted on purpose, dismiss the error.

Object not found (610)

QBOL-NFND-1002 - QuickBooks refused the request while {action}: {Message}: {Detail} (code 610, ..., intuit_tid {id}).

  • Description: A record the call refers to (for example a customer, item or account) does not exist or is not usable.

  • Resolution: Check the record named in the message, fix the reference in the mapping or translation, then resend.

Could not reach QuickBooks

QBOL-EXTN-1002 - Could not reach QuickBooks at {API Url host} while {action}: {reason}. Check the API Url setting.

  • Description: No answer came back. The API Url may be wrong, or the network or QuickBooks had a problem.

  • Resolution: Check that API Url is quickbooks.api.intuit.com. If it is right, the problem is temporary: iPaaS.com retries the transfer.

QuickBooks unavailable

QBOL-EXTN-1003 - QuickBooks answered {status} while {action} (intuit_tid {id}). The transfer will be retried.

  • Description: QuickBooks answered with a server error and no Fault. This is usually temporary.

  • Resolution: None needed at first: iPaaS.com retries the transfer. If it keeps happening, your MiSP can raise it with Intuit using the intuit_tid.

No company information

QBOL-EXTN-1004 - QuickBooks answered without company information.

  • Description: The integration's connection check read the company, but the answer had no company name.

  • Resolution: Check API Url and Company ID, then send the record again.

Unexpected refusal (other 4xx)

QBOL-EXTN-1005 - QuickBooks answered {status} while {action} (intuit_tid {id}).

  • Description: QuickBooks refused the call with a 4xx status other than 401, 403, 404 or 429, and no Fault.

  • Resolution: Correct what the message names and resend the record, or dismiss the error. If it persists, your MiSP can review it with the intuit_tid.

QuickBooks refused the request

QBOL-EXTN-1006 - QuickBooks refused the request while {action}: {Message}: {Detail} (code {code}, field {element}, intuit_tid {id}).

  • Description: A Fault that is not a validation fault, with a code not listed above.

  • Resolution: Correct what the message names, then resend. If it is not clear, your MiSP can review it with the intuit_tid.

Rate limit reached (429)

QBOL-EXTN-1014 - QuickBooks limited the request rate while {action} (500 requests a minute per company). iPaaS.com will retry after a minute.

  • Description: Intuit allows each app 500 requests a minute, and 10 requests a second, for each QuickBooks company. One of these limits was reached. QuickBooks gives the same answer when a read goes beyond an overall monthly allowance for data reads that iPaaS.com manages for its Intuit app.

  • Resolution: None needed at first: iPaaS.com holds the transfer and retries it after a minute. If it happens often, lower Concurrent Batch Executions on the subscription. If rate-limit errors continue for hours, contact your MiSP, or iPaaS.com Support at support@ipaas.com.

Calls to iPaaS.com, and internal errors

iPaaS.com call failed

QBOL-INTL-1002 - iPaaS.com could not complete {action} ({status}). The transfer is retried; if it keeps failing, contact iPaaS.com support.

  • Description: During some transfers the integration reads data from iPaaS.com, for example a paid order's link to the QuickBooks invoice it was posted as. iPaaS.com did not answer, or answered with an error. The status is the HTTP status, or "no response". The error usually appears inside QBOL-EXTN-1013. This is usually temporary.

  • Resolution: None needed at first: iPaaS.com retries the transfer. If it keeps failing, raise it with your MiSP first, then iPaaS.com Support at support@ipaas.com.

Internal error

QBOL-INTL-1001 - Internal: call to {step} with unhandled parameters ({collection type}, {details}). Nothing was written. Contact iPaaS.com support with this message.

  • Description: iPaaS.com asked the integration to handle a record it was not built to handle in that step. Nothing was written to QuickBooks. It points to a problem in the integration or its setup, not in your data.

  • Resolution: Raise it with your MiSP first, then iPaaS.com Support at support@ipaas.com, with the full message and the iPaaS.com error log entry.

Customer FROM iPaaS.com

Customer has no name

QBOL-VALD-1001 - A QuickBooks customer needs a display name, company name, first or last name, or email. Map at least one.

  • Description: QuickBooks requires a display name. With none mapped, the integration uses the company name, else first and last name, else the email. All were empty.

  • Resolution: Map at least one of them in the Customer collection.

Customer already exists

QBOL-BIZL-1001 - QuickBooks already has customer {id} ('{display name}') with this email or display name. Link it, or set the collection's collision handling to Remap and Link or Update and Link.

  • Description: A customer with this email (or, with no email, this display name) exists, and the collection's Collision Handling Method is Error.

  • Resolution: Link the existing customer, or set the collection's Collision Handling Method to Remap and Link or Update and Link.

Email shared by several QuickBooks customers

QBOL-BIZL-1002 - QuickBooks has {2 or 3 or more} customers with the email {email}: {id} '{name}', {id} '{name}'. The integration does not guess which one, so nothing was written. Map the transaction's or customer's QuickBooks Customer Id (link the right customer), or give each QuickBooks customer its own email.

  • Description: The customer is matched by email, because no QuickBooks Customer Id was mapped, and two or more QuickBooks customers have that email. QuickBooks allows it; the integration does not pick one. It applies to Customer FROM iPaaS.com under every collision handling setting, and to sales receipts and invoices FROM iPaaS.com whose customer is matched by email.

  • Resolution: Link the right QuickBooks customer to the iPaaS.com customer, so its QuickBooks id is mapped as Customer Id, or give each QuickBooks customer its own email. Then resend.

Customer update without its id

QBOL-VALD-1002 - Cannot update a QuickBooks customer without its id (got '{value}').

  • Description: The update had no valid QuickBooks customer id.

  • Resolution: Check the customer's external id in iPaaS.com.

Payment term not found

QBOL-NFND-1004 - QuickBooks has no payment term '{terms}'. Create it (Settings > All lists > Terms) or fix the customer's Terms mapping.

  • Description: The customer's Terms names a term QuickBooks does not have.

  • Resolution: Create the term in QuickBooks, or fix the mapping.

Record to update is gone

QBOL-NFND-1003 - QuickBooks has no {record} {id} to update (it may have been deleted). Remove the stale link in iPaaS.com and send the record again.

  • Description: An update (of a customer, item, payment method, sales receipt or invoice) found no record with that id in QuickBooks.

  • Resolution: Remove the external id link in iPaaS.com, then send the record again so it is created.

Item FROM iPaaS.com, and items for transaction lines

Unknown item type

QBOL-VALD-1005 - '{type}' is not a QuickBooks item type: use Inventory, NonInventory or Service (a translation can map the iPaaS.com product type).

  • Description: The item's Type is not one QuickBooks knows.

  • Resolution: Map Inventory, NonInventory or Service, for example with a translation.

Item has no name or SKU

QBOL-VALD-1006 - A QuickBooks item needs a name or a SKU.

  • Description: A new item is created only with a name or a SKU to name it by, and the product carries neither.

  • Resolution: Map Name or Sku in the Product collection.

Item already exists

QBOL-BIZL-1004 - QuickBooks already has item {id} ('{name}', SKU '{sku}'). Link it, or set the collection's collision handling to Remap and Link or Update and Link.

  • Description: An item with this SKU or name exists, and the collection's Collision Handling Method is Error.

  • Resolution: Link the existing item, or set the collection's Collision Handling Method to Remap and Link or Update and Link.

Name or SKU of a category or bundle

QBOL-BIZL-1005 - The {SKU or name} belongs to QuickBooks {Category or Group} {id} ('{name}'), which is not a product or service and cannot be sold or linked. Rename one of them, or map the line's QuickBooks Item Id.

  • Description: Only Inventory, Non-inventory and Service items are matched. The product's name or SKU belongs to a QuickBooks category or bundle (a Group item), which cannot be linked to a product or sold on a line. A product FROM iPaaS.com that matches one is refused under every collision handling setting. On a transaction line, a name that belongs to a category or bundle, on a line that has a SKU, does not raise this: the line gets an item of its own named "Name (SKU)". This error is raised for a line whose SKU belongs to a bundle, or whose name belongs to a category or bundle and that has no SKU. Nothing is written.

  • Resolution: Rename the product or the QuickBooks category or bundle, give the line a SKU, or map the line's QuickBooks Item Id. Then resend.

Item update without its id

QBOL-VALD-1007 - Cannot update a QuickBooks item without its id (got '{value}').

  • Description: An update of a product linked to QuickBooks reached the integration, but its external id is not a QuickBooks item id (for example, it was edited by hand or copied from another system).

  • Resolution: Check the product's external id in iPaaS.com.

Account not found

QBOL-NFND-1005 - QuickBooks has no account '{name or id}'. Fix the {setting} setting (or the item's account mapping) to an account name or id from the chart of accounts.

  • Description: Income Account, Expense Account or Inventory Asset Account, or the item's mapped account, names an account QuickBooks does not have.

  • Resolution: Set it to an account name or id from your chart of accounts. Write a sub-account as Parent:Child.

Item missing for a line

QBOL-NFND-1006 - QuickBooks has no item with SKU '{sku}' or name '{name}', and Create Missing Items is off. Create the item, send the product first, or turn the setting on.

  • Description: A transaction line (or the shipping line) names an item QuickBooks does not have, and Create Missing Items is false.

  • Resolution: Create the item in QuickBooks, send the product FROM iPaaS.com first, or set Create Missing Items to true. Then resend the transaction.

Payment Method FROM iPaaS.com

Payment method has no name

QBOL-VALD-1003 - A QuickBooks payment method needs a name.

  • Description: A new payment method is created only with a name, and the iPaaS.com payment method has none.

  • Resolution: Map Name in the Payment Method collection.

Payment method already exists

QBOL-BIZL-1003 - QuickBooks already has payment method {id} '{name}'. Link it, or set the collection's collision handling to Remap and Link.

  • Description: A payment method with this name exists in QuickBooks, and the collection's Collision Handling Method is Error.

  • Resolution: Link the existing payment method, or set the collection's Collision Handling Method to Remap and Link.

Payment method update without its id

QBOL-VALD-1004 - Cannot update a QuickBooks payment method without its id (got '{value}').

  • Description: An update of a payment method linked to QuickBooks reached the integration, but its external id is not a QuickBooks payment method id.

  • Resolution: Check the payment method's external id in iPaaS.com.

Sales receipt and invoice FROM iPaaS.com

Unknown transaction type

QBOL-VALD-1008 - '{type}' is not a QuickBooks transaction type this integration writes: use SalesReceipt or Invoice.

  • Description: The mapped Transaction Type is not Invoice, SalesReceipt or Receipt (in any letter case, spaces ignored).

  • Resolution: Map Transaction Type to SalesReceipt or Invoice.

Transaction type missing

QBOL-VALD-1012 - Transaction Type is required: SalesReceipt or Invoice (the default templates set it).

  • Description: A new transaction is created as a sales receipt or an invoice, and Transaction Type is blank because its mapping was removed or returns nothing.

  • Resolution: Map Transaction Type in the Transaction collection.

Document number too long

QBOL-VALD-1009 - Document number '{number}' is longer than QuickBooks' 21 characters. Shorten it in the mapping (the default template keeps the last 21 and puts the full number in the private note).

  • Description: QuickBooks allows at most 21 characters in a document number. Nothing was sent.

  • Resolution: Shorten the Doc Number mapping, for example to the last 21 characters, and put the full number in Private Note.

Transaction has no lines

QBOL-VALD-1010 - A QuickBooks sales receipt or invoice needs at least one line. Check the transaction's line mapping.

  • Description: No product line, shipping amount or discount was mapped.

  • Resolution: Check the Transaction Line collection and its filter.

Transaction has no customer

QBOL-VALD-1011 - The transaction has no QuickBooks customer: map Customer Id (the customer's QuickBooks external id), Customer Email or Customer Name.

  • Description: The integration could not find or create the customer: no customer id, email or name was mapped (nor a name on the billing address).

  • Resolution: Map Customer Id, Customer Email or Customer Name.

Transaction already exists

QBOL-BIZL-1006 - QuickBooks already has {type} {id} numbered {number}. Link it, or set the collection's collision handling to Remap and Link or Update and Link.

QBOL-BIZL-1006 - QuickBooks already has Invoice {id} numbered {number} for this customer, and it is not the invoice this order was posted as. Nothing was posted or paid. Link the order to that invoice, or set the collection's collision handling to Remap and Link or Update and Link.

  • Description: A sales receipt or invoice with this document number exists, and the collection's Collision Handling Method is Error. The second form comes from Add QuickBooks Online Sales Receipt FROM iPaaS.com: a paid order has the document number and customer of a QuickBooks invoice that is not the invoice the order was itself posted as (for example an invoice entered by hand). A paid order is applied only to its own invoice, found through its iPaaS.com link, so that invoice is not paid. When the collection's Ipaas Transaction Id mapping is blank, the message says so, because the order's own invoice cannot be found without it. Nothing is posted or paid.

  • Resolution: If the QuickBooks document belongs to this order, link it; otherwise change one of the document numbers. Or set the collection's Collision Handling Method to Remap and Link or Update and Link. For paid-later orders, keep the Ipaas Transaction Id mapping (the default template maps it from the transaction Id). Then resend.

Transaction update without its id

QBOL-VALD-1013 - Cannot update a QuickBooks {type} without its id (got '{value}').

  • Description: An update of a transaction linked to QuickBooks reached the integration, but its external id does not hold a QuickBooks document id.

  • Resolution: Check the transaction's external id in iPaaS.com. It has the form Invoice-{id} or SalesReceipt-{id}.

Tax amount needs a tax code

QBOL-VALD-1014 - This QuickBooks company uses manual sales tax, so a tax amount needs a tax code. Fill the Sales Tax Code setting (e.g. the tax code or group named for the state) or map Tax Code.

  • Description: The transaction has a tax total other than zero, no tax code is mapped or set, and the company does not use automated sales tax. QuickBooks would ignore the tax total.

  • Resolution: Fill Sales Tax Code on the subscription, or map Tax Code. Then resend.

Payment method not found

QBOL-NFND-1007 - QuickBooks has no payment method '{name}'. Create it in QuickBooks, or fix the mapping or translation that supplies it.

  • Description: A sales receipt's or payment's method names a payment method QuickBooks does not have. This usually means the payment-method translation has no entry for it. On a new sales receipt or invoice, every payment's method is checked before anything is written, so the error names the method whichever payment carries it.

  • Resolution: Add the entry to the translation, or create the payment method in QuickBooks. Then resend.

QBOL-NFND-1007 - The iPaaS.com payment method '{method}' has no QuickBooks payment method in the payment-method translation. Add a row for it (iPaaS.com: the collection's Method translation), then retry.

  • Description: The iPaaS.com payment method has no row in the payment-method translation. iPaaS.com sends an untranslated value as blank, so without this check the sales receipt or payment would post with no method at all. The integration tells the two cases apart with SourceMethod (the method mapped untranslated).

  • Resolution: Add a row for the method to the payment-method translation, then resend.

Custom field not found

QBOL-NFND-1008 - QuickBooks has no sales form custom field named '{name}'. Add it (Settings > Account and settings > Sales > Custom fields) or remove the mapping.

  • Description: A custom field mapped on the transaction has no turned-on sales form custom field with that name in QuickBooks.

  • Resolution: Add and turn on the custom field in QuickBooks, or remove the mapping.

Reference not found

QBOL-NFND-1009 - QuickBooks has no {payment term, deposit account, class, location or sales tax code} '{name}'. Create it in QuickBooks, or fix the mapping or translation that supplies it.

  • Description: A name used by the transaction or payment (terms, Deposit Account, class, location, Sales Tax Code or Tax Code) matches nothing in QuickBooks.

  • Resolution: Create it in QuickBooks, or fix the setting, mapping or translation.

Payment amount missing

QBOL-VALD-1015 - A payment for invoice {id} needs a positive amount (got {amount or none}). Nothing was written. Fix the payment at the source, or exclude it with the payment collection's filter (the default records only Completed payments above 0), then resend.

QBOL-VALD-1015 - A payment for invoice {id} needs a positive amount.

  • Description: A payment to record on an invoice has no amount, or an amount of zero or less. It is checked before the invoice is written (the longer message: nothing is written), and again as each payment is recorded (the shorter message: that payment is not recorded). The default template's payment filter (Status == "Completed" && Amount > 0) keeps such payments out.

  • Resolution: Fix the payment's Amount at the source or in the mapping, or leave the payment out with the payment collection's filter. Then resend.

Same-amount payment entered in QuickBooks

QBOL-BIZL-1010 - Invoice {id} already has QuickBooks payment {QuickBooks payment id} of {amount}, entered in QuickBooks, and nothing tells whether this iPaaS.com payment {payment id} of {amount} is the same payment. Nothing was written. In QuickBooks, edit the memo of payment {QuickBooks payment id}: if it is the same payment, add "{mark}"; if it is another payment, add "iPaaS.com: not this payment" and the integration records this one. Then resend the transaction.

  • Description: A new payment FROM iPaaS.com for an invoice has the same amount as a payment entered by hand on that invoice in QuickBooks, and nothing tells whether they are the same payment: no reference on both sides, and no matching date (a different date alone is not enough). Recording it could pay the invoice twice; skipping it could lose a real second payment. So nothing is written. The same-payment mark is iPaaS.com payment followed by the iPaaS.com payment id, or iPaaS.com payment (no id) for a payment without one. iPaaS.com's transaction payment has no reference or date field of its own, and the default templates map neither, so with the default templates every such payment is refused. Under Update and Link collision handling the invoice is still linked; only the payment waits.

  • Resolution: Edit the memo of the QuickBooks payment the message names, in QuickBooks. If it is the same payment, add the quoted iPaaS.com payment … mark: nothing is recorded again. If it is another payment, add iPaaS.com: not this payment: the integration records the iPaaS.com payment itself, with its method and deposit account. The marks are not case-sensitive. Then resend the transaction; until then iPaaS.com retries it. See QuickBooks Online Known Limitations, section 14.

Reversed at the source after posting

QBOL-BIZL-1007 - The iPaaS.com transaction {number} is {status} at the source, but it is already posted to QuickBooks as {type} {id}. The integration does not reverse QuickBooks documents, so nothing was changed. In QuickBooks, {the reversal to enter}; then dismiss this error.

  • Description: A sales receipt or invoice the integration posted belongs to an iPaaS.com transaction that is now Cancelled, Refunded, Partially Refunded or Returned. The integration writes no refunds, credit memos or voids, so it stops and names the document, and nothing is changed in QuickBooks. The message names the reversal: a refund receipt for a sales receipt; for an invoice, a credit memo for the amount refunded and a refund for any money returned, or a void when the invoice was cancelled and nothing was owed. An order cancelled, refunded or returned before it was ever posted is skipped by the default filters, with no error; if a filter lets one through, it is refused with QBOL-BIZL-1011. The check uses the collection's Source Status mapping.

  • Resolution: Enter the reversal in QuickBooks, then dismiss the error; iPaaS.com retries it until it is dismissed. To turn the check off, unmap Source Status; that also turns off the check for QBOL-BIZL-1011.

Reversed at the source before posting

QBOL-BIZL-1011 - The iPaaS.com transaction {number} is {status} at the source and was not posted to QuickBooks, so there is no sale to post. Nothing was written. If the books need it (for example a partial refund), enter the sale and its refund in QuickBooks; otherwise dismiss this error. The default filters skip a {status} transaction that is not in QuickBooks yet: add that clause to the collection's filter to stop this error.

  • Description: An iPaaS.com transaction that is Cancelled, Refunded, Partially Refunded or Returned reached a sales receipt or invoice collection before the integration ever posted it to QuickBooks. Posting it would book a sale the source has reversed, so nothing is written. The default filters of both collections skip such a transaction, so this error means the collection's filter lets it through. The check runs before the integration looks for the document in QuickBooks, so it is raised even when a matching document was entered in QuickBooks by hand. The check uses the collection's Source Status mapping.

  • Resolution: First check QuickBooks for the sale, for example by its document number. If it is already there, leave it and dismiss the error. If it is not and the books need it (for example the part of a partly refunded order that was kept), enter the sale and its refund in QuickBooks, then dismiss the error. To stop the error, restore the default filter's status clause.

Closed-period invoice: change not written, payment recorded

QBOL-BIZL-1012 - Invoice {id} is dated {date}, in a period closed in QuickBooks, so its changed lines or tax from iPaaS.com were not written; QuickBooks refuses changes to a closed period. The payment was recorded in the open period (iPaaS.com payment {payment id} of {amount} is QuickBooks payment {QuickBooks payment id}). To change the invoice, reopen the period in QuickBooks (Settings > Account and settings > Advanced > Accounting > Close the books) and resend the transaction, or record the adjustment in the open period; otherwise dismiss this error.

  • Description: The source sent a new payment for an invoice dated in a period closed in QuickBooks, together with a change to the invoice's lines or tax. The payment was recorded in the open period and applied to the invoice; the invoice was not changed, because QuickBooks refuses changes to a closed period. Sending the transaction again does not record the payment twice; it reports this error again until the invoice matches.

  • Resolution: Reopen the period in QuickBooks and resend the transaction, or record the adjustment in the open period. If the change does not belong in QuickBooks, dismiss the error. See QuickBooks Online Known Limitations, section 25.

Changed in QuickBooks since the last write

QBOL-BIZL-1008 - {type} {id} was changed in QuickBooks since iPaaS.com last wrote it (its lines or amounts differ, or it was voided). Nothing was overwritten. To keep the QuickBooks version, leave it and dismiss this error; to replace it with the iPaaS.com version, delete the "iPaaS.com sync …" mark from the {type}'s private note in QuickBooks, then resend.

  • Description: Every sales receipt or invoice the integration writes ends its private note with a mark that starts with iPaaS.com sync, which records the line amounts it posted. Before an update, the integration compares the document's lines in QuickBooks with the mark. A line was added, removed or repriced in QuickBooks, or the document was voided, so the update is refused and nothing is overwritten. Payments and credit memos applied in QuickBooks do not count as changes. An edit that keeps every line amount (for example a changed description) is not detected.

  • Resolution: To keep the QuickBooks version, dismiss the error. To replace it with the iPaaS.com version, delete the iPaaS.com sync … mark from the document's private note in QuickBooks, then resend.

iPaaS.com link unreadable

QBOL-EXTN-1013 - Could not read iPaaS.com transaction {id}'s link to QuickBooks ({reason}); nothing was posted. The transfer is retried.

  • Description: A paid order is applied to the QuickBooks invoice it was itself posted as, which the integration finds through the order's iPaaS.com link (the Ipaas Transaction Id mapping). Reading that link from iPaaS.com failed, so nothing was posted. This is usually temporary.

  • Resolution: None needed at first: iPaaS.com retries the transfer. If it keeps failing, check the iPaaS.com status page or contact iPaaS.com support.

Unsupported collection type

QBOL-BIZL-1009 - QuickBooks Online does not support this collection's data type (mapping collection type {type}). Remove or deactivate the collection; it can never transfer.

  • Description: The subscription has a mapping collection of a data type QuickBooks Online does not support, for example Gift Card.

  • Resolution: Remove or deactivate that collection. The supported data types are customers, items, quantities, sales receipts, invoices, payments and payment methods.

Invoice updated, payment failed

QBOL-EXTN-1011 - Invoice {id} was updated, but a payment could not be recorded: {the payment's error}

QBOL-EXTN-1011 - Invoice {id} is dated {date}, in a period closed in QuickBooks, so it was not changed, and a payment could not be recorded: {the payment's error}

  • Description: The invoice update succeeded and was saved, or (second wording) the invoice is in a period closed in QuickBooks and was left as it is, but one of its new payments failed, for example because its payment method or deposit account is not in QuickBooks, or because the payment itself is dated in the closed period. The payment's own error is included. A payment with a missing, zero or negative amount does not cause this: it is refused with QBOL-VALD-1015 before the invoice is written.

  • Resolution: Fix the problem the included error names, then resend. Payments already applied to the invoice are recognised and not recorded again.

Invoice created, payment failed

QBOL-EXTN-1012 - Invoice {id} was created, but a payment could not be recorded: {the payment's error}

  • Description: The invoice was created and saved (iPaaS.com links it), but one of its payments failed, for example because its payment method or deposit account is not in QuickBooks. The payment's own error is included. A payment with a missing, zero or negative amount does not cause this: it is refused with QBOL-VALD-1015 before the invoice is written.

  • Resolution: Fix the problem the included error names, then resend. The resend updates the invoice and records only the missing payment: payments already applied to the invoice are recognised and not recorded again.

Reporting an issue

If you see an error not covered above, capture the iPaaS.com Subscription ID, the QuickBooks record (document number or id, if any), and the iPaaS.com error log entry, including the intuit_tid. Raise it with your MiSP first. For problems on the QuickBooks side, your MiSP can contact Intuit support with the intuit_tid.

Related Documents

Related Articles
Did this answer your question?