Settings and activity
2 results found
-
244 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 
Linda Tan
supported this idea
·
-
119 votesLinda Tan
supported this idea
·
Accounting standards globally (IFRS, US GAAP, ASPE and similar frameworks) require accurate maintenance of source document data and proper period recognition. The invoice date (document date) and posting date (accounting period date) serve different purposes and must be separate.
When a prior period is closed and a backdated invoice is entered later, the system forces the invoice date to be changed to the posting date. This results in:
• Recording an incorrect document date
• Compromising audit trail integrity
• Distorting vendor history and aging
A standard audit cut-off procedure (under ISA and PCAOB standards) is to identify invoices dated on or before period-end but recorded after period-end.
Without separate fields:
• This query cannot be performed systemically
• Auditors cannot rely on system-generated reports
• Manual testing increases
• Control reliance decreases
Separate invoice and posting dates are fundamental for:
• Accurate recordkeeping
• Proper audit cut-off testing
• Reliable internal controls
This is a core accounting system requirement, not an enhancement.