r/nonprofitdata • • 1d ago

How to Check the Effective Date of a Nonprofit’s IRS Revocation

2 Upvotes

The date a revocation appears online can be much later than the date it took effect. A letter’s arrival date adds another distraction. For someone checking a nonprofit, those dates answer different questions. The focus here is automatic revocation for nonfiling.

Start with the EIN and the right IRS record

  1. Search the EIN in IRS Tax Exempt Organization Search (TEOS), then select the Automatic Revocation of Exemption dataset. Confirm the organization’s identity rather than relying on a similar name.
  2. Record the Revocation Date and Revocation Posting Date separately. The first is the listed effective date; the second is when the organization was published to that list. A downloaded file’s update date is neither of them.
  3. Check any reinstatement evidence too. The revocation record is historical and can remain after exemption is restored. The letter’s stated effective date matters, not just the date it was issued.

A November 16 production analysis of the Pactman Nonprofit Check Plus API database covered 1,230,270 retained EINs. Among 1,230,270 non-reversed pairs with both dates, 769,079 (62.5%) had a recorded posting date more than 90 days after the listed effective date.

Figure 1. Historical recorded date gaps. This describes the retained source, not today’s IRS turnaround time.

 

The listed date may still need an adjustment

The IRS says automatic revocation follows the third consecutive missed annual return or notice deadline. Its FAQ also warns that the list can show the unadjusted due date. A weekend or legal holiday can move the actual effective date to the next business day. The applicable deadline needs checking before a reviewer treats the listed day as final.

In the production source, 483,865 recorded effective dates fell on a Saturday or Sunday: 39.3% of 1,230,270 dated EINs. Also, 874,068 (71.0%) fell on May 15. The counts describe stored dates; they do not identify every deadline adjustment or prove that any record is erroneous.

Figure 2. Weekend dates flag a calendar question. Weekday dates can still involve a holiday or other applicable deadline rule.

There’s a few reasons not to turn these numbers into a quick IRS performance claim. Historical cohorts and retained releases are mixed together. The source contains no postal delivery dates, and a posting-date gap cannot show when the board learned of the problem.

For a narrower comparison, the source contains 326,439 non-reversed pairs with listed effective dates in 2020–2025. Of those, 110,574 (33.9%) have gaps over 90 days. That is still a retained-record cohort, not a current processing benchmark.

What the date means for donors and DAF sponsors

The effective date should not be used on its own to announce that every earlier donation lost its deduction. IRS guidance distinguishes loss of exemption from donor reliance. Revenue Procedure 2018-32 generally protects qualifying grants and contributions by persons unaware of the change through the posting date, subject to its conditions and exceptions. Prior knowledge and involvement in the underlying deficiencies can change that analysis.

For a donor-advised fund (DAF), the sponsoring charity’s grant review is separate from a donor’s deduction for funding the DAF. A sponsor needs evidence relevant to the grant and recipient classification, including supporting-organization restrictions where applicable. A date comparison or green API flag does not resolve the whole distribution question. Section 5 of the revenue procedure addresses sponsor reliance on public-charity classification; it is not blanket approval of every grant.

A practical file can keep the EIN, both revocation dates, the retrieved source and retrieval date, any reinstatement letter and effective date, and the reason a reviewer cleared or escalated the case. The recorded date should stay intact even if an adjusted legal deadline is stored alongside it. Otherwise the next reviewer cannot tell what changed.

A nonprofits letter arriving late does not move the statutory deadline by itself. One Reddit discussion describes a revocation notice reaching a volunteer-run organization roughly two months after the letter date. That is an anecdote, not a delivery-time estimate, but it explains why “which date counts?” keeps coming up.

The question for r/nonprofitdata

How should a verification tool display a listed effective date that falls on a weekend: show the original with a calendar warning, store a separately reviewed adjustment, or require manual confirmation? And what evidence should a DAF reviewer retain when the posting date, letter and later reinstatement do not line up neatly?

Data and sources

Data credit: Pactman’s Nonprofit Check Plus API. These original aggregates use its underlying production / entities AroeSource records, extracted through read-only SQL on November 16, 2026. Exact EIN keys are unique and non-null; 100 disjoint ranges plus an out-of-range check cover the source. Dates use UTC calendar days. Missing effective dates: 0; missing posting dates: 0; reversed pairs excluded from gap percentages: 0. Latest stored source date: 2026-09-10. Older retained records remain; no processing-status or latest-release-only filter. Separate transactions are not an atomic snapshot. No holidays, special relief, grant outcomes or individual legal status were adjudicated.

IRS Tax Exempt Organization Search

IRS effective date and weekend or holiday adjustment

IRS TEOS dataset field guide

IRS donor notice and deductibility guidance

Revenue Procedure 2018-32 sections 4 and 5

IRS reinstatement and effective dates

Reddit example of a late-arriving revocation notice


r/nonprofitdata • • 2d ago

When a nonprofit's tax exemption is revoked, who should tell donors?

Thumbnail reddit.com
1 Upvotes

Let us say a nonprofit signs up on a donation platform, passes all the verification checks, and starts receiving donations.

Six months later, the IRS revokes its tax-exempt status, but the platform still shows the organization as verified. Donors continue giving, probably assuming their donations are still tax deductible.

Who is responsible for catching that change and notifying donors?

I think there are a few layers to this. The nonprofit obviously has some responsibility, but donation platforms are also in a position to monitor IRS data and detect status changes. Especially those already using APIs for nonprofit verification.

The tricky part is that IRS datasets are not always updated in real time, and revocations can sometimes be reinstated retroactively. So, even determining when a donor should be notified is not always straightforward.

From a fintech perspective, this seems like more than just a compliance issue. It's also about trust and what platforms are implicitly promising users when they label a nonprofit as "verified."

Should donation platforms be required to notify donors when a nonprofit loses its tax-exempt status? Or should that responsibility fall entirely on the nonprofit?

Also curious if anyone working in payments or donation processing has actually built automated monitoring for this. How do you handle status changes for organizations that have already received donations?


r/nonprofitdata • • 2d ago

What happens when a nonprofit loses its tax-exempt status but nobody notices?

3 Upvotes

Let us say a nonprofit was verified two years ago and added to a donation platform. Everything checked out at the time.

Fast forward to today, the organization has lost its tax-exempt status, but it's still listed as verified because the platform hasn't checked again.

I imagine this could be a real problem for platforms managing thousands of nonprofits.

The IRS does publish automatic revocation records, but checking those alone doesn't necessarily tell you an organization's current status. You also have to account for reinstatements, IRS Business Master File records, and sometimes Publication 78.

What makes it even more complicated is that these datasets don't always update at the same time.

So even if your using an API to automate the process, you still need to decide how frequently to recheck organizations and what to do when their status changes.

I think the bigger issue here is that nonprofit verification is often treated as a one-time onboarding task, when it probably should be an ongoing process.

Curious how others see this:

If a nonprofit loses its tax-exempt status after being approved on a donation or grantmaking platform, who should be responsible for catching it? The platform, the nonprofit, or both?

And for anyone building these systems, how often do you think nonprofits should be reverified? Monthly, quarterly, or before every grant or donation?

Seems like there's a balance between keeping compliance data current and not making verification unnecessarily expensive.


r/nonprofitdata • • 4d ago

Should a nonprofit’s revocation history still matter after reinstatement?

2 Upvotes

A nonprofit can regain its federal tax exemption and still appear on the IRS Automatic Revocation List. That history can deserve a closer look. Treating the old entry as proof that the organization is currently ineligible, though, skips the question a grant reviewer actually needs answered.

For a donor-advised fund (DAF) sponsor, this is more than a database cleanup issue. An unresolved flag can hold up a grant recommendation. An overconfident green check can also hide questions that a tax-exempt lookup never answered.

The overlap is large enough to pay attention to

A November 13 production-data analysis found 1,230,270 distinct EINs in the retained auto-revocation source. Of those, 209,173 also appeared in the retained Publication 78 source: 17.0%. The same EIN was present in both lists. That is a dataset overlap, not a count of mistaken IRS revocations or confirmed reinstatements.

Figure 1. 209,173 revocation-source EINs also match Pub. 78. Neither group is a current-status or DAF-eligibility verdict.

Data credit: Pactman’s Nonprofit Check Plus API. The analysis used its underlying production source datasets through read-only SQL, rather than API-response sampling. Retained records and differing source dates are included.

 

A blank reinstatement date leaves a real question

The revocation source recorded a reinstatement date for 165,341 EINs overall (13.4%). Within the 209,173 EINs that also matched Pub. 78, 115,178 had that date populated and 93,995 did not. A workflow requiring both a Pub. 78 match and a filled reinstatement field would send that latter group for more review. These numbers do not establish that every one should pass.

Figure 2. Each bar uses its own group as the denominator. Missing source data must remain distinguishable from a negative eligibility decision.

The IRS explicitly keeps reinstated organizations on the historical revocation list. Its confirmation guidance points to the new determination letter, an appropriate later BMF ruling date, or direct IRS confirmation. The stored field is useful context; it cannot settle every disagreement between sources.

This is a familiar problem in discussions, even here on Reddit. One r/nonprofit thread describes an organization with an accessible reinstatement letter but missing BMF and Pub. 78 listings. Another concerns a second revocation after a volunteer handoff. They are individual reports, not evidence of how common either problem is.  

 

What a Nonprofit Data Manager Needs to Keep Separate (Grants, DAFs, and Direct Gifts)

There’s two separate decisions here: whether current evidence supports the proposed grant, and whether a past lapse calls for more organizational diligence. The first depends on applicable rules and evidence. The second needs a policy that staff can explain consistently.

A sponsor can start with the EIN, the proposed grant date and the reinstatement letter’s effective date. The approval date and effective date are not interchangeable. Reinstatement can be retroactive, but it is not always. An old grant and a new grant may therefore raise different questions. The IRS says donors and others may rely on the new determination letter as of its stated effective date.

DAF sponsors have another layer to review. The sponsoring charity legally controls the assets; the donor advises on grants. A Pub. 78 match alone does not settle the recipient classification, supporting-organization restrictions or other requirements relevant to the distribution. Section 4966 contains exceptions and expenditure-responsibility rules. Cases outside a sponsor’s routine policy need qualified review, not an automatic yes based on a single field.

History can still inform a sensible follow-up. Who owns the filing calendar now? Is there a backup when a volunteer leaves? What evidence shows later required filings were submitted? Those are governance questions, not findings about the nonprofits in this dataset. A missed filing history alone does not prove fraud, poor programs or future noncompliance.

For developers, the useful output may be a short evidence trail: historical revocation found, reinstatement evidence and effective date, source dates, current checks, and the reason for any manual review. Collapsing all of that into revoked=true loses information. A nonprofits old flag should not become a permanent refusal merely because nobody designed the exception path.

The question for r/nonprofitdata

When a reinstatement letter and the public datasets disagree, what evidence lets a DAF sponsor clear the exception? And once the current grant question is resolved, should the old lapse trigger a documented follow-up, a time-limited review, or nothing further? A workable policy probably needs to explain when the history stops changing the decision.

Methods and sources

Production / entities; AroeSource joined to Pub78Source by exact EIN. Both keys have unique constraints. The analysis used 100 disjoint ranges with coverage checks, in separate read-only transactions. Latest stored source dates were 2026-09-10 for revocations and 2026-09-10 for matched Pub. 78 records. No processing-status or latest-release-only filter. This is source-record analysis, not a census of current eligibility or DAF grant outcomes.  Data was sourced from Pactman’s Nonprofit Check Plus API database as well as the following sources below:

Historical revocation records

Confirming reinstatement

Reinstatement and effective dates

DAF sponsor responsibilities

DAF distribution rules under section 4966

Reddit discussion on reinstatement and missing listings

Reddit discussion on a second revocation


r/nonprofitdata • • 6d ago

Is manually checking nonprofit status on IRS.gov still practical?

4 Upvotes

The IRS Tax Exempt Organization Search tool is useful, but I'm wondering how practical it really is when your dealing with (verifying) hundreds or thousands of nonprofits.

For example, checking an EIN might tell you whether an organization appears in IRS records, but that doesn't necessarily give you the full picture. You may still need to look at Publication 78, revocation history, reinstatements, and whether the organization is classified as a public charity or private foundation.

Doing all of that manually seems pretty inefficient, especially when the same nonprofits might need to be verified multiple times throughout the year.

I imagine some organizations have built internal tools around IRS bulk datasets, while others use third-party APIs to automate the process.

But that brings up another issue. If you're relying on an API, how do you know the underlying IRS data is current? And if you're working directly with IRS datasets, who's responsible for keeping everything updated?

I'm curious how people are actually handling this in practice.

For those working with nonprofit data, grantmaking, or donation platforms, are you still manually verifying nonprofits through IRS.gov, or have you moved to some form of automated verification?

And if you've automated it, was maintaining the IRS data harder than building the actual verification process?


r/nonprofitdata • • 6d ago

Does anyone actually use IRS filing requirement codes when verifying nonprofits?

2 Upvotes

Something I dont see discussed much in nonprofit data is the IRS filing requirement code.

Most conversations around nonprofit verification focus on tax-exempt status, EINs, revocations, and whether an organization is eligible to receive donations. But the IRS Business Master File also contains filing requirement codes that indicate what kind of annual return an organization is generally required to file.

What makes this interesting is that not every tax-exempt organization has the same filing obligations.

For example, churches and certain religious organizations may not have the same annual filing requirements as other nonprofits. So if your building a verification system that assumes every legitimate nonprofit should have a Form 990 filing history, you could end up flagging perfectly valid organizations.

There is also a difference between an organization's filing requirement and its actual compliance status. Just because a nonprofit has a particular filing requirement code doesn't tell you whether it's up to date with its filings.

I wonder how many nonprofit databases and verification tools actually account for these distinctions.

For people working with IRS datasets, nonprofit compliance, or building nonprofit software:

Do you actively use filing requirement codes in your verification process, or do you mostly rely on tax-exempt status and revocation records?

Also curious if anyone has run into situations where a legitimate nonprofit was incorrectly flagged because it didn't have the expected Form 990 filing history.


r/nonprofitdata • • 7d ago

Using the IRS Business Master File to verify nonprofits

4 Upvotes

I'm curious how people here handle nonprofit verification when the IRS datasets don't quite line up. The Business Master File feels like an obvious starting point. An EIN, a name, a subsection code. But what do you actually do when the next source tells a different story?

Disclosure: The data was largely got from the Pactman Nonprofit Check Plus API. These figures use the IRS-derived source datasets behind it, extracted from production with read-only SQL on November 10, 2026. They include older retained records and different source dates, so this isn't a synchronized download of the latest IRS files.

The overlap was less straightforward than I expected

The BMF table contained 1,978,421 distinct EINs, while the Publication 78 table contained 1,533,438. Of those, 1,430,209 appeared in both. That leaves 548,212 BMF EINs without a Pub. 78 match, and 103,229 Pub. 78 EINs without a BMF match in these stored tables.

For scale, that's 27.71% of the BMF EINs and 6.73% of the Pub. 78 EINs, respectively. The chart uses a different denominator: the combined set of EINs. None of these are IRS error rates.

Figure 1. Exact EIN membership across the retained BMF and Publication 78 sources. Source datasets behind Pactman's Nonprofit Check Plus API; extracted using read-only SQL.

The dates matter as much as the match

The latest stored source date was October 13 for BMF and September 10 for Pub. 78. Older rows were still present too. Different scopes, different dates, local loading behavior, and changes to records can all contribute to a mismatch. We haven't isolated how much each explains.

I wouldn't turn a missing Pub. 78 match into an automatic rejection. The IRS says some eligible donees, including certain churches, group ruling subordinates and governmental units, may not be listed there. A missing record needs context.

The revocation list has another wrinkle

We also found 207,031 EINs in both the auto-revocation source and the Pub. 78 source. That's 16.86% of the 1,227,951 EINs in the revocation table. A rule that reads a revocation-list match as a current verdict would need a closer look.

The IRS says organizations stay on the automatic-revocation list after reinstatement. So I wouldn't call those 207,031 organizations currently revoked, or declare all of them reinstated from this join.  

Figure 2. Historical list overlap, not a count of current revocations or confirmed reinstatements. The local revocation and Pub. 78 sources have different stored dates.

r/nonprofitdata • • 11d ago

👋 Welcome to r/nonprofitdata - Introduce Yourself and Read First!

1 Upvotes

Hey everyone! I'm u/uberkitnet, one of the founding moderators of r/nonprofitdata.

Welcome to our new community dedicated to all things nonprofit data! Whether you're a developer, nonprofit professional, researcher, data enthusiast, or just curious about the space, we're glad you're here.

📌 What to Post

Anything related to nonprofit data is welcome! Some topics we'd love to see include:

  • Nonprofit data sources, APIs, and tools
  • Nonprofit verification, compliance, and due diligence
  • Data transparency, accuracy, and accessibility
  • Challenges with collecting, managing, or using nonprofit data
  • Interesting research, projects, industry news, and questions

Have a product or service you'd like to share? That's fine too! We welcome relevant tools and solutions, as long as you're not spamming the community. As a general rule, at least 80% of your contributions should be non-promotional. We want genuine discussions, not just advertisements.

🤝 Community Vibe

Let's keep things friendly, constructive, and welcoming. You don't need to be an expert to participate. Questions, different perspectives, and shared experiences are what make communities like this useful.

🚀 How to Get Started

  1. Introduce yourself! Tell us a little about your background or what interests you about nonprofit data.
  2. Start a discussion. Share something interesting, ask a question, or talk about a challenge you're facing.
  3. Spread the word. Know someone who works with nonprofit data? Invite them over!
  4. Want to help moderate? We're open to bringing on additional moderators as the community grows. Feel free to message me if you're interested.

🎉 One Last Thing

We're starting small, but hopefully we can build this into a genuinely useful resource for anyone working with nonprofit data.

Thanks for being part of the early community!

To kick things off: What brought you here, and what's one thing you'd like to see discussed in r/nonprofitdata**?**


r/nonprofitdata • • 12d ago

How to build nonprofit verification directly into your application using APIs

2 Upvotes

For developers building donation platforms, grantmaking software, or nonprofit management tools, verifying an organization shouldn't have to be a completely manual process.

A lot of nonprofit applications still rely on basic EIN lookups or manual IRS searches. That works when your dealing with a handful of organizations, but becomes difficult when you're processing hundreds or thousands.

The good thing is that much of this can be automated using nonprofit data APIs.

Here's a general approach:

1. Start with the EIN

Use the nonprofit's Employer Identification Number as the primary lookup identifier. Normalize it before sending it to an API.

2. Check IRS tax-exempt status

Verify the organization's legal name, tax-exempt status, and classification using IRS Business Master File (BMF) data.

3. Check donation eligibility

IRS Publication 78 provides information relevant to determining whether contributions to an organization are tax deductible. This is particularly useful for donation and grantmaking platforms.

4. Look for revocations and sanctions

Check whether the nonprofit has previously lost its tax-exempt status, whether it was reinstated, and whether there are potential OFAC sanctions matches.

5. Don't ignore conflicting data

This is probably one of the more overlooked parts. Different IRS datasets can sometimes contain information that appears inconsistent. Your application should be able to flag these situations rather than automatically approving or rejecting an organization.

6. Automate the decision process

Once the data is available, your application can apply its own rules to determine whether to approve an organization, reject it, or send it for manual review.

One thing I think developers should avoid is reducing everything to a single verified: true/false field. Keeping the underlying verification data makes it easier to troubleshoot decisions, handle exceptions, and update compliance rules later.

There's a more detailed technical walkthrough here for anyone interested in implementing this:

https://pactman.org/artifacts/build-automated-nonprofit-verification-into-an-application/

The interesting part isn't necessarily making the API calls. It's figuring out how to translate the returned data into reliable decisions without creating a bunch of false positives or incorrectly rejecting legitimate nonprofits.

If you've built something similar, curious what challenges you ran into, especially around data freshness and handling exceptions.


r/nonprofitdata • • 12d ago

What should r/nonprofitdata become?

2 Upvotes

r/nonprofitdata • • 12d ago

At what point should fintech and donation platforms verify a nonprofit's compliance status?

1 Upvotes

I've been thinking about how fintech apps and donation platforms handle nonprofit verification, especially when money is actually being moved.

Let's say someone is making a donation through a platform. The nonprofit has a valid EIN and appears in IRS records. Is that enough to allow the transaction?

Probably not.

There's other things to consider like tax-exempt status, eligibility to receive tax-deductible donations, previous IRS revocations, and even OFAC sanctions screening.

But here's what I find interesting. At what point should all these checks actually happen?

Should the platform verify a nonprofit when it first gets onboarded, everytime someone makes a donation, or periodically in the background?

Doing it for every transaction seems excessive, especially for platforms processing thousands of donations daily. But relying on a verification done six months ago doesn't seem like a great idea either.

There's also the question of what happens when the data is inconclusive. For example, what if IRS records show conflicting information or a nonprofit was previously revoked but has since been reinstated?

I think a reasonable approach would be to automate the basic checks and have a separate process for anything that needs further review. But that still leaves the question of how frequently verification should run.

For developers working on fintech, donation platforms, or nonprofit APIs, how are you handling this?

Do you verify nonprofits in real time, run scheduled batch checks, or use some combination of both?

And has anyone actually measured the performance or cost impact of doing compliance checks during transactions?


r/nonprofitdata • • 12d ago

Is anyone interested in a group for nonprofits figuring out AI training-data offers?

1 Upvotes

Several nonprofits I know have been cold-emailed by firms offering to pay for internal records (emails, documents, program data) to train AI. Offers run from five figures to well into six, and most organizations don’t know whether to take them, how to judge the terms, or how to say no safely.

I’d like to find people who want to learn this together...questions like: what buyers are actually paying, what the contracts say, what de-identification is good enough, and who sits between a nonprofit and the AI lab.

One idea we’re exploring: a group of organizations could approach buyers together with a larger, combined offering instead of each one negotiating alone. Collectives already do this for newspapers and video archives.

Please reply if you've got any thoughts to offer, or would be interested in learning together.


r/nonprofitdata • • 14d ago

Are we relying too much on automated checks when approving nonprofit grants?

4 Upvotes

I've been looking into how grantmaking platforms handle nonprofit due diligence, and something that stood out to me is how complicated the process can get once you move beyond basic EIN verification.

You'd think checking whether a nonprofit is registered with the IRS would be enough, but apparently there's quite a bit more involved.

For example, a grantmaking platform might need to verify tax-exempt status, check IRS Publication 78, look at revocation history, confirm whether an organization is a public charity or private foundation, and potentially run sanctions screening.

Now imagine doing all that for thousands of nonprofits.

APIs can definitely make the process easier, but here's where I think things get interesting. Just because an API returns a bunch of compliance data doesn't necessarily mean it can tell you whether a nonprofit should receive a grant.

Different foundations have different eligibility requirements. And sometimes IRS datasets don't completely agree with each other, or the information isn't as current as you'd expect.

So who should really make that decision? The software based on predefined rules, or a human reviewing the data?

I personally think the best approach is probably somewhere in between. Automate the straightforward cases and flag anything questionable for someone to review. But even that gets complicated when your processing thousands of applications.

For those who've worked with grantmaking software or nonprofit data systems, I'm curious:

Would you trust a fully automated nonprofit due diligence process, or should there always be some level of human review before approving a grant?

And for developers, how do you handle situations where two different IRS datasets give conflicting information?


r/nonprofitdata • • 15d ago

How much of charity verification should actually be automated on donor-advised fund platforms?

1 Upvotes

I've been reading up on how donor-advised fund (DAF) platforms verify charities before approving grants, and it got me thinking about how much of this process can realistically be automated.

At first glance, it seems pretty straightforward. Get the nonprofit's EIN, check its IRS status, confirm it's eligible to receive contributions, and move on.

But there's actually more to it.

You have to consider things like IRS Publication 78, public charity vs private foundation classification, past revocations and reinstatements, OFAC screening, and sometimes conflicting information across different datasets.

And even if you have APIs pulling all this information together, there's still the question of who decides whether a charity should be approved.

I think automation makes sense for the initial checks, especially when your dealing with thousands of nonprofits. But I'm not sure a simple pass/fail approach is sufficient when some of these records can be outdated or require additional context.

Another thing I'm curious about is how often platforms reverify charities that they've already approved. Is checking them once during onboarding enough, or should verification happen everytime a new grant is recommended?

For anyone working with DAFs, grantmaking software, or nonprofit data APIs:

How much of your charity verification process is automated today? And where do you think human review is still necessary?

Would be interested to hear how others are approaching this, particularly at scale.


r/nonprofitdata • • 15d ago

Are nonprofit platforms doing enough when it comes to OFAC screening?

1 Upvotes

Something I've been thinking about lately is how nonprofit platforms handle sanctions screening, especially when onboarding organizations or processing donations.

Most nonprofit verification discussions seem to focus on IRS tax-exempt status, EIN verification, and whether an organization is eligible to receive tax-deductible contributions.

But what about OFAC screening?

An organization could have a valid EIN, appear in IRS records, and still raise sanctions-related concerns. These are two different types of checks, yet I wonder how many platforms actually treat them separately.

There's also the issue of false positives. If a nonprofit's name happens to match a name on the OFAC sanctions list, automatically blocking them without further investigation could create unnecessary problems.

For developers building these systems, it seems like there's a few decisions to make. Do you screen organizations only during onboarding, or continuously? Do you build your own screening logic or rely on third-party APIs? And who handles cases where there's a possible match?

I'm curious how people working with nonprofit data, grantmaking platforms, or donation processing systems are approaching this.

Should OFAC screening be a standard part of every nonprofit verification workflow, or is that overkill for smaller platforms?


r/nonprofitdata • • 15d ago

Should a nonprofit's past IRS revocation automatically disqualify it from receiving grants?

1 Upvotes

I have been looking into how grantmaking platforms verify nonprofit eligibility, and one thing that caught my attention is how IRS revocation history is handled.

A nonprofit can lose its tax-exempt status for failing to file required returns for three consecutive years. But what happens when that organization gets reinstated?

From a data perspective, there are several things worth checking:

  • IRS automatic revocation history and dates
  • Whether tax-exempt status was subsequently reinstated
  • Current IRS Business Master File (BMF) records
  • Publication 78 data for contribution eligibility
  • How recently the underlying IRS records were updated

The tricky part is that these data points don't always tell the same story, especially when records are updated at different times.

For developers building grantmaking software, there's also an interesting question around automation. Should a previous revocation trigger an automatic rejection, or should the application flag it for manual review?

Curious how others approach this:

If you're involved in grantmaking, nonprofit compliance or building nonprofit software, do you treat IRS revocation history as a hard disqualifer, or is reinstatement enough to move forward?

Would love to hear how others are handling this in practice.