Month: January 2021

Link to Pay

We’re rolling out a new feature for statements, dubbed “Link to Pay.”

Some background. For some time now, we’ve offered the ability to send statement notifications by email. The statement notification has a link, that enables the congregant to pull down a statement. That statement is exactly what would have appeared if you’d printed it in the office.

Similarly, we offer a member portal. With a user id and password that we generate, any of your members are able to log in, edit family information, pull statements, and conduct financial transactions. Included, too, is a member search.

This new feature, “link to pay,” combines these capabilities. Within the emailed statement notification, you may include a link that automatically logs the person into the respective account. No password needed. In fact, it goes one step further. It sends your congregant directly to the payment page within the member portal.

To see this feature in action, please view this video.

Link to Pay. Automatically log into the member portal from the statement notification.
Link to Pay

As the video shows, there is a small but key setup item in the email template. Feel free to contact us if you’d like some help in getting that ready.

Five Enhancements

We have five enhancements to show and explain. In no particular order, they are as follows.

On the member query, you can now enter part (or all) of a family code as your search criteria. This might be especially useful if you’re intending to send an email via ShalomCloud to members of a specific family, who may have different last names.

Also on the member query, specifically the part of the screen used to send emails. Until now, the email addresses were placed into a text box. If you wanted to avoid sending content to one or several of the selected members, you had to find the respective email addresses and delete them from the screen. Now, you can use the check-boxes on the right of the screen to effect that selection.

Turning our attention to Yahrzeits — in the case where

  • the person passed away on February 29 (of a leap year, of course), and
  • there are observers by Gregorian date, and
  • the current year is not a leap year

the system works correctly if you pull a list for February 1 through February 28.

The “all-children report” now includes a record count.

For those who use our QuickBooks Desktop integration — you can now query financial transactions by the batch code. Furthermore, the batch code appears on the CSV exports. The batch code does not have to be complete. For example, you could query on something like 2020-12-20, and that will pick up all all batches from that day, such as 2020-12-20-1-CHK, 2020-12-20-2-CRD, etc.

If you’d like to see any or all of these changes in action, have a look at this presentation.