Settings and activity
4 results found
-
19 votes
Kenny Frisby
supported this idea
·
An error occurred while saving the comment -
60 votes
Hi team, back again to share progress on the idea from my lat update. As mentioned our product team are now in the process of developing a way to make reports that've been customised within a clients org available to include in Adviser packs.
I'll keep you in the loop of this feature and when you can start making use of it, here!
An error occurred while saving the comment Kenny Frisby
commented
The ability to add a client level Custom Report to a Practice Annual Report template once its been created at client level.
With a wide range of chart of accounts and not all client charts set-up with report codes mapped we need to rebuild every custom Profit & Loss and Balance Sheet when doing Annual Reports now.
This will be excruciating for the first year while we are forced onto the new reports.
We should simply be able to add a client level custom made report into the Annual Report once we have created a new one from the template at client level. Then delete the ones not needed.
This would be a quick easy fix for now, for what will be some really long term pain.
Furthermore across a wide range of clients and client types we don't necessarily need a practice level P&L or Balance Sheet. DIfferent strokes for different folks and its just much easier to build these custom reports at client level and slip them into the Annual Report while preparing.
Surely I'm not the only one with this pain.
Especially when no-one has the time to map all the report codes for each individual client and clients add their new codes during the year sometimes which is just ongoing work mapping to practice templates when we can quickly just customise at client level while doing ongoing work during the year.
Furthermore I have dozens of custom reports at client level that have been requested to have different groupings and layouts that i shouldn't need to rebuild while doing Annual Reports.
Should just be able to slip them in!An error occurred while saving the comment Kenny Frisby
commented
This is essential Xero!
We shouldn't need to rebuild a custom Profit & Loss and Balance Sheet from within Annual Accounts templates once created at client level.
We should just be able to delete the relevant reports that are useless and add the client level custom reports.
Not only are we now going to need to do this for every single client as we do Annual Reports, but then each year they will need amended for any changes during the year.
Its not practical to use the templates at practice level for every client.
Too many charts of accounts are completely different, especially those we pick up as new clients from competitors and those that set up Xero themselves then came for help.This is madness.
Please just give us the ability to add a custom report to client level Annual Reports.
Rant over.
Kenny Frisby
supported this idea
·
-
5 votes
An error occurred while saving the comment Kenny Frisby
commented
Only changed to the new reports today due to this problem. The new reports are so much slower to update and work with
Kenny Frisby
supported this idea
·
-
22 votes
An error occurred while saving the comment Kenny Frisby
commented
This is essential Xero!
We shouldn't need to rebuild a custom Profit & Loss and Balance Sheet from within Annual Accounts templates once created at client level.
We should just be able to delete the relevant reports that are useless and add the client level custom reports.
Not only are we now going to need to do this for every single client as we do Annual Reports, but then each year they will need amended for any changes during the year.
Its not practical to use the templates at practice level for every client.
Too many charts of accounts are completely different, especially those we pick up as new clients from competitors and those that set up Xero themselves then came for help.This is madness.
Please just give us the ability to add a custom report to client level Annual Reports.
Rant over.
Kenny Frisby
supported this idea
·
Point 1 is absolutely essential and would be so easy for implement. I'm surprised it isn't already part of the new reporting framework