Experience the difference of "Elite".

PM Statements: Add Expense Categories

Status: Requested 1 Vote
Nov 3, 2022 1:58 PM
Joined Jan, 2020 79 posts

Now that Expense Categories have been added, it would be ideal for them to be fully integrated throughout OwnerRez. Most crucial for us right now is in PM Statements. When we run a PM Statement and then export it to Excel, there’s no column displaying the Expense Categories on the Expenses tab. We've adapted our processes to utilize these Categories in regards to Owner Statements and not being able to access them on the PM Statements as well is becoming an issue.

Rex C
Nov 7, 2022 6:16 PM
OR Team Member Joined Aug, 2021 25 posts

Hi Alece,


This should be already available, based on the configurations within your Settings > Statement Views. If you need assistance, please write an email to help@ownerreservations.com and we will be glad to help with getting this set up.

Nov 8, 2022 10:38 AM
Joined Jan, 2020 79 posts

Hey Rex! That's where I started (emailing the support team). Caleb replied that it wasn't possible and said I should propose it as a feature request! (Also, to my knowledge, Statement Views are only for Owner Statements. There isn't an equivalent for PM Statements... that I've found anyway!)

Joel P
Nov 8, 2022 11:10 AM
OR Team Member Joined Oct, 2009 61 posts

Hi Alece,

You are correct. Statement views are for Owner Statements.

However, all expenses in OwnerRez are Owner Expenses. There is not (yet) the concept of a PM expense, hence, we have not exposed expense columns in the same manner on PM statements.

We'll keep this Feature Request around, as we have lots of stuff planned for the PM module in the coming roadmap.

Nov 8, 2022 11:58 AM
Joined Jan, 2020 79 posts

Yes, they are owner expenses that are facilitated by (and then reimbursed to) the PM. Which is why it's helpful to have the categories that are already assigned to those expenses be visible on the PM statement exports as well. Thank you for keeping this Feature Request around for (hopefully!) future development within the PM module.