RENXT JustGiving Integration: Processing Data And Donations 7499

RENXT JustGiving Integration: Processing Data And Donations

Published

Suggested steps for processing donations and data from Blackbaud Peer to Peer Fundraising, powered by JustGiving.

As organizations find success fundraising on Blackbaud Peer to Peer Fundraising, powered by JustGiving they are also developing new policies and procedures. One of the processes you may need to build is for data and gift processing. To give you a starting place, I have outlined the big picture steps I would use for gift processing as it relates to JustGiving. As always, feel free to change this to fit your organization.

The steps as I give them have intentionality in the order. By following this order, I try to account for the following: duplicate records, data only stored in Web View ( Peer to Peer tile and Attachments,) reports needed for reconciliation.

In Web View:
  1. Go to Data Health>Possible Duplicates and look for any duplicates that may have been created in the import process.
    1. Merge any identified duplicate records, moving the unapproved gifts from the source record to the target record More about Possible Duplicates here.
  2. Go to Gift Management
    1. Edit any batch details, as necessary.
    2. Adjust/edit any gift details, as necessary.
    3. Approve the gift batch.
      1. Since JustGiving creates a new batch every 24 hours, consider processing JustGiving donations each morning for the previous day’s gifts. This will enable you to keep gifts in batches grouped by date. You may consider doing this more often if the data is needed throughout the day for something like a giving day.
In Database View:
  1. Go to Reports>Financial Reports>Cash Receipts Journal, this will be the report you provide to the financial office for reconciliation purposes. This takes the place of the Batch Commit Report that pops up after committing a batch in Database View. Please note that depending on your time filter, there could be gifts that appear in the Cash Receipts Journal and the Batch Commit Report.
  2. Go to Admin>Duplicate Constituent Management Tool
    1. Run the tool and merge the records according to your policies and procedures. More about the Duplicate Constituent Management Tool.
    2. Decide if you are going to keep, delete or mark inactive (or some combination) the source/duplicate record.
Deciding when to delete the source/duplicate record, follow your organization’s policies and procedures. (Some organizations choose to keep the source record for a small period and delete it later.)

I strongly recommend using both Web View and Database View duplicate management tools – start with Web View and then move Database View. To ensure the full integrity of the record, I recommend deleting the record in Database View. As a tip, once all duplicate record merges are complete, mark the record inactive. Then, pull all inactive records into a Constituent Query and delete the records via the tool of your choice: one at a time or via Global Delete (be sure you use a static query for Global Delete.)

What procedures have you developed for processing data from Blackbaud Peer to Peer Fundraising, powered by JustGiving? What tips, tricks, secrets would you share with others? Let me know in the comments below.

Leave a Comment

Check back soon!

Share: