Hi everyone! Something I am trying to figure out on our end is how to reconcile individuals purchasing sponsorships and contributions via TNEW web/online contribution pages on behalf of their companies. In exploring and troubleshooting how we make sure these transactions live in the right constituent record, I discovered that ALL of our contributions made via the web are being processed within a ticketing batch type (not the manual contribution batch type). This makes it very hard to reallocate donations processed via the web. I've also learned that this is one of the normal "headaches" that comes with using Tessitura/TNEW.
I'm still a bit new to using the full scope of Tessitura/TNEW, so I wanted to put this to the wider Development community. What would you all say (or have seen) is best practice in this area? How do you all manage this at your organizations? I have a list of options from utilizing on-account funds to just not offering online sponsorship payments--all of which would pose a different challenge for our donors, Finance department, staff, and/or our data integrity/cleanliness.
Right now our volume on these gifts is low enough that I have visibility on the wonky ones, but if/when the volume picks up they will be harder to spot. Before this happens, I'd love to know what more experienced users are doing to mitigate this.
THANK YOU ALL!!! :)
When I catch it happening and it's a new gift (not a pledge payment), I've been known to merge the "new" individual record into the existing corporate record. It works fine as long as it's not a pledge payment.
This is what we've been doing right now. With us still being so new in Tessitura we're still seeing a lot of new records being created, so we've been lucky. It's when we get the individuals participating on their own and have other transactions owned by them and not their company that I'm worried about.