Resolve Touchless Integration export errors (QBO)

Prev Next

Overview

Below are common errors that you might experience when using Touchless Integration with QuickBooks Online (QBO). The resolution to each error is listed to help you quickly resolve any identified issues.


Who uses this feature

  • Administrators, office employees, managers, accountants, and bookkeepers

  • Applies to all business types

  • Applies to all trades

Feature configuration

  • Account configuration is required to use this feature. Please contact Technical Support for details.

  • Currently, this feature is only available for QuickBooks Online and Intacct.

  • This feature requires the Journal Entries and Accounting Periods features to be set up and configured. For more, see Journal entries overview and Use Accounting Periods.

Things to know

  • The errors below are generalized. For example, where it says “Business Unit Name” the specific name of the business unit experiencing the error would appear. Likewise, the number sign (#) indicates where a number would appear in the error.

  • Sometimes QuickBooks won’t accept the information on the first export run. Try to export again if your first attempt fails. If the error persists, see the error message solutions below.

  • If you’re looking for the solution to a specific error on this page, press Ctrl + F and search for it.

Read errors in QuickBooks

Typically, the first part of a QuickBooks error will generally specify where the error is occurring (Customer list, Item list, etc.) and what item is causing the error (the specific service, customer, business unit, and so on). The second part of the QuickBooks error will generally explain why the error occurred.

Error message indicating a missing Sales Tax Payable item in QuickBooks Item List.


Errors and solutions for QuickBooks Online Touchless Integration

BadRequest. Details: Permission Denied Error : To access this, sign in again or contact an administrator. Missing permission on Account to Read

This error occurs if you do not have sufficient permissions in QuickBooks. Set your permissions in QuickBooks to the correct level to resolve this error. For more, see QuickBooks export permissions.

BadRequest. Details: The account period has closed and the account books cannot be updated through the QBO Services API. Please use the QBO website to make these changes.

This error occurs if you have set a date in QuickBooks Online that does not allow transactions from posting before that date.

In QuickBooks Online:

  1. Go to Settings > Accounts and Settings.

  2. Select the Advanced tab.

  3. Select Edit in the Accounting section.

  4. Change the Closing date in the Close the books section.
    Note: To change your password, enter a new password and confirm it.

  5. Click Save and then Done.

There was an error while communicating with the Ids Server.

This error occurs when the QuickBooks servers are down. This can result from server maintenance, technical issues, or high traffic. We recommend you check the QBO status page for updates and wait until the service is restored.

Validation Exception was thrown.Details:The name supplied already exists. : null.

This error occurs when there are special characters in the Name field for accounts. Remove any special characters in your account names in both ServiceTitan and QuickBooks Online.

Classification mismatch between Source Account (Customer Refunds, Liability and Target Account (Customer Refunds, Revenue).

This error occurs if the GL account types in QuickBooks Online and ServiceTitan do not match. For example, a GL account is classified as a liability account in QuickBooks Online but the same GL account is classified as an asset account in ServiceTitan. Update your GL accounts so the account types match both in ServiceTitan and QuickBooks Online.

QBO Class "[QBOCLASS]" was not found for Business Unit "[BusinessUnit]".

This error occurs if you did not properly map a ServiceTitan business unit to a QuickBooks Online class. Make sure your business units are correctly mapped to an existing QuickBooks Online class. For more, see QBO Onboarding Step 7: Create classes in QuickBooks Online.

BadRequest. Details: The account period has closed. Txn Date=MM/DD/YYYY is before book closing date=MM/DD/YYYY

This error occurs when ServiceTitan tries to push updates but the accounting period is closed in QuickBooks Online.  You need to open the period in QuickBooks and then manually resync from the Journal Entry screen in ServiceTitan.  Then you can close the period again in QuickBooks Online.

JournalEntryConfigurationInvalid - BusinessUnitsNotSupported - Sync peer Qbo:NNNNNNNNNN/NNNNNNNNNN is setup for BusinessUnits ["NNN", “NNNN”]. However, the journal entry contains BusinessUnits ["NNNNNNNN","NNN"].\

This error occurs if different business units are associated with different QuickBooks Online accounts. To resolve this error, all business units in a journal entry must be associated with the same QuickBooks Online account. You can update which business units are connected to a specific QuickBooks Online account using the QuickBooks Online authentication page.

Additionally, if you have imported transactions associated with the Imported Default Business Unit, that business unit should not be deactivated and must be connected to a QuickBooks Online account.

BadRequest. Details: The name supplied already exists. : null

You may receive this error if a customer, vendor, or location name already exists in QuickBooks.

Search across all lists in QuickBooks for the customer, vendor, or location name. If the name found is identical to the one you are attempting to use, change the existing name.

This operation cannot be performed after the request has been submitted.

This error occurs when the QuickBooks servers are down. This can result from server maintenance, technical issues, or high traffic. We recommend you check the QBO status page for updates and wait until the service is restored.

BadRequest. Details: Duplicate Document Number Error : You must specify a different number. This number has already been used. DocNumber=10 is assigned to TxnType=Journal Entry with TxnId=57211

This error occurs if the journal entry number already exists in QuickBooks Online. To resolve this, remove the journal entry from QuickBooks Online and manually resync the journal entry.

The following Accounts were not found in QBO: [{"AccountNumber":"NN","AccountName":"Accounts Receivable","AccountType":"Asset","AccountSubtype":"Accounts Receivable"},{"AccountNumber":"NN","AccountName":"Accrued Sales & Use Tax","AccountType":"Liability","AccountSubtype":"Current Liability"}]

This error occurs if you have missing GL accounts in QBO or the GL account names do not match between ServiceTitan and QBO.

Make sure the GL accounts referenced in the error exist or the GL account names match between ServiceTitan and QBO.

Applied Payment type journal entry sync error to QBO "Payment application can not be journaled at this moment. Related invoice ID=NNNNN is not synchronized yet." or Journal Entry was expected in external system, but was not found with key (XXX).

This error occurs when the invoice is not syncing correctly to the GL service. If you are not syncing journal entries yet, you can bulk sync the records by using the Bulk Sync option on the GL Administration screen under Accounting.

Deposit total NNNNN.N doesn't match sum of payments NNNNNN.NN.

This error occurs when a deposit in QuickBooks Online has already been matched, preventing the journal entry from re-syncing. To fix this, unmatch the deposit from the bank account in QuickBooks Online and re-sync the journal entry.

Validation Exception was thrown. Details: You cannot delete this transaction because it is matched to a transaction that was downloaded into a different account.

This error occurs when a deposit in QuickBooks Online has already been matched, preventing the journal entry from re-syncing. To fix this, unmatch the deposit from the bank account in QuickBooks Online and re-sync the journal entry.

JournalEntryConfigurationInvalid - MultiLevelAutoExport - The Journal Entry is not setup correctly for export. It contains transactions which are setup to export at different levels or some transactions are enabled for auto export but others are not.

This error is rare and may appear when a journal entry is not correctly generated. This can occur when grouped transactions are set to be exported as documents in the same journal entry that contains transactions set to be exported as journal entries.

To fix this, the journal entry must be re-generated by re-syncing the records to the GL service through the GL Administration option under Accounting.

Error: Validation Exception was thrown. Details: This transaction has been deposited. If you want to change or delete it, you must edit the deposit it appears on and remove it first.  

This error occurs when a payment journal entry synced to QuickBooks has been manually deposited and later modified in ServiceTitan

To fix this, remove the payment from the deposit in QBO and re-sync the journal entry.

Sorry but the app didn't connect or You need admin permissions to connect this app to your company

This error occurs when you don’t have admin permissions in QuickBooks Online, when the business units are greyed out and display as N/A, or when multiple business units need to be connected but the connection fails.

Only QuickBooks Online admin users can connect business units to ServiceTitan. If you’re unable to connect, contact your QuickBooks Online administrator to either:

  • Connect the business units for you, or

  • Grant you admin permissions in QuickBooks Online.

If you’re already an admin, try disconnecting and reconnecting all business units through Settings > Integrations > QuickBooks Online.

Error:** "Entity with Key = 'BusinessUnit, (0)' does not exist

This issue occurs when payments or invoices in the batch are missing business unit assignments, which prevents the export from completing successfully. To fix the problem, ensure that every transaction in the batch has a valid business unit assigned.

  1. Review all transactions in the failing batch.

  2. Open each payment or invoice that's missing a business unit.

  3. Assign a valid, active business unit to the transaction.

  4. Save your changes and retry the export.

Doing this ensures all transactions are properly linked to a business unit, allowing the batch to export without errors.

Error: GL account "account name" does not exist in QB, but the account exists in QuickBooks Online

This issue occurs when there’s a mismatch or discrepancy between account details in QuickBooks Online (QBO) and ServiceTitan. Common causes include accounts being set up as sub-accounts in QBO but not in ServiceTitan, differences in account names such as spacing or capitalization, or the account being inactive in QBO. These inconsistencies prevent proper syncing and mapping between the two systems.

To resolve the issue:

  1. Check if the account is a sub-account in QBO. If it is, update ServiceTitan to use the "Parent Account:Sub-account Name" format.

  2. Verify that the account names in both systems match exactly, including spelling, spacing, and capitalization.

  3. In QBO, check whether the account is inactive and reactivate it if necessary.

  4. After making any updates, refresh the GL account mapping in ServiceTitan to ensure the changes take effect.

Error: Export finished with errors. See Pending Export Report in ServiceTitan for more details

This issue occurs when the required reference account othercurrentliability is missing in QuickBooks Online (QBO). ServiceTitan relies on this account as a system reference during export, and without it, the export process cannot complete successfully.

To resolve the issue:

  1. In QuickBooks Online, go to Settings (gear icon) > Chart of Accounts.

  2. Create a new account named “othercurrentliability” — use all lowercase letters with no spaces.

  3. Set both the Account Type and Detail Type to Other Current Liabilities.

  4. No account number is required.

  5. You do not need to map any transactions or data to this account; it serves as a reference only.

  6. After creating the account, retry the export.

Error: You cannot change transaction which is 365 days or older

Contact ServiceTitan Technical Support if you receive this error.

Want to learn more?