-
Notifications
You must be signed in to change notification settings - Fork 4k
[No QA] Create Manage-Vendor-Matching-for-Xero.md #100458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,78 @@ | ||
| --- | ||
| title: Manage Vendor Matching for Xero | ||
| description: Learn how Xero vendor matching assigns contacts to non-reimbursable company card expenses before they export as bank transactions, including automatic matching and manual selection. | ||
| keywords: [Xero, vendor matching, vendor, contacts, suppliers, company card expenses, bank transactions] | ||
| internalScope: Audience is workspace admins using the Xero connection. Covers imported Xero contacts, automatic and manual vendor assignment, and how vendors are assigned when company card expenses export as bank transactions. Does not cover Xero connection setup or other export types. | ||
| --- | ||
|
|
||
| # Manage Vendor Matching for Xero | ||
|
|
||
| Xero vendor matching lets workspace admins review and update the vendor assigned to non-reimbursable expenses before they export to Xero as bank transactions. Expensify imports eligible contacts from Xero, automatically matches vendors where possible, and lets admins set or update the **Vendor** field before export. This helps ensure expenses export with the correct vendor instead of requiring manual corrections in Xero. | ||
|
|
||
| ## Who can use Xero vendor matching | ||
|
|
||
| This feature is available to workspace admins whose workspace is connected to Xero. | ||
|
stephanieelliott marked this conversation as resolved.
|
||
|
|
||
|
stephanieelliott marked this conversation as resolved.
|
||
| If your workspace isn't connected to Xero yet, [learn how to connect to Xero](/articles/new-expensify/connections/xero/Connect-to-Xero). | ||
|
|
||
| --- | ||
|
|
||
| ## How Xero contacts are available for vendor matching | ||
|
|
||
| Expensify imports and stores Contacts from Xero for vendor matching. | ||
|
|
||
| Contacts marked as Customers are excluded _unless_ they are also marked as Suppliers. This means the **Vendor** list includes contacts that are marked as both Customers and Suppliers. | ||
|
|
||
| Contacts marked as Customers but not Suppliers aren't available for vendor matching. | ||
|
|
||
| --- | ||
|
|
||
| ## How vendors are matched to non-reimbursable expenses | ||
|
|
||
| Expensify assigns vendors automatically in the following order: | ||
|
|
||
| - If a workspace merchant rule specifies a vendor, that vendor is assigned. | ||
| - Otherwise, Expensify automatically matches the merchant name against your Xero vendor list. For example, **STARBUCKS #456 DOWNTOWN** matches **Starbucks**. | ||
| - If no match is found, the **Vendor** field remains empty until a workspace admin selects one. | ||
|
|
||
| Whenever a vendor is assigned automatically, Concierge posts a system message on the expense indicating whether the vendor was set by a merchant rule or by vendor matching. | ||
|
|
||
| Workspace admins can manually select a vendor from the searchable **Vendor** field on an expense at any time. Once a vendor is selected manually, Expensify preserves that selection and won't overwrite it with automatic matching. | ||
|
|
||
| --- | ||
|
stephanieelliott marked this conversation as resolved.
|
||
|
|
||
| ## How to set a fallback (default) vendor for non-reimbursable expenses | ||
|
|
||
| 1. In the navigation tabs (on the left on web, on the bottom on mobile), go to **Workspaces > [workspace name]**. | ||
| 2. Select **Accounting**. | ||
| 3. Under **Xero**, select **Export**. | ||
| 4. Select **Default vendor**. | ||
| 5. Choose a vendor from the list. | ||
|
|
||
| The default vendor is used only when an expense doesn't already have a vendor assigned. If no default vendor is configured, expenses export to the vendor **Credit Card Misc**. | ||
|
|
||
| --- | ||
|
|
||
| # FAQ | ||
|
|
||
| ## Do I have to set a vendor for a non-reimbursable expense? | ||
|
|
||
| No. The **Vendor** field is optional. | ||
|
|
||
| Expensify automatically attempts to match a vendor using eligible contacts imported from Xero. If no match is found, the field can remain blank. | ||
|
|
||
| ## Which Xero contacts appear in the Vendor field? | ||
|
|
||
| Expensify imports Xero contacts and excludes contacts that are marked as Customers unless they're also marked as Suppliers. | ||
|
|
||
| A contact marked only as a Customer won't appear in the **Vendor** field. A contact marked as both a Customer and a Supplier can appear. | ||
|
|
||
| ## Who can see the Vendor field on an expense? | ||
|
|
||
| Only workspace admins can view and edit the **Vendor** field. Members and submitters don't see it. | ||
|
|
||
| ## Does manually assigning a vendor stop automatic matching? | ||
|
|
||
| Yes. Once a workspace admin manually assigns a vendor to an expense, Expensify preserves that selection and won't replace it with automatic matching. | ||
|
|
||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.