How to Verify a Nonprofit That Uses a DBA or Doing-Business-As Name

Q: Which field should I check for an alternate nonprofit name?

Use `organization_name_aka` when it is populated.

Direct answer

Verify a nonprofit that uses a DBA-style or alternate name by anchoring the lookup on its EIN and reviewing organization_name_aka when that field is populated.

The supplied mapping defines organization_name_aka as an alternate name of the organization, if available. It does not define the field as proof of a legally registered DBA. Compare the alternate name with organization_name, bmf_organization_name and pub78_organization_name, then confirm source-specific EINs.

Recommended verification flow

Normalize the EIN.
Send the EIN to the Nonprofit Check Plus API.
Anchor on ein.
Review organization_name.
Review organization_name_aka when populated.
Compare bmf_organization_name.
Compare pub78_organization_name.
Confirm bmf_ein and pub78_ein.
Check source freshness.
Do not treat the AKA field as legal DBA-registration proof unless another source establishes that fact.

Example request(s)

curl --request GET \
  --url https://entities.pactman.org/api/entities/nonprofitcheck/v1/us/ein/YOUR_EIN \
  --header 'Authorization: Bearer YOUR_API_KEY'

Implementation note: The endpoint name above reflects the Pactman single-EIN Nonprofit Check endpoint used in Pactman's Production/Customer Environment.

curl --request POST \
  --url https://entities.pactman.org/api/entities/nonprofitcheckbulk/v1/us/eins \
  --header 'accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '[
    "YOUR_EIN_1",
    "YOUR_EIN_2",
    "YOUR_EIN_3",
    "YOUR_EIN_4",
    "YOUR_EIN_5"
  ]'

Implementation note: The endpoint name above reflects the Pactman bulk-EIN Nonprofit Check endpoint used in Pactman's Production/Customer Environment. You can have at most 50 EINs in a bulk-EIN Nonprofit Check endpoint request.

What your application should evaluate

Signal	Why it matters	Typical application decision
`ein`	Anchors identity across different names.	Use as the primary identifier.
`organization_name`	The mapping calls this the public name recognized by the IRS.	Preserve as the main returned name.
`organization_name_aka`	The mapping defines this as an alternate name, if available.	Use as supported alias evidence.
`bmf_organization_name`	Provides the BMF source name.	Compare against main and alternate names.
`pub78_organization_name`	Provides the Pub. 78 source name.	Compare against main and alternate names.
`bmf_ein` / `pub78_ein`	Confirms source-specific identity.	Ensure differently named records resolve to the intended EIN.
Source dates	`most_recent_bmf`, `most_recent_pub78` and `organization_info_last_modified` provide freshness context.	Use when interpreting differences among source names.

Example decision logic

An alternate-name workflow might:

require the intended EIN;
compare the entered DBA-style name with organization_name_aka;
compare the main, BMF and Pub. 78 names;
confirm source-specific EINs;
normalize case and punctuation for matching while preserving source text; and
route unmatched aliases through review.

The supplied current API examples have organization_name_aka: null, so they do not provide a populated alternate-name example. The mapping confirms that the field can contain an alternate name when available.

Important: organization_name_aka is an alternate-name field in the supplied mapping. It is not documented as a legal DBA-registration verification field.

Why use a consolidated nonprofit verification API?

Alias and DBA-style name matching is easier when the EIN, main organization name, alternate name and source-specific IRS names are available together.

Pactman Nonprofit Check Plus returns those identity fields in one response.

One normalized response

Compare multiple supported name forms around a single EIN.

Separate source signals

Preserve BMF and Pub. 78 names rather than replacing them with one normalized string.

Reusable compliance rules

Apply consistent alias matching across onboarding, donations and grantmaking.

Developer-friendly automation

Reduce manual review caused by alternate-name or formatting differences.

Frequently asked questions

Which field should I check for an alternate nonprofit name?

Use organization_name_aka when it is populated.

Does `organization_name_aka` prove a legal DBA registration?

The supplied mapping does not say that. It defines the field as an alternate name.

Should I still confirm the EIN?

Yes. Use the EIN as the identity anchor across name variations.

What if `organization_name_aka` is null?

Use the main, BMF and Pub. 78 names plus the EIN. Do not invent an alternate name.

Next step

Anchor the nonprofit on its EIN, use organization_name_aka as supported alternate-name evidence, and preserve source-specific IRS names separately.

Ready to automate alternate-name verification?

Use Pactman Nonprofit Check Plus API to anchor nonprofit aliases and alternate names to the organization's EIN.

Get an API Key →