Match your spend to the right apps

What you get

More reliable app-level spend. Until imported transactions are matched to the correct applications, cost and savings views can be incomplete or misleading.

The four tabs

Go to Spend Overview.

• Mapped — Matched and counting. What to do: nothing.
• Needs Review — AppVentory has suggested an app. What to do: confirm — start here.
• Unmapped — No match found. What to do: assign the software ones.
• Archived — Excluded from totals. What to do: nothing.

Start with Needs Review

Where AppVentory has suggested a match, the row can include the transaction, an App Suggestion and a Confidence Score. Treat the suggestion as a shortcut to review, not as proof that the match is correct.

1. Open Needs Review.
2. Read the suggestion against the description and amount.
3. Confirm. It moves to Mapped and starts counting.
4. Reject it if the suggestion is wrong.

Spend Overview Needs Review tab showing App Suggestion and Confidence Score

Give the low-confidence rows a proper look — a wrong confirmation puts someone else's cost against your app.

Then Unmapped

1. Open Unmapped and sort by amount, largest first.
2. Assign each software payment to its app.
3. Use Create Rule for recurring vendors — one rule saves the same assignment twelve times a year.
4. Click Recheck Unmapped when you finish.

Spend Overview Unmapped tab with a row's Assign action open

Needs Review should normally be worked down as suggestions are confirmed or rejected. Unmapped can legitimately retain non-software expenses that do not belong against an app.

What you've unlocked

Your spend views now have a stronger basis for app-level cost, trends and savings analysis.