Skip to main content

End of Day Errors - QuickBooks Desktop Sync

Distributor troubleshooting for QuickBooks Desktop sync errors at End of Day in Encompass: mismatched journal entries, invoice numbers over 20 characters, missing ListIDs, can't open QB file. v23.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 23.01

Pre-Conditions

Companies.GeneralAccountSystem = QuickBooks

Steps

Common QuickBooks Desktop Sync errors and how to troubleshoot them:

Journal Entry in Encompass Does Not Match QB Journal Entry:

  • This message appears when the sync detects a Journal No. in QuickBooks (Enc JE ID: ####) that matches a Journal Entry ID in Encompass (####) AND the Journal Entry amounts do not match

  • Ensure the Journal No. in QuickBooks is not being posted from another source (many QuickBooks integrations will take the most recent Journal No. and replicate it)

  • If the Journal Entry is from Encompass, ensure the Journal Entry in QuickBooks was not manually edited

  • Syncing to QuickBooks requires any validated Journal Entry match between both systems to prevent subledger discrepancies

  • Once the Journal Entry in QuickBooks is updated, run the sync client again

Quickbooks requires that the length of Purchases.InvoiceNum cannot exceed 20 characters:

  • This message appears due to a QuickBooks restriction on the length of an Invoice Number on a synced Purchase

  • Copy the PurchaseID(s) listed

  • Go to the Purchases table and select the PurchaseID(s) from the error message

  • Edit the Invoice Number on the Purchase(s) to be 20 or fewer total characters (including spaces)

  • Editing the Purchase(s) may require UnConfirming

  • Once all Purchases have been updated with the allowable length Invoice Number re-sync to QuickBooks

AccountID = # on JE #### has an empty string ListID:

  • This message appears when an Account in Encompass has not been synced to an Account in QuickBooks and Encompass cannot find an exact match (Accounts.Account, Accounts.QBAccountType)

  • If the Account listed does exist in QuickBooks, Encompass has already matched the QuickBooks Account with a different Encompass Account

  • Check similarly named Accounts in Encompass and clear the ListID field if this is a mismatch

  • If the Account listed does not exist in QuickBooks, create the Account in QuickBooks

  • Once the above step(s) have been completed, re-run the sync client

AccountID # is set as the Accounts Payable Account on APAccount ____ and is missing a ListID:

  • This message appears when an Account with AccountType = AccountsPayable in Encompass has not been synced to an Account in QuickBooks and Encompass cannot find an exact match

  • If the Account listed does exist in QuickBooks, Encompass has already matched the QuickBooks Account with a different Encompass Account

  • Check similarly named Accounts in Encompass and clear the ListID field if this is a mismatch

  • If the Account listed does not exist in QuickBooks, create the Account in QuickBooks

  • Once the above step(s) have been completed, re-run the sync client

Could not open QuickBooks File:

  • This message appears when the sync client cannot detect the QuickBooks file

  • Ensure your QuickBooks company file is open

  • In QuickBooks, press Ctrl + 1 to view the file path for your QuickBooks company file

  • In Encompass, go to the Companies table and compare the file path set in the Company File field to the file path displayed in QuickBooks

  • If these do not match, edit the Company File field to match the file path displayed in QuickBooks and then re-run the sync client

  • If these do match, re-run the sync client

  • If the same message appears, edit the Company File field to [none] and re-run the sync client with the QuickBooks company file open

Fields And Definitions

The system uses the following condition to sync the purchase to QB:

  1. APAccounts.CompanyID = Currenct select Company in QB

  2. Purchases.PostDate = New PeriodCloseDate of Company

  3. PurchaseAccounts.Debit <> 0 OR PurchaseAccounts.Credit <> 0

  4. Shipments.Status =Verified

  5. PurchaseAccounts.AccountID <> APAccounts.AccountsPayableAccountID

  6. Purchases.TxnID IS NULL

Did this answer your question?