Conditional vs. Unconditional Contributions: The Two-Part Test That Decides When Your Nonprofit Can Book Grant Revenue

Your nonprofit just won a $250,000 grant, the award letter is signed, and the first check is already in the bank. Your board wants to see it in this quarter's revenue. Here is the uncomfortable question your auditor will ask before you book a dollar of it: are you actually entitled to keep that money yet, or do you owe it back if you fail to deliver what the grant requires?

That question is the entire subject of FASB's grant-accounting guidance, ASU 2018-08. Get the answer wrong in one direction and you overstate revenue, understate liabilities, and hand your auditor a restatement. Get it wrong in the other direction and you defer revenue you had every right to recognize, making a healthy year look like a shortfall. This guide walks through the two-part test the standard requires, what counts as a barrier, and the journal entries that follow from each answer.

Why This Distinction Controls Your Revenue Timing​

Every contribution your nonprofit receives falls into one of two buckets, and the bucket decides when revenue hits your statement of activities:

• Unconditional contributions are recognized as revenue immediately — when the promise is made or the cash arrives, even if the donor restricted the gift to a future program or period.
• Conditional contributions are not revenue at all until the conditions are substantially met or explicitly waived by the donor. Cash received in the meantime sits on your balance sheet as a refundable advance, which is a liability, not revenue.

Notice what this means in practice. Two nonprofits can receive identical $100,000 checks in December and report legitimately different Decembers: one books $100,000 of contribution revenue, the other books a $100,000 liability and zero revenue. The difference is not the check. It is the strings attached to it.

Before 2018, nonprofits applied this distinction inconsistently — especially to government grants, where it was genuinely unclear whether the grant was a purchase of services or a gift. ASU 2018-08, now codified in ASC 958-605, settled both questions with a decision sequence every grant file should document: first, is this an exchange transaction or a contribution? Second, if it is a contribution, is it conditional or unconditional?

Step One: Is It an Exchange Transaction or a Contribution?​

This first question trips up more grant files than the second one, so do not skip it. An exchange transaction means the resource provider gets something of commensurate value in return — your nonprofit sells goods or services and the funder is the customer. A contribution means the funder gives you resources and the benefit flows to someone else, typically the general public.

The test is who benefits, not what the document is called. A "contract" can be a contribution and a "grant" can be an exchange. Ask: does the resource provider itself receive value roughly equal to what it paid?

• A city pays your theater company to stage free concerts in public parks. The city gets goodwill and happy residents, but the concerts benefit the public, not the city government as a customer. Contribution.
• A corporation pays your research institute to test its new alloy and report the results back to the company privately. The company receives the direct benefit of the work. Exchange transaction, accounted for under the revenue recognition standard (ASC 606), not the contribution guidance.
• A federal agency reimburses your clinic for each qualifying patient visit under published program rules. The agency is funding a public program, not buying healthcare for itself. Contribution — and, as discussed below, usually a conditional one.

The practical payoff of ASU 2018-08 was clarifying that most government grants land in the contribution bucket, because the government rarely receives commensurate value as an entity. That moved a huge population of grants out of ASC 606 and into the conditional-versus-unconditional analysis. If your books still treat a cost-reimbursement government grant as an exchange contract with deferred revenue, this is the first thing to revisit with your CPA.

Step Two: The Two-Part Test for Conditional Contributions​

Once you have established that a transfer is a contribution, ASU 2018-08 gives you a strict two-part test. A contribution is conditional only if the agreement contains both:

1. One or more barriers that you must overcome before you are entitled to the resources, and
2. A right of return of the assets transferred to you, or a right of release of the donor from its obligation to transfer assets.

Both. If the agreement has a barrier but no right of return or release, the contribution is unconditional — recognize it now. If it has a right of return but no barrier, likewise unconditional. Only the combination defers recognition.

Two related rules surprise people who learned the old guidance:

• You do not assess probability. Under prior practice, accountants weighed how likely the nonprofit was to meet the condition. ASU 2018-08 eliminated that judgment entirely: if the barrier and the return right are both present, the contribution is conditional even if meeting the barrier is a near-certainty. Revenue is recognized when the barrier is overcome, not when overcoming it starts looking likely.
• Ambiguity defaults to conditional. If it is genuinely unclear from the agreement whether a stipulation is a condition, and no further information resolves it, you treat the contribution as conditional. Document the ambiguity in the grant file so your auditor sees a judgment, not an oversight.

What Counts as a Barrier​

The standard gives three indicators for identifying a barrier. Any one of them can establish one:

1. A measurable performance-related barrier​

The agreement requires you to achieve something countable: a specified level of service, an identified number of units of output, a specific outcome or milestone, or a matching requirement. Examples:

• A foundation pledges $1 for every $1 you raise from new donors, up to $100,000. The matching requirement is the barrier; you recognize revenue as the match is raised, dollar for dollar.
• A workforce grant pays out as you place trainees in jobs, at a fixed rate per verified placement. Each placement overcomes a slice of the barrier.
• A challenge grant releases funds only if your annual gala clears $500,000 in ticket sales. The outcome threshold is the barrier.

2. Limited discretion over how you conduct the activity​

The stipulation constrains the way you perform, not just the topic. Indicators include requirements to follow specific guidelines about which expenses qualify, to hire specific individuals, or to adhere to a specific protocol. The classic case is the cost-reimbursement grant: you are entitled to the funds only to the extent you incur allowable costs under the agreement's rules, so each qualifying dollar you spend overcomes part of the barrier and lets you recognize a dollar of revenue.

3. A stipulation related to the purpose of the agreement​

This indicator is mostly a filter: it confirms the barrier connects to what the contribution is for, and it explicitly excludes administrative and trivial stipulations. Filing an annual report, submitting to an audit, or sending the donor a thank-you letter are not barriers, no matter how sternly the agreement phrases them. Neither are goals or budgets that carry no penalty if you miss them.

Conditions Are About Timing; Restrictions Are About Classification​

The single most confused pairing in nonprofit accounting is the condition-versus-restriction distinction, so fix it with one sentence: a condition controls when you recognize revenue; a restriction controls which net asset class the revenue lands in.

• "We will give you $80,000 to run the after-school program" is a restriction (purpose) on an unconditional contribution. Book the $80,000 as contribution revenue immediately, classified as with donor restrictions, and release it from restriction as you spend on the program.
• "We will reimburse up to $80,000 of your after-school program costs as you incur them" is a condition (barrier: incurring qualifying costs, plus a right of return for unspent funds). Book nothing as revenue until you spend; cash in hand is a refundable advance.
• "We will give you $80,000 next July" is a restriction (time), unconditional. Recognize it now — with donor restrictions for the time stipulation — not next July.

A contribution can carry both: a conditional grant whose fulfilled portion is then restricted to a purpose. First the barrier gates recognition; then the restriction gates classification. Work the sequence in that order and the accounting follows.

The Journal Entries, Side by Side​

Suppose a donor makes an unconditional $50,000 pledge for next year's literacy program, and a foundation sends a $100,000 conditional grant check (cost-reimbursement) in advance.

Unconditional pledge received:

• Debit Contributions receivable — $50,000
• Credit Contribution revenue, with donor restrictions — $50,000

Conditional grant cash received before barriers are met:

• Debit Cash — $100,000
• Credit Refundable advance (liability) — $100,000

Note what you did not do in the second entry: no revenue, no receivable games. The liability account should ideally be tracked per grant, so each award's unrelieved balance is visible at a glance.

Month passes; you incur $30,000 of qualifying expenses under the conditional grant:

• Debit Refundable advance — $30,000
• Credit Grant revenue (contribution revenue) — $30,000

And if the barrier is never met and the funder claws the money back, the refundable advance debits against cash with no revenue entry ever touching the statement of activities — which is exactly why the liability treatment exists.

One more case: a conditional promise where no cash has arrived yet gets no journal entry at all. You do not book a receivable for money you are not yet entitled to receive. Disclosure in the financial statement notes is the appropriate treatment until the condition is met.

Five Mistakes That Draw Audit Adjustments​

1. Booking revenue on the award date. The grant announcement, the signed award letter, and the press release are not recognition events for a conditional contribution. Revenue is recognized when the barrier falls. Every year, auditors reverse revenue that development teams booked the day the award letter arrived.

2. Treating reporting requirements as barriers. "Submit quarterly financial reports and an annual audit" sounds demanding, but administrative stipulations do not create conditional contributions. Over-deferring on this basis understates revenue just as surely as booking early overstates it.

3. Assessing likelihood anyway. "We will definitely raise the match, so let's book the full matching grant now" is explicitly prohibited. Probability does not enter the analysis. The matching dollars you have not raised yet are not revenue.

4. Confusing a purpose restriction with a condition. "Use this for scholarships" tells you how to spend it, not whether you may keep it. That is a restriction on an unconditional gift — recognize it now, with donor restrictions — not a reason to park it in refundable advances.

5. Failing to read the agreement at all. The most common finding of all: finance books the grant based on the development team's summary, the actual agreement surfaces during fieldwork with a right of return nobody mentioned, and the financials need a material adjustment. The fix is process, not accounting knowledge — route every award letter and grant agreement through the person who decides the accounting before anything is booked.

A Grant-File Checklist Your Auditor Will Love​

For each grant, keep a one-page memo in the file answering these questions in order:

1. Exchange or contribution? Who receives commensurate value — the funder or the public? Cite the agreement section.
2. Barrier? Name the measurable hurdle or the discretion limit, with the page number. If the only stipulations are reports, audits, or goals without penalties, say so explicitly.
3. Right of return or release? Quote the clause. No clause, no condition.
4. Conditional or unconditional? Both elements present means conditional; anything else means recognize now.
5. Restrictions? Purpose, time, or perpetual — these set the net asset class once revenue is recognized.
6. Recognition pattern. One date (matching threshold hit, event held) or over time (costs incurred)? Track the trigger per grant so each month's entry ties to evidence.

That memo is the difference between a clean audit inquiry and a proposed adjustment. Auditors test exactly this sequence; handing them your documented answers converts a judgmental area into a verified one.

Keep Your Grant Books Audit-Ready From Day One​

Grant revenue is only as defensible as the records behind it: per-grant liability tracking, barrier evidence tied to each recognition entry, and award letters filed where finance can actually find them. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.