Settings and activity
2 results found
-
186 votes
Hi community, we appreciate this idea has collected a fair amount of interest which has all been shared with and reviewed by the product team.
While this isn't currently being worked on there are other ideas this team are working on right now, including a bulk void feature and highlighting rows when selected. Although these features are still under development process and we don't have confirmed release dates yet.
With regards to having a separate field for the posting date and invoice date, our team is interested in better understanding this idea as it may be something they look to develop down the track. They really appreciate and encourage you to continue to share your experiences, pain points and insights. This will help them understand how this feature can benefit you and other customers, as well as gauge demand for it.
As always, if there's any change we will…
An error occurred while saving the comment Ingrid Crozier supported this idea · -
157 votes
An error occurred while saving the comment Ingrid Crozier commentedUnless I'm missing something else, the second reference field is necessary for me as currently there is no ability to have a separate invoice date and posting date on bills. What if the invoice date is in a closed period? I then have to change the invoice date to be a date outside the period and now have incorrect information when trying to search up the invoice details in Xero (invoice date now shows a different date than is on the invoice). At least with a customizable second reference field I can add the invoice date in there.
Ingrid Crozier supported this idea ·
This is a requirement when it comes to accrual-basis accounting and prevents the ability to do any sort of month-end or quarter-end close process, as using the invoice date would backdate transactions into "closed" periods. If the posting date is entered into the invoice date field, then you have incorrect invoice details in Xero that do not match the invoice itself. This is absolutely a critical requirement and I am very surprised this feature does not already or exist, or is even being worked on at the moment.