What happens if two rules match the same transaction?

If two rules match the same transaction, the system applies the rule with the higher priority. This ensures the transaction is coded accurately and avoids duplication or conflicts in your ledger.

When do multiple rules apply to the same transaction

When automated coding rules grow in number and complexity, overlaps naturally occur. Each rule serves a specific purpose, but transactions often meet more than one condition at the same time.

For instance, a single purchase might fit both a department-level rule and a vendor-based rule. These overlaps are common in finance systems that utilize layered automation to maintain flexible and accurate coding.

• Overlapping criteria: Different rules may share similar conditions, such as merchant name, category, or department. When a transaction meets both sets of criteria, the system identifies more than one possible match.
• Vendor and card-based rules intersecting: A rule tied to a specific vendor can overlap with another rule linked to a card or team that frequently makes the same type of purchase. Both rules apply because they target the same expense from different angles.
• Broad versus specific rules: A general rule that covers an entire spend category can overlap with a more targeted rule built for a single merchant or project. The system must determine which one takes priority based on specificity.
• Legacy rules not updated over time: As new automation is added, older rules may continue to exist with outdated parameters. These rules can unintentionally conflict with newer ones if they target similar expense patterns.
• Shared costs across teams: Transactions split between departments, such as shared software or marketing tools, often trigger rules set by multiple cost centers. Each rule recognizes the same charge as relevant.
• Complex approval structures: In organizations where both department-level and company-wide rules exist, a single payment can match multiple approval layers. The overlap occurs because both rules correctly identify their part of responsibility.

How Ramp decides which rule takes priority

Ramp determines rule priority through a structured hierarchy that ensures each transaction is coded correctly and consistently. The system reviews all active rules and applies the one with the most specific match. A rule built with multiple data points, such as merchant and department, takes precedence over one that only uses a single condition, like merchant name.

Card-based rules rank the highest since they apply directly to a specific card or program. Advanced rules come next, followed by standard mapping rules. This order keeps automated categorization predictable and avoids conflicting results.

For example, if a rule is set to code all marketing expenses under one account, and another rule targets charges from Google Ads. Here, Ramp gives priority to the Google Ads rule because it is more specific. The expense is then coded according to that rule.

Ramp also learns from your history. When recurring transactions follow the same coding pattern, the system remembers and applies that logic automatically in future months.

What the final transaction outcome looks like

When multiple rules are reviewed and the system selects one, the final transaction outcome shows how the charge is categorized and recorded in your books. Each field reflects the logic of the chosen rule, including the assigned GL code, department, and expense category. This clarity allows you to see at a glance why a transaction was coded a certain way and which rule influenced it.

If a rule splits the transaction, the outcome displays each allocation clearly with its corresponding percentage or amount. These splits appear in your accounting system the same way they were defined. The final record links back to the original transaction so that you can trace every detail, including merchant, cardholder, and rule applied.

How to review or adjust rule conflicts with Ramp

Ramp allows you to view, edit, and manage overlapping accounting rules directly within your account settings. When multiple rules match the same transaction, the platform applies a clear hierarchy, but you can still review and refine logic when needed.

• Step 1: Open your accounting rules. Navigate to Accounting → Settings → Coding Rules to see all active rules. Each rule displays its type and the conditions that trigger it.
• Step 2: Identify overlaps. Check for rules that share similar conditions, such as merchant names or departments. Ramp highlights the rule applied to each transaction in the Transactions view with a lightning bolt icon and “View Rule” option.
• Step 3: Compare rule specificity. Advanced rules that include multiple conditions, like merchant and department, take precedence over broader ones. Reviewing parameters helps confirm whether a conflict exists or if the system is applying the correct rule.
• Step 4: Edit or remove conflicting rules. If two rules consistently affect the same vendor or spend category, update or delete the redundant one from the Coding Rules page. Changes take effect immediately for un-synced transactions and reimbursements. Transactions that have already synced to your accounting system remain unchanged.
• Step 5: Validate changes. After adjustments, review a few new transactions to confirm that rules are applying as expected. Ramp automatically maintains consistency by following its internal hierarchy: card-based rules first, advanced rules next, and standard mappings last.