When commiting a batch and PaperSave is in use backups are attached to the wrong gifts

Sofia Durkee:
Would like to know if anyone is using PaperSave and also is using the gift batch entry. The system is having problem connecting the new gift id created when committing a batch with a system record id that has the same number as the new gift id created by the batch. Therefore, attaching the documents to gifts entered at an earlier date for a different constituent. How have you fix the problem?

 This is very likely a problem that needs to be addressed by PaperSave support.  BUT before you go there, let me just ask if you are new to using batch entry to attach gifts?  It can be confusing at first and I have had many users come to me in a panic because they thought they were attaching documents to the wrong gifts.

 I would also ask if you are manually assigning gift IDs or if you are letting the system automatically create one.  Also, do all gifts have IDs?  If you only recently started adding these, I would go back and make sure that all past gifts have an ID - probably import (this is us, we had a problem with PaperSave, of course, and had to start using gift ID, it seems to prefer this to import ID which had been our preferred method) .

If none of those answers lead you to a fix, then you need to work with PaperSave support on this.

Sofia Durkee:

I have been talking to PaperSave and Blackbaud and they recommend to go to the business rules and uncheck the generate gift id. We have always use the Gift ID.  

When we import a batch, the gifts on the new batch are attaching to documents that were scanned earlier.   

 Eek.  That is the exact opposite of the solution they had for us!  We were getting an error when committing the batch and they told us to CHECK the box so that it would generate IDs. [:^)]