abvius module
International solidarity organizations face a singular requirement: the same expense must be justified to several stakeholders, each according to its own framework. The head office’s tax administration expects accounts that comply with the national standard; the authorities of the countries of intervention impose their local norms; each donor requires reporting under its own budget structure. In practice, this multiplicity too often leads to redundant data entry, time-consuming reconciliations and discrepancies that are hard to justify in an audit. Multi-standard accounting addresses precisely this situation. This article presents the principle, how it works within abvius, and the concrete benefits for finance teams.
An accounting framework is a set of rules defining how operations are recorded and presented: chart of accounts, valuation principles, standardized financial statements. The French Plan Comptable Général (PCG), the SYCEBNL applicable in the 17 States of the OHADA area, or the budget frameworks specific to each donor (AFD, ECHO, European Union, foundations) are all distinct frameworks. For a detailed presentation of each country’s requirements, see our page on fiscal localizations, referenced at the bottom of this article. Multi-standard accounting refers to the ability to keep a single set of books in which every entry can be reported under several of these frameworks simultaneously. A frequent misunderstanding should be cleared up: multi-standard accounting does not mean keeping several parallel sets of books — on the contrary, it means maintaining a single source, able to produce reports that comply with each norm.
A French NGO running activities in Mali illustrates the situation well. At headquarters, it keeps its accounts under the PCG (ANC regulation 2018-06 for associations) and must be able to produce a Fichier des Écritures Comptables (FEC, the French statutory audit file) in the event of a tax inspection. In the field, its activities fall within the scope of the SYCEBNL, which applies to any non-profit entity headquartered in an OHADA member State or operating there: a specific chart of accounts, dedicated financial statements, a numbered and initialed donor register. Towards its donors, it reports according to the budget structure of each funding contract — activity lines, support costs, specific eligibility rules. Each agreement is, in effect, an additional reporting framework. Without a suitable tool, the usual arrangement consists of entering each expense in several systems, by different people, sometimes at different exchange rates. This redundancy mechanically generates discrepancies, and justifying them consumes a considerable amount of the finance teams’ time — to the detriment of their analysis and steering missions.
Each operation is recorded once, with its full context: amount, currency, third party, project, funding, country of execution. Controls take place at the point of entry: the analytical allocation across donors applies immediately, including in co-funding situations, and each contract’s eligibility rules are checked at this stage — when a correction is still possible, rather than during the preparation of the financial report.
The module maintains the mapping tables between accounting frameworks: each PCG account is associated with its equivalent in the applicable local chart of accounts and with the budget lines of the donors concerned. This configuration is done once, updated as new funding arrives, then applied automatically to every entry. It remains manageable directly by the finance team, without technical intervention.
Each stakeholder receives the expected documents in its own format: FEC and PCG trial balance for the French administration, financial statements compliant with the local framework for the countries of intervention, financial reports in each donor’s contractual format. All come from the same source: every amount can be traced back to the original entry, and this traceability is identical whichever document is consulted — an essential condition for audit security.
The general framework is not always enough; the module provides for the cases where frameworks genuinely diverge:
Consider a training session led by a local consultant for €1,000, funded by an institutional donor. A single entry in abvius produces three consistent reports: account 6226 “Fees” in the French trial balance, traceable in the FEC; the corresponding expense account of the local chart of accounts in the mission’s financial statements; the line “Activity 2.1 — Teacher training” in the donor’s interim report, at the contractual exchange rate. No re-keying, no reconciliation between parallel systems — and above all, a reduced risk of ineligible expenses, since compliance is checked at the moment of commitment. This is the conviction abvius is built on: the amounts donors refuse to reimburse are the main hidden cost of multi-country management, and they are determined at data entry, not at reporting.
No. It is a single set of books, reported under several normative frameworks. Keeping parallel sets of books is precisely the practice that multi-standard accounting makes it possible to abandon.
Analytical accounting organizes operations along the organization’s own management dimensions (projects, activities, funding). Multi-standard accounting reports them under externally imposed norms (PCG, local frameworks, donor formats). The two dimensions complement each other: in abvius, the analytical allocation by funding directly feeds the reports intended for donors.
No. Organizations with small finance teams are the first to benefit: an organization of a few people working in two countries with three donors already has to serve six distinct reporting frameworks, without the resources needed for double data entry.
In France, on sovereign hosting, in line with the data protection requirements of many organizations in the sector.
There is a precise moment in the life of an NGO when someone discovers that the same expense has to be told three times: once for the head office’s tax authority, once for the administration of the country of intervention, once for the donor. Three nomenclatures, three formats, three deadlines. That is exactly the problem we built abvius’ multi-standard accounting module for — and this article explains how it works, without asking you to love accounting in order to read it.
An accounting framework is a set of rules that says how to record and present your operations: a chart of accounts, principles, standard financial statements. The PCG in France, the SYCEBNL in the 17 countries of the OHADA area, each donor’s budget formats — each one is a framework. (For the detail of what each country requires, we wrote a full page on fiscal localizations — the link is at the bottom of this article.) Multi-standard accounting is the ability to keep a single set of books in which every entry can be reported under several of these rule sets at once. Beware of the misreading: it is not “having several sets of books”. It is precisely the opposite — a single source of truth that knows how to translate itself.
The textbook case is the international NGO, because it accumulates every possible audience. The head office’s tax authority. A French NGO keeps its accounts under the PCG and must produce a FEC in the event of an inspection. The administrations of the countries of intervention. The same NGO with a mission in Mali operates on OHADA territory: there, the SYCEBNL is what counts — a specific chart of accounts, dedicated financial statements, a donor register. A double accounting life, perfectly legal and perfectly mandatory. The donors. AFD, ECHO, the EU or a foundation read neither the PCG nor the SYCEBNL: they read their budget structure (“Result 1 — Activity 1.2”, “Support costs”…). Each funding contract is, in effect, one more mini-framework. Without a suitable tool, the classic setup consists of entering each expense two or three times, in different systems, by different people, sometimes at different exchange rates. The mechanical result: discrepancies. And each discrepancy is an investigation — who entered what, when, and why the head office’s €1,000 became €998.40 in the field. It is not that the teams work badly; it is that the system asks them to maintain by hand a consistency that software can guarantee structurally.
Each operation — a consultant’s invoice, a salary, an equipment purchase — is entered once, with its full context: amount, currency, third party, project, funding, country of execution. Everything plays out at data entry: the multi-donor analytical allocation applies immediately, including in co-funding cases, and each donor’s eligibility rules are checked at that moment — not six months later, when the ineligible expense has become a cash-flow problem.
The module maintains the mapping between frameworks: PCG account 6226 “Fees” knows which local chart account it corresponds to, and which budget line of each donor it can be charged to. This mapping is configured once, kept alive as new funding arrives, and then applied automatically to every entry — without a support ticket for every new account.
At the output, everyone receives their version: the FEC and the PCG trial balance for France, statements compliant with the local framework for the field, the financial report in each donor’s exact format. All consistent with one another, because they come out of the same source. When an auditor asks “where does this figure come from?”, the answer is the same in all three documents — which, in an audit, is more or less the definition of happiness.
Because real life does not settle for a nice diagram:
Take a training session led by a Malian consultant for €1,000, funded by an institutional donor. One entry in abvius, and this invoice lives three lives: account 6226 in the French trial balance (traceable in the FEC), the local chart’s expense account in the mission’s statements, the line “Activity 2.1 — Teacher training” in the donor’s interim report, at the right exchange rate. Zero re-keying. Zero end-of-month reconciliation between three Excel files that have never met. And above all: fewer ineligible expenses, because compliance is checked at the moment when you can still act. That is abvius’ reason for being — the amounts donors refuse to reimburse are the real hidden cost of multi-country management, and they are decided at data entry, not at reporting.
No, it is the opposite: a single set of books, reported under several rule sets. Several parallel sets of books is precisely the problem the module removes.
Analytical accounting slices your operations along your own management dimensions (projects, activities, funding). Multi-standard accounting reports them under externally imposed norms (PCG, local frameworks, donor formats). In abvius, the two combine: the analytical allocation by funding directly feeds donor reports.
No — quite the opposite. The smaller the finance team, the fewer hands it has for re-keying. An NGO of five people with two countries of intervention and three donors already has six reporting frameworks to serve.
In France, on sovereign hosting. Your accounting data does not cross the Atlantic to fetch a donor report.