-
Notifications
You must be signed in to change notification settings - Fork 4k
[No QA] Docs updates for E/A#96407 Document importing merchant rules via spreadsheet #96544
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
+76
−0
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e08924e
Docs: document importing Merchant Rules via spreadsheet
MelvinBot 353c3e9
Docs: direct Rules Revamp users to Expense defaults tab before import
MelvinBot eea17b5
Docs: state mobile import support directly in Merchant Rules FAQ
MelvinBot 82f31c7
Docs: align navigation phrasing with helpsite convention
MelvinBot 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
75 changes: 75 additions & 0 deletions
75
docs/articles/new-expensify/workspaces/Import-Merchant-Rules.md
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,75 @@ | ||
| --- | ||
| title: Import Merchant Rules using a spreadsheet | ||
| description: Learn how to bulk-create Merchant Rules by importing a spreadsheet, and how Tag values are interpreted for single-level and multi-level tags. | ||
| keywords: [New Expensify, import merchant rules, merchant rules spreadsheet, bulk merchant rules, import rules CSV, workspace rules, multi-level tags import] | ||
| internalScope: Audience is Workspace Admins on the Control plan with Rules enabled. Covers bulk-creating Merchant Rules by importing a spreadsheet and how Tag cells are interpreted for single-level and multi-level tags. Does not cover creating Merchant Rules manually, personal expense rules, or importing tags themselves. | ||
| --- | ||
|
|
||
| # Import Merchant Rules using a spreadsheet | ||
|
|
||
| Importing a spreadsheet lets Workspace Admins create many Merchant Rules at once instead of adding them one at a time. Map each column in your file to a merchant rule field, and Expensify creates a rule for every row so matching expenses are automatically coded. | ||
|
|
||
| --- | ||
|
|
||
| ## Who can import Merchant Rules | ||
|
|
||
| To import Merchant Rules, you must be: | ||
|
|
||
| - A Workspace Admin. | ||
| - On a workspace with **Rules** enabled (available on the Control plan). | ||
|
|
||
| If **Rules** is not enabled, [learn how to enable Workspace Rules](/articles/new-expensify/workspaces/Workspace-Rules#enable-workspace-rules). | ||
|
|
||
| --- | ||
|
|
||
| ## How to import Merchant Rules using a spreadsheet | ||
|
|
||
| Prepare a spreadsheet where each row is one rule. Include a column for the merchant to match and a column for each field you want the rule to update (for example, Tag). | ||
|
|
||
| 1. In the navigation tabs (on the left on web, and at the bottom on mobile), click **Workspaces > [workspace name]**. | ||
| 2. Click **Rules**. | ||
| 3. Click **More**, then select **Import merchant rules**. | ||
|
NicolasBonet marked this conversation as resolved.
Outdated
|
||
| 4. Upload your spreadsheet file. | ||
| 5. Map each column to a merchant rule field. Map the merchant column to **Merchant is** or **Merchant contains**, and map at least one field to update, such as **Updated merchant**, **Updated category**, **Updated tag**, or **Updated description**. | ||
| 6. Click **Import**. | ||
|
|
||
| <!-- SCREENSHOT: | ||
| Suggestion: The column-mapping screen with a spreadsheet column mapped to Merchant is and another mapped to Updated tag. | ||
| Location: After step 5. | ||
| Purpose: Confirms admins are on the correct mapping screen and shows how to pair a spreadsheet column with a specific merchant rule field, which is the step most likely to cause confusion. | ||
| --> | ||
|
|
||
| You must map at least one **Merchant is** or **Merchant contains** column plus at least one field to update, or the import can't complete. | ||
|
|
||
| --- | ||
|
|
||
| ## How Tag values are interpreted when importing Merchant Rules | ||
|
|
||
| How a colon in a Tag cell is read depends on how your workspace tags are set up **at the time of import**, so set up your tags before importing. Learn more about [expense tags](/articles/new-expensify/workspaces/Create-and-manage-expense-tags). | ||
|
|
||
| - **Workspace with multi-level tags:** A colon separates tag levels. A Tag cell of `Parent: Child` is imported as a multi-level tag with the first level set to `Parent` and the second level set to `Child`. Any spaces around the colon are trimmed. | ||
| - **Workspace with a single-level tag list:** A colon is part of the tag name. A Tag cell of `ab:cd` is imported as one tag named `ab:cd`. | ||
|
|
||
| --- | ||
|
|
||
| ## What happens after you import Merchant Rules | ||
|
|
||
| - A confirmation message shows how many Merchant Rules were added. | ||
| - Rules that duplicate an existing rule are skipped. | ||
| - Each new rule appears in the **Merchant** section of the **Rules** page and is applied to matching expenses going forward. | ||
|
|
||
| --- | ||
|
|
||
| # FAQ | ||
|
|
||
| ## Why did some rows not import as Merchant Rules? | ||
|
|
||
| A row is skipped when it duplicates an existing rule, or when the required columns aren't mapped. Make sure you mapped a **Merchant is** or **Merchant contains** column plus at least one field to update. | ||
|
|
||
| ## Why did my imported Tag value display differently than expected? | ||
|
|
||
| Tag cells are interpreted based on your workspace tag setup at the time of import. On a workspace with multi-level tags, a colon splits the value into tag levels; on a workspace with a single-level tag list, the colon stays part of the tag name. Set up your tags before importing so the values are read the way you intend. | ||
|
|
||
| ## Can I import Merchant Rules on mobile? | ||
|
|
||
| Importing a spreadsheet is done from the **Rules** page. For the best experience uploading and mapping a spreadsheet, use Expensify on web. | ||
|
NicolasBonet marked this conversation as resolved.
Outdated
|
||
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.