FAQ - ExpensiError QBO088: Error Creating Vendor

Alejandro Paz

ExpensiError QBO088: Error Creating Vendor, "A vendor with the same name already exists in QuickBooks Online", means you have an Employee Record set up with the employee's name, which prevents the Expensify integration from automatically creating the Vendor Record with the same name, since QuickBooks Online won't allow you to have an employee and vendor with the same name. 

Option 1:

You can access the Employee Records for your submitters in QBO and edit the name to differentiate them from the name they have on their account in Expensify, then sync your connection in Expensify via Settings > Policies > [policy name] > Connections > Sync Now (under QBO). Finally, try exporting your report(s) again, at which point we should be able to successfully create the associated vendor(s). 

Option 2:

Alternatively, you can create all of your Vendor Records manually, making sure that the email matches the email address associated with the user in Expensify.

In this case, we recommend disabling Automatically Create Vendors under Settings > Policies > [policy name] > Connections > Configure > Advanced, so that you will receive the correct error messages when a vendor record doesn't exist.

Related Articles

• FAQ - QuickBooks Desktop: The Wrong QuickBooks Company is Open
• FAQ - QuickBooks Desktop: Please Close Any Dialog Boxes Open Within QuickBooks
• FAQ - QuickBooks Online: Where Can I Find My Expenses?
• FAQ - QuickBooks Online: Your Payee is Showing as 'Credit Card Misc.'
• FAQ - QuickBooks Online: Why Can't I Export Without a Category Selected?
• FAQ - QuickBooks Online: Exporting Negative Expenses
• How-to: 3-way connection with Bill.com and QBO, Sage Intacct, Xero, NetSuite
• Deep Dive: Expensify Card and QuickBooks Online Auto-Reconciliation: How it works!

gherkert

Should this help someone else in the future, I was having this issue. I didn't have an Employee record or a Vendor record. It was the latter that was the issue.

I created a Vendor record with my email address and that solved this error.

Zany Renney

Thanks @gherkert for that tip! Great to hear it resolved the error for you.

Thanks for being part of the community.