Actions on a Receipt

A Receipt record has actions for working with that one receipt: creating its .pdf again, emailing it, marking it as emailed or printed when you sent it yourself, and voiding it. This article explains each one. It is written for the staff who run receipting and for Salesforce administrators. To work with many receipts at once, use Batch Receipts.

All of these actions need the Receipt User or Receipt Admin permission set. Without it, they show "You don't have permission to perform this action."

Create PDF

The Create PDF button creates the receipt's .pdf again from its receipt template, and shows "… has been created." with the file name.

• It uses the template's current content and the current charity details. Use it after fixing a template, or when a receipt's .pdf is missing.
• To create the missing .pdfs of many receipts at once, use Receipt Settings > App Utilities > Create Missing .pdfs instead.

Email Receipt

The Email Receipt button emails this receipt to the donor, with its .pdf attached, through Salesforce email. It always uses Salesforce, even when Send Emails Using is set to "Amazon SES".

1. The confirmation screen shows who the email goes to: the donor's name and email address. When Enable Receipting Account is on, it also shows the sending organization's name and email address.
2. Click Email Receipt. The screen says "The receipt will be emailed in a moment."

The action refuses to email the receipt when:

Message	Reason
"Cannot email this receipt because the .pdf is not created."	The .pdf doesn't exist yet. Use the Create PDF button first.
"Cannot email this receipt because the donor email address is missing or the donor receipt delivery is not "Email"."	Update the receipt's Donor Email and Donor Receipt Delivery, or void it and issue a replacement.
"Cannot email this receipt because the email template is missing."	Set the receipt's email template.
"Cannot email this receipt because it's already been emailed."	The receipt was already emailed and Enable All CRA Rules is on. Acknowledgments can always be emailed again.

Emails sent this way count toward the Daily Email Limit and Salesforce's daily email allowance. See Email Setup.

Set as Emailed and Set as Printed

Use these when you sent a receipt yourself, outside the app. For example, you downloaded its .pdf and emailed it from your own mailbox, or printed and mailed it.

1. Download the receipt's .pdf from its Files and send it.
2. Click Set as Emailed or Set as Printed, then confirm.

The receipt is then counted as delivered, and Batch Receipts no longer offers it for emailing or printing. The actions refuse a receipt that is "Voided" or has no .pdf, and a receipt that is already set as emailed (or printed): "Receipt is already set as emailed." (or printed).

Void Receipt

The Void Receipt button cancels the receipt, after you confirm.

• Its status becomes "Voided", and its .pdf is re-created in the background so it shows as voided.
• If the receipt had been emailed, the action offers to email the voided receipt to the donor. Click Email Voided Receipt, or close the window if you don't want to.
• Its gifts can then be receipted again with the New Receipt button. The Receipt Eligibility article explains how voided gifts are treated.

A receipt that is already voided can't be voided again: "The receipt has already been voided."

Troubleshooting

Symptom	Check
The emailed receipt shows old wording or old charity details	The .pdf was created before the change. Use the Create PDF button, then email it again if allowed.
The Email Receipt button refuses to send	Read the message; the table under Email Receipt explains each one.
The Set as Emailed button or the Set as Printed button says it can't proceed	The receipt is "Voided" or has no .pdf. Use the Create PDF button first, or issue a new receipt.
The email never arrived	Check the sender mailbox for a bounce notice, and that the receipt's Donor Email is correct. See Email Setup.
"You don't have permission to perform this action."	Assign the Receipt User or Receipt Admin permission set. See Permissions.