Receipt Settings

This page explains every Dryad Receipting setting: what it controls, what values it accepts, what it defaults to, and how the app behaves when you change it. It is written for Salesforce administrators. For a plain-language overview of the objects and fields, see the Data Model page.

Before You Change Anything

Where Settings Live

• All settings are stored in a single hierarchy custom setting, Receipt Settings (dryad__Receipt_Settings__c). The record is created automatically when the package is installed, with the defaults listed on this page.
• Edit settings on the Dryad Receipting Settings page, not through Setup > Custom Settings. The page needs the Receipt Admin custom permission, which is included in the Receipt Admin permission set. The left-hand menu has these items:
  • the three settings groups (Charity Information, General Settings, Advanced Settings)
  • Templates
  • Field Mappings
  • Scheduled Jobs
  • App Utilities
  • App Details
• Yes/No settings are stored as the text values "Yes" and "No", not as checkboxes. A blank Enable … setting is treated as "No".

Keep exactly one settings record, at the organization level. Apex reads "the first" Receipt Settings record it finds. Formula fields read the hierarchy ($Setup), which prefers profile- or user-level records. If you add profile or user overrides, Apex and formulas can disagree, and different users can see different receipt statuses.

Changes Take Effect Immediately

Many settings are used by formula fields, so changing them recalculates values across your whole org straight away:

• Eligibility. Receipt Status on Opportunities, Payments and Recurring Donations is a formula that reads General Options, Minimum Receipt Amount, and the Household and In-Kind record types. Changing these can instantly move unreceipted gifts between "Eligible" and "Ineligible".
• Existing receipts. The charity details, signature, logo, sender email and formatted dates on a Receipt are formulas too. Changing your charity address or date format changes those field values on existing Receipt records. PDFs that were already generated don't change, but any PDF you regenerate later will use the new values.
• Indexed fields. If Enable Index Optimization is on, run App Utilities > Refresh Indexed Fields after changing any setting that affects eligibility, so the indexed copies of Receipt Status match the formulas.

Receipting Accounts Override Many Settings

When Enable Receipting Account is in use, a gift's Receipting Account supplies its own charity details, numbering, sender email and templates. Settings on this page are the fallback. Where the fallback works differently from field to field, the table below says so.

Charity Information

The details of your primary charity, printed on every receipt that doesn't use a Receipting Account. They reach receipts through formula fields on the Receipt object (for example Charity_Name__c, Charity_Address_Multiline__c and Location_Issued__c). Flows can also read them through the Get Receipt Settings invocable action.

Primary Charity Details

Setting	How It Works
Name	Your charity's legal name. Receipt field: Charity Name. If a receipt has a Receipting Account, the Account's Name is used instead, always (there is no per-field fallback).
Registration #	Your CRA registration (business) number, which is required on official receipts. Receipt field: Charity Registration #. With a Receipting Account, the Account's Charity Registration # is used, even if it is blank.
Phone	Receipt field: Charity Phone. With a Receipting Account, the Account's standard Phone is used.
Website	Receipt field: Charity Website. With a Receipting Account, the Account's standard Website is used.
Logo	The publicly reachable URL of your logo image. The Settings page shows a preview and lets you pick an image. Receipt field: Charity Logo URL, used in templates as an <img> source. With a Receipting Account, the Account's logo is used if it has one. Otherwise the logo here is used.

Primary Charity Address

Setting	How It Works
Street	Combined into the Receipt fields Charity Address (one line) and Charity Address Multiline (with <br/> line breaks, for templates). Location Issued (City, Province), which CRA requires on official receipts, is built from City and Province/State. With a Receipting Account, the Account's standard Billing Address is used for every part of the address, even parts that are blank.
City
Province/State
Postal Code/Zip
Country

Authorized Individual

Setting	How It Works
Name	The person authorized to sign receipts. Receipt field: Authorized Name. With a Receipting Account, the Account's value is used if it has one; otherwise the value here is used.
Title	That person's title. Receipt field: Authorized Title. Same fallback as Name.
Signature	The publicly reachable URL of a signature image. The Settings page shows a preview. Receipt field: Authorized Signature URL. Same fallback as Name.

General Settings

Receipt Details

These settings control the numbering of official tax receipts (types "Single Receipt" and "Consolidated Receipt"). The number becomes the Receipt record's Name. It is assigned automatically when the receipt is inserted, while the settings record is locked, so receipts created at the same time never get the same number.

Setting	How It Works
Next Receipt #	Default: 1. The number the next official receipt will get. It goes up by 1 for each receipt created without a Receipting Account (or whose Receipting Account has no Receipt Next #). Set this once, when you go live (for example, to continue from your previous system's numbering). Never lower it. Receipt names aren't enforced as unique, so lowering it creates duplicate receipt numbers.
Receipt Prefix	Optional. Text placed in front of the number, for example R- or 2026-. The full receipt number is cut off at 80 characters.
Receipt # Length	Pads the number on the left to a fixed length. Both settings must be filled in for padding to apply. Example: Length 6 and Padding 0 turn receipt 123 into 000123, so with prefix R- the number is R-000123. A number that is already longer than the length isn't cut short. Padding applies only to the main receipt sequence. It doesn't apply to Receipting Account numbers, acknowledgments or giving summaries.
Receipt # Padding
Minimum Receipt Amount	Default: 20. Blank is treated as 0. The smallest receiptable amount that gets an official receipt. Acknowledgments and giving summaries are never affected. Single receipts: a gift whose Receiptable Amount is below the minimum gets the status "Ineligible - Receipt amount is below minimum". Consolidated receipts (and recurring donations that are consolidated): each gift stays eligible. The minimum is checked against the total when the receipt is created. If the total is below the minimum, the receipt is simply not created, and the gifts stay eligible for a later run.

Non-Receipt Details

Numbering for documents that aren't tax receipts. They use a separate sequence, so your official receipt numbers have no gaps.

Setting	How It Works
Next Non-Receipt #	Default: 1. A single counter shared by acknowledgments and giving summaries. It goes up by 1 for each one created. These documents always use this counter, even when the gift has a Receipting Account, and they are never padded.
Acknowledgment Prefix	Optional. Default: ACK-. Placed in front of acknowledgment numbers, for example ACK-42.
Giving Summary Prefix	Optional. Default: SUM-. Placed in front of giving summary numbers, for example SUM-43. Because the counter is shared, acknowledgment and summary numbers interleave.

General Options

Setting	How It Works
Enable All CRA Rules	Options: Yes or No. Default: "Yes". Turns on the stricter Canada Revenue Agency checks. When "Yes": Donor address required. Official receipts need the donor's street, city, province/state and postal code. For households these come from the primary contact's mailing address; for organizations, from the Account's billing address. Gifts with an incomplete address get the status "Ineligible - Donor address missing". No re-emailing. An official receipt that has already been emailed can't be emailed again from the Email Receipt button. To send another copy, void the receipt and issue a replacement. Acknowledgments can still be re-sent. The advantage rules (the 10%/$75 and 80% thresholds) always apply, whatever this setting says.
Date Format	Options: "yyyy-mm-dd" (default), "mmm dd, yyyy", "dd/mm/yyyy" or "mm/dd/yyyy". Controls how dates appear on receipts, through the Calculated_…_Date__c formula fields on Receipt and Receipt Item and the PDF renderer. For 5 March 2026 that gives 2026-03-05, Mar 05, 2026, 05/03/2026 or 03/05/2026. A blank value behaves like "yyyy-mm-dd". The mmm format always uses English month abbreviations, even on French receipts. Pick a numeric format if you issue bilingual or French receipts.
Concatenate GAUs	Options: Yes or No. Default: "Yes". Blank is treated as Yes. When "Yes", each time a receipt is created, Dryad Receipting reads the gift's NPSP GAU Allocations. It writes them to GAUs and GAUs with Amounts on the Opportunity (or Recurring Donation), so they can be copied to the receipt and printed. When "No", those fields are left as they are, for example if you maintain them yourself.
Enable Receipt by Payment	Options: Yes or No. Default: "No". Chooses whether receipts are created from Opportunities ("No") or from individual Payments ("Yes"). This is a fundamental choice, so decide it before you go live. "No": Opportunities can be eligible. Every Payment shows "Ineligible - Payments cannot have receipts". "Yes": Every Opportunity shows "Ineligible - Only payments can have receipts". Payments are evaluated individually and must be marked "Paid". It also changes which options the Create Receipt buttons and the Batch Receipts screens offer, which field mappings appear on the Field Mappings tab, and what the scheduled daily receipt job processes.
Enable Receipting Account	Options: Yes or No. Default: "No". Turns on support for issuing receipts from more than one charity (several registration numbers in one org). When "Yes": the Batch Receipts screens offer Receipting Account as a way to select gifts the Set Receipting Account Details button becomes available on Accounts the email actions take the Receipting Account into account The receipt formulas always use a gift's Receipting Account field if it's filled in. This setting controls the screens and actions, so leave that field blank when the setting is "No".
Enable RD Consolidation	Options: Yes or No. Default: "No". Applies to donors whose Receipt Occurrence is "Consolidated" and who have several recurring donations. When "No", each recurring donation gets its own consolidated receipt. When "Yes", all of the donor's consolidated recurring donations go on one receipt, provided they share the same currency, the same assigned receipt template and the same receipt period.
Enable Single Receipts for RDs	Options: Yes or No. Default: "No". "No": gifts that belong to a recurring donation are always "Eligible for Consolidated", whatever the donor's Receipt Occurrence. The Minimum Receipt Amount is then checked on the consolidated total. "Yes": those gifts follow the donor's Receipt Occurrence. A donor set to "Single" gets a receipt for each installment, and the Minimum Receipt Amount applies to each one.
Enable Preview Report	Options: Yes or No. Default: "No". When "Yes", the Batch Receipts screens that create single, consolidated and recurring donation receipts show the Create Preview Report button whenever there are fewer eligible records than the Preview Report Limit. The report is only built if you click it. It is built in the background, with a progress ring, and a View Report link appears when it's complete. Up to the Table Record Limit: the button appears above the table of records. The report is for checking only; you still choose which records to receipt. Above the Table Record Limit: the button appears on the confirmation screen. If you build the report, "Create Receipts" waits until it's complete and then receipts exactly the records in the report. If you don't, receipts are created from your selection, as before. Creating giving summaries doesn't offer a preview report. When "No", the button isn't shown. After an upgrade the setting is "No" (or blank, which is treated as "No"), so set it to "Yes" to offer the preview report.
Require Payment	Options: Yes or No. Default: "Yes". When "Yes", a "Closed Won" Opportunity is "Ineligible - Payment missing" if it has no Payment records or still has an amount outstanding. In-kind gifts (see In-Kind Gift Record Type) are exempt. Set it to "No" if you don't use NPSP Payments, or if Payments are created after the gift is closed.
Receipt File Repository	Options: "Salesforce" only. Where receipt PDFs are stored. PDFs are always saved as Salesforce Files linked to the Receipt. The Amazon S3 storage option is currently disabled.

Email Settings

Setting	How It Works
Send Emails Using	Options: "Salesforce" (default) or "Amazon SES". The service used when you email receipts in bulk from Batch Receipts > Email receipts, or in the email step of Create, email, and print receipts. Salesforce: emails go out through Salesforce. They count against Salesforce's own daily email allowance and the Daily Email Limit. Amazon SES (Dryad Mailer): creates an "Email" record with one Email Recipient per receipt, and sends through Amazon Simple Email Service using the Named Credential. Delivery, open, bounce and complaint notifications come back as Email Event records. This suits high volumes and gives delivery tracking.
Sender Email Address	The default "from" address. It feeds the Receipt formula Sender Email, which a Receipting Account's Receipt Sender Email overrides when it has one. With "Salesforce" sending, it must match an Organization-Wide Email Address that is verified and available to all profiles. If no match is found, the email fails with "The sender email address is not specified." With "Amazon SES", it must be a verified identity in Amazon SES.
Configuration Set	Amazon SES only. The name of the SES configuration set that publishes delivery and open events back to Salesforce (for example dryad-mailer-tracking). Without it, mail is still sent, but the Email Recipient tracking flags won't update. Leave it blank if you use Salesforce sending.
Named Credential	The API name of the Named Credential that authenticates to Amazon (for example Amazon_SES_NC). It is used for two things: sending mail through SES the Validate Email buttons (on a Contact and from Contact list views), which call the Amazon SES email-insights API and set Email Validation Status on Contacts Leave it blank if you use neither.

Advanced Settings

Performance, safety limits and org-specific configuration. The defaults suit most orgs. Change them mainly for large data volumes, or if your NPSP record types use non-standard names.

Setting	How It Works
Table Record Limit	Default: 100 (also used when blank). Range: 10–1,000. Recommended: 100. Decides whether the Batch Receipts screens (creating receipts and giving summaries, emailing, merging and printing) show a table of the eligible records: Up to this many records: they are listed in a table, and you choose which ones to process. The table shows at most this many rows. Above it: no table is shown. You see the record count (and possibly the Create Preview Report button, see Enable Preview Report), and all eligible records are processed as a background job. Printing above it: receipts can't be printed one by one. Print individual receipts offers to merge them instead, and you then print them with Print merged receipts. The records you pick from the table are also processed as a background job, and the last screen shows its progress. Raising this limit lets you pick from bigger lists, but the screens take longer to load.
Preview Report Limit	Default: 10,000. Range: 10–50,000. Recommended: 10,000. Only applies when Enable Preview Report is "Yes". In the Batch Receipts screens, when the number of eligible records is below this limit, you can build a preview report of the records before you confirm. At or above the limit, the Create Preview Report button isn't shown.
Daily Receipt Limit	Default: 100,000. Blank is treated as 200,000. Range: 1–500,000. Recommended: 100,000. A safety limit against runaway receipt creation. Before inserting receipts, Dryad Receipting counts Receipt records created in the last 24 hours, a rolling window that also counts deleted receipts. If the new receipts would push that count over the limit, the whole insert is refused with an error, and no receipts from that request are created.
Daily Email Limit	Default: 5,000 (also used when blank). Range: 1–5,000. Recommended: 2,500. Caps how many receipts can be emailed per calendar day when Send Emails Using = Salesforce. Amazon SES sending isn't limited by this setting. The count is kept in Daily Email Total and resets when Daily Email Date is no longer today. Before each send, Dryad Receipting also reserves the capacity with Salesforce. If Salesforce's own daily single-email allowance is lower, that limit is hit first.
Batch Threshold	Default: 100 (also used when blank). Range: 10–200. Recommended: 100. The cut-off between processing records right away and processing them in the background when your own flows or automation use the Create Receipts for Opportunities or Create Receipts for Payments options. Up to this many records are processed straight away, in the same transaction. Above it, a batch job is started and tracked in a Batch Receipt Log. It doesn't apply to Batch Receipts or to the New Receipts button from an Opportunity list view, which always process records in the background and show the job's progress. Raising the Batch Threshold makes small runs quicker, but you risk hitting CPU and SOQL governor limits on gifts with complex data.
Receipt Batch Size	Default: 20. Range: 2–20. Recommended: 20. The scope size (records per execute) for Dryad Receipting's batch jobs: creating receipts, consolidated and recurring receipts, generating PDFs, the scheduled daily job, and creating missing PDFs. Generating a PDF is resource-heavy, so lower this (for example to 5–10) if batch jobs fail with CPU-time or heap-size errors.
.pdf Merge Batch Size	Default: 100. Range: 2–100. Recommended: 100. How many receipt PDFs are combined into each merged PDF when you merge receipts for printing. The merge is done by Dryad's web service (it needs the API Key). Larger files mean fewer downloads, but each download is bigger and slower. If merges often fail because the merge service took too long to respond, try a lower value.
.pdf Segments	Default: 3 (also used when blank). Range: 1–5; values above 5 are treated as 5. Recommended: 3. How many background jobs create receipt PDFs at the same time. Each bulk PDF run (after batch receipt creation, the scheduled daily job, or creating missing PDFs) is split into this many segments of roughly equal size, and each segment runs as its own job. Running several at once makes large runs much faster. The run is tracked by one "Create .pdfs" Batch Receipt Log, with a Batch Receipt Log Segment for each job. The log is complete when its last segment finishes. Small runs use fewer segments: a run never has more segments than it has batches of Receipt Batch Size. Salesforce runs at most 5 batch jobs at a time per org. While the segments run, other batch jobs (yours or other apps') may wait in the queue. Lower this setting if that is a problem; set it to 1 to create PDFs in a single job.
Enable Index Optimization	Options: Yes or No. Default: "No". For very large data volumes only. Receipt Status and Payment Date on Opportunities are formula fields, and Salesforce can't index formulas, so queries on them slow down when you have millions of gifts. When "Yes": A trigger handler keeps two plain fields on Opportunity, Receipt Status Indexed and Payment Date Indexed, in step with the formulas. It updates them whenever the Opportunity, its Account or Contact, its Payments, or its Receipts change. The receipt-selection queries filter on those fields instead of the formulas. After turning it on (and after changing any setting that affects eligibility), run App Utilities > Refresh Indexed Fields for the date range you receipt. For the queries to actually be faster, ask Salesforce Support to add custom indexes on the two fields. If an indexed value is out of date, a gift can be skipped or picked up wrongly, so leave this "No" unless you need it.
In-Kind Gift Record Type	Default: InKindGift. The developer name of the Opportunity record type for in-kind (non-cash) gifts. Gifts of this type: are exempt from Require Payment always get a single receipt (they're never consolidated) leave out the advantage sentence (Advantage Text) on the receipt If the value doesn't match a real record type, in-kind gifts are treated like cash gifts.
Household Record Type	Default: HH_Account. The developer name of the Account record type for NPSP households. Many formulas use it to decide where donor details come from: Household Accounts: name, address, email and preferences come from the gift's primary contact. All other Accounts: they come from the Account itself. Consolidated receipt jobs also process households and organizations separately. If this doesn't match your household record type, household gifts are receipted to the Account name and billing address.
API Key	Set at install. Sent as the x-api-key header on calls to Dryad's web services (api.dryadreceipting.com), which merge PDFs for printing, delete stored files, and verify your app edition. Don't change it unless Dryad support asks you to. Your org also needs a Remote Site Setting for that domain (installed with the package).

Templates

The default templates, set on the Templates tab of the Settings page. A Receipt Template is chosen by checking these in order:

1. the Receipt Template field on the gift itself
2. the gift's Receipting Account
3. the settings below

At each step, the receipt type and the donor's language (Donor Receipt Language, which defaults to English) decide which template is used. You can see the result in the Receipt Template Id Assigned formula field on Opportunities, Payments and Recurring Donations.

Setting	How It Works
Receipt Template – Donation (EN / FR)	Sample English and French templates are created at install. Used for official receipts and tribute receipts (Receipt Type = Donation or Tribute). The English template is also the fallback when the Create Missing PDFs utility needs a template.
Receipt Template – Acknowledgment (EN / FR)	Used when Receipt Type = Acknowledgment, which is when the gift, recurring donation, contact or account has the Do Not Receipt Reason "Acknowledgments Only".
Receipt Template – Giving Summary (EN / FR)	Used for giving summaries. These are chosen by the code when the summary is created (Receipting Account first, then these settings), not by the Assigned formula fields.
Email Template (EN / FR)	Sample templates are created at install. The email body used when a receipt is emailed. It is chosen the same way (gift's Email Template Id, then Receipting Account, then these settings) and shown in Email Template Id Assigned. A receipt with no email template can't be emailed; its Delivery Status will show "To be Printed".

App Details

Setting	How It Works
App Edition	Default: Pro. Your Dryad Receipting edition. It is set when you register or verify your edition on the App Details tab, which checks with Dryad's web service using the API Key. Don't edit it by hand.

System and Deprecated Fields

These fields aren't shown on the Settings page. Leave them alone unless Dryad support asks you to change them.

Setting	How It Works
Daily Email Date	The day that Daily Email Total is counting. When it isn't today, the total resets to 0 before the next send.
Daily Email Total	Receipts emailed through Salesforce on the Daily Email Date. It is compared with the Daily Email Limit.
Daily Receipt Total	For information only: the number of receipts created in the last 24 hours, as at the last receipt run. The limit check counts Receipt records directly and doesn't read this field.
Amazon S3 Named Credential	Connection for storing PDFs in Amazon S3. Not currently used, because S3 storage is disabled.
Amazon S3 URL	Base download URL for PDFs stored in S3. Not currently used.
DEPRECATED: Enable Amazon S3	Options: Yes or No. No longer has any effect.
DEPRECATED: Copy Amount to Eligible Amt	Options: Yes or No. No longer has any effect. A blank Eligible Amount now simply means "use the full amount".
DEPRECATED: Suspend Receipt Creation	Options: Yes or No. No longer has any effect.
DEPRECATED: Starting Receipt #	No longer has any effect. Use Next Receipt # instead.