Audit-Ready Documentation Without Manual End-of-Project Work | Automatic Supporting Documents, Blocking Ineligible Expenses, InforEuro Conversion | Abvius

How to generate audit-ready documentation without manual work at the end of a project?

Reading time: ~7 min

Table of contents

1. The answer in three mechanisms
2. What a "ready" audit file contains
3. Mechanism 1: automatic supporting documents
4. Mechanism 2: blocking ineligible expenses
5. Mechanism 3: InforEuro conversion
6. Closing day: what is left to do
7. Configuration checklist per grant agreement
8. FAQ
9. Conclusion
10. Go further

The answer in three mechanisms

Audit-ready documentation without manual end-of-project work rests on three mechanisms, all of which must exist in the system where the expense is born: automatic supporting documents, meaning documents required and attached by the workflow at the point of spend; blocking of ineligible expenses, meaning a donor rule that refuses the commitment instead of flagging it; and InforEuro conversion (or conversion at the rate set by the agreement) applied by the system and stored on every transaction. abvius, an ERP designed exclusively for NGOs, implements these three mechanisms across its 68 toggleable modules. This reference page describes how, and what is left to do on closing day.

What a "ready" audit file contains

Before talking about automation, let us be precise about the object. A complete donor audit file, for one grant agreement and one period, contains:

• the expense ledger by budget line, in the agreement's currency, with for each transaction the original currency, original amount and rate applied;
• for each expense, the supporting document (invoice, receipt, contract, comparative quotes, purchase order, delivery note, payment voucher), dated and legible;
• for salaries, contracts, payslips, approved timesheets and the allocation key per agreement;
• for purchases above thresholds, proof of competition, the bid evaluation report and, where relevant, the justified derogation;
• for shared costs, the allocation key and its justification;
• the audit trail: who requested, who approved, when, and what was changed;
• the financial report in the donor's format, reconciled with the ledger.

A "ready" file is one where each of these elements already exists, linked to the others, when the auditor asks for it. Our project closure guide describes the manual version of this exercise.

Mechanism 1: automatic supporting documents

"Automatic" does not mean the document generates itself: a supplier invoice is still a supplier invoice. It means the system requires it at the right moment, from the right person, and attaches it permanently to the transaction.

In abvius, every spending workflow has its list of mandatory documents, configured according to the nature of the expense and the agreement's requirements:

• Procurement: quotes (number depending on the tier), purchase order, delivery note, invoice, proof of payment, supplier screening result.
• Expense claims and card or petty cash expenses: dated receipt, purpose, project and line charged.
• Travel and per diem: approved mission order, TERF, transport and accommodation receipts.
• Cash requests and petty cash: signed vouchers, reconciliations.
• Timesheets: monthly line-manager approval, feeding salary allocation from payroll.

Without the document, the transaction does not move to the next step. The document is kept in unlimited archiving, linked to the accounting entry, and retrievable by agreement, line, supplier or date. On audit day, nobody searches for anything.

Mechanism 2: blocking ineligible expenses

An ineligible expense discovered at audit costs twice: the amount repaid, and credibility with the donor. The only way to be rid of it is to stop it getting in.

In the grants management module, each agreement is configured with its eligibility period, authorised and excluded expense categories, caps per line and heading, flexibility margin between headings, and procurement thresholds. When an expense is charged to the agreement, the system checks each of these rules before approval:

• date outside the eligibility period: blocked;
• category excluded by the agreement: blocked;
• budget line exhausted (commitments included): blocked, with the overrun amount and a pointer to the amendment procedure;
• amount above a procurement threshold without the required quotes: blocked;
• supplier with a positive screening hit: blocked.

A block is not a dead end: a justified derogation, approved at the hierarchical level provided for, can lift it, and it is traced with its reason. That is exactly what an auditor wants to see: not an organisation without exceptions, but one whose exceptions are decided and documented. Real-time budget tracking permanently shows what is left on each line, so that blocks are rare because they are predictable.

Mechanism 3: InforEuro conversion

European Union funding (ECHO, DG INTPA and most EU instruments) requires expenses in local currency to be converted at the InforEuro rate, the monthly accounting rate published by the Commission, following a rule set out in each agreement (rate of the month of expense, of payment, or of the report). Applied by hand in a spreadsheet, this rate is the first source of audit discrepancies: wrong month, wrong currency, different rounding, copied formula.

abvius's automatic InforEuro conversion module retrieves the monthly rates, applies the rule configured for the agreement to every transaction, and stores, on the transaction itself, the rate applied and the converted amount. The financial report and the audit file show both amounts and the rate, which is precisely what the auditor checks first. Other donors (fixed contractual rate, UN operational rate, payment-date rate) are configured with the same mechanism. The multi-currency shared costs module then applies allocation keys to the converted amounts. Our multi-currency guide details the special cases.

Closing day: what is left to do

When the three mechanisms have been running for the whole project, closing comes down to four actions:

1. Check in budget tracking that all committed expenses are paid and justified (the system lists those that are not).
2. Generate the financial report in the donor's format from the grants module, automatically reconciled with the ledger.
3. Export the donor audit file for the agreement and period: ledger, documents, rates, salary allocations, derogations, audit trail.
4. Write the narrative report, drawing on the MEAL module to put results next to expenses. abvius's optional AI modules (connected to Mistral, ChatGPT or Claude, as you choose) can help produce a first draft from the project data.

Manual end-of-project work does not vanish entirely: it shrinks to review and signature, which is the work one expects from a finance department.

Configuration checklist per grant agreement

For the three mechanisms to work, here is what must be configured when each agreement is signed, in one working session (the 8 hours of monthly support included in the abvius subscription are there for this):

• eligibility period, agreement currency, exchange rate rule;
• budget by line and heading, flexibility margin, amendment rule;
• excluded expense categories;
• procurement thresholds and documents required at each tier;
• list of mandatory documents per expense type;
• shared cost allocation keys;
• approval levels and derogation authorities;
• financial report template and reporting calendar, with alerts.

FAQ

Does this work for donors outside the European Union?

Yes. The three mechanisms are donor-independent; only the values change (rates, thresholds, categories, report format). UN agencies, AFD, bilateral agencies, foundations: the same agreement template adapts.

What happens if a document is lost anyway?

The receiptless expense reconciliation module lets you document the absence properly (declaration, substitute document, decision to cover from own funds) instead of discovering it at audit.

Does abvius replace the auditor or internal control?

No. It executes the internal control you have defined and makes the audit fast. Segregation of duties and derogation decisions remain human.

And pricing?

It depends on the modules switched on and the size of the organisation; we work it out with you in a demo.

Conclusion

Generating audit-ready documentation without manual end-of-project work is not a matter of extra effort, it is a matter of timing: the evidence must be produced when the expense is produced. Documents required at source, ineligible expenses blocked before commitment, InforEuro conversion applied by the system: with these three mechanisms in place, the audit file is an export, and the end of a project goes back to being what it should be, a moment to look at what the project changed rather than where the invoices were filed.

Go further

Explore the donor audit files module, automatic InforEuro conversion and grants management, or browse all 68 modules on abvius.org. Then book a 30-minute demo with Lydia and Marie: bring a live grant agreement, we will configure its rules together and export a first audit file.