Define the parties in scope
Choose the parties and sources required by your grant or partner policy. Avoid collecting unrelated personal data.
Sanctions screening for nonprofits, charities and NGOs
Run sanctions checks for partners, grantees and suppliers. Review possible matches as a team. Save each result and the reasons for your choice with the right program.
Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.
Client acceptance review
Keep the screening attached to the engagement.
Built around your work
A grantee may appoint a new local partner during a program. The original grantee’s check does not cover that new organization. Staff need to keep the current parties and their evidence clear.
Choose the parties and sources required by your grant or partner policy. Avoid collecting unrelated personal data.
Compare possible matches with known names and registry facts. Record uncertainty and request facts that help when needed.
Keep the program reference, review reasons, and approval path together. Monitor selected long-term partners when your policy calls for repeat checks.
Put it into practice
A program can add a local partner after the grant was first reviewed. Staff need to keep the new party visible without losing the earlier evidence.
Distinct subject results share the program reference. The grant approver can see which identity questions are resolved and which remain open.
Identify the grantee, partner, or supplier and any other required parties. Collect the known legal details and a program reference.
Run checks against the chosen lists and assign possible matches. Keep failed checks open and distinguish them from no-match.
Record the finding about the match and finish the separate grant or activity assessment. Update the party roster when partners change.
Example Laurel Aid works with a registered recipient in an invented grant program. The recipient later names a new implementing partner. Staff record that partner as a distinct organization and choose the sources required by their grant-review policy.
A similar name appears in a source record. The reviewer uses the grant reference to find the right file and compares known registry facts. Ask for more evidence where needed. Leave open questions clear to the grant approver. The first grantee’s no-match does not cover each new partner or aid recipient.
Scroll horizontally to compare every column.
| Work item | Screening evidence | Boundary |
|---|---|---|
| Grant recipient | Organization screening and grant reference. | Recipient identity and program eligibility need their own evidence. |
| Implementing partner | Distinct party record and candidate review. | A new partner does not inherit the recipient’s result. |
| Grant decision | Source scope, review reasons, and supporting references. | Program, destination, ownership, and authorization questions remain separate. |
Start free with 250 live screenings. Use them in the API or dashboard. Your first workspace gets this allowance once, with no monthly reset. No credit card is needed.
Try a grantee and replacement partner with facts your team may share. Ask staff to find each result and the owner of any open question. Try a case export and a record with a missing registry detail.
The optional demo uses made-up records for a quick tour. Use the sandbox to test errors without using live checks.
Check which sources you can use now. Count the first checks and repeat checks for the partners you plan to monitor. The wider grant review still needs to assess who owns an entity, where the work will take place, and whether the activity is allowed. A list check cannot authorize aid or approve a grant.
Use the grant or program reference to link distinct partner checks. Record each party’s role so a future reviewer can tell the recipient from an implementing partner or supplier. Preserve earlier results when the roster changes.
Your policy determines which parties require screening. Do not assume every aid beneficiary should be screened or asked for more personal data. Set a clear purpose for each check and collect the details needed for that task.
TRY IT WITH YOUR TEAM
Check your sources, try a free live check and estimate your monthly cost.
Find your required sources, what they cover and when they were refreshed.
Explore coverageUse your free live checks to find possible matches. Compare the evidence and save a decision.
Start with 250 free checksCount new checks, rows in uploaded lists and repeat checks from monitoring.
See workload examples
Evaluate the fit
Yes. Submit each required person or company as its own subject with chosen sources. Use a grant or program reference to connect the checks while keeping each identity and result distinct.
No. It says that the chosen lists returned no possible match for that subject. Your team still needs to assess the program, place, owners, and rules that apply to the activity. Finish those tasks before making the grant decision.
Your rules and needs decide who to check. This page does not tell you to screen everyone. State why you need the check. Collect only the personal details you need.
Yes, if its known details remain saved and you create a monitor with chosen sources and schedule. Assign someone to alerts and failed checks. Completed rescreens use the shared production allowance.
Record the new organization as a separate subject and perform the required checks. Keep the original recipient’s result as history. The new partner does not inherit it.
See SanctionsKit in action
Start with 250 free live checks. Use the API or dashboard to review matches and save decisions. Choose a paid plan when you need more checks.