- Eligibility stops being one rule set. A programme running in twelve countries rarely has the same conditions in all twelve, so rules have to apply per applicant location or they are wrong somewhere.
- Currency has to be decided before the call opens, not at payment. Which currency the applicant budgets in, which rate applies, and on what date, are three separate decisions, and leaving any of them implicit produces disputes at closeout.
- Grantees lose money twice on conversion. UK Aid Match guidance flags the double conversion problem, where funds converted on receipt and again on spend, at local bank rates, erode the award before any work happens.
- Language is a review problem, not a translation problem. Accepting applications in several languages only works if reviewers who read those languages are routed the right files, and if the scoring criteria mean the same thing in each.
An international grant programme is one where applicants, and often the money, cross borders. That single fact changes four things a domestic programme can leave implicit: who is eligible, how the organisation is vetted, what currency the amounts are in, and which language the file is read in.
None of these is conceptually hard. They become hard because they are usually discovered mid-round, after the call is published and an applicant asks a question nobody prepared an answer for.
Eligibility stops being a single rule set
The first assumption to abandon is that one set of eligibility criteria can serve every country. Legal forms differ, so does what counts as a registered charity, and so do the thresholds that make sense: a minimum operating history that is reasonable in one market excludes most of the sector in another.
A global rule set is therefore wrong in one of two directions. Either it is permissive enough for the loosest jurisdiction, in which case it filters almost nothing in the strictest, or it is strict enough for the tightest, in which case it excludes organisations you would have wanted to fund.
The workable answer is rules applied per applicant location, set once and evaluated at submission. It costs more to configure and it is the difference between a screening stage that works everywhere and one that works at headquarters.
Publishing those rules per country matters as much as applying them. An applicant who can check the conditions for their own jurisdiction before investing two days in a form is the main beneficiary, and the volume of ineligible applications falls at source.
Vetting an organisation you cannot easily verify
Domestic due diligence leans on registries the funder knows how to read. Across borders, the registry may be in another language, structured differently, or not public.
For US private foundations, two established routes exist for grants to foreign organisations: making an equivalency determination that the grantee is the equivalent of a US public charity, or exercising expenditure responsibility over the grant. They carry different documentation and reporting obligations, and which one fits depends on the grantee and the grant. This is a tax question with real consequences, so it belongs with counsel rather than with a template.
Funders outside the US face a comparable problem with a different vocabulary: proving the recipient exists, is what it claims to be, and can account for the money. Whatever the framework, the practical requirement is the same, which is that the evidence collected is recorded against the grant rather than living in the programme officer's email.
Currency: three decisions, taken before the call opens
Currency is where international programmes most often lose money and goodwill, and it is entirely avoidable with three decisions made in advance.
Which currency does the applicant budget in? Their own, which makes the budget realistic and the comparison across applications harder, or yours, which does the reverse. Either is defensible. Not deciding means receiving both.
Which rate, and on what date? The rate at submission, at award, or at payment. These can differ materially over a six-month cycle, and the difference is the applicant's problem unless you say otherwise.
Who carries the movement between award and payment? If a grant is awarded in one currency and paid in another months later, someone absorbs the variation. The Council on Foundations has long flagged exchange-rate exposure as a standing risk in international grantmaking, and it is a risk that has to sit somewhere by design rather than by default.
There is a further cost that funders rarely see. Guidance published for UK Aid Match highlights the double conversion problem: funds converted once on receipt and again when spent, at local bank rates, can erode an award before any programme work happens. A grantee reporting an underspend against budget may simply have lost the difference on the way in.
The practical detail of converting grant amounts across currencies deserves its own answer, and the decision belongs in the grant agreement rather than in a follow-up email.
Contact us or request a demo to stop wasting time on spreadsheets— and start managing grants with speed and clarity.
Reviewing applications in languages your team does not read
Accepting applications in several languages is a review problem before it is a translation problem. Three things have to hold.
Reviewers who read the language must receive the files in that language, which makes routing a language question as well as a thematic one. Machine translation is useful for triage and unreliable for judgement, particularly where an application turns on nuance in describing a community or a method. And the criteria have to mean the same thing in each language, which is a drafting problem: a rubric translated loosely produces scores that are not comparable, however carefully each reviewer applies it.
The common failure is subtler than a mistranslation. When applications in the headquarters language are read by senior reviewers and the others are routed to whoever is available, the language of submission quietly becomes a scoring factor. Checking outcomes by submission language once a year is the simplest way to find out whether that is happening.
Our answer on reviewing grant applications in other languages goes into the routing detail.
Data, compliance and where records live
Grant applications contain personal data, and moving them across borders puts them inside data protection regimes that differ. For European applicants, GDPR obligations in grantmaking apply regardless of where the funder sits, which affects what is collected, how long it is kept and who can see it.
Data residency, meaning where the records are physically stored, is a separate question from data protection and increasingly a procurement requirement in its own right. It is worth establishing early with any platform, because it is rarely changeable later.
Reporting obligations also multiply. A single programme can owe different grantee reports in different formats to different authorities, and the consolidated view the board wants on top. Deciding the common fields at design time is what makes that consolidation possible without a manual exercise per country.
The limits, stated plainly
Running internationally adds real cost, and it is honest to say so. Vetting takes longer, conversion consumes value, and translation and routing add weeks to a cycle. A programme that funds a handful of small grants abroad each year may find the overhead exceeds the benefit, and concentrating on fewer countries is a legitimate answer.
Standardising too hard is the other failure. A single global form, a single rubric and a single set of thresholds produce comparable data and systematically favour applicants who resemble the market the programme was designed in. Comparability and fairness pull against each other here, and the tension does not resolve, it gets managed.
And none of this is settled by software. Which currency, which rate, which vetting route, and what happens to unspent funds are policy decisions. A platform enforces them consistently once made, and enforces the absence of them just as consistently.
How Optimy handles international grant programmes
Optimy applies eligibility rules automatically at submission with conditions set per applicant location, which is the mechanism that lets one programme run under twelve different rule sets without twelve different forms. Applications are collected in your applicants' languages, and reviewer permissions control who sees which files, with scores kept separate between reviewers until the review period closes. The platform is GDPR-compliant by default, and every decision and document stays on the grant record as an audit trail for the authority that asks later.
Currency handling and data residency depend on how a programme is configured and on the plan, so they are worth raising specifically rather than assuming. Book a walkthrough with your own country list and we can go through them.
If you are comparing platforms, our guide to the best grant management software covers scope, pricing and hosting. For the full picture of running a multi-country programme, see also our answer on grant programmes across countries, currencies and languages, or the grant management page.
