IATI reporting is easier when the operating system already carries clean project structure, indicators, locations, finance records, and supporting evidence. This guide explains how EMPOBase helps teams get there.
An IATI activity file is a structured record of who funds what, where it happens, what it costs and what it achieves. Each element family maps to records your team already keeps — EMPOBase holds them in one project structure.
Organisation and activity identifiers, activity status, and planned versus actual dates.
Funders, implementers and partners named on the activity, each with a role.
Sector codes plus the places where work happens, from country down to site.
Baselines, targets and actuals for the indicators the activity reports against.
Budgets, commitments, disbursements and expenditure, each dated and valued.
Reports, evaluations and agreements linked to the activity they describe.
None of this waits for an XML button. Clean publishing is mostly the product of ordinary, day-to-day record discipline — start now and export day becomes routine.
Use consistent organisation, donor, project, sector, location, and reporting-period records before export. IATI quality starts with ordinary data discipline.
Link indicators, outputs, field reports, files, and finance records to the same project structure so narrative and numbers can be checked together.
Pro and Enterprise tiers support IATI-oriented export workflows. Teams should review sensitive fields before publishing externally.
Use audit logs and changelog notes when correcting figures, revising dates, or moving activities between reporting periods.
EMPOBase supports CSV and PDF exports across reporting surfaces, with IATI-compliant XML export planned for Pro and Enterprise workflows. We keep the public guide honest so teams can plan around the current product state.
Structured data out of every reporting surface — indicators, reach, finance.
Formatted reports ready to share with donors and boards.
Planned for Pro and Enterprise export workflows — follow progress on the roadmap.
EMPOBase keeps projects, indicators, finance and evidence in one structure — so reporting day is an export, not a reconstruction.
