Skip to content
← For small businesses

Enter your idea

For small businesses: Accounting features

Categories

(thinking…)

Expense Claim Report - By Contact spent with

We need to be able to run a report of historical Expense Claims, by Customer contact in order to see what Expenses were entered for a certain time period. The Expense Claims Detail report does not show anything when I run it. I need the Expense Claim Report to be able to be sorted by our Customers names, not sorted by our employees.

10 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

madeline bardolf shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Richard Warren commented  ·   ·  Report

    Or of course the expenses system could revert back with key features we had before. In particular having the expense be a contact.....

  • Matthew Botherway commented  ·   ·  Report

    I find it amazing that there is about a dozen things you can search on in the expenses, yet "Spent at" is not one of them. This feature is so basic and yet missing. Really need to be able to search on "Bunnings" etc,

  • Jaimie Halstead commented  ·   ·  Report

    Could the "spent at" field be populated from the contacts or create a new contact?

    I'm sure this worked before the contacts were upgraded a few years ago.

    Please fix this..

  • Emma Ranade commented  ·   ·  Report

    This would be great. Or at least an option to search expense claims by description/supplier.

  • Judith Hayes commented  ·   ·  Report

    I would like the entered receipt added to the Contact Activity. When the receipt is entered into the expense claim it creates a new Contact but does not record the activity in the Contact. Please fix this.