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!!! :)
I actually just had a gift with that issue! I ended up having to "refund" the money from the individual and then use a separate payment for the company, but that's a hassle (and this, thankfully, doesn't often happen to us). Assuming there is an existing record for the company (with an email tied to it) could you direct them to create an account for their company (not themselves) and if needed use the "Forgot Login" to prompt them to create a new password for the company record? That might require a bit more effort on your part (at least until they start remembering to log in as the company) but it's probably easier than moving funds around!
I thought about this! Making some very visible instructions for how to do this on the payment page and staying on top of the org logins...The biggest problem is that not all of them have standing constituent records in our system.