Thom Boivin
My feedback
10 results found
-
18 votesThom Boivin
supported this idea
·
-
62 votesThom Boivin
supported this idea
·
-
111 votesThom Boivin
supported this idea
·
-
4 votes
An error occurred while saving the comment Thom Boivin
supported this idea
·
-
17 votesThom Boivin
supported this idea
·
-
4 votes
Thanks for the idea JPP. Can you be more specific about where you want the debit and credit used to be added back to the gift? There are certainly limitations as to where data could be written back to the gift due to field size constraints as well as considering all of the output that is typically in Post to General Ledger files.
Here are a few more questions for consideration:
What is the goal of having this data in RE/how would that data be used?
Should there be any considerations if an adjustment is being posted due to adjustments creating reversing entries to reverse out what was previously posted and then having new journal entries created for the updated information?
What other scenarios might we need to account for if we added a write-back feature?
Thank you
Steve Brewer
Product Manager
Thom Boivin
supported this idea
·
-
6 votesThom Boivin
supported this idea
·
-
14 votesThom Boivin
supported this idea
·
An error occurred while saving the comment Thom Boivin
commented
perhaps bring back tags (and the related filtering) from ImportOmatic classic and make some columns sortable?
-
62 votesThom Boivin
supported this idea
·
-
8 votesThom Boivin
shared this idea
·
This is crucial for organizations that have multiple constituent codes for some scenarios. Our most complicated scenario is for a university and its employees - an employee may hold several classifications simultaneously: is faculty, has an administrative role (as a department chair, dean etc.), and is a retiree (but returned from retirement). Each of these borad roles/classifications has its own consituent codes, which change over time.