Our Finance department is shifting the chart of general ledger accounts and mapped new accounts attempting to respond to a request (demand?) from the annual auditors that isn't actually possible in the current Fund setup in Tessitura. Right now, when the Restricted to Unrestricted batch is created and appropriate funds selected, each appropriate restricted transaction amounts are debited and the unrestricted general ledger for that fund is credited. What they want is for any restricted income to remain in the restricted account, but a totally different "Release from Restriction" (not the Unrestricted GL account) account to be credited, even though the Restricted GL isn't debited, when the funds are released from either a time or purpose restriction.
I talked with Tessitura Consulting who said that this is impossible, which is what I told my Finance department - it's impossible within the current constraints of the Tessitura client and fund setup.
HOWEVER, when I asked if a 'release from restriction' utility could be built that basically doesn't debit the restricted income GL but adds a transaction to the specified 'Release from Restriction' GL, they said that couldn't be done. I just wanted to throw this out to Tessitura Network Developers to ask if adding rows to T_TRANSACTION in a way that isn't currently available out-of-the-box actually breaks things. Can you clarify the risk involved in having a custom utility that adds these release from restrictions? It could create a batch that's posted to do so - that makes sense to me, but I don't quite get why writing to T_TRANSACTION in a way that's not currently part of the client as delivered is out of the question.
Thanks so much for your thoughts on this.
Monica Martin
Oregon Shakespeare Festival