Feature area
Sapling connects gift entry, recurring giving, receipt templates, generated receipt files, delivery history, refunds, failed payments, soft credits, passthrough gifts, year-end statements, and Sapling Pay context.
Why it matters
Gift work is where fundraising, finance, and stewardship collide. Sapling is designed so the gift record does not stop at amount and date: it can carry donor context, payment truth, receipt status, recurring cadence, refund history, soft crediting, passthrough logic, year-end statements, and the review state staff need to explain what happened later.
Gift operations preview
Sapling keeps receipt status, recurring commitments, refund review, year-end statements, soft credits, passthrough context, and Sapling Pay transaction truth beside the gift record.
Needs receipt
18Generate, email, print, or mark sent
Recurring watch
7Past-due or card-update attention
Refund review
3Original gift, notice, and net impact preserved
Year-end ready
246Donor statements by year and gift scope
Gift review queue
Sapling gifts are meant to be understandable after the fact. A staff member should be able to see the donor, amount, date, campaign, fund, payment method, receipt treatment, recurring status, related credits, and exceptions without chasing spreadsheets or processor screens.
Receipt work is built around reviewable queues and repeatable templates. Teams can generate receipts, email them, download PDFs, batch-generate missing receipts, export generated receipts, and keep delivery state attached to the gift.
When a gift changes, Sapling should not erase the original story. Voiding a receipt returns the gift to needs-receipt state with a recorded reason. Refunds create linked reversal context, support partial or full returns, and can generate donor-facing refund notices.
Recurring commitments are derived from gift records and grouped by donor, cadence, amount, fund, and campaign. Sapling can flag past-due expected gifts, estimate monthly recurring revenue, and show contact-level recurring giving without separating the relationship from the payment pattern.
Nonprofit gifts often involve more than one party. Sapling is built to keep DAFs, passthrough entities, soft credits, matching gifts, anonymous gifts, sponsorships, event gifts, and special receipt treatment connected without flattening the donor story.
Receipts and statements are not just one-off documents. Sapling supports year-end donor statement queues by year and gift scope, manual marking for printed or mailed statements, and finance-friendly context around exports, refunds, payments, and reconciliation.
Keep exploring