NGO Fraud Risk Due Diligence: Public-Source Signals to Document

What this check is

Document public allegations and records related to fraud, misuse of funds, procurement concerns and integrity issues. It is a structured public-source and adverse-media review for a specific risk review. The work focuses on the organization, known or discoverable key people, former names, local-language variants and risk terms that may matter to the decision.

For this risk category, the goal is not to prove misconduct. The goal is to preserve the public-source trail: what was searched, what was found, what appears relevant, what looks like a false positive, and what should be clarified before a decision is made.

When to run it

• A preferred partner has been identified as the preferred option.
• The team is preparing an award, grant agreement, contract, consortium role, onboarding step or periodic renewal.
• A donor file, procurement file, partner file or internal approval memo needs a documented public-source review.
• Names, acronyms, former names, key officials or local-language variants should be checked before signing.

What risk categories it covers

A useful ngo fraud risk due diligence should be broader than a name search. IntegrityFile reports organize public-source signals into review categories so the file shows what was checked and why it mattered.

• adverse media, public complaints and reputation signals
• identity, governance, leadership and official registration indicators
• fraud, corruption and misuse of funds
• safeguarding and PSEA concerns
• aid diversion and restricted-party exposure
• political exposure and neutrality concerns
• conflicts of interest and related-party links
• rebranding, former names and identity continuity
• governance, registration and leadership concerns
• legal, regulatory and court-record signals

Practical checks to run

These are the checks that make the file useful to a real reviewer rather than just a generic screening note.

• Separate allegations, official findings, court records, donor actions, media claims and social posts into different evidence types.
• Record severity, recency, source reliability, whether the matter is resolved, and whether the same entity or person is confirmed.
• Use local-language terms for fraud, abuse, corruption, exploitation, diversion, terrorism financing, prosecution, audit and investigation.
• Log false positives with the reason: different country, unrelated acronym, similar person name, outdated article or weak identity match.
• Translate or summarize local-language material carefully and preserve the original title, outlet, date and link.

What public sources may be reviewed

Source availability varies by country, entity type and language. The review should record the sources searched, the search terms used, and any limits in public coverage.

• official organization, company, charity or NGO registries where available
• beneficial ownership, director and officer records where public
• organization websites, annual reports, project pages and leadership pages
• donor, audit, inspector-general, debarment and procurement records
• government, regulator, court and legal records where accessible
• media archives, local-language searches and public web footprint indicators

Useful source notes

These reference points help reviewers understand what to capture, how to search, and why a name-only result is not enough.

• UN Security Council sanctions are organized by regime, so a possible match should be reviewed against the specific listing basis and measures, not just the name.
• OFAC search results include program codes; those codes are part of the review because different sanctions programs may imply different treatment.
• World Bank debarment search works better with partial names and without accents or generic company words such as Limited, Corp. or Ltd.
• For PSEA and safeguarding review, public-source checks should sit beside capacity assessment, reporting-channel review, survivor-centered procedures and partner clarification where appropriate.
• For terrorist-financing or aid-diversion risk, FATF guidance is a reminder to keep measures focused and proportionate rather than treating all civil-society activity as high risk.

Field focus for this review

Document public-source signals involving fraud, corruption, misuse of funds, procurement manipulation, financial controls or integrity concerns.

Do not turn a public-source signal into a conclusion. The file should show the source, identity match, relevance analysis, false-positive reasoning where applicable, and any follow-up or escalation taken.

• inspector-general, audit and donor findings
• court, regulator and prosecutor records
• procurement complaints, debarment and exclusion sources
• media reports using fraud, corruption and embezzlement terms
• official registry records for legal name, status, address and officers
• organization website, annual report, donor pages and leadership biographies
• local-language media and civil-society references using spelling variants

Search terms to try

Replace the placeholders with the legal name, acronym, former name, original-language name, country, project location and known key officials. Keep the exact search terms in the file so the review can be repeated later.

What reviewers often miss

• Ignoring procurement terms such as collusion, bid rigging, kickback, overbilling or conflict of interest.
• Failing to search director and signatory names separately.
• Missing donor audit reports because they refer to project names rather than the organization name.
• Treating a settled repayment issue the same as an active criminal case.
• Not capturing whether the matter involved donor funds, unrestricted funds or an unrelated private activity.
• Only searching the English name and missing the original-language legal name.
• Treating a same-name article as relevant before checking country, address, registration number or official title.
• Failing to search former names, abbreviations and local transliterations.
• Not recording the search term and access date, which makes the file hard to defend later.
• Saving only the conclusion instead of the source link, date, identity match and reviewer reasoning.

What to do when a signal appears

A useful file records the reviewer response, not only the search result. Use the table as a practical starting point and adapt it to internal policy.

Realistic review scenarios

File-ready wording examples

Use cautious language. The wording should describe the public-source review and next step, not make the final selection decision.

What the report includes

• organization name, country, acronym, legal or original-language name and known aliases
• known key officials, or a best-efforts public-source identification of relevant officials
• risk category summary with source-linked findings for human review
• search terms, source table, dates reviewed and evidence notes
• false positive log for unrelated names, outdated results or weak matches
• reviewer fields for relevance, clarification, escalation and final file notes

Evidence to capture in the file

• source title, publisher, URL and date accessed
• exact search term used, including language and spelling variant
• identity match notes: country, address, registration number, official title, date of birth if lawfully available
• finding type: relevant, irrelevant, false positive, needs clarification or escalation required
• reviewer note explaining why the item was included or dismissed
• follow-up question for the partner, vendor, grantee or internal reviewer

Common false positives to watch for

• same acronym used by an unrelated organization in another country
• same person name but different title, city, employer or date range
• old legal dispute involving a predecessor entity with no confirmed continuity
• media article about a sector-wide issue that does not identify the organization under review
• sanctions or debarment search result with weak fuzzy-match confidence and no matching identifiers

What it does not replace

This check does not replace sanctions screening, legal review, safeguarding investigation, procurement approval, vendor eligibility checks, finance review, donor clearance or any required internal decision process. It supports the public-source due diligence step by creating a documented record for human review.

Sample follow-up questions

1. Does the public-source record confirm this is the same organization or associated key person under review?
2. Are there former names, aliases, directors, signatories or related entities that should be searched separately?
3. Are any findings current, serious and relevant to the proposed decision, or are they historical or likely unrelated?
4. Should the organization be asked for clarification before approval, award or escalation?
5. Do any findings trigger internal safeguarding, procurement, legal, donor, finance or management review requirements?

Reference sources for reviewers

Related due diligence guides