ONL945 Export Error
ONL945 Export Error in QuickBooks Online
If you see the error:
ONL945: Vendor/supplier not found. The submitter’s email may be linked to another record in QuickBooks Online.
This means Expensify cannot match the report submitter to a vendor record in QuickBooks Online, usually because the email address is associated with another record.
Why the ONL945 Export Error Happens in QuickBooks Online
The ONL945 error occurs when:
- The vendor record Expensify is attempting to locate uses an email address that is already associated with another record in QuickBooks Online.
- Multiple records (such as vendor and employee) share the same email address.
- QuickBooks Online cannot determine which record to use during export.
Expensify relies on exact email matches to identify vendor records during export.
How to Check for Duplicate Email Records in QuickBooks Online
- Log in to QuickBooks Online.
- Use the global search bar at the top of the screen.
- Search for the report creator or submitter’s email address.
- Review all records returned (vendor, employee, customer, etc.).
- Identify any duplicate records using the same email address.
- Remove or deactivate duplicate entries as appropriate.
- Save your changes.
After cleaning up duplicate records, refresh your connection in Expensify.
How to Sync QuickBooks Online in Expensify
On Web
- Go to the Workspaces navigation tab on the left.
- Select your Workspace.
- Click Accounting.
- Click the three-dot icon next to the QuickBooks Online connection.
- Select Sync now.
On Mobile
- Tap the Workspaces navigation tab on the bottom.
- Select your Workspace.
- Tap Accounting.
- Tap the three-dot icon next to the QuickBooks Online connection.
- Tap Sync now.
Once the sync completes, retry exporting the report.
FAQ
Does the Vendor Email Have to Be Unique in QuickBooks Online?
Yes. The email address used to match vendors during export should only be associated with one active record in QuickBooks Online.
Do I Need to Reconnect QuickBooks Online?
No. In most cases, removing duplicate records and running Sync now resolves the issue.