Automated Transaction Mapping

Zluri pulls spend transactions from your accounting systems, cards, and expense tools, and maps each one to the application it paid for. Transactions that Zluri can't map land on the Unrecognised tab, where someone has to map them by hand. When the same charges come in the next month, they have to be mapped again.

Automated transaction mapping reduces this manual work. Rules in Spends > Automation map, unmap, or archive transactions automatically. You can create a rule while you're mapping, unassigning, or archiving a transaction, right from the same window, so you don't have to leave the page and rebuild the rule from memory.

How transactions are mapped automatically

1. Your rules run first, in priority order. Rules in Spends > Automation apply to matching transactions. When a transaction matches more than one rule, only the higher-priority rule applies.
2. Zluri's mapping AI runs after your rules. It uses patterns from transaction details and vendors to map remaining unmapped transactions. It's on by default, but you can turn it off for a fully rule-based, deterministic system.
3. Anything still unmapped stays on the Unrecognised tab for you to map.

See Transaction Automation.

Create a rule while you map a transaction

When you map a transaction from the Unrecognised tab, Zluri asks Do you want to create a rule for similar transactions?

Steps

1. On the Unrecognised tab, scroll right to the Assign_app column, then click Assign to App on the transaction row.
2. In the Assigning transactions to application dialog, under Select Application, search for and select the application.
3. Decide whether to keep Do you want to create a rule for similar transactions? selected. Keep it selected only if the transaction description reliably identifies this application every time. Clear it if the description is generic and could belong to different applications.
4. Click Map & Create Rule. If you cleared the checkbox, click Map.

The transaction is mapped first, so declining the rule doesn't affect the mapping.

Create a rule while you unassign or archive transactions

The same option appears when you unassign or archive transactions on the Recognised tab.

Steps

1. On the Recognised tab, select one or more transactions.
2. Click Bulk Edit, then click Unassign Apps or Archive.
3. Decide whether to keep Do you want to create a rule for similar transactions? selected.
4. Click the button for your choice:

How the rule is filled in

Zluri builds the rule from the transaction you acted on:

When you select several transactions, Zluri fills in a field only if it has the same value across all of them. If the values differ, Zluri leaves the field empty.

📘

Why new rules go last

A rule created this way is inferred from one transaction. Rules that someone wrote on the Automation page reflect deliberate intent, so they keep priority. If the new rule turns out to be too broad, existing rules still apply first.

You can edit, reorder, deactivate, or delete these rules on the Automation page, like any other rule.

Related articles

• Transaction Automation
• Unrecognized Transactions
• Recognized Transactions
• Archived Transactions