Error Creating Vendor exporting to QBO
I processed a report, and it paid with Expensify with ACH. When I try to export to Quickbooks Online, I get an error saying "Error Creating Vendor, A vendor with the same name already exists in QuickBooks Online." It links to https://docs.expensify.com/quickbooks-online-error-creating-vendor which says to change the export method to check/journal entry. I tried both check and journal entry, and got the same error message. QBO doesn't want to create a vendor with the same name as the employee when I do it manually.
How do I get this sync to work?
Best Answer
-
@davidjs - Can you confirm that you have the employee record setup for the employee with the same email they use in Expensify in the main email field?
Answers
-
Hey @davidjs, thanks for posting to the Community!
To clarify, are you getting an error message when trying to create a vendor that matches the user's email address in QuickBooks? If yes, can you share the error message?
Thanks!
-
I am having the same problem
Error Creating Vendor
A vendor with the same name already exists in QuickBooks Online. -
My goal was to change the Expensify settings and not have to create a vendor on the Quickbooks Online side. According to the troubleshooting guide, "either change your reimbursable export method to a check/journal entry or add a second record for your employee as a vendor," this should be possible. Based on that page, it should be possible to export by changing the export method, and that isn't working. When I change the export method and click "Export" again on the report, I get the same error.
The error message I am getting from Expensify is basically what is shown on the troubleshooting page.
-
@davidjs -- Hi there, so that I'm sure, did you sync the connection after changing the export type to Journal Entry and before trying to export again? If so, can you also confirm if the report submitter has an employee record created for them in QuickBooks with the same email they use in Expensify?
If so, just let me know!
-
@Sheena Trepanier The issue was the lack of matching employee record. Once I created that on the Quickbooks side, the export worked. Until I did that, any amount of changing export type and syncing the connection didn't change the error message.
Thanks for your help! -
Thanks so much for letting me know @davidjs, I'm really glad this is working for you now. I hope you have a great weekend, take care!
