Fix this: Prevent backdating a Journal entry to earlier than it's JE Lines

Follow
Rebecca Ralls

There is a new VR that was added to JE Lines that will prevent a JEL from having a date that is after the Journal entry date.

However, if a user changes the date of the journal entry to earlier than the JE lines after the je lines are created, this VR never fies because updating the header doesn't trigger any changes on the lines. and then, when you're trying to reconcile your JE transactions or add them to a depostit, the VR fires when the JEL is updated.  This is problematic.  Can you put someting in place that will prevent this?  

Separately, it's also a problem if there were any JEL that might trip this VR in place before the VR was created.  Do you have a suggested work around for managing lines that fit that profile?  Unposting them and fixing them can be very difficult if they are many periods in the past.  

4

Comments

3 comments

Date Votes
  • Official comment
    Permanently deleted user

    Hello Rebecca, 

    Thank you for informing us about this issue. I will have this reviewed by the Product Development team. 

    Comment actions Permalink
  • Brianc

    We have the same issue. How about the ability to fix the line date (post period close) provided you are not changing accounting periods?

    0
    Comment actions Permalink
  • Bao Do

    If the period is not closed, have a flow fire that loops thru the lines and set line date to header date. Alternatively, have the flow find the latest line date and throw a custom error message if the new header date precedes the line date.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post