Skip to main content
Question

Register Arrival (Non-Inventory) allows today’s date but rejects other dates in same closed period for user group

  • May 27, 2026
  • 1 reply
  • 36 views
C
Do Gooder (Customer)
Forum|alt.badge.img+3

Hello IFS’s Experts,

I am facing a behavior in IFS Cloud 24R2 that I would like to better understand and fix.

Context

  • Module: Procurement / Register Arrival
  • Scenario: Non-inventory purchase order receipt
  • Company / Site: XXX
  • User Group: RECEP
  • Accounting period involved: 5 (may 2026) 
  • User Group (RECEP) period status = Closed
  • Voucher Type : 0 (The only one group related to is RECEP)

 

In a context of periodical closing, we have decided to close the periods for the user group in charge to perform all the Register Arrival transactions.

If we select a date within the closed period with is not today’s date → Transaction is blocked (expected behavior).

If we do NOT change the default date (system date) the transaction is successfully completed (unexpected behavior).

Both dates (26/05 or 27/05 in this case) are within the same accounting period (May 2026), which is closed for the user group RECEP.

 

Has anyone experienced this behavior in IFS Cloud and how can we fix this unexpected behavior ?

 

Is it possible that we are missing a configuration setting? Could there be any setup related to transaction date validation at the site level?

Thank you in advance for your help.

1 reply

A
Hero (Partner)
Forum|alt.badge.img+12
  • AsankaGaru
  • Hero (Partner)
  • June 4, 2026

Hi,

This behaviour can also be seen in inventory purchases for a closed period. In this case as well, the transaction for a 'Closed Period' is allowed when the transaction applied date is today, but not for any other day within the closed period.

 

(Below is my screenshot from non-inv purchase)

NOIN PURCH


I cannot see any justification for this behaviour, especially since the ‘transfer of the transaction to the GL' background job will fail with an error stating that the period is closed for the user group. (I tested with user group AC)


I think If IFS has deliberately allowed this behaviour to enable transaction registration, it should be clearly documented. I cannot find such.

 

I think you should raise it with IFS as bug. If they say its not a bug, please also share their reasoning with us.


Thanks and hope this helps
Asanka

Asanka Garusinghe - https://www.linkedin.com/in/asanka-garusinghe-61634a64/
Piyal Perera
Hero (Employee)
Forum|alt.badge.img+12
  • Piyal Perera
  • Hero (Employee)
  • June 5, 2026

Hi ​@Charles-E,

I do Cursor-assisted code/functional search for your issue and hope these insights are beneficial.

My view is that your issue is a defect, not a configuration mistake. The period close for user group RECEP is enforced inconsistently depending on whether the arrival date equals the site (system) date.

According to Cursor’s analysis, root cause for this issue is:

 The validation lives in Mpccom_Accounting_API.Check_Date_Applied, which correctly checks whether the user’s finance user group has an open period for the given date:

But that check is not always called. In MpccomAccounting.Check_Insert___, it is skipped when date_applied equals the site date:

The original assumption was effectively: “today’s date does not need a period check.” That breaks when you close the current period for a user group — which is exactly your periodic-closing scenario.

Please proceed creating a support issue and IFS team will have more detailed investigation into this.

Regards,

Piyal

 

 

Piyal
Terms & ConditionsAccessibility statement