What we do
Tools
Industries
Department
How we workLet's talk →
Home/Expensify/Expensify QuickBooks Integration
Expensify + QuickBooks

The Expensify QuickBooks Integration: Picking an Export Type, and Fixing the Ones That Fail

The report is approved, and QuickBooks either gets a clean, coded bill or an error code nobody recognizes. Expensify's own connection to QuickBooks Online and QuickBooks Desktop decides most of that through two settings: the export type, and how your classes and customers come across as tags.

Expensify to QuickBooks, in four lines

It's native, for both versions. QuickBooks Online connects directly. QuickBooks Desktop connects through the QuickBooks Web Connector. In New Expensify the settings sit under Import, Export and Advanced.

Workspaces your workspace Connections Configure

What comes in: the chart of accounts as categories (always on), classes and customers/projects as tags, plus locations, tax rates, and items that have purchasing information.

What goes out: each approved report as one itemized vendor bill, check or journal entry. Company card spend goes as credit card or debit card charges, or as a vendor bill.

One company file per workspace. A second QuickBooks company means a second Expensify workspace.

Which QuickBooks export type suits your reports

Out-of-pocket reports take one of the first three. Company cards take the last row or a vendor bill.

Export as Lands in QuickBooks as Worth knowing
Vendor bill (Expensify's recommended choice) One itemized bill per report, on your A/P account, with the employee as the vendor. Billable lines carry their customer. A bill dated in a closed period posts on the first day of the next open one. With Sync Reimbursed Reports on, an ACH reimbursement in Expensify marks the bill paid in QuickBooks.
Check One itemized check per report, from a bank account. Billable lines carry over here too. In QuickBooks Online you can mark the check to print later.
Journal entry One itemized journal entry per report. Not allowed while tax is on, and journal entries don't carry the project field, so projects won't come across.
Credit or debit card (company cards) Individual card transactions on the card's account. Set a default vendor, or New Expensify posts them to a "Credit Card Misc" or "Debit Card Misc" vendor. The Expensify Card always exports as credit card charges.

The Expensify export errors that keep coming back

A category, class or vendor QuickBooks no longer has

How you'll know: The export fails after someone renamed, merged or deleted an account, class or vendor on the QuickBooks side.

Fix: Sync the connection so Expensify refreshes its lists, recode the report against the current names, and export again. If two vendor records should be one, merge them in QuickBooks first. Auto-create entities lets Expensify add a missing vendor on export instead of failing.

Journal entries picked while tax is on

How you'll know: Reports won't export, and Expensify shows error ONL939.

Fix: Switch the out-of-pocket export type to vendor bill or check, which both carry tax.

Auto Sync is on, and older reports are still sitting there

How you'll know: Reports approved before you turned Auto Sync on never reached QuickBooks.

Fix: Only reports approved after that point export on their own. Export the backlog by hand, once. Exporting a report a second time creates a duplicate in QuickBooks, and Expensify warns you before it does.

A foreign-currency report lands at a figure you don't recognize

How you'll know: The amount in QuickBooks doesn't match the report total in your home currency.

Fix: QuickBooks doesn't apply a conversion rate on export, and vendor bills go out in the vendor's currency. Adjust the rate after export. Generally the treatment of the difference is your accountant's call, so check it with them.

QuickBooks Desktop shows nothing new

How you'll know: A day of approvals in Expensify, and the company file hasn't changed.

Fix: Desktop only syncs while QuickBooks Desktop and the Web Connector are both open, and only the company file tied to that workspace should be open during the sync. Run Sync Now once both are up.

When one workspace and a class field run out

The native connection assumes one company file and a coding scheme QuickBooks can hold: a category, a class, a customer or project. A group with three entities, or a contractor costing every job by phase and cost code, outgrows that. Then someone moves people between workspaces by hand, recodes lines in QuickBooks after each export, or keeps job detail in a spreadsheet beside both.

n-frames builds the layer around the connector, on Expensify's Integration Server API. Each employee is placed in the workspace for their entity from your HR records, so their reports start in the right company file. Job and phase codes are pushed into Expensify as tags from the system that owns them, so employees code against a current list. Detail QuickBooks has no field for stays in your job-costing tool, matched to the bill the export created. On the QuickBooks side, see billable expenses and adding a class.

Expensify and QuickBooks, setting by setting

Does Expensify integrate with QuickBooks Online and QuickBooks Desktop?

Yes, both, as separate connections set up from the workspace. QuickBooks Online connects directly. Desktop runs through the QuickBooks Web Connector on the computer that holds the company file, so it only syncs while QuickBooks and the Web Connector are open.

What does Expensify export to QuickBooks?

Approved reports, each as one itemized vendor bill, check or journal entry, depending on the export type you set. Company card spend exports as credit or debit card transactions, or as a vendor bill, and invoices go to the account you choose. Each line is coded with the categories, classes and customers Expensify imported from QuickBooks.

Can I sync Expensify with more than one QuickBooks company file?

Not from one workspace. Each workspace connects to a single company file, so a group with several entities runs one workspace per company. Getting each person's reports into the right one is then a setup someone does by hand, or one n-frames builds from your HR or org data.

Why did my Expensify export to QuickBooks fail?

Usually a mismatch: a category, class, customer or vendor on the report that QuickBooks no longer has under that name. Journal entries with tax turned on fail too, and on Desktop so do syncs with the Web Connector closed or the wrong company file open. The error code Expensify shows matches a help article for that exact error.

Does Auto Sync export reports to QuickBooks by itself?

Yes, once it's on. Expensify Classic's help says it runs daily, refreshes accounts, customers and vendors, exports non-reimbursable reports at final approval, and exports reimbursable ones after they're reimbursed. Reports approved before you switched it on wait until you export them.

Where do job costs go when QuickBooks classes aren't enough?

Into the system that already tracks jobs, matched back to the QuickBooks bill. n-frames writes that link: job and phase codes fed into Expensify as tags, and the extra detail kept in your job-costing tool against each exported report.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.