web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...

Restrict financial postings for a specific date range to handle closing in a better way

(1) ShareShare
ReportReport
Posted on by 71
We perform inventory closing every month. What we want to achieve is - After every 25th day of the month, restrict users to post any financial transactions between 1st and 25th day of the month. They can still post the transactions for the days after 25th. 
The objective is: To handle the closing effectively by not having any ad-hoc transactions. 
Is there any provision in D365 FO to do the same? Or, are there any other ways to handle this requirement? 
Categories:
I have the same question (0)
  • Suggested answer
    Adis Profile Picture
    5,720 Super User 2025 Season 2 on at
    Restrict financial postings for a specific date range to handle closing in a better way
    Hello,
     
    Short answer, no there is no such functionality. However, you wont be lost alone in the forum 😊
     
    Let me explain how we handle this situation. We most likely have different business cases, however, providing some ideas may help.
     
     
    1:
    The way we manage this, is to set the period status "On hold" and select a user group. There are a handful of users assigned to this user group, as they are the only ones who are allowed to post journals. Yes, they can select any date, however, they are well trained and aware of the business case.
    This also doesnt cover 100% in our business case, however, you work with what you have.
     
     
     
     
    2:
    If you are working with journals, you could activate a workflow to double check for incorrect dates. Its not my favorite, but I wanted to list what we have.
     
     
     
     
    3:
     
    I love this function. Unfortunately, the parameter doesnt exist for all journals, however, if that works, I would extend the functionality. With a parameter implemented, you can always switch between custom code and standard.
    Nevertheless, what the parameter does, is during posting, if the period you post in (Period status in ledger calendar is set to "On hold"), it post on the 1st day of the next open period, project date staying the same. This functionality is also available for expense journals.
     
     
    The overall idea of 3 is, that if you want to separate project date and ledger date, then you can do this with this parameter. There is no parameter for the general ledger f.e., because you can define an accounting date, so if the period is closed (=on hold), you receive an error and then you select the next open period.
     
     
    So, I would start with 1. If you have already, then it would be interesting why it doesnt work for you.
     

    Kind regards, Adis

     

    If this helped, please mark it as "Verified" for others facing the same issue

    Keep in mind that it is possible to mark more than one answer as verified

     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

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

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 1,850

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 795 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 519 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans