Determining when an acknowledgement is created during a contribuion and moving it to a new spot!

Normal 0 false false false EN-CA X-NONE X-NONE MicrosoftInternetExplorer4

I originally posted this over in Development but I think it might be more suitable over here!

I'm hoping someone can help me out with a change we are making!  We are changing our procedures related to the posting of donation batches and want to ensure that we can't print acknowledgements (tax receipts) until AFTER a batch has been posted.

Right now it appears we can print acknowledgements as soon as we close the batch.  Does anyone know where we might be able to alter this in the process.  Securities perhaps? or a System Table??

Thanks,

Teri

Parents
  • Former Member
    Former Member $organization

    There's not anywhere in system tables or security settings. I've recently been looking into our custom acknowledgement report so I may be able to help. You will have to know SQL or pay someone who does to write this for you.

    You can print acknowledgements once they are saved to the database. (After you close a controlled batch, or once you save to the database in an uncontrolled batch). Somewhere in LP_Acknowledgement_letters (or your custom version), or perhaps multiple places, add to the WHERE clause that post_no on the transaction must NOT be Null. This would be pretty complicated.

    It may be easier to implement a process where you only print letters from yesterday and before every morning. I don't know how much volume you're dealing with though.

    Ann

  • Thanks Ann,

    What we were after is a fail safe to ensure that everything was signed off on by our finance team (who will be posting batches going forward) before a receipt is issued.   We do our receipts weekly so it might be as simple as changing the dates on the report to not include the prior days batches and catch those the following week.

    That said, I'll see what our IT team thinks about the WHERE clause.  It makes sense when I read it but it putting into place might be harder than it sounds.

    Thanks for your help!

    Teri

     

Reply
  • Thanks Ann,

    What we were after is a fail safe to ensure that everything was signed off on by our finance team (who will be posting batches going forward) before a receipt is issued.   We do our receipts weekly so it might be as simple as changing the dates on the report to not include the prior days batches and catch those the following week.

    That said, I'll see what our IT team thinks about the WHERE clause.  It makes sense when I read it but it putting into place might be harder than it sounds.

    Thanks for your help!

    Teri

     

Children
No Data