ASU 2018 08 can sound technical at first, but the main idea is pretty straightforward: Before a nonprofit records contribution revenue, the finance team needs to know whether the organization has actually earned the right to that money yet.

That’s where the difference between conditional and unconditional contributions comes in.

Some grants and gifts are yours once they are promised or received, even if the donor says the money has to be used for a certain program. Others come with strings attached that must be satisfied first. Those strings can change when revenue gets recorded.

For nonprofit finance teams, this distinction is really important. In this blog, we’ll break down ASU 2018-08 in plain English, explain how to tell the difference between conditional and unconditional contributions, and walk through common grant examples nonprofit finance teams are likely to see in practice.

Why ASU 2018-08 Matters for Nonprofit Revenue Recognition

Nonprofits deal with all kinds of funding agreements: foundation grants, government contracts, donor pledges, reimbursement grants, matching gifts, and program awards.

Before ASU 2018-08, organizations often handled these agreements differently. One nonprofit might record a grant as revenue right away. Another might wait until costs were incurred. Another might treat a similar agreement as an exchange transaction.

ASU 2018-08 helped clarify two big questions:

1. Is this funding a contribution or an exchange transaction?
2. If it is a contribution, is it conditional or unconditional?

The answers determine when revenue should be recognized.

First, Is It a Contribution or an Exchange Transaction?

Before you can decide whether a contribution is conditional, you have to decide whether it is a contribution at all.

A contribution means the resource provider gives money or assets without receiving equal value directly in return.

An exchange transaction means the nonprofit is giving goods or services back to the funder in exchange for payment.

Here’s a simple way to think about it:

If a foundation gives your nonprofit $100,000 to run a community food program, the community receives the main benefit. The foundation may care deeply about the mission, but it is not receiving direct equal value back. That is usually a contribution.

If a government agency pays your nonprofit to provide a specific service directly on its behalf, and the agency is receiving direct value under the arrangement, that may be an exchange transaction.

The name of the agreement does not decide the accounting. A document can be called a “contract” and still be treated as a contribution. A document can be called a “grant” and still need closer review.

Finance has to look at the substance of the agreement.

The Big Question: Is the Contribution Conditional?

Once you know you are dealing with a contribution, the next question is:

Does the nonprofit have to do something before it is entitled to the money?

Under ASU 2018-08, a contribution is conditional only when both of these are present:

• A barrier that must be overcome.
• A right of return or right of release.

Both pieces matter.

If there is a barrier but no right of return or release, the contribution may not be conditional. If there is repayment language but no real barrier, the contribution may not be conditional either.

What Is a Barrier?

A barrier is a real requirement the nonprofit has to meet before it is entitled to the funds.

It is more than basic paperwork. It is more than a donor saying, “Please use this for the after-school program.”

A barrier might look like this:

• The nonprofit must raise matching funds before the donor gives.
• The nonprofit must incur eligible costs before being reimbursed.
• The nonprofit must serve a certain number of clients.
• The nonprofit must complete a project phase.
• The nonprofit must meet specific program outcomes.
• The nonprofit must follow detailed requirements that affect how the work is carried out.

Here’s the practical test: Would missing this requirement mean the nonprofit does not get the money or has to give it back?

If yes, you may be looking at a barrier.

What Is a Right of Return or Right of Release?

The second piece is the funder’s ability to get out of the agreement or recover the money.

A right of return means the nonprofit may have to give money back if it does not meet the condition. A right of release means the donor does not have to pay if the nonprofit does not meet the condition.

You might see language like:

• “Funds must be returned if…”
• “Payment is contingent upon…”
• “The donor is not obligated to pay unless…”
• “Unspent funds must be returned.”
• “Reimbursement will be made only for allowable costs.”
• “The pledge is payable upon completion of…”

This language matters because it tells you the nonprofit may not yet be fully entitled to the contribution.

Conditional vs. Restricted: This Is Where Teams Get Tripped Up

This is probably the most important distinction in the whole topic:

Conditional contributions affect when revenue is recognized.

Restricted contributions affect how revenue is classified after it is recognized.

A donor restriction does not automatically make a gift conditional. For example, say a donor gives $50,000 and says it must be used for the youth mentoring program.

That is likely a restricted contribution, not a conditional one. The nonprofit can recognize the revenue when the gift is promised or received, but it records it as donor-restricted until the money is used for the youth mentoring program.

Now say a donor pledges $50,000 only if the nonprofit raises another $50,000 from other donors by the end of the year. If the nonprofit does not raise the match, the donor does not have to pay.

That is likely conditional. The nonprofit should generally wait to recognize the revenue until the match is met.

Common Examples Finance Teams See

Once the finance team understands the basic ASU 2018-08 test, the next step is applying it to real funding agreements. That is where the details start to matter. The financial accounting standards board clarified this area because nonprofits were often reaching different conclusions on similar grants and donor agreements.

Most nonprofit teams are not reviewing abstract accounting scenarios. They are looking at grant awards, reimbursement agreements, donor pledges, match commitments, and time-restricted gifts. Each one can look similar on the surface, but the revenue recognition answer may be different.

The examples below show how conditional and unconditional contribution guidance often appears in practice.

Cost-Reimbursement Grants

Cost-reimbursement grants are very common for nonprofits, especially organizations that receive government or foundation funding.

In these agreements, the nonprofit usually has to spend money on eligible costs before the funder reimburses it. That requirement often creates a condition because the organization is not entitled to the funding until qualifying expenses have been incurred.

For example, if the agreement says the funder will reimburse only allowable expenses, and the nonprofit is not entitled to payment until those costs are incurred, revenue is usually recognized as eligible expenses are incurred.

That means the full grant amount is not always recognized upfront. Even if the award letter says the organization has been approved for $500,000, the finance team still needs to look at when the nonprofit actually becomes entitled to that funding.

Cost-reimbursement grants are a good reminder that an approved award amount and recognized revenue are not always the same thing. The accounting depends on the terms of the agreement, not just the total funding commitment.

Matching Grants

Matching grants are another common area where conditional contribution guidance comes into play.

A donor might say, “We will give $100,000 if you raise $100,000 from other donors.” In that case, the nonprofit has to meet a specific requirement before the donor is obligated to give.

That matching requirement is usually a barrier. If the donor is released from the promise when the match is not met, the contribution is conditional.

Revenue is generally recognized when the nonprofit satisfies the match.

This is different from a donor simply encouraging the organization to raise more money. The finance team needs to look for binding language. Is the match required before payment? Can the donor walk away if the match is not reached? Those details determine whether the pledge should be treated as conditional.

Matching grants can be powerful fundraising tools, but they need careful accounting review because the donor commitment may not be revenue yet.

Milestone-Based Grants

Some grants are tied to project milestones. These agreements often show up in capital campaigns, construction projects, program launches, research initiatives, and multi-phase grants.

For example, funding may depend on the nonprofit reaching a specific checkpoint, such as:

• Completing Phase 1 of construction.
• Launching a new program site.
• Delivering a required training series.
• Finishing a research report.
• Reaching a specified program milestone.

If the nonprofit has to complete the milestone before it is entitled to the money, and the funder can withhold payment or recover funds, the grant may be conditional.

The key is whether the milestone is a real requirement or just a progress marker. A funder may ask for updates along the way, and that does not automatically create a condition. But if payment depends on completing the milestone, the accounting may need to follow that timing.

Milestone-based grants require the finance team to work closely with program leaders. Finance may need help understanding whether a milestone has actually been met, while program staff may need finance’s help understanding how that milestone affects revenue recognition.

Outcome-Based Grants

Some funders tie payment to results. These agreements can be especially tricky because outcome language is not always written clearly.

For example, an agreement may reference:

• Number of clients served.
• Number of job placements.
• Graduation or completion rates.
• Housing placements.
• Medical visits.
• Training completions.

Sometimes these outcomes are goals. Other times, they are requirements the nonprofit must meet before it is entitled to payment.

That difference matters.

If the agreement says the nonprofit will be paid only after a certain number of clients are served, or that funds can be withheld if outcomes are not met, the arrangement may include a condition. If the outcomes are simply part of the program description or reporting expectations, the contribution may not be conditional.

The finance team should read these agreements closely and document the conclusion. Outcome-based funding often involves judgment, so the file should clearly show why the organization reached its accounting decision.

Time-Restricted Gifts

Time-restricted gifts are different from the examples above.

If a donor gives money in December and says it is for next year’s program, that usually creates a donor restriction, not a condition. The nonprofit may recognize the revenue when the gift is made, then classify it as donor-restricted until the time restriction expires.

This is one of the most common areas of confusion.

The donor is not necessarily saying, “You have to do something before you are entitled to the money.” The donor is saying, “Use this money in a specific period.”

That affects net asset classification, but it does not automatically delay revenue recognition.

Time-restricted gifts are a helpful way to remember the larger rule: conditions are about whether the nonprofit has the right to the money; restrictions are about how or when the nonprofit can use money it already has the right to receive.

With those examples in mind, finance teams can move from case-by-case judgment to a more consistent review process.

A Simple Review Process for Finance Teams

ASU 2018-08 becomes much easier to apply when the finance team uses the same set of questions for every major grant, pledge, or contribution agreement.

The goal is not to turn every award into a long accounting memo. The goal is to create a repeatable process that helps the team spot conditions, separate them from restrictions, and support the revenue recognition decision later. That is why this accounting guidance is most useful when it is built into the organization’s normal grant review workflow.

Here is a practical way to review each grant or contribution agreement.

1. Read the Agreement Before Recording Revenue

Do not rely only on the award name, donor email, or grant summary. The accounting answer is usually in the agreement language.

A document called a “grant agreement” could still include exchange-like terms. A “contract” could still be a contribution. A donor email may mention restrictions but leave out payment terms that appear in the signed agreement.

The safest starting point is always the full agreement.

2. Decide Whether It Is a Contribution or Exchange Transaction

Ask: Is the funder receiving direct value back, or is the public/program beneficiary receiving the main benefit?

If the funder is not receiving direct equal value, the agreement may be a contribution.

This step matters because conditional contribution guidance applies after the team determines the transaction is a contribution. If the agreement is an exchange transaction, the organization may need to look at different revenue recognition guidance.

3. Look for a Barrier

Ask: Does the nonprofit have to meet a real requirement before it is entitled to the money?

Look for match requirements, eligible-cost requirements, milestones, measurable outcomes, or other specific hurdles.

A barrier should be more than routine reporting or general donor preference. It should affect whether the nonprofit has earned the right to the funds.

4. Look for Return or Release Language

Ask: Can the funder withhold payment, avoid payment, or require money back if the requirement is not met?

If yes, the agreement may be conditional.

This step is important because a barrier alone is not enough. To classify the contribution as conditional, the agreement also needs a right of return or right of release.

5. Separate Conditions From Restrictions

Ask: Is this about earning the money, or is it about how the money can be used?

That one question helps prevent a lot of classification errors.

If the nonprofit has to meet a requirement before it is entitled to the funding, the agreement may be conditional. If the donor is telling the nonprofit how or when to use the funding, the agreement may be restricted instead.

A consistent review process also makes it easier to spot mistakes before they reach the financial statements. The right software that is built specifically for nonprofits can really help here, and we will touch on that later.

What to Document in the Grant File

The finance team does not need to write a long memo for every agreement. But the file should include enough detail for another person to understand the decision later.

At a minimum, document:

• Name of the funder.
• Total award amount.
• Whether the agreement is a contribution or exchange transaction.
• Whether the contribution is conditional or unconditional.
• The exact agreement language that supports the conclusion.
• Revenue recognition timing.
• Any donor restrictions.
• Preparer and reviewer notes.

For larger grants, it is worth writing a short memo. It can be simple, but it should clearly explain the team’s reasoning.

That documentation is especially helpful during the audit. It also protects the organization when staff turnover happens. A future controller, CFO, auditor, or board finance committee member should be able to open the file and understand why revenue was recognized the way it was.

For nonprofits managing multiple grants at once, this is where documentation can quickly become hard to manage in spreadsheets. A purpose-built fund-accounting-software can help finance teams keep award details, donor restrictions, revenue timing, and reporting requirements tied to the right grant record.

Conclusion on ASU 2018 08

ASU 2018-08 gives nonprofit finance teams a clearer way to think about grants, pledges, and donor agreements.

The main question is simple:

Does the nonprofit already have the right to the money, or does something have to happen first?

If something has to happen first, look for two things: a real barrier and language that lets the funder withhold payment, avoid payment, or require money back.

If both are present, the contribution is likely conditional. If not, the contribution may be unconditional, even if the donor restricted how the money can be used.

For nonprofit finance teams, the real work is creating a consistent review process, documenting the decision, and making sure revenue is recorded in the right period.

That is also where the right accounting for nonprofits system matters. With Sage Intacct, nonprofit finance teams can track grants, restrictions, conditions, projects, and funding sources with more control than a basic general ledger can provide. Instead of relying on spreadsheets to monitor recognition timing and grant requirements, teams can build cleaner reporting around the way funding is actually managed.

ASU 2018-08 still requires judgment. But Sage Intacct can give finance teams a stronger structure for applying that judgment, supporting audit files, and giving leadership financial reports they can trust.

Key Takeaways

• ASU 2018-08 helps nonprofits decide whether funding is a contribution or exchange transaction, and whether a contribution is conditional or unconditional.
• A contribution is conditional only when there is both a barrier and a right of return or release.
• A donor restriction is not the same as a donor condition.
• Restricted contributions may be recognized before the restriction is satisfied.
• Conditional contributions are generally recognized when the condition is substantially met.
• Cost-reimbursement, matching, milestone-based, and outcome-based grants need careful review.
• The finance team should document the accounting conclusion in the grant file.
• Accounting software matters because finance teams need a clean way to track grants, restrictions, timing, projects, and reporting requirements.

Frequently Asked Questions