The Error Transactions page in Alvys provides a centralized overview of both transactions that failed to sync with your external accounting system and transactions that have yet to be pulled in by the QuickBooks Web Connector. This page allows users to quickly identify failed exports, examine detailed error messages, and take the necessary corrective actions. You can access this page from the “Accounting” menu by selecting Error Transactions within Alvys.

Not all transactions can be automatically re-synced from this page. Currently, only the following entity types can be re-synced:

Use Sync All Transactions only if all transactions in the Error Transactions list are ready for export. Any transactions that still require corrections will be skipped.

For carrier settlements, summary invoices, and driver pay, corrections and re-syncs must be performed directly from their respective pages rather than from the general Error Transactions page.

If a transaction has been manually corrected in the external accounting system and no longer requires action in Alvys, it can be cleared from the Error Transactions page:

Only mark a transaction as synced if it has been fully resolved, as this action cannot be undone.

This section provides a comprehensive overview of the most frequently encountered errors within the QuickBooks Desktop (QBD) integration, covering both Web Connector Errors that prevent communication and Export and Sync Errors that occur during data transfer.

This QuickBooks Web Connector (QBWC) error occurs when you attempt to add an Alvys Web Connector (.QWC) file to a QuickBooks Desktop (QBD) company file that already contains a "registration" for that specific application. When you first link Alvys to QuickBooks by adding the application to the connector, a unique set of IDs is written into the "brain" (metadata) of your company file (QWC). If you try to add the application again without properly removing the original registration first, QuickBooks blocks the action to prevent data corruption, such as duplicate invoices or double-posted payments.

To understand the fix, you must understand the relationship between these three (3) components:

The Two Key Identifiers:

Inside the Alvys Web Connector File. QWC instruction file are two unique "ID Tags" that QuickBooks uses to verify the connection.

When a user encounters a sync issue and thinks, "I'll just start over," they often click "Remove" on the Alvys line inside the QuickBooks Web Connector (QBWC) program. Clicking "Remove" in the Web Connector only deletes the Scheduler (the clock that tells the sync when to run). It does NOT scrub the internal ID registry from the actual QuickBooks Desktop (QBD) company file. When you "Add an application," the Messenger (Web Connector) hands these two ID tags to the Vault (QuickBooks Desktop), the Vault looks at its internal security list and says: "I already have a record for this Alvys OwnerID and this FileID. Since I already have a record on file for this app, I won't let you add it again as a new connection."

The QuickBooks Web Connector (QBWC) CP3 Tool is an official utility developed by Intuit to perform a "surgical strike" on the internal database of your QuickBooks company file. It targets the "OwnerID Stamp" hidden in the metadata of your file and erases it entirely, removing the app from the company registry.

This method involves manually editing the QuickBooks Web Connector Configuration file (.QWC) to assign it a new digital identity. By altering the unique identifiers (GUIDs), you bypass the "Error 1039" conflict, allowing QuickBooks to recognize the integration as a fresh, separate application rather than a duplicate of a previously installed one.

To avoid QuickBooks Web Connector (QBWC) Error 1039 in the future, follow these "Golden Rules" whenever you move, rename, or reset your Alvys connection.

If you ever need to "start over" with your Alvys connection, you must delete the old connection in two separate places. If you only do one, QuickBooks will block the new attempt as a "duplicate."

The Web Connector Program

If you only remove the app from the Web Connector, the QuickBooks Company File still thinks it is registered to Alvys. When you try to add Alvys again, QuickBooks sees the ID, checks its memory, and says: "I already have a record for this; I won't allow a second one."

If you are moving your QuickBooks file to a new computer/server or renaming your file (e.g., changing Trucking_2025.qbw to Trucking_2026.qbw), you must "sign out" first.

Before you move the file or rename it, open the Web Connector on the old computer (or using the old file name). 2. Click Remove on the Alvys line. 3. Confirm with Yes.

QuickBooks links the Alvys connection to the specific computer name and file path. If you move the file without "signing out" first, the new computer is treated as an "unauthorized intruder" when it tries to use the same Alvys ID.

Never try to use the same Alvys QWC file for two different QuickBooks company files. Every QuickBooks file has its own hidden "Identity Badge" (FileID). An Alvys connection file is a "Custom Key" meant for only one badge. If you try to use one key for two different badges, QuickBooks will detect the mismatch and trigger a security error.

This version of Error 1039 occurs when the QuickBooks Web Connector (QBWC) tries to sync with QuickBooks Desktop (QBD), but QuickBooks denies the request because the digital permissions have been revoked, changed, or were never fully granted.

Think of this as an expired security badge. The Messenger (Web Connector) shows up at the Vault (QuickBooks) with an ID badge that says "Alvys." The Vault looks at the badge and says:

"I recognize this badge, but your access has been suspended. I cannot let you in to see the data until the Administrator re-authorizes your clearance”.

This specific error is usually triggered by one of the following "Security Blockades":

This is the most common fix. You need to tell the "Security Guard" that Alvys is allowed back in.

If Option 1 doesn't work, the "Security Badge" is likely corrupted and needs to be replaced.

This error occurs when QuickBooks can't successfully connect application through the QuickBooks Web Connector. When an integration is being added, Inside QuickBooks Desktop an Application Certificate prompt must be displayed, this is how it asks you to authorize the app's access to your data. If no company file is open at the time of setup, QuickBooks has no context to attach that authorization to, and the process fails before the permission dialog ever appears. This can also happen if the location of the company file was moved or if you aren't on the newest release of QuickBooks.

Make sure each version of QuickBooks on your system are on the newest release. If you've uninstalled a newer version of QuickBooks than you currently use, you may need to reinstall and update the newer product to the newest release. QuickBooks products are dependent on the latest version you installed.

Example: You upgrade from QuickBooks 2020 to QuickBooks 2021. You decide not to use QuickBooks 2021 and use QuickBooks 2020. You'll need to install QuickBooks 2021 and update it to the newest release. You do not need to use the program, but it needs to be installed and updated.

This error occurs when the QuickBooks Web Connector is unable to verify the status of an integration because the QuickBooks Company File is not accessible. To safely remove an application, the Web Connector must perform a final communication with the specific company file to de-authorize the connection. If the file is not open, or if the Web Connector cannot find it at its original location, the removal process is blocked.

The Company File is Closed: The Web Connector cannot send the "Remove" command if QuickBooks is closed or sitting on the "No Company Open" screen.

File Path Mismatch: This happens if the company file has been moved to a new folder or server drive since the integration was first added. The Web Connector is still looking for the file at the old directory path shown in the error message.

The File has been Renamed: Even a slight change to the filename (e.g., adding "2026" to the end) causes the Web Connector to believe the "Vault" is missing, as it only recognizes the exact original filename.

To fix this, you must ensure the connection between both programs is active and synchronized.

This error occurs when the Web Connector and QuickBooks company file are in different file directories. It typically surfaces after a company file has been moved or when the Web Connector is being run on a different machine than the one where the company file is hosted.

Locate your company file: Open QuickBooks Desktop and press F2 or Ctrl + 1 on your keyboard. The product information window will display the full folder path of your QuickBooks Desktop company file under the File Information field. Make a note of this location.

Make sure the Web Connector is running from the same directory as the company file

This error occurs when a user who does not have Administrator rights attempts to add a .QWC file to the Web Connector. During the application setup, QuickBooks needs to display an Application Certificate window so the Administrator can grant the app permission to access the company file. Without Administrator access, this window cannot be completed, and the application will not be added to the Web Connector.

Close the Web Connector If the Web Connector is currently open, close it before proceeding.

Open QuickBooks and sign in as Administrator Launch QuickBooks Desktop and sign in using an Administrator account. If QuickBooks is running in Multi User Mode, go to File > Switch to Single User Mode. Administrator access in Single User Mode is required to complete the application authorization.

Reopen the Web Connector and add the .QWC file With QuickBooks open and signed in as Administrator, go to File > App Management > Update Web Services to launch the Web Connector directly.

Add the .QWC file Inside the Web Connector, select File > Add Application and locate your QWC configuration file. Select it to begin the authorization process.

Complete the Application Certificate QuickBooks will now present the Application Certificate window. Select "Yes, whenever this QuickBooks company file is open" and click Continue. In the Access Confirmation window that follows, click Yes to grant the application access to your company file. The application will now appear in the Web Connector ready to sync.

Error Code: 3140

This error occurs when QuickBooks receives a transaction from Alvys that references a name already in use elsewhere in the company file. QuickBooks does not allow duplicate names across customers, vendors, and employees. This means if "Alvys Foods" exists as a Vendor, it cannot also exist as a customer, and vice versa. Any overlap across these three lists will cause the transaction to fail.

Error Variations

Variation 1: Invalid Customer Reference "There is an invalid reference to QuickBooks Customer 'Alvys Foods' in the Invoice. QuickBooks error message: The specified name is either invalid or of the wrong type."

Variation 2: Invalid Vendor Reference "There is an invalid reference to QuickBooks Vendor 'Alvys Foods' in the Invoice. QuickBooks error message: The specified name is either invalid or of the wrong type."

Step 1. Identify the duplicate in QuickBooks Open QuickBooks Desktop and search for the name referenced in the error message. Check across your Customer, Vendor, and Employee lists to find where the name appears more than once or under the wrong entity type.

Step 2. Resolve the duplicate You have two options depending on your situation.

Option A: Rename the duplicate Open the conflicting entry in QuickBooks and update the name to make it unique across all lists. For example, renaming "Alvys Foods" to "Alvys Foods - Customer" will distinguish it from any other entry sharing that name.

Option B: Delete the duplicate If the conflicting entry is no longer needed, delete it from QuickBooks to remove the conflict entirely.

Step 3. Retry the transaction in Alvys Once the conflict has been resolved in QuickBooks, go to the Error Transactions page in Alvys and locate the failed transaction. Right-click on it and select Sync to retry the export. Then open the Connector and select Update Selected to push the transaction through to QuickBooks Desktop.

Error Code: 3070

Error Shown in Error Transaction:

Error Message: "The string '[transaction ID]' in the field 'EditSequence' is too long."

This error occurs when a transaction that was originally zero-valued, for example a customer invoice with a total of $0, is later updated to an amount greater than $0 and Alvys attempts to export it to QuickBooks Desktop. If the Ignore Zero Valued Transactions setting was previously enabled in Alvys, the original $0 transaction may have been skipped entirely and never exported to QuickBooks. When the transaction is later updated to a non-zero value, QuickBooks has no record of the original transaction to reference, causing it to generate an error related to the transaction's internal ID. This prevents the updated transaction from exporting successfully.

Step 1. Identify the affected transaction In Alvys, locate the transaction that was originally $0 and has since been updated to a non-zero value.

Step 2. Contact Alvys Support This error cannot be resolved manually and requires assistance from the Alvys Support team. Send an email to Alvys Support with the following information:

Q: Does appearing on the Error Transactions page always mean my sync failed? A: No. Because QuickBooks Desktop relies on the Web Connector to pull data, all transactions are initially shown here in a queued (-) state. This simply means the transaction is waiting for the Web Connector to run. It only counts as a failure if an actual error message appears after the sync cycle is complete.

Q: Where can I find the specific reason a transaction failed to export?

A: On the Error Transactions page, look for the Error Message or Details column. Alvys displays the exact response sent by the QuickBooks Web Connector, which will identify the missing account, duplicate name, or permission issue causing the hold-up.

Q: Which Alvys transactions can I re-sync directly from the Error Transactions page?

A: Currently, the following entity types support direct re-syncing: Loads, Trips, E-checks, and Paystubs.

Q: What should I do if I see a "Duplicate Name" error?

A: QuickBooks requires every Customer, Vendor, and Employee to have a completely unique name. If you receive this error, check if the External Accounting Name in Alvys already exists in another list in QuickBooks (for example, a customer name that is already saved as a vendor). You must make the name unique in either Alvys or QuickBooks and then re-sync.

Q: How do I re-send a transaction after I have fixed the error?

A: Once you have corrected the data (such as mapping a missing account or fixing a name), go to the Error Transactions page, select the checkbox for the specific transaction, and click Retry or Re-sync. Then, open your QuickBooks Web Connector and click Update Selected to process the fix.

Q: Why do my transactions stay in "Queued" status even after I run the Web Connector?

A: This typically happens if the wrong QuickBooks Company file is open or if the Web Connector is not selected to "Auto-Run." Ensure you are logged into the correct .QBW file as an Admin and that the checkbox for the Alvys application is checked within the Web Connector window.

Q: What is an "Edit Sequence" error and how do I fix it?

A: This error occurs when a transaction has been modified in both Alvys and QuickBooks, causing the systems to lose track of which version is current. To resolve this, you must contact Alvys Support, as they will need to manually reset the sequence ID to allow the sync to proceed.

Q: Can I remove a failed transaction from the Error Transactions page if I don't want to sync it?

A: Yes. If you do not intend to sync a transaction, for example, if you manually entered it into QuickBooks, you can select the transaction and choose Mark as Synced. This removes it from the error list and tells Alvys that the record has been handled, preventing it from remaining in the export queue.