Sage 100

Do you know the reason behind DTR posting logic. - If you post within a module and update the detail but do not update DTR (answer No to update DTR) then a. If you subsequently go to the module you see that the DTR is blank/empty (even though it was not updated initially) b. If you to GL you can view and update the DTR b. And gets more confusing if the user then goes into the same module and enters another transaction and follows the posting process all the way through and answers yes to update the DTR Do you know the logic behind this? Seems like it would be simpler to leave the DTR in the module and/or have the DTR in GL

For b., it seems that you could have separation of duties. One person posts the journal for a module but then someone else reviews and posts all of the DTR's at the end of the day.

Ever since this issue occurred the module DTR have never worked the same. https://90minds-com.socialcast.com/messages/8225716?ref=stream

I noticed this quite some time ago, I assumed it was to keep users from accidentally updating DTR from a different user or different batch. but Moria's answer makes a lot of sense too.

Interesting @MoiraGoggin. Once the DTR is in the system there's no practical way to reverse it so why not post the whole thing at the time that the module journal is updated. It is confusing to new people to understand how this works. Admittedly, at sites where users are trained to always update all the way to the DTR then I never get a question. It's usually the people that aren't fully updating the registers that get confused.

This is confusing. One control I insist on for clients is that prior to printing financial statements that the DTR be printed from the GL because that is the only way to ensure there are no unposted DTRs in any module.

I preach to the controller to update the GL DTR once a week. I had one financial manager not notice an unposted entry for four months. When I brought it to her attention, she said she had been looking for it and ended up doing a JE to fix it......

DTR is not necessary when the initial posting occurs, so why force sales and operations people to waste time doing it? The accounting supervisor runs DTR at EOD, and gets a pdf with all the transactions on it, instead of scattered across many. If using Sage Alerts, set one up to flag unposted DTR's to run at 9 pm nightly. My own preference is that non-accounting users shouldn't have to bother with DTR; they certainly see no value in it. So leave that to Accounting.

One customer had this as such a nagging issue so I set up a nightly alert for unposted DTR data. At least it's better than the Yes / No / Clear I saw once for an ancient version.