Audit Trial on Project Timesheets Entry and Reporting in CU7 For AX 2012 R2

Hello Friends,

It has been hectic two months and I have not been able to spend time to write here. Hope you all are up and running on your AX learning curves.

Here I am back today ! and in today’s post, we will discuss about the new audit trial features, which are introduced for the Project Timesheets functionality in the CU7 release for AX 2012 R2.

This new feature allows you to setup audit trials on all the timesheets which are submitted by the workers of your organization by which you can record all the changes which are made by the workers to the timesheets. This new feature also includes the option of blocking future timesheet entries, except for the planned absences of the employee.

Let us now see each of these new enhancements in action.

1. Parameter Controlled: The first step in this is to enable the necessary controls in the Project Management and Accounting Parameters form. You can always choose whether to enable the audit trials or not.

    Notice the various check boxes you have under the “Validation” group highlighted in screenshot below.


2. Block Future Timesheet Entries: In CU7 and later versions of AX 2012, you can now “Block the entry of timesheets for the future period”. This is a very useful enhancement to have good control over the employee timesheet entries. However, you employees can enter planned absences for the future with this parameter enabled.

  • Go to PMA > Common > My Timesheets and create a new Timesheet for a future period which is 04/21 – 04/27 and then create a new timesheet line for a project except for the planned absences.


  • Notice that, system will block this with a warning message as shown below.


3. Validate Absence Categories and Validate Absence: With the “Block future timesheets” enabled, if you do not select the “Validate Absence Categories” check box, then the workers cannot enter future absences in a timesheet for a future period. Notice in screenshot below that with these checkbox marked and worker is able to enter a future absence  for a future period.

image image

4. Require Timesheet Audit Trial: When you enable only this checkbox, your workers will not forced to enter a Reason for timesheet changes such as Deletion, or editing after Submitting. But, the Timesheet Audit trial will be maintained. This means that if workers update anything in an original timesheet, the audit trial will be stored for future references.

  • In the example below, Julia submitted the timesheet for period 04/13.


  • The reviewer of the timesheet has rejected the timesheet asking for additional comments on the timesheet lines. Julia then adds  more comments and resubmits the TS.


  • The Project Accounting Team or the Timesheet Reviewers can see the complete audit trials history of the timesheets by clicking the Manage Versions button on the ‘All Timesheets” list page. System maintains a complete audit trial of the timesheet to track what happened to it since creation.


  • Additionally, you can also compare the various updates by clicking the “Compare” button to know what exactly was changed in the TS version.


5. Allow Timesheet Change Reason: When you select the Require timesheet audit trial check box, then you can also select to tell the system if the worker can enter a reason for change when they change timesheet.

  • In the screenshot below, notice that, a new field is shown the timesheet line for entering change reasons, when you enable the “Allow Timesheet Change Reason” parameter.


  • Workers can enter reasons for changes, but it is not mandatory to enter the reason for change, unless you mark the “ Require Timesheet Change Reason” checkbox.


6. Require Timesheet change reason: When you mark this, workers are needed to enter change reasons for every change they make to the timesheets.

  • If we Reject the timesheet which Julia submitted above with this parameter enabled, Julia will need to enter a reason to be entered before resubmitting the TS.
  • Notice that when Julia changes the #hours to 4 from 3 and tries to save or submit the timesheet, system gives a warning message asking for the reason to be entered.
  • When the workers enter the change reasons and resubmit, then complete TS history along with the change reasons can be seen in the Timesheet versions form.


7. Deleted Timesheet History: This new feature also allows to keep complete track of all your deleted timesheets. You can track the reasons why workers deleted the timesheets.

  • In Screenshot below Julia deletes the timesheet as she created it for a future period by mistake. When Julia clicks Delete, notice that she needs to enter a reason.


  • Navigate to PMA > Common > Timesheets > Deleted Timesheets History list page to see the list of all the deleted timesheets along with the reasons. You can also trace the versions of the timesheet from this screen.


8. Submitting Timesheets Into a Closed GL Period: Another great addition you will notice is the “Allow Date Corrections On Timesheet” functionality. This allows you to submitting timesheets into a GL period which is already closed or On-Hold.


  • Screenshot below shows the ledger period 08/01 to 08/30/2013 is Kept “On-Hold”.


  • When you submit a timesheet for this period and try to post the timesheet, system did not allow the posting earlier and system would block this saying the Period is not open.


  • With the “Allow date corrections on Timesheets” checkbox marked, you can now post the timesheet, and system will automatically post the ledger transactions into an advanced period which is Open subsequently. However, the Project transaction dates will remain as the original timesheet line dates.


  • Notice that system posted the ledger transactions automatically to the next period which is Open, i.e. 09/01/2013.

image IMPORTANT NOTE: You might find that the “Project Transaction date” also gets populated with the next open date which is “9/01/2013”. This was an issue in the CU7 release and a HOTFIX  KB 2922713 was released around January of this year. Please make sure you install the hotfix to see the correct results. Well, that’s it for today! Stay tuned.. Keep Reading…

4 thoughts on “Audit Trial on Project Timesheets Entry and Reporting in CU7 For AX 2012 R2

  1. Hi Sandeep,

    Your insights into each topic is of great help for us while implementing AX 2012 r2 to clients. Thanks a lot for posting and we really appreciate that.


  2. Hi Sandeep,

    Perhaps a little off topic, but we have noticed since upgrading to CU7 that the “Comments” button is missing in enterprise portal for timesheets. Any recommendations on bringing this back?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s