Skip to main content
Question

PO505000 – How can a purchase order be created with a date in the year 5026?

  • Nov 16, 2026 8:22 PM UTC
  • 5 replies
  • 37 views
  • Translate All

Hi everyone,

We noticed an unusual date on a purchase order in Acumatica 2025 R1.

The purchase order was actually created on November 12, 2026, but its Order Date (POOrder.OrderDate) is June 16, 5026.

We confirmed that the purchase order was generated through Create Purchase Orders (PO505000).

I performed a few tests in 2025 R1 to understand how this date is determined:

  1. The Creation Date (POCreateFilter.PurchDate) in PO505000 defaults to the current Business Date.

  2. When I manually change this date before processing, the generated purchase order in PO301000 uses the specified date.

  3. Changing the Business Date also updates the default Creation Date when reopening PO505000.

Other purchase orders created on November 12, 2026 have the expected date.

My initial assumption is that the date may have been entered incorrectly in PO505000, but I haven't confirmed this.

My questions are:

  • Is it expected standard behavior for Acumatica to accept a purchase order date as far in the future as the year 5026?

  • Is there any standard date validation in PO505000 or PO301000 to prevent this?

  • Is there a way to trace the original value of POCreateFilter.PurchDate used when generating a purchase order?

I'm trying to determine whether this is expected behavior, a missing validation, or something that requires further investigation.

Thanks for your help!

 

5 replies

mohammadnawaz51
Varsity I
Forum|alt.badge.img+8

​@ERPNavigator Is the financial period opened for 5026?

Translate

jdobish
Captain II
Forum|alt.badge.img+2
  • Captain II
  • Nov 16, 2026 9:46 PM UTC

Someone is really planning for the future!

Translate

  • Author
  • Freshman I
  • Nov 17, 2026 8:00 AM UTC

Hi,

I've just checked, and the financial periods for the year 5026 are not open.

However, the purchase order was successfully created through PO505000 with an Order Date of 06/16/5026.

What I'm also trying to understand is how we can identify what actually happened.

The purchase order was created on November 12, 2026, and other purchase orders created on the same day have the correct date.

Is there a way in Acumatica to determine whether:

  • The user manually entered 06/16/5026 in the Creation Date field (POCreateFilter.PurchDate) before processing?

  • The incorrect date was automatically assigned by the system during purchase order generation?

For example, is there any audit history, processing log, or other standard functionality that could help trace the value used in PO505000 at the time of creation?

I'd like to understand whether this was a user input error or a system issue, rather than just assume that the date was entered incorrectly.

Thanks for your help!

Translate

darylbowman
Captain II
Forum|alt.badge.img+17

I'd like to understand whether this was a user input error or a system issue, rather than just assume that the date was entered incorrectly.

I’m not sure I can give you definitive answer here, but what I can tell you is that according to my research of the source code, there is no date validation on that screen which would prevent a user from creating a PO with that date. Seeing 25 R1 is a relatively old release, and I’ve not seen anyone else complaining about this issue, I think you could safely assume it was a user error.

Translate

craig2
Pro I
Forum|alt.badge.img+4
  • Pro I
  • Nov 17, 2026 4:44 PM UTC

I think ​@darylbowman has it, being user error.  I probably have 7 or 8 Business Events running around to alert users when a date seems unreasonable.

Translate