How to Check the Reinstatement Date of a Tax-Exempt Organization

Direct answer

To check a tax-exempt organization's reinstatement date, read reinstatement_date in the Pactman Nonprofit Check Plus API response.

The supplied mapping defines reinstatement_date as the date of reinstatement, if any. Preserve revocation_date and revocation_code alongside it so your application keeps the original revocation event rather than replacing it with the later reinstatement event.

Recommended verification flow

Normalize the EIN.
Send the EIN to the Nonprofit Check Plus API.
Confirm the organization. Match ein and organization_name.
Check the revocation record. Review revocation_code and revocation_date.
Read the reinstatement date. Review reinstatement_date.
Preserve both event dates. Do not overwrite revocation_date.
Review BMF presence. Check bmf_status.
Review Pub. 78 presence. Check pub78_verified.
Check freshness. Review most_recent_bmf, most_recent_pub78 and organization_info_last_modified.
Apply your current-status policy. Distinguish historical revocation from later reinstatement.

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
`reinstatement_date`	The mapping defines this as the date of reinstatement, if any.	Use as the direct reinstatement-date value.
`revocation_date`	Preserves the earlier revocation event.	Keep it with the reinstatement record for chronology and audit.
`revocation_code`	Provides Automatic Revocation file context.	Retain the IRS revocation code separately from the dates.
`bmf_status`	Indicates BMF presence.	Use as separate current IRS-record context.
`pub78_verified`	Indicates Pub. 78 presence.	Use as separate contribution-list context.
Source dates	`most_recent_bmf`, `most_recent_pub78` and `organization_info_last_modified` provide freshness context.	Use before treating the overall status as current enough for your workflow.

Example decision logic

A reinstatement-date workflow might:

confirm the organization identity;
preserve revocation_code and revocation_date;
read reinstatement_date;
compare revocation and reinstatement chronology when both are present;
keep BMF and Pub. 78 signals separate; and
use source freshness for the broader status decision.

The supplied current examples return reinstatement_date: null, so they demonstrate the field's place in the schema but do not provide a positive reinstatement-date example.

Important: Do not substitute report_date, most_recent_bmf or most_recent_pub78 for reinstatement_date.

Why use a consolidated nonprofit verification API?

A reinstatement date is more useful when revocation history, BMF presence, Pub. 78 presence and source freshness are available in the same response.

Pactman Nonprofit Check Plus returns those signals together using the current 43 organization-level fields.

One normalized response

Retrieve revocation and reinstatement history with supporting IRS status signals.

Separate source signals

Keep event dates, BMF presence and Pub. 78 presence distinct.

Reusable compliance rules

Apply one reinstatement-date rule across grants, donations, onboarding and recurring reviews.

Developer-friendly automation

Retrieve reinstatement data directly from the nonprofit's EIN instead of manually comparing IRS records.

Frequently asked questions

Which Pactman field contains the reinstatement date?

Use reinstatement_date.

Should I retain the original `revocation_date`?

Yes. Preserve both dates so your application keeps the complete event history.

What if `reinstatement_date` is null?

The response contains no reinstatement date in that field. Do not infer a date that is not returned.

Does a reinstatement date alone prove every current-status requirement is satisfied?

No. Review BMF, Pub. 78 and source freshness separately when the workflow needs a broader current-status decision.

Next step

Use reinstatement_date as the reinstatement-event date, preserve the revocation history, and apply BMF, Pub. 78 and freshness rules separately.

Ready to automate reinstatement-date checks?

Use Pactman Nonprofit Check Plus API to retrieve revocation and reinstatement history directly from an EIN.

Get an API Key →