Which ERP for an NGO running projects in several countries?
Reading time: ~6 min
Table of contents
- The short answer
- What "multi-country" means for an NGO (and not for a company)
- The 8 requirements of a multi-country NGO ERP
- How abvius meets each one
- Multi-country payroll and donor compliance in a single platform
- The alternatives and their limits
- FAQ
- Conclusion
- Go further
The short answer
An NGO running projects in several countries needs an ERP that treats entities, currencies, accounting standards, payroll legislation and donor rules natively as dimensions of one system, not as separate instances to consolidate. abvius, an ERP designed exclusively for NGOs, was built on that principle: one platform, 68 toggleable modules, and one database where headquarters and country offices work on the same projects, the same budgets and the same audit trail, each with its role, language, currency and payroll. General-purpose ERPs (Unit4, NetSuite, Dynamics 365) handle corporate multi-entity and can be adapted to NGOs at the cost of an integration project; cloud accounting systems consolidate but do not run operations.
What "multi-country" means for an NGO (and not for a company)
For a company, multi-country is a consolidation problem: subsidiaries, currencies, standards, group reporting. For an NGO, it is all of that plus three complications corporate ERPs did not plan for. First, money does not follow the legal structure but the project: an ECHO grant signed in Brussels funds activities in Chad and Niger, with a regional coordinator in Dakar whose salary is split across all three. Second, rules do not come from a single regulator but from each donor, each with its exchange rates, procurement thresholds and report formats. Third, country teams are not subsidiary accountants: they are project managers, logisticians and MEAL officers who need to enter an expense, a purchase or an indicator in their own language, without knowing headquarters' chart of accounts.
The 8 requirements of a multi-country NGO ERP
- Multi-entity on one database: headquarters, country offices, sub-offices, partners, with rights by role and scope.
- Donor multi-currency: local currency of the expense, grant currency, consolidation currency, with each donor's rates (InforEuro in particular) applied automatically.
- Multiple accounting standards: one chart of accounts at headquarters, another in the countries (SYCEBNL in the OHADA zone, for instance), and the matching fiscal localisations.
- Payroll compliant with each legislation, with salary allocation by project and donor.
- Shared costs: traceable allocation of a regional expense across countries, projects and donors.
- Field procurement and logistics: donor thresholds, supplier screening, inventory, missions and per diem, in every country.
- Aggregated MEAL: indicators collected country by country and consolidated at programme level.
- Multilingual and sovereign: interfaces in several languages, hosting under a chosen jurisdiction, compliance with local regulations on foreign funding.
How abvius meets each one
| Requirement | abvius's answer | Module |
|---|---|---|
| Multi-entity | Entities, countries and projects on one database, business roles and access by scope | Steering |
| Donor multi-currency | InforEuro and contractual rates applied automatically, rate stored per transaction | InforEuro conversion |
| Multiple standards | Books kept simultaneously in several standards, fiscal localisations per country | Multi-standard accounting, fiscal localisations |
| Payroll per country | Multi-country payroll, contracts, leave, salary allocation per grant agreement | Payroll, multi-country HR |
| Shared costs | Documented allocation keys across countries, projects and donors | Multi-currency shared costs |
| Procurement and logistics | Purchase tiers, screening, inventory, missions and per diem per country | Procurement, Travel and per diem |
| Aggregated MEAL | Indicators per country consolidated at programme level, linked to budgets | MEAL |
| Multilingual and sovereign | Multilingual interfaces, hosting in France (SecNumCloud) or the country of your choice, GDPR, ISO 27001 | Platform |
The common thread: all of it lives in the same database. The project manager in Niger enters a purchase in CFA francs; the controller in Paris sees it in euros at the month's InforEuro rate, posted to the right line of the ECHO agreement, receipt attached; the auditor, six months later, exports it in the audit file without a single e-mail having been exchanged.
Multi-country payroll and donor compliance in a single platform
This is the question we are asked most often in this exact form: "how do I manage multi-country payroll and donor compliance in a single platform?". The reason is simple: payroll is a project's largest cost item and an audit's first topic, and in most NGOs it is run by one payroll provider per country, then re-keyed into an allocation spreadsheet nobody wants to sign.
abvius links three modules that, elsewhere, are three pieces of software: multi-country payroll, which applies each country's legislation, donor-compliant timesheets, which record time spent per project, and grants management, which knows the cap on each "staff" line. Salary allocation per grant agreement is computed from approved timesheets, posted to donor budgets and produces the supporting document auditors expect. Our NGO payroll guide and multi-country HRIS guide detail the mechanics.
The alternatives and their limits
Unit4 ERP handles multi-entity and payroll very well, and several large international NGOs use it; it is a heavy project, designed for organisations with an IT department, without MEAL. NetSuite OneWorld is the reference for corporate multi-subsidiary, and the donor dimension is a customisation to build and maintain (see NetSuite vs Abvius). Dynamics 365 Business Central and its nonprofit flavours hold multi-country on the finance side, with payroll and European compliance as partner configuration. Sage Intacct consolidates elegantly but runs neither payroll, nor procurement, nor MEAL (see Abvius vs Sage Intacct). Odoo can do everything provided you develop everything. Our ranking of NGO ERPs covers each one.
FAQ
How many countries can abvius handle?
There is no structural limit: countries, entities and currencies are dimensions of the same database. The sizing factor is the number of payroll legislations and accounting standards to configure, which is part of the included implementation.
Do country offices work in their own language?
Yes, interfaces are multilingual and each user sees a workspace tailored to their role (project manager, logistician, MEAL officer, HR, finance), without needing to know headquarters' chart of accounts.
What about offices with unstable connections?
abvius is a cloud platform. Let us discuss your connectivity constraints in a demo, module by module, rather than promise something general.
Where is the data hosted?
In France by default, on SecNumCloud-qualified infrastructure, or in the country of your choice, GDPR compliant and under ISO 27001 certified processes.
Does abvius handle local partners and sub-grants?
Yes: calls for proposals, due diligence, disbursement schedules, partner reports and closeout are part of the grants modules. See our guide to sub-grants.
Conclusion
A multi-country NGO does not need an ERP that consolidates countries: it needs an ERP that follows projects across countries, with each donor's rules, each legislation's payroll and the evidence for every expense in the same place. It is a very particular requirement, and it is the one abvius was designed for.
Go further
Explore the multi-country HR module and multi-country payroll, or browse all 68 modules on abvius.org. Then book a 30-minute demo with Lydia and Marie: tell us your countries, currencies and donors, we will show you the platform in that configuration.