Skip to content
  • There are no suggestions because the search field is empty.

My spend numbers look wrong

Work through the common causes of missing, inflated or suddenly changed spend before you escalate a data issue.

What you get

A practical order for checking the most common causes of unexpected spend before you assume the underlying accounting data is wrong.

Too low

The most common one, and the most misleading — it makes savings look smaller than they are.

  • Suggestions waiting in Needs Review. AppVentory has matched the payment but is waiting for you to confirm it. Until you do, the cost belongs to no app. Go to Spend Overview → Needs Review and confirm.
  • Software still in Unmapped. A payment AppVentory could not place at all. Sort Unmapped by amount and assign the software ones.

Too high

  • A transaction on the wrong app. Open the app's Spend tab, find the stray line, and Reassign it.
  • The same tool arriving twice under two vendor names. Keep the one carrying the spend, deactivate the other.

A sudden dip

Check the connection and sync history first. A gap in imported data can look like a real reduction in spend. Re-authorise or re-sync using the actions available for that connector, then compare the period again.

A drop after tidying up

Deleting an app moves its transactions to Archived, out of your totals. If you meant to keep the history, restore the app from Settings → Deleted Apps and bring its spend back from Archived.

The order to check

Needs Review → Unmapped → app mapping → connection history → Archived. This order catches the data-quality issues most likely to change an app total.

What you've unlocked

You now have a repeatable first-line check for spend discrepancies.