Dynamics Community Forum Thread Details

D365FO - Project voucher transactions behave differently on Ledger calender setup

Dear all,

There is a scenario where we are closing the previous month, so we want to allow certain user groups to post in gen. ledger but prevent postings of project transactions in the closed\previous month, i.e. project postings can be done with the project date in the closed month, but the voucher (accounting) date should be moved to the next open period.

I dont think its possible in standard D365FO, however, I d like to ask you, the community for input.

SETUP

Scenario 1
Feb. is “On hold”.

In project posted transactions, the project date is the 11.02., because the period is on hold, the voucher date was moved to 01.03. That was expected.

Scenario 2
We tried the following setup, because we want some users to post in the general journal in the (previous.) month Feb., but we don’t want project timesheets\journals to be posted in February.

The voucher date is NOT moved to 1^st of march. Since the ledger postings are not allowed for my user, I was expecting to move the date to the next open period, which is march.

In my opinion the Period status (Ledger calenders) "On hold" should behave equally to being set to "Open", but setting "Ledger" to "none" or a specific user group, which I am not part of it.

Thanks in advance for your input.

Adis-

Categories:

Dynamics 365 Finance

Your requirement is to allow general journal postings in the closed month for specific user groups while preventing project transactions from being posted in the same period. However, you want project postings to respect the period status and automatically move the voucher (accounting) date to the next open period.

Analysis of Current Behavior

Scenario 1 (Period On Hold)
- February is On Hold.
- Project transaction date = 11.02.2025
- Voucher (accounting) date automatically moved to 01.03.2025 ✅ Expected behavior
Scenario 2 (Ledger Assigned to Specific User Group)
- February is still On Hold, but Ledger access is assigned to a specific user group.
- Project transaction date = 12.02.2025
- Voucher (accounting) date is not moved to 01.03.2025 ❌ Unexpected behavior

Root Cause of Issue

When the Period Status is set to On Hold, Dynamics 365 Finance and Operations moves the voucher date to the next open period.
However, when Ledger Access is restricted to a user group, the system does not treat it the same way as "On Hold." Instead, it assumes the period is "Open" for authorized users, and since your user is unauthorized, the transaction does not follow the same automatic date adjustment.

Solution: Ensuring Project Transactions Always Move to the Next Open Period

Since standard D365FO does not provide a direct configuration for this behavior, consider the following solutions:

Option 1: Use the "Automatically Set Accounting Date" Parameter

Navigate to:
Project management and accounting > Setup > Project management and accounting parameters
Under the Ledger section, ensure that “Automatically set accounting date” is enabled ✅.
This setting should ensure that when a period is not open, the voucher date automatically moves to the next available open period.

Option 2: Adjust Ledger Calendar Period Access with a Workaround

If Option 1 does not work as expected, you may need to:

Keep the Ledger Period as “On Hold” for February to ensure all project transactions move to March.
Use a separate Ledger Period Access setup (System Administration > User groups > Ledger access) to allow only the general journal users to post in February.
Configure a Posting Validation Policy via security roles to ensure that project journals are not posted in February but general journals are allowed.

Option 3: Customization via Ledger Posting Class (if needed)

If the standard settings do not work, a small customization in the Ledger posting logic (via X++ code) can enforce the rule that all project transactions posted in a closed period must have their voucher date moved forward.

Conclusion

Standard D365FO behavior does not treat "On Hold" and restricted Ledger Access equally.
"Automatically set accounting date" should be enabled to enforce proper date movement.
If the issue persists, configure security roles & user groups correctly to differentiate between general and project journal postings.
As a last resort, consider a minor customization to enforce the voucher date shift for project transactions.

Quick Links

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL