Settings and activity
3 results found
-
454 votes
Hey everyone, we've been following the conversation closely and we want to acknowledge how important this is for many of you.
Atm, we’re on a long journey to provide more controls within Xero features that our customers need. Being such a broad idea that touches many areas of our platform, we’d like to encourage adding your votes to specific user permissions that matter most to you, such as:
- Bank Accounts: For more control over who can see bank account balances and access specific accounts, please see the idea here: User Role - Restrict access to individual bank accounts
- Sales and Invoicing: If you’d like to see changes to permissions around sales reporting and editing invoice templates, you can follow that conversation here: User roles: Restrict access to Invoice Settings
- Reports: To have your say on restricting access to specific reports, the relevant idea is here: User permissions - Assign user…
Gayo Primic
supported this idea
·
-
418 votes
Hi everybody, coming across from the previous forums we know this idea has a lot of interest.
There is a way of using Xero's reports to accomplish what you're asking here and save the format so you can easily access and send this report to your customers outside of Xero.
Running the Aged Receivables detail report you can choose how many ageing periods you'd like to show and set the period to '30 days'. Simply Filter the report by Contact and Update to run.
- Once you've got it set up, save as Custom so you can easily access this format anytime
- If you deal with groups of contacts this also means you could Filter for multiple contacts to combine the view into one report rather than multiple customer statements 🙂
- Export the report to PDF, where you can send to customers from your email system outside of Xero
We appreciate…
An error occurred while saving the comment An error occurred while saving the comment
Gayo Primic
commented
Please have a way to add an Age Analysis on the Footer of Statements.
(See screen-shot from Sage)
Gayo Primic
supported this idea
·
-
35 votes
An error occurred while saving the comment
Gayo Primic
commented
Kelly, I've created a second Dev. request, as suggested. (I'm unable to Edit the original one to remove "part 2".)
Gayo Primic
shared this idea
·
Thank you, Gary,
Statey feels like "way overkill" for the simple piece of reporting that we are asking for; and that "should" already be on the Statement.