Settings and activity
6 results found
-
64 votes
Hi everyone, thanks for your feedback on this idea. We appreciate you sharing how important STP reporting is.
The existing solution is to view the STP finalisation screen, as this information is included in the employee's STP summary.
Something to note is that leave paid out on termination has several reporting types depending on the termination reason and leave type (i.e. Type U, Lump Sum A, etc).
If you use the STP finalisation reports, you may like to view this in conjunction with the ATO’s guide: STP Phase 2 Reporting - Quick reference guide.
Creating a new report for unused leave paid out on termination isn’t currently on our product team’s road map, so we've updated this idea to Not in Pipeline. The idea remains open for votes though so we can continue to monitor interest.
Stephen Harding
supported this idea
·
-
6 votes
Hi Ana, out of interest is there a transaction type you generally find needing to use these actions? For example Spend money, Receive money or Payments applied to invoices and bills?
I've slightly amended the title of your idea for the date of the transactions, we have separate idea for changing the bank account you can join for any updates.
An error occurred while saving the comment Stephen Harding
supported this idea
·
-
121 votes
Hi everyone, we appreciate your patience & would like to thank everyone who’s shared their thoughts and supported this idea.
Xero's payroll reports do currently offer some options to adjust columns, filters & layout. However we hear & understand the need for having additional information & more flexibility with payroll reporting, including the ability to customise & save reports for future use.
Being open here, these improvements are not in our current pipeline. However we'll use this feedback to shape how we plan future improvements in Xero Payroll reports.
Stephen Harding
supported this idea
·
-
425 votes
Hi team, we appreciate the on-going support and feedback we're receiving on this idea and pleased to be able to share this update. Our product team are actively exploring how we can best solve for the needs raised here, although at this time are unable to provide any set timeframes.
They are very much aware of the appetite from our community on this, and as part of their exploration have reached out some users here as they gather insights.
For the time being we'll shift to In discovery and I'll return as soon as there is more on this to share.
Stephen Harding
supported this idea
·
-
132 votes
Hi team, thank you for showing your support in this idea. While this has been reviewed and looked into at present the work we are developing will not extend to start and end timesheets.
This is something we'll continue to consider closely as the team keep planning their roadmaps and we'll make sure to share if there are updates surrounding this, here.
Stephen Harding
supported this idea
·
-
750 votes
Hi community, we appreciate your continued feedback on having different default email addresses for various transaction types in Xero contacts, and the manual steps involved to ensure you're communicating with the right person for different purposes.
Currently, one way of managing this in Xero would be to include every additional person on a contact record in emails, and then removing those that aren't required when sending each transaction. However we totally get this isn't the ideal solution.
While being able to set different email addresses for differing transaction types is something we want to address longer term, like the idea for multiple addresses work for this feature requires cross-collaboration between teams in order to achieve.
Once the multiple addresses feature is live this is something we'll be able to consider more closely and provide further updates on.
We do regularly review all ideas here, and your input is vital. We'll…
Stephen Harding
supported this idea
·
We have an issue with our Stripe integration with Xero. Stripe creates payment transactions in Xero and then when the payout comes in on the bank feed, it matches the payment transactions to the payout, which would be handy *except* that it's causing problems with reconciliation because if the payment transactions are created late in a calendar month (for example, 29th December) and the payout arrives in the bank account in the following month (for example, 3rd January) the bank statement closing balance doesn't match with the balance sheet closing balance.
The only way to currently fix this is to 'Remove & Redo' the payment transactions and then fix the dates and re-match. It's cumbersome. It would be a lot easier to simply have a function to adjust the dates to match the payout so the closing balances match. Alternatively, being able to disable Stripe from creating payment transactions and creating them manually would be preferable to the mucking around but apparently we can't disable this and still keep Stripe as a payment method.