Understanding the Fair Market Value (FMV) Field

When a constituent pays for something and gets a benefit back in return — a meal at a gala, a tote bag with a membership, admission to an event — only part of that payment is tax-deductible. The Fair Market Value (FMV) field is how Humanitru captures the value of that benefit, so the deductible portion of the gift calculates correctly and your receipts hold up to IRS scrutiny. This guide covers what FMV means, where it lives in Humanitru, how the math works behind the scenes, and where it shows up elsewhere in the system.

Fair Market Value is the standard nonprofit and IRS concept used to determine how much of a gift is actually tax-deductible. Per IRS Publication 1771, a donor's deduction for a contribution is generally limited to the fair market value of the contribution minus the fair market value of any goods or services the organization gives back in exchange.

This situation — a donor paying money and receiving something of value in return — is known as a quid pro quo contribution. The classic example from IRS guidance: a donor gives $100 for a concert ticket worth $40. The deductible portion is capped at $60, and because the payment exceeds $75, the organization must furnish the donor a written disclosure stating the deductible amount and a good-faith estimate of the benefit's value.

Why the $75 threshold matters: Any single payment over $75 that's partly a gift and partly payment for goods or services requires a written disclosure statement telling the donor what's deductible. This is separate from the $250 threshold, which triggers the donor's need for a contemporaneous written acknowledgment for any single contribution — quid pro quo or not.

The token exception: Not every benefit counts against the deduction. Low-cost items — a mug or tote bearing your logo, insubstantial benefits under IRS inflation-adjusted thresholds — can be disregarded entirely, meaning the gift is treated as fully deductible even though something was technically given in return. This guide's FMV field doesn't automatically apply these exceptions; if a benefit qualifies for the token or membership exception, your organization can enter $0 for FMV and treat the gift as fully deductible.

The FMV field only appears on transactional Actions — Donation, Membership, and Ticket — since these are the Action types where a constituent might receive something of value back. When you set Type to one of these in the Add/Edit Action modal, three dollar fields appear side by side:

If you leave Fair Market Value blank and save, it's automatically set to $0 — meaning the gift is treated as fully deductible by default. You only need to enter a value when the constituent actually received something back.

• Tax Deductible Amount is not stored in the database. It's a live, client-side calculation — max(0, Amount − FMV) — that recomputes instantly as you edit either Amount or FMV.
• The floor is $0. Tax Deductible Amount can never go negative, even if FMV is entered higher than Amount.
• Manual override available. An admin can enter an explicit Tax Deductible Amount that bypasses the Amount − FMV formula entirely. Once set, the override value displays in place of the calculated figure (stored separately as amount_deductible_overridden). Use this for edge cases the standard formula doesn't handle cleanly — for example, a benefit exception applies, or the organization has already calculated deductibility a different way.
• Locked Actions. If an Action is locked, Amount and FMV become non-editable unless the specific field has been whitelisted for that Action. This protects historical financial records from accidental edits after verification.

Note the cash-donation row: when a donor gives with nothing expected in return, FMV stays at $0 and the full amount is deductible — this is the default behavior and the most common case.

• Eventbrite and Pinecone: these ticketing integrations populate FMV automatically on imported ticket Actions, since both platforms already track benefit value per ticket at the source.
• Notes and reportability: FMV and Tax Deductible Amount are standard reportable fields on any transactional Action — no special setup needed to include them in reports or exports.

• Set FMV at the point of entry for gala, auction, and ticketed-event Actions — it's much harder to reconstruct benefit values after the fact.
• Use a prefix (such as “Benefits:”) in the notes field to track the benefits received and include them in any reports or acknowledgements as needed.
• Remember the $75 disclosure threshold: any single quid pro quo payment over $75 needs a written disclosure statement to the donor, not just an FMV field entry — the field supports your compliance, but the donor-facing disclosure is a separate step.
• If a benefit likely qualifies for the IRS token or membership exception (low-cost items, modest annual membership perks), you can leave FMV at $0 rather than reducing the donor's deduction unnecessarily — use judgment and consult Publication 1771 for the current thresholds, which are adjusted annually for inflation.
• Use the manual Tax Deductible Amount override sparingly and document why in the Action's Notes — it bypasses the standard formula and can be easy to lose track of during an audit.

Sources

IRS Publication 1771, Charitable Contributions – Substantiation and Disclosure Requirements (final authority) — https://www.irs.gov/pub/irs-pdf/p1771.pdf

AFP Global, "How to Issue Donation Receipts for Different Types of Gifts" (supplemental) — https://afpglobal.org/how-issue-donation-receipts-different-types-gifts