Every Receipt Is a Stewardship Moment: Rebuilding Donation Processing at Texas A&M Foundation

A donation receipt is a legally required document. The IRS mandates that donors receive written acknowledgment for charitable contributions. Most organizations treat this as compliance paperwork. Something that has to go out. A box to check.

Texas A&M Foundation saw it differently.

Every receipt is a touchpoint. A donor just made a gift, an act of generosity and trust. The receipt is often the first communication they receive in response. What should that moment feel like?

If the receipt arrives three days later, formatted in generic type with a third-party vendor's aesthetic, it communicates: "We processed your transaction." If it arrives within minutes, beautifully branded, clearly formatted, and personally addressed, it communicates: "We received your gift, we value your generosity, and we represent it with the same care you showed in giving."

That distinction is the difference between compliance and stewardship.

The Vendor Problem

The Foundation used an external vendor for receipt processing. The system worked, in the narrowest sense. Receipts went out. Donors received them. The IRS requirements were met.

But the problems were significant. The vendor's output had inconsistent branding. Receipts did not look like they came from the Foundation. They looked like they came from a document processing company, because they did. Any update to the receipt design, language, or format required coordinating with the vendor. Turnaround was slow. Control was limited.

There was no instant verification capability. When the Gift Administration team needed to confirm that a receipt had been sent, or pull up a copy for a donor who called, they had to go through the vendor's system. Simple questions required unnecessary steps.

And the cost was $3,600 per year. Not a massive line item, but real money for a service that did not meet the Foundation's standards.

Rethinking the Approach

The strategy was to treat every receipt as a stewardship communication. That meant the Foundation needed full control over the design, timing, and delivery. It meant branded formatting that matched the Foundation's visual identity. It meant speed: a donor should receive their receipt quickly after making a gift. And it meant the internal team should be able to verify and retrieve any receipt instantly.

The experience I was designing started at the moment of giving. A donor completes a gift. Within minutes, they receive a receipt that looks and feels like it belongs to the Texas A&M Foundation. The formatting is clean. The information is precise. The branding is consistent. For the donor, it reinforces the relationship. For the Gift Administration staff, any receipt is instantly verifiable without vendor intermediation.

Building the System

I was the sole developer. The project took about six months, with stops and starts due to the complexity of the requirements and the need to work around other organizational priorities.

The architecture is event-driven. When a gift is recorded in Salesforce, an Apex trigger fires. That trigger sends the gift data to a Pipedream orchestration layer, which routes the information to a Node.js processing engine.

The processing engine is where the complexity lives. 700 lines of conditional logic handle the full range of scenarios the Foundation encounters:

Multiple gift types, each with different receipt requirements. Cash gifts, stock transfers, planned giving instruments, matching gifts. Each type has specific language and formatting requirements.

IRS compliance rules that vary by gift type and amount. Certain thresholds trigger additional disclosure language. Quid pro quo contributions (where the donor received something in return, such as event tickets) require specific fair market value statements.

Dual branding. The Foundation and the University have distinct visual identities, and receipts needed to reflect the appropriate branding based on the context of the gift.

International addresses with formatting conventions that differ from domestic standards.

The processing engine generates branded PDFs using Handlebars templates and Puppeteer. Each receipt is rendered to Foundation design standards with the donor's specific information, the correct gift-type language, and the appropriate compliance text.

Generated PDFs are stored in OneDrive and transferred via SFTP to Salesforce Marketing Cloud for email delivery. Gift Administration staff can access any receipt instantly through the internal filing system.

Overcoming Resistance

The project faced initial stakeholder resistance. There was understandable caution about replacing a functioning vendor system with a custom-built solution. "What if it breaks? Who maintains it? The vendor is reliable."

These were fair questions. I addressed them by building incrementally and proving reliability at each stage. Test batches were processed and reviewed by the stewardship team before any donor-facing receipts were generated. Edge cases were identified and handled. The team saw the quality of the output and the speed of the processing before committing to the full transition.

By the time the system was fully operational, the response from the team was straightforward: "Loves it."

What Happened

The system processes approximately 10,000 receipts annually at a cost of $400 per year. That is an 88% cost reduction from the $3,600 vendor fee.

But cost reduction was not the point. The point was control, quality, and speed.

The Foundation now has complete control over the receipt experience. Design updates happen internally, immediately. New gift types or compliance requirements are handled by updating the processing logic, not by submitting a vendor ticket and waiting.

Gift Administration staff can verify any receipt instantly. A donor calls and asks about a receipt from last month. The answer takes seconds, not a vendor inquiry.

The branding is consistent. Every receipt looks like it came from the Foundation, because it did. The donor experience at the moment of giving acknowledgment now matches the caliber of the Foundation's broader communications.

What This Reinforced

This project reinforced something I keep returning to: the distinction between viewing a communication as a transaction versus viewing it as a relationship touchpoint.

A receipt is a transaction in the legal sense. But in the context of donor stewardship, it is a moment. The first response to an act of generosity. The way an organization handles that moment says something about how it views the relationship.

The strategy was: treat every communication, even the compliance-driven ones, as an expression of the relationship. The experience was: fast, branded, precise, personal. The systems were: event-driven automation that makes the strategy and experience reliable at scale.

Systems serve experiences. Experiences express strategy. When all three layers align, even a donation receipt becomes a stewardship moment.