Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -161,4 +161,12 @@ Yes. The QuickBooks Desktop integration is available on the **Control** plan.
* **Tags**: Applied at the individual expense level, allowing different expenses on the same report to have different values
* **Report fields**: Applied at the report level, meaning all expenses on a report share the same value

## Can I export to an employee record instead of a vendor record?

You can export to an employee record when exporting reports as **Journal Entries** or **Checks**.

By default, we'll look for a vendor record with an email address matching the report submitter. If we don't find one, we'll look for an employee record. Employees must have a **Main Email** in QuickBooks Desktop that matches the email associated with their Expensify account.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style consistency: This paragraph uses first-person "we'll" three times (lines 168 and 170), but the rest of the article's FAQ answers use "Expensify" as the subject (e.g., line 137: "Expensify will display an alert...") or passive constructions. For consistency, rephrase to use "Expensify" or passive voice.

Suggested rewrite:

By default, Expensify looks for a vendor record with an email address matching the report submitter. If no match is found, Expensify looks for an employee record. Employees must have a Main Email in QuickBooks Desktop that matches the email associated with their Expensify account.


If there is no vendor or employee record and **Auto-create entities** is enabled, we'll create a new vendor record for the submitter.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style consistency: Same first-person "we'll" issue. Consider: "If there is no vendor or employee record and Auto-create entities is enabled, Expensify creates a new vendor record for the submitter."



Loading