For a DG ECHO partner, everything goes through one document: the Single Form. The initial proposal, modification requests, interim reports and the final report are not separate documents but successive states of the same form, which lives in APPEL from the project's first day until the agreement is settled. It is a powerful logic — one source, one story of the project — but disorienting for teams discovering the system: what you write at proposal stage commits the entire reporting cycle that follows.
This guide covers the Single Form's structure, its life cycle (RQ, MR, reports), the modification rules, and the too-often underestimated link between the form and your accounts — because at final report stage, it is your general ledger that is requested. Ground where an ERP like Abvius makes the difference.
ECHO Single Form: understanding the single document that follows your project end to end
Reading time: ~7 min
- What is the Single Form?
- The structure: the chapters that matter
- The life cycle: RQ, MR, interim and final reports
- Modifications: what needs an MR, what falls under flexibility
- The financial side: from budget to general ledger
- Drafting and monitoring best practices
- How Abvius prepares the ECHO final report
- Mini FAQ
What is the Single Form?
The Single Form is DG ECHO's standardised form for the entire cycle of a funded humanitarian project: it serves to submit the proposal (Request, RQ), to reflect field reality through Modification Requests (MR), to report along the way (interim report), and to inform ECHO of achievements at final report stage — on the basis of which the agreement is settled. It is filled in and submitted electronically via APPEL, the ECHO partners' portal (the eSingle Form), which we present in our guide to the EU funding portals. Access requires being a certified DG ECHO partner.
The practical consequence: at each stage, the form redisplays what was encoded at previous stages. Validated sections appear read-only, and only the fields specific to the current stage open for entry. You never "start over" — and you never escape what you promised.
The structure: the chapters that matter
The Single Form walks through the entire project logic in chapters: general information and summary of the action, needs assessment and risk analysis, the organisation's presence in the area, beneficiaries, logic of intervention with its logframe (results, indicators, activities), quality markers (gender-age, resilience), monitoring and evaluation, field coordination, visibility and communication, financial overview, administrative information, and conclusions. Three chapters concentrate ECHO desks' attention: the needs assessment (the action's justification), the logic of intervention (measurable indicators — they are what you will report against), and the financial overview (consistency between ambition and means). One cross-cutting principle: everything quantified at proposal stage — beneficiaries, indicator targets, budget — will be compared with actuals. Drafting a Single Form is already writing your future final report.
The life cycle: RQ, MR, interim and final reports
Each document in the cycle carries a structured reference (year, project number, document type, version): the initial RQ, its possible revised versions after exchanges with the desk, MRs during implementation, one or more interim reports, then the final report. The interim report is for monitoring: ECHO checks implementation compliance with the agreement, the trajectory of activities and indicators, and the credibility of achieving the results. The final report triggers settlement: the balance payment is decided there — and the financial side becomes central. Submission deadlines are set by your agreement: manage them as fully-fledged donor reporting deadlines, with a back-planning schedule.
Modifications: what needs an MR, what falls under flexibility
The strength of the ECHO system is that it assumes humanitarian reality moves. The MR adjusts the action along the way: the partner edits the relevant chapters directly and justifies the changes in the dedicated section. A calendar rule to remember: the MR must be submitted at the latest 30 calendar days before the end of the implementation period, except in duly justified exceptional cases. Not everything needs a formal amendment: budget adjustments without a substantive change to the description of the action fall under flexibility, while essential changes (results, activities, implementing partners, duration extensions) go through the modification track. The safe reflex: document each deviation as it appears, and settle doubts with your desk — never at final report time. Our article on budget amendments gives the general method.
The financial side: from budget to general ledger
Financially, the ECHO cycle links three documents: the estimated budget by cost category annexed to the agreement, the financial overview maintained in the Single Form, and — at final report — the final cost statement together with the project's general ledger. That last point changes everything: ECHO does not ask for one more summary table, but for the accounts themselves. Every declared amount must reconcile with the entries, every entry with its supporting document, every conversion with its rate — with ECHO eligibility requirements in the background and, in case of gaps, the risk of ineligible expenses to reimburse. A project with clean analytical accounting produces its final statement in days; a project tracked on scattered spreadsheets spends weeks on it — precisely when the team is already on the next project.
Drafting and monitoring best practices
1. Draft the proposal with the final report in mind: every promised indicator must be measurable with the means actually planned.
2. Keep a log of deviations between planned and actual, chapter by chapter, from month one — the raw material of MRs and reports.
3. Align analytical accounting with ECHO cost categories at project opening, not at closure.
4. Anticipate the 30-day rule: an internal arbitration point at mid-term and another three months before the end avoids the last-chance MR.
5. Archive as you go everything the final report will require: documents, exchange rates, timesheets, procurement files.
How Abvius prepares the ECHO final report
In Abvius, the project's accounts carry the dual nomenclature from entry — chart of accounts and donor cost categories — so the final cost statement and the project ledger come from the same source, reconciled by construction. Currency conversions are traced line by line with their rate and supporting document, timesheets and procurement files are attached to the entries, and the audit pack builds continuously during implementation. At ECHO final report time, the finance team assembles — it does not reconstruct.
Mini FAQ
Who can submit a Single Form?
Certified DG ECHO partners, via the APPEL portal. Certification (formerly FPA) is a separate prior process, demanding on the organisation's management capacity.
Can the budget be changed without a formal request?
Budget adjustments are possible without an amendment as long as they do not imply a substantive change to the description of the action; beyond that, the modification track applies. When in doubt, ask your desk before spending.
What is the deadline for a Modification Request?
At the latest 30 calendar days before the end of the implementation period, except in duly justified exceptional cases.
What must accompany the final report?
Per your agreement: the final cost statement by category and the project's general ledger, plus the planned annexes. It is the reconciliation between the two that is checked.
A general ledger ready for the ECHO final report, with no reconstruction: request an Abvius demo.