Repository navigation
Description
Background
R1 centralized existing card and expense-default rules. Today, however, several common rules are created from the Categories settings (e.g. "require itemized receipt for Meals and Entertainment", "flag for review when category is X and amount is above Y"). That split keeps Rules from being the single source of truth.
This release moves that category-driven creation into the centralized Rules experience by adding two new custom rule types — Require fields and Flag for review — to both the Rules page (as new tabs) and the universal creation flow. After this release, the four creation options are Restrict card spend, Flag for review, Require fields, and Apply expense defaults.
Scope
- Add
Require fieldsas a new rule type, with its own tab and creation branch. - Add
Flag for reviewas a new rule type, with its own tab and creation branch. - Each new type has its own table tab and its own empty state (to anticipate, no mock yet).
- Extend the
New ruleflow to four options. - Add 12 default merchant-type categorization rules to
Expense defaults, with a Merchants / Merchant types subsection split.
Product and design details
New rule type: Require fields
- Table columns: Type (Require pill), Condition (e.g. Category is "Meals and Entertainment"), Rule (e.g. Require itemized receipt). Click a row opens it's edit flow.
- Empty state: When no expense default rules exist, we'll show an empty state with a short heading ("Catch missing details upfront") and supporting copy ("Make sure key fields are filled in before expenses are submitted."), which explain what require fields do and a primary CTA to create the first rule (routes into
Require fieldsbranch of the creation flow).
New rule type: Flag for review
- Table columns: Type (Flag pill), Condition (e.g. "Category is Meals and Entertainment and amount above …"), Rule (Flag for review). Click a row opens it's edit flow.
- Empty state: When no flag rules exist, we'll show an empty state with a short heading ("Surface expenses that need a closer look") and supporting copy ("Alert approvers when specific expenses are worth an extra review."), which explain what require fields do and a primary CTA to create the first rule (routes into
Flag for reviewbranch of the creation flow).
Default merchant-type categorization in Expense defaults
This release adds a set of default merchant-type categorization rules to the Expense defaults tab. These map an incoming merchant type (MCC) to a default category so expenses are coded automatically. They behave as default (locked) rules, analogous to the All cards default in Card restrictions.
- The
Expense defaultstable is split into two subsections: Merchants (admin-created, editable rules, e.g. Merchant is "Bungalow Bowls" → Category to "Meals and Entertainment") and Merchant types (the 12 default rules below, each locked). - Partially locked editing: for a merchant-type default, the condition is locked — the admin cannot edit the merchant type itself, nor add or delete merchant-type rules. The admin can edit the category the merchant type maps to. In the rule's RHP, the
Merchant typecondition row shows the lock affordance while theCategoryrow remains editable (opens a category picker). All 12 rows always exist; none can be created or removed.
- The 12 default merchant types and their default categories:
| Merchant type | Default category |
|---|---|
| Airline | Airfare |
| Commuter | Car |
| Gas | Car |
| Goods | Materials |
| Groceries | Meals and Entertainment |
| Hotel | Travel |
| Office Supplies | |
| Rental | Travel |
| Services | Professional Services |
| Taxi | Travel |
| Uncategorized | Other |
| Utilities | Utilities |
- Subsection-header logic (consistent with R1): when only default rules exist (no custom merchant rules), show a flat list with no subsection headers. The Merchants and Merchant types headers appear once at least one custom merchant rule exists.
- Type pill: every row in this tab uses the
Updatepill (consistent with the R1 label change), including the locked merchant-type rows.
Migration from Categories
Rules previously authored from Categories settings now create and edit through the centralized Rules flow. Existing category rules must continue to function and appear in the appropriate new tab. The Categories page no longer hosts rule creation as the primary path (contextual display returns in R3).
Creation flow update
The New rule RHP now lists four options in order: Restrict card spend, Flag for review, Require fields, Apply expense defaults. Recommended/example chips (e.g. "Flag alcohol purchases", "Block gambling charges") may appear under a Show examples affordance.
Examples
- Admin creates "Require itemized receipt when Category is Meals and Entertainment" from
+ Rule: it lands in theRequire fieldstab. - Admin creates "Flag for review when Category is Home Office": it lands in the
Flag for reviewtab. - A previously category-authored "Meals and Entertainment + amount above" flag rule appears in
Flag for reviewand is editable through the centralized flow. - A workspace with no require-fields rules sees the new
Require fieldsempty state. - Opening the locked
Merchant type is "Gas"default: the Merchant type condition is locked, but the admin changes its mapped Category from "Car" to a different category and saves. - A workspace with no custom merchant rules sees the 12 locked Merchant types rows as a flat list; adding one custom merchant rule makes the Merchants and Merchant types subsection headers appear.
Issue Owner
Current Issue Owner: @mallenexpensifyMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Jun 4, 2026
Current assignee @dubielzyk-expensify is eligible for the NewFeature assigner, not assigning anyone new.
54 remaining items
JmillsExpensify commentedon Jul 17, 2026
Going to keep this open for the regression tests, once the beta is lifted.
JS00001 commentedon Aug 18, 2026
Close to removing beta
dylanexpensify commentedon Sep 21, 2026
Does this need to be open still?
JS00001 commentedon Sep 21, 2026
I dont think so, no