By using this website, you agree to our Terms of Use (click here)
Good Morning,
I have a question on transaction entry. We use a third party provider who provides unique screens and processes that embed into the Acumatica framework. These lead to some differences, but I have also noticed a substantial amount of similarities. I am able to see the database architecture and skim across it, this permits inside knowledge on what the software probably supports. Now to the question lol.
In the backed, I see many date fields on the transaction table. Such as Finperiod, create,update,invoice, Revenue, and incur.
We have an issue where transactions are entered in a latter month to address a transaction that occurred in a previous month. Managers then want those latter numbers to roll into the previous month on some reports. i.e. payment entered in June and reversed in July should both show in June in a summary report. However, this does not occur. I believe the problem is that when the transaction is entered, no retro date is provided and the application would have no way to know the payments are related by date. Does Acumatica have a way you would handle this when entering a transaction? Of course at my local company, things have been done for such a long time that even looking at a process for potential improvements sends chills down the spine. So any additional insight is greatly appreciated.
Hi SQLRunner,
Maybe you can include a screenshot of the screen where these transactions are getting entered. I doubt this is a backend problem. Most likely, the users just need to make sure to backdate their transactions.
I have attached an example of the entry window. I'm certain your right, I have seen this kind of problem before. I use to work with a collection company that had a "post date" and a "payment date", they had some important reasons that they could not be different, which when tested, ended up being untrue. Because managers had believed that to be the case for over 15 years (Company had the same software vendor since the 80's), it was very difficult for them to switch into a new mindset of payment entries with different payment/post dates. Similar situation here, things are done a certain way and there are many reasons that it has to be that way. But you end up in this dialetheism situation, you want to show a payment in a different period but you don't want to enter it with that data. I'm pretty confident they just need to select the period they want the payment to show in and provide the other dates as they are laid out, i.e. incur date left as is and so on. The screen may be different from Acumatica, I turned off my install and can not immediately test.
That's correct. The Transaction Date in your screenshot is the date of the transaction. The Post Period is the financial period that you want the transaction to appear in for Accounting purposes.
One confusing thing here that I often encounter is that people expect to see a Post Date field (so did I when I first started using Acumatica), but you only get a Post Period in Acumatica.
And the Transaction Date does not need to fall within the Post Period. They can be different.