Repository navigation
[NO QA] Docs updates for E/A#100885 Add GL code steps for dependent multi-level tags #102459
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
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 | ||||
|---|---|---|---|---|---|---|
| @@ -1,7 +1,7 @@ | ||||||
| --- | ||||||
| title: Create and Manage Expense Tags | ||||||
| description: Add tags to use for coding expenses. | ||||||
| keywords: [New Expensify, expense tags, class tracking, cost center, import tags, coding expenses, tag GL code, tag approver, tag rules, tag approval] | ||||||
| keywords: [New Expensify, expense tags, class tracking, cost center, import tags, coding expenses, tag GL code, multi-level tag GL code, dependent tag GL code, tag approver, tag rules, tag approval] | ||||||
| internalScope: Audience is Workspace Admins. Covers enabling, creating, importing, activating, and managing expense tags, including multi-level tags, tag GL codes, and tag approvers (Tag Rules) and how Tag/Category/workspace approvers combine in the approval chain. Does not cover personal expense rules or accounting system configuration. | ||||||
| --- | ||||||
|
|
||||||
|
|
@@ -105,7 +105,7 @@ Example: If you use single-level Tags for Department, members will see one field | |||||
|
|
||||||
| **Note:** | ||||||
| - With single-level Tags, you can edit or delete individual tags directly in the workspace. | ||||||
| - With multi-level Tags, you must update and re-import your spreadsheet to make changes. | ||||||
| - With multi-level Tags, you must update and re-import your spreadsheet to make changes. The exception is tag GL codes, which you can edit directly in the workspace. | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
|
|
@@ -157,12 +157,15 @@ When importing multi-level Tags, enable **These are independent tags** to import | |||||
|
|
||||||
| ## How to add or edit a tag GL code | ||||||
|
|
||||||
| Workspaces on the Control plan can assign a GL code to each tag for exporting purposes. By default, tag GL codes are not visible to members, but you can choose to show them in the tag picker. | ||||||
| Workspaces on the Control plan can assign a GL code to each tag for exporting purposes. This includes single-level tags and every level of dependent or independent multi-level tags. By default, tag GL codes are not visible to members, but you can choose to show them in the tag picker. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It would be helpful to call out exclusions, but there are no exclusions, so this added sentence is unnecessary. |
||||||
|
|
||||||
| 1. In the **navigation tabs** (on the left on web, and at the bottom on mobile), select **Workspaces** > **[workspace name]**. | ||||||
| 2. Select **Tags**. | ||||||
| 3. Select a tag to open its detail panel. | ||||||
| 4. Select the **GL Code** field, enter or update the code, then select **Save**. | ||||||
| 3. If you use multi-level tags, select the tag list for the level you want to update (for example: **State**, **Region**, or **City**). | ||||||
| 4. Select a tag to open its detail panel. | ||||||
| 5. Select **GL code**, enter or update the code, then select **Save**. | ||||||
|
|
||||||
| For dependent multi-level tags, each GL code is saved to the tag you selected under its parent tags. If the same tag name appears under different parents (for example: **Springfield** under both **Illinois** and **Missouri**), each one keeps its own GL code. | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
|
|
@@ -248,6 +251,10 @@ Multi-level tags are available on Control workspaces only. If your Control works | |||||
|
|
||||||
| By default, no. Tag GL codes are visible only to Workspace Admins. However, a Workspace Admin can turn on **Show GL codes when selecting a tag** in **Tags** > **More** > **Settings** to display each tag's GL code in the tag picker for members. If that setting is off, you can still include the GL code in the tag name (for example: `1001 - Marketing`). | ||||||
|
|
||||||
| ## Can I add GL codes to dependent multi-level tags? | ||||||
|
|
||||||
| Yes. Dependent multi-level tags support a GL code at each level, the same as independent multi-level tags. You can include GL codes in the adjacent columns when you import your spreadsheet, or edit a tag's **GL code** directly in the workspace. | ||||||
|
|
||||||
| ## Why isn't a GL code displayed for a tag? | ||||||
|
|
||||||
| If **Show GL codes when selecting a tag** is on but a tag has no GL code next to it, that tag doesn't have a GL code available in your accounting system. Add the GL code in your accounting system and sync the connection so it appears in Expensify. | ||||||
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.