It contains all the reports you're used to seeing in the old Box Office Reports tab, and more.

Having Payment Transaction records for all Donations increases your reporting capabilities in PatronManager. To help you use the new data that the system has been creating for you since the July 2019 release, the Financial Reports tab includes two new options:

CRM Snapshots are a great way to run commonly-used reports like a LYBUNT for your donors, or a list of patrons who bought tickets but haven't donated.

Previously, Snapshots could only take Donations into account if they had been processed, a.k.a. if the Probability was 100% (equivalent to Posted or Closed/Won).

Now, CRM Snapshots that reference Donations allow you to choose the Probability percentage to include. They default to 100%, which will include only those Posted Donations as in the past, but you can now adjust that if you want. For example, to include Pledged and Pending Donations, you'd set the Probability to 90%.

We've added new fields to the Ticket Order Item object to give you easier access to data when cross-filtering in reports. For example, you can now create an email list using a Contact report, and cross-filter to only show Contacts with tickets to Events in a specific venue. The newly-added Ticket Order Item fields are:

• Event Instance Date
• Event Instance Name
• Ticket Allocation Name
• Ticketable Event Type
• Venue Name
• Ticket Order Status

For more information about using cross-filters, check out this article.

You can now add custom fields to the Benefit object and edit those fields directly on a Benefit record. This is useful if you need to track whether certain perks have been awarded to members outside PatronManager ticketing (e.g. all members at a certain level receive a gift bag). You could even add an auto-number field in order to mark each Benefit with a unique ID, which you could then print on a membership card.

Ready to get started? Here are step-by-step instructions.

Ticket Orders containing a large number of tickets sometimes failed to send a confirmation email due to a timeout error. Confirmation emails with large numbers of tickets listed were also a bit overwhelming to read. Now, confirmation emails for Ticket Orders that contain 20 or more items and do not contain a subscription will show a summary, rather than line-item detail:

If you need to send specific seat information to patrons for a large order containing only single tickets, you'll be able to create a custom confirmation email with that level of detail, and send it as a follow-up email from the Ticket Order.

Here's how to do that.

Your Accounts already had a field called "Amount Donated This Fiscal Year", which adds up the total amount of Closed/Won Donations in your current FY, except for any Donation Record Types you marked as excluded in the Organization Settings tab.

Now, you can also easily see the "Amount Donated Last Fiscal Year" as well -- and like the field for this FY, it will update automatically with each new fiscal year.

PatronManager provides a Mobile Box Office app for Android tablets, which pairs with the Wisepad 2 credit card terminal (only available for Bluefin).

Your patrons will now be able to tap to pay with contactless cards, and insert the chip on chip-enabled cards. For credit cards with these enhanced features, swiping the magnetic stripe will no longer work on the Wisepad 2.

There was a problem involving Ticketable Events that had a period followed by many characters in the Event Name field. When uploading Managed Content (images for the new public ticketing site) for those Ticketable Events, the system attempted to convert the characters following the period into a file extension, which caused the upload to fail.

There was a problem affecting a small subset of Ticket Orders, where adding a Contact immediately before saving the Ticket Order as a reservation caused the status change to fail. The Ticket Order would then revert back to Draft status, requiring the user to try again.

The Tax Deductible Amount field was not calculating correctly on the new Enhanced Donation Forms. This has been fixed; to learn more about Enhanced Donation Forms, check out this article.

Certain scenarios (double-clicking, refreshing the page, multiple users qualifying an Order at the same time...) could sometimes cause duplicate PatronTicket Donations when qualifying a Ticket Order.

As a best practice, we recommend attaching a Contact to most Donations, using the "Donor" field. There are some kinds of Donations where that doesn't make sense, though -- for example, Corporate Donations and Grant Payments. Previously, Donations without a Donor could not be refunded.

The new PTS used to show the "Name" field on the venue, which is a field meant for internal use. The "Display Name" field is the venue name that's intended to be visible to the public.

You alerted us to a bug that prevented the new PTS from recognizing certain limitations you can define on a Discount Code:

• Minimum Number of Tickets
• Minimum Number of Unique Events
• Single Transaction Limit

In the Fee Setup tab you can choose to group several fees together, and label the grouping (for example, you might combine an Item Fee and a Facility Fee into "Per-Ticket Fees").

If you use sales tax, you can also customize how that appears to your patrons via the "Sales Tax Label" field in the PatronTicket Settings tab.