Sitemap

Activity Standard

This section details the IATI Activity standard. It contains the following main areas:

• Overview - an introduction to key aspects of the activity standard.

• Elements - details on each and every element and attribute of the standard, including relevant code lists, rules and example usage.

Additionally:

• A summary table provides an overview of all aspects of the activity standard.

• An example XML file is provided, which is also used throughout the documentation.

Definition

The IATI activity standard is designed for reporting the details of individual development cooperation activities/projects. An activity is defined by the reporting organisation. Depending on who is reporting, it might be a large programme, a small project or another logical grouping of work and resources.

The IATI activity standard is the most widely used part of IATI. The activity standard supports around forty different fields, referenced by standard codelists, and designed to capture information about many different kinds of aid activities.

Organisations publish this data in an activity file. It is expected that every organisation publishing IATI data should include one at least activity file.

A activity file can detail one or many activities, and a organisation can publish one or many files.

Considerations

When declaring information using the IATI activity standard the following should be considered:

• What is the name and description of the activity?

• What is the unique identifier </activity-standard/overview/iati-identifier/> of the activity?

• What dates help describe the timeframe of the activity?

• Which organisations are involved, and what is their role?

• Where is the activity geographically?

• How is the activity classified?

• What are the activity’s financial details, including budgets and transactions over time?

• What are the expected and actual results?

• How is the activity linked to other activities?

• What public documents help us find out more?

• Can any Creditor Reporting System and/or Forward Survey Spending data be included?

• What are the designated contact details for the activity?

Contents

Overview

These overview pages provide initial guidance and information about the IATI activity standard.

Further guidance, examples and details can be found in the reference section.

What do I need to publish?

Publishing to IATI means you are telling a story about the work your organisation does. For this you break your work down into activities, these could be your programmes or projects. For each activity you detail what the work is, where and when it is happening, who is involved and how it is being financed etc. Further detail can then be added e.g. geographic co-ordinates, results information, document links and policy markers. The IATI technical team recommends that you start by adding the details (in the form of elements) below:

Topic	Element	Mandatory (at v2.x)	Recommended
Identification	IATI Identifier	Yes	Yes
	Reporting Org	Yes	Yes
Basic Activity Information	Title	Yes	Yes
	Description	Yes	Yes
	Activity Status	Yes	Yes
	Activity Date	Yes	Yes
Participating Organisations	Participating Org	Yes	Yes
Geopolitical Information	Recipient Country		Yes
	Or, Recipient Region		Yes
Classifications	Sector	Yes	Yes
Financial	Budget		Yes
	Transactions		Yes

Please note that elements only became mandatory at version 2.0 of the IATI Standard. If you are publishing at version 1.x then these elements are still recommended.

A full table of elements that can be reported in IATI is available here:

• All elements in IATI

If you receive funding from DFID, the Dutch or Belgian government you will have additional reporting requirements, for information on these please go to the following pages:

• Dutch Requirements

• DFID Requirements

• Belgian Requirements (coming soon)

Full list of top-level elements in IATI

The table below lists all of the elements that can be included in your publishing to IATI. This includes all of the mandatory and recommended elements outlined in What to Publish.

One publishing approach is to start with the mandatory and recommended (minimum) elements, and then build up over time. Each element you include will increase the comprehensiveness of your data and will help people to understand the work you are carrying out.

List of top-level elements

Topic	Element	Mandatory	Recommended (minimum)
Identification	IATI Identifier	Yes	Yes
	Reporting Org	Yes	Yes
	Other Identifier
Basic Activity Information	Title	Yes	Yes
	Description	Yes	Yes
	Activity Status	Yes	Yes
	Activity Date	Yes	Yes
	Contact Info
	Activity Scope
Participating Organisations	Participating Org	Yes	Yes
Geopolitical Information	Recipient Country		Yes
	Or, Recipient Region		Yes
	Location
Classifications	Sector	Yes	Yes
	Policy Marker
	Collaboration Type
	Default Flow Type
	Default Finance Type
	Default Aid Type
	Default Tied Status
	Country Budget Items
Humanitarian	Humanitarian Scope
Financial	Budget		Yes
	Transactions		Yes
	Planned Disbursement
	Capital Spend
Related Documents	Document Link
Relations	Related Activity
	Legacy Data
Performance	Conditions
	Results
OECD Reporting	CRS-add
	FSS

Activity Standard Summary Table

Section	Item	Description	Type	Codelist	XML	Occur	Rules
iati-activities		Top-level list of one or more IATI activity records.			iati-activities
	version	A number indicating the IATI specification version in use. This is mandatory and must be a valid version.	xsd:string	Version	iati-activities/@version	1..1
	generated-datetime	A date/time stamp for when this file was generated. This is not necessarily the last-updated date for the individual activity records in it. Use of this attribute is highly recommended, to allow recipients to know when a file has been updated.	xsd:dateTime		iati-activities/@generated-datetime	0..1
	linked-data-default	If a publisher chooses to publish linked data about their IATI activities then allowing them to declare where this data is published would support discovery of it, and any additional information they may choose to publish as Linked Data alongside it. This attribute is a URI path upon which an activity identifier can be appended to get a differentiable URI for any activity contained within a file. Where a publisher declares using one of these properties that authoritative linked data is accessible for an activity then consuming applications that are generating Linked Data from an IATI XML file should assert an owl:sameAs relationship to the relevant URI.	xsd:anyURI		iati-activities/@linked-data-default	0..1
iati-activity		Top-level element for a single IATI activity report.			iati-activities/iati-activity	1..*
	last-updated-datetime	The last date/time that the data for this specific activity was updated. This date must change whenever the value of any field changes.	xsd:dateTime		iati-activities/iati-activity/@last-updated-datetime	0..1	@last-updated-datetime must not be more recent than the current date
	xml:lang	A code specifying the default language of text in this activity. It is recommended that wherever possible only codes from ISO 639-1 are used. If this is not declared then the xml:lang attribute MUST be specified for each narrative element.		Language	iati-activities/iati-activity/@xml:lang	0..1	@xml:lang must exist, otherwise all lang must exist.
	default-currency	Default ISO 4217 alphabetic currency code for all financial values in this activity report. If this is not declared then the currency attribute MUST be specified for all monetary values.	xsd:string	Currency	iati-activities/iati-activity/@default-currency	0..1	@default-currency must exist, otherwise all currency must exist.
	humanitarian	A process flag to indicate that this activity relates entirely or partially to humanitarian aid.	xsd:boolean		iati-activities/iati-activity/@humanitarian	0..1
	hierarchy	The hierarchical level within the reporting organisation’s subdivision of its units of aid. (eg activity = 1; sub-activity = 2; sub-sub-activity = 3). If hierarchy is not reported then 1 is assumed. If multiple levels are reported then, to avoid double counting, financial transactions should only be reported at the lowest hierarchical level.	xsd:int		iati-activities/iati-activity/@hierarchy	0..1
	linked-data-uri	A Linked Data URI for a given activity (overrides iati-activities/@linked-data-default if set)	xsd:anyURI		iati-activities/iati-activity/@linked-data-uri	0..1
	budget-not-provided	A code indicating the reason why this activity does not contain any iati-activity/budget elements. The attribute MUST only be used when no budget elements are present.	xsd:string	Budget Not Provided	iati-activities/iati-activity/@budget-not-provided	0..1
iati-identifier		A globally unique identifier for the activity. This MUST be prefixed with EITHER the current IATI organisation identifier for the reporting organisation (reporting-org/@ref) OR a previous identifier reported in other-identifier, and suffixed with the organisation’s own activity identifier. The prefix and the suffix should be separated by a hyphen “-“. Once an activity has been reported to IATI its identifier MUST NOT be changed in subsequent updates.			iati-activities/iati-activity/iati-identifier	1..1	iati-identifier should match the regex [^\/\&\|\?]+
			xsd:string		iati-activities/iati-activity/iati-identifier/text()
reporting-org		The organisation issuing the report. May be a primary source (reporting on its own activity as donor, implementing agency, etc) or a secondary source (reporting on the activities of another organisation). Specifying the @ref attribute is mandatory. May contain the organisation name as content. All activities in an activity xml file must contain the same @ref AND this @ref must be the same as the iati-identifier recorded in the registry publisher record of the account under which this file is published.			iati-activities/iati-activity/reporting-org	1..1
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}.	xsd:string		iati-activities/iati-activity/reporting-org/@ref	1..1	reporting-org/@ref should match the regex [^\/\&\|\?]+
	type	The type of organisation issuing the report. See IATI codelist for values.	xsd:string	Organisation Type	iati-activities/iati-activity/reporting-org/@type	1..1
	secondary-reporter	A flag indicating that the reporting organisation of this activity is acting as a secondary reporter. A secondary reporter is one that reproduces data on the activities of an organisation for which it is not directly responsible. This does not include a publisher officially assigned as a proxy to report on behalf of another.	xsd:boolean		iati-activities/iati-activity/reporting-org/@secondary-reporter	0..1
	narrative	The name of the organisation. May be repeated for different languages.			iati-activities/iati-activity/reporting-org/narrative	1..*
			xsd:string		iati-activities/iati-activity/reporting-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/reporting-org/narrative/@xml:lang	0..1
title		A short, human-readable title that contains a meaningful summary of the activity. May be repeated for different languages.			iati-activities/iati-activity/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/title/narrative/@xml:lang	0..1
description		A longer, human-readable description containing a meaningful description of the activity. May be repeated for different languages.			iati-activities/iati-activity/description	1..*
	type	The type of description being provided. This is not required if only one general description of the activity is reported.	xsd:string	Description Type	iati-activities/iati-activity/description/@type	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/description/narrative/@xml:lang	0..1
participating-org		An organisation involved with the activity. May be a donor, fund, agency, etc. Specifying the @ref identifier is strongly recommended. May contain the organisation name as narrative. If the reporting organisation plays a role in the activity it should be repeated here. One organisation may play more than one role (eg, funding and implementing): in such a case each role should be reported and the name of the organisation repeated.			iati-activities/iati-activity/participating-org	1..*
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.	xsd:string		iati-activities/iati-activity/participating-org/@ref	0..1	participating-org/@ref should match the regex [^\/\&\|\?]+ Either @ref or narrative must be present.
	type	The type of organisation issuing the report. See IATI codelist for values.	xsd:string	Organisation Type	iati-activities/iati-activity/participating-org/@type	0..1
	role	An IATI code describing the organisation’s role in the activity (donor, agency, etc.).	xsd:string	Organisation Role	iati-activities/iati-activity/participating-org/@role	1..1
	activity-id	A valid activity identifier published by the participating organisation which points to the activity that it has published to IATI that describes its role in this activity.	xsd:string		iati-activities/iati-activity/participating-org/@activity-id	0..1
	crs-channel-code	Under CRS++ Reporting Directives this code identifies the implementing agency. Codes ending in ‘00’ are generic and are similar to the OrganisationType code.	xsd:string	CRS Channel Code	iati-activities/iati-activity/participating-org/@crs-channel-code	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/participating-org/narrative	0..*	Either narrative or @ref must be present.
			xsd:string		iati-activities/iati-activity/participating-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/participating-org/narrative/@xml:lang	0..1
other-identifier		An other identifier for the activity. This may be a publishers own identifier that it wishes to record with the activity. This element is also used to trace changes to activity identifiers, for example when and organisation has changed it’s organisation identifier.			iati-activities/iati-activity/other-identifier	0..*
	ref	The identifier you wish to report. This can be used to report a number of different types of identifiers. See the OtherIdentifierType codelist for details and options.	xsd:string		iati-activities/iati-activity/other-identifier/@ref	1..1
	type	The type of identifier being reported, taken from the OtherIdentifierType codelist.	xsd:string	Other Identifier Type	iati-activities/iati-activity/other-identifier/@type	1..1
	owner-org	Where applicable, the organisation that owns the other identifier being reported. When used, then either other-identifier/owner-org/@ref or other-identifier/owner-org/narrative/text() MUST be present.			iati-activities/iati-activity/other-identifier/owner-org	0..1
	ref	An organisation identifier. This is NOT MANDATORY but when used MUST contain a valid organisation identifier.	xsd:string		iati-activities/iati-activity/other-identifier/owner-org/@ref	0..1	Either @ref or narrative must be present.
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/other-identifier/owner-org/narrative	0..*	Either narrative or @ref must be present.
			xsd:string		iati-activities/iati-activity/other-identifier/owner-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/other-identifier/owner-org/narrative/@xml:lang	0..1
activity-status		The current status of the activity. See codelist for values.			iati-activities/iati-activity/activity-status	1..1
	code	An IATI code defining the current status of the activity.	xsd:string	Activity Status	iati-activities/iati-activity/activity-status/@code	1..1
activity-date		The planned and actual start and completion dates of the activity. Start dates may reflect either the commencement of funding, planning or physical activity. End dates should, wherever possible, reflect the ending of physical activity. The narrative content may contain text (e.g. 2011Q1) for accurately recording less specific dates such as month, quarter, or year.			iati-activities/iati-activity/activity-date	1..*	activity-date[@type='1' or @type='2'] must be present.
	type	An IATI code defining the type of activity date being reported.	xsd:string	Activity Date Type	iati-activities/iati-activity/activity-date/@type	1..1
	iso-date		xsd:date		iati-activities/iati-activity/activity-date/@iso-date	1..1	activity-date[@type='1']/@iso-date must be before or the same as activity-date[@type='3']/@iso-date activity-date[@type='2']/@iso-date must be before or the same as activity-date[@type='4']/@iso-date activity-date[@type='2']/@iso-date must not be in the future. activity-date[@type='4']/@iso-date must not be in the future.
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/activity-date/narrative	0..*
			xsd:string		iati-activities/iati-activity/activity-date/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/activity-date/narrative/@xml:lang	0..1
contact-info		Contact information for the activity. Specify whatever is available. You may repeat this element for each contact person.			iati-activities/iati-activity/contact-info	0..*
	type	The type of contact. See IATI codelist for values.	xsd:string	Contact Type	iati-activities/iati-activity/contact-info/@type	0..1
	organisation	The name of the organisation to contact for more information about the activity.			iati-activities/iati-activity/contact-info/organisation	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/contact-info/organisation/narrative	1..*
			xsd:string		iati-activities/iati-activity/contact-info/organisation/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/contact-info/organisation/narrative/@xml:lang	0..1
	department	The department within the organisation to contact for more information about the activity.			iati-activities/iati-activity/contact-info/department	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/contact-info/department/narrative	1..*
			xsd:string		iati-activities/iati-activity/contact-info/department/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/contact-info/department/narrative/@xml:lang	0..1
	person-name	The name of the contact person for the activity.			iati-activities/iati-activity/contact-info/person-name	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/contact-info/person-name/narrative	1..*
			xsd:string		iati-activities/iati-activity/contact-info/person-name/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/contact-info/person-name/narrative/@xml:lang	0..1
	job-title	The job title of the contact person at the organisation.			iati-activities/iati-activity/contact-info/job-title	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/contact-info/job-title/narrative	1..*
			xsd:string		iati-activities/iati-activity/contact-info/job-title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/contact-info/job-title/narrative/@xml:lang	0..1
	telephone	The contact telephone number. May be repeated for multiple numbers.			iati-activities/iati-activity/contact-info/telephone	0..*
			xsd:string		iati-activities/iati-activity/contact-info/telephone/text()
	email	The contact email address. May be repeated for multiple addresses.			iati-activities/iati-activity/contact-info/email	0..*
			xsd:string		iati-activities/iati-activity/contact-info/email/text()
	website	The contact web address. May be repeated for multiple sites.			iati-activities/iati-activity/contact-info/website	0..*
			xsd:anyURI		iati-activities/iati-activity/contact-info/website/text()
	mailing-address	The contact mailing address.			iati-activities/iati-activity/contact-info/mailing-address	0..*
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/contact-info/mailing-address/narrative	1..*
			xsd:string		iati-activities/iati-activity/contact-info/mailing-address/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/contact-info/mailing-address/narrative/@xml:lang	0..1
activity-scope		The geographical scope of the activity: regional, national, sub-national, etc.			iati-activities/iati-activity/activity-scope	0..1
	code	The geographical scope. See IATI codelist for values.	xsd:string	Activity Scope	iati-activities/iati-activity/activity-scope/@code	1..1
recipient-country		A country that will benefit from this activity. If a specific country is not known the recipient-region element should be used instead. For geographical location, use the location element. Multiple countries and regions can be reported, in which case the percentage attribute MUST be used to specify the share of total commitments across all reported countries and regions. The country can also be specified at transaction rather than activity level. If recipient-country OR recipient-region are reported at the transaction level, ALL transactions MUST contain a recipient-country or recipient-region element and iati-activity/recipient-country and iati-activity/recipient-region MUST NOT be used.			iati-activities/iati-activity/recipient-country	0..*
	code	ISO 3166-1 alpha-2 code for the country.	xsd:string	Country	iati-activities/iati-activity/recipient-country/@code	1..1
	percentage	The percentage of total commitments or total activity budget to this item. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign. Percentages for all reported countries and regions within a vocabulary MUST add up to 100.	xsd:decimal		iati-activities/iati-activity/recipient-country/@percentage	0..1	The sum of values matched at recipient-country/@percentage and recipient-region/@percentage must be 100. The value of each of the elements described by recipient-country/@percentage must be at least 0.0 no more than 100.0 (inclusive).
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/recipient-country/narrative	0..*
			xsd:string		iati-activities/iati-activity/recipient-country/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/recipient-country/narrative/@xml:lang	0..1
recipient-region		A supranational geopolitical region that will benefit from this activity. For sub-national geographical location, use the location element. Multiple countries and regions can be reported, in which case the percentage attribute MUST be used to specify the share of total commitments across all reported countries and regions. Recipient-region must not be used merely to describe the region of a country reported in recipient-country, but ONLY if the region is a recipient IN ADDITION to the country. Region can also be reported at transaction rather than activity level. If transaction/recipient-country AND/OR transaction/recipient-region are used THEN ALL transaction elements MUST contain a recipient-country and/or recipient-region element AND iati-activity/recipient-region and iati-activity/recipient-region MUST NOT be used AND each transaction MUST only contain one recipient-country or recipient-region.			iati-activities/iati-activity/recipient-region	0..*
	code	Either an OECD DAC or UN region code. Codelist is determined by vocabulary attribute.	xsd:string	(Region)	iati-activities/iati-activity/recipient-region/@code	1..1
	vocabulary	An IATI code for the vocabulary from which the region code is drawn. If it is not present 1 - ‘OECD DAC’ is assumed.	xsd:string	Region Vocabulary	iati-activities/iati-activity/recipient-region/@vocabulary	0..1
	vocabulary-uri	The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.	xsd:anyURI		iati-activities/iati-activity/recipient-region/@vocabulary-uri	0..1
	percentage	The percentage of total commitments or total activity budget to this item. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign. Percentages for all reported countries and regions within a vocabulary MUST add up to 100.	xsd:decimal		iati-activities/iati-activity/recipient-region/@percentage	0..1	The sum of values matched at recipient-region/@percentage and recipient-country/@percentage must be 100. The value of each of the elements described by recipient-region/@percentage must be at least 0.0 no more than 100.0 (inclusive).
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/recipient-region/narrative	0..*
			xsd:string		iati-activities/iati-activity/recipient-region/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/recipient-region/narrative/@xml:lang	0..1
location		The sub-national geographical identification of the target locations of an activity. These can be described by gazetteer reference, coordinates, administrative areas or a textual description. Any number of locations may be reported.			iati-activities/iati-activity/location	0..*
	ref	An internal reference that describes the location in the reporting organisation’s own system.	xsd:string		iati-activities/iati-activity/location/@ref	0..1
	location-reach	Does this location describe where the activity takes place or where the intended beneficiaries reside?			iati-activities/iati-activity/location/location-reach	0..1
	code	An IATI code for the geographic scope of the activity.	xsd:string	Geographic Location Reach	iati-activities/iati-activity/location/location-reach/@code	1..1
	location-id	A unique code describing the location according to a recognised gazetteer or administrative boundary repository. Administrative areas should only be reported here if the location being defined is the administrative area itself. For describing the administrative area/s within which a more specific location falls the location/administrative element should be used.			iati-activities/iati-activity/location/location-id	0..*
	code	A code from the gazetteer or administrative boundary repository specified by the vocabulary	xsd:string		iati-activities/iati-activity/location/location-id/@code	1..1
	vocabulary	An IATI code for a recognised gazetteer or administrative boundary repository.	xsd:string	Geographic Vocabulary	iati-activities/iati-activity/location/location-id/@vocabulary	1..1
	name	The human-readable name for the location.			iati-activities/iati-activity/location/name	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/location/name/narrative	1..*
			xsd:string		iati-activities/iati-activity/location/name/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/location/name/narrative/@xml:lang	0..1
	description	A description that qualifies the location, not the activity.			iati-activities/iati-activity/location/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/location/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/location/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/location/description/narrative/@xml:lang	0..1
	activity-description	A description that qualifies the activity taking place at the location. This should not duplicate information provided in the main activity description, and should typically be used to distinguish between activities at multiple locations within a single iati-activity record.			iati-activities/iati-activity/location/activity-description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/location/activity-description/narrative	1..*
			xsd:string		iati-activities/iati-activity/location/activity-description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/location/activity-description/narrative/@xml:lang	0..1
	administrative	Coded identification of national and sub-national divisions according to recognised administrative boundary repositories. Multiple levels may be reported.			iati-activities/iati-activity/location/administrative	0..*
	code	The code for the administrative area being reported from the vocabulary specified.	xsd:string	(Country)	iati-activities/iati-activity/location/administrative/@code	1..1
	vocabulary	An IATI code for a recognised administrative boundary repository.	xsd:string	Geographic Vocabulary	iati-activities/iati-activity/location/administrative/@vocabulary	1..1
	level	A number defining a subdivision within a hierarchical system of administrative areas. The precise system for defining the particular meaning of each @level value is determined by the @vocabulary being used.	xsd:nonNegativeInteger		iati-activities/iati-activity/location/administrative/@level	0..1
	point	The point element is based on a subset of the GML 3.3 Point element.			iati-activities/iati-activity/location/point	0..1
	srsName	The name of the spatial reference system used by the coordinates. Always: http://www.opengis.net/def/crs/EPSG/0/4326	xsd:string		iati-activities/iati-activity/location/point/@srsName	1..1
	pos	The latitude and longitude coordinates in the format “lat lng”	xsd:string		iati-activities/iati-activity/location/point/pos	1..1
	exactness	Defines whether the location represents the most distinct point reasonably possible for this type of activity or is an approximation due to lack of more detailed information.			iati-activities/iati-activity/location/exactness	0..1
	code	A code from the Geographic Exactness Codelist.	xsd:string	Geographic Exactness	iati-activities/iati-activity/location/exactness/@code	1..1
	location-class	Whether the location refers to a structure, a populated place (e.g. city or village), an administrative division, or another topological feature (e.g. river, nature reserve).			iati-activities/iati-activity/location/location-class	0..1
	code	A code from the Location Class codelist	xsd:string	Geographic Location Class	iati-activities/iati-activity/location/location-class/@code	1..1
	feature-designation	A more refined coded classification of the type of feature referred to by this location.			iati-activities/iati-activity/location/feature-designation	0..1
	code	A feature designation code form the authorised list (maintained by the US National Geospatial-Intelligence Agency)	xsd:string	Location Type	iati-activities/iati-activity/location/feature-designation/@code	1..1
sector		A recognised code, from a recognised vocabulary, classifying the purpose of the activity. Sector MUST EITHER be reported here OR at transaction level for ALL transactions			iati-activities/iati-activity/sector	0..*	Either sector or transaction/sector must be present. sector must exist, otherwise all sector must exist. If count(sector[@vocabulary=98 or @vocabulary=99]) > 0 evaluates to true, then count(sector[@vocabulary=98 or @vocabulary=99]/narrative) >= count(sector[@vocabulary=98 or @vocabulary=99]) must evaluate to true.
	vocabulary	An IATI code for the vocabulary (see codelist) used for sector classifications. If omitted, OECD DAC 5-digit Purpose Codes are assumed. It is recommended that OECD DAC 5-digit Purpose Codes are used wherever possible. It is also recommended that if a publisher has its own classification system or systems then the vocabularies 99 or 98 (Reporting Organisation’s own vocabularies) should be used in addition to DAC codes. Publishers using 98 or 99 must also include a narrative in the narrative element. Note that if multiple sector codes are used in multiple vocabularies, then each vocabulary’s percentages should add up to 100. Sector can also be reported at the transaction level rather than the activity level. Sector must only be reported at EITHER transaction level OR activity level.	xsd:string	Sector Vocabulary	iati-activities/iati-activity/sector/@vocabulary	0..1
	vocabulary-uri	The URI where this vocabulary is defined. If the vocabulary is 99 or 98 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.	xsd:anyURI		iati-activities/iati-activity/sector/@vocabulary-uri	0..1
	code	The code for the sector.	xsd:string	(DAC 5 Digit Sector)(DAC 3 Digit Sector)(UN Sustainable Development Goals (SDG))(UN Sustainable Development Goals (SDG) Targets)	iati-activities/iati-activity/sector/@code	1..1
	percentage	The percentage of total commitments or total activity budget to this item. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign. All reported sectors from the same vocabulary MUST add up to 100.	xsd:decimal		iati-activities/iati-activity/sector/@percentage	0..1	The sum of values matched at sector[@vocabulary = '1' or not(@vocabulary)]/@percentage must be 100. The value of each of the elements described by sector/@percentage must be at least 0.0 no more than 100.0 (inclusive).
	narrative	The description of a sector defined by the reporting organisation. (Only to be used when the reporting organisation’s own vocabulary is being used).			iati-activities/iati-activity/sector/narrative	0..*
			xsd:string		iati-activities/iati-activity/sector/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/sector/narrative/@xml:lang	0..1
tag		Categorisations from established taxonomies that enrich the classification of the activity but that, unlike those reported in the sector element, cannot be associated with percentage splits on finances.			iati-activities/iati-activity/tag	0..*
	code	The code for the tag as defined in the specified vocabulary.	xsd:string	(UN Sustainable Development Goals (SDG))(UN Sustainable Development Goals (SDG) Targets)	iati-activities/iati-activity/tag/@code	1..1
	vocabulary	An IATI code for the vocabulary or taxonomy (see non-embedded codelist) used for tag classifications.	xsd:string	Tag Vocabulary	iati-activities/iati-activity/tag/@vocabulary	1..1
	vocabulary-uri	The URI where this vocabulary is defined.	xsd:anyURI		iati-activities/iati-activity/tag/@vocabulary-uri	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/tag/narrative	0..*
			xsd:string		iati-activities/iati-activity/tag/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/tag/narrative/@xml:lang	0..1
country-budget-items		This item encodes the alignment of activities with both the functional and administrative classifications used in the recipient country’s Chart of Accounts. This applies to both on- and off-budget activities.			iati-activities/iati-activity/country-budget-items	0..1
	vocabulary	An IATI code for the common functional classification or country system (This allows for common codes, country-specific, or any other classification agreed between countries and donors).	xsd:string	Budget Identifier Vocabulary	iati-activities/iati-activity/country-budget-items/@vocabulary	1..1
	budget-item	Identifier for a single item in the recipient-country budget. If more than one identifier is reported the percentage share must be reported and all percentages should add up to 100 percent.			iati-activities/iati-activity/country-budget-items/budget-item	1..*
	code	A code for the budget-item from the vocabulary specified.	xsd:string	(Budget Identifier)	iati-activities/iati-activity/country-budget-items/budget-item/@code	1..1
	percentage	When multiple budget-item elements are declared within a single country-budget-items element, then, for each vocabulary used, the percentage values should sum 100%.	xsd:decimal		iati-activities/iati-activity/country-budget-items/budget-item/@percentage	0..1	The value of each of the elements described by country-budget-items/budget-item/@percentage must be at least 0.0 no more than 100.0 (inclusive).
	description	A longer, human-readable description of the budget-item. May be repeated for different languages.			iati-activities/iati-activity/country-budget-items/budget-item/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/country-budget-items/budget-item/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/country-budget-items/budget-item/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/country-budget-items/budget-item/description/narrative/@xml:lang	0..1
humanitarian-scope		Classification of emergencies, appeals and other humanitarian events and actions.			iati-activities/iati-activity/humanitarian-scope	0..*
	type	A code for the type of event or action being classified.	xsd:string	Humanitarian Scope Type	iati-activities/iati-activity/humanitarian-scope/@type	1..1
	vocabulary	A code for a recognised vocabulary of terms classifying the event or action.	xsd:string	Humanitarian Scope Vocabulary	iati-activities/iati-activity/humanitarian-scope/@vocabulary	1..1
	vocabulary-uri	A u.r.i. for the vocabulary specified which provides access to the list of codes and descriptions.	xsd:anyURI		iati-activities/iati-activity/humanitarian-scope/@vocabulary-uri	0..1
	code	A code for the event or action from the vocabulary specified.	xsd:string		iati-activities/iati-activity/humanitarian-scope/@code	1..1
	narrative	The description of the code specified.			iati-activities/iati-activity/humanitarian-scope/narrative	0..*
			xsd:string		iati-activities/iati-activity/humanitarian-scope/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/humanitarian-scope/narrative/@xml:lang	0..1
policy-marker		A policy or theme addressed by the activity. This element was designed for the reporting of OECD DAC CRS policy markers (columns 20-23 and 28-31 of the CRS++ reporting format) but the vocabulary attribute allows it use by other (including local) systems. This element can be repeated for each policy marker.			iati-activities/iati-activity/policy-marker	0..*
	vocabulary	An IATI code for the vocabulary to be used to define policy markers. If omitted then the OECD DAC vocabulary is assumed.	xsd:string	Policy Marker Vocabulary	iati-activities/iati-activity/policy-marker/@vocabulary	0..1
	vocabulary-uri	If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined.	xsd:anyURI		iati-activities/iati-activity/policy-marker/@vocabulary-uri	0..1
	code	A policy marker code from the codelist specified in the vocabulary.	xsd:string	(Policy Marker)	iati-activities/iati-activity/policy-marker/@code	1..1
	significance	An OECD DAC CRS code indicating the significance of the policy marker for this activity. This attribute MUST be used for all OECD DAC CRS vocabularies.	xsd:string	Policy Significance	iati-activities/iati-activity/policy-marker/@significance	0..1	@significance must be present if @vocabulary=’1’ or not(@vocabulary)
	narrative	A description of the policy marker. This MUST ONLY be used if vocabulary is 99 (the reporting organisation’s own marker vocabulary). May be repeated for multiple languages.			iati-activities/iati-activity/policy-marker/narrative	0..*	narrative must be present if @vocabulary=’99’
			xsd:string		iati-activities/iati-activity/policy-marker/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/policy-marker/narrative/@xml:lang	0..1
collaboration-type		The type of collaboration involved in the activity’s disbursements, e.g. “bilateral” or “multilateral”.			iati-activities/iati-activity/collaboration-type	0..1
	code	A code from the OECD DAC CRS “Bi_Multi” codelist.	xsd:string	Collaboration Type	iati-activities/iati-activity/collaboration-type/@code	1..1
default-flow-type		Whether the activity is funded by Official Development Assistance (ODA), Other Official Flows (OOF), etc			iati-activities/iati-activity/default-flow-type	0..1
	code	A code from the OECD DAC CRS “Type of flow” codelist	xsd:string	Flow Type	iati-activities/iati-activity/default-flow-type/@code	1..1
default-finance-type		The type of finance (e.g. grant, loan, debt relief, etc). This the default value for all transactions in the activity report; it can be overridden by individual transactions.			iati-activities/iati-activity/default-finance-type	0..1
	code	A code from the OECD DAC CRS “Type of finance” codelist	xsd:string	Finance Type	iati-activities/iati-activity/default-finance-type/@code	1..1
default-aid-type		The type of aid being supplied (project-type intervention, budget support, debt relief, etc.). This element specifies a default for all the activity’s financial transactions; it can be overridden at the individual transaction level.			iati-activities/iati-activity/default-aid-type	0..*
	code	A code from the specified vocabulary.	xsd:string	(Aid Type)(Earmarking Category)(Cash and Voucher Modalities)	iati-activities/iati-activity/default-aid-type/@code	1..1
	vocabulary	A code for the vocabulary aid-type classifications. If omitted the AidType (OECD DAC) codelist is assumed. The code must be a valid value in the AidTypeVocabulary codelist. Each selected vocabulary should only be used once for each activity (iati-activity/default-aid-type) or transaction (iati-activity/transaction/aid-type). All activities and/or transactions should contain a code from the DAC Type of Aid Vocabulary. The above guidelines should be converted to rules at the next integer upgrade.	xsd:string	Aid Type Vocabulary	iati-activities/iati-activity/default-aid-type/@vocabulary	0..1
default-tied-status		Whether the aid is untied, tied, or partially tied. This element specifies a default for all the activity’s financial transactions; it can be overridden at the individual transaction level. If an activity is partially tied it is recommended that tied and untied commitments are reported as separate transactions and that transaction/tied-status is used to classify them.			iati-activities/iati-activity/default-tied-status	0..1
	code	An IATI code interpreting the usage of Columns 36-38 of the CRS++ reporting format. (Amount tied, Amount partially untied, Amount tied)	xsd:string	Tied Status	iati-activities/iati-activity/default-tied-status/@code	1..1
budget		The value of the activity’s budget for each financial quarter or year over the lifetime of the activity. The purpose of this element is to provide predictability for recipient planning on an annual basis. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative. The sum of budgets may or may not match the sum of commitments, depending on a publisher’s business model and legal frameworks.			iati-activities/iati-activity/budget	0..*
	type	Whether this is the original budget (prepared when the original commitment was made) or has subsequently been revised	xsd:string	Budget Type	iati-activities/iati-activity/budget/@type	0..1
	status	The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.	xsd:string	Budget Status	iati-activities/iati-activity/budget/@status	0..1
	period-start	The start of the budget period.			iati-activities/iati-activity/budget/period-start	1..1
	iso-date		xsd:date		iati-activities/iati-activity/budget/period-start/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	period-end	The end of the period (which must not be greater than one year)			iati-activities/iati-activity/budget/period-end	1..1
	iso-date		xsd:date		iati-activities/iati-activity/budget/period-end/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	value	The budget for this period.			iati-activities/iati-activity/budget/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-activities/iati-activity/budget/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-activities/iati-activity/budget/value/@value-date	1..1
planned-disbursement		The planned disbursement element should only be used to report specific planned cash transfers. These should be reported for a specific date or a meaningfully predictable period. These transactions should be reported in addition to budgets - which are typically annual breakdowns of the total activity commitment.			iati-activities/iati-activity/planned-disbursement	0..*
	type	Whether this is an original plan (prepared when the original commitment was made) or has subsequently been revised.	xsd:string	Budget Type	iati-activities/iati-activity/planned-disbursement/@type	0..1
	period-start	The exact date of the planned disbursement OR the starting date of the period in which this specific disbursement will be made.			iati-activities/iati-activity/planned-disbursement/period-start	1..1
	iso-date		xsd:date		iati-activities/iati-activity/planned-disbursement/period-start/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date
	period-end	The ending date for the period in which this specific disbursement will be made.			iati-activities/iati-activity/planned-disbursement/period-end	0..1
	iso-date		xsd:date		iati-activities/iati-activity/planned-disbursement/period-end/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date
	value	The amount that is planned to be disbursed in the specified currency.			iati-activities/iati-activity/planned-disbursement/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-activities/iati-activity/planned-disbursement/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-activities/iati-activity/planned-disbursement/value/@value-date	1..1
	provider-org	The organisation from which the planned disbursement will originate. If omitted the reporting-org is assumed.			iati-activities/iati-activity/planned-disbursement/provider-org	0..1
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.	xsd:string		iati-activities/iati-activity/planned-disbursement/provider-org/@ref	0..1
	provider-activity-id	The identifier for the activity in which the planned disbursement will be reported. If omitted the current activity is assumed.	xsd:string		iati-activities/iati-activity/planned-disbursement/provider-org/@provider-activity-id	0..1
	type	The type of organisation providing the funds.	xsd:string	Organisation Type	iati-activities/iati-activity/planned-disbursement/provider-org/@type	0..1
	narrative	The name of the organisation. This can be repeated in multiple languages			iati-activities/iati-activity/planned-disbursement/provider-org/narrative	0..*
			xsd:string		iati-activities/iati-activity/planned-disbursement/provider-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/planned-disbursement/provider-org/narrative/@xml:lang	0..1
	receiver-org	The organisation receiving the money from the planned disbursement.			iati-activities/iati-activity/planned-disbursement/receiver-org	0..1
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.	xsd:string		iati-activities/iati-activity/planned-disbursement/receiver-org/@ref	0..1
	receiver-activity-id	If outgoing funds are being provided to another activity that is reported to IATI, this may, if possible, record the unique IATI activity identifier for that activity.	xsd:string		iati-activities/iati-activity/planned-disbursement/receiver-org/@receiver-activity-id	0..1
	type	The type of organisation receiving the funds.	xsd:string	Organisation Type	iati-activities/iati-activity/planned-disbursement/receiver-org/@type	0..1
	narrative	The name of the organisation. This can be repeated in multiple languages			iati-activities/iati-activity/planned-disbursement/receiver-org/narrative	0..*
			xsd:string		iati-activities/iati-activity/planned-disbursement/receiver-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/planned-disbursement/receiver-org/narrative/@xml:lang	0..1
capital-spend		The percentage of the total commitment that is for capital spending			iati-activities/iati-activity/capital-spend	0..1
	percentage	The percentage of the total commitment allocated to or planned for capital expenditure. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign.	xsd:decimal		iati-activities/iati-activity/capital-spend/@percentage	1..1	The value of each of the elements described by capital-spend/@percentage must be at least 0.0 no more than 100.0 (inclusive).
transaction		Transactions recording committed or actual funds flowing in or out of an aid activity.			iati-activities/iati-activity/transaction	0..*
	ref	An internal reference linking this transaction back to the publisher’s financial management system.	xsd:string		iati-activities/iati-activity/transaction/@ref	0..1
	humanitarian	A process flag to indicate that this transaction relates entirely or partially to humanitarian aid. If the entire activity relates to humanitarian aid this should be reported using iati-activity/@humanitarian, rather than for each transaction.	xsd:boolean		iati-activities/iati-activity/transaction/@humanitarian	0..1
	transaction-type	The type of the transaction (e.g. commitment, disbursement, expenditure, etc.).			iati-activities/iati-activity/transaction/transaction-type	1..1
	code	A code from the specified vocabulary.	xsd:string	Transaction Type	iati-activities/iati-activity/transaction/transaction-type/@code	1..1
	transaction-date	The date on which the transaction was made or (in the case of commitments) agreed. The narrative content may contain text (e.g. 2011Q1) for accurately recording less specific dates such as month, quarter, or year.			iati-activities/iati-activity/transaction/transaction-date	1..1
	iso-date		xsd:date		iati-activities/iati-activity/transaction/transaction-date/@iso-date	1..1	transaction-date/@iso-date must not be in the future.
	value	The amount of the contribution.			iati-activities/iati-activity/transaction/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-activities/iati-activity/transaction/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-activities/iati-activity/transaction/value/@value-date	1..1	value/@value-date must not be in the future.
	description	A human-readable description of the transaction.			iati-activities/iati-activity/transaction/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/transaction/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/transaction/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/transaction/description/narrative/@xml:lang	0..1
	provider-org	For incoming funds this is the organisation from which the transaction originated. If omitted on outgoing funds the reporting-org is assumed.			iati-activities/iati-activity/transaction/provider-org	0..1
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.	xsd:string		iati-activities/iati-activity/transaction/provider-org/@ref	0..1	transaction/provider-org/@ref should match the regex [^\/\&\|\?]+ Either @ref or narrative must be present.
	provider-activity-id	If incoming funds are being provided from the budget of another activity that is reported to IATI, it if STRONGLY RECOMMENDED that this should record the provider’s unique IATI activity identifier for that activity.	xsd:string		iati-activities/iati-activity/transaction/provider-org/@provider-activity-id	0..1
	type	The type of organisation providing the funds.	xsd:string	Organisation Type	iati-activities/iati-activity/transaction/provider-org/@type	0..1
	narrative	The name of the organisation. This can be repeated in multiple languages			iati-activities/iati-activity/transaction/provider-org/narrative	0..*	Either narrative or @ref must be present.
			xsd:string		iati-activities/iati-activity/transaction/provider-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/transaction/provider-org/narrative/@xml:lang	0..1
	receiver-org	The organisation receiving the money from the transaction (if omitted on incoming funds then the receiver organisation is assumed to be the reporting organisation).			iati-activities/iati-activity/transaction/receiver-org	0..1
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.	xsd:string		iati-activities/iati-activity/transaction/receiver-org/@ref	0..1	transaction/receiver-org/@ref should match the regex [^\/\&\|\?]+ Either @ref or narrative must be present.
	receiver-activity-id	If outgoing funds are being provided to another activity that is reported to IATI, this may, if possible, record the unique IATI activity identifier for that activity.	xsd:string		iati-activities/iati-activity/transaction/receiver-org/@receiver-activity-id	0..1
	type	The type of organisation receiving the funds.	xsd:string	Organisation Type	iati-activities/iati-activity/transaction/receiver-org/@type	0..1
	narrative	The name of the organisation. This can be repeated in multiple languages			iati-activities/iati-activity/transaction/receiver-org/narrative	0..*	Either narrative or @ref must be present.
			xsd:string		iati-activities/iati-activity/transaction/receiver-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/transaction/receiver-org/narrative/@xml:lang	0..1
	disbursement-channel	The channel through which the funds will flow for this transaction, from an IATI codelist.			iati-activities/iati-activity/transaction/disbursement-channel	0..1
	code	An IATI code defining channels of disbursement	xsd:string	Disbursement Channel	iati-activities/iati-activity/transaction/disbursement-channel/@code	1..1
	sector	A recognised code, from a recognised vocabulary, classifying the purpose of this transaction. If this element is used then ALL transaction elements should contain a transaction/sector element and iati-activity/sector should NOT be used. This element can be used multiple times, but only one sector can be reported per vocabulary.			iati-activities/iati-activity/transaction/sector	0..*	Either transaction/sector or sector must be present.
	vocabulary	An IATI code for the vocabulary (codelist) used for sector classifications. If omitted, OECD DAC 5-digit Purpose Codes are assumed. It is recommended that OECD DAC 5-digit Purpose Codes are used wherever possible. It is also recommended that if a publisher has its own classification system or systems, then the vocabularies 99 or 98 (Reporting Organisation’s own vocabularies) should be used in addition to the DAC codes. Note that at transaction level, only one sector per vocabulary can be reported.	xsd:string	Sector Vocabulary	iati-activities/iati-activity/transaction/sector/@vocabulary	0..1
	vocabulary-uri	The URI where this vocabulary is defined. If the vocabulary is 99 or 98 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.	xsd:anyURI		iati-activities/iati-activity/transaction/sector/@vocabulary-uri	0..1
	code	The code for the sector.	xsd:string	(DAC 5 Digit Sector)(DAC 3 Digit Sector)(UN Sustainable Development Goals (SDG))(UN Sustainable Development Goals (SDG) Targets)	iati-activities/iati-activity/transaction/sector/@code	1..1
	narrative	The free text description of the reporting organisation’s own sector definition. This can be repeated in multiple languages			iati-activities/iati-activity/transaction/sector/narrative	0..*
			xsd:string		iati-activities/iati-activity/transaction/sector/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/transaction/sector/narrative/@xml:lang	0..1
	recipient-country	A country that will benefit from this transaction. If a specific country is not known the recipient-region element should be used instead. If transaction/recipient-country AND/OR transaction/recipient-region are used THEN ALL transaction elements MUST contain a recipient-country or recipient-region element AND (iati-activity/recipient-country AND iati-activity/recipient-region MUST NOT be used)			iati-activities/iati-activity/transaction/recipient-country	0..1	transaction/recipient-country must not be present alongisde recipient-region and recipient-country.
	code	ISO 3166-1 alpha-2 code for the country.	xsd:string	Country	iati-activities/iati-activity/transaction/recipient-country/@code	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/transaction/recipient-country/narrative	0..*
			xsd:string		iati-activities/iati-activity/transaction/recipient-country/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/transaction/recipient-country/narrative/@xml:lang	0..1
	recipient-region	A supranational geopolitical region that will benefit from this transaction. If a specific country is not known, then this element MUST be used. If transaction/recipient-country AND/OR transaction/recipient-region are used THEN ALL transaction elements MUST contain a recipient-country or recipient-region element AND (iati-activity/recipient-country AND iati-activity/recipient-region MUST NOT be used)			iati-activities/iati-activity/transaction/recipient-region	0..1	transaction/recipient-region must not be present alongisde recipient-region and recipient-country.
	code	Either an OECD DAC or UN region code. Codelist is determined by vocabulary attribute.	xsd:string	(Region)	iati-activities/iati-activity/transaction/recipient-region/@code	1..1
	vocabulary	An IATI code for the vocabulary from which the region code is drawn. If it is not present 1 - ‘OECD DAC’ is assumed.	xsd:string	Region Vocabulary	iati-activities/iati-activity/transaction/recipient-region/@vocabulary	0..1
	vocabulary-uri	The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.	xsd:anyURI		iati-activities/iati-activity/transaction/recipient-region/@vocabulary-uri	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/transaction/recipient-region/narrative	0..*
			xsd:string		iati-activities/iati-activity/transaction/recipient-region/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/transaction/recipient-region/narrative/@xml:lang	0..1
	flow-type	Optional element to override the top-level default-flow-type element.			iati-activities/iati-activity/transaction/flow-type	0..1
	code	A code from the OECD DAC CRS “Type of flow” codelist	xsd:string	Flow Type	iati-activities/iati-activity/transaction/flow-type/@code	1..1
	finance-type	Optional element to override the top-level default-finance-type element on a transaction-by-transaction basis, if needed.			iati-activities/iati-activity/transaction/finance-type	0..1
	code	A code from the OECD DAC CRS “Type of finance” codelist	xsd:string	Finance Type	iati-activities/iati-activity/transaction/finance-type/@code	1..1
	aid-type	Optional element to override the top-level default-aid-type element (debt relief, etc.) on a transaction-by-transaction basis if needed.			iati-activities/iati-activity/transaction/aid-type	0..*
	code	A code from the specified vocabulary.	xsd:string	(Aid Type)(Earmarking Category)(Cash and Voucher Modalities)	iati-activities/iati-activity/transaction/aid-type/@code	1..1
	vocabulary	A code for the vocabulary aid-type classifications. If omitted the AidType (OECD DAC) codelist is assumed. The code must be a valid value in the AidTypeVocabulary codelist. Each selected vocabulary should only be used once for each activity (iati-activity/default-aid-type) or transaction (iati-activity/transaction/aid-type). All activities and/or transactions should contain a code from the DAC Type of Aid Vocabulary. The above guidelines should be converted to rules at the next integer upgrade.	xsd:string	Aid Type Vocabulary	iati-activities/iati-activity/transaction/aid-type/@vocabulary	0..1
	tied-status	Optional element to override the top-level default-tied-status element on a transaction-by-transaction basis if needed.			iati-activities/iati-activity/transaction/tied-status	0..1
	code	An IATI code interpreting the usage of Columns 36-38 of the CRS++ reporting format. (Amount tied, Amount partially untied, Amount tied)	xsd:string	Tied Status	iati-activities/iati-activity/transaction/tied-status/@code	1..1
document-link		A link to an online, publicly accessible web page or document.			iati-activities/iati-activity/document-link	0..*
	url	The target URL of the external document, e.g. “http://www.example.org/doc.odt”.	xsd:anyURI		iati-activities/iati-activity/document-link/@url	1..1
	format	An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.	xsd:string	File Format	iati-activities/iati-activity/document-link/@format	1..1
	title	A short, human-readable title.			iati-activities/iati-activity/document-link/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/document-link/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/document-link/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/document-link/title/narrative/@xml:lang	0..1
	description	A description of the document contents, or guidance on where to access the relevant information in the document.			iati-activities/iati-activity/document-link/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/document-link/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/document-link/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/document-link/description/narrative/@xml:lang	0..1
	category	IATI Document Category Code			iati-activities/iati-activity/document-link/category	1..*
	code	An IATI code defining the category of the document.	xsd:string	Document Category	iati-activities/iati-activity/document-link/category/@code	1..1
	language	The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.			iati-activities/iati-activity/document-link/language	0..*
	code	ISO 639-1 language code	xsd:string	Language	iati-activities/iati-activity/document-link/language/@code	1..1
	document-date	The date of publication of the document that is being linked to.			iati-activities/iati-activity/document-link/document-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/document-link/document-date/@iso-date	1..1
related-activity		Another separately reported IATI activity that is related to this one. The ‘type’ attribute describes the type of relationship: (eg. parent, child, multifunded). It is strongly recommended that linkage between activities in a hierarchical group should always be managed by use of this element with @type of 1 (parent) or 2 (child).			iati-activities/iati-activity/related-activity	0..*
	ref	A valid activity identifier (as defined in iati-activity/iati-identifier).	xsd:string		iati-activities/iati-activity/related-activity/@ref	1..1
	type	An IATI code for the type of relationship	xsd:string	Related Activity Type	iati-activities/iati-activity/related-activity/@type	1..1
legacy-data		The legacy data element allows for the reporting of values held in a field in the reporting organisation’s system which is similar, but not identical to an IATI element.			iati-activities/iati-activity/legacy-data	0..*
	name	The original field name in the reporting organisation’s system	xsd:string		iati-activities/iati-activity/legacy-data/@name	1..1
	value	The original field value in the reporting organisation’s system	xsd:string		iati-activities/iati-activity/legacy-data/@value	1..1
	iati-equivalent	The name of the equivalent IATI element.	xsd:NMTOKEN		iati-activities/iati-activity/legacy-data/@iati-equivalent	0..1
conditions		Specific terms and conditions attached to the activity that, if not met, may influence the delivery of commitments made by participating organisations.			iati-activities/iati-activity/conditions	0..1
	attached	A yes/no (1/0) value stating whether there are conditions attached to the activity. It is strongly recommended that this attribute is reported, even if there are no conditions attached (i.e. attached=”0”)	xsd:boolean		iati-activities/iati-activity/conditions/@attached	1..1
	condition	The text of a specific condition attached to the activity. Organisation-wide terms and conditions that apply to all activities should not be reported here, but in either iati-organisation/document-link or iati-activity-document-link			iati-activities/iati-activity/conditions/condition	0..*
	type	An IATI code defining the type of condition.	xsd:string	Condition Type	iati-activities/iati-activity/conditions/condition/@type	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/conditions/condition/narrative	1..*
			xsd:string		iati-activities/iati-activity/conditions/condition/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/conditions/condition/narrative/@xml:lang	0..1
result		A container for reporting outputs, outcomes, impacts and other results that stem directly from the activity. This may be repeated for each type of result reported.			iati-activities/iati-activity/result	0..*
	type	An IATI code for the type of result being reported.	xsd:string	Result Type	iati-activities/iati-activity/result/@type	1..1
	aggregation-status	Boolean flag indicating whether the data in the result set are suitable for aggregation.	xsd:boolean		iati-activities/iati-activity/result/@aggregation-status	0..1
	title	A short, human-readable title.			iati-activities/iati-activity/result/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/title/narrative/@xml:lang	0..1
	description	A longer, human-readable description.			iati-activities/iati-activity/result/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/description/narrative/@xml:lang	0..1
	document-link	A link to an online, publicly accessible web page or document expanding on the result.			iati-activities/iati-activity/result/document-link	0..*
	url	The target URL of the external document, e.g. “http://www.example.org/doc.odt”.	xsd:anyURI		iati-activities/iati-activity/result/document-link/@url	1..1
	format	An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.	xsd:string	File Format	iati-activities/iati-activity/result/document-link/@format	1..1
	title	A short, human-readable title.			iati-activities/iati-activity/result/document-link/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/document-link/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/document-link/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/document-link/title/narrative/@xml:lang	0..1
	description	A description of the document contents, or guidance on where to access the relevant information in the document.			iati-activities/iati-activity/result/document-link/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/document-link/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/document-link/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/document-link/description/narrative/@xml:lang	0..1
	category	IATI Document Category Code			iati-activities/iati-activity/result/document-link/category	1..*
	code	An IATI code defining the category of the document.	xsd:string	Document Category	iati-activities/iati-activity/result/document-link/category/@code	1..1
	language	The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.			iati-activities/iati-activity/result/document-link/language	0..*
	code	ISO 639-1 language code	xsd:string	Language	iati-activities/iati-activity/result/document-link/language/@code	1..1
	document-date	The date of publication of the document that is being linked to.			iati-activities/iati-activity/result/document-link/document-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/result/document-link/document-date/@iso-date	1..1
	reference	A reference element to allow for the coded identification of a results framework.			iati-activities/iati-activity/result/reference	0..*
	code	A code from the codelist identified in vocabulary that identifies a results framework.	xsd:string		iati-activities/iati-activity/result/reference/@code	1..1
	vocabulary	A code for the results framework vocabulary. The code must be a valid value in the ResultVocabulary codelist.	xsd:string	Result Vocabulary	iati-activities/iati-activity/result/reference/@vocabulary	1..1
	vocabulary-uri	The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.	xsd:anyURI		iati-activities/iati-activity/result/reference/@vocabulary-uri	0..1
	indicator	The indicator(s) that meet the results. There can be multiple indicators for each result.			iati-activities/iati-activity/result/indicator	1..*
	measure	An IATI code defining the unit of measure in which the value is reported.	xsd:string	Indicator Measure	iati-activities/iati-activity/result/indicator/@measure	1..1
	ascending	A boolean describing the behaviour of the indicator. It is “true” if the indicator improves from small to large (e.g. clinics built); false if it improves from large to small (e.g. cases of a disease).	xsd:boolean		iati-activities/iati-activity/result/indicator/@ascending	0..1
	aggregation-status	Boolean flag indicating whether the data in the result set are suitable for aggregation.	xsd:boolean		iati-activities/iati-activity/result/indicator/@aggregation-status	0..1
	title	A short, human-readable title.			iati-activities/iati-activity/result/indicator/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/title/narrative/@xml:lang	0..1
	description	A longer, human-readable description.			iati-activities/iati-activity/result/indicator/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/description/narrative/@xml:lang	0..1
	document-link	A link to an online, publicly accessible web page or document expanding on the result.			iati-activities/iati-activity/result/indicator/document-link	0..*
	url	The target URL of the external document, e.g. “http://www.example.org/doc.odt”.	xsd:anyURI		iati-activities/iati-activity/result/indicator/document-link/@url	1..1
	format	An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.	xsd:string	File Format	iati-activities/iati-activity/result/indicator/document-link/@format	1..1
	title	A short, human-readable title.			iati-activities/iati-activity/result/indicator/document-link/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/document-link/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/document-link/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/document-link/title/narrative/@xml:lang	0..1
	description	A description of the document contents, or guidance on where to access the relevant information in the document.			iati-activities/iati-activity/result/indicator/document-link/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/document-link/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/document-link/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/document-link/description/narrative/@xml:lang	0..1
	category	IATI Document Category Code			iati-activities/iati-activity/result/indicator/document-link/category	1..*
	code	An IATI code defining the category of the document.	xsd:string	Document Category	iati-activities/iati-activity/result/indicator/document-link/category/@code	1..1
	language	The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.			iati-activities/iati-activity/result/indicator/document-link/language	0..*
	code	ISO 639-1 language code	xsd:string	Language	iati-activities/iati-activity/result/indicator/document-link/language/@code	1..1
	document-date	The date of publication of the document that is being linked to.			iati-activities/iati-activity/result/indicator/document-link/document-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/result/indicator/document-link/document-date/@iso-date	1..1
	reference	A standardised means of identifying the indicator from a code in a recognised vocabulary. Multiple vocabularies may be specified, but each vocabulary may be specified only once for each indicator.			iati-activities/iati-activity/result/indicator/reference	0..*	There must be no more than one element or attribute matched at reference[1] or ../reference[1].
	vocabulary	A code for a recognised vocabulary of indicators. The value for this field should appear in the IndicatorVocabulary codelist.	xsd:string	Indicator Vocabulary	iati-activities/iati-activity/result/indicator/reference/@vocabulary	1..1
	code	A code for an indicator defined in the specified vocabulary specified.	xsd:string		iati-activities/iati-activity/result/indicator/reference/@code	1..1
	indicator-uri	The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.	xsd:anyURI		iati-activities/iati-activity/result/indicator/reference/@indicator-uri	0..1
	baseline	The baseline value for the indicator			iati-activities/iati-activity/result/indicator/baseline	0..*
	iso-date		xsd:date		iati-activities/iati-activity/result/indicator/baseline/@iso-date	0..1
	year	The year the baseline value was taken (yyyy)	xsd:positiveInteger		iati-activities/iati-activity/result/indicator/baseline/@year	1..1
	value	The baseline value. The @value should be omitted for qualitative measures. The @value must be included for non-qualitative measures. The @value should be a valid number for all non-qualitative measures.	xsd:string		iati-activities/iati-activity/result/indicator/baseline/@value	0..1
	location	A location already defined and described in the iati-activity/location element.			iati-activities/iati-activity/result/indicator/baseline/location	0..*
	ref	A cross-reference to the internal reference assigned to a defined location: iati-activity/location/@ref.	xsd:string		iati-activities/iati-activity/result/indicator/baseline/location/@ref	0..1
	dimension	A category used for disaggregating the result by gender, age, etc.			iati-activities/iati-activity/result/indicator/baseline/dimension	0..*
	name	Freetext description of a category being disaggregated.	xsd:string		iati-activities/iati-activity/result/indicator/baseline/dimension/@name	0..1
	value	Description of the value being disaggregated.	xsd:string		iati-activities/iati-activity/result/indicator/baseline/dimension/@value	0..1
	document-link	A link to an online, publicly accessible web page or document expanding on the result.			iati-activities/iati-activity/result/indicator/baseline/document-link	0..*
	url	The target URL of the external document, e.g. “http://www.example.org/doc.odt”.	xsd:anyURI		iati-activities/iati-activity/result/indicator/baseline/document-link/@url	1..1
	format	An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.	xsd:string	File Format	iati-activities/iati-activity/result/indicator/baseline/document-link/@format	1..1
	title	A short, human-readable title.			iati-activities/iati-activity/result/indicator/baseline/document-link/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/baseline/document-link/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/baseline/document-link/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/baseline/document-link/title/narrative/@xml:lang	0..1
	description	A description of the document contents, or guidance on where to access the relevant information in the document.			iati-activities/iati-activity/result/indicator/baseline/document-link/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/baseline/document-link/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/baseline/document-link/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/baseline/document-link/description/narrative/@xml:lang	0..1
	category	IATI Document Category Code			iati-activities/iati-activity/result/indicator/baseline/document-link/category	1..*
	code	An IATI code defining the category of the document.	xsd:string	Document Category	iati-activities/iati-activity/result/indicator/baseline/document-link/category/@code	1..1
	language	The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.			iati-activities/iati-activity/result/indicator/baseline/document-link/language	0..*
	code	ISO 639-1 language code	xsd:string	Language	iati-activities/iati-activity/result/indicator/baseline/document-link/language/@code	1..1
	document-date	The date of publication of the document that is being linked to.			iati-activities/iati-activity/result/indicator/baseline/document-link/document-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/result/indicator/baseline/document-link/document-date/@iso-date	1..1
	comment	A human-readable comment associated with a piece of aid information.			iati-activities/iati-activity/result/indicator/baseline/comment	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/baseline/comment/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/baseline/comment/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/baseline/comment/narrative/@xml:lang	0..1
	period	The period covered for the results reported. Multiple periods can be reported for a single indicator.			iati-activities/iati-activity/result/indicator/period	0..*
	period-start	The start of the reporting period.			iati-activities/iati-activity/result/indicator/period/period-start	1..1
	iso-date		xsd:date		iati-activities/iati-activity/result/indicator/period/period-start/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date
	period-end	The end of the reporting period.			iati-activities/iati-activity/result/indicator/period/period-end	1..1
	iso-date		xsd:date		iati-activities/iati-activity/result/indicator/period/period-end/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date
	target	The target milestone for this period			iati-activities/iati-activity/result/indicator/period/target	0..*
	value	The target value. The @value should be omitted for qualitative measures. The @value must be included for non-qualitative measures. The @value should be a valid number for all non-qualitative measures.	xsd:string		iati-activities/iati-activity/result/indicator/period/target/@value	0..1
	location	A location already defined and described in the iati-activity/location element.			iati-activities/iati-activity/result/indicator/period/target/location	0..*
	ref	A cross-reference to the internal reference assigned to a defined location: iati-activity/location/@ref.	xsd:string		iati-activities/iati-activity/result/indicator/period/target/location/@ref	0..1
	dimension	A category used for disaggregating the result by gender, age, etc.			iati-activities/iati-activity/result/indicator/period/target/dimension	0..*
	name	Freetext description of a category being disaggregated.	xsd:string		iati-activities/iati-activity/result/indicator/period/target/dimension/@name	0..1
	value	Description of the value being disaggregated.	xsd:string		iati-activities/iati-activity/result/indicator/period/target/dimension/@value	0..1
	comment	A human-readable comment associated with a piece of aid information.			iati-activities/iati-activity/result/indicator/period/target/comment	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/period/target/comment/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/period/target/comment/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/period/target/comment/narrative/@xml:lang	0..1
	document-link	A link to an online, publicly accessible web page or document expanding on the result.			iati-activities/iati-activity/result/indicator/period/target/document-link	0..*
	url	The target URL of the external document, e.g. “http://www.example.org/doc.odt”.	xsd:anyURI		iati-activities/iati-activity/result/indicator/period/target/document-link/@url	1..1
	format	An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.	xsd:string	File Format	iati-activities/iati-activity/result/indicator/period/target/document-link/@format	1..1
	title	A short, human-readable title.			iati-activities/iati-activity/result/indicator/period/target/document-link/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/period/target/document-link/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/period/target/document-link/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/period/target/document-link/title/narrative/@xml:lang	0..1
	description	A description of the document contents, or guidance on where to access the relevant information in the document.			iati-activities/iati-activity/result/indicator/period/target/document-link/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/period/target/document-link/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/period/target/document-link/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/period/target/document-link/description/narrative/@xml:lang	0..1
	category	IATI Document Category Code			iati-activities/iati-activity/result/indicator/period/target/document-link/category	1..*
	code	An IATI code defining the category of the document.	xsd:string	Document Category	iati-activities/iati-activity/result/indicator/period/target/document-link/category/@code	1..1
	language	The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.			iati-activities/iati-activity/result/indicator/period/target/document-link/language	0..*
	code	ISO 639-1 language code	xsd:string	Language	iati-activities/iati-activity/result/indicator/period/target/document-link/language/@code	1..1
	document-date	The date of publication of the document that is being linked to.			iati-activities/iati-activity/result/indicator/period/target/document-link/document-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/result/indicator/period/target/document-link/document-date/@iso-date	1..1
	actual	A record of the achieved result for this period.			iati-activities/iati-activity/result/indicator/period/actual	0..*
	value	The actual measure. The @value should be omitted for qualitative measures. The @value must be included for non-qualitative measures. The @value should be a valid number for all non-qualitative measures.	xsd:string		iati-activities/iati-activity/result/indicator/period/actual/@value	0..1
	location	A location already defined and described in the iati-activity/location element.			iati-activities/iati-activity/result/indicator/period/actual/location	0..*
	ref	A cross-reference to the internal reference assigned to a defined location: iati-activity/location/@ref.	xsd:string		iati-activities/iati-activity/result/indicator/period/actual/location/@ref	0..1
	dimension	A category used for disaggregating the result by gender, age, etc.			iati-activities/iati-activity/result/indicator/period/actual/dimension	0..*
	name	Freetext description of a category being disaggregated.	xsd:string		iati-activities/iati-activity/result/indicator/period/actual/dimension/@name	0..1
	value	Description of the value being disaggregated.	xsd:string		iati-activities/iati-activity/result/indicator/period/actual/dimension/@value	0..1
	comment	A human-readable comment associated with a piece of aid information.			iati-activities/iati-activity/result/indicator/period/actual/comment	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/period/actual/comment/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/period/actual/comment/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/period/actual/comment/narrative/@xml:lang	0..1
	document-link	A link to an online, publicly accessible web page or document expanding on the result.			iati-activities/iati-activity/result/indicator/period/actual/document-link	0..*
	url	The target URL of the external document, e.g. “http://www.example.org/doc.odt”.	xsd:anyURI		iati-activities/iati-activity/result/indicator/period/actual/document-link/@url	1..1
	format	An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.	xsd:string	File Format	iati-activities/iati-activity/result/indicator/period/actual/document-link/@format	1..1
	title	A short, human-readable title.			iati-activities/iati-activity/result/indicator/period/actual/document-link/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/period/actual/document-link/title/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/period/actual/document-link/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/period/actual/document-link/title/narrative/@xml:lang	0..1
	description	A description of the document contents, or guidance on where to access the relevant information in the document.			iati-activities/iati-activity/result/indicator/period/actual/document-link/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-activities/iati-activity/result/indicator/period/actual/document-link/description/narrative	1..*
			xsd:string		iati-activities/iati-activity/result/indicator/period/actual/document-link/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-activities/iati-activity/result/indicator/period/actual/document-link/description/narrative/@xml:lang	0..1
	category	IATI Document Category Code			iati-activities/iati-activity/result/indicator/period/actual/document-link/category	1..*
	code	An IATI code defining the category of the document.	xsd:string	Document Category	iati-activities/iati-activity/result/indicator/period/actual/document-link/category/@code	1..1
	language	The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.			iati-activities/iati-activity/result/indicator/period/actual/document-link/language	0..*
	code	ISO 639-1 language code	xsd:string	Language	iati-activities/iati-activity/result/indicator/period/actual/document-link/language/@code	1..1
	document-date	The date of publication of the document that is being linked to.			iati-activities/iati-activity/result/indicator/period/actual/document-link/document-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/result/indicator/period/actual/document-link/document-date/@iso-date	1..1
crs-add		Additional items specific to CRS++ reporting.			iati-activities/iati-activity/crs-add	0..1
	other-flags	This covers the four CRS++ columns titled: “Free standing technical cooperation”; “Programme-based approach”; “Investment project”; “Associated financing”			iati-activities/iati-activity/crs-add/other-flags	0..*
	code	An IATI code describing the equivalent CRS++ columns	xsd:string	CRS Additional Other Flags	iati-activities/iati-activity/crs-add/other-flags/@code	1..1
	significance	A boolean indicating whether the flag applies. If ‘false’ do not report the flag	xsd:boolean		iati-activities/iati-activity/crs-add/other-flags/@significance	1..1
	loan-terms	Loan repayment terms and interest rates			iati-activities/iati-activity/crs-add/loan-terms	0..1
	rate-1	Interest Rate. If an ODA loan with variable interest rate, report the variable rate here and the reference fixed rate as rate-2 Enter the rate without the percentage sign.	xsd:decimal		iati-activities/iati-activity/crs-add/loan-terms/@rate-1	0..1
	rate-2	Second Interest Rate. If an ODA loan with variable interest rate, report the variable rate as rate-1 and the reference fixed rate here Enter the rate without the percentage sign.	xsd:decimal		iati-activities/iati-activity/crs-add/loan-terms/@rate-2	0..1
	repayment-type	The type of loan repayment			iati-activities/iati-activity/crs-add/loan-terms/repayment-type	0..1
	code	An IATI codelist tabulating CRS-specified values for the type of Repayment.	xsd:string	Loan Repayment Type	iati-activities/iati-activity/crs-add/loan-terms/repayment-type/@code	1..1
	repayment-plan	Number of repayments per annum.			iati-activities/iati-activity/crs-add/loan-terms/repayment-plan	0..1
	code	An IATI codelist tabulating CRS-specified values for the number of repayments per annum.	xsd:string	Loan Repayment Period	iati-activities/iati-activity/crs-add/loan-terms/repayment-plan/@code	1..1
	commitment-date	The CRS++ reported commitment date			iati-activities/iati-activity/crs-add/loan-terms/commitment-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/crs-add/loan-terms/commitment-date/@iso-date	1..1
	repayment-first-date	First Repayment Date.			iati-activities/iati-activity/crs-add/loan-terms/repayment-first-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/crs-add/loan-terms/repayment-first-date/@iso-date	1..1
	repayment-final-date	Final Repayment Date.			iati-activities/iati-activity/crs-add/loan-terms/repayment-final-date	0..1
	iso-date		xsd:date		iati-activities/iati-activity/crs-add/loan-terms/repayment-final-date/@iso-date	1..1
	loan-status	The status of loan and interest repayments for the most recently reported financial year			iati-activities/iati-activity/crs-add/loan-status	0..1
	year	CRS Reporting Year (CRS++ Column 1)	xsd:decimal		iati-activities/iati-activity/crs-add/loan-status/@year	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-activities/iati-activity/crs-add/loan-status/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-activities/iati-activity/crs-add/loan-status/@value-date	1..1
	interest-received	Interest received during the reporting year	xsd:decimal		iati-activities/iati-activity/crs-add/loan-status/interest-received	0..1
	principal-outstanding	The amount of principal owed on the loan at the end of the reporting year.	xsd:decimal		iati-activities/iati-activity/crs-add/loan-status/principal-outstanding	0..1
	principal-arrears	Arrears of principal at the end of the year. Included in principal-outstanding	xsd:decimal		iati-activities/iati-activity/crs-add/loan-status/principal-arrears	0..1
	interest-arrears	Arrears of interest at the end of the year	xsd:decimal		iati-activities/iati-activity/crs-add/loan-status/interest-arrears	0..1
	channel-code	The CRS channel code for this activity. This should only be used for reporting to CRS. The code list contains both organisation types and names of organisations. For non-CRS purposes these should be reported using the participating-org element.	xsd:string		iati-activities/iati-activity/crs-add/channel-code	0..1
fss		This section allows entry of data required for the OECD DAC Forward Spending Survey at an activity level.			iati-activities/iati-activity/fss	0..1
	extraction-date	The exact date when the information was collected or extracted from donors’ aid management systems.	xsd:date		iati-activities/iati-activity/fss/@extraction-date	1..1
	priority	True if the partner country is a priority partner country.	xsd:boolean		iati-activities/iati-activity/fss/@priority	0..1
	phaseout-year	If there are plans to phase out operations from the partner country, this column shows the projected year of last disbursements.	xsd:decimal		iati-activities/iati-activity/fss/@phaseout-year	0..1
	forecast	A container to hold separate forecasts for each of the years specified Text() holds the forecast value for each year.			iati-activities/iati-activity/fss/forecast	0..*
			xsd:decimal		iati-activities/iati-activity/fss/forecast/text()
	year	The calendar year that the forward spend covers	xsd:decimal		iati-activities/iati-activity/fss/forecast/@year	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-activities/iati-activity/fss/forecast/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-activities/iati-activity/fss/forecast/@value-date	0..1

International Aid Transparency Initiative: Activity-Information Schema

Release 2.03, 2018-02-19

NOTE: the xml.xsd and iati-common.xsd schemas must be in the
same directory as this one.

This W3C XML Schema defines an XML document type for information
about one or more aid-related activities, following the standard
published at http://iatistandard.org/

This document type may be extended with additional elements and
attributes, but they must belong to an explicit XML namespace.

Activity file

Definition

The activity file contains the data defined by the IATI activity standard.

It is an XML file, containing the relevant IATI activity standard fields for the publishing organisation.

Considerations

When using the IATI activity standard to produce an activity-file, the following should be considered:

• An IATI publisher should publish at least one activity file.

• An activity file should contain at least one iati-activity

• It should be updated at least annually.

• It must be well-formed XML.

• It must validate against the relevant version of the IATI activity schema

• Any activity file must have iati-activities as the root element - to contain all other elements.

• The generated-datetime attribute of iati-activities - a date/time stamp for when the activity-file was generated - is highly recommended.

• The generated-datetime is declared at the iati-activities level. Is not necessarily the same as the last-updated-datetime for the individual iati-activity records within it.

• Across a set of activity files published by a single organisation, individual iati-activity, referenced via a unique iati-identifier, should not be duplicated.

• A link to the activity file(s) should be published on the IATI Registry.

• Ideally, this link would be to an activity file(s) on the publisher website or open data portal. However, third party tools are available to generate and host files on behalf of publishers.

• When creating the activity file it is recommended to avoid spaces and non-ascii characters in file names and urls. For example:

  • iatiactivity.xml is preferable to IATI Activity.xml.

  • http://example.org/files/iatidata/iatiactivity.xml is preferable to http://example.org/files/iati data/IATI Activity.xml.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• It is recommended that a single activity-file does not exceed 40MB in file size.

• Data publishers are encouraged to segment their data into ‘meaningful chunks’. Prior to version 2.01 they were encouraged to segment their data by country and/or regions. This is no longer necessarily considered to be best practice.

• The order of the elements presented in an activity-file must follow the order set out in the schema.

• The version of the IATI standard being used must be declared via the version attribute of the iati-activities element. This must be a valid value on the Version codelist.

Further Guidance

• For well-formed XML tests, see the W3C XML Validator

• The IATI Validator tests data against the relevant version of the IATI activity schema.

IATI Activity

Definition

Within the IATI activity standard the iati-activity is the building block to describe development cooperation activities.

An iati-activity represents a distinct grouping of information that reports various facts of an activity.

A human-readable title and description for an iati-activity can be provided using:

• title - a short, human-readable title.

• description - a longer, human-readable description.

Considerations

When using the IATI activity standard to declare an iati-activity, the following should be considered:

• Every iati-activity must have a globally unique iati-identifier

• Publishers can decide on how best to structure and segment their data around one or several iati-activity

• Publishers can decide to utilise the @hierarchy attribute to represent subdivision of units of aid.

• A publisher can set a default language and @default-currency, that is then used throughout the iati-activity. This can be overridden in subsequent elements however.

• The @last-updated-datetime date must change whenever the value of any field within the associated iati-activity is updated.

• It is recommended that the title should be concise and jargon-free

• A description can have different focal points, by using the appropriate DescriptionType codelist

• The free-text instances of title and description should avoid use of text in CAPITALS, where possible.

• Both the title and descriptions can be repeated for different languages.

• When an iati-activity is being implemented in a recipient-country where the official language is different to that of the reporting-org it is recommended that activity title and description are provided in all official reporting-org and recipient-country languages

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• The title and description are mandatory elements of any iati-activity.

• Any freetext title or description must be included in the child narrative element, which can be repeated for different languages.

• The order of the elements presented in any iati-activity must follow the order set out in the schema.

IATI Identifier

Definition

Within the IATI activity standard, the iati-identifier is the unique reference for an an iati-activity.

The iati-identifier is a concatenation of the reporting-org reference and the reference allocated to iati-activity by the reporting-org. Together, these make the iati-identifier.

Considerations

When using the IATI activity standard to declare an iati-identifier the following should be considered:

• The iati-identifier must be unique for every iati-activity within the complete dataset published.

• The iati-identifier should have no leading or trailing whitespace.

• It is recommended that no forward slashes (/) or spaces should be contained within the iati-identifier.

• It is recommended to avoid spaces and non-ascii characters.

• For example:

  • AA-AAA-123456789-ABC123 is preferable to AA-AAA-123456789-ABC 123.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• The iati-identifier must begin with either the current IATI organisation identifier for the reporting organisation or a previous identifier reported in the element other-identifier.

Further Guidance

Please also consider and refer to the Organisation Identifiers guidance when constructing an appropriate identifier.

Activity Dates

Definition

Within the IATI activity standard several types of dates can be specified.

Dates that relate directly to the iati-activity:

• activity-date - the planned and actual start/end dates of the iati-activity.

• transaction-date - the date a specific transaction took place.

• value-date - the specific date for the value of a budget or transaction, which is used for currency conversion purposes.

• period-start and period-end dates are used to describe a period of time in a budget , planned-disbursement or indicator

Additionally, a time-sensitive (non-date) declaration works in conjunction with the activity-date:

• activity-status - a numeric code to declare current stage of the iati-activity.

Considerations

When using the IATI activity standard to declare dates, the following should be considered:

• Date format for activity-date, period-start, period-end, transaction-date and value-date must be in ISO 8601 (YYYY-MM-DD), eg: 2014-03-21

• Date format for generated-datetime last-updated-datetime must use ISO 8601 date format, e.g. “2014-03-21T18:45:00+01:00”.

• A start and end date must be provided - if exact dates are not known then start planned or end planned should be used

• Any start date should be before the end date, or the same

• All dates can be updated at any point

• An activity-date can have four types:

  • start-planned (code 1) - the forecast start date for the iati-activity (e.g. if the iati-activity is in the pipeline stage or the date of the first disbursement is not known).

  • start-actual (code 2) - the actual start date for the iati-activity (e.g. the date of the first disbursement).

  • end-planned (code 3) - the forecast end date for the iati-activity.

  • end-actual (code 4)- the actual end date for the iati-activity (End dates should, wherever possible, reflect the ending of physical activity.).

• The activity-status represents the latest stage for the activity. It can be updated at any time.

• When the activity-status reaches ActivityStatus codes 3, 4 or 5 then it is recommended that an end-actual (code 4) date is added.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• The ActivityDateType codes for activity-date have changed to being numeric in versions 2.01 and above.

• Dates must be a valid xsd:date, and a datetimes must be a valid xsd:dateTime.

Organisations

Definition

Within the IATI activity standard organisations can be declared in three ways:

• reporting-org - the organisation publishing the activity file and associated data.

• participating-org - the organisation that has a role within the activity (there can be various roles)

• provider-org / receiver-org - the organisation providing or receiving a specific transaction

Considerations

When using the IATI activity standard to declare organisations, the following should be considered:

• In many cases, an activity file will contain information from the perspective of a single organisation. Most commonly, this will be the same as the reporting-org

• It is also expected that this organisation would be cited as a participating-org, along with their associated role(s).

• It is possible for multiple participating-org to be reported within a single activity.

• Multiple participating-org with the same OrganisationRole code are also feasible.

• For reporting-org and participating-org inclusion of the OrganisationType code is recommended.

• In all cases, when describing an organisation, reference to their associated unique identifier should be included.

• Should a provider-org or receiver-org within a transaction be the same as the reporting-org it is not expected that they are declared, but recommended.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• A reporting-org is a mandatory element

• A participating-org with OrganisationRole of funding (code 1) and/or implementing (code 4) is mandatory.

• A reporting-org identifier must start with a value published on the OrganisationRegistrationAgency codelist.

• Any freetext name for an organisation, must be included in the child narrative element, which can be repeated for different languages.

Further Guidance

Please consider and refer to the Organisation Identifiers guidance when constructing an appropriate identifier.

Geography

Definition

Within the IATI activity standard there are three ways to describe the geography of an iati-activity:

• recipient-country - the country that will benefit from the iati-activity.

• recipient-region - geopolitical region (above the country level) that will benefit from the iati-activity.

• location - a geographical location of the iati-activity.

In addition, the following can also be utilised:

• activity-scope - to classify the geographic coverage of the the iati-activity.

Considerations

When using the IATI activity standard to describe geography, the following should be considered:

• When describing the recipient-country the relevant Country code must be used.

• When describing the recipient-region the relevant Region code must be used.

• It is possible to have multiple recipient-country in an iati-activity

• It is possible to have multiple recipient-region in an iati-activity

• When declaring multiple recipient-country or recipient-region then a @pecentage must be declared. These must sum to 100%.

• If a recipient-country is known, then a recipient-region is not expected.

• If a recipient-country is not known, then a recipient-region is expected.

• The activity-scope element should only be used once. It must use a relevant ActivityScope code.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• It is not desirable to include the freetext name of any recipient-country or recipient-region. Only in exceptional circumstances - where the publishing organisation must provide different text to the name on the relevant Country or Region codelist.

• It is feasible to have both a recipient-country and recipient-region in the same iati-activity. In such cases, the @percentage must be declared, and sum to 100 across both elements.

• Both a recipient-country and recipient-region can also be published as child elements of a transaction. When this is done, it is expected that all transaction include such data, whilst the relevant element is subsequently not included at the iati-activity level.

Country Budget Alignment

Guidance on implementing budget and aid alignment

During the 2.03 upgrade process, decision was made to deprecate BudgetIdentifier codelist. As a result, further guidance was required to provide to publishers on implementing aid and budget alignment. This guidance explains how the methodology now works. It stems from work conducted by the IATI TAG 2017 Working Group on Aid and Budget Alignment, and reflects decisions made by the WP-STAT and IATI Steering Committee. In summary:

1) Publish the capital-spend field

For activities at the commitment stage, the percentage of an activity that is capital expenditure should be published using the capital-spend field. The definition of capital expenditure follows the IMF GFS definition:

Capital spending is generally defined as physical assets with a useful life of more than one year. But it also includes capital improvements or the rehabilitation of physical assets that enhance or extend the useful life of the asset (as distinct from repair or maintenance, which assures that the asset is functional for its planned life). Capital includes all aspects of design and construction that are required to make the asset operational. Source: D Jacobs, 2009, Capital Expenditures and the Budget, IMF PFM Technical Guidance Note No 8. (IMF, Washington)]

This definition was approved by WP-STAT under the written procedure in February 2016.

2) Publish detailed CRS purpose codes in the sector field

(a) Don’t use very broad codes

Broad “multisector aid” or “sector not specified” purpose codes are not mappable to budgets and are too aggregate to tell you much that is useful about the activity. Publishers should not use these purpose codes if they want activities to be mappable to budgets.

List of multisector codes that should not be used (source IATI 2012 Study on Better Reflecting Aid Flows in Country Budgets, Annex 4 - codes that are “not classifiable - multisector”):

• 43010 - Multisector aid

• 43050 - Non-agricultural alternative development

• 43081 - Multisector education / training

• 43082 - Research / scientific institutions

• 52010 - Food aid/food security programmes

• 99810 - Sectors not specified

(b) Use the more detailed “voluntary” CRS purpose codes, not “parent” codes

In a fairly broad sample of 35-40 countries, various studies found that more disaggregated (“voluntary”) codes under 15 existing CRS purpose codes were needed to map to budgets. Publishers should use the voluntary codes instead of the “parent” codes if they want their activities to be mappable to budgets.

The CRS purpose codes, including the more detailed voluntary codes, are listed in the DAC and CRS codelists Excel sheet .

The additional codes were approved by WP-STAT under the written procedure in February 2016. The IATI Steering Committee approved the use of the more detailed CRS purpose codes (instead of using the “Common Code” codelist) in March 2014.

Classifications

Definition

Within the IATI activity standard it is expected that classifications information is provided for any iati-activity

Namely:

• sector - the thematic catgory (or set of categories) an iati-activity operates with

Additionally, the following classifications enable the publication of various codes (often associated with CRS++ reporting)

• policy-marker

• collaboration-type

• default-finance-type

• default-flow-type

• default-aid-type

• default-tied-status

Considerations

When using the IATI activity standard to declare documents, the following should be considered:

• An iati-activity can have singular or multiple sector

• When multiple sector are described, then a @percentage should be declared for each. All reported sectors from the same vocabulary must add up to 100%.

• A @vocabulary can be declared when describing a sector. This must be on the Vocabulary codelist.

• If no @vocabulary is declared, then the DAC 5 digit codelist is assumed.

• A reporting-org can declare their own @vocabulary, via using the 99 (Reporting Org) Vocabulary code.

• Multiple or singular policy-marker can also be described. Unlike sector, there is no @percentage attribute to add.

• The classifications of default-finance-type, default-flow-type, default-aid-type and default-tied-status apply to the whole iati-activity. These can be overridden within a single transaction via using any of finance-type , flow-type , aid-type and/or tied-status.

• If an iati-activity is either wholly tied, partially tied or untied it is recommended that the appropriate default-tied-status code is used.

• If an iati-activity has more than one tied status it is recommended that the reported commitment(s) are split into the relevant tied, untied and/or partially-tied amounts and tied-status is reported at transaction level. (NB that tied status should be reported for commitments only.)

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• A sector is mandatory.

• Descriptive text / name is no longer supported for any classification elements.

• A sector can also be published as child elements of a transaction. When this is done, it is expected that all transaction include such data, whilst sector is subsequently not included at the iati-activity level.

Budgets

Definition

The monetary budgets assigned to a specific iati-activity can be described in the IATI activity standard using the following:

• transaction-type type Commitment (code 2) can be used to describe the total committed budget for the duration of the activity. Any changes to the original commitment should be reported as additional, incremental transactions (positive or negative) so that the sum of commitments represents the total committed budget.

• budget - the value of the iati-activity budget for each financial year over the lifetime of the activity, as stated in the original project document or revised accordingly. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative. The sum of budgets may or may not match the sum of commitments, depending on a publisher’s business model and legal frameworks.

• planned-disbursement - a scheduled payment, set up against the budget

Additionally, there are two areas within the IATI activity standard that allow further clarification of budgets:

• country-budget-item - alignment of iati-activity with the functional and administrative classifications used in the recipient-country Chart of Accounts.

• capital-spend - the percentage of the total commitment that is for capital spending.

These all relate to the specific iati-activity being described.

Considerations

When using the IATI activity standard to declare budgets, the following should be considered:

• It is recommended that budgets are presented in financial years.

• A budget must not span a period greater than one year.

• When presenting multiple budgets, then the budget element should be repeated accordingly.

• It is expected that the financial years for reporting-org are described.

• It is possible to report periods other than years, but this is not recommended.

• Financial periods can be presented using the period-start and period-end dates.

• For planned-disbursement it is valid to only report the period-start as a single date.

• It is possible to report budget values in multiple currencies, overriding the default currency set in iati-activity

• It is expected that budgets would be described from the reporting-org perspective.

• When declaring a value-date for any budget, this date must be in the past.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• The planned-disbursement element no longer has an @updated attribute. This has been replaced by a @type attribute

Transaction

Definition

The IATI activity standard enables transaction information to be published.

The transaction data is a core component to IATI, detailing the flow of monies between organisations.

Considerations

When using the IATI activity standard to declare transaction, the following should be considered:

• Every iati-activity should contain at least one transaction. However, this may not always be possible for early-stage activities, for example.

• Every transaction must contain a transaction-date , value, value-date and transaction-type.

• For every transaction a type contained on the TransactionType codelist is required,

• There are several types of transactions. The most common are:

  • Incoming funds (code*1*) - the funds received from a funding source (e.g. a donor).

  • Outgoing Commitment (code*2*) - the total agreed committed budget for the activity (this may or may not match the value of the activity’s budget)

  • Disbursement (code*3*) - the amount transferred to another organisation in the aid delivery chain (e.g. a partner organisation being funded).

  • Expenditure (code*4*) - the outlay on goods and services and project overheads.

• The value of a transaction can be positive or negative, and contain decimals. It should not contain comma separators (eg: 3,000)

  • example: 3000 or 3000.00 or -3000 is acceptable. 3,000 is not

• Both the transaction-date and value-date must be in ISO 8601 format (YYYY-MM-DD), eg: 2014-03-21.

• Neither of transaction-date and value-date can be in the “future”. A transaction always describes something that has taken place.

• A transaction can be declared in any currency on the Currency codelist.

• A transaction can also include finance-type , flow-type , aid-type and/or tied-status information.

• Both currency and finance-type , flow-type , aid-type, tied-status can be set as defaults in the iati-activity element. There is no requirement to restate these within a transaction if they are the same.

• A transaction can also contain information on the source and destination organisation. When describing these the provider-org and receiver-org should be used. Ideally, the unique organisation identifier would be included.

• Where possible, it is recommended that a transaction includes the provider-activity-id and/or receiver-activity-id to reference the iati-activity from which funds flow from/to.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• Dates should be a valid xsd:date, and a datetimes should be a valid xsd:dateTime.

• A recipient-country, recipient-region` and sector can also be published as child elements of a transaction. When this is done, it is expected that all transaction include such data, whilst the relevant element is subsequently not included at the iati-activity level. Also none of these elements when published as child elements of a transaction need or use a percentage attribute as they do at the iati-activity level.

Result

Definition

The IATI activity standard enables the publishing of information on measurable results from an iati-activity, through use of the result element via:

• result - a container for reporting outputs, outcomes, impacts and other results that stem directly from the iati-activity.

Considerations

When using the IATI activity standard to declare result, the following should be considered:

• Any iati-activity can have multiple result elements.

• A result must have a title and should include a description to clarify the information being detailed.

• Every result must include an indicator, which in turn details a period of time, and then a target and actual measure.

• An indicator must have a title and should include a description to clarify the information being detailed.

• An indicator can be repeated within any result.

• It is also recommended to include a baseline measure for each result recorded.

• Any target, actual and baseline can have attached a comment to provide additional narrative or information.

• The free-text instances of title, description and comment can be repeated for multiple languages, using @xml:lang.

• The free-text instances of title, description and comment should avoid use of text in CAPITALS, where possible.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• Any freetext title, description or comment must be included in the child narrative element, which can be repeated for different languages.

Related Data

Definition

Within the IATI activity standard it is possible to express relations between iati-activity records across different publishers / reporting-org.

This can be described through two methods:

• related-activity - another iati-activity that has relationship to the one being described.

• transaction - both provider-activity-id & receiver-activity-id can be used to link funds from one iati-activity to another.

Considerations

When using the IATI activity standard to declare related data, the following should be considered:

• A related-activity can be one published by any reporting-org - it does not have to be from the same publisher.

• When declaring a related-activity it is vital to include the reference to the unique iati-identifier. This enables structured links to be made.

• It is also recommended to include the type of relationship that is being expressed, through use of the RelatedActivityType code.

• When declaring links between different activities, it is recommended to use the related-activity element and associated RelatedActivityType code in all relevant iati-activities, so that all activities are related to each other.

• At the transaction level , it is recommended to connect iati-activity through use of the provider-activity-id & receiver-activity-id fields. Specifically:

  • When an Incoming Fund (code 1) is being described, use the provider-activity-id reference to declare the immediate source of the funds, using the relevant iati-identifier of the iati-activity, if published by the provider-org

  • When a Disbursement (code 3) or Commitment (code 2) is being described, use the receiver-activity-id reference to declare the immediate destination of the funds, using the relevant iati-identifier of the iati-activity, if published by the receiver-org

Related Documents

Definition

Within the IATI activity standard any number of links to supporting documents can be declared.

The main element for this is:

• document-link - a categorized link to an external document.

The following also enable the links from the iati-activity to external resources:

• linked data - declaring the path at which information on the specific iati-activity is available as linked-data

Considerations

When using the IATI activity standard to declare related documents, the following should be considered:

• All document-link should be presented in the form of URLs (eg: http://example.org/exampledocument.odt)

• The URL must resolve to a valid internet address that provides direct access to the document in question.

• Attention should be paid by the publisher to any links that become obsolete.

• If the documents are in different languages, which are available at different URLs, then repeat the document-link element

• If the same document has multiple languages within it, then repeat the language element.

• For every document presented a title and at least one category is required

• The title element can be repeated for different languages, regardless of the language of the actual document.

• The free-text instances of title should avoid use of text in CAPITALS, where possible.

• In the IATI activity standard, documents that relate to the specific iati-activity would be linked to. Organisation/agency specific documents are published via the IATI organisation standard.

• For document category in the IATI activity standard, it is expected that the DocumentCategory code would be have the A prefix.

• When a document has multiple categories, then the category element can be repeated.

• Using the @format attribute helps inform what to expect from the document.

• Use of the @format must be accompanied by a code on the FileFormat codelist.

• The document-date/@iso-date would normally be the production or published date of the relevant document to identify the specific document version.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• The schema data type used for some data fields where a URL is expected is now set as xsd:anyURI.

• The activity-website element has been removed. These can now be expressed as a document-link with the relevant FileFormat and DocumentType codes.

• Any freetext title must be included in the child narrative element, which can be repeated for different languages.

CRS & FSS

Please note: This part of the activity standard is only relevant to organisations that actively report to CRS++ and/or the OECD DAC Forward Spending Survey. OECD Reporting Directives should be followed for guidance.

Definition

Within the IATI activity standard it is possible to describe items specific to CRS++ and/or the OECD DAC Forward Spending Survey:

• crs-add - additional items specific to CRS++ reporting.

• fss - allows entry of data required for the OECD DAC Forward Spending Survey at an activity level.

Conditions

Definition

Within the IATI activity standard conditions that relate to an iati-activity can be described:

• conditions - a container element to declare whether condition are attached.

• condition - the specific statement around a condition.

Considerations

When using the IATI activity standard to declare conditions, the following should be considered:

• An iati-activity does not require a conditions statement, if none are relevant.

• However, it is also valid to declare that no conditions are attached to a specific iati-activity via the @attached attribute.

• For every condition a relevant ConditionType code is expected.

• When multiple condition exist, these can be presented separately within the same conditions element.

• The same condition can be presented in different languages, by using the narrative child element`` and the relevant xml:lang.

• The free-text to describe the condition should avoid jargon

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• Any freetext condition text must be included in the child narrative element, which can be repeated for different languages.

Contact Info

Definition

The IATI activity standard enables contact-info to be included for any iati-activity

The following fields can be included:

• organisation

• person-name

• job-title

• telephone

• email

• mailing-address

• website

Considerations

When using the IATI activity standard to declare contact info, the following should be considered:

• Any contact-info should include at least one of the available fields.

• More than one contact-info can be included within an iati-activity.

• Use of the ContactType code is recommended, especially when declaring multiple contact-info.

• Careful attention should be paid to personal data being published. Always include organisational contact-info.

• Telephone numbers should include the international dialing code. Avoid presentation of internal telephone numbers.

• The free-text instances of organisation, person-name, job-title and mailing-address should avoid use of text in CAPITALS, where possible.

2.01+ Considerations

In versions 2.01 and above, the following must also be considered:

• Any freetext text for organisation, person-name, job-title and mailing-address must be included in a child narrative element, which can be repeated for different languages.

Humanitarian Reporting

Please also see the Humanitarian Reporting Guidelines which are currently out for community review on the IATI Community Discuss Forum

Definition

Within the IATI activity standard there are a number of elements and vocabularies that enable humanitarian specific information to be published.

• humanitarian-scope defines the emergency or event that a specific activity is in response to.

The humanitarian-scope element uses the following vocabularies:

• HumanitarianScopeType codelist is used to describe types of humanitarian events.

• HumanitarianScopeVocabulary is used to define the public list(s) on which an emergency is referenced.

Humanitarian related information is also on:

• SectorVocabulary – code "10": The Humanitarian Global Clusters (Inter-Agency Standing Committee) defines the global clusters to which a a specific activity relates.

The following also enables any activity or transaction that is humanitarian related to be identified:

• The iati-activity/@humanitarian – indicates that the relevant iati-activity is humanitarian-related.

• transaction/@humanitarian – indicates that a specific transaction is humanitarian-related.

Timely Reporting

In the event of any rapid onset or other emergency it is recommended that publishers refresh and re-publish humanitarian activities on a daily or at least weekly basis in order that the most up to date information is continually available to data users. Such data users include, but are not limited to, UN OCHA FTS who are able to automatically import IATI files that contain humanitarian elements into the OCHA FTS systems. This therefore may require a change to a publishers own verification and / or publishing processes in order to enable this to happen as data may not be subject to ‘normal’ verification processes in order to allow this to happen.

Considerations

When using the IATI activity standard to declare humanitarian related activities the following should be considered:

• It is the data owner who decides if an activity should include humanitarian elements.

• It is recommended that at least the humanitarian-scope element and iati-activity/@humanitarian attribute should be used for each humanitarian related activity.

• If the emergency is included on more than one on of the lists defined on HumanitarianScopeVocabulary then all references should be declared via multiple humanitarian-scope elements.

• The title of an emergency can be repeated in different languages via the use of the <narrative> field of the humanitarian-scope element.

• If an emergency is not defined on any of the lists included on HumanitarianScopeVocabulary then a publisher can declare their own values using code ‘99’. It is recommended that the title of an emergency is constructed using the format ‘location of event + type of event + month of event + year of event’ eg ‘Nepal Earthquake April 2015’.

• When an activity relates to multiple clusters the sector element should be repeated and a @percentage attribute must be used. The total of all specified percentages must add up to 100.

• When an activity relates to multiple humanitarian policies the policy-marker element should be repeated.

• When defining a humanitarian policy-marker element, the policy-marker/@significance attribute is not required.

Self-defined Vocabularies

Definition

For several elements in the IATI activity standard and the IATI organisation standard, the vocabulary for a given code can be set via the @vocabulary attribute:

A good example of this is the sector element, which will typically be given a 5-digit code such as “11120”. However, this code only makes sense to data users if they know which sector codelist it is from.

To achieve this, the sector/@vocabulary should be set to the appropriate entry on the SectorVocabulary codelist. For “11120”, this would be vocabulary "1" - the OECD DAC CRS Purpose Codes (5 digit), and would hence denote the code for Education facilities and training.

It’s important to note that if there are multiple sectors given from the same vocabulary, their @percentage attributes should add up to 100.

Here is an example:

<iati-activity>
    <!-- Other elements -->
    <sector vocabulary="1" code="11120" percentage="50" />
    <sector vocabulary="1" code="11121" percentage="50" />
    <!-- Other elements -->
</iati-activity>

For any given element that has a @vocabulary attribute, the guidance on this site will link to the relevant codelist, which can be seen in the guidance for the sector element.

For each of these vocabularies, there is almost always the option for a publisher to provide their own. For instance, if a publisher wants to declare that an activity is “11120” for the OECD DAC 5-digit vocabulary, but also wants to declare it as “general_education” on their own codelist, they would simply have to set the vocabulary to “Reporting Organisation” (which is usually but not always "99"), and then use the @vocabulary-uri attribute to link through to their own (machine-readable) codelist.

Here is an example:

<iati-activity>
    <!-- Other elements -->
    <sector vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="general_education" percentage="100" />
    <!-- Other elements -->
</iati-activity>

Considerations

When using the IATI activity standard to declare budgets, the following should be considered:

• It is very important that @percentages add up to 100 per vocabulary.

• When a publisher uses code "99", or whichever other code denotes that they are using a Reporting Organisation provided codelist, they should provide the corresponding @vocabulary-uri (or equivalent) attribute.

Pre 2.02 Considerations

Not all of the elements mentioned above exist in some previous versions of the standard, but most of them do in version 2.01, and this practice should be standard in all 2.xx versions and above.

Example Usage XML

Definition

This page presents example usage XML for the IATI activity standard

Considerations

These is example usage XML and not intended to reflect any real activities, organisations or entities.

Extracts from these example files are used throughout this documentation.

Comments markup is optional and intended to supplement the documentation:

  <!--iati-identifier ends-->

  <!--reporting-org starts-->

Download Example Usage File

The example usage XML file can be downloaded.

Example Usage File (in full)

<iati-activities generated-datetime="2014-09-10T07:15:37Z" version="2.03" linked-data-default="http://data.example.org/">

 <!--iati-activity starts-->
 <iati-activity xml:lang="en" default-currency="USD" last-updated-datetime="2014-09-10T07:15:37Z" humanitarian="1" linked-data-uri="http://data.example.org/123456789" hierarchy="1" budget-not-provided="1">

  <!--iati-identifier starts-->
  <iati-identifier>AA-AAA-123456789-ABC123</iati-identifier>
  <!--iati-identifier ends-->

  <!--reporting-org starts-->
  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>
  <!--reporting-org ends-->

  <!--title starts-->
  <title>
   <narrative>Activity title</narrative>
   <narrative xml:lang="fr">Titre de l'activité</narrative>
   <narrative xml:lang="es">Título de la actividad</narrative>
  </title>
  <!--title ends-->

  <!--description starts-->
  <description type="1">
   <narrative>General activity description text.  Long description of the activity with no particular structure.</narrative>
   <narrative xml:lang="fr">Activité générale du texte de description. Longue description de l'activité sans structure particulière.</narrative>
  </description>
  <description type="2">
   <narrative>Objectives for the activity, for example from a logical framework.</narrative>
   <narrative xml:lang="fr">Objectifs de l'activité, par exemple à partir d'un cadre logique.</narrative>
  </description>
  <description type="3">
   <narrative>Statement of groups targeted to benefit from the activity.</narrative>
   <narrative xml:lang="fr">Déclaration de groupes ciblés pour bénéficier de l'activité.</narrative>
  </description>
  <!--description ends-->

  <!--participating-org starts-->
  <participating-org ref="BB-BBB-123456789" role="1" type="40" activity-id="BB-BBB-123456789-1234">
   <narrative>Name of Agency B</narrative>
  </participating-org>
  <participating-org ref="CC-CCC-123456789" role="2" type="10" activity-id="CC-CCC-123456789-1234">
   <narrative>Name of Agency C</narrative>
  </participating-org>
  <participating-org ref="AA-AAA-123456789" role="3" type="21" activity-id="AA-AAA-123456789-1234" crs-channel-code="000000">
   <narrative>Name of Agency A</narrative>
   <narrative xml:lang="fr">Nom de l'agence A</narrative>
  </participating-org>
  <!--participating-org ends-->

  <!--other-identifier starts-->
  <other-identifier ref="ABC123-XYZ" type="A1">
   <owner-org ref="AA-AAA-123456789">
    <narrative>Organisation name</narrative>
   </owner-org>
  </other-identifier>
  <!--other-identifier ends-->

  <!--activity-status starts-->
  <activity-status code="2" />
  <!--activity-status ends-->

  <!--activity-date starts-->
  <activity-date iso-date="2012-04-15" type="1">
   <narrative>Planned start date of the activity</narrative>
   <narrative xml:lang="fr">Date prévue de début de l'activité</narrative>
  </activity-date>
  <activity-date iso-date="2012-04-28" type="2" />
  <activity-date iso-date="2015-12-31" type="3" />
  <!--activity-date ends-->

  <!--contact-info starts-->
  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>
  <!--contact-info ends-->

  <!--activity-scope starts-->
  <activity-scope code="3" />
  <!--activity-scope ends-->

  <!--recipient-country starts-->
  <recipient-country code="AF" percentage="25" />
  <recipient-country code="AG" percentage="25" />
  <!--recipient-country ends-->

  <!--recipient-region starts-->
  <recipient-region code="489" vocabulary="1" percentage="25" />
  <recipient-region code="A1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" percentage="25" />
  <!--recipient-region ends-->

  <!--location-single starts-->
  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>
  <!--location-single ends-->

  <!--location-additional starts-->
  <location ref="KH-PNH">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1821306" />
   <name>
  <narrative>Location #2 name</narrative>
   </name>
   <description>
  <narrative>Location #2 description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at location #2</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>11.5500 104.9167</pos>
   </point>
   <exactness code="1" />
   <location-class code="2" />
   <feature-designation code="ADMF" />
  </location>
  <!--location-additional ends-->

  <!--sector starts-->
  <sector vocabulary="2" code="111" percentage="50" />
  <sector vocabulary="2" code="112" percentage="50" />
  <sector vocabulary="98" vocabulary-uri="http://example.com/vocab.html" code="A1" percentage="100" />
  <!--sector ends-->

  <!--tag starts-->
  <tag vocabulary="1" code="1">
    <narrative>A description of the tag</narrative>
  </tag>
  <tag vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="T1">
    <narrative>A description of the tag</narrative>
  </tag>
  <!--tag ends-->

  <!--country-budget-items starts-->
  <country-budget-items vocabulary="4">
   <budget-item code="1844" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
   <budget-item code="1900" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
  </country-budget-items>
  <!--country-budget-items ends-->

  <!--humanitarian-scope starts-->
  <humanitarian-scope type="1" vocabulary="1-2" code="EQ-2015-000048-NPL">
 	  <narrative>Nepal Earthquake April 2015</narrative>
    <narrative xml:lang="fr"> Népal Earthquake Avril 2015</narrative>
  </humanitarian-scope>
  <humanitarian-scope type="1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1">
   <narrative xml:lang="en">Nepal Earthquake April 2015</narrative>
  </humanitarian-scope>
  <!--humanitarian-scope ends-->

  <!--policy-marker starts-->
  <policy-marker vocabulary="1" code="2" significance="3" />
  <policy-marker vocabulary="1" code="9" significance="4" />
  <policy-marker vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" significance="3" />
  <!--policy-marker ends-->

  <!--collaboration-type starts-->
  <collaboration-type code="1" />
  <!--collaboration-type ends-->

  <!--default-flow-type starts-->
  <default-flow-type code="10" />
  <!--default-flow-type ends-->

  <!--default-finance-type starts-->
  <default-finance-type code="110" />
  <!--default-finance-type ends-->

  <!--default-aid-type starts-->
  <default-aid-type code="A01" vocabulary="1" />
  <default-aid-type code="1" vocabulary="2" />
  <!--default-aid-type ends-->

  <!--default-tied-status starts-->
  <default-tied-status code="3" />
  <!--default-tied-status ends-->

  <!--budget starts-->
  <budget type="1" status="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
  </budget>
  <!--budget ends-->

  <!--planned-disbursement starts-->
  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>
  <!--planned-disbursement ends-->

  <!--planned-disbursement-single-date starts-->
  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
  </planned-disbursement>
  <!--planned-disbursement ends-->

  <!--capital-spend starts-->
  <capital-spend percentage="88.8" />
  <!--capital-spend ends-->

  <!--transaction starts-->
  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>
  <!--transaction ends-->

  <!--document-link starts-->
  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>
  <!--document-link ends-->

  <!--related-activity starts-->
  <related-activity ref="AA-AAA-123456789-6789" type="1" />
  <!--related-activity ends-->

  <!--legacy-data starts-->
  <legacy-data name="Project Status" value="7" iati-equivalent="activity-status" />
  <legacy-data name="cost" value="1000" iati-equivalent="transaction" />
  <!--legacy-data ends-->

  <!--conditions starts-->
  <conditions attached="1">
   <condition type="1">
    <narrative>Conditions text</narrative>
    <narrative xml:lang="fr">Conditions texte</narrative>
   </condition>
  </conditions>
  <!--conditions ends-->

  <!--result starts-->
  <result type="1" aggregation-status="1">
   <title>
    <narrative>Result title</narrative>
   </title>
   <description>
    <narrative>Result description text</narrative>
   </description>
   <!--result-document-link example starts-->
   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>
<!--result-document-link example ends-->
<!--result-reference starts-->
   <reference vocabulary="99" code="B1" vocabulary-uri="http://example.com/indicators.html" />
<!--result-reference ends-->
<!--result-indicator starts-->
   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>
   <!--result-indicator ends-->
  </result>
  <!--result ends-->

  <!--crs-add starts-->
  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>
  <!--crs-add ends-->

  <!--fss starts-->
  <fss extraction-date="2014-05-06" priority="1" phaseout-year="2016">
   <forecast year="2014" value-date="2013-07-03" currency="GBP">10000</forecast>
  </fss>
  <!--fss ends-->

 </iati-activity>
  <!--iati-activity ends-->

</iati-activities>

Further guidance

• IATI activity standard - reference pages

Elements

This section contains detailed documentation for each XML element in the IATI Activity Standard.

For each element, the relevant attributes are listed, with subsequent child elements listed.

For each element, any rules for usage are declared.

Additionally, XML examples are provided for each element, with the relevant markup highlighted.

Further information

All code examples are derived from a single source: Example Usage XML.

For an single page table of all elements see Activity Standard Summary Table.

For more general material see also the Overview section.

Contents

iati-activities

iati-activities

This is the reference page for the XML element iati-activities.

Definition

Top-level list of one or more IATI activity records.

Attributes

@version

A number indicating the IATI specification version in use. This is mandatory and must be a valid version.

This attribute is required.

This value must be of type xsd:string.

This value must be on the Version codelist.

@generated-datetime

A date/time stamp for when this file was generated. This is not necessarily the last-updated date for the individual activity records in it. Use of this attribute is highly recommended, to allow recipients to know when a file has been updated.

This value must be of type xsd:dateTime.

@linked-data-default

If a publisher chooses to publish linked data about their IATI activities then allowing them to declare where this data is published would support discovery of it, and any additional information they may choose to publish as Linked Data alongside it.

This attribute is a URI path upon which an activity identifier can be appended to get a differentiable URI for any activity contained within a file.

Where a publisher declares using one of these properties that authoritative linked data is accessible for an activity then consuming applications that are generating Linked Data from an IATI XML file should assert an owl:sameAs relationship to the relevant URI.

This value must be of type xsd:anyURI.

Example Usage

Example usage of iati-activities.

This element is a parent for other all other elements of the IATI Activity Standard.

This example provides a dateTime of 2014-09-10T07:15:37Z for the @generated-datetime attribute.

A dateTime in UTC time is indicated by adding a Z behind the time

This example date time format conforms to the xsd:dateTime standard.

The @version attribute declares a valid code (2.x) from the Version codelist.

The optional @linked-data-default attribute is also included.

<iati-activities generated-datetime="2014-09-10T07:15:37Z" version="2.03" linked-data-default="http://data.example.org/">

The iati-activities element acts as a container for other sub-elements. It is closed as follows:

</iati-activities>

Changelog

1.02

Introduced the @linked-data-default attribute on iati-activities element

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

iati-activity

iati-activities/iati-activity

This is the reference page for the XML element iati-activity.

Definition

Top-level element for a single IATI activity report.

Rules

This element must occur at least once (within each parent element).

Attributes

@last-updated-datetime

The last date/time that the data for this specific activity was updated. This date must change whenever the value of any field changes.

This value must be of type xsd:dateTime.

@last-updated-datetime must not be more recent than the current date

@xml:lang

A code specifying the default language of text in this activity. It is recommended that wherever possible only codes from ISO 639-1 are used. If this is not declared then the xml:lang attribute MUST be specified for each narrative element.

This value should be on the Language codelist.

@xml:lang must exist, otherwise all lang must exist.

@default-currency

Default ISO 4217 alphabetic currency code for all financial values in this activity report. If this is not declared then the currency attribute MUST be specified for all monetary values.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@default-currency must exist, otherwise all currency must exist.

@humanitarian

A process flag to indicate that this activity relates entirely or partially to humanitarian aid.

This value must be of type xsd:boolean.

@hierarchy

The hierarchical level within the reporting organisation’s subdivision of its units of aid. (eg activity = 1; sub-activity = 2; sub-sub-activity = 3). If hierarchy is not reported then 1 is assumed. If multiple levels are reported then, to avoid double counting, financial transactions should only be reported at the lowest hierarchical level.

This value must be of type xsd:int.

@linked-data-uri

A Linked Data URI for a given activity (overrides iati-activities/@linked-data-default if set)

This value must be of type xsd:anyURI.

@budget-not-provided

A code indicating the reason why this activity does not contain any iati-activity/budget elements. The attribute MUST only be used when no budget elements are present.

This value must be of type xsd:string.

This value must be on the BudgetNotProvided codelist.

Example Usage

Example of iati-activity.

This element is a parent for other child elements.

This example provides a dateTime of 2014-09-10T07:15:37Z for the @last-updated-datetime attribute.

A dateTime in UTC time is indicated by adding a Z behind the time

This example date time format conforms to the xsd:dateTime standard.

The @xml:lang attribute declares a valid code (en) from the Language codelist.

The @default-currency attribute declares a valid code (USD) from the Currency codelist.

The optional @humanitarian attribute is set as 1

The optional @hierarchy attribute is set as 1

The optional @linked-data-uri attribute is also included.

The optional @budget-not-provided attribute is also included.

 <iati-activity xml:lang="en" default-currency="USD" last-updated-datetime="2014-09-10T07:15:37Z" humanitarian="1" linked-data-uri="http://data.example.org/123456789" hierarchy="1" budget-not-provided="1">

The iati-activity element acts as a container for other sub-elements. It is closed as follows:

 </iati-activity>

Changelog

2.03

The @budget-not-provided attribute was added.

2.02

The @humanitarian attribute was added.

2.01

The @version attribute was removed.

1.02

Introduced the @linked-data-uri attribute on iati-activity element

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

iati-identifier

iati-activities/iati-activity/iati-identifier

This is the reference page for the XML element iati-identifier.

Definition

A globally unique identifier for the activity.

This MUST be prefixed with EITHER the current IATI organisation identifier for the reporting organisation (reporting-org/@ref) OR a previous identifier reported in other-identifier, and suffixed with the organisation’s own activity identifier. The prefix and the suffix should be separated by a hyphen “-“.

Once an activity has been reported to IATI its identifier MUST NOT be changed in subsequent updates.

Rules

The text in this element must be of type xsd:string.

This element must occur once and only once (within each parent element).

iati-identifier should match the regex [^\/\&\|\?]+

Example Usage

Example iati-identifier of an iati-activity.

Example uses a concatenation of the reporting-org identifier AA-AAA-123456789 and the internal activity identifier ABC123.

  <iati-identifier>AA-AAA-123456789-ABC123</iati-identifier>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

reporting-org

iati-activities/iati-activity/reporting-org

This is the reference page for the XML element reporting-org.

Definition

The organisation issuing the report. May be a primary source (reporting on its own activity as donor, implementing agency, etc) or a secondary source (reporting on the activities of another organisation).

Specifying the @ref attribute is mandatory. May contain the organisation name as content.

All activities in an activity xml file must contain the same @ref AND this @ref must be the same as the iati-identifier recorded in the registry publisher record of the account under which this file is published.

Rules

This element must occur once and only once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}.

This attribute is required.

This value must be of type xsd:string.

reporting-org/@ref should match the regex [^\/\&\|\?]+

@type

The type of organisation issuing the report. See IATI codelist for values.

This attribute is required.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

@secondary-reporter

A flag indicating that the reporting organisation of this activity is acting as a secondary reporter. A secondary reporter is one that reproduces data on the activities of an organisation for which it is not directly responsible. This does not include a publisher officially assigned as a proxy to report on behalf of another.

This value must be of type xsd:boolean.

Example Usage

Example reporting-org for an iati-activity

An example organisation @ref of AA-AAA-123456789 is declared.

The @type attribute declares a valid code (40) from the OrganisationType codelist.

The optional @secondary-reporter boolean is included, for illustration.

  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>

Changelog

2.03

The definition of the @ref attributed was updated.

The definition of the @secondary-reporter attributed was updated.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

1.04

The @secondary-reporter was introduced in 1.04.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/reporting-org/narrative

This is the reference page for the XML element narrative.

Definition

The name of the organisation. May be repeated for different languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the reporting-org element.

  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the xml:lang attribute:

  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

title

iati-activities/iati-activity/title

This is the reference page for the XML element title.

Definition

A short, human-readable title that contains a meaningful summary of the activity. May be repeated for different languages.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example title for an iati-activity:

  <title>
   <narrative>Activity title</narrative>
   <narrative xml:lang="fr">Titre de l'activité</narrative>
   <narrative xml:lang="es">Título de la actividad</narrative>
  </title>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title parent element.

  <title>
   <narrative>Activity title</narrative>
   <narrative xml:lang="fr">Titre de l'activité</narrative>
   <narrative xml:lang="es">Título de la actividad</narrative>
  </title>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

  <title>
   <narrative>Activity title</narrative>
   <narrative xml:lang="fr">Titre de l'activité</narrative>
   <narrative xml:lang="es">Título de la actividad</narrative>
  </title>

Note: It is recommended to provide a title in the language(s) spoken in the country(ies) where the iati-activity take place, or is aimed at.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/description

This is the reference page for the XML element description.

Definition

A longer, human-readable description containing a meaningful description of the activity. May be repeated for different languages.

Rules

This element must occur at least once (within each parent element).

Attributes

@type

The type of description being provided. This is not required if only one general description of the activity is reported.

This value must be of type xsd:string.

This value must be on the DescriptionType codelist.

Example Usage

Example description of an iati-activity.

The @type attribute declares a valid code (en) from the DescriptionType codelist.

<description type="1">
   <narrative>General activity description text.  Long description of the activity with no particular structure.</narrative>
</description>

The description element can be repeated in any iati-activity.

In this example, three different description are declared.

Note - it is optional to include all DescriptionType.

  <description type="1">
   <narrative>General activity description text.  Long description of the activity with no particular structure.</narrative>
   <narrative xml:lang="fr">Activité générale du texte de description. Longue description de l'activité sans structure particulière.</narrative>
  </description>
  <description type="2">
   <narrative>Objectives for the activity, for example from a logical framework.</narrative>
   <narrative xml:lang="fr">Objectifs de l'activité, par exemple à partir d'un cadre logique.</narrative>
  </description>
  <description type="3">
   <narrative>Statement of groups targeted to benefit from the activity.</narrative>
   <narrative xml:lang="fr">Déclaration de groupes ciblés pour bénéficier de l'activité.</narrative>
  </description>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description parent element.

  <description type="1">
   <narrative>General activity description text.  Long description of the activity with no particular structure.</narrative>
   <narrative xml:lang="fr">Activité générale du texte de description. Longue description de l'activité sans structure particulière.</narrative>
  </description>
  <description type="2">
   <narrative>Objectives for the activity, for example from a logical framework.</narrative>
   <narrative xml:lang="fr">Objectifs de l'activité, par exemple à partir d'un cadre logique.</narrative>
  </description>
  <description type="3">
   <narrative>Statement of groups targeted to benefit from the activity.</narrative>
   <narrative xml:lang="fr">Déclaration de groupes ciblés pour bénéficier de l'activité.</narrative>
  </description>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

  <description type="1">
   <narrative>General activity description text.  Long description of the activity with no particular structure.</narrative>
   <narrative xml:lang="fr">Activité générale du texte de description. Longue description de l'activité sans structure particulière.</narrative>
  </description>
  <description type="2">
   <narrative>Objectives for the activity, for example from a logical framework.</narrative>
   <narrative xml:lang="fr">Objectifs de l'activité, par exemple à partir d'un cadre logique.</narrative>
  </description>
  <description type="3">
   <narrative>Statement of groups targeted to benefit from the activity.</narrative>
   <narrative xml:lang="fr">Déclaration de groupes ciblés pour bénéficier de l'activité.</narrative>
  </description>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

participating-org

iati-activities/iati-activity/participating-org

This is the reference page for the XML element participating-org.

Definition

An organisation involved with the activity. May be a donor, fund, agency, etc. Specifying the @ref identifier is strongly recommended. May contain the organisation name as narrative.

If the reporting organisation plays a role in the activity it should be repeated here. One organisation may play more than one role (eg, funding and implementing): in such a case each role should be reported and the name of the organisation repeated.

Rules

This element must occur at least once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.

This value must be of type xsd:string.

participating-org/@ref should match the regex [^\/\&\|\?]+

Either @ref or narrative must be present.

@type

The type of organisation issuing the report. See IATI codelist for values.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

@role

An IATI code describing the organisation’s role in the activity (donor, agency, etc.).

This attribute is required.

This value must be of type xsd:string.

This value must be on the OrganisationRole codelist.

@activity-id

A valid activity identifier published by the participating organisation which points to the activity that it has published to IATI that describes its role in this activity.

This value must be of type xsd:string.

@crs-channel-code

Under CRS++ Reporting Directives this code identifies the implementing agency. Codes ending in ‘00’ are generic and are similar to the OrganisationType code.

This value must be of type xsd:string.

This value must be on the CRSChannelCode codelist.

Example Usage

Example participating-org in an iati-activity.

An example organisation @ref of BB-BBB-123456789 is declared.

The @role attribute declares a valid code (2) from the OrganisationRole codelist.

The @type attribute declares a valid code (40) from the OrganisationType codelist.

The @activity-id attribute declares an IATI activity identifier.

The @crs-channel-code attribute declares the CRS Channel Code for the participating organisation.

<participating-org ref="BB-BBB-123456789" role="2" type="40" activity-id="BB-BBB-123456789-1234">
        <narrative>Name of Agency B</narrative>
</participating-org>

As demonstrated in the the above example, it is strongly recommended that the name of the organisation is provided (using the narrative child element) in addition to a valid organisation identifier. Where an organisation identifier is not present the name (using the narrative child element) is mandatory.

The participating-org element can be repeated in any iati-activity.

In this example, three participating-org are declared.

  <participating-org ref="BB-BBB-123456789" role="1" type="40" activity-id="BB-BBB-123456789-1234">
   <narrative>Name of Agency B</narrative>
  </participating-org>
  <participating-org ref="CC-CCC-123456789" role="2" type="10" activity-id="CC-CCC-123456789-1234">
   <narrative>Name of Agency C</narrative>
  </participating-org>
  <participating-org ref="AA-AAA-123456789" role="3" type="21" activity-id="AA-AAA-123456789-1234" crs-channel-code="000000">
   <narrative>Name of Agency A</narrative>
   <narrative xml:lang="fr">Nom de l'agence A</narrative>
  </participating-org>

Changelog

2.03

The definition of the @ref attribute was updated.

The @crs-channel-code attribute was added.

2.02

The activity-id attribute was added.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

The OrganisationRole codelist was changed to numeric codes

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/participating-org/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Either narrative or @ref must be present.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the participant-org element.

  <participating-org ref="BB-BBB-123456789" role="1" type="40" activity-id="BB-BBB-123456789-1234">
   <narrative>Name of Agency B</narrative>
  </participating-org>
  <participating-org ref="CC-CCC-123456789" role="2" type="10" activity-id="CC-CCC-123456789-1234">
   <narrative>Name of Agency C</narrative>
  </participating-org>
  <participating-org ref="AA-AAA-123456789" role="3" type="21" activity-id="AA-AAA-123456789-1234" crs-channel-code="000000">
   <narrative>Name of Agency A</narrative>
   <narrative xml:lang="fr">Nom de l'agence A</narrative>
  </participating-org>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute.

One example illustrated below:

  <participating-org ref="BB-BBB-123456789" role="1" type="40" activity-id="BB-BBB-123456789-1234">
   <narrative>Name of Agency B</narrative>
  </participating-org>
  <participating-org ref="CC-CCC-123456789" role="2" type="10" activity-id="CC-CCC-123456789-1234">
   <narrative>Name of Agency C</narrative>
  </participating-org>
  <participating-org ref="AA-AAA-123456789" role="3" type="21" activity-id="AA-AAA-123456789-1234" crs-channel-code="000000">
   <narrative>Name of Agency A</narrative>
   <narrative xml:lang="fr">Nom de l'agence A</narrative>
  </participating-org>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

other-identifier

iati-activities/iati-activity/other-identifier

This is the reference page for the XML element other-identifier.

Definition

An other identifier for the activity. This may be a publishers own identifier that it wishes to record with the activity. This element is also used to trace changes to activity identifiers, for example when and organisation has changed it’s organisation identifier.

Rules

This element may occur any number of times.

Attributes

@ref

The identifier you wish to report. This can be used to report a number of different types of identifiers. See the OtherIdentifierType codelist for details and options.

This attribute is required.

This value must be of type xsd:string.

@type

The type of identifier being reported, taken from the OtherIdentifierType codelist.

This attribute is required.

This value must be of type xsd:string.

This value must be on the OtherIdentifierType codelist.

Example Usage

Example other-identifier of an iati-activity.

An example @ref of ABC123-XYZ is declared.

The @type attribute declares a valid code (A1) from the OtherIdentifierType codelist.

  <other-identifier ref="ABC123-XYZ" type="A1">
   <owner-org ref="AA-AAA-123456789">
    <narrative>Organisation name</narrative>
   </owner-org>
  </other-identifier>

2.01

Freetext support of the other-identifier was removed. A new other-identifier/@ref was added as a replacement.

A new attribute other-identifier/@type was added, to be used with new code list OtherIdentifierType.

The other-identifier/@owner-ref and other-identifier/@owner-name attributes were removed.

The owner-org child element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

owner-org

iati-activities/iati-activity/other-identifier/owner-org

This is the reference page for the XML element owner-org.

Definition

Where applicable, the organisation that owns the other identifier being reported. When used, then either other-identifier/owner-org/@ref or other-identifier/owner-org/narrative/text() MUST be present.

Rules

This element must occur no more than once (within each parent element).

Attributes

@ref

An organisation identifier. This is NOT MANDATORY but when used MUST contain a valid organisation identifier.

This value must be of type xsd:string.

Either @ref or narrative must be present.

Example Usage

Example owner-org of an other-identifier of an iati-activity.

An example organisation @ref of AA-AAA-123456789 is declared.

  <other-identifier ref="ABC123-XYZ" type="A1">
   <owner-org ref="AA-AAA-123456789">
    <narrative>Organisation name</narrative>
   </owner-org>
  </other-identifier>

Changelog

2.01

The owner-org element was added in version 2.01

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/other-identifier/owner-org/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Either narrative or @ref must be present.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the owner-org of an other-identifier.

  <other-identifier ref="ABC123-XYZ" type="A1">
   <owner-org ref="AA-AAA-123456789">
    <narrative>Organisation name</narrative>
   </owner-org>
  </other-identifier>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The owner-org element was added in version 2.01

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

activity-status

iati-activities/iati-activity/activity-status

This is the reference page for the XML element activity-status.

Definition

The current status of the activity. See codelist for values.

Rules

This element must occur once and only once (within each parent element).

Attributes

@code

An IATI code defining the current status of the activity.

This attribute is required.

This value must be of type xsd:string.

This value must be on the ActivityStatus codelist.

Example Usage

Example activity-status of an iati-activity

The @code attribute declares a valid code (2) from the ActivityStatus codelist.

  <activity-status code="2" />

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

activity-date

iati-activities/iati-activity/activity-date

This is the reference page for the XML element activity-date.

Definition

The planned and actual start and completion dates of the activity. Start dates may reflect either the commencement of funding, planning or physical activity. End dates should, wherever possible, reflect the ending of physical activity.

The narrative content may contain text (e.g. 2011Q1) for accurately recording less specific dates such as month, quarter, or year.

Rules

This element must occur at least once (within each parent element).

activity-date[@type='1' or @type='2'] must be present.

Attributes

@type

An IATI code defining the type of activity date being reported.

This attribute is required.

This value must be of type xsd:string.

This value must be on the ActivityDateType codelist.

@iso-date

This attribute is required.

This value must be of type xsd:date.

activity-date[@type='1']/@iso-date must be before or the same as activity-date[@type='3']/@iso-date

activity-date[@type='2']/@iso-date must be before or the same as activity-date[@type='4']/@iso-date

activity-date[@type='2']/@iso-date must not be in the future.

activity-date[@type='4']/@iso-date must not be in the future.

Example Usage

Example activity-date for an``iati-activity``.

The @type attribute declares a valid code (1) from the ActivityDateType codelist.

An example date is declared in the @iso-date attribute.

Example date format conforms to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

<activity-date iso-date="2012-04-28" type="1" />

The activity-date element can be repeated in any iati-activity.

In this example four activity-date are declared.

  <activity-date iso-date="2012-04-15" type="1">
   <narrative>Planned start date of the activity</narrative>
   <narrative xml:lang="fr">Date prévue de début de l'activité</narrative>
  </activity-date>
  <activity-date iso-date="2012-04-28" type="2" />
  <activity-date iso-date="2015-12-31" type="3" />

Note: In some cases, not all ActivityDateType codes can be declared, depending on the activity-status of the iati-activity

Note: All instances of the ActivityDateType code 2 & 4 (actual dates) are not expected to be in the future.

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

The ActivityDateType codelist was changed to numeric codes

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/activity-date/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the activity-date element.

Note: In this example, free text narrative has been included with the just one activity-date element. This is entirely optional, and best applied when such text can add additional clarification to the activity-date.

  <activity-date iso-date="2012-04-15" type="1">
   <narrative>Planned start date of the activity</narrative>
   <narrative xml:lang="fr">Date prévue de début de l'activité</narrative>
  </activity-date>
  <activity-date iso-date="2012-04-28" type="2" />
  <activity-date iso-date="2015-12-31" type="3" />

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute.

One example illustrated below:

  <activity-date iso-date="2012-04-15" type="1">
   <narrative>Planned start date of the activity</narrative>
   <narrative xml:lang="fr">Date prévue de début de l'activité</narrative>
  </activity-date>
  <activity-date iso-date="2012-04-28" type="2" />
  <activity-date iso-date="2015-12-31" type="3" />

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

contact-info

iati-activities/iati-activity/contact-info

This is the reference page for the XML element contact-info.

Definition

Contact information for the activity. Specify whatever is available. You may repeat this element for each contact person.

Rules

This element may occur any number of times.

Attributes

@type

The type of contact. See IATI codelist for values.

This value must be of type xsd:string.

This value must be on the ContactType codelist.

Example Usage

Example contact-info for an iati-activity.

This element is a parent for other child elements.

The @type attribute declares a valid code (1) from the ContactType codelist.

<contact-info type="1">
...
</contact-info>

Full example with all child elements:

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Changelog

2.01

The optional contact-info/department element was added.

1.03

Added the optional contact-info/website element.

Added the optional contact-info/@type attribute.

Changed the following subelements of contact-info to allow multiple-language versions explicitly (no change to parsing; purely semantic):

• organisation

• person-name

• job-title

• mailing-address

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

organisation

iati-activities/iati-activity/contact-info/organisation

This is the reference page for the XML element organisation.

Definition

The name of the organisation to contact for more information about the activity.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example organisation within contact-info of an iati-activity

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/contact-info/organisation/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the organisation element of contact-info.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

department

iati-activities/iati-activity/contact-info/department

This is the reference page for the XML element department.

Definition

The department within the organisation to contact for more information about the activity.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example department within contact-info of an iati-activity.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Changelog

2.01

The contact-info/department child element was added

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/contact-info/department/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the department element of contact-info.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

person-name

iati-activities/iati-activity/contact-info/person-name

This is the reference page for the XML element person-name.

Definition

The name of the contact person for the activity.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example person-name within contact-info of an iati-activity

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/contact-info/person-name/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the person-name element of contact-info.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

job-title

iati-activities/iati-activity/contact-info/job-title

This is the reference page for the XML element job-title.

Definition

The job title of the contact person at the organisation.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example job-title within contact-info of an iati-activity

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

1.03

Added the optional contact-info/job-title element

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/contact-info/job-title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the job-title element of contact-info.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

telephone

iati-activities/iati-activity/contact-info/telephone

This is the reference page for the XML element telephone.

Definition

The contact telephone number. May be repeated for multiple numbers.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Example Usage

Example telephone within contact-info of an iati-activity

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

email

iati-activities/iati-activity/contact-info/email

This is the reference page for the XML element email.

Definition

The contact email address. May be repeated for multiple addresses.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Example Usage

Example email within contact-info of an iati-activity.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

website

iati-activities/iati-activity/contact-info/website

This is the reference page for the XML element website.

Definition

The contact web address. May be repeated for multiple sites.

Rules

The text in this element must be of type xsd:anyURI.

This element may occur any number of times.

Example Usage

Example website within contact-info of an iati-activity.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Changelog

1.03

Added the optional contact-info/website element

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

mailing-address

iati-activities/iati-activity/contact-info/mailing-address

This is the reference page for the XML element mailing-address.

Definition

The contact mailing address.

Rules

This element may occur any number of times.

Example Usage

Example mailing-address within contact-info of an iati-activity

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/contact-info/mailing-address/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the mailing-address element of contact-info.

  <contact-info type="1">
   <organisation>
    <narrative>Agency A</narrative>
   </organisation>
   <department>
    <narrative>Department B</narrative>
   </department>
   <person-name>
    <narrative>A. Example</narrative>
   </person-name>
   <job-title>
    <narrative>Transparency Lead</narrative>
   </job-title>
   <telephone>0044111222333444</telephone>
   <email>transparency@example.org</email>
   <website>http://www.example.org</website>
   <mailing-address>
    <narrative>Transparency House, The Street, Town, City, Postcode</narrative>
   </mailing-address>
  </contact-info>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

activity-scope

iati-activities/iati-activity/activity-scope

This is the reference page for the XML element activity-scope.

Definition

The geographical scope of the activity: regional, national, sub-national, etc.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

The geographical scope. See IATI codelist for values.

This attribute is required.

This value must be of type xsd:string.

This value must be on the ActivityScope codelist.

Example Usage

Example of an activity-scope of an iati-activity.

The @code attribute declares a valid code (3) from the ActivityScope codelist.

  <activity-scope code="3" />

Changelog

2.01

Freetext is no longer allowed within this element.

1.03

This is a new element, introduced in version 1.03 of the standard

1.02

This element did not exist

1.01

This element did not exist

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

recipient-country

iati-activities/iati-activity/recipient-country

This is the reference page for the XML element recipient-country.

Definition

A country that will benefit from this activity. If a specific country is not known the recipient-region element should be used instead. For geographical location, use the location element.

Multiple countries and regions can be reported, in which case the percentage attribute MUST be used to specify the share of total commitments across all reported countries and regions.

The country can also be specified at transaction rather than activity level. If recipient-country OR recipient-region are reported at the transaction level, ALL transactions MUST contain a recipient-country or recipient-region element and iati-activity/recipient-country and iati-activity/recipient-region MUST NOT be used.

Rules

This element may occur any number of times.

Attributes

@code

ISO 3166-1 alpha-2 code for the country.

This attribute is required.

This value must be of type xsd:string.

This value should be on the Country codelist.

@percentage

The percentage of total commitments or total activity budget to this item. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign. Percentages for all reported countries and regions within a vocabulary MUST add up to 100.

This value must be of type xsd:decimal.

The sum of values matched at recipient-country/@percentage and recipient-region/@percentage must be 100.

The value of each of the elements described by recipient-country/@percentage must be at least 0.0 no more than 100.0 (inclusive).

Example Usage

Example recipient-country of an iati-activity.

The @code attribute declares a valid code (AF) from the Country codelist.

<recipient-country code="AF" />

The recipient-country element can be repeated in any iati-activity.

When multiple recipient-country are declared, then the @percentage values should sum to 100% for the specific iati-activity:

<recipient-country code="AF" percentage="50" />
<recipient-country code="AG" percentage="50" />

When both the recipient-region and recipient-country, then the @percentage values should sum to 100% for the specific iati-activity.

<recipient-country code="AF" percentage="50" />
<recipient-region code="489" vocabulary="1" percentage="50" />

Changelog

2.03

Definition of @percentage attribute updated.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element, but only in particular use-cases.

1.03

Where used, the @percentage attribute is now designated as a decimal value and no longer as a positive Integer

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/recipient-country/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-country element.

Note: Both the recipient-region and recipient-country elements still allow both a @code and descriptive text to be specified. This is to cover the isolated cases where the organisation publishing the data may not agree with name of a country or region given by the lookup codelists IATI uses. Example in the case of a recipient-country element:

<recipient-country code="57" vocabulary="1">
        <narrative>Kosovo (As per UNSCR 1244)<narrative>
</recipient-country>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The recipient-country element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

recipient-region

iati-activities/iati-activity/recipient-region

This is the reference page for the XML element recipient-region.

Definition

A supranational geopolitical region that will benefit from this activity. For sub-national geographical location, use the location element.

Multiple countries and regions can be reported, in which case the percentage attribute MUST be used to specify the share of total commitments across all reported countries and regions. Recipient-region must not be used merely to describe the region of a country reported in recipient-country, but ONLY if the region is a recipient IN ADDITION to the country.

Region can also be reported at transaction rather than activity level. If transaction/recipient-country AND/OR transaction/recipient-region are used THEN ALL transaction elements MUST contain a recipient-country and/or recipient-region element AND iati-activity/recipient-region and iati-activity/recipient-region MUST NOT be used AND each transaction MUST only contain one recipient-country or recipient-region.

Rules

This element may occur any number of times.

Attributes

@code

Either an OECD DAC or UN region code. Codelist is determined by vocabulary attribute.

This attribute is required.

This value must be of type xsd:string.

This value must be on the Region codelist, if the relevant vocabulary is used.

@vocabulary

An IATI code for the vocabulary from which the region code is drawn. If it is not present 1 - ‘OECD DAC’ is assumed.

This value must be of type xsd:string.

This value must be on the RegionVocabulary codelist.

@vocabulary-uri

The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

This value must be of type xsd:anyURI.

@percentage

The percentage of total commitments or total activity budget to this item. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign. Percentages for all reported countries and regions within a vocabulary MUST add up to 100.

This value must be of type xsd:decimal.

The sum of values matched at recipient-region/@percentage and recipient-country/@percentage must be 100.

The value of each of the elements described by recipient-region/@percentage must be at least 0.0 no more than 100.0 (inclusive).

Example Usage

Example recipient-region of an iati-activity.

The @code attribute declares a valid code (489) from the Region codelist.

The optional @vocabulary attribute declares a valid code (1) from the RegionVocabulary codelist.

<recipient-region code="489" vocabulary="1" />

If a publisher uses a vocabulary of 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example:

<recipient-region code="A1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" />

Please note, if using your own vocabulary (i.e. code 99), it is recommended that this is used in addition to the DAC OECD region vocabulary (code 1).

The recipient-region element can be repeated in any iati-activity.

When multiple recipient-region are declared, then the @percentage values should sum to 100% for the specific iati-activity.

<recipient-region code="489" vocabulary="1" percentage="50" />
<recipient-region code="389" vocabulary="1" percentage="50" />

When both the recipient-region and recipient-country, then the @percentage values should sum to 100% for the specific iati-activity.

<recipient-country code="AF" percentage="50" />
<recipient-region code="489" vocabulary="1" percentage="50" />

Changelog

2.03

Definition of @vocabulary-uri attribute updated. Definition of @percentage attribute updated.

2.02

The vocabulary-uri attribute was added.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element, but only in particular use-cases.

1.03

Where used, the @percentage attribute is now designated as a decimal value and no longer as a positive Integer

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/recipient-region/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-region element.

Note: Both the recipient-region and recipient-country elements still allow both a @code and descriptive text to be specified. This is to cover the isolated cases where the organisation publishing the data may not agree with name of a country or region given by the lookup codelists IATI uses. Example in the case of a recipient-region element:

<recipient-region code="589" vocabulary="1">
        <narrative>Middle East, regional (As per WHO Eastern Mediterranean Region)<narrative>
</recipient-region>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The recipient-region element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

location

iati-activities/iati-activity/location

This is the reference page for the XML element location.

Definition

The sub-national geographical identification of the target locations of an activity. These can be described by gazetteer reference, coordinates, administrative areas or a textual description. Any number of locations may be reported.

Rules

This element may occur any number of times.

Attributes

@ref

An internal reference that describes the location in the reporting organisation’s own system.

This value must be of type xsd:string.

Example Usage

Example location for an iati-activity.

This element is a parent for other child elements.

An example organisation @ref of AF-KAN is declared.

<location ref="AF-KAN">
...
</location>

Full example with all child elements:

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

The location element can be repeated in any iati-activity:

<location ref="AF-KAN">
...
</location>
<location ref="KH-PNH">
...
</location>

Changelog

2.01

The following child elements were removed: coordinates; gazetteer-entry; location-type.

The @percentage attribute was removed.

1.04

Note that major changes were made to the subelements of location in version 1.04.

For more information refer to:

• the 1.04 location changes overview guidance

• the Activities Schema Changelog (or the individual subemelement pages)

The @ref attribute was introduced to provide a cross reference that a publisher can use to link back to their own internal system.

The @percentage attribute was deemed unworkable and deprecated in 1.04

1.03

Where used, the @percentage attribute is now designated as a decimal value and no longer as a positive Integer

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

location-reach

iati-activities/iati-activity/location/location-reach

This is the reference page for the XML element location-reach.

Definition

Does this location describe where the activity takes place or where the intended beneficiaries reside?

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

An IATI code for the geographic scope of the activity.

This attribute is required.

This value must be of type xsd:string.

This value must be on the GeographicLocationReach codelist.

Example Usage

Example usage of location-reach within a location of an iati-activity.

The @code attribute declares a valid code (1) from the GeographicLocationReach codelist.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

1.04

Introduced in 1.04

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

location-id

iati-activities/iati-activity/location/location-id

This is the reference page for the XML element location-id.

Definition

A unique code describing the location according to a recognised gazetteer or administrative boundary repository. Administrative areas should only be reported here if the location being defined is the administrative area itself. For describing the administrative area/s within which a more specific location falls the location/administrative element should be used.

Rules

This element may occur any number of times.

Attributes

@code

A code from the gazetteer or administrative boundary repository specified by the vocabulary

This attribute is required.

This value must be of type xsd:string.

@vocabulary

An IATI code for a recognised gazetteer or administrative boundary repository.

This attribute is required.

This value must be of type xsd:string.

This value must be on the GeographicVocabulary codelist.

Example Usage

Example usage of location-id within a location of an iati-activity..

The @vocabulary attribute declares a valid code (G1) from the GeographicVocabulary codelist.

An example value of 1453782 from that vocabulary is declared in the @code attribute.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Note: If the GeographicVocabulary G2 (Open Street Map) is used, then the @code value should be of the form <OSM element>/<OSM identifier>

The OSM element will be a node, way or relation.

Examples:

• node/1234567

• way/1234567

• relation/1234567

<location-id vocabulary="G2" code="node/25524229" />

Changelog

2.01

Freetext is no longer allowed within this element.

1.04

New in 1.04

The location-id element was introduced in 1.04 to replace the gazetteer-entry element which was deprecated in 1.04

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

name

iati-activities/iati-activity/location/name

This is the reference page for the XML element name.

Definition

The human-readable name for the location.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of name within a location of an iati-activity.:

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/location/name/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative element can be used to declare freetext for the name child element of location.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/location/description

This is the reference page for the XML element description.

Definition

A description that qualifies the location, not the activity.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description within a location of an iati-activity.:

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

1.04

The documentation in the schema has changed from “A human-readable description of the location (not the activity).”

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/location/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative element can be used to declare freetext for the description child element of location.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the xml:lang attribute. Example not shown.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

activity-description

iati-activities/iati-activity/location/activity-description

This is the reference page for the XML element activity-description.

Definition

A description that qualifies the activity taking place at the location. This should not duplicate information provided in the main activity description, and should typically be used to distinguish between activities at multiple locations within a single iati-activity record.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of activity-description within a location of an iati-activity.:

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

1.04

The activity-description element was introduced in 1.04.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/location/activity-description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative element can be used to declare freetext for the activity-description child element of location.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

administrative

iati-activities/iati-activity/location/administrative

This is the reference page for the XML element administrative.

Definition

Coded identification of national and sub-national divisions according to recognised administrative boundary repositories. Multiple levels may be reported.

Rules

This element may occur any number of times.

Attributes

@code

The code for the administrative area being reported from the vocabulary specified.

This attribute is required.

This value must be of type xsd:string.

This value should be on the Country codelist, if the relevant vocabulary is used.

@vocabulary

An IATI code for a recognised administrative boundary repository.

This attribute is required.

This value must be of type xsd:string.

This value must be on the GeographicVocabulary codelist.

@level

A number defining a subdivision within a hierarchical system of administrative areas. The precise system for defining the particular meaning of each @level value is determined by the @vocabulary being used.

This value must be of type xsd:nonNegativeInteger.

Example Usage

Example usage of administrative within a location of an iati-activity.

The @vocabulary attribute declares a valid code (G1) from the GeographicVocabulary codelist.

An example value of 1453782 from that vocabulary is declared in the @code attribute.

An example value of 1 is declared for the @level attribute.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Note: Multiple administrative levels can be reported by repeating the administrative element:

<location ref="AF-KAN">
   <location-id vocabulary="G1" code="1453782" />
   <name>Location name</name>
   <description>Location description</description>
   <activity-description>A description that qualifies the activity taking place at the location</activity-description>
   <administrative level="0" code="1149361" vocabulary="G1" />
   <administrative level="1" code="1453782" vocabulary="G1" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-reach code="1" />
   <location-class code="2"/>
   <feature-designation code="PRNQ"/>
  </location>

Changelog

2.01

Freetext is no longer allowed within this element.

The @county, @adm1 and @adm2 attributes were removed.

1.04

In 1.04 the @country, @adm1 and @adm2 attributes were deprecated. The new attributes replace the function of the previous ones.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

point

iati-activities/iati-activity/location/point

This is the reference page for the XML element point.

Definition

The point element is based on a subset of the GML 3.3 Point element.

Rules

This element must occur no more than once (within each parent element).

Attributes

@srsName

The name of the spatial reference system used by the coordinates.

Always: http://www.opengis.net/def/crs/EPSG/0/4326

This attribute is required.

This value must be of type xsd:string.

Example Usage

Example usage of point within a location of an iati-activity.

Note: The @srsName attribute should always be populated with http://www.opengis.net/def/crs/EPSG/0/4326.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

1.04

Introduced in 1.04 to align the geocoding standard with Geographic Markup Language (GML)

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

pos

iati-activities/iati-activity/location/point/pos

This is the reference page for the XML element pos.

Definition

The latitude and longitude coordinates in the format “lat lng”

Rules

The text in this element must be of type xsd:string.

This element must occur once and only once (within each parent element).

Example Usage

Example usage of pos, a child element of the point element of location.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

1.04

Introduced in 1.04 to align the geocoding standard with Geographic Markup Language (GML)

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

exactness

iati-activities/iati-activity/location/exactness

This is the reference page for the XML element exactness.

Definition

Defines whether the location represents the most distinct point reasonably possible for this type of activity or is an approximation due to lack of more detailed information.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A code from the Geographic Exactness Codelist.

This attribute is required.

This value must be of type xsd:string.

This value must be on the GeographicExactness codelist.

Example Usage

Example usage of exactness within a location of an iati-activity.

The @code attribute declares a valid code (1) from the GeographicExactness codelist.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

2.01

Freetext is no longer allowed within this element.

1.04

New in 1.04

This is used as a replacement for the deprecated location/coordinates/@precision attribute

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

location-class

iati-activities/iati-activity/location/location-class

This is the reference page for the XML element location-class.

Definition

Whether the location refers to a structure, a populated place (e.g. city or village), an administrative division, or another topological feature (e.g. river, nature reserve).

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A code from the Location Class codelist

This attribute is required.

This value must be of type xsd:string.

This value must be on the GeographicLocationClass codelist.

Example Usage

Example usage of location-class within a location of an iati-activity.

The @code attribute declares a valid code (2) from the GeographicLocationClass codelist.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

1.04

New in 1.04

The location-class element was introduced in 1.04 and replaced the now deprecated location-type element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

feature-designation

iati-activities/iati-activity/location/feature-designation

This is the reference page for the XML element feature-designation.

Definition

A more refined coded classification of the type of feature referred to by this location.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A feature designation code form the authorised list (maintained by the US National Geospatial-Intelligence Agency)

This attribute is required.

This value must be of type xsd:string.

This value must be on the LocationType codelist.

Example Usage

Example usage of feature-designation within a location of an iati-activity.

The @code attribute declares a valid code (ADMF) from the LocationType codelist.

  <location ref="AF-KAN">
   <location-reach code="1" />
   <location-id vocabulary="G1" code="1453782" />
   <name>
  <narrative>Location name</narrative>
   </name>
   <description>
  <narrative>Location description</narrative>
   </description>
   <activity-description>
  <narrative>A description that qualifies the activity taking place at the location.</narrative>
   </activity-description>
   <administrative vocabulary="G1" level="1" code="1453782" />
   <point srsName="http://www.opengis.net/def/crs/EPSG/0/4326">
    <pos>31.616944 65.716944</pos>
   </point>
   <exactness code="1"/>
   <location-class code="2"/>
   <feature-designation code="ADMF"/>
  </location>

Changelog

1.04

New in 1.04

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

sector

iati-activities/iati-activity/sector

This is the reference page for the XML element sector.

Definition

A recognised code, from a recognised vocabulary, classifying the purpose of the activity. Sector MUST EITHER be reported here OR at transaction level for ALL transactions

Rules

This element may occur any number of times.

Either sector or transaction/sector must be present.

sector must exist, otherwise all sector must exist.

If count(sector[@vocabulary=98 or @vocabulary=99]) > 0 evaluates to true, then count(sector[@vocabulary=98 or @vocabulary=99]/narrative) >= count(sector[@vocabulary=98 or @vocabulary=99]) must evaluate to true.

Attributes

@vocabulary

An IATI code for the vocabulary (see codelist) used for sector classifications. If omitted, OECD DAC 5-digit Purpose Codes are assumed.

It is recommended that OECD DAC 5-digit Purpose Codes are used wherever possible. It is also recommended that if a publisher has its own classification system or systems then the vocabularies 99 or 98 (Reporting Organisation’s own vocabularies) should be used in addition to DAC codes.

Publishers using 98 or 99 must also include a narrative in the narrative element.

Note that if multiple sector codes are used in multiple vocabularies, then each vocabulary’s percentages should add up to 100.

Sector can also be reported at the transaction level rather than the activity level. Sector must only be reported at EITHER transaction level OR activity level.

This value must be of type xsd:string.

This value must be on the SectorVocabulary codelist.

@vocabulary-uri

The URI where this vocabulary is defined. If the vocabulary is 99 or 98 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

This value must be of type xsd:anyURI.

@code

The code for the sector.

This attribute is required.

This value must be of type xsd:string.

This value must be on the Sector codelist, if the relevant vocabulary is used.

This value must be on the SectorCategory codelist, if the relevant vocabulary is used.

This value must be on the UNSDG-Goals codelist, if the relevant vocabulary is used.

This value must be on the UNSDG-Targets codelist, if the relevant vocabulary is used.

@percentage

The percentage of total commitments or total activity budget to this item. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign. All reported sectors from the same vocabulary MUST add up to 100.

This value must be of type xsd:decimal.

The sum of values matched at sector[@vocabulary = '1' or not(@vocabulary)]/@percentage must be 100.

The value of each of the elements described by sector/@percentage must be at least 0.0 no more than 100.0 (inclusive).

Example Usage

Example sector of an iati-activity.

The @vocabulary attribute declares a valid code (2) from the SectorVocabulary codelist.

An example value 111 from this vocabulary is declared with the @code attribute.

<sector vocabulary="2" code="111" />

The sector element can be repeated in any iati-activity.

When multiple sector are declared, then the @percentage values should sum to 100% for the specific iati-activity.

  <sector vocabulary="2" code="111" percentage="50" />
  <sector vocabulary="2" code="112" percentage="50" />
  <sector vocabulary="98" vocabulary-uri="http://example.com/vocab.html" code="A1" percentage="100" />

The vocabulary is used to declare which SectorVocabulary classification list is in use. If this is omitted, then IATI assumes a SectorVocabulary of 1 (OECD DAC CRS Purpose Codes (5 digit)).

If a vocabulary is not on the SectorVocabulary codelist, then the value of 99 or 98 (Reporting Organisation) should be declared.

If a publisher uses a vocabulary of 98 or 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example:

<sector vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />

Changelog

2.03

The @vocabulary attribute definition was updated (to remove the % sign).

2.02

The vocabulary-uri attribute was added.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element, but only in particular use-cases.

1.03

Where used, the @percentage attribute is now designated as a decimal value and no longer as a positive Integer

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/sector/narrative

This is the reference page for the XML element narrative.

Definition

The description of a sector defined by the reporting organisation. (Only to be used when the reporting organisation’s own vocabulary is being used).

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the sector element.

The narrative element should be used specially when the 99 (Reporting Organisation) or 98 (Reporting Organisation 2) SectorVocabulary are declared.

<sector vocabulary="99" code="1">
        <narrative>Health Sector</narrative>
</sector>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

tag

iati-activities/iati-activity/tag

This is the reference page for the XML element tag.

Definition

Categorisations from established taxonomies that enrich the classification of the activity but that, unlike those reported in the sector element, cannot be associated with percentage splits on finances.

Rules

This element may occur any number of times.

Attributes

@code

The code for the tag as defined in the specified vocabulary.

This attribute is required.

This value must be of type xsd:string.

This value must be on the UNSDG-Goals codelist, if the relevant vocabulary is used.

This value must be on the UNSDG-Targets codelist, if the relevant vocabulary is used.

@vocabulary

An IATI code for the vocabulary or taxonomy (see non-embedded codelist) used for tag classifications.

This attribute is required.

This value must be of type xsd:string.

This value must be on the TagVocabulary codelist.

@vocabulary-uri

The URI where this vocabulary is defined.

This value must be of type xsd:anyURI.

Example Usage

Example tag in a iati-activity element.

The @vocabulary attribute declares a valid code (1) from the TagVocabulary codelist.

An example value 1 from this vocabulary is declared with the @code attribute.

<tag vocabulary="1" code="1" />

The tag element can be repeated in any iati-activity.

  <tag vocabulary="1" code="1">
    <narrative>A description of the tag</narrative>
  </tag>
  <tag vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="T1">
    <narrative>A description of the tag</narrative>
  </tag>

If a vocabulary is not on the TagVocabulary codelist, then the value of 99 (Reporting Organisation) should be declared.

If a publisher uses a vocabulary of 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example:

<tag vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="T1" />

Changelog

2.03

The tag element within a iati-activity element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/tag/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative element can be used to declare freetext for the tag parent element.

  <tag vocabulary="1" code="1">
    <narrative>A description of the tag</narrative>
  </tag>
  <tag vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="T1">
    <narrative>A description of the tag</narrative>
  </tag>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

Changelog

2.03

The optional narrative element within a tag element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

country-budget-items

iati-activities/iati-activity/country-budget-items

This is the reference page for the XML element country-budget-items.

Definition

This item encodes the alignment of activities with both the functional and administrative classifications used in the recipient country’s Chart of Accounts. This applies to both on- and off-budget activities.

Rules

This element must occur no more than once (within each parent element).

Attributes

@vocabulary

An IATI code for the common functional classification or country system (This allows for common codes, country-specific, or any other classification agreed between countries and donors).

This attribute is required.

This value must be of type xsd:string.

This value must be on the BudgetIdentifierVocabulary codelist.

Example Usage

Example country-budget-items for an iati-activity.

This element is a parent for other child elements.

The @vocabulary attribute declares a valid code (2) from the BudgetIdentifierVocabulary codelist.

<country-budget-items vocabulary="2">
    ...
</country-budget-items>

Full example with all child elements:

<country-budget-items vocabulary="2">
        <budget-item code="1.1.1">
                <description>
                        <narrative>Description text</narrative>
                </description>
        </budget-item>
</country-budget-items>

Changelog

1.03

This is a new element, introduced in version 1.03 of the standard.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

budget-item

iati-activities/iati-activity/country-budget-items/budget-item

This is the reference page for the XML element budget-item.

Definition

Identifier for a single item in the recipient-country budget. If more than one identifier is reported the percentage share must be reported and all percentages should add up to 100 percent.

Rules

This element must occur at least once (within each parent element).

Attributes

@code

A code for the budget-item from the vocabulary specified.

This attribute is required.

This value must be of type xsd:string.

This value must be on the BudgetIdentifier codelist, if the relevant vocabulary is used.

@percentage

When multiple budget-item elements are declared within a single country-budget-items element, then, for each vocabulary used, the percentage values should sum 100%.

This value must be of type xsd:decimal.

The value of each of the elements described by country-budget-items/budget-item/@percentage must be at least 0.0 no more than 100.0 (inclusive).

Example Usage

Example budget-item within country-budget-items of an iati-activity.

The @code attribute declares a code (1844) provided from the Reporting Organisation’s codelist.

Please note that the vocabulary for the budget-item code is specified in the country-budget-items element.

<country-budget-items vocabulary="4">
        <budget-item code="1844">
                <description>
                        <narrative>Description text</narrative>
                </description>
        </budget-item>
</country-budget-items>

The budget-item element can be repeated in any country-budget-items of the same vocabulary.

When multiple budget-item elements are declared within a single country-budget-items element, then, for each vocabulary used, the percentage values should sum 100%:

  <country-budget-items vocabulary="4">
   <budget-item code="1844" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
   <budget-item code="1900" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
  </country-budget-items>

Changelog

1.04

The @percentage attribute had been erroneously set to be required in the schema on it’s introduction in 1.03. This has now been set to ‘optional’ in the schema.

1.03

Added the optional country-budget-item element

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

description

iati-activities/iati-activity/country-budget-items/budget-item/description

This is the reference page for the XML element description.

Definition

A longer, human-readable description of the budget-item. May be repeated for different languages.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of budget-item element, a child element of country-budget-items.

  <country-budget-items vocabulary="4">
   <budget-item code="1844" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
   <budget-item code="1900" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
  </country-budget-items>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element, but only in particular use-cases.

The @type attribute was removed.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/country-budget-items/budget-item/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description parent element.

  <country-budget-items vocabulary="4">
   <budget-item code="1844" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
   <budget-item code="1900" percentage="50">
    <description>
     <narrative>Description text</narrative>
    </description>
   </budget-item>
  </country-budget-items>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

humanitarian-scope

iati-activities/iati-activity/humanitarian-scope

This is the reference page for the XML element humanitarian-scope.

Definition

Classification of emergencies, appeals and other humanitarian events and actions.

Rules

This element may occur any number of times.

Attributes

@type

A code for the type of event or action being classified.

This attribute is required.

This value must be of type xsd:string.

This value should be on the HumanitarianScopeType codelist.

@vocabulary

A code for a recognised vocabulary of terms classifying the event or action.

This attribute is required.

This value must be of type xsd:string.

This value should be on the HumanitarianScopeVocabulary codelist.

@vocabulary-uri

A u.r.i. for the vocabulary specified which provides access to the list of codes and descriptions.

This value must be of type xsd:anyURI.

@code

A code for the event or action from the vocabulary specified.

This attribute is required.

This value must be of type xsd:string.

Example Usage

Example humanitarian-scope of an iati-activity.

The @type attribute declares a valid code (1) from the HumanitarianScopeType codelist.

The @vocabulary attribute declares a valid code (1-2) from the HumanitarianScopeVocabulary codelist.

The @code attribute declares a valid code (EQ-2015-000048-NPL) from the specified vocabulary.

<humanitarian-scope type="1" vocabulary="1-2" code="EQ-2015-000048-NPL">
...
</humanitarian-scope>

If a publisher uses a vocabulary of 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example:

<humanitarian-scope type="1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="5">
  <narrative>Nepal Earthquake (April 2015)</narrative>
</humanitarian-scope>

The humanitarian-scope element can be repeated in any iati-activity.

  <humanitarian-scope type="1" vocabulary="1-2" code="EQ-2015-000048-NPL">
 	  <narrative>Nepal Earthquake April 2015</narrative>
    <narrative xml:lang="fr"> Népal Earthquake Avril 2015</narrative>
  </humanitarian-scope>
  <humanitarian-scope type="1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1">
   <narrative xml:lang="en">Nepal Earthquake April 2015</narrative>
  </humanitarian-scope>

If a vocabulary is not on the HumanitarianScopeVocabulary codelist, then the value of 99 (Reporting Organisation) should be declared.

Changelog

2.03

The definition of the @vocabulary-uri was updated.

2.02

The humanitarian-scope element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/humanitarian-scope/narrative

This is the reference page for the XML element narrative.

Definition

The description of the code specified.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the humanitarian-scope element.

The narrative element should be used only when the 99 (Reporting Organisation) HumanitarianScopeVocabulary is declared.

<humanitarian-scope type="1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="5">
  <narrative>Nepal Earthquake (April 2015)</narrative>
</humanitarian-scope>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.02

The humanitarian-scope and narrative elements were introduced in 2.02.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

policy-marker

iati-activities/iati-activity/policy-marker

This is the reference page for the XML element policy-marker.

Definition

A policy or theme addressed by the activity. This element was designed for the reporting of OECD DAC CRS policy markers (columns 20-23 and 28-31 of the CRS++ reporting format) but the vocabulary attribute allows it use by other (including local) systems. This element can be repeated for each policy marker.

Rules

This element may occur any number of times.

Attributes

@vocabulary

An IATI code for the vocabulary to be used to define policy markers. If omitted then the OECD DAC vocabulary is assumed.

This value must be of type xsd:string.

This value must be on the PolicyMarkerVocabulary codelist.

@vocabulary-uri

If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined.

This value must be of type xsd:anyURI.

@code

A policy marker code from the codelist specified in the vocabulary.

This attribute is required.

This value must be of type xsd:string.

This value must be on the PolicyMarker codelist, if the relevant vocabulary is used.

@significance

An OECD DAC CRS code indicating the significance of the policy marker for this activity. This attribute MUST be used for all OECD DAC CRS vocabularies.

This value must be of type xsd:string.

This value must be on the PolicySignificance codelist.

@significance must be present if @vocabulary=’1’ or not(@vocabulary)

Example Usage

Example policy-marker of an iati-activity.

The @vocabulary attribute declares a valid code (1) from the PolicyMarkerVocabulary codelist.

The @code attribute declares a valid code (1) from the PolicyMarker codelist.

The @significance attribute declares a valid code (3) from the PolicySignificance codelist.

<policy-marker vocabulary="1" code="2" significance="3" />

If a publisher uses a vocabulary of 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example:

<policy-marker vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" significance="3" />

The policy-marker element can be repeated in any iati-activity.

  <policy-marker vocabulary="1" code="2" significance="3" />
  <policy-marker vocabulary="1" code="9" significance="4" />
  <policy-marker vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" significance="3" />

If a vocabulary is not on the PolicyMarkerVocabulary codelist, then the value of 99 (Reporting Organisation) should be declared.

Changelog

2.03

The definition of the @vocabulary-uri was updated.

2.02

The vocabulary-uri attribute was added.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element, but only in particular use-cases.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/policy-marker/narrative

This is the reference page for the XML element narrative.

Definition

A description of the policy marker. This MUST ONLY be used if vocabulary is 99 (the reporting organisation’s own marker vocabulary). May be repeated for multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

narrative must be present if @vocabulary=’99’

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the policy-marker element.

The narrative element should be used only when the 99 (Reporting Organisation) PolicyMarkerVocabulary is declared.

<policy-marker vocabulary="99" code="10" significance="3">
        <narrative>Policy Marker Text</narrative>
</policy-marker>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

collaboration-type

iati-activities/iati-activity/collaboration-type

This is the reference page for the XML element collaboration-type.

Definition

The type of collaboration involved in the activity’s disbursements, e.g. “bilateral” or “multilateral”.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A code from the OECD DAC CRS “Bi_Multi” codelist.

This attribute is required.

This value must be of type xsd:string.

This value must be on the CollaborationType codelist.

Example Usage

Example collaboration-type for an iati-activity.

The @code attribute declares a valid code (1) from the CollaborationType codelist.

  <collaboration-type code="1" />

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

default-flow-type

iati-activities/iati-activity/default-flow-type

This is the reference page for the XML element default-flow-type.

Definition

Whether the activity is funded by Official Development Assistance (ODA), Other Official Flows (OOF), etc

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A code from the OECD DAC CRS “Type of flow” codelist

This attribute is required.

This value must be of type xsd:string.

This value must be on the FlowType codelist.

Example Usage

Example default-flow-type for an iati-activity.

The @code attribute declares a valid code (10) from the FlowType codelist.

  <default-flow-type code="10" />

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

default-finance-type

iati-activities/iati-activity/default-finance-type

This is the reference page for the XML element default-finance-type.

Definition

The type of finance (e.g. grant, loan, debt relief, etc). This the default value for all transactions in the activity report; it can be overridden by individual transactions.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A code from the OECD DAC CRS “Type of finance” codelist

This attribute is required.

This value must be of type xsd:string.

This value must be on the FinanceType codelist.

Example Usage

Example default-finance-type for an iati-activity.

The @code attribute declares a valid code (110) from the FinanceType codelist.

  <default-finance-type code="110" />

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

default-aid-type

iati-activities/iati-activity/default-aid-type

This is the reference page for the XML element default-aid-type.

Definition

The type of aid being supplied (project-type intervention, budget support, debt relief, etc.). This element specifies a default for all the activity’s financial transactions; it can be overridden at the individual transaction level.

Rules

This element may occur any number of times.

Attributes

@code

A code from the specified vocabulary.

This attribute is required.

This value must be of type xsd:string.

This value must be on the AidType codelist, if the relevant vocabulary is used.

This value must be on the EarmarkingCategory codelist, if the relevant vocabulary is used.

This value must be on the CashandVoucherModalities codelist, if the relevant vocabulary is used.

@vocabulary

A code for the vocabulary aid-type classifications. If omitted the AidType (OECD DAC) codelist is assumed. The code must be a valid value in the AidTypeVocabulary codelist.

Each selected vocabulary should only be used once for each activity (iati-activity/default-aid-type) or transaction (iati-activity/transaction/aid-type). All activities and/or transactions should contain a code from the DAC Type of Aid Vocabulary. The above guidelines should be converted to rules at the next integer upgrade.

This value must be of type xsd:string.

This value must be on the AidTypeVocabulary codelist.

Example Usage

Example default-aid-type for an iati-activity.

The @code attribute declares a valid code from the specified codelist.

The @vocabulary attribute declares a valid code (1) from the AidTypeVocabulary codelist.

<default-aid-type code="A01" vocabulary="1" />

The default-aid-type element can be repeated in any iati-activity.

  <default-aid-type code="A01" vocabulary="1" />
  <default-aid-type code="1" vocabulary="2" />

The vocabulary is used to declare which AidType list is in use. If omitted, an AidType Vocabulary of 1 (OECD DAC) is assumed.

Note: The aid-type element can override the default-aid-type value set in iati-activity

Changelog

2.03

The default-aid-type element can be reported multiple times within a iati-activity element added. The @code attribute definition was updated. The @vocabulary attribute was added.

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

default-tied-status

iati-activities/iati-activity/default-tied-status

This is the reference page for the XML element default-tied-status.

Definition

Whether the aid is untied, tied, or partially tied. This element specifies a default for all the activity’s financial transactions; it can be overridden at the individual transaction level.

If an activity is partially tied it is recommended that tied and untied commitments are reported as separate transactions and that transaction/tied-status is used to classify them.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

An IATI code interpreting the usage of Columns 36-38 of the CRS++ reporting format. (Amount tied, Amount partially untied, Amount tied)

This attribute is required.

This value must be of type xsd:string.

This value must be on the TiedStatus codelist.

Example Usage

Example default-tied-status for an iati-activity.

The @code attribute declares a valid code (3) from the TiedStatus codelist.

  <default-tied-status code="3" />

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

budget

iati-activities/iati-activity/budget

This is the reference page for the XML element budget.

Definition

The value of the activity’s budget for each financial quarter or year over the lifetime of the activity. The purpose of this element is to provide predictability for recipient planning on an annual basis. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative. The sum of budgets may or may not match the sum of commitments, depending on a publisher’s business model and legal frameworks.

Rules

This element may occur any number of times.

Attributes

@type

Whether this is the original budget (prepared when the original commitment was made) or has subsequently been revised

This value must be of type xsd:string.

This value must be on the BudgetType codelist.

@status

The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

This value must be of type xsd:string.

This value must be on the BudgetStatus codelist.

Example Usage

Example budget for an iati-activity.

This element is a parent for other child elements.

The @type attribute declares a valid code (1) from the BudgetType codelist.

The @status attribute declares a valid code (1) from the BudgetStatus codelist.

<budget type="1" status="1">
...
</budget>

Note: If the @type attribute is omitted, then BudgetType code 1 (Original) is assumed.

Similarly, if the @status attribute is omitted, then BudgetStatus code 1 (Indicative) is assumed.

Full example with all child elements:

  <budget type="1" status="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
  </budget>

The budget element can be repeated in any iati-activity.

Changelog

27/02/2018

The budget definition was updated as a bug fix.

2.02

The status attribute was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

period-start

iati-activities/iati-activity/budget/period-start

This is the reference page for the XML element period-start.

Definition

The start of the budget period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example usage of period-start of budget for an iati-activity.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <budget type="1" status="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
  </budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-activities/iati-activity/budget/period-end

This is the reference page for the XML element period-end.

Definition

The end of the period (which must not be greater than one year)

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example usage of period-end of budget for an iati-activity.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <budget type="1" status="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
  </budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-activities/iati-activity/budget/value

This is the reference page for the XML element value.

Definition

The budget for this period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of value of budget for an iati-activity.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code EUR, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-activity element.

  <budget type="1" status="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
  </budget>

Changelog

1.03

Values are now allowed to be declared as decimals instead of integers.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

planned-disbursement

iati-activities/iati-activity/planned-disbursement

This is the reference page for the XML element planned-disbursement.

Definition

The planned disbursement element should only be used to report specific planned cash transfers. These should be reported for a specific date or a meaningfully predictable period. These transactions should be reported in addition to budgets - which are typically annual breakdowns of the total activity commitment.

Rules

This element may occur any number of times.

Attributes

@type

Whether this is an original plan (prepared when the original commitment was made) or has subsequently been revised.

This value must be of type xsd:string.

This value must be on the BudgetType codelist.

Usage in practice

The purpose of planned-disbursement is to describe any predefined payment schedule.

Planned disbursements should relate to an actual transfer of funds.

Planned disbursements do not replace the activity-budget.

Example Usage

Example planned-disbursement for an iati-activity.

This element is a parent for other child elements.

The @type attribute declares a valid code (1) from the BudgetType codelist.

<planned-disbursement type="1">
...
</planned-disbursement>

Note: If omitted, then BudgetType code 1 (Original) is assumed.

Full example with all child elements:

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

Note: multiple planned disbursements are expressed by repeating the planned-disbursement element.

Changelog

2.01

The attribute @last-updated was removed.

The attribute @type was added.

1.05

A description was added to this element

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

period-start

iati-activities/iati-activity/planned-disbursement/period-start

This is the reference page for the XML element period-start.

Definition

The exact date of the planned disbursement OR the starting date of the period in which this specific disbursement will be made.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

Usage in practice

The period start should define when the actual transfer of funds will take place, if a specific date is known. If the specific payment date is not known, the period in which the transfer is due to take place should be described by using both period-start and period-end dates.

The timeframe between period-start and period-end should not normally exceed 3 calendar months.

Example Usage

Example usage of period-start of planned-disbursement for an iati-activity.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

Changelog

2.02

The definition of this element was amended for clarity.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-activities/iati-activity/planned-disbursement/period-end

This is the reference page for the XML element period-end.

Definition

The ending date for the period in which this specific disbursement will be made.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

Usage in practice

The period start should define when the actual transfer of funds will take place, if a specific date is known. If the specific payment date is not known, the period in which the transfer is due to take place should be described by using both period-start and period-end dates.

The timeframe between period-start and period-end should not normally exceed 3 calendar months.

Example Usage

Example usage of period-end of planned-disbursement for an iati-activity.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

In some instances, it may not be feasible to declare an period-end date. In such cases, the element is not included:

<planned-disbursement type="1">
        <period-start iso-date="2014-01-01" />
        <value currency="EUR" value-date="2014-01-01">3000</value>
</planned-disbursement>

Changelog

2.02

The definition of this element was amended for clarity.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-activities/iati-activity/planned-disbursement/value

This is the reference page for the XML element value.

Definition

The amount that is planned to be disbursed in the specified currency.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of value in context of planned-disbursement element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code EUR, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-activity element.

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

Changelog

1.03

Values are now allowed to be declared as decimals instead of integers.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

provider-org

iati-activities/iati-activity/planned-disbursement/provider-org

This is the reference page for the XML element provider-org.

Definition

The organisation from which the planned disbursement will originate. If omitted the reporting-org is assumed.

Rules

This element must occur no more than once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.

This value must be of type xsd:string.

@provider-activity-id

The identifier for the activity in which the planned disbursement will be reported. If omitted the current activity is assumed.

This value must be of type xsd:string.

@type

The type of organisation providing the funds.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

Example Usage

Example usage of provider-org of a planned-disbursement in an iati-activity.

This example declares the organisation identifier with the @ref attribute.

This example also declares the type of organisation which provided the funds, using the @type attribute.

<provider-org ref="BB-BBB-123456789-1234AA" type="10" />

This example declares the unique iati-identifier of the reported iati-activity from where the transaction is provided, with the @provider-activity-id attribute.

<provider-org ref="BB-BBB-123456789" type="10" provider-activity-id="BB-BBB-123456789-1234AA" />

Full example, within a planned-disbursement.

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

Changelog

2.03

The definition of the @ref attribute was updated.

2.02

The optional provider-org element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/planned-disbursement/provider-org/narrative

This is the reference page for the XML element narrative.

Definition

The name of the organisation. This can be repeated in multiple languages

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the provider-org element of a planned-disbursement.

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.02

Added the optional receiver-org element, including the narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

receiver-org

iati-activities/iati-activity/planned-disbursement/receiver-org

This is the reference page for the XML element receiver-org.

Definition

The organisation receiving the money from the planned disbursement.

Rules

This element must occur no more than once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.

This value must be of type xsd:string.

@receiver-activity-id

If outgoing funds are being provided to another activity that is reported to IATI, this may, if possible, record the unique IATI activity identifier for that activity.

This value must be of type xsd:string.

@type

The type of organisation receiving the funds.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

Example Usage

Example usage of receiver-org of a planned-disbursement in an iati-activity.

This example declares the organisation identifier with the @ref attribute.

This example also declares the type of organisation which received the funds, using the @type attribute.

<receiver-org ref="AA-AAA-123456789" type="23">Agency A</receiver-org>

This example declares the unique iati-identifier of the reported iati-activity to where the transaction is received, with the @receiver-activity-id attribute.

<receiver-org ref="AA-AAA-123456789" type="23" receiver-activity-id="AA-AAA-123456789-1234" />

Full example, within a planned-disbursement.

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

Changelog

2.03

The definition of the @ref attribute was updated.

2.02

The optional receiver-org element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/planned-disbursement/receiver-org/narrative

This is the reference page for the XML element narrative.

Definition

The name of the organisation. This can be repeated in multiple languages

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the receiver-org element of a planned-disbursement.

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.02

Added the optional receiver-org element, including the narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

capital-spend

iati-activities/iati-activity/capital-spend

This is the reference page for the XML element capital-spend.

Definition

The percentage of the total commitment that is for capital spending

Rules

This element must occur no more than once (within each parent element).

Attributes

@percentage

The percentage of the total commitment allocated to or planned for capital expenditure. Content must be a decimal number between 0 and 100 inclusive, with no percentage sign.

This attribute is required.

This value must be of type xsd:decimal.

The value of each of the elements described by capital-spend/@percentage must be at least 0.0 no more than 100.0 (inclusive).

Example Usage

Example capital-spend of an iati-activity.

This example uses the @percentage attribute to state 88.8% of the total commitment for the iati-activity is for capital expenditure.

  <capital-spend percentage="88.8" />

Changelog

2.03

Definition of @percentage attribute updated.

1.03

This is a new element, introduced in version 1.03 of the standard

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

transaction

iati-activities/iati-activity/transaction

This is the reference page for the XML element transaction.

Definition

Transactions recording committed or actual funds flowing in or out of an aid activity.

Rules

This element may occur any number of times.

Attributes

@ref

An internal reference linking this transaction back to the publisher’s financial management system.

This value must be of type xsd:string.

@humanitarian

A process flag to indicate that this transaction relates entirely or partially to humanitarian aid. If the entire activity relates to humanitarian aid this should be reported using iati-activity/@humanitarian, rather than for each transaction.

This value must be of type xsd:boolean.

Example Usage

Example transaction in an iati-activity.

This element is a parent for other child elements.

An example @ref of 1234 is declared.

<transaction ref="1234">
....
</transaction>

An example which would denote this as a humanitarian transaction i.e. with the @humanitarian element set to ‘1’.

<transaction ref="1234">
....
</transaction>

Full example with all child elements:

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

The transaction element can be repeated in any iati-activity.

Changelog

2.02

The humanitarian attribute was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

transaction-type

iati-activities/iati-activity/transaction/transaction-type

This is the reference page for the XML element transaction-type.

Definition

The type of the transaction (e.g. commitment, disbursement, expenditure, etc.).

Rules

This element must occur once and only once (within each parent element).

Attributes

@code

A code from the specified vocabulary.

This attribute is required.

This value must be of type xsd:string.

This value must be on the TransactionType codelist.

Example Usage

Example usage of transaction-type of transaction for an iati-activity.

The @code attribute declares a valid code (1) from the TransactionType codelist.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

transaction-date

iati-activities/iati-activity/transaction/transaction-date

This is the reference page for the XML element transaction-date.

Definition

The date on which the transaction was made or (in the case of commitments) agreed. The narrative content may contain text (e.g. 2011Q1) for accurately recording less specific dates such as month, quarter, or year.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

transaction-date/@iso-date must not be in the future.

Example Usage

Example usage of transaction-date of a transaction in an iati-activity.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-activities/iati-activity/transaction/value

This is the reference page for the XML element value.

Definition

The amount of the contribution.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

value/@value-date must not be in the future.

Example Usage

Example usage of value of a transaction in an iati-activity.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code EUR, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-activity element.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

1.03

Values are now allowed to be declared as decimals instead of integers.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/transaction/description

This is the reference page for the XML element description.

Definition

A human-readable description of the transaction.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of a transaction in an iati-activity.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/transaction/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element of an transaction.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

provider-org

iati-activities/iati-activity/transaction/provider-org

This is the reference page for the XML element provider-org.

Definition

For incoming funds this is the organisation from which the transaction originated. If omitted on outgoing funds the reporting-org is assumed.

Rules

This element must occur no more than once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.

This value must be of type xsd:string.

transaction/provider-org/@ref should match the regex [^\/\&\|\?]+

Either @ref or narrative must be present.

@provider-activity-id

If incoming funds are being provided from the budget of another activity that is reported to IATI, it if STRONGLY RECOMMENDED that this should record the provider’s unique IATI activity identifier for that activity.

This value must be of type xsd:string.

@type

The type of organisation providing the funds.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

Example Usage

Example usage of provider-org of a transaction in an iati-activity.

This example declares the organisation identifier with the @ref attribute.

This example declares the type of organisation who provided the funds, using the @type attribute.

<provider-org ref="BB-BBB-123456789-1234AA" type="10">
  <narrative>Agency B</narrative>
</provider-org>

This example additionally declares the unique iati-identifier of the reported iati-activity from where the transaction is provided, with the @provider-activity-id attribute.

<provider-org ref="BB-BBB-123456789" type="10" provider-activity-id="BB-BBB-123456789-1234AA">
  <narrative>Agency B</narrative>
</provider-org>

Full example, within a transaction.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.03

The definition of the @ref attribute was updated.

2.02

The attribute @type was added.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/transaction/provider-org/narrative

This is the reference page for the XML element narrative.

Definition

The name of the organisation. This can be repeated in multiple languages

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Either narrative or @ref must be present.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the provider-org element of a transaction.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

receiver-org

iati-activities/iati-activity/transaction/receiver-org

This is the reference page for the XML element receiver-org.

Definition

The organisation receiving the money from the transaction (if omitted on incoming funds then the receiver organisation is assumed to be the reporting organisation).

Rules

This element must occur no more than once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.

This value must be of type xsd:string.

transaction/receiver-org/@ref should match the regex [^\/\&\|\?]+

Either @ref or narrative must be present.

@receiver-activity-id

If outgoing funds are being provided to another activity that is reported to IATI, this may, if possible, record the unique IATI activity identifier for that activity.

This value must be of type xsd:string.

@type

The type of organisation receiving the funds.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

Example Usage

Example usage of receiver-org of a transaction in an iati-activity.

This example declares the organisation identifier with the @ref attribute.

This example declares the type of organisation receiving the funds, using the @type attribute.

<receiver-org ref="AA-AAA-123456789" type="23">
  <narrative>Agency B</narrative>
</receiver-org>

This example additionally declares the unique iati-identifier of the reported iati-activity to where the transaction is received, with the @receiver-activity-id attribute.

<receiver-org ref="AA-AAA-123456789" type="23" receiver-activity-id="AA-AAA-123456789-1234">
  <narrative>Agency A</narrative>
</receiver-org>

Full example, within a transaction.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.03

The definition of the @ref attribute was updated.

2.02

The attribute @type was added.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/transaction/receiver-org/narrative

This is the reference page for the XML element narrative.

Definition

The name of the organisation. This can be repeated in multiple languages

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Either narrative or @ref must be present.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the receiver-org element of a transaction.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

disbursement-channel

iati-activities/iati-activity/transaction/disbursement-channel

This is the reference page for the XML element disbursement-channel.

Definition

The channel through which the funds will flow for this transaction, from an IATI codelist.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

An IATI code defining channels of disbursement

This attribute is required.

This value must be of type xsd:string.

This value must be on the DisbursementChannel codelist.

Example Usage

Example usage of disbursement-channel of a transaction in an iati-activity.

The @code attribute declares a valid code (1) from the DisbursementChannel codelist.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

sector

iati-activities/iati-activity/transaction/sector

This is the reference page for the XML element sector.

Definition

A recognised code, from a recognised vocabulary, classifying the purpose of this transaction.

If this element is used then ALL transaction elements should contain a transaction/sector element and iati-activity/sector should NOT be used.

This element can be used multiple times, but only one sector can be reported per vocabulary.

Rules

This element may occur any number of times.

Either transaction/sector or sector must be present.

Attributes

@vocabulary

An IATI code for the vocabulary (codelist) used for sector classifications. If omitted, OECD DAC 5-digit Purpose Codes are assumed.

It is recommended that OECD DAC 5-digit Purpose Codes are used wherever possible. It is also recommended that if a publisher has its own classification system or systems, then the vocabularies 99 or 98 (Reporting Organisation’s own vocabularies) should be used in addition to the DAC codes.

Note that at transaction level, only one sector per vocabulary can be reported.

This value must be of type xsd:string.

This value must be on the SectorVocabulary codelist.

@vocabulary-uri

The URI where this vocabulary is defined. If the vocabulary is 99 or 98 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

This value must be of type xsd:anyURI.

@code

The code for the sector.

This attribute is required.

This value must be of type xsd:string.

This value must be on the Sector codelist, if the relevant vocabulary is used.

This value must be on the SectorCategory codelist, if the relevant vocabulary is used.

This value must be on the UNSDG-Goals codelist, if the relevant vocabulary is used.

This value must be on the UNSDG-Targets codelist, if the relevant vocabulary is used.

Example Usage

Example sector of a transaction within an iati-activity.

The @vocabulary attribute declares a valid code (2) from the SectorVocabulary codelist.

An example value 111 from this vocabulary is declared with the @code attribute.

<sector vocabulary="2" code="111" />

The sector element can be repeated in any transaction.

The vocabulary is used to declare which SectorVocabulary classification list is in use. If this is omitted, then IATI assumes a SectorVocabulary of 1 (OECD DAC CRS Purpose Codes (5 digit)).

If a vocabulary is not on the SectorVocabulary codelist, then the value of 99 or 98 (Reporting Organisation) should be declared.

If a publisher uses a vocabulary of 98 or 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example:

<sector vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />

Full example:

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.03

The definition of the @vocabulary-uri was updated.

2.02

The @vocabulary-uri attribute was added.

2.01

The sector element was added as a child element of transaction.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/transaction/sector/narrative

This is the reference page for the XML element narrative.

Definition

The free text description of the reporting organisation’s own sector definition. This can be repeated in multiple languages

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the sector element of a transaction.

The narrative element should be used specially when the 99 (Reporting Organisation) or 98 (Reporting Organisation 2) SectorVocabulary are declared.

<sector vocabulary="99" code="1">
        <narrative>Health Sector</narrative>
</sector>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The sector element was added to transaction in 2.01

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

recipient-country

iati-activities/iati-activity/transaction/recipient-country

This is the reference page for the XML element recipient-country.

Definition

A country that will benefit from this transaction. If a specific country is not known the recipient-region element should be used instead.

If transaction/recipient-country AND/OR transaction/recipient-region are used THEN ALL transaction elements MUST contain a recipient-country or recipient-region element AND (iati-activity/recipient-country AND iati-activity/recipient-region MUST NOT be used)

Rules

This element must occur no more than once (within each parent element).

transaction/recipient-country must not be present alongisde recipient-region and recipient-country.

Attributes

@code

ISO 3166-1 alpha-2 code for the country.

This attribute is required.

This value must be of type xsd:string.

This value should be on the Country codelist.

Example Usage

Example recipient-country of transaction in an iati-activity.

The @code attribute declares a valid code (AF) from the Country codelist.

<recipient-country code="AF" />

Full example:

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.01

The sector element was added as a child element of transaction.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/transaction/recipient-country/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-country element.

Note: Both the recipient-region and recipient-country elements still allow both a @code and descriptive text to be specified. This is to cover the isolated cases where the organisation publishing the data may not agree with name of a country or region given by the lookup codelists IATI uses.

<recipient-country code="XK">
        <narrative>Kosovo (As per UNSCR 1244)<narrative>
</recipient-country>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The recipient-country element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

recipient-region

iati-activities/iati-activity/transaction/recipient-region

This is the reference page for the XML element recipient-region.

Definition

A supranational geopolitical region that will benefit from this transaction. If a specific country is not known, then this element MUST be used.

If transaction/recipient-country AND/OR transaction/recipient-region are used THEN ALL transaction elements MUST contain a recipient-country or recipient-region element AND (iati-activity/recipient-country AND iati-activity/recipient-region MUST NOT be used)

Rules

This element must occur no more than once (within each parent element).

transaction/recipient-region must not be present alongisde recipient-region and recipient-country.

Attributes

@code

Either an OECD DAC or UN region code. Codelist is determined by vocabulary attribute.

This attribute is required.

This value must be of type xsd:string.

This value must be on the Region codelist, if the relevant vocabulary is used.

@vocabulary

An IATI code for the vocabulary from which the region code is drawn. If it is not present 1 - ‘OECD DAC’ is assumed.

This value must be of type xsd:string.

This value must be on the RegionVocabulary codelist.

@vocabulary-uri

The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

This value must be of type xsd:anyURI.

Example Usage

Example recipient-region of an iati-activity.

The @code attribute declares a valid code (489) from the Region codelist.

The optional @vocabulary attribute declares a valid code (1) from the RegionVocabulary codelist.

<recipient-region code="489" vocabulary="1" />

If a publisher uses a vocabulary of 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example:

<recipient-region code="A1" vocabulary="99" vocabulary-uri="http://example.com/vocab.html" />

Full example:

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.03

Definition of @vocabulary-uri attribute updated.

2.02

The vocabulary-uri attribute was added.

2.01

The sector element was added as a child element of transaction.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/transaction/recipient-region/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-region element.

Note: Both the recipient-region and recipient-country elements still allow both a @code and descriptive text to be specified. This is to cover the isolated cases where the organisation publishing the data may not agree with name of a country or region given by the lookup codelists IATI uses. Example not shown.

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The recipient-country element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

flow-type

iati-activities/iati-activity/transaction/flow-type

This is the reference page for the XML element flow-type.

Definition

Optional element to override the top-level default-flow-type element.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A code from the OECD DAC CRS “Type of flow” codelist

This attribute is required.

This value must be of type xsd:string.

This value must be on the FlowType codelist.

Example Usage

Example usage of flow-type of a transaction in an iati-activity.

The @code attribute declares a valid code (20) from the FlowType codelist.

Note: The flow-type element can override the default-flow-type value set in iati-activity:

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

finance-type

iati-activities/iati-activity/transaction/finance-type

This is the reference page for the XML element finance-type.

Definition

Optional element to override the top-level default-finance-type element on a transaction-by-transaction basis, if needed.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

A code from the OECD DAC CRS “Type of finance” codelist

This attribute is required.

This value must be of type xsd:string.

This value must be on the FinanceType codelist.

Example Usage

Example usage of finance-type of a transaction in an iati-activity.

The @code attribute declares a valid code (111) from the FinanceType codelist.

Note: The finance-type element can override the default-finance-type value set in iati-activity:

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

aid-type

iati-activities/iati-activity/transaction/aid-type

This is the reference page for the XML element aid-type.

Definition

Optional element to override the top-level default-aid-type element (debt relief, etc.) on a transaction-by-transaction basis if needed.

Rules

This element may occur any number of times.

Attributes

@code

A code from the specified vocabulary.

This attribute is required.

This value must be of type xsd:string.

This value must be on the AidType codelist, if the relevant vocabulary is used.

This value must be on the EarmarkingCategory codelist, if the relevant vocabulary is used.

This value must be on the CashandVoucherModalities codelist, if the relevant vocabulary is used.

@vocabulary

A code for the vocabulary aid-type classifications. If omitted the AidType (OECD DAC) codelist is assumed. The code must be a valid value in the AidTypeVocabulary codelist.

Each selected vocabulary should only be used once for each activity (iati-activity/default-aid-type) or transaction (iati-activity/transaction/aid-type). All activities and/or transactions should contain a code from the DAC Type of Aid Vocabulary. The above guidelines should be converted to rules at the next integer upgrade.

This value must be of type xsd:string.

This value must be on the AidTypeVocabulary codelist.

Example Usage

Example usage of aid-type of a transaction in an iati-activity.

The @code attribute declares a valid code from the specified codelist.

The @vocabulary attribute declares a valid code (1) from the AidTypeVocabulary codelist.

<aid-type code="A01" vocabulary="1" />

The aid-type element can be repeated in any iati-activity.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

The vocabulary is used to declare which AidType list is in use. If omitted, an AidType Vocabulary of 1 (OECD DAC) is assumed.

Note: The aid-type element can override the default-aid-type value set in iati-activity

Changelog

2.03

The aid-type element can be reported multiple times within a transaction element added. The @code attribute definition was updated. The @vocabulary attribute was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

tied-status

iati-activities/iati-activity/transaction/tied-status

This is the reference page for the XML element tied-status.

Definition

Optional element to override the top-level default-tied-status element on a transaction-by-transaction basis if needed.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

An IATI code interpreting the usage of Columns 36-38 of the CRS++ reporting format. (Amount tied, Amount partially untied, Amount tied)

This attribute is required.

This value must be of type xsd:string.

This value must be on the TiedStatus codelist.

Example Usage

Example usage of tied-status of a transaction in an iati-activity.

The @code attribute declares a valid code (5) from the TiedStatus codelist.

Note: The tied-status element can override the default-tied-status value set in iati-activity:

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-link

iati-activities/iati-activity/document-link

This is the reference page for the XML element document-link.

Definition

A link to an online, publicly accessible web page or document.

Rules

This element may occur any number of times.

Attributes

@url

The target URL of the external document, e.g. “http://www.example.org/doc.odt”.

This attribute is required.

This value must be of type xsd:anyURI.

@format

An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.

This attribute is required.

This value must be of type xsd:string.

This value must be on the FileFormat codelist.

Example Usage

Example document-link in an iati-activity.

This element is a parent for other child elements.

The @format attribute declares a valid code (application/vnd.oasis.opendocument.text) from the FileFormat codelist.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
...
</document-link>

Full example with all child elements:

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

The document-link element can be repeated in any iati-activity.

Changelog

2.03

The child element description was added.

1.02

Removed @language attribute from, and introduced an new language child element to, the document-link element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/document-link/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title of a document-link in an iati-activity.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/document-link/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title element.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/document-link/description

This is the reference page for the XML element description.

Definition

A description of the document contents, or guidance on where to access the relevant information in the document.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of a document-link in a iati-activity element.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

Changelog

2.03

The optional description element of a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/document-link/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a description in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

category

iati-activities/iati-activity/document-link/category

This is the reference page for the XML element category.

Definition

IATI Document Category Code

Rules

This element must occur at least once (within each parent element).

Attributes

@code

An IATI code defining the category of the document.

This attribute is required.

This value must be of type xsd:string.

This value must be on the DocumentCategory codelist.

Example Usage

Example usage of category of a document-link in an iati-activity.

This examples declares the DocumentCategory code A01, using the @code attribute.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

The category element can be repeated in any document-link.

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

language

iati-activities/iati-activity/document-link/language

This is the reference page for the XML element language.

Definition

The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.

Rules

This element may occur any number of times.

Attributes

@code

ISO 639-1 language code

This attribute is required.

This value must be of type xsd:string.

This value should be on the Language codelist.

Example Usage

Example usage of language of a document-link in an iati-activity.

The @language attribute declares a valid code (en) from the Language codelist.

Note: This specifies the language of the document being linked to.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

In some cases, a document-link may be in multiple languages. This is expressed by repeating the language element.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report.odt">
        <title>
                <narrative>Project Report 2013</narrative>
                <narrative xml:lang="fr">Rapport de projet 2013</narrative>
        </title>
        <category code="A01" />
        <language code="en" />
        <language code="fr" />
</document-link>

Changelog

2.01

Freetext is no longer allowed within this element.

In 2.01 this element usage rules were changed, to allow it to be repeated.

1.02

Addition of a @language element as a child of the document-link element: document-link/language/text() (0..1) - The ISO 639 code for the language of the document

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-date

iati-activities/iati-activity/document-link/document-date

This is the reference page for the XML element document-date.

Definition

The date of publication of the document that is being linked to.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Usage in practice

This document-date element would normally be the production or published date of the relevant document to identify the specific document version.

Example Usage

Example usage of the document-date element within a document-link as part of an iati-activity.

This examples declares an ISO date (corresponding to 5th February 2014) using the @iso-date attribute.

  <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
   <title>
    <narrative>Project Report 2013</narrative>
    <narrative xml:lang="fr">Rapport de projet 2013</narrative>
   </title>
   <description>
     <narrative> Description of the content of the project report or guidance on where to access the relevant information in this report </narrative>
   </description>
   <category code="A01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
  </document-link>

The document-date element should only be used once for each document-link element.

Changelog

2.02

The optional document-date element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

related-activity

iati-activities/iati-activity/related-activity

This is the reference page for the XML element related-activity.

Definition

Another separately reported IATI activity that is related to this one. The ‘type’ attribute describes the type of relationship: (eg. parent, child, multifunded). It is strongly recommended that linkage between activities in a hierarchical group should always be managed by use of this element with @type of 1 (parent) or 2 (child).

Rules

This element may occur any number of times.

Attributes

@ref

A valid activity identifier (as defined in iati-activity/iati-identifier).

This attribute is required.

This value must be of type xsd:string.

@type

An IATI code for the type of relationship

This attribute is required.

This value must be of type xsd:string.

This value must be on the RelatedActivityType codelist.

Example Usage

Example related-activity of an iati-activity.

The @type attribute declares a valid code (1) from the RelatedActivityType codelist.

An example @ref for another iati-activity of AA-AAA-123456789-6789 is provided.

  <related-activity ref="AA-AAA-123456789-6789" type="1" />

Note: multiple related activities are expressed by repeating the related-activity element.

Changelog

2.03

Definition of related-activity element updated.

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

legacy-data

iati-activities/iati-activity/legacy-data

This is the reference page for the XML element legacy-data.

Definition

The legacy data element allows for the reporting of values held in a field in the reporting organisation’s system which is similar, but not identical to an IATI element.

Rules

This element may occur any number of times.

Attributes

@name

The original field name in the reporting organisation’s system

This attribute is required.

This value must be of type xsd:string.

@value

The original field value in the reporting organisation’s system

This attribute is required.

This value must be of type xsd:string.

@iati-equivalent

The name of the equivalent IATI element.

This value must be of type xsd:NMTOKEN.

Example Usage

Example legacy-data of an iati-activity.

This example declares two non-IATI values for activity-status and transaction.

  <legacy-data name="Project Status" value="7" iati-equivalent="activity-status" />
  <legacy-data name="cost" value="1000" iati-equivalent="transaction" />

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

conditions

iati-activities/iati-activity/conditions

This is the reference page for the XML element conditions.

Definition

Specific terms and conditions attached to the activity that, if not met, may influence the delivery of commitments made by participating organisations.

Rules

This element must occur no more than once (within each parent element).

Attributes

@attached

A yes/no (1/0) value stating whether there are conditions attached to the activity. It is strongly recommended that this attribute is reported, even if there are no conditions attached (i.e. attached=”0”)

This attribute is required.

This value must be of type xsd:boolean.

Example Usage

Example conditions for an iati-activity.

This element is a parent for condition child element(s).

The @attached 0 boolean is included, for illustration of no conditions.

<conditions attached="0"/>

The @attached 1 boolean is included, for illustration of conditions.

<conditions attached="1">
...
</conditions>

Full example with all child elements:

  <conditions attached="1">
   <condition type="1">
    <narrative>Conditions text</narrative>
    <narrative xml:lang="fr">Conditions texte</narrative>
   </condition>
  </conditions>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

condition

iati-activities/iati-activity/conditions/condition

This is the reference page for the XML element condition.

Definition

The text of a specific condition attached to the activity. Organisation-wide terms and conditions that apply to all activities should not be reported here, but in either iati-organisation/document-link or iati-activity-document-link

Rules

This element may occur any number of times.

Attributes

@type

An IATI code defining the type of condition.

This attribute is required.

This value must be of type xsd:string.

This value must be on the ConditionType codelist.

Example Usage

Example condition child element of conditions of an iati-activity.

The @type attribute declares a valid code (1) from the ConditionType codelist.

  <conditions attached="1">
   <condition type="1">
    <narrative>Conditions text</narrative>
    <narrative xml:lang="fr">Conditions texte</narrative>
   </condition>
  </conditions>

The condition element can be repeated in any conditions of an iati-activity.

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

1.04

It was always the intention of the standard that a condition could be specified in different languages but the schema has never allowed it.

This has now been fixed.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/conditions/condition/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the condition element.

  <conditions attached="1">
   <condition type="1">
    <narrative>Conditions text</narrative>
    <narrative xml:lang="fr">Conditions texte</narrative>
   </condition>
  </conditions>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

  <conditions attached="1">
   <condition type="1">
    <narrative>Conditions text</narrative>
    <narrative xml:lang="fr">Conditions texte</narrative>
   </condition>
  </conditions>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

result

iati-activities/iati-activity/result

This is the reference page for the XML element result.

Definition

A container for reporting outputs, outcomes, impacts and other results that stem directly from the activity. This may be repeated for each type of result reported.

Rules

This element may occur any number of times.

Attributes

@type

An IATI code for the type of result being reported.

This attribute is required.

This value must be of type xsd:string.

This value must be on the ResultType codelist.

@aggregation-status

Boolean flag indicating whether the data in the result set are suitable for aggregation.

This value must be of type xsd:boolean.

Example Usage

Example result for an iati-activity.

This element is a parent for other child elements.

The @type attribute declares a valid code (1) from the ResultType codelist.

The @aggregation-status 1 boolean is included, for illustration of suitability for aggregation.

<result type="1" aggregation-status="1">
                ...
</result>

Full example with all child elements:

  <result type="1" aggregation-status="1">
   <title>
    <narrative>Result title</narrative>
   </title>
   <description>
    <narrative>Result description text</narrative>
   </description>
   <!--result-document-link example starts-->
   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>
<!--result-document-link example ends-->
<!--result-reference starts-->
   <reference vocabulary="99" code="B1" vocabulary-uri="http://example.com/indicators.html" />
<!--result-reference ends-->
<!--result-indicator starts-->
   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>
   <!--result-indicator ends-->
  </result>

The result element can be repeated in any iati-activity.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/result/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title in a result of an iati-activity.

  <result type="1" aggregation-status="1">
   <title>
    <narrative>Result title</narrative>
   </title>
   <description>
    <narrative>Result description text</narrative>
   </description>
   <!--result-document-link example starts-->
   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>
<!--result-document-link example ends-->
<!--result-reference starts-->
   <reference vocabulary="99" code="B1" vocabulary-uri="http://example.com/indicators.html" />
<!--result-reference ends-->
<!--result-indicator starts-->
   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>
   <!--result-indicator ends-->
  </result>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title parent element.

<title>
        <narrative>Result title</narrative>
        <narrative xml:lang="fr">Result titre</narrative>
</title>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

<title>
        <narrative>Result title</narrative>
        <narrative xml:lang="fr">Result titre</narrative>
</title>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/result/description

This is the reference page for the XML element description.

Definition

A longer, human-readable description.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description in a result of an iati-activity.

  <result type="1" aggregation-status="1">
   <title>
    <narrative>Result title</narrative>
   </title>
   <description>
    <narrative>Result description text</narrative>
   </description>
   <!--result-document-link example starts-->
   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>
<!--result-document-link example ends-->
<!--result-reference starts-->
   <reference vocabulary="99" code="B1" vocabulary-uri="http://example.com/indicators.html" />
<!--result-reference ends-->
<!--result-indicator starts-->
   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>
   <!--result-indicator ends-->
  </result>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

The @type attribute was removed.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description of a result.

<description>
        <narrative>Result description text</narrative>
        <narrative xml:lang="fr">Result texte de description</narrative>
</description>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

<description>
        <narrative>Result description text</narrative>
        <narrative xml:lang="fr">Result texte de description</narrative>
</description>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-link

iati-activities/iati-activity/result/document-link

This is the reference page for the XML element document-link.

Definition

A link to an online, publicly accessible web page or document expanding on the result.

Rules

This element may occur any number of times.

Attributes

@url

The target URL of the external document, e.g. “http://www.example.org/doc.odt”.

This attribute is required.

This value must be of type xsd:anyURI.

@format

An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.

This attribute is required.

This value must be of type xsd:string.

This value must be on the FileFormat codelist.

Example Usage

Example document-link in a result element.

This element is a parent for other child elements.

The @format attribute declares a valid code (application/vnd.oasis.opendocument.text) from the FileFormat codelist.

The @url attribute provides the document location.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
...
</document-link>

Full example with all child elements:

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The document-link element can be repeated in any result element.

Changelog

2.03

The optional document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/result/document-link/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title of a document-link in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The mandatory title element of a document-link in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/document-link/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a title in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/result/document-link/description

This is the reference page for the XML element description.

Definition

A description of the document contents, or guidance on where to access the relevant information in the document.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of a document-link in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The optional description element of a document-link in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/document-link/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a description in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

category

iati-activities/iati-activity/result/document-link/category

This is the reference page for the XML element category.

Definition

IATI Document Category Code

Rules

This element must occur at least once (within each parent element).

Attributes

@code

An IATI code defining the category of the document.

This attribute is required.

This value must be of type xsd:string.

This value must be on the DocumentCategory codelist.

Example Usage

Example usage of category of a document-link in a result element.

This examples declares the DocumentCategory code A01, using the @code attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The category element can be repeated in any document-link.

Changelog

2.03

The mandatory category element of a document-link in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

language

iati-activities/iati-activity/result/document-link/language

This is the reference page for the XML element language.

Definition

The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.

Rules

This element may occur any number of times.

Attributes

@code

ISO 639-1 language code

This attribute is required.

This value must be of type xsd:string.

This value should be on the Language codelist.

Example Usage

Example usage of language of a document-link in a result element.

The @language attribute declares a valid code (en) from the Language codelist.

Note: This specifies the language of the document being linked to.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

In some cases, a document-link may be in multiple languages. This is expressed by repeating the language element.

Changelog

2.03

The optional language element of a document-link in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-date

iati-activities/iati-activity/result/document-link/document-date

This is the reference page for the XML element document-date.

Definition

The date of publication of the document that is being linked to.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

This document-date element would normally be the production or published date of the relevant document to identify the specific document version.

Example Usage

Example usage of the document-date element within a document-link as part of a result element.

This examples declares an ISO date (corresponding to 5th February 2014) using the @iso-date attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The document-date element should only be used once for each document-link element.

Changelog

The optional document-date element of a document-link in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

reference

iati-activities/iati-activity/result/reference

This is the reference page for the XML element reference.

Definition

A reference element to allow for the coded identification of a results framework.

Rules

This element may occur any number of times.

Attributes

@code

A code from the codelist identified in vocabulary that identifies a results framework.

This attribute is required.

This value must be of type xsd:string.

@vocabulary

A code for the results framework vocabulary. The code must be a valid value in the ResultVocabulary codelist.

This attribute is required.

This value must be of type xsd:string.

This value must be on the ResultVocabulary codelist.

@vocabulary-uri

The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

This value must be of type xsd:anyURI.

Example Usage

Example of reference in the context of a result element.

This example declares use of @vocabulary 99, with a @code of B1. The @vocabulary-uri attribute should also be used:

<reference vocabulary="99" code="B1" vocabulary-uri="http://example.com/indicators.html" />

The reference element can be repeated in any result. If the reference element is reported at result level it must not be reported at indicator level:

   <reference vocabulary="99" code="B1" vocabulary-uri="http://example.com/indicators.html" />

Changelog

2.03

The optional reference element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

indicator

iati-activities/iati-activity/result/indicator

This is the reference page for the XML element indicator.

Definition

The indicator(s) that meet the results. There can be multiple indicators for each result.

Rules

This element must occur at least once (within each parent element).

Attributes

@measure

An IATI code defining the unit of measure in which the value is reported.

This attribute is required.

This value must be of type xsd:string.

This value must be on the IndicatorMeasure codelist.

@ascending

A boolean describing the behaviour of the indicator. It is “true” if the indicator improves from small to large (e.g. clinics built); false if it improves from large to small (e.g. cases of a disease).

This value must be of type xsd:boolean.

@aggregation-status

Boolean flag indicating whether the data in the result set are suitable for aggregation.

This value must be of type xsd:boolean.

Example Usage

Example usage of indicator in a result of an iati-activity.

This element is a parent for other child elements. It is also contained within a result element.

The @measure attribute declares a valid code (1) from the IndicatorMeasure codelist.

The @ascending boolean of 1 also declares that the data is asscending.

The @aggregation-status 1 boolean is included, for illustration of suitability for aggregation.

   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>

The indicator element can be repeated in any result of an iati-activity.

Changelog

2.03

The optional attribute @aggregation-status was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/result/indicator/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title in context of an indicator in a result element.

   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title parent element.

<title>
        <narrative>Indicator title</narrative>
        <narrative xml:lang="fr">Indicator titre</narrative>
</title>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

<title>
        <narrative>Indicator title</narrative>
        <narrative xml:lang="fr">Indicator titre</narrative>
</title>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/result/indicator/description

This is the reference page for the XML element description.

Definition

A longer, human-readable description.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description in context of an indicator in a result element.

   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

The @type attribute was removed.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description of a result.

<description>
        <narrative>Indicator title</narrative>
        <narrative xml:lang="fr">Indicator titre</narrative>
</description>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

<description>
        <narrative>Indicator title</narrative>
        <narrative xml:lang="fr">Indicator titre</narrative>
</description>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-link

iati-activities/iati-activity/result/indicator/document-link

This is the reference page for the XML element document-link.

Definition

A link to an online, publicly accessible web page or document expanding on the result.

Rules

This element may occur any number of times.

Attributes

@url

The target URL of the external document, e.g. “http://www.example.org/doc.odt”.

This attribute is required.

This value must be of type xsd:anyURI.

@format

An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.

This attribute is required.

This value must be of type xsd:string.

This value must be on the FileFormat codelist.

Example Usage

Example document-link in a indicator in a result element.

This element is a parent for other child elements.

The @format attribute declares a valid code (application/vnd.oasis.opendocument.text) from the FileFormat codelist.

The @url attribute provides the document location.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
...
</document-link>

Full example with all child elements:

   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>

The document-link element can be repeated in any result element.

Changelog

2.03

The optional document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/result/indicator/document-link/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title of a document-link in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The mandatory title element of a document-link in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/document-link/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a title in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/result/indicator/document-link/description

This is the reference page for the XML element description.

Definition

A description of the document contents, or guidance on where to access the relevant information in the document.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of a document-link in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The optional description element of a document-link in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/document-link/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a description in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

category

iati-activities/iati-activity/result/indicator/document-link/category

This is the reference page for the XML element category.

Definition

IATI Document Category Code

Rules

This element must occur at least once (within each parent element).

Attributes

@code

An IATI code defining the category of the document.

This attribute is required.

This value must be of type xsd:string.

This value must be on the DocumentCategory codelist.

Example Usage

Example usage of category of a document-link in a indicator in a result element.

This examples declares the DocumentCategory code A01, using the @code attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The category element can be repeated in any document-link.

Changelog

2.03

The mandatory category element of a document-link in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

language

iati-activities/iati-activity/result/indicator/document-link/language

This is the reference page for the XML element language.

Definition

The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.

Rules

This element may occur any number of times.

Attributes

@code

ISO 639-1 language code

This attribute is required.

This value must be of type xsd:string.

This value should be on the Language codelist.

Example Usage

Example usage of language of a document-link in a indicator in a result element.

The @language attribute declares a valid code (en) from the Language codelist.

Note: This specifies the language of the document being linked to.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

In some cases, a document-link may be in multiple languages. This is expressed by repeating the language element.

Changelog

2.03

The optional language element of a document-link in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-date

iati-activities/iati-activity/result/indicator/document-link/document-date

This is the reference page for the XML element document-date.

Definition

The date of publication of the document that is being linked to.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

This document-date element would normally be the production or published date of the relevant document to identify the specific document version.

Example Usage

Example usage of the document-date element within a document-link in a indicator as part of a result element.

This examples declares an ISO date (corresponding to 5th February 2014) using the @iso-date attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The document-date element should only be used once for each document-link element.

Changelog

The optional document-date element of a document-link in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

reference

iati-activities/iati-activity/result/indicator/reference

This is the reference page for the XML element reference.

Definition

A standardised means of identifying the indicator from a code in a recognised vocabulary. Multiple vocabularies may be specified, but each vocabulary may be specified only once for each indicator.

Rules

This element may occur any number of times.

There must be no more than one element or attribute matched at reference[1] or ../reference[1].

Attributes

@vocabulary

A code for a recognised vocabulary of indicators. The value for this field should appear in the IndicatorVocabulary codelist.

This attribute is required.

This value must be of type xsd:string.

This value should be on the IndicatorVocabulary codelist.

@code

A code for an indicator defined in the specified vocabulary specified.

This attribute is required.

This value must be of type xsd:string.

@indicator-uri

The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

This value must be of type xsd:anyURI.

Example Usage

Example of reference in the context of an indicator of a result element.

This example declares use of @vocabulary 1, with a @code of 3429:

<reference vocabulary="1" code="3429" />

If a publisher uses a vocabulary of 99 (i.e. ‘Reporting Organisation’), then the @indicator-uri attribute should also be used, for example:

<reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />

The reference element can be repeated in any indicator. If the reference element is reported at indicator level it must not be reported at result level:

   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>

Changelog

2.03

Definition of @indicator-uri attribute updated.

The rule for using the reference element was added.

2.02

The optional reference element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

baseline

iati-activities/iati-activity/result/indicator/baseline

This is the reference page for the XML element baseline.

Definition

The baseline value for the indicator

Rules

This element may occur any number of times.

Attributes

@iso-date

This value must be of type xsd:date.

@year

The year the baseline value was taken (yyyy)

This attribute is required.

This value must be of type xsd:positiveInteger.

@value

The baseline value.

The @value should be omitted for qualitative measures.

The @value must be included for non-qualitative measures.

The @value should be a valid number for all non-qualitative measures.

This value must be of type xsd:string.

Example Usage

Example of baseline in context of an indicator in a result element.

This example declares @year as 2012, @iso-date as 2012-01-01,with a @value of 10:

   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>

Changelog

2.03

The occurance rules of the baseline element were amended so that it can be reported multiple times.

The attribute @iso-date was added.

The attribute @value was made optional and rules for its use added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

location

iati-activities/iati-activity/result/indicator/baseline/location

This is the reference page for the XML element location.

Definition

A location already defined and described in the iati-activity/location element.

Rules

This element may occur any number of times.

Attributes

@ref

A cross-reference to the internal reference assigned to a defined location: iati-activity/location/@ref.

This value must be of type xsd:string.

Example Usage

Example of location in context of a baseline element (as part of a parent result/indicator element).

This example declares @ref as AF-KAN, which matches the @ref value for a location already referenced in iati-activity/location:

<location ref="AF-KAN" />

The location element can be repeated within any actual element:

     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>

Changelog

2.03

The optional location element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

dimension

iati-activities/iati-activity/result/indicator/baseline/dimension

This is the reference page for the XML element dimension.

Definition

A category used for disaggregating the result by gender, age, etc.

Rules

This element may occur any number of times.

Attributes

@name

Freetext description of a category being disaggregated.

This value must be of type xsd:string.

@value

Description of the value being disaggregated.

This value must be of type xsd:string.

Example Usage

Example of dimension in context of a baseline element (as part of a parent result/indicator element).

This example declares @name as sex, with a @value of female:

<dimension name="sex" value="female" />

The dimension element can be repeated within any target element:

     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>

Changelog

2.03

The optional dimension element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-link

iati-activities/iati-activity/result/indicator/baseline/document-link

This is the reference page for the XML element document-link.

Definition

A link to an online, publicly accessible web page or document expanding on the result.

Rules

This element may occur any number of times.

Attributes

@url

The target URL of the external document, e.g. “http://www.example.org/doc.odt”.

This attribute is required.

This value must be of type xsd:anyURI.

@format

An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.

This attribute is required.

This value must be of type xsd:string.

This value must be on the FileFormat codelist.

Example Usage

Example document-link in a baseline in a indicator in a result element.

This element is a parent for other child elements.

The @format attribute declares a valid code (application/vnd.oasis.opendocument.text) from the FileFormat codelist.

The @url attribute provides the document location.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
...
</document-link>

Full example with all child elements:

     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>

The document-link element can be repeated in any result element.

Changelog

2.03

The optional document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/result/indicator/baseline/document-link/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title of a document-link in a baseline in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The mandatory title element of a document-link in a baseline in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/baseline/document-link/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a title in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/result/indicator/baseline/document-link/description

This is the reference page for the XML element description.

Definition

A description of the document contents, or guidance on where to access the relevant information in the document.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of a document-link in a baseline in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The optional description element of a document-link in a baseline in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/baseline/document-link/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a description in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

category

iati-activities/iati-activity/result/indicator/baseline/document-link/category

This is the reference page for the XML element category.

Definition

IATI Document Category Code

Rules

This element must occur at least once (within each parent element).

Attributes

@code

An IATI code defining the category of the document.

This attribute is required.

This value must be of type xsd:string.

This value must be on the DocumentCategory codelist.

Example Usage

Example usage of category of a document-link in a baseline in a indicator in a result element.

This examples declares the DocumentCategory code A01, using the @code attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The category element can be repeated in any document-link.

Changelog

2.03

The mandatory category element of a document-link in a baseline in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

language

iati-activities/iati-activity/result/indicator/baseline/document-link/language

This is the reference page for the XML element language.

Definition

The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.

Rules

This element may occur any number of times.

Attributes

@code

ISO 639-1 language code

This attribute is required.

This value must be of type xsd:string.

This value should be on the Language codelist.

Example Usage

Example usage of language of a document-link in a baseline in a indicator in a result element.

The @language attribute declares a valid code (en) from the Language codelist.

Note: This specifies the language of the document being linked to.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

In some cases, a document-link may be in multiple languages. This is expressed by repeating the language element.

Changelog

2.03

The optional language element of a document-link in a baseline in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-date

iati-activities/iati-activity/result/indicator/baseline/document-link/document-date

This is the reference page for the XML element document-date.

Definition

The date of publication of the document that is being linked to.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

This document-date element would normally be the production or published date of the relevant document to identify the specific document version.

Example Usage

Example usage of the document-date element within a document-link in a baseline in a indicator as part of a result element.

This examples declares an ISO date (corresponding to 5th February 2014) using the @iso-date attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The document-date element should only be used once for each document-link element.

Changelog

The optional document-date element of a document-link in a baseline in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

comment

iati-activities/iati-activity/result/indicator/baseline/comment

This is the reference page for the XML element comment.

Definition

A human-readable comment associated with a piece of aid information.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of comment for baseline:

     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/baseline/comment/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the comment of a baseline.

<comment>
        <narrative>Baseline comment text</narrative>
        <narrative xml:lang="fr">Baseline comment texte</narrative>
</comment>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

<comment>
        <narrative>Baseline comment text</narrative>
        <narrative xml:lang="fr">Baseline comment texte</narrative>
</comment>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period

iati-activities/iati-activity/result/indicator/period

This is the reference page for the XML element period.

Definition

The period covered for the results reported. Multiple periods can be reported for a single indicator.

Rules

This element may occur any number of times.

Example Usage

Example usage of period in context of an indicator in a result element.

This element is a parent for other child elements.

   <indicator measure="1" ascending="1" aggregation-status="1">
     <title>
      <narrative>Indicator title</narrative>
     </title>
     <description>
      <narrative>Indicator description text</narrative>
     </description>
     <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_indicator_en.odt">
      <title>
       <narrative>Results Indicator Report 2013</narrative>
      </title>
      <description>
        <narrative>Report of results indicator</narrative>
      </description>
      <category code="A01" />
      <language code="en" />
      <document-date iso-date="2014-02-05" />
     </document-link>
     <reference vocabulary="1" code="3429" />
     <reference vocabulary="7" code="861" />
     <reference vocabulary="99" code="B1" indicator-uri="http://example.com/indicators.html" />
<!--result-baseline starts-->
     <baseline year="2012" iso-date="2012-01-01" value="10">
      <location ref="AF-KAN" />
      <location ref="KH-PNH" />
      <dimension name="sex" value="female" />
      <dimension name="age" value="adult" />
      <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_baseline_en.odt">
       <title>
        <narrative>Results Baseline Report 2013</narrative>
       </title>
       <description>
         <narrative>Report of results baseline</narrative>
       </description>
       <category code="A01" />
       <language code="en" />
       <document-date iso-date="2014-02-05" />
      </document-link>
      <comment>
       <narrative>Baseline comment text</narrative>
      </comment>
     </baseline>
     <!--result-baseline ends-->
     <!--result-period starts-->
     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>
     <!--result-period ends-->
   </indicator>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

period-start

iati-activities/iati-activity/result/indicator/period/period-start

This is the reference page for the XML element period-start.

Definition

The start of the reporting period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

Example Usage

Example usage of period-start within period, in context of an indicator in a result element.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-activities/iati-activity/result/indicator/period/period-end

This is the reference page for the XML element period-end.

Definition

The end of the reporting period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

Example Usage

Example usage of period-end within period, in context of an indicator in a result element.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

target

iati-activities/iati-activity/result/indicator/period/target

This is the reference page for the XML element target.

Definition

The target milestone for this period

Rules

This element may occur any number of times.

Attributes

@value

The target value.

The @value should be omitted for qualitative measures.

The @value must be included for non-qualitative measures.

The @value should be a valid number for all non-qualitative measures.

This value must be of type xsd:string.

Example Usage

Example usage of target within period, in context of an indicator in a result element.

The @value attribute declares an example value of 11

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.03

The target element of a period in a indicator in a result element can be reported multiple times added.

The attribute @value was made optional and rules for its use added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

location

iati-activities/iati-activity/result/indicator/period/target/location

This is the reference page for the XML element location.

Definition

A location already defined and described in the iati-activity/location element.

Rules

This element may occur any number of times.

Attributes

@ref

A cross-reference to the internal reference assigned to a defined location: iati-activity/location/@ref.

This value must be of type xsd:string.

Example Usage

Example of location in context of an target element (as part of a parent result/indicator element).

This example declares @ref as AF-KAN, which matches the @ref value for a location already referenced in iati-activity/location:

<location ref="AF-KAN" />

The location element can be repeated within any target element:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.02

The optional location element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

dimension

iati-activities/iati-activity/result/indicator/period/target/dimension

This is the reference page for the XML element dimension.

Definition

A category used for disaggregating the result by gender, age, etc.

Rules

This element may occur any number of times.

Attributes

@name

Freetext description of a category being disaggregated.

This value must be of type xsd:string.

@value

Description of the value being disaggregated.

This value must be of type xsd:string.

Example Usage

Example of dimension in context of an target element (as part of a parent result/indicator element).

This example declares @name as sex, with a @value of female:

<dimension name="sex" value="female" />

The dimension element can be repeated within any target element:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.02

The optional dimension element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

comment

iati-activities/iati-activity/result/indicator/period/target/comment

This is the reference page for the XML element comment.

Definition

A human-readable comment associated with a piece of aid information.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of comment for target:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/period/target/comment/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the comment of a target.

<comment>
        <narrative>Target comment text</narrative>
        <narrative xml:lang="fr">Target comment texte</narrative>
</comment>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

<comment>
        <narrative>Target comment text</narrative>
        <narrative xml:lang="fr">Target comment texte</narrative>
</comment>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-link

iati-activities/iati-activity/result/indicator/period/target/document-link

This is the reference page for the XML element document-link.

Definition

A link to an online, publicly accessible web page or document expanding on the result.

Rules

This element may occur any number of times.

Attributes

@url

The target URL of the external document, e.g. “http://www.example.org/doc.odt”.

This attribute is required.

This value must be of type xsd:anyURI.

@format

An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.

This attribute is required.

This value must be of type xsd:string.

This value must be on the FileFormat codelist.

Example Usage

Example document-link in a target in a period in a indicator in a result element.

This element is a parent for other child elements.

The @format attribute declares a valid code (application/vnd.oasis.opendocument.text) from the FileFormat codelist.

The @url attribute provides the document location.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
...
</document-link>

Full example with all child elements:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

The document-link element can be repeated in any result element.

Changelog

2.03

The optional document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/result/indicator/period/target/document-link/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title of a document-link in a target in a period in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The mandatory title element of a document-link in a target in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/period/target/document-link/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a title in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/result/indicator/period/target/document-link/description

This is the reference page for the XML element description.

Definition

A description of the document contents, or guidance on where to access the relevant information in the document.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of a document-link in a target in a period in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The optional description element of a document-link in a target in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/period/target/document-link/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a description in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

category

iati-activities/iati-activity/result/indicator/period/target/document-link/category

This is the reference page for the XML element category.

Definition

IATI Document Category Code

Rules

This element must occur at least once (within each parent element).

Attributes

@code

An IATI code defining the category of the document.

This attribute is required.

This value must be of type xsd:string.

This value must be on the DocumentCategory codelist.

Example Usage

Example usage of category of a document-link in a target in a period in a indicator in a result element.

This examples declares the DocumentCategory code A01, using the @code attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The category element can be repeated in any document-link.

Changelog

2.03

The mandatory category element of a document-link in a target in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

language

iati-activities/iati-activity/result/indicator/period/target/document-link/language

This is the reference page for the XML element language.

Definition

The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.

Rules

This element may occur any number of times.

Attributes

@code

ISO 639-1 language code

This attribute is required.

This value must be of type xsd:string.

This value should be on the Language codelist.

Example Usage

Example usage of language of a document-link in a target in a period in a indicator in a result element.

The @language attribute declares a valid code (en) from the Language codelist.

Note: This specifies the language of the document being linked to.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

In some cases, a document-link may be in multiple languages. This is expressed by repeating the language element.

Changelog

2.03

The optional language element of a document-link in a target in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-date

iati-activities/iati-activity/result/indicator/period/target/document-link/document-date

This is the reference page for the XML element document-date.

Definition

The date of publication of the document that is being linked to.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

This document-date element would normally be the production or published date of the relevant document to identify the specific document version.

Example Usage

Example usage of the document-date element within a document-link in a target in a period in a indicator as part of a result element.

This examples declares an ISO date (corresponding to 5th February 2014) using the @iso-date attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The document-date element should only be used once for each document-link element.

Changelog

The optional document-date element of a document-link in a target in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

actual

iati-activities/iati-activity/result/indicator/period/actual

This is the reference page for the XML element actual.

Definition

A record of the achieved result for this period.

Rules

This element may occur any number of times.

Attributes

@value

The actual measure.

The @value should be omitted for qualitative measures.

The @value must be included for non-qualitative measures.

The @value should be a valid number for all non-qualitative measures.

This value must be of type xsd:string.

Example Usage

Example usage of actual within period, in context of an indicator in a result element.

The @value attribute declares an example value of 11

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.03

The actual element of a period in an indicator in a result element can be reported multiple times added.

The attribute @value was made optional and rules for its use added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

location

iati-activities/iati-activity/result/indicator/period/actual/location

This is the reference page for the XML element location.

Definition

A location already defined and described in the iati-activity/location element.

Rules

This element may occur any number of times.

Attributes

@ref

A cross-reference to the internal reference assigned to a defined location: iati-activity/location/@ref.

This value must be of type xsd:string.

Example Usage

Example of location in context of an actual element (as part of a parent result/indicator element).

This example declares @ref as AF-KAN, which matches the @ref value for a location already referenced in iati-activity/location:

<location ref="AF-KAN" />

The location element can be repeated within any actual element:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.02

The optional location element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

dimension

iati-activities/iati-activity/result/indicator/period/actual/dimension

This is the reference page for the XML element dimension.

Definition

A category used for disaggregating the result by gender, age, etc.

Rules

This element may occur any number of times.

Attributes

@name

Freetext description of a category being disaggregated.

This value must be of type xsd:string.

@value

Description of the value being disaggregated.

This value must be of type xsd:string.

Example Usage

Example of dimension in context of an actual element (as part of a parent result/indicator element).

This example declares @name as sex, with a @value of female:

<dimension name="sex" value="female" />

The dimension element can be repeated within any actual element:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.02

The optional dimension element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

comment

iati-activities/iati-activity/result/indicator/period/actual/comment

This is the reference page for the XML element comment.

Definition

A human-readable comment associated with a piece of aid information.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of comment for actual:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/period/actual/comment/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the comment of a actual.

<comment>
        <narrative>Actual comment text</narrative>
        <narrative xml:lang="fr">Actual comment texte</narrative>
</comment>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute:

<comment>
        <narrative>Actual comment text</narrative>
        <narrative xml:lang="fr">Actual comment texte</narrative>
</comment>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-link

iati-activities/iati-activity/result/indicator/period/actual/document-link

This is the reference page for the XML element document-link.

Definition

A link to an online, publicly accessible web page or document expanding on the result.

Rules

This element may occur any number of times.

Attributes

@url

The target URL of the external document, e.g. “http://www.example.org/doc.odt”.

This attribute is required.

This value must be of type xsd:anyURI.

@format

An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.

This attribute is required.

This value must be of type xsd:string.

This value must be on the FileFormat codelist.

Example Usage

Example document-link in a actual in a period in a indicator in a result element.

This element is a parent for other child elements.

The @format attribute declares a valid code (application/vnd.oasis.opendocument.text) from the FileFormat codelist.

The @url attribute provides the document location.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
...
</document-link>

Full example with all child elements:

     <period>
      <period-start iso-date="2013-01-01" />
      <period-end iso-date="2013-03-31" />
      <target value="10">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
        <narrative>Target comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_target_en.odt">
        <title>
         <narrative>Results Period Target Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period target</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </target>
      <actual value="11">
       <location ref="AF-KAN" />
       <location ref="KH-PNH" />
       <dimension name="sex" value="female" />
       <dimension name="age" value="adult" />
       <comment>
         <narrative>Actual comment text</narrative>
       </comment>
       <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_period_actual_en.odt">
        <title>
         <narrative>Results Period Actual Report 2013</narrative>
        </title>
        <description>
          <narrative>Report of results period actual</narrative>
        </description>
        <category code="A01" />
        <language code="en" />
        <document-date iso-date="2014-02-05" />
       </document-link>
      </actual>
     </period>

The document-link element can be repeated in any result element.

Changelog

2.03

The optional document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

title

iati-activities/iati-activity/result/indicator/period/actual/document-link/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title of a document-link in a actual in a period in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The mandatory title element of a document-link in a actual in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/period/actual/document-link/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a title in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-activities/iati-activity/result/indicator/period/actual/document-link/description

This is the reference page for the XML element description.

Definition

A description of the document contents, or guidance on where to access the relevant information in the document.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example usage of description of a document-link in a actual in a period in a indicator in a result element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

Changelog

2.03

The optional description element of a document-link in a actual in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-activities/iati-activity/result/indicator/period/actual/document-link/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a description in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

category

iati-activities/iati-activity/result/indicator/period/actual/document-link/category

This is the reference page for the XML element category.

Definition

IATI Document Category Code

Rules

This element must occur at least once (within each parent element).

Attributes

@code

An IATI code defining the category of the document.

This attribute is required.

This value must be of type xsd:string.

This value must be on the DocumentCategory codelist.

Example Usage

Example usage of category of a document-link in a actual in a period in a indicator in a result element.

This examples declares the DocumentCategory code A01, using the @code attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The category element can be repeated in any document-link.

Changelog

2.03

The mandatory category element of a document-link in a actual in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

language

iati-activities/iati-activity/result/indicator/period/actual/document-link/language

This is the reference page for the XML element language.

Definition

The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.

Rules

This element may occur any number of times.

Attributes

@code

ISO 639-1 language code

This attribute is required.

This value must be of type xsd:string.

This value should be on the Language codelist.

Example Usage

Example usage of language of a document-link in a actual in a period in a indicator in a result element.

The @language attribute declares a valid code (en) from the Language codelist.

Note: This specifies the language of the document being linked to.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

In some cases, a document-link may be in multiple languages. This is expressed by repeating the language element.

Changelog

2.03

The optional language element of a document-link in a actual in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-date

iati-activities/iati-activity/result/indicator/period/actual/document-link/document-date

This is the reference page for the XML element document-date.

Definition

The date of publication of the document that is being linked to.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

This document-date element would normally be the production or published date of the relevant document to identify the specific document version.

Example Usage

Example usage of the document-date element within a document-link in a actual in a period in a indicator as part of a result element.

This examples declares an ISO date (corresponding to 5th February 2014) using the @iso-date attribute.

   <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/result_en.odt">
    <title>
     <narrative>Results Report 2013</narrative>
    </title>
    <description>
      <narrative>Report of results</narrative>
    </description>
    <category code="A01" />
    <language code="en" />
    <document-date iso-date="2014-02-05" />
   </document-link>

The document-date element should only be used once for each document-link element.

Changelog

The optional document-date element of a document-link in a actual in a period in a indicator in a result element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

crs-add

iati-activities/iati-activity/crs-add

This is the reference page for the XML element crs-add.

Definition

Additional items specific to CRS++ reporting.

Rules

This element must occur no more than once (within each parent element).

Example Usage

Example crs-add for an iati-activity.

This element is a parent for other child element.

<crs-add attached="1">
...
</crs-add>

Full example with all child elements:

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

other-flags

iati-activities/iati-activity/crs-add/other-flags

This is the reference page for the XML element other-flags.

Definition

This covers the four CRS++ columns titled: “Free standing technical cooperation”; “Programme-based approach”; “Investment project”; “Associated financing”

Rules

This element may occur any number of times.

Attributes

@code

An IATI code describing the equivalent CRS++ columns

This attribute is required.

This value must be of type xsd:string.

This value must be on the CRSAddOtherFlags codelist.

@significance

A boolean indicating whether the flag applies. If ‘false’ do not report the flag

This attribute is required.

This value must be of type xsd:boolean.

Example Usage

Example usage of other-flags of crs-add for an iati-activity.

The @code attribute declares a valid code (1) from the CRSAddOtherFlags codelist.

A @significance boolean of 1 indicates that this flag is reported.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

2.01

The element aid-type-flag has been renamed.

The associated codelist AidTypeFlag has been renamed as CRSAddOtherFlags

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

loan-terms

iati-activities/iati-activity/crs-add/loan-terms

This is the reference page for the XML element loan-terms.

Definition

Loan repayment terms and interest rates

Rules

This element must occur no more than once (within each parent element).

Attributes

@rate-1

Interest Rate. If an ODA loan with variable interest rate, report the variable rate here and the reference fixed rate as rate-2

Enter the rate without the percentage sign.

This value must be of type xsd:decimal.

@rate-2

Second Interest Rate. If an ODA loan with variable interest rate, report the variable rate as rate-1 and the reference fixed rate here

Enter the rate without the percentage sign.

This value must be of type xsd:decimal.

Example Usage

The loan-terms element acts as a container for other elements.

Example usage of loan-terms in context of crs-add element.

The @rate-1 attribute declares an example value of 4.

The @rate-2 attribute declares an example value of 3.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

repayment-type

iati-activities/iati-activity/crs-add/loan-terms/repayment-type

This is the reference page for the XML element repayment-type.

Definition

The type of loan repayment

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

An IATI codelist tabulating CRS-specified values for the type of Repayment.

This attribute is required.

This value must be of type xsd:string.

This value must be on the LoanRepaymentType codelist.

Example Usage

Example usage of repayment-type within loan-terms in context of crs-add element.

The @code attribute declares a valid code (1) from the LoanRepaymentType codelist.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

2.01

Freetext is no longer allowed within this element.

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

repayment-plan

iati-activities/iati-activity/crs-add/loan-terms/repayment-plan

This is the reference page for the XML element repayment-plan.

Definition

Number of repayments per annum.

Rules

This element must occur no more than once (within each parent element).

Attributes

@code

An IATI codelist tabulating CRS-specified values for the number of repayments per annum.

This attribute is required.

This value must be of type xsd:string.

This value must be on the LoanRepaymentPeriod codelist.

Example Usage

Example usage of repayment-plan within loan-terms in context of crs-add element.

The @code attribute declares a valid code (4) from the LoanRepaymentPeriod codelist.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

2.01

Freetext is no longer allowed within this element.

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

commitment-date

iati-activities/iati-activity/crs-add/loan-terms/commitment-date

This is the reference page for the XML element commitment-date.

Definition

The CRS++ reported commitment date

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of commitment-date within loan-terms in context of crs-add element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

repayment-first-date

iati-activities/iati-activity/crs-add/loan-terms/repayment-first-date

This is the reference page for the XML element repayment-first-date.

Definition

First Repayment Date.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of repayment-first-date within loan-terms in context of crs-add element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

repayment-final-date

iati-activities/iati-activity/crs-add/loan-terms/repayment-final-date

This is the reference page for the XML element repayment-final-date.

Definition

Final Repayment Date.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of repayment-final-date within loan-terms in context of crs-add element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

loan-status

iati-activities/iati-activity/crs-add/loan-status

This is the reference page for the XML element loan-status.

Definition

The status of loan and interest repayments for the most recently reported financial year

Rules

This element must occur no more than once (within each parent element).

Attributes

@year

CRS Reporting Year (CRS++ Column 1)

This attribute is required.

This value must be of type xsd:decimal.

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of loan-status in context of crs-add element.

This element is a parent for other child elements.

This example declares the attribute @year as 2014.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code GBP, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-activity element.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

interest-received

iati-activities/iati-activity/crs-add/loan-status/interest-received

This is the reference page for the XML element interest-received.

Definition

Interest received during the reporting year

Rules

The text in this element must be of type xsd:decimal.

This element must occur no more than once (within each parent element).

Example Usage

Example usage of interest-received within loan-status in context of crs-add element.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

principal-outstanding

iati-activities/iati-activity/crs-add/loan-status/principal-outstanding

This is the reference page for the XML element principal-outstanding.

Definition

The amount of principal owed on the loan at the end of the reporting year.

Rules

The text in this element must be of type xsd:decimal.

This element must occur no more than once (within each parent element).

Example Usage

Example usage of principle-outstanding within loan-status in context of crs-add element.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

principal-arrears

iati-activities/iati-activity/crs-add/loan-status/principal-arrears

This is the reference page for the XML element principal-arrears.

Definition

Arrears of principal at the end of the year. Included in principal-outstanding

Rules

The text in this element must be of type xsd:decimal.

This element must occur no more than once (within each parent element).

Example Usage

Example usage of principle-arrears within loan-status in context of crs-add element.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

interest-arrears

iati-activities/iati-activity/crs-add/loan-status/interest-arrears

This is the reference page for the XML element interest-arrears.

Definition

Arrears of interest at the end of the year

Rules

The text in this element must be of type xsd:decimal.

This element must occur no more than once (within each parent element).

Example Usage

Example usage of interest-arrears within loan-status in context of crs-add element.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

1.03

New in 1.03

Added the optional crs-add element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

channel-code

iati-activities/iati-activity/crs-add/channel-code

This is the reference page for the XML element channel-code.

Definition

The CRS channel code for this activity. This should only be used for reporting to CRS. The code list contains both organisation types and names of organisations. For non-CRS purposes these should be reported using the participating-org element.

Rules

The text in this element must be of type xsd:string.

This element must occur no more than once (within each parent element).

Example Usage

Example usage of channel-code of crs-add for an iati-activity.

The contents of the element contain a valid code (21039) from the CRSChannelCode codelist.

  <crs-add>
   <other-flags code="1" significance="1" />
   <loan-terms rate-1="4" rate-2="3">
    <repayment-type code="1" />
    <repayment-plan code="4" />
    <commitment-date iso-date="2013-09-01"/>
    <repayment-first-date iso-date="2014-01-01" />
    <repayment-final-date iso-date="2020-12-31" />
   </loan-terms>
   <loan-status year="2014" currency="GBP" value-date="2013-05-24">
     <interest-received>200000</interest-received>
     <principal-outstanding>1500000</principal-outstanding>
     <principal-arrears>0</principal-arrears>
     <interest-arrears>0</interest-arrears>
   </loan-status>
   <channel-code>21039</channel-code>
  </crs-add>

Changelog

2.02

The optional channel-code element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

fss

iati-activities/iati-activity/fss

This is the reference page for the XML element fss.

Definition

This section allows entry of data required for the OECD DAC Forward Spending Survey at an activity level.

Rules

This element must occur no more than once (within each parent element).

Attributes

@extraction-date

The exact date when the information was collected or extracted from donors’ aid management systems.

This attribute is required.

This value must be of type xsd:date.

@priority

True if the partner country is a priority partner country.

This value must be of type xsd:boolean.

@phaseout-year

If there are plans to phase out operations from the partner country, this column shows the projected year of last disbursements.

This value must be of type xsd:decimal.

Example Usage

Example of fss of an iati-activity.

An example date is declared in the @extraction-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares the attribute @phaseout-year as 2016.

A @priority boolean 1 declares that this is a partner country priority.

  <fss extraction-date="2014-05-06" priority="1" phaseout-year="2016">
   <forecast year="2014" value-date="2013-07-03" currency="GBP">10000</forecast>
  </fss>

Changelog

1.03

New in 1.03

Added the optional fss element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

forecast

iati-activities/iati-activity/fss/forecast

This is the reference page for the XML element forecast.

Definition

A container to hold separate forecasts for each of the years specified Text() holds the forecast value for each year.

Rules

The text in this element must be of type xsd:decimal.

This element may occur any number of times.

Attributes

@year

The calendar year that the forward spend covers

This attribute is required.

This value must be of type xsd:decimal.

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This value must be of type xsd:date.

Example Usage

Example of forecast for the fss of an iati-activity.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares the attribute @year as 2014.

This example declares a Currency code GBP, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-activity element.

  <fss extraction-date="2014-05-06" priority="1" phaseout-year="2016">
   <forecast year="2014" value-date="2013-07-03" currency="GBP">10000</forecast>
  </fss>

Note: multiple forecasts are expressed by repeating the forecast element.

Changelog

1.03

New in 1.03

Added the optional fss element and its child elements

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Organisation Standard

This section details the IATI Organisation standard. It contains the following main areas:

• Overview - an introduction to key aspects of the organisation standard.

• Elements - details on each and every element and attribute of the standard, including relevant code lists, rules and example usage.

Additionally:

• A summary table provides an overview of all aspects of the organisation standard.

• An example XML file is provided, which is also used throughout the documentation.

Definition

The IATI organisational standard is used to describe one or more organisations involved in any stage development cooperation (funding, implementing etc.).

It is designed to report forward-looking aggregate budget information for the reported organisations, and planned future budgets to recipient institutions or countries.

The IATI organisational standard is also used to report links to relevant public documents.

Organisations publish this data in an organisation file. It is expected that every organisation publishing IATI data should include one organisation file, which is updated at least annually.

Considerations

When declaring information using the IATI organisation standard the following should be considered:

• Who are the Organisations involved?

• How are the Organisations unquiely identified?

• What are the organisation’s planned future annual total budgets?

• What are the organisation’s planned future budgets for aid given to recipient countries?

• What are the organisation’s planned future budgets for aid given to recipient organisations?

• Where are the organisation’s official public documents?

Contents

Overview

These overview pages provide initial guidance and information about the IATI organisation standard.

Further guidance, examples and specific details can be found in the reference section.

Organisation Standard Summary Table

Section	Item	Description	Type	Codelist	XML	Occur	Rules
iati-organisations		Top-level list of one or more IATI organisation records.			iati-organisations
	version	A number indicating the IATI specification version in use. This is mandatory and must be a valid version.	xsd:string	Version	iati-organisations/@version	1..1
	generated-datetime	A date/time stamp for when this file was generated. This is not necessarily the last-updated date for the individual activity records in it. Use of this attribute is highly recommended, to allow recipients to know when a file has been updated.	xsd:dateTime		iati-organisations/@generated-datetime	0..1
iati-organisation		Top-level element for a single IATI organisation report.			iati-organisations/iati-organisation	1..*
	last-updated-datetime	The last date/time that the data for this specific organisation was updated. This date must change whenever the value of any field changes.	xsd:dateTime		iati-organisations/iati-organisation/@last-updated-datetime	0..1	@last-updated-datetime must not be more recent than the current date
	xml:lang	A code specifying the default language of text in this organisation. It is recommended that wherever possible only codes from ISO 639-1 are used. If this is not declared then the xml:lang attribute MUST be specified for each narrative element.		Language	iati-organisations/iati-organisation/@xml:lang	0..1	@xml:lang must exist, otherwise all lang must exist.
	default-currency	Default ISO 4217 currency code for all financial values in this activity report. If this is not declared then the currency attribute MUST be specified for all monetary values.	xsd:string	Currency	iati-organisations/iati-organisation/@default-currency	0..1	@default-currency must exist, otherwise all currency must exist.
organisation-identifier		Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}.			iati-organisations/iati-organisation/organisation-identifier	1..1	organisation-identifier should match the regex [^\/\&\|\?]+
name		The human-readable name of the organisation.			iati-organisations/iati-organisation/name	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/name/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/name/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/name/narrative/@xml:lang	0..1
reporting-org		The organisation issuing the report. May be a primary source (reporting on its own activity as donor, implementing agency, etc) or a secondary source (reporting on the activities of another organisation). Specifying the @ref attribute is mandatory. May contain the organisation name as content. All activities in an activity xml file must contain the same @ref AND this @ref must be the same as the iati-identifier recorded in the registry publisher record of the account under which this file is published.			iati-organisations/iati-organisation/reporting-org	1..1
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}.	xsd:string		iati-organisations/iati-organisation/reporting-org/@ref	1..1	reporting-org/@ref should match the regex [^\/\&\|\?]+
	type	The type of organisation issuing the report. See IATI codelist for values.	xsd:string	Organisation Type	iati-organisations/iati-organisation/reporting-org/@type	1..1
	secondary-reporter	A flag indicating that the reporting organisation of this activity is acting as a secondary reporter. A secondary reporter is one that reproduces data on the activities of an organisation for which it is not directly responsible. This does not include a publisher officially assigned as a proxy to report on behalf of another.	xsd:boolean		iati-organisations/iati-organisation/reporting-org/@secondary-reporter	0..1
	narrative	The name of the organisation. May be repeated for different languages.			iati-organisations/iati-organisation/reporting-org/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/reporting-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/reporting-org/narrative/@xml:lang	0..1
total-budget		The total-budget element allows for the reporting of the organisation’s own budget. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three years is reported. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.			iati-organisations/iati-organisation/total-budget	0..*
	status	The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.	xsd:string	Budget Status	iati-organisations/iati-organisation/total-budget/@status	0..1
	period-start	The start of the budget period.			iati-organisations/iati-organisation/total-budget/period-start	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/total-budget/period-start/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	period-end	The end of the period (which must not be greater than one year)			iati-organisations/iati-organisation/total-budget/period-end	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/total-budget/period-end/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	value	The total value of the organisation’s aid budget for this period.			iati-organisations/iati-organisation/total-budget/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-organisations/iati-organisation/total-budget/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/total-budget/value/@value-date	1..1
	budget-line	A breakdown of the total budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent total-budget element. The sum of budget-line values does not have to equal the value given in the parent element.			iati-organisations/iati-organisation/total-budget/budget-line	0..*
	ref	An internal reference for this budget line taken from the reporting organisation’s own system. Optional.	xsd:string		iati-organisations/iati-organisation/total-budget/budget-line/@ref	0..1
	value	The budget sub-total. The definition of the sub-division is determined by iati-organisation/total-budget/budget-line/narrative			iati-organisations/iati-organisation/total-budget/budget-line/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string		iati-organisations/iati-organisation/total-budget/budget-line/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/total-budget/budget-line/value/@value-date	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/total-budget/budget-line/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/total-budget/budget-line/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/total-budget/budget-line/narrative/@xml:lang	0..1
recipient-org-budget		The recipient-org-budget element allows for the reporting of forward looking budgets for each institution which receives core funding from the reporting organisation. The recommendation is that, where and when possible, annual planned budgets for each recipient institution for each of the next three financial years are reported. This is primarily applicable to donors but any provider of core funding is expected to use it. Earmarked budgets should be reported at activity-level through the Activity Standard. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.			iati-organisations/iati-organisation/recipient-org-budget	0..*
	status	The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.	xsd:string	Budget Status	iati-organisations/iati-organisation/recipient-org-budget/@status	0..1
	recipient-org	The organisation that will receive the funds.			iati-organisations/iati-organisation/recipient-org-budget/recipient-org	1..1
	ref	Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.	xsd:string		iati-organisations/iati-organisation/recipient-org-budget/recipient-org/@ref	0..1
	narrative	The name of the organisation. This can be repeated in multiple languages.			iati-organisations/iati-organisation/recipient-org-budget/recipient-org/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/recipient-org-budget/recipient-org/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/recipient-org-budget/recipient-org/narrative/@xml:lang	0..1
	period-start	The start of the budget period.			iati-organisations/iati-organisation/recipient-org-budget/period-start	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/recipient-org-budget/period-start/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	period-end	The end of the period (which must not be greater than one year)			iati-organisations/iati-organisation/recipient-org-budget/period-end	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/recipient-org-budget/period-end/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	value	The total value of the money budgeted to be disbursed to the specified recipient organisation during this time period.			iati-organisations/iati-organisation/recipient-org-budget/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-organisations/iati-organisation/recipient-org-budget/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/recipient-org-budget/value/@value-date	1..1
	budget-line	A breakdown of the recipient organisation’s budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent recipient-org-budget element. The sum of budget-line values does not have to equal the value given in the parent element.			iati-organisations/iati-organisation/recipient-org-budget/budget-line	0..*
	ref	An internal reference for this budget line taken from the reporting organisation’s own system. Optional.	xsd:string		iati-organisations/iati-organisation/recipient-org-budget/budget-line/@ref	0..1
	value	The budget sub-total. The definition of the sub-division is determined by iati-organisation/recipient-org-budget/budget-line/narrative			iati-organisations/iati-organisation/recipient-org-budget/budget-line/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-organisations/iati-organisation/recipient-org-budget/budget-line/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/recipient-org-budget/budget-line/value/@value-date	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/recipient-org-budget/budget-line/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/recipient-org-budget/budget-line/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/recipient-org-budget/budget-line/narrative/@xml:lang	0..1
recipient-region-budget		The recipient-region-budget element allows for the reporting of forward looking budgets where the organisation maintains region-wide, rather than or in addition to country-specific budgets. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three financial years is reported for each recipient region. This must NOT include an aggregation of budgets reported in the recipient-country-budget element. It is strongly recommended that publishers report to existing defined regions wherever possible. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.			iati-organisations/iati-organisation/recipient-region-budget	0..*
	status	The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.	xsd:string	Budget Status	iati-organisations/iati-organisation/recipient-region-budget/@status	0..1
	recipient-region	The supranational geographic region where funds have been allocated.			iati-organisations/iati-organisation/recipient-region-budget/recipient-region	1..1
	vocabulary	An IATI code for the vocabulary from which the region code is drawn. If it is not present, code 1 (‘OECD DAC’) is assumed.	xsd:string	Region Vocabulary	iati-organisations/iati-organisation/recipient-region-budget/recipient-region/@vocabulary	0..1
	vocabulary-uri	The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.	xsd:anyURI		iati-organisations/iati-organisation/recipient-region-budget/recipient-region/@vocabulary-uri	0..1
	code	Either an OECD DAC, UN region code or (if code ‘99’ Reporting organisation is selected for recipient-region/@vocabulary) a code from your internal vocabulary. The codelist is determined by vocabulary attribute. The value in recipient-region/@code should appear within the Region codelist, if the vocabulary code 1 (‘OECD DAC’) is used.	xsd:string	(Region)	iati-organisations/iati-organisation/recipient-region-budget/recipient-region/@code	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/recipient-region-budget/recipient-region/narrative	0..*
			xsd:string		iati-organisations/iati-organisation/recipient-region-budget/recipient-region/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/recipient-region-budget/recipient-region/narrative/@xml:lang	0..1
	period-start	The start of the budget period.			iati-organisations/iati-organisation/recipient-region-budget/period-start	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/recipient-region-budget/period-start/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	period-end	The end of the period (which must not be greater than one year)			iati-organisations/iati-organisation/recipient-region-budget/period-end	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/recipient-region-budget/period-end/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	value	The total value of the money budgeted to be disbursed to the specified region during this time period. This element is required.			iati-organisations/iati-organisation/recipient-region-budget/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-organisations/iati-organisation/recipient-region-budget/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/recipient-region-budget/value/@value-date	1..1
	budget-line	A breakdown of the recipient region’s budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent recipient-region-budget element. The sum of budget-line values does not have to equal the value given in the parent element.			iati-organisations/iati-organisation/recipient-region-budget/budget-line	0..*
	ref	An internal reference for this budget line taken from the reporting organisation’s own system. Optional.	xsd:string		iati-organisations/iati-organisation/recipient-region-budget/budget-line/@ref	0..1
	value	The budget sub-total. The definition of the sub-division is determined by iati-organisation/recipient-region-budget/budget-line/narrative			iati-organisations/iati-organisation/recipient-region-budget/budget-line/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-organisations/iati-organisation/recipient-region-budget/budget-line/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/recipient-region-budget/budget-line/value/@value-date	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/recipient-region-budget/budget-line/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/recipient-region-budget/budget-line/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/recipient-region-budget/budget-line/narrative/@xml:lang	0..1
recipient-country-budget		The recipient-country-budget element allows for the reporting of forward looking budgets for each country in which the organisation operates. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three financial years is reported for each recipient country. It is strongly recommended that the start and end of the reported financial years match those of the recipient country’s budgetary/planning cycle. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.			iati-organisations/iati-organisation/recipient-country-budget	0..*
	status	The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.	xsd:string	Budget Status	iati-organisations/iati-organisation/recipient-country-budget/@status	0..1
	recipient-country	The recipient country.			iati-organisations/iati-organisation/recipient-country-budget/recipient-country	1..1
	code	ISO 3166-1 alpha-2 code for the country.	xsd:string	Country	iati-organisations/iati-organisation/recipient-country-budget/recipient-country/@code	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/recipient-country-budget/recipient-country/narrative	0..*
			xsd:string		iati-organisations/iati-organisation/recipient-country-budget/recipient-country/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/recipient-country-budget/recipient-country/narrative/@xml:lang	0..1
	period-start	The start of the budget period.			iati-organisations/iati-organisation/recipient-country-budget/period-start	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/recipient-country-budget/period-start/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	period-end	The end of the period (which must not be greater than one year)			iati-organisations/iati-organisation/recipient-country-budget/period-end	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/recipient-country-budget/period-end/@iso-date	1..1	period-start/@iso-date must be before or the same as period-end/@iso-date The time between period-start/@iso-date and period-end/@iso-date must not be over a year
	value	The total value of the money budgeted to be disbursed to the specified country during this time period. This element is required.			iati-organisations/iati-organisation/recipient-country-budget/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-organisations/iati-organisation/recipient-country-budget/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/recipient-country-budget/value/@value-date	1..1
	budget-line	A breakdown of the recipient country’s budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent recipient-country-budget element. The sum of budget-line values does not have to equal the value given in the parent element.			iati-organisations/iati-organisation/recipient-country-budget/budget-line	0..*
	ref	An internal reference for this budget line taken from the reporting organisation’s own system. Optional.	xsd:string		iati-organisations/iati-organisation/recipient-country-budget/budget-line/@ref	0..1
	value	The budget sub-total. The definition of the sub-division is determined by iati-organisation/recipient-country-budget/budget-line/narrative			iati-organisations/iati-organisation/recipient-country-budget/budget-line/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string	Currency	iati-organisations/iati-organisation/recipient-country-budget/budget-line/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/recipient-country-budget/budget-line/value/@value-date	1..1	The budget-line/value/@value-date must be between the period-start/@iso-date and period-end/@iso-date dates.
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/recipient-country-budget/budget-line/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/recipient-country-budget/budget-line/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/recipient-country-budget/budget-line/narrative/@xml:lang	0..1
total-expenditure		The total-expenditure element allows for the reporting of the organisation’s international development expenditure. The recommendation is that, where and when possible, the organisation’s total expenditure for each of the past three years is reported. The expense line allows publishers to record further breakdown.			iati-organisations/iati-organisation/total-expenditure	0..*
	period-start	The start of the budget period.			iati-organisations/iati-organisation/total-expenditure/period-start	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/total-expenditure/period-start/@iso-date	1..1	The time between period-start/@iso-date and period-end/@iso-date must not be over a year period-start/@iso-date must be before or the same as period-end/@iso-date
	period-end	The end of the period (which must not be greater than one year)			iati-organisations/iati-organisation/total-expenditure/period-end	1..1
	iso-date		xsd:date		iati-organisations/iati-organisation/total-expenditure/period-end/@iso-date	1..1	The time between period-start/@iso-date and period-end/@iso-date must not be over a year period-start/@iso-date must be before or the same as period-end/@iso-date
	value	The total value of the organisation’s aid expenditure for this period.			iati-organisations/iati-organisation/total-expenditure/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string		iati-organisations/iati-organisation/total-expenditure/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/total-expenditure/value/@value-date	1..1
	expense-line	A breakdown of the total expenditure into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent total-expenditure element. The sum of expenditure-line values does not have to equal the value given in the parent element.			iati-organisations/iati-organisation/total-expenditure/expense-line	0..*
	ref	An internal reference for this expenditure line taken from the reporting organisation’s own system. Optional.	xsd:string		iati-organisations/iati-organisation/total-expenditure/expense-line/@ref	0..1
	value	The expenditure sub-total. The definition of the sub-division is determined by iati-organisation/total-expenditure/expenditure-line/narrative			iati-organisations/iati-organisation/total-expenditure/expense-line/value	1..1
	currency	A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.	xsd:string		iati-organisations/iati-organisation/total-expenditure/expense-line/value/@currency	0..1
	value-date	The date to be used for determining the exchange rate for currency conversions.	xsd:date		iati-organisations/iati-organisation/total-expenditure/expense-line/value/@value-date	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/total-expenditure/expense-line/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/total-expenditure/expense-line/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/total-expenditure/expense-line/narrative/@xml:lang	0..1
document-link		A link to an online, publicly accessible web page or document.			iati-organisations/iati-organisation/document-link	0..*
	url	The target URL of the external document, e.g. “http://www.example.org/doc.odt”.	xsd:anyURI		iati-organisations/iati-organisation/document-link/@url	1..1
	format	An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.	xsd:string	File Format	iati-organisations/iati-organisation/document-link/@format	1..1
	recipient-country	The recipient country that is the focus of the document. May be repeated for multiple countries.			iati-organisations/iati-organisation/document-link/recipient-country	0..*
	code	ISO 3166-1 alpha-2 code for the country.	xsd:string	Country	iati-organisations/iati-organisation/document-link/recipient-country/@code	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/document-link/recipient-country/narrative	0..*
			xsd:string		iati-organisations/iati-organisation/document-link/recipient-country/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/document-link/recipient-country/narrative/@xml:lang	0..1
	title	A short, human-readable title.			iati-organisations/iati-organisation/document-link/title	1..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/document-link/title/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/document-link/title/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/document-link/title/narrative/@xml:lang	0..1
	description	A description of the document contents, or guidance on where to access the relevant information in the document.			iati-organisations/iati-organisation/document-link/description	0..1
	narrative	The free text name or description of the item being described. This can be repeated in multiple languages.			iati-organisations/iati-organisation/document-link/description/narrative	1..*
			xsd:string		iati-organisations/iati-organisation/document-link/description/narrative/text()
	xml:lang	A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.		Language	iati-organisations/iati-organisation/document-link/description/narrative/@xml:lang	0..1
	category	IATI Document Category Code			iati-organisations/iati-organisation/document-link/category	1..*
	code	An IATI code defining the category of the document.	xsd:string	Document Category	iati-organisations/iati-organisation/document-link/category/@code	1..1
	language	The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.			iati-organisations/iati-organisation/document-link/language	0..*
	code	ISO 639-1 language code	xsd:string	Language	iati-organisations/iati-organisation/document-link/language/@code	1..1
	document-date	The date of publication of the document that is being linked to.			iati-organisations/iati-organisation/document-link/document-date	0..1
	iso-date		xsd:date		iati-organisations/iati-organisation/document-link/document-date/@iso-date	1..1

International Aid Transparency Initiative: Organisation-Information Schema

Release 2.03, 2018-02-19

NOTE: the xml.xsd and iati-common.xsd schemas must be in the
same directory as this one.

This W3C XML Schema defines an XML document type for information
about an aid organisation, following the standard published at
http://iatistandard.org

This document type may be extended with additional elements and
attributes, but they must belong to an explicit XML namespace.

Organisation file

Definition

The organisation file contains the data defined by the IATI organisation standard.

It is an XML file, containing the relevant IATI organisation standard fields for the publishing organisation.

The IATI organisation standard allows publishers to report on information for multiple organisations: a government agency may report on behalf of other agencies; an INGO may report on behalf of its national associates; a private company may report on behalf of its subsidiaries.

Considerations

When using the IATI organisation standard to produce the organisation file, the following should be considered:

• An IATI publisher should publish one organisation file.

• An organisation file should contain at least one iati-organisation

• It should be updated at least annually.

• It must be well-formed XML.

• It must validate against the relevant version of the IATI organisation schema

• The organisation file must have iati-organisations as the root element - to contain all other elements.

• The generated-datetime attribute of iati-organisations - a date/time stamp for when this activity-file was generated - is highly recommended.

• A link to the organisation file should be published on the IATI Registry.

• Ideally, this link would be to an organisation file on the publisher website or open data portal. However, third party tools are available to generate and host files on behalf of publishers.

• When creating the organisation file it is recommended to avoid spaces and non-ascii characters in file names and urls. For example:

  • iatiorganisation.xml is preferable to IATI Organisation.xml

  • http://example.org/files/iatidata/iatiorganisation.xml is preferable to http://example.org/files/iati data/IATI Organisation.xml.

2.01 Considerations

In version 2.01, the following must also be considered:

• It is recommended that a single organisation-file does not exceed 40MB in file size.

• The order of the elements presented in an organisation-file must follow the order set out in the schema.

• The version of the IATI standard being used must be declared via the version attribute of the iati-organisations element. This must be a valid value on the Version codelist.

Further Guidance

• For well-formed XML tests, see the W3C XML Validator

• The IATI Validator tests data against the relevant version of the IATI organisation schema.

IATI Organisation

Definition

Within the IATI organisation standard. the iati-organisation is the building block to describe organisations.

An iati-organisation represents a distinct grouping of information that reports various facts about an organisation.

For each iati-organisation described, the following are expected as a minium:

• iati-identifier is the unique reference for the organisation.

• name - a human-readable name of the organisation.

Considerations

When using the IATI organisation standard to declare an iati-organisation, the following should be considered:

• Every iati-organisation must use a globally unique organisation-identifier

• The organisation-identifier should have no leading or trailing whitespace.

• It is recommended that no forward slashes (/) or spaces should be contained within the organisation-identifier.

• It is recommended to avoid spaces and non-ascii characters. For example:

  • AA-AAA-123456789 is preferable to AA-AAA 123456789.

• A default language and @default-currency can be set for any iati-organisation. This can be overridden in subsequent elements.

• The @last-updated-datetime date must change whenever the value of any field within the associated iati-organisation are updated.

• The name can be repeated for different languages.

• The free-text instance of name should avoid use of text in CAPITALS, where possible.

2.01 Considerations

In version 2.01, the following must also be considered:

• The iati-identifier in the Organisation standard has been renamed to organisation-identifier

• A reporting-org identifier must start with a value published on the OrganisationRegistrationAgency codelist.

• Any freetext name for an organisation, must be included in the child narrative element, which can be repeated for different languages.

Further Guidance

Please also consider and refer to the Organisation Identifiers guidance when constructing an appropriate identifier.

Type of Organisations

Definition

Within the IATI organisation standard three types of organisations can be declared:

• reporting-org - the organisation publishing the data within the organisation file.

• iati-organisation - the organisation that the data is about

• recipient-org - the organisation in receipt of budgets specified in recipient-org-budget

Considerations

When using the IATI organisation standard to declare organisations, the following should be considered:

• In many cases, an organisation file will contain information from the perspective of a single iati-organisation. Most commonly, this will be the same as the reporting-org

• Multiple iati-organisation can be described in a single organisation file.

• reporting-org and iati-organisation should include reference to their associated unique iati-identifier

• For reporting-org, inclusion of the OrganisationType code is recommended.

• An iati-organisation should include a name element - free text title of the organisation

• Single or multiple recipient-org entries can be recorded.

• For each recipient-org multiple forward looking recipient-org-budget can be recorded.

2.01 Considerations

In version 2.01, the following must also be considered:

• A reporting-org is a mandatory element

• A reporting-org identifier must start with a value published on the OrganisationRegistrationAgency codelist.

• Any freetext name for an organisation, must be included in the child narrative element, which can be repeated for different languages.

Further Guidance

Please also consider and refer to the Organisation Identifiers guidance when constructing an appropriate identifier.

Budgets

Definition

Within the IATI organisation standard three types of budgets can be declared.

These all relate to the specific iati-organisation being described:

• total-budget - total annual planned budget of the iati-organisation.

• recipient-org-budget - budget for disbursements to another organisation.

• recipient-country-budget - budget for each country in which the iati-organisation operates.

Considerations

When using the IATI organisation standard to declare budgets, the following should be considered:

• It is recommended that budgets in the IATI organisation standard are forward-looking.

• It is recommended, where possible, that budgets are presented for the next three financial years.

• When presenting multiple budgets, then the relevant budget element should be repeated accordingly.

• It is possible to report periods other than financial years, but this is not recommended.

• Financial periods are presented using the period-start and period-end dates.

• It is expected that financial years appropriate to the relevant iati-organisation would be described.

• It is strongly recommended that the period-start and period-end of the financial years described for any recipient-country-budget match the budgetary/planning cycle of the recipient-country.

• It is possible to report budget values in multiple @currency.

• The @default-currency can be set in the iati-organisation element. Should subsequent budgets be in the same @currency then there is no need to restate.

• When declaring a value-date for any budget, this date must be in the past.

2.01 Considerations

In version 2.01, the following must also be considered:

• The budget-line element was introduced.

Documents

Definition

Within the IATI organisation standard any number of links to relevant documents can be declared using:

• document-link - a categorized link to an external document.

Considerations

When using the IATI organisation standard to declare documents, the following should be considered:

• In the IATI organisation standard, documents that relate to the organisation/agency would be linked to. iati-activity specific documents are published via the IATI activity standard.

• All document-link should be presented in the form of URLs (eg: http://example.org/exampledocument.odt)

• The URL must resolve to a valid internet address that provides direct access to the document in question.

• Attention should be paid by the publisher to any links that become obsolete.

• If the documents are in different languages, which are available at different URLs, then repeat the document-link element

• If the same document has multiple languages within it, then repeat the language element.

• For every document presented either a title or category is expected (or both).

• The title element can be repeated for different languages, regardless of the language of the actual document.

• The free-text instances of title should avoid use of text in CAPITALS, where possible.

• For document category in the IATI organisation standard, it is expected that the DocumentCategory code would be have the B prefix.

• DocumentCategory code A documents should only be reported if there is a good reason for the document not to be linked to a specific iati-activity.

• Using the @format attribute helps inform what to expect from the document.

• Use of the @format must be accompanied by a code on the FileFormat codelist.

2.01 Considerations

In version 2.01, the following must also be considered:

• In version 2.01 of the IATI Standard, the schema data type used for some data fields where a URL is expected is now set as xsd:anyURI.

• Any freetext title must be included in the child narrative element, which can be repeated for different languages.

Example Usage XML

Definition

This page presents example usage XML for the IATI organisation standard.

Considerations

This is a example usage XML and not intended to reflect any real organisations or entities.

Extracts from this example are used throughout this documentation.

Comments markup is optional and intended to supplement the documentation:

  <!--organisation-identifier ends-->

  <!--name starts-->

Download Example Usage File

The example usage XML file can be downloaded.

Example Usage File (in full)

Full XML example usage of the IATI organisation standard:

<iati-organisations generated-datetime="2014-09-10T07:15:37Z" version="2.03">

 <!--iati-organisation starts-->
 <iati-organisation default-currency="EUR" last-updated-datetime="2014-09-10T07:15:37Z" xml:lang="en">

  <!--organisation-identifier starts-->
  <organisation-identifier>AA-AAA-123456789</organisation-identifier>
  <!--organisation-identifier ends-->

  <!--name starts-->
  <name>
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </name>
  <!--name ends-->

  <!--reporting-org starts-->
  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>
  <!--reporting-org ends-->

  <!--total-budget starts-->
  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>
  <!--total-budget ends-->

  <!--recipient-org-budget starts-->
  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>
  <!--recipient-org-budget ends-->

  <!--recipient-region-budget starts-->
  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>
  <!--recipient-region-budget ends-->

  <!--recipient-country-budget starts-->
  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>
  <!--recipient-country-budget ends-->

  <!--total-expenditure starts-->
  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>
 <!--total-expenditure ends-->

 <!--document-link starts-->
 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>
 <!--document-link ends-->

 <!--document-link-title starts-->
 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
    <narrative>Annual Report 2013</narrative>
    <narrative xml:lang="fr">Rapport annuel 2013</narrative>
   </title>
   <category code="B01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
  </document-link>
  <!--document-link-title ends-->

  <!--document-link-lang starts-->
  <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_fr.odt">
   <title>
    <narrative>Annual Report 2013</narrative>
    <narrative xml:lang="fr">Rapport annuel 2013</narrative>
   </title>
   <category code="B01" />
   <language code="fr" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
  </document-link>
  <!--document-link-lang ends-->

  <!--multi-cat-document-link starts-->
  <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
   <title>
    <narrative>Annual Report 2013</narrative>
    <narrative xml:lang="fr">Rapport annuel 2013</narrative>
   </title>
   <description>
     <narrative>Description of the document</narrative>
   </description>
   <category code="B01" />
   <category code="B02" />
   <category code="B03" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
  </document-link>
  <!--multi-cat-document-link ends-->

  <!--multi-country-document-link starts-->
  <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
   <title>
    <narrative>Country Report 2013</narrative>
    <narrative xml:lang="fr">Rapport Pays 2013</narrative>
   </title>
   <description>
     <narrative>Description of the document</narrative>
   </description>
   <category code="B01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
   <recipient-country code="AX" />
   <recipient-country code="AL" />
  </document-link>
  <!--multi-country-document-link ends-->

 </iati-organisation>
 <!--iati-organisation ends-->

</iati-organisations>
<!--iati-organisations ends-->

Further guidance

• IATI organisation standard - reference pages

Elements

This section contains detailed documentation for each XML element in the IATI Organisation Standard.

For each element, the relevant attributes are listed, with subsequent child elements listed.

For each element, any rules for usage are declared.

Additionally, XML examples are provided for each element, with the relevant markup highlighted.

Further information

All code examples are derived from a single source: Example Usage XML.

For an single page table of all elements see Organisation Standard Summary Table.

For more general material see also the Overview section.

Contents

iati-organisations

iati-organisations

This is the reference page for the XML element iati-organisations.

Definition

Top-level list of one or more IATI organisation records.

Attributes

@version

A number indicating the IATI specification version in use. This is mandatory and must be a valid version.

This attribute is required.

This value must be of type xsd:string.

This value must be on the Version codelist.

@generated-datetime

A date/time stamp for when this file was generated. This is not necessarily the last-updated date for the individual activity records in it. Use of this attribute is highly recommended, to allow recipients to know when a file has been updated.

This value must be of type xsd:dateTime.

Example Usage

Example usage of iati-organisations.

This element is a parent for other all other elements of the IATI Organisation Standard.

This example provides a dateTime of 2014-09-10T07:15:37Z for the @generated-datetime attribute.

A dateTime in UTC time is indicated by adding a Z behind the time

This example dateTime format conforms to the xsd:dateTime standard.

The @version attribute declares a valid code (2.01) from the Version codelist.

<iati-organisations generated-datetime="2014-09-10T07:15:37Z" version="2.03">

The iati-organisation element acts as a container for other sub-elements. It is closed as follows:

</iati-organisations>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

iati-organisation

iati-organisations/iati-organisation

This is the reference page for the XML element iati-organisation.

Definition

Top-level element for a single IATI organisation report.

Rules

This element must occur at least once (within each parent element).

Attributes

@last-updated-datetime

The last date/time that the data for this specific organisation was updated. This date must change whenever the value of any field changes.

This value must be of type xsd:dateTime.

@last-updated-datetime must not be more recent than the current date

@xml:lang

A code specifying the default language of text in this organisation. It is recommended that wherever possible only codes from ISO 639-1 are used. If this is not declared then the xml:lang attribute MUST be specified for each narrative element.

This value should be on the Language codelist.

@xml:lang must exist, otherwise all lang must exist.

@default-currency

Default ISO 4217 currency code for all financial values in this activity report. If this is not declared then the currency attribute MUST be specified for all monetary values.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@default-currency must exist, otherwise all currency must exist.

Example Usage

Example usage of iati-organisation.

This element is a parent for other child elements.

This example provides a dateTime of 2014-09-10T07:15:37Z for the @last-updated-datetime attribute.

A dateTime in UTC time is indicated by adding a Z behind the time

This example dateTime format conforms to the xsd:dateTime standard.

The @xml:lang attribute declares a valid code (en) from the Language codelist.

The @default-currency attribute declares a valid code (EUR) from the Currency codelist.

 <iati-organisation default-currency="EUR" last-updated-datetime="2014-09-10T07:15:37Z" xml:lang="en">

The iati-organisation element acts as a container for other sub-elements. It is closed as follows:

 </iati-organisation>

Changelog

2.01

The version attribute was removed

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

organisation-identifier

iati-organisations/iati-organisation/organisation-identifier

This is the reference page for the XML element organisation-identifier.

Definition

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}.

Rules

This element must occur once and only once (within each parent element).

organisation-identifier should match the regex [^\/\&\|\?]+

Example Usage

Example organisation-identifier of an iati-organisation.

  <organisation-identifier>AA-AAA-123456789</organisation-identifier>

Changelog

2.03

The definition of the organisation-identifier element was updated.

2.01

The iati-identifier element was renamed as organisation-identifier

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

name

iati-organisations/iati-organisation/name

This is the reference page for the XML element name.

Definition

The human-readable name of the organisation.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example of name of an iati-organisation.

  <name>
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </name>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/name/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the name element.

  <name>
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </name>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute:

  <name>
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </name>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

reporting-org

iati-organisations/iati-organisation/reporting-org

This is the reference page for the XML element reporting-org.

Definition

The organisation issuing the report. May be a primary source (reporting on its own activity as donor, implementing agency, etc) or a secondary source (reporting on the activities of another organisation).

Specifying the @ref attribute is mandatory. May contain the organisation name as content.

All activities in an activity xml file must contain the same @ref AND this @ref must be the same as the iati-identifier recorded in the registry publisher record of the account under which this file is published.

Rules

This element must occur once and only once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}.

This attribute is required.

This value must be of type xsd:string.

reporting-org/@ref should match the regex [^\/\&\|\?]+

@type

The type of organisation issuing the report. See IATI codelist for values.

This attribute is required.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

@secondary-reporter

A flag indicating that the reporting organisation of this activity is acting as a secondary reporter. A secondary reporter is one that reproduces data on the activities of an organisation for which it is not directly responsible. This does not include a publisher officially assigned as a proxy to report on behalf of another.

This value must be of type xsd:boolean.

Example Usage

Example reporting-org for an iati-organisation.

An example organisation @ref of AA-AAA-123456789 is declared.

The @type attribute declares a valid code (40) from the OrganisationType codelist.

The optional @secondary-reporter boolean is included, for illustration.

  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>

Changelog

2.03

The definition of the @ref attributed was updated.

The definition of the @secondary-reporter attributed was updated.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

1.04

The @secondary-reporter attribute was introduced in 1.04.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/reporting-org/narrative

This is the reference page for the XML element narrative.

Definition

The name of the organisation. May be repeated for different languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the reporting-org element.

  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute:

  <reporting-org ref="AA-AAA-123456789" type="40" secondary-reporter="0">
   <narrative>Organisation name</narrative>
   <narrative xml:lang="fr">Nom de l'organisme</narrative>
  </reporting-org>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

total-budget

iati-organisations/iati-organisation/total-budget

This is the reference page for the XML element total-budget.

Definition

The total-budget element allows for the reporting of the organisation’s own budget. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three years is reported. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

Rules

This element may occur any number of times.

Attributes

@status

The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

This value must be of type xsd:string.

This value must be on the BudgetStatus codelist.

Example Usage

Example of total-budget for an iati-organisation.

This element is a parent for other child elements.

<total-budget status="1">
...
</total-budget>

Full example with all child elements.

  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>

The total-budget element can be repeated in any iati-organisation.

Changelog

2.02

The status attribute was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

period-start

iati-organisations/iati-organisation/total-budget/period-start

This is the reference page for the XML element period-start.

Definition

The start of the budget period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-start of total-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-organisations/iati-organisation/total-budget/period-end

This is the reference page for the XML element period-end.

Definition

The end of the period (which must not be greater than one year)

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-end of total-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-organisations/iati-organisation/total-budget/value

This is the reference page for the XML element value.

Definition

The total value of the organisation’s aid budget for this period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example value of total-budget for an iati-organisation.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>

Changelog

1.03

Currency values are now allowed to be declared as decimals instead of integers.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

budget-line

iati-organisations/iati-organisation/total-budget/budget-line

This is the reference page for the XML element budget-line.

Definition

A breakdown of the total budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent total-budget element. The sum of budget-line values does not have to equal the value given in the parent element.

Rules

This element may occur any number of times.

Attributes

@ref

An internal reference for this budget line taken from the reporting organisation’s own system. Optional.

This value must be of type xsd:string.

Example Usage

Example budget-line for total-budget of an iati-organisation.

An example @ref attribute is included.

  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>

The budget-line element can be repeated in any total-budget.

Changelog

2.01

The budget-line element was added as a child element of total-budget.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

value

iati-organisations/iati-organisation/total-budget/budget-line/value

This is the reference page for the XML element value.

Definition

The budget sub-total. The definition of the sub-division is determined by iati-organisation/total-budget/budget-line/narrative

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of value in context of budget-line element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>

Changelog

2.01

The budget-line element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

narrative

iati-organisations/iati-organisation/total-budget/budget-line/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the budget-line element.

  <total-budget status="2">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">200000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </total-budget>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The budget-line element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

recipient-org-budget

iati-organisations/iati-organisation/recipient-org-budget

This is the reference page for the XML element recipient-org-budget.

Definition

The recipient-org-budget element allows for the reporting of forward looking budgets for each institution which receives core funding from the reporting organisation. The recommendation is that, where and when possible, annual planned budgets for each recipient institution for each of the next three financial years are reported. This is primarily applicable to donors but any provider of core funding is expected to use it. Earmarked budgets should be reported at activity-level through the Activity Standard. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

Rules

This element may occur any number of times.

Attributes

@status

The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

This value must be of type xsd:string.

This value must be on the BudgetStatus codelist.

Example Usage

Example of recipient-org-budget for an iati-organisation.

This element is a parent for other child elements.

<recipient-org-budget status="1">
...
</recipient-org-budget>

Full example with all child elements.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

The recipient-org-budget element can be repeated in any iati-organisation.

Changelog

2.02

The status attribute was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

recipient-org

iati-organisations/iati-organisation/recipient-org-budget/recipient-org

This is the reference page for the XML element recipient-org.

Definition

The organisation that will receive the funds.

Rules

This element must occur once and only once (within each parent element).

Attributes

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.

This value must be of type xsd:string.

Example Usage

Example usage of recipient-org in context of recipient-org-budget element:

This example declares the organisation identifier with the @ref attribute.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

Changelog

2.03

The definition of the @ref attribute was updated.

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/recipient-org-budget/recipient-org/narrative

This is the reference page for the XML element narrative.

Definition

The name of the organisation. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-org element.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-start

iati-organisations/iati-organisation/recipient-org-budget/period-start

This is the reference page for the XML element period-start.

Definition

The start of the budget period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-start of recipient-org-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-organisations/iati-organisation/recipient-org-budget/period-end

This is the reference page for the XML element period-end.

Definition

The end of the period (which must not be greater than one year)

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-end of recipient-org-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-organisations/iati-organisation/recipient-org-budget/value

This is the reference page for the XML element value.

Definition

The total value of the money budgeted to be disbursed to the specified recipient organisation during this time period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example value of recipient-org-budget for an iati-organisation.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

Changelog

1.03

Currency values are now allowed to be declared as decimals instead of integers.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

budget-line

iati-organisations/iati-organisation/recipient-org-budget/budget-line

This is the reference page for the XML element budget-line.

Definition

A breakdown of the recipient organisation’s budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent recipient-org-budget element. The sum of budget-line values does not have to equal the value given in the parent element.

Rules

This element may occur any number of times.

Attributes

@ref

An internal reference for this budget line taken from the reporting organisation’s own system. Optional.

This value must be of type xsd:string.

Example Usage

Example budget-line for recipient-org-budget of an iati-organisation.

An example @ref attribute is included.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

The budget-line element can be repeated in any recipient-org-budget.

Changelog

2.01

The budget-line element was added as a child element of recipient-org-budget.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

value

iati-organisations/iati-organisation/recipient-org-budget/budget-line/value

This is the reference page for the XML element value.

Definition

The budget sub-total. The definition of the sub-division is determined by iati-organisation/recipient-org-budget/budget-line/narrative

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of value in context of budget-line element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

Changelog

2.01

The budget-line element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

narrative

iati-organisations/iati-organisation/recipient-org-budget/budget-line/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the budget-line element.

  <recipient-org-budget status="2">
   <recipient-org ref="AA-ABC-1234567">
    <narrative>Org Name</narrative>
   </recipient-org>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">2500000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
     <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-org-budget>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The budget-line element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

recipient-region-budget

iati-organisations/iati-organisation/recipient-region-budget

This is the reference page for the XML element recipient-region-budget.

Definition

The recipient-region-budget element allows for the reporting of forward looking budgets where the organisation maintains region-wide, rather than or in addition to country-specific budgets. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three financial years is reported for each recipient region. This must NOT include an aggregation of budgets reported in the recipient-country-budget element. It is strongly recommended that publishers report to existing defined regions wherever possible. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

Rules

This element may occur any number of times.

Attributes

@status

The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

This value must be of type xsd:string.

This value must be on the BudgetStatus codelist.

Example Usage

Example of recipient-region-budget for an iati-organisation.

This element is a parent for other child elements.

<recipient-region-budget status="1">
...
</recipient-region-budget>

Full example with all child elements.

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

The recipient-region-budget element can be repeated in any iati-organisation.

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

recipient-region

iati-organisations/iati-organisation/recipient-region-budget/recipient-region

This is the reference page for the XML element recipient-region.

Definition

The supranational geographic region where funds have been allocated.

Rules

This element must occur once and only once (within each parent element).

Attributes

@vocabulary

An IATI code for the vocabulary from which the region code is drawn. If it is not present, code 1 (‘OECD DAC’) is assumed.

This value must be of type xsd:string.

This value must be on the RegionVocabulary codelist.

@vocabulary-uri

The URI where this vocabulary is defined. If the vocabulary is 99 (reporting organisation), the URI where this internal vocabulary is defined. While this is an optional field it is STRONGLY RECOMMENDED that all publishers use it to ensure that the meaning of their codes are fully understood by data users.

This value must be of type xsd:anyURI.

@code

Either an OECD DAC, UN region code or (if code ‘99’ Reporting organisation is selected for recipient-region/@vocabulary) a code from your internal vocabulary. The codelist is determined by vocabulary attribute. The value in recipient-region/@code should appear within the Region codelist, if the vocabulary code 1 (‘OECD DAC’) is used.

This value must be of type xsd:string.

This value must be on the Region codelist, if the relevant vocabulary is used.

Example Usage

Example usage of recipient-region in context of recipient-region-budget element:

The @code attribute declares a valid code (489) from the Region codelist.

The optional @vocabulary attribute declares a valid code (1) from the RegionVocabulary codelist.

<recipient-region code="489" vocabulary="1" />

If a publisher uses a vocabulary of 99 (i.e. ‘Reporting Organisation’), then the @vocabulary-uri attribute should also be used, for example: .. code-block:: xml

<recipient-region code=”A1” vocabulary=”99” vocabulary-uri=”http://example.com/vocab.html” />

Example of recipient-region in context of a complete recipient-region-budget element:

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

Changelog

2.03

Definition of @vocabulary-uri attribute updated.

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/recipient-region-budget/recipient-region/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-region element.

Note: Both the recipient-region and recipient-country elements still allow both a @code and descriptive text to be specified. This is to cover the isolated cases where the organisation publishing the data may not agree with name of a country or region given by the lookup codelists IATI uses. Example in the case of a recipient-region element:

<recipient-region code="589" vocabulary="1">
        <narrative>Middle East, regional (As per WHO Eastern Mediterranean Region)<narrative>
</recipient-region>

The narrative element can be repeated for any language additional to the default language set in iati-activity, by using the @xml:lang attribute. Example not shown.

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-start

iati-organisations/iati-organisation/recipient-region-budget/period-start

This is the reference page for the XML element period-start.

Definition

The start of the budget period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-start of recipient-region-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-organisations/iati-organisation/recipient-region-budget/period-end

This is the reference page for the XML element period-end.

Definition

The end of the period (which must not be greater than one year)

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-end of recipient-region-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-organisations/iati-organisation/recipient-region-budget/value

This is the reference page for the XML element value.

Definition

The total value of the money budgeted to be disbursed to the specified region during this time period. This element is required.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example value of recipient-region-budget for an iati-organisation.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

budget-line

iati-organisations/iati-organisation/recipient-region-budget/budget-line

This is the reference page for the XML element budget-line.

Definition

A breakdown of the recipient region’s budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent recipient-region-budget element. The sum of budget-line values does not have to equal the value given in the parent element.

Rules

This element may occur any number of times.

Attributes

@ref

An internal reference for this budget line taken from the reporting organisation’s own system. Optional.

This value must be of type xsd:string.

Example Usage

Example budget-line for recipient-region-budget of an iati-organisation.

An example @ref attribute is included.

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

The budget-line element can be repeated in any recipient-region-budget.

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

value

iati-organisations/iati-organisation/recipient-region-budget/budget-line/value

This is the reference page for the XML element value.

Definition

The budget sub-total. The definition of the sub-division is determined by iati-organisation/recipient-region-budget/budget-line/narrative

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of value in context of budget-line element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

narrative

iati-organisations/iati-organisation/recipient-region-budget/budget-line/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the budget-line element.

  <recipient-region-budget status="2">
   <recipient-region vocabulary="99" vocabulary-uri="http://example.com/vocab.html" code="A1" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative xml:lang="en">Budget Line</narrative>
   </budget-line>
  </recipient-region-budget>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.02

The optional recipient-region-budget element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

recipient-country-budget

iati-organisations/iati-organisation/recipient-country-budget

This is the reference page for the XML element recipient-country-budget.

Definition

The recipient-country-budget element allows for the reporting of forward looking budgets for each country in which the organisation operates. The recommendation is that, where and when possible, the organisation’s total annual planned budget for each of the next three financial years is reported for each recipient country. It is strongly recommended that the start and end of the reported financial years match those of the recipient country’s budgetary/planning cycle. The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

Rules

This element may occur any number of times.

Attributes

@status

The status explains whether the budget being reported is indicative or has been formally committed. The value should appear within the BudgetStatus codelist. If the @status attribute is not present, the budget is assumed to be indicative.

This value must be of type xsd:string.

This value must be on the BudgetStatus codelist.

Example Usage

Example of recipient-country-budget for an iati-organisation.

This element is a parent for other child elements.

<recipient-country-budget status="1">
...
</recipient-country-budget>

Full example with all child elements.

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

The recipient-country-budget element can be repeated in any iati-organisation.

Changelog

2.02

The status attribute was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

recipient-country

iati-organisations/iati-organisation/recipient-country-budget/recipient-country

This is the reference page for the XML element recipient-country.

Definition

The recipient country.

Rules

This element must occur once and only once (within each parent element).

Attributes

@code

ISO 3166-1 alpha-2 code for the country.

This attribute is required.

This value must be of type xsd:string.

This value should be on the Country codelist.

Example Usage

Example usage of recipient-country in context of recipient-country-budget element:

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element, but only in particular use-cases.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/recipient-country-budget/recipient-country/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-country element.

Note: Both the recipient-region and recipient-country elements still allow both a @code and descriptive text to be specified. This is to cover the isolated cases where the organisation publishing the data may not agree with name of a country or region given by the lookup codelists IATI uses. Example in the case of a recipient-country element:

<recipient-country code="XK">
        <narrative>Kosovo (As per UNSCR 1244)<narrative>
</recipient-country>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-start

iati-organisations/iati-organisation/recipient-country-budget/period-start

This is the reference page for the XML element period-start.

Definition

The start of the budget period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-start of recipient-country-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-organisations/iati-organisation/recipient-country-budget/period-end

This is the reference page for the XML element period-end.

Definition

The end of the period (which must not be greater than one year)

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

period-start/@iso-date must be before or the same as period-end/@iso-date

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

Example Usage

Example period-end of recipient-country-budget for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-organisations/iati-organisation/recipient-country-budget/value

This is the reference page for the XML element value.

Definition

The total value of the money budgeted to be disbursed to the specified country during this time period. This element is required.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example value of recipient-country-budget for an iati-organisation.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

Changelog

1.03

Values are now allowed to be declared as decimals instead of integers.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

budget-line

iati-organisations/iati-organisation/recipient-country-budget/budget-line

This is the reference page for the XML element budget-line.

Definition

A breakdown of the recipient country’s budget into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent recipient-country-budget element. The sum of budget-line values does not have to equal the value given in the parent element.

Rules

This element may occur any number of times.

Attributes

@ref

An internal reference for this budget line taken from the reporting organisation’s own system. Optional.

This value must be of type xsd:string.

Example Usage

Example budget-line for recipient-country-budget of an iati-organisation.

An example @ref attribute is included.

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

The budget-line element can be repeated in any recipient-country-budget.

Changelog

2.01

The budget-line element was added as a child element of recipient-country-budget.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

value

iati-organisations/iati-organisation/recipient-country-budget/budget-line/value

This is the reference page for the XML element value.

Definition

The budget sub-total. The definition of the sub-division is determined by iati-organisation/recipient-country-budget/budget-line/narrative

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

This value must be on the Currency codelist.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

The budget-line/value/@value-date must be between the period-start/@iso-date and period-end/@iso-date dates.

Example Usage

Example usage of value in context of budget-line element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

Changelog

2.01

The budget-line element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

narrative

iati-organisations/iati-organisation/recipient-country-budget/budget-line/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the budget-line element.

  <recipient-country-budget status="2">
   <recipient-country code="AF" />
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">25000000</value>
   <budget-line ref="1234">
    <value currency="USD" value-date="2014-01-01">2000000</value>
    <narrative>Budget Line</narrative>
   </budget-line>
  </recipient-country-budget>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The budget-line element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

total-expenditure

iati-organisations/iati-organisation/total-expenditure

This is the reference page for the XML element total-expenditure.

Definition

The total-expenditure element allows for the reporting of the organisation’s international development expenditure. The recommendation is that, where and when possible, the organisation’s total expenditure for each of the past three years is reported. The expense line allows publishers to record further breakdown.

Rules

This element may occur any number of times.

Example Usage

Example of total-expenditure for an iati-organisation.

This element is a parent for other child elements.

<total-expenditure>
...
</total-expenditure>

Full example with all child elements.

  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>

The total-expenditure element can be repeated in any iati-organisation.

Changelog

2.02

The optional total-expenditure element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

period-start

iati-organisations/iati-organisation/total-expenditure/period-start

This is the reference page for the XML element period-start.

Definition

The start of the budget period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

period-start/@iso-date must be before or the same as period-end/@iso-date

Example Usage

Example period-start of total-expenditure for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>

Changelog

2.02

The optional total-expenditure element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

period-end

iati-organisations/iati-organisation/total-expenditure/period-end

This is the reference page for the XML element period-end.

Definition

The end of the period (which must not be greater than one year)

Rules

This element must occur once and only once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

The time between period-start/@iso-date and period-end/@iso-date must not be over a year

period-start/@iso-date must be before or the same as period-end/@iso-date

Example Usage

Example period-end of total-expenditure for an iati-organisation.

An example date is declared in the @iso-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>

Changelog

2.02

The optional total-expenditure element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

value

iati-organisations/iati-organisation/total-expenditure/value

This is the reference page for the XML element value.

Definition

The total value of the organisation’s aid expenditure for this period.

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example value of total-expenditure for an iati-organisation.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>

Changelog

2.02

The optional total-expenditure element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

expense-line

iati-organisations/iati-organisation/total-expenditure/expense-line

This is the reference page for the XML element expense-line.

Definition

A breakdown of the total expenditure into sub-totals. The breakdown is determined by the reporting organisation and described in the narrative. The period covered is the same as that covered by the parent total-expenditure element. The sum of expenditure-line values does not have to equal the value given in the parent element.

Rules

This element may occur any number of times.

Attributes

@ref

An internal reference for this expenditure line taken from the reporting organisation’s own system. Optional.

This value must be of type xsd:string.

Example Usage

Example expense-line for total-expenditure of an iati-organisation.

An example @ref attribute is included.

  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>

The expense-line element can be repeated in any total-expenditure.

Changelog

2.02

The optional total-expenditure element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

value

iati-organisations/iati-organisation/total-expenditure/expense-line/value

This is the reference page for the XML element value.

Definition

The expenditure sub-total. The definition of the sub-division is determined by iati-organisation/total-expenditure/expenditure-line/narrative

Rules

This element must occur once and only once (within each parent element).

Attributes

@currency

A three letter ISO 4217 code for the original currency of the amount. This is required for all currency amounts unless the iati-organisation/@default-currency attribute is specified.

This value must be of type xsd:string.

@value-date

The date to be used for determining the exchange rate for currency conversions.

This attribute is required.

This value must be of type xsd:date.

Example Usage

Example usage of value in context of expense-line element.

An example date is declared in the @value-date attribute.

This example date format conform to the xsd:date standard - for most cases YYYY-MM-DD is sufficient.

This example declares a Currency code USD, using the @currency attribute.

Note: A Currency code should only be declared if different to @default-currency in the iati-organisation element.

  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>

Changelog

2.02

The optional total-expenditure element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

narrative

iati-organisations/iati-organisation/total-expenditure/expense-line/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the expense-line element.

  <total-expenditure>
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="USD" value-date="2014-01-01">250000000</value>
   <expense-line ref="1234">
     <value currency="USD" value-date="2014-01-01">200000000</value>
     <narrative xml:lang="en">Expense Line</narrative>
   </expense-line>
 </total-expenditure>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.02

The optional total-expenditure element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-link

iati-organisations/iati-organisation/document-link

This is the reference page for the XML element document-link.

Definition

A link to an online, publicly accessible web page or document.

Rules

This element may occur any number of times.

Attributes

@url

The target URL of the external document, e.g. “http://www.example.org/doc.odt”.

This attribute is required.

This value must be of type xsd:anyURI.

@format

An IANA code for the MIME type of the document being referenced, e.g. “application/pdf”.

This attribute is required.

This value must be of type xsd:string.

This value must be on the FileFormat codelist.

Example Usage

Example document-link in an iati-organisation.

This element is a parent for other child elements.

The @format attribute declares a valid code (application/vnd.oasis.opendocument.text) from the FileFormat codelist.

    <document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report_en.odt">
    ...
</document-link>

Full example with all child elements:

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>

The document-link element can be repeated in any iati-organisation.

Changelog

2.03

The description element was added.

1.02

Removed @language attribute from, and introduced an new language child element to, the document-link element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

recipient-country

iati-organisations/iati-organisation/document-link/recipient-country

This is the reference page for the XML element recipient-country.

Definition

The recipient country that is the focus of the document. May be repeated for multiple countries.

Rules

This element may occur any number of times.

Attributes

@code

ISO 3166-1 alpha-2 code for the country.

This attribute is required.

This value must be of type xsd:string.

This value should be on the Country codelist.

Example Usage

Example usage of recipient-country of a document-link in an iati-organisation.

The @code attribute declares a valid code (AF) from the Country codelist.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>

The recipient-country element can be repeated in any document-link.

Example declaring multiple recipient-country elements for the same document-link:

  <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
   <title>
    <narrative>Country Report 2013</narrative>
    <narrative xml:lang="fr">Rapport Pays 2013</narrative>
   </title>
   <description>
     <narrative>Description of the document</narrative>
   </description>
   <category code="B01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
   <recipient-country code="AX" />
   <recipient-country code="AL" />
  </document-link>

Changelog

2.01

The recipient-country element was added as a child element of document-link.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/document-link/recipient-country/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element may occur any number of times.

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the recipient-country element.

Note: Both the recipient-region and recipient-country elements still allow both a @code and descriptive text to be specified. This is to cover the isolated cases where the organisation publishing the data may not agree with name of a country or region given by the lookup codelists IATI uses.

<recipient-country code="XK">
        <narrative>Kosovo (As per UNSCR 1244)<narrative>
</recipient-country>

Note: The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the @xml:lang attribute. Example not shown.

Changelog

2.01

The recipient-country element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

title

iati-organisations/iati-organisation/document-link/title

This is the reference page for the XML element title.

Definition

A short, human-readable title.

Rules

This element must occur once and only once (within each parent element).

Example Usage

Example usage of title of a document-link in an iati-organisation.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>

Changelog

2.01

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/document-link/title/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the title element.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the xml:lang attribute.

Note: This relates to the language of the text in the XML.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
    <narrative>Annual Report 2013</narrative>
    <narrative xml:lang="fr">Rapport annuel 2013</narrative>
   </title>
   <category code="B01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
  </document-link>

Changelog

2.01

The narrative element was introduced in 2.01.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

description

iati-organisations/iati-organisation/document-link/description

This is the reference page for the XML element description.

Definition

A description of the document contents, or guidance on where to access the relevant information in the document.

Rules

This element must occur no more than once (within each parent element).

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

narrative

iati-organisations/iati-organisation/document-link/description/narrative

This is the reference page for the XML element narrative.

Definition

The free text name or description of the item being described. This can be repeated in multiple languages.

Rules

The text in this element must be of type xsd:string.

This element must occur at least once (within each parent element).

Attributes

@xml:lang

A code specifying the language of text in this element. It is recommended that wherever possible only codes from ISO 639-1 are used. If not present, the default language is assumed.

This value should be on the Language codelist.

Example Usage

The narrative child element can be used to declare freetext for the description element.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>

The narrative element can be repeated for any language additional to the default language set in iati-organisation, by using the xml:lang attribute.

Note: This relates to the language of the text in the XML.

Changelog

2.03

This mandatory narrative element of a description in a document-link element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

category

iati-organisations/iati-organisation/document-link/category

This is the reference page for the XML element category.

Definition

IATI Document Category Code

Rules

This element must occur at least once (within each parent element).

Attributes

@code

An IATI code defining the category of the document.

This attribute is required.

This value must be of type xsd:string.

This value must be on the DocumentCategory codelist.

Example Usage

Example usage of category of a document-link in an iati-organisation.

This examples declares the DocumentCategory code B01, using the @code attribute.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>

The category element can be repeated in any document-link.

Example declaring multiple DocumentCategory codes for the same document-link:

  <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
   <title>
    <narrative>Annual Report 2013</narrative>
    <narrative xml:lang="fr">Rapport annuel 2013</narrative>
   </title>
   <description>
     <narrative>Description of the document</narrative>
   </description>
   <category code="B01" />
   <category code="B02" />
   <category code="B03" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
  </document-link>

Changelog

2.01

Freetext is no longer allowed within this element.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

language

iati-organisations/iati-organisation/document-link/language

This is the reference page for the XML element language.

Definition

The ISO 639-1 language code in which target document is written, e.g. “en”. Can be repeated to describe multi-lingual documents.

Rules

This element may occur any number of times.

Attributes

@code

ISO 639-1 language code

This attribute is required.

This value must be of type xsd:string.

This value should be on the Language codelist.

Example Usage

Example usage of language of a document-link in an iati-organisation.

The @language attribute declares a valid code (en) from the Language codelist.

Note: This specifies the language of the document being linked to.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
    <narrative>Annual Report 2013</narrative>
    <narrative xml:lang="fr">Rapport annuel 2013</narrative>
   </title>
   <category code="B01" />
   <language code="en" />
   <document-date iso-date="2014-02-05" />
   <recipient-country code="AF" />
  </document-link>

In some cases, a document-link may be in multiple languages. This is expressed by repeating the language element.

<document-link format="application/vnd.oasis.opendocument.text" url="http:www.example.org/docs/report.odt">
        <title>
                <narrative>Annual Report 2013</narrative>
                <narrative xml:lang="fr">Rapport annuel 2013</narrative>
        </title>
        <category code="B01" />
        <language code="en" />
        <language code="fr" />
</document-link>

Changelog

2.01

Freetext is no longer allowed within this element.

In 2.01 this element usage rules were changed, to allow it to be repeated.

1.02

Addition of a @language element as a child of the document-link element: document-link/language/text() (0..1) - The ISO 639 code for the language of the document

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

document-date

iati-organisations/iati-organisation/document-link/document-date

This is the reference page for the XML element document-date.

Definition

The date of publication of the document that is being linked to.

Rules

This element must occur no more than once (within each parent element).

Attributes

@iso-date

This attribute is required.

This value must be of type xsd:date.

Usage in practice

This document-date element would normally be the production or published date of the relevant document to identify the specific document version.

Example Usage

Example usage of the document-date element within a document-link as part of an iati-organisation.

This examples declares an ISO date (corresponding to 5th February 2014) using the @iso-date attribute.

 <document-link format="application/vnd.oasis.opendocument.text" url="http://www.example.org/docs/report_en.odt">
  <title>
   <narrative>Annual Report 2013</narrative>
  </title>
  <category code="B01" />
  <language code="en" />
  <document-date iso-date="2014-02-05" />
  <recipient-country code="AF" />
 </document-link>

The document-date element should only be used once for each document-link element.

Changelog

2.02

Added the optional document-date element was added.

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Namespaces & Extensions

Adding other information

There will be situations where reporting organisations want to publish additional data that are not covered by the default IATI elements, or want to specify the data using the original formats or values to avoid information loss. IATI provides two mechanisms for doing so:

• Use an XML namespace to extend the schema.

• Use the legacy-data element to provide original data values.

XML namespaces

The first approach allows reporting organisations to invent any required markup and add it to an IATI activity report. IATI users who don’t recognise the extended markup are required simply to ignore it, without reporting an error. Here is an example:

<iati-activity xmlns:acme="http://example.org/acme/ns#">

...

  <acme:risk-level>3</acme:risk-level>

...

</iati-activity>

In this example, ACME has defined its own namespace using the URL http://example.org/acme/ns# and mapped that to the prefix acme. It then adds the new element, acme:risk-level, to provide information about its risk assessment for the activity. IATI users who don’t recognise the http://example.org/acme/ns# namespace are required to ignore the acme:risk element rather than reporting an error, so the extended markup does not harm compatibility. Users who are familiar with the namespace, however, can take advantage of the additional information.

Adding XML namespaces in versions 2.0x

Please note: elements must occur in the order they are specified in the Schema. When adding XML namespaces in versions 2.0x of the IATI standard, they should be placed as the last element. At the activity level, they must only be included at the end of the activity (before </iati-activity>). If added as a subelement, the namespace element must be placed as the last subelement. Example:

1. XML namespace at activity level

<iati-activity xmlns:acme="http://example.org/acme/ns#">

...

  </fss>
  <acme:risk-level>3</acme:risk-level>

...

</iati-activity>

2. XML namespace as a subelement within transaction

<iati-activity xmlns:acme="http://example.org/acme/ns#">

...

  <transaction>

...

    </value>
    <acme:risk-level>3</acme:risk-level>
  </transaction>

...

</iati-activity>

Codelists

The IATI codelists are key to making IATI activity and organisation data from different publishers comparable.

Codes are used to represent many standard values in an IATI activity. For example, codelists such as organisation type ensure that different publishers have unambiguous, comparable definitions (e.g. 23 = Regional NGO; 60 = Foundation; or 70 = Private Sector) they can use when describing activities.

Codelists are updated through a managed process. A codelist can either be embedded (centrally managed by IATI) or non-embedded (derived from an authority source).

For every codelist, the embedded status, alongside the relevant IATI element(s) are declared and linked to.

An API is also available for accessing codelists.

General Information about Codelists

IATI Codelist Management

The IATI codelists are key to making IATI data from different publishers comparable.

These lists need to be managed to deal with additions, amendments, bugs, and deletions. We use GitHub as a tool to manage our change control process. By placing codelists in GitHub, we have the ability to track very minor changes and to ‘tag’ major releases.

The structure of the codelists themselves is governed by a schema that is versioned and maintained in the GitHub repository for each version of the standard. e.g. for v2.02: https://github.com/IATI/IATI-Codelists/blob/version-2.02/codelist.xsd

In managing the codelists we make a distinction between ‘embedded’ and ‘non-embedded’ codelists. In addition, we may refer to these lists as either ‘complete’ or ‘incomplete’.

Embedded Codelists

These are ‘functional’ codelists that are core to IATI. Changing them has a big impact on all those publishing and using IATI data. For example, adding, removing or renaming something on the transaction-types codelist http://iatistandard.org/codelists/transaction_type/ could be very disruptive.

Embedded codelists are  managed via GitHub at: https://github.com/IATI/IATI-Codelists/

• Any changes to these codelists should be handled through a formal decimal or integer upgrade process. (http://dev.iatistandard.org/upgrades/). (except bug fixes - see below)

• Releases are tagged in line with the IATI Standard versions. This means you can grab a snapshot of e.g. everything to do with version 1.03.

• There are branches for each version of the standard. These can change between decimal and integer releases of the standard ONLY for bug fixes, typos, and translations. Users can chose to track changes to those branches if they like but our documentation (from v1.04 onwards) will always track the corresponding branch.

• During an upgrade to the standard, the new version of a new branch is created for development.

Non-Embedded Codelists

These ‘non-functional’ codelists usually provide lookup information on e.g. currencies, languages in use, countries, etc. Often they are derived from third party lists and an addition or modification has a minor impact on the sense and use of the data.

Non-embedded codelists are managed via GitHub at: https://github.com/IATI/IATI-Codelists-NonEmbedded

• We aim to make changes to these lists quickly to allow data users to take advantage of the changes immediately. These changes can be made outside of a formal decimal or integer upgrade process.

• Releases would be tagged in line with standard but the minor changes will be available on the master branch of this repository.

Updates to Non-embedded Codelists

Potential changes to Non-embedded Codelists may come to the team via:

• Personal requests/Support tickets

• Email notifications

• Announcements from the source organisations

• Automatic detection of changes to external sources compared with our own lists.

All proposals will be added to the The Non-embedded Codelist-Amendments Forum

The IATI Technical Team hold regular team meetings once a week. All outstanding proposals will be discussed at that meeting. The IATI Technical Lead (Bill Anderson) has the ultimate responsibility for decisions taken.

If a decision has been made to make a change to a non-embedded list the IATI Standard discussion thread will be notified (within 1 working day) about the change that is to be made and the date that the change will take effect (usually within 7 calendar days). The proposal will be marked as ‘Planned’ on the support forum. At this point people have the right to disagree. Discussion should take place via the IATI Standard discussion thread. Unresolved matters can be taken to the following team meeting.

In most circumstances the decision to alter these codelists is straightforward. In rare cases, the team may decide to seek further clarification, or to consult further on whether or not to adopt a change. If so, a timetable outlining the process and time scales will be issued.

Once a change has been agreed, a GitHub issue will be created and will be linked to from the forum post.

When the change has been made and accepted into the master branch of the Non-embedded Codelist repository, the change will be ‘live’ to anyone who consumes these codelists directly from Github or via the API.

At this point the technical team will:

• Update the Non-Embedded Codelist changelog record

• Regenerate the IATI Standard Website.

• Mark the forum post as ‘Done’

A summary of all changes to all non-emebedded codelists is published on the IATI Standard website. They can also be found via the list of commits to the GitHub repository.

Special Cases

File Format

The IATI Technical Team will use its judgement to assess the importance of a change to the file format list and whether or not an announcement is required (i.e. the list may alter to stay inline with the external source, but announcements will not necessarily be made).

Organisation Registration Agency

Because there is a need to add registration agencies quickly, so that people can do their work, and because we anticipate many additions that will not be of interest to most people, we will add values to this list without making announcements. Values to be added will be agreed at the weekly team meeting.

Code status, addition and withdrawal dates

All new codes added to codelist from the release of version 2.02 (December 2015) will feature status="active" and activation-date attributes in the underlying GitHub source code repositories. Similarly, codes withdrawn from the release of version 2.02 (December 2015) will feature status="withdrawn" and withdrawal-date attributes.

Complete vs Incomplete Codelists

Some codelists, such as the ISO country codes, are not ‘complete’ lists of all possible values that might be used. In the case of countries, publishers may use extra user defined codes (such as ‘XK’ for Kosovo) or valid historical values that are not on our maintained list.

For other codelists, such as the DescriptionType codelist, if the value is not on the codelist the data doesn’t make any sense - it is invalid. This is an example of a ‘complete’ codelist.

We distinguish between these two types of codelists by the use of an xml attribute: complete="1"

Codelist API

IATI provides two machine readable ways for people to consume the codelists needed to create and interpret IATI data.

You can:

1. use the Codelist API to request a codelist via a URL

2. From version 1.04 of the IATI standard upwards, you can work directly with our GitHub repositories

API Calls

To download a codelist. Select your endpoint (see below) and then specify the codelist name and the format:

<endpoint><codelist name>.<extension (xml/json/csv)>

Codelist Mappings

There exists a machine readable mapping from attributes to the codelist they should be on. This is available on GitHub as an XML file: https://github.com/IATI/IATI-Codelists/blob/version-2.01/mapping.xml

It is also available as XML and JSON from the codelist API:

http://iatistandard.org/{105,201}/codelists/downloads/clv{1,2,3}/mapping.{xml,json}

Endpoints

The codelists used in each version of the standard are derived from different endpoints as a result of the historical management of the codelist API. From May 2014, these are now under in-house control at IATI.

Therefore anyone relying on the services at:

• http://datadev.aidinfolabs.org/data/, or

• http://data.aidinfolabs.org/data/

is strongly advised to migrate to the new endpoints given below.

• v1.01 of the standard - used datadev - change to http://codelists102.archive.iatistandard.org/data/

• v1.02 of the standard - used datadev - change to - http://codelists102.archive.iatistandard.org/data/

• v1.03 of the standard - used data - change to - http://codelists103.archive.iatistandard.org/data/

Codelists in Version 1.x after v1.03 (e.g. v1.04, v1.05) of the standard

In v1.04 of the standard a new codelists structure was introduced. See Why create a new structure for codelists? below.

We call this ‘codelist version 2 (CLv2)’. This forms the ‘single source of truth’ from which codelists in various forms can be produced.

As this new structure would force a change on data users/producers to alter their routines for consuming codelists, we use the single source of truth to generate codelists in the previous format that they are used to. We named that format ‘codelist version 1 (CLv1)’.

Data users/producers can choose which format they wish to consume via the API. To stick with the old format, use CLv1.

The codelists matching the highest decimal version of the version 1.x standard will always be found using either:

• http://iatistandard.org/codelists/downloads/clv1/, or

• http://iatistandard.org/codelists/downloads/clv2/

To ‘lock in’ to a particular version of the codelists (above v1.03) you may specify

• http://iatistandard.org/<version>/codelists/downloads/clv1/

For example: (note: use version number without the decimal point)

• http://iatistandard.org/104/codelists/downloads/clv1/ will always return v1.04 codelists

• http://iatistandard.org/105/codelists/downloads/clv1/ will always return v1.05 codelists

By locking into a specified version in this way, you can always guarantee you are getting the lists associated with that particular version of the standard, and not accidentally move up to a new version when a new version is released.

From version 1.04 onwards, developers might also choose to work directly with GitHub to get the data (see below).

New Codelist version (CLv3) in Version 2.01 of the IATI Standard

Version 2.01 of the IATI Standard sees a significant change to the way multilingual text can be reported. (see http://iatistandard.org/201/upgrades/integer-upgrade-to-2-01/migrating/#handling-translations)

As codelists can also supply definitions and descriptions in multiple languages, we decided to bring the XML format of the codelists into line with rest of the standard.

This change applies to the ‘source’ XML files from which the codelist API, the documentation on the website, and so on, is generated.

We are changing the format of the source XML in the IATI-Codelists and IATI-Codelists-NonEmbedded repositories. This is the third change we have made to the codelist format over the lifetime of IATI, so we are calling this CLv3 (Code List format version 3). The XML schema that defines the new format is available here: https://github.com/IATI/IATI-Codelists/blob/version-2.01/codelist.xsd

Anyone who fetches their codelists directly from GitHub will be affected by this change.

Developers dealing with version 1.04, 1.05 (and any subsequent version 1.x decimal versions) data with need to work with both the CLv2 format in the IATI-Codelists repository on the version-1.x branch, AND the CLv3 version of the IATI-Codelists-NonEmbedded repository (master branch)

However, the old XML formats (CLv1,CLv2) are still available from the web API. Since the API is versioned, the new CLv3 XML will only be served via the API to those explicitly requesting it.

To compare the old style XML with the new see for example:

Old style XML (CLv2):

http://iatistandard.org/201/codelists/downloads/clv2/xml/ActivityDateType.xml

New Style XML (CLv3):

http://iatistandard.org/201/codelists/downloads/clv3/xml/ActivityDateType.xml

Working with GitHub Directly

The codelist source is now on GitHub:

Embedded Codelists

As of version 1.04, each version of the standard has it’s own branch in this repository. Branches are named version-<version-number> e.g. version-1.05. So, for example, the version 1.05 codelists can be found at:

• https://github.com/IATI/IATI-Codelists/tree/version-1.05/xml

Non-Embedded Codelists

These values on these lists can change independently of IATI versions. The latest versions are always on the ‘master’ branch.

• https://github.com/IATI/IATI-Codelists-NonEmbedded/tree/master/xml

This repository now uses the Codelist Version 3 format.

We use this source to create all derived versions, (CSV, JSON and all forms of codelist version 1, and codelist version 2 files, as well as all the documentation on the iatistandard.org website)

If you wish to use the new style XML, or are prepared to run the supplied python scripts for converting to a different format of your choice, you can fetch the codelists from GitHub directly.

Developers dealing with version 1.04, 1.05 (and any subsequent version 1.x decimal versions) data with need to work with both the CLv2 format in the IATI-Codelists repository on the version-1.x branch, AND the CLv3 version of the IATI-Codelists-NonEmbedded repository (master branch)

Why did we create a new structure for codelists for verison 1.04?

As part of our move towards creating a Single Source of Truth for the IATI Standard, we have started to take a different approach to codelists. See background paper previously circulated: https://docs.google.com/document/d/1oeH-8BFB__2IYF4MLnUwx2LcXZCVd5e-iYsXtQ4ViTk/edit

As this work progressed, it became evident that for the codelists to work in that environment we would need to make a few changes. As a result:

1. The newer codelist files are more consistent:

• they don’t include the element name as a tag name

• all have language information described the same way as IATI XML.

2. There is also a codelist schema that all the source XML validates against - https://github.com/IATI/IATI-Codelists/blob/version-1.04/codelist.xsd.

3. Finally, more metadata, including a description, is now included in the codelists.

If you rely on the codelist API you should also read the notes on Codelist API Compatibility in version 1.04 of the IATI Standard and above below.

Codelist API Compatibility in version 1.04 of the IATI Standard and above

For version 2.01 data, a more sustainable approach would be to migrate your codelist handling routines to deal with the latest CLv3 format.

If moving from a version before 1.04 to a higher 1.x decimal version you might first consider moving your data to version 2.01 instead. If you decide to upgrade to a higher 1.x version, you should consider going to the highest decimal version your data can accommodate. If you do this you may not need to alter the way you deal with codelists, but there are a few things that anyone relying on CLv1 should be aware of.

• The ‘metadata’ link/call is no longer available (instead, some of this is now available in the CLv2 style code lists, and some is stored in the github repository metadata to be consistent with the rest of the Single Source of Truth)

• Only the latest versions (those required in v1.04 of the standard and above) will be available through the API. If you need an older version use the static archives detailed above.

• URLs containing the version and/or language do not work. (for example in the past a url like: /data/codelist/AidTypeFlag/version/1.0/lang/en was possible. This will not work using the /codelists/downloads/clv1/ endpoint. Instead, translations, where available, are maintained in the codelist version 2 (CLv2) files.

• The ‘fields’ element is no longer provided in the index XML/JSON (See http://data.aidinfolabs.org/data/codelist.xml and compare with http://iatistandard.org/codelists/downloads/clv1/codelist.xml

• Version information is no longer provided in the XML.

• Specific changes to codelists:

  • Budget Identifier has different categories, and no ‘sector’ elements.

  • Names in the File Format list are no longer there as they make little sense, and the list now tracks the IANA source it is derived from directly.

All Codelists

Activity Date Type

Types of date for activities.

There are many different business models and dates that can be used to describe the start and end of activities. It is recommended that each publisher adopts their own consistent approach that provides users with a meaningful indication of the lifespan of an activity.

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/activity-date/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Planned start	The date on which the activity is planned to start, for example the date of the first planned disbursement or when physical activity starts.
2	Actual start	The actual date the activity starts, for example the date of the first disbursement or when physical activity starts.
3	Planned End	The date on which the activity is planned to end, for example the date of the last planned disbursement or when physical activity is complete.
4	Actual end	The actual date the activity ends, for example the date of the last disbursement or when physical activity is complete.

Changelog

2.01

The ActivityDateType codelist was amended to numeric values.

Activity Scope

Geographic scope of activity

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/activity-scope/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Global	The activity scope is global
2	Regional	The activity scope is a supranational region
3	Multi-national	The activity scope covers multiple countries, that don’t constitute a region
4	National	The activity scope covers one country
5	Sub-national: Multi-first-level administrative areas	The activity scope covers more than one first-level subnational administrative areas (e.g. counties, provinces, states)
6	Sub-national: Single first-level administrative area	The activity scope covers one first-level subnational administrative area (e.g. country, province, state)
7	Sub-national: Single second-level administrative area	The activity scope covers one second-level subnational administrative area (e.g. municipality or district)
8	Single location	The activity scope covers one single location (e.g. town, village, farm)

Activity Status

Lifecycle status of the activity from pipeline to completion

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/activity-status/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Pipeline/identification	The activity is being scoped or planned
2	Implementation	The activity is currently being implemented
3	Finalisation	Physical activity is complete or the final disbursement has been made, but the activity remains open pending financial sign off or M&E
4	Closed	Physical activity is complete or the final disbursement has been made.
5	Cancelled	The activity has been cancelled
6	Suspended	The activity has been temporarily suspended

Aid Type

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/default-aid-type/@code

• iati-activities/iati-activity/transaction/aid-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
A01	General budget support	Unearmarked contributions to the government budget including funding to support the implementation of macroeconomic reforms (structural adjustment programmes, poverty reduction strategies). Budget support is a method of financing a recipient country’s budget through a transfer of resources from an external financing agency to the recipient government’s national treasury. The funds thus transferred are managed in accordance with the recipient’s budgetary procedures. Funds transferred to the national treasury for financing programmes or projects managed according to different budgetary procedures from those of the recipient country, with the intention of earmarking the resources for specific uses, are therefore excluded.	A
A02	Sector budget support	Sector budget support, like general budget support, is a financial contribution to a recipient government’s budget. However, in sector budget support, the dialogue between donors and partner governments focuses on sector-specific concerns, rather than on overall policy and budget priorities.	A
B01	Core support to NGOs, other private bodies, PPPs and research institutes	Funds are paid over to NGOs (local, national and international) for use at the latter’s discretion, and contribute to programmes and activities which NGOs have developed themselves, and which they implement on their own authority and responsibility. Core contributions to PPPs, funds paid over to foundations (e.g. philanthropic foundations), and contributions to research institutes (public and private) are also recorded here. Annex 2 of the DAC Directives provides a list of INGOs, PPPs and networks core contributions to which may be reported under B01. This list is not exclusive.	B
B02	Core contributions to multilateral institutions	These funds are classified as multilateral ODA (all other categories fall under bilateral ODA). The recipient multilateral institution pools contributions so that they lose their identity and become an integral part of its financial assets. See Annex 2 of the DAC Directives for a comprehensive list of agencies core contributions to which may be reported under B02 (Section I. Multilateral institutions).	B
B03	Contributions to specific-purpose programmes and funds managed by implementing partners	In addition to their core-funded operations, international organisations, NGOs, PPPs and networks, both in provider and in third countries, set up programmes and funds with a specific sectoral, thematic or geographical focus. Donors’ bilateral contributions to such programmes and funds are recorded here.	B
B031	Contributions to multi-donor/multi-entity funding mechanisms	Funding mechanisms that pool contributions from several donors and that are implemented by several multilateral entities e.g. UN inter-agency pooled funds, including CERF and country-based pooled funds; Financial Intermediary Funds (GEF, CIFs) for which the World Bank is the Trustee.	B03
B032	Contributions to multi-donor/single-entity funding mechanisms	Contributions to multi-donor funding mechanisms managed by a single multilateral organisation e.g. UN single-agency thematic funds; World Bank or other MDB trust funds. Classify the contribution as B032 even if in the initial stages only one donor contributes to the fund.	B03
B033	Contributions to single-donor funding mechanisms and contributions earmarked for a specific funding window or geographical location	Contributions to funding mechanisms where the donor has a significant influence on the allocation of funds. This includes contributions to single-donor trust funds and earmarked contributions to specific countries/geographical locations or funding windows within multi-donor trust funds. When the donor designs the activity but channels it through an international organisation, the activity should be classified as C01.	B03
B04	Basket funds/pooled funding	The donor contributes funds to an autonomous account, managed jointly with other donors and/or the recipient. The account will have specific purposes, modes of disbursement and accountability mechanisms, and a limited time frame. Basket funds are characterised by common project documents, common funding contracts and common reporting/audit procedures with all donors. Donors’ contributions to funds managed autonomously by international organisations are recorded under B03.	B
C01	Project-type interventions	A project is a set of inputs, activities and outputs, agreed with the partner country*, to reach specific objectives/outcomes within a defined time frame, with a defined budget and a defined geographical area. Projects can vary significantly in terms of objectives, complexity, amounts involved and duration. There are smaller projects that might involve modest financial resources and last only a few months, whereas large projects might involve more significant amounts, entail successive phases and last for many years. A large project with a number of different components is sometimes referred to as a programme, but should nevertheless be recorded here. Feasibility studies, appraisals and evaluations are included (whether designed as part of projects/programmes or dedicated funding arrangements). Academic studies, research and development, trainings, scholarships, and other technical assistance activities not directly linked to development projects/programmes should instead be recorded under D02. Aid channelled through NGOs or multilaterals is also recorded here. This includes payments for NGOs and multilaterals to implement donors’ projects and programmes, and funding of specified NGOs projects. By contrast, core funding of NGOs and multilaterals as well as contributions to specific-purpose funds are recorded under B.* In the cases of equity investments, humanitarian aid or aid channelled through NGOs, projects are recorded here even if there was no direct agreement between the donor and the partner country. Contributions to single-donor trust funds and contributions to trust funds earmarked for a specific funding window and/or country are recorded under B033.	C
D01	Donor country personnel	Experts, consultants, teachers, academics, researchers, volunteers and contributions to public and private bodies for sending experts to developing countries.	D
D02	Other technical assistance	Provision, outside projects as described in category C01, of technical assistance in recipient countries (excluding technical assistance performed by donor experts reported under D01, and scholarships/training in donor country reported under E01). This includes training and research; language training; south-south studies; research studies; collaborative research between donor and recipient universities and organisations); local scholarships; development-oriented social and cultural programmes. This category also covers ad hoc contributions such as conferences, seminars and workshops, exchange visits, publications, etc.	D
E01	Scholarships/training in donor country	Financial aid awards for individual students and contributions to trainees.	E
E02	Imputed student costs	Indirect (“imputed”) costs of tuition in donor countries.	E
F01	Debt relief	Groups all actions relating to debt (forgiveness, conversions, swaps, buy-backs, rescheduling, refinancing).	F
G01	Administrative costs not included elsewhere	Administrative costs of development assistance programmes not already included under other ODA items as an integral part of the costs of delivering or implementing the aid provided. This category covers situation analyses and auditing activities.As regards the salaries component of administrative costs, it relates to in-house agency staff and contractors only; costs associated with donor experts/consultants are to be reported under category C or D01.	G
H01	Development awareness	Funding of activities designed to increase public support, i.e. awareness in the donor country of development co-operation efforts, needs and issues.	H
H02	Refugees/asylum seekers in donor countries	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months, when costs cannot be disaggregated. See section II.6 and Annex 17.	H
H03	Asylum-seekers ultimately accepted	Costs incurred in donor countries for basic assistance to asylum seekers, when these are ultimately accepted. This category includes only costs incurred prior to recognition.	H
H04	Asylum-seekers ultimately rejected	Costs incurred in donor countries for basic assistance to asylum seekers, when these are ultimately rejected. This category includes only costs incurred prior to rejection. Members may base their reporting on the first instance rejection, where a final decision on status is anticipated to occur after a 12-month period, and this facilitates the establishment of a conservative estimate. For further guidance on how to proceed with calculating costs related to rejected asylum seekers, see Clarification 5, third bullet in section II.6 of the Reporting Directives.	H
H05	Recognised refugees	Costs incurred in donor countries for basic assistance to refugees with a recognised status. This category only includes costs after recognition (or after date of entry into a country through a resettlement programme).	H

Aid Type (category)

This codelists exists to group the Aid Type codelist into categories. It is not used as a codelist in its own right.

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
A	Budget support	For contributions under this category, the donor relinquishes the exclusive control of its funds by sharing the responsibility with the recipient.
B	Core contributions and pooled programmes and funds	For contributions under this category, the donor relinquishes the exclusive control of its funds by sharing the responsibility with other stakeholders (other donors, NGOs, multilateral institutions, Public Private Partnerships). The category covers both core contributions (B01 and B02), and pooled contributions with a specific earmarking (B03 and B04).
C	Project-type interventions	N.B. Within this category, members able to do so are requested to report the aggregate amount used for financing donor experts/consultants on Table DAC11. Where the activity consists solely of experts’ costs, report under category D.
D	Experts and other technical assistance	This category covers the provision, outside projects as described in category C, of know-how in the form of personnel, training and research.
E	Scholarships and student costs in donor countries
F	Debt relief
G	Administrative costs not included elsewhere
H	Other in-donor expenditures	Groups a number of contributions that do not give rise to a cross-border flow.

Aid Type Vocabulary

The AidTypeVocabulary codelist defines a range of external codelists which themselves provide codes and descriptions for aid type.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/default-aid-type/@vocabulary

• iati-activities/iati-activity/transaction/aid-type/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1	OECD DAC	List of codes provided by the OECD DAC used to distinguish types of aid	http://reference.iatistandard.org/codelists/AidType/
2	Earmarking Category	This vocabulary has been created by IATI and is derived from the Grand Bargain Earmarking Modality codelist	http://reference.iatistandard.org/codelists/EarmarkingCategory/
3	Earmarking Modality	Codes A to L replicated directly from Grand Bargain document found in Annex 1 (pg.16)	https://reliefweb.int/sites/reliefweb.int/files/resources/Grand_Bargain_final_22_May_FINAL-2.pdf
4	Cash and Voucher Modalities	This vocabulary has been created by IATI, following agreements and recommendations of the Tracking Cash and Voucher Assistance (CVA) Working Group.	http://reference.iatistandard.org/codelists/CashandVoucherModalities/

Budget Identifier

IATI Functional and Administrative Common Code : One of several possible Budget Identifier Vocabularies. As of version 2.03 this codelist has been deprecated.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/country-budget-items/budget-item/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
1.1.1	Executive - executive		1.1
1.2.1	Legislative - legislative		1.2
1.3.1	Accountability - macroeconomic policy		1.3
1.3.2	Accountability - budgeting		1.3
1.3.3	Accountability - planning		1.3
1.3.4	Accountability - Treasury/Accounts		1.3
1.3.5	Accountability - debt and aid management		1.3
1.3.6	Accountability - tax policy		1.3
1.3.7	Accountability - tax collection		1.3
1.3.8	Accountability - local government finance		1.3
1.3.9	Accountability - other central transfers to institutions		1.3
1.3.10	Accountability - national audit		1.3
1.3.11	Accountability - national monitoring and evaluation		1.3
1.3.12	Accountability - monetary institutions		1.3
1.3.13	Accountability - financial sector policy and regulation		1.3
1.4.1	External Affairs - foreign affairs		1.4
1.4.2	External Affairs - diplomatic missions		1.4
1.4.3	External Affairs - official development assistance		1.4
1.5.1	General Personnel Services - general personnel services		1.5
1.6.1	Statistics - statistics		1.6
1.7.1	Other General Services - support to civil society		1.7
1.7.2	Other General Services - central procurement		1.7
1.7.3	Other General Services - Local Government Administration		1.7
1.7.4	Other General Services - other general services		1.7
1.8.1	Elections - elections		1.8
2.1.1	Justice, Law and Order - policy, planning and administration		2.1
2.1.2	Justice, Law and Order - fire or police		2.1
2.1.3	Justice, Law and Order - judicial affairs		2.1
2.1.4	Justice, Law and Order - Ombudsman		2.1
2.1.5	Justice, Law and Order - human rights affairs		2.1
2.1.6	Justice, Law and Order - immigration		2.1
2.1.7	Justice, Law and Order - anti corruption		2.1
2.1.8	Justice, Law and Order - prisons		2.1
2.1.9	Justice, Law and Order - peace building		2.1
2.1.10	Justice, Law and Order - demobilisation		2.1
2.2.1	Defence - policy, planning and administration		2.2
2.2.2	Defence - military		2.2
2.2.3	Defence - civil defence		2.2
2.2.4	Defence - foreign military aid		2.2
3.1.1	General Economic, Commercial and Labour Affairs - policy, planning and administration		3.1
3.1.2	General Economic, Commercial and Labour Affairs - general economic affairs		3.1
3.1.3	General Economic, Commercial and Labour Affairs - investment promotion		3.1
3.1.4	General Economic, Commercial and Labour Affairs - privatisation		3.1
3.1.5	General Economic, Commercial and Labour Affairs - trade		3.1
3.1.6	General Economic, Commercial and Labour Affairs - labour		3.1
3.1.7	General Economic, Commercial and Labour Affairs - national standards development		3.1
3.2.1	Public Works - policy, planning and administration		3.2
3.2.2	Public Works - construction regulation		3.2
3.2.3	Public Works - mechanical services		3.2
3.3.1	Agriculture - policy, planning and administration		3.3
3.3.2	Agriculture - irrigation		3.3
3.3.3	Agriculture - inputs		3.3
3.3.4	Agriculture - food crop		3.3
3.3.5	Agriculture - industrial crop		3.3
3.3.6	Agriculture - livestock		3.3
3.3.7	Agriculture - agricultural training and extension		3.3
3.3.8	Agriculture - research		3.3
3.3.9	Agriculture - other services		3.3
3.4.1	Forestry - policy, planning and administration		3.4
3.4.2	Forestry - development and services		3.4
3.4.3	Forestry - education/training		3.4
3.4.4	Forestry - research		3.4
3.5.1	Fishing and Hunting - policy, planning and administration		3.5
3.5.2	Fishing and Hunting - development and services		3.5
3.5.3	Fishing and Hunting - education and training		3.5
3.5.4	Fishing and Hunting - research		3.5
3.6.1	Energy - policy, planning and administration		3.6
3.6.2	Energy - education and training		3.6
3.6.3	Energy - energy regulation		3.6
3.6.4	Energy - electricity transmission		3.6
3.6.5	Energy - nuclear		3.6
3.6.6	Energy - power generation		3.6
3.6.7	Energy - gas		3.6
3.7.1	Mining and Mineral Development - policy, planning and administration		3.7
3.7.2	Mining and Mineral Development - prospection and exploration		3.7
3.7.3	Mining and Mineral Development - coal and other solid mineral fuels		3.7
3.7.4	Mining and Mineral Development - petroleum and gas		3.7
3.7.6	Mining and Mineral Development - other fuel		3.7
3.7.7	Mining and Mineral Development - non fuel minerals		3.7
3.8.1	Transport - policy, planning and administration		3.8
3.8.2	Transport - transport regulation		3.8
3.8.3	Transport - feeder road construction		3.8
3.8.4	Transport - feeder road maintenance		3.8
3.8.5	Transport - national road construction		3.8
3.8.6	Transport - national road maintenance		3.8
3.8.7	Transport - rail		3.8
3.8.8	Transport - water		3.8
3.8.9	Transport - air		3.8
3.8.10	Transport - pipeline		3.8
3.8.11	Transport - storage and distribution		3.8
3.8.12	Transport - public transport services		3.8
3.8.13	Transport - meteorological services		3.8
3.8.14	Transport - education and training		3.8
3.9.1	Industry - policy, planning and administration		3.9
3.9.2	Industry - development and services		3.9
3.9.3	Industry - industrial research		3.9
3.9.4	Industry - (investment in industry)		3.9
3.10.1	Communications - policy, planning and administration		3.10
3.10.2	Communications - ICT Infrastructure		3.10
3.10.3	Communications - telecoms and postal services		3.10
3.10.4	Communications - information services		3.10
3.11.1	Tourism - policy, planning and administration		3.11
3.11.2	Tourism - services		3.11
3.12.1	Microfinance and financial services - Microfinance and financial services		3.12
4.1.1	Water supply and Sanitation - policy, planning and administration		4.1
4.1.2	Water supply and Sanitation - education/training		4.1
4.1.3	Water supply and Sanitation - rural water supply and sanitation		4.1
4.1.4	Water supply and Sanitation - urban water supply and sanitation		4.1
4.1.5	Water supply and Sanitation - rural water supply		4.1
4.1.6	Water supply and Sanitation - urban water supply		4.1
4.1.7	Water supply and Sanitation - rural sanitation		4.1
4.1.8	Water supply and Sanitation - urban sanitation		4.1
4.1.9	Water supply and Sanitation - sewage and waste management		4.1
4.2.1	Environment - policy, planning and administration		4.2
4.2.2	Environment - research/ education and training		4.2
4.2.3	Environment - natural resource management		4.2
4.2.4	Environment - water resources management		4.2
4.2.5	Environment - wildlife protection, parks and site preservation		4.2
5.1.1	Health - policy, planning and administration		5.1
5.2.1	Recreation, Culture and Religion - recreation and sport		5.2
5.2.2	Recreation, Culture and Religion - culture		5.2
5.2.3	Recreation, Culture and Religion - broadcasting and publishing		5.2
5.2.4	Recreation, Culture and Religion - religion		5.2
5.3.1	Education - administration, policy and planning		5.3
5.3.2	Education - research		5.3
5.3.3	Education - pre-primary		5.3
5.3.4	Education - primary		5.3
5.3.5	Education - lower secondary		5.3
5.3.6	Education - upper secondary		5.3
5.3.7	Education - post secondary non tertiary		5.3
5.3.8	Education - tertiary		5.3
5.3.9	Education - vocational training		5.3
5.3.10	Education - advanced technical and managerial training		5.3
5.3.11	Education - basic adult education		5.3
5.3.12	Education - teacher training		5.3
5.3.13	Education - subsidiary services		5.3
5.4.1	Social Protection, Land Housing and Community Amenities - policy, planning and administration		5.4
5.4.2	Social Protection, Land Housing and Community Amenities - social security (excl pensions)		5.4
5.4.3	Social Protection, Land Housing and Community Amenities - general pensions		5.4
5.4.4	Social Protection, Land Housing and Community Amenities - civil service and military pensions		5.4
5.4.5	Social Protection, Land Housing and Community Amenities - social services (incl youth development and women+ children)		5.4
5.4.6	Social Protection, Land Housing and Community Amenities - land policy and management		5.4
5.4.7	Social Protection, Land Housing and Community Amenities - rural devt		5.4
5.4.8	Social Protection, Land Housing and Community Amenities - urban devt		5.4
5.4.9	Social Protection, Land Housing and Community Amenities - housing and community amenities		5.4
5.4.10	Social Protection, Land Housing and Community Amenities - emergency relief		5.4
5.4.11	Social Protection, Land Housing and Community Amenities - disaster prevention and preparedness		5.4
5.4.12	Social Protection, Land Housing and Community Amenities - support to refugees and internally displaced persons		5.4
6.1.1	Development Partner affairs - policy planning and administration		6.1
6.1.2	Development Partner affairs - Technical staff services		6.1
7.1.1	External to government sector - External to general government sector		7.1
7.2.1	General Budget Support - General Budget Support		7.2

Budget Identifier Sector

This codelists exists to group the Budget Identifier codelist into sectors. It is not used as a codelist in its own right.

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
1.1	Executive		1
1.2	Legislative		1
1.3	Accountability		1
1.4	External Affairs		1
1.5	General Personnel Services		1
1.6	Statistics		1
1.7	Other General Services		1
1.8	Elections		1
2.1	Justice, Law and Order		2
2.2	Defence		2
3.1	General Economic, Commercial and Labour Affairs		3
3.2	Public Works		3
3.3	Agriculture		3
3.4	Forestry		3
3.5	Fishing and Hunting		3
3.6	Energy		3
3.7	Mining and Mineral Development		3
3.8	Transport		3
3.9	Industry		3
3.10	Communications		3
3.11	Tourism		3
3.12	Microfinance and financial services		3
4.1	Water supply and Sanitation		4
4.2	Environment		4
5.1	Health		5
5.2	Recreation, Culture and Religion		5
5.3	Education		5
5.4	Social Protection, Land Housing and Community Amenities		5
6.1	Development Partner affairs		6
7.1	External to government sector		7
7.2	General Budget Support		7

Budget Identifier Sector (category)

This codelists exists to group the Budget Identifier codelist into categories. It is not used as a codelist in its own right.

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	General Public Service
2	Justice, Law, Order and Security
3	Economic Affairs
4	Water, Natural Resource Management and Environment
5	Social Affairs
6	Development Partner Affairs
7	General Budget Support and Aid support external to General Government Sector

Budget Identifier Vocabulary

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/country-budget-items/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1 (withdrawn)	IATI	The budget identifier reported uses IATI budget identifier categories
2	Country Chart of Accounts	The budget identifier reported corresponds to the recipient country chart of accounts
3	Other Country System	The budget identifier reported corresponds to a recipient country system other than the chart of accounts
4	Reporting Organisation	The budget identifier reported corresponds to categories that are specific to the reporting organisation
5	Other	The budget identifier reported uses a different vocabulary, not specified in the codelist

Budget Not Provided

A codelist defining the reasons why an activity does not contain any iati-activity/budget elements.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/@budget-not-provided

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Commercial Restrictions
2	Legal Restrictions
3	Rapid Onset Emergency

Budget Status

Code to denote if the described budget is binding.

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/budget/@status

• iati-organisations/iati-organisation/total-budget/@status

• iati-organisations/iati-organisation/recipient-org-budget/@status

• iati-organisations/iati-organisation/recipient-region-budget/@status

• iati-organisations/iati-organisation/recipient-country-budget/@status

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Indicative	A non-binding estimate for the described budget.
2	Committed	A binding agreement for the described budget.

Budget Type

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/budget/@type

• iati-activities/iati-activity/planned-disbursement/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Original	The original budget allocated to the activity
2	Revised	The updated budget for an activity

CRS Additional Other Flags

OECD DAC classification used to distinguish aid modalities.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/crs-add/other-flags/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Free standing technical cooperation	Free standing technical cooperation (Col 24 in CRS++ Reporting format)
2	Programme-based approach	Programme-based approach (Col 25 in CRS++ Reporting format)
3	Investment project	Investment project (Col 26 in CRS++ Reporting format)
4	Associated financing	Associated financing (Col 27 in CRS++ Reporting format)

Changelog

2.01

The AidTypeFlag was renamed to CRSAddOtherFlags

CRS Channel Code

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/participating-org/@crs-channel-code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
10000	Public Sector Institutions
11000	Donor Government
11001	Central Government		11000
11002	Local Government		11000
11003	Public corporations		11000
11004	Other public entities in donor country		11000
12000	Recipient Government
12001	Central Government		12000
12002	Local Government		12000
12003	Public corporations		12000
12004	Other public entities in recipient country		12000
13000	Third Country Government (Delegated co-operation)
20000	Non-Governmental Organisation (NGO) and Civil Society
21000	International NGO
21001	Association of Geoscientists for International Development		21000
21002	Agency for International Trade Information and Co-operation		47000
21003	Latin American Council for Social Sciences		23000
21004	Council for the Development of Economic and Social Research in Africa		51000
21005	Consumer Unity and Trust Society International		21000
21006	Development Gateway Foundation		22000
21007	Environmental Liaison Centre International		21000
21008	Eurostep		22000
21009	Forum for Agricultural Research in Africa		51000
21010	Forum for African Women Educationalists		23000
21011	Global Campaign for Education		21000
21013	Health Action International		21000
21014	Human Rights Information and Documentation Systems		22000
21015	International Catholic Rural Association		22000
21016	International Committee of the Red Cross		21000
21017	International Centre for Trade and Sustainable Development		32000
21018	International Federation of Red Cross and Red Crescent Societies		21000
21019	International Federation of Settlements and Neighbourhood Centres		22000
21020	International HIV/AIDS Alliance		21000
21021	International Institute for Environment and Development		51000
21022	International Network for Alternative Financial Institutions		21000
21023	International Planned Parenthood Federation		21000
21024	Inter Press Service, International Association		21000
21025	International Seismological Centre		22000
21026	International Service for Human Rights		22000
21027	ITF Enhancing Human Security		22000
21028	International University Exchange Fund - IUEF Stip. in Africa and Latin America		23000
21029	Doctors Without Borders		21000
21030	Pan African Institute for Development		23000
21031	PANOS Institute		21000
21032	Population Services International		21000
21033	Transparency International		22000
21034	International Union Against Tuberculosis and Lung Disease		21000
21035	World Organisation Against Torture		22000
21036	World University Service		21000
21037	Women’s World Banking		22000
21038	International Alert		21000
21039	International Institute for Sustainable Development		51000
21040	International Women’s Tribune Centre		22000
21041	Society for International Development		21000
21042	International Peacebuilding Alliance		21000
21043	European Parliamentarians for Africa		32000
21044	International Council for the Control of Iodine Deficiency Disorders		21000
21045	African Medical and Research Foundation		21000
21046	Agency for Cooperation and Research in Development		21000
21047	AgriCord		22000
21048	Association of African Universities		23000
21049	European Centre for Development Policy Management		22000
21050	Geneva Call		22000
21051	Institut Supérieur Panafricaine d’Economie Coopérative		23000
21053	IPAS-Protecting Women’s Health, Advancing Women’s Reproductive Rights		21000
21054	Life and Peace Institute		21000
21055	Regional AIDS Training Network		23000
21056	Renewable Energy and Energy Efficiency Partnership		31000
21057	International Centre for Transitional Justice		21000
21058	International Crisis Group		22000
21059	Africa Solidarity Fund		23000
21060	Association for the Prevention of Torture		22000
21061	International Rehabilitation Council for Torture Victims		21000
21062	The Nature Conservancy		21000
21063	Conservation International		21000
21064	Clinton Health Access Initiative, Inc.		21000
21501	OXFAM International		21000
21502	World Vision		21000
21503	Family Health International 360		21000
21504	International Relief and Development		21000
21505	Save the Children		21000
21506	International Rescue Committee		21000
21507	Pact World		21000
22000	Donor country-based NGO
22501	OXFAM - provider country office		22000
22502	Save the Children - donor country office		22000
23000	Developing country-based NGO
23501	National Red Cross and Red Crescent Societies		23000
30000	Public-Private Partnerships (PPP) and Networks
30001	Global Alliance for Improved Nutrition		31000
30003	Global e-Schools and Communities Initiative		31000
30004	Global Water Partnership		31000
30005	International AIDS Vaccine Initiative		31000
30006	International Partnership on Microbicides		31000
30007	Global Alliance for ICT and Development		31000
30008	Cities Alliance		31000
30009	Small Arms Survey		31000
30010	International drug purchase facility		41100
30011	International Union for the Conservation of Nature		31000
30012	Global Climate Partnership Fund		31000
30013	Microfinance Enhancement Facility		31000
30014	Regional Micro, Small and Medium Enterprise Investment Fund for Sub-Saharan Africa		31000
30015	Global Energy Efficiency and Renewable Energy Fund		31000
30016	European Fund for Southeast Europe		31000
30017	SANAD Fund for Micro, Small and Medium Enterprises		31000
31000	Public-Private Partnerships (PPP)
31001	Global Development Network		32000
31002	Global Knowledge Partnership		32000
31003	International Land Coalition		32000
31004	Extractive Industries Transparency Initiative International Secretariat		32000
31005	Parliamentary Network on the World Bank		32000
31006	Coalition for Epidemic Preparedness Innovations		31000
32000	Networks
40000	Multilateral Organisations
41000	United Nations (UN) agency, fund or commission
41100	UN entities (core contributions reportable in full)
41101	Convention to Combat Desertification		41100
41102	Desert Locust Control Organisation for Eastern Africa		41600
41103	Economic Commission for Africa		41100
41104	Economic Commission for Latin America and the Caribbean		41100
41105	Economic and Social Commission for Western Asia		41100
41106	Economic and Social Commission for Asia and the Pacific		41100
41107	International Atomic Energy Agency (Contributions to Technical Cooperation Fund Only)		41100
41108	International Fund for Agricultural Development		41100
41109 (withdrawn)	International Research and Training Institute for the Advancement of Women		41000
41110	Joint United Nations Programme on HIV/AIDS		41100
41111	United Nations Capital Development Fund		41100
41112	United Nations Conference on Trade and Development		41100
41114	United Nations Development Programme		41100
41116	United Nations Environment Programme		41100
41119	United Nations Population Fund		41100
41120	United Nations Human Settlement Programme		41100
41121	United Nations Office of the United Nations High Commissioner for Refugees		41100
41122	United Nations Children’s Fund		41100
41123	United Nations Industrial Development Organisation		41100
41124 (withdrawn)	United Nations Development Fund for Women		41000
41125	United Nations Institute for Training and Research		41100
41126	United Nations Mine Action Service		41600
41127	United Nations Office of Co-ordination of Humanitarian Affairs		41100
41128	United Nations Office on Drugs and Crime		41100
41129	United Nations Research Institute for Social Development		41100
41130	United Nations Relief and Works Agency for Palestine Refugees in the Near East		41100
41131	United Nations System Staff College		41100
41132	United Nations System Standing Committee on Nutrition		41600
41133	United Nations Special Initiative on Africa		41600
41134	United Nations University (including Endowment Fund)		41100
41135	United Nations Volunteers		41100
41136	United Nations Voluntary Fund on Disability		41600
41137	United Nations Voluntary Fund for Technical Co-operation in the Field of Human Rights		41600
41138	United Nations Voluntary Fund for Victims of Torture		41600
41140	World Food Programme		41100
41141	United Nations Peacebuilding Fund		41400
41142	United Nations Democracy Fund		41600
41143	World Health Organisation - core voluntary contributions account		41100
41144	International Labour Organisation - Regular Budget Supplementary Account		41100
41145	International Maritime Organization - Technical Co-operation Fund		41100
41146	United Nations Entity for Gender Equality and the Empowerment of Women		41100
41147	Central Emergency Response Fund		41400
41148	United Nations Department of Political Affairs, Trust Fund in Support of Political Affairs		41500
41149	United Nations Development Coordination Office		41100
41150	United Nations Institute for Disarmament Research		41300
41151	International Agency for Research on Cancer		41300
41300	Other UN (Core Contributions Reportable in Part)
41301	Food and Agricultural Organisation		41300
41302	International Labour Organisation - Assessed Contributions		41300
41303	International Telecommunications Union		41300
41304	United Nations Educational, Scientific and Cultural Organisation		41300
41305	United Nations		41300
41306	Universal Postal Union		41300
41307	World Health Organisation - assessed contributions		41300
41308	World Intellectual Property Organisation		41300
41309	World Meteorological Organisation		41300
41310	United Nations Department of Peacekeeping Operations [only MINURSO, MINUSCA, MINUSMA, MINUJUSTH, MONUSCO, UNAMID, UNIFIL, UNISFA, UNMIK, UNMIL, UNMISS, UNOCI]. Report contributions mission by mission in CRS++.		41300
41311 (withdrawn)	United Nations Peacebuilding Fund (Window One: Flexible Contributions Only)		41000
41312	International Atomic Energy Agency - assessed contributions		41300
41313	United Nations High Commissioner for Human Rights (extrabudgetary contributions only)		41300
41314	United Nations Economic Commission for Europe (extrabudgetary contributions only)		41300
41315	United Nations International Strategy for Disaster Reduction		41300
41316	United Nations Framework Convention on Climate Change		41300
41317	Green Climate Fund		47000
41318	Global Mechanism		41600
41319	World Tourism Organization		41300
41320	Technology Bank for Least Developed Countries		41600
41400	UN inter-agency pooled funds
41401	UN-Multi Partner Trust Fund Office		41400
41500	UN single-agency thematic funds
41501	United Nations Reducing Emissions from Deforestation and Forest Degradation		41600
41502	United Nations Office for Project Services		41300
41503	UN-led Country-based Pooled Funds		41400
41600	Existing UN channels not included in Standard I - UN entity- of the UN Data Cube reporting framework	Canaux existants de l’ONU non inclus dans la norme I - entité des Nations Unies - du cadre de reporting du cube de données de l’ONU
42000	European Union Institutions
42001	European Commission - Development Share of Budget		42000
42003	European Commission - European Development Fund		42000
42004	European Investment Bank		42000
42005 (withdrawn)	Facility for Euro-Mediterranean Investment and Partnership Trust Fund		42000
43000	International Monetary Fund (IMF)
43001	International Monetary Fund - Poverty Reduction and Growth Trust		43000
43002	International Monetary Fund - Poverty Reduction and Growth - Heavily Indebted Poor Countries Debt Relief Initiative Trust Fund [includes HIPC, Extended Credit Facility (ECF), and ECF-HIPC sub-accounts]		43000
43003	International Monetary Fund - Subsidization of Emergency Post Conflict Assistance/Emergency Assistance for Natural Disasters for PRGT-eligible members		43000
43004	International Monetary Fund - Poverty Reduction and Growth - Multilateral Debt Relief Initiative Trust		43000
43005	International Monetary Fund - Post-Catastrophe Debt Relief Trust		43000
43006	Catastrophe Containment and Relief Trust		43000
44000	World Bank Group (WB)
44001	International Bank for Reconstruction and Development		44000
44002	International Development Association		44000
44003	International Development Association - Heavily Indebted Poor Countries Debt Initiative Trust Fund		44000
44004	International Finance Corporation		44000
44005	Multilateral Investment Guarantee Agency		44000
44006	Advance Market Commitments		44000
44007	International Development Association - Multilateral Debt Relief Initiative		44000
45000	World Trade Organisation (WTO)
45001	World Trade Organisation - International Trade Centre		41100
45002	World Trade Organisation - Advisory Centre on WTO Law		41100
45003	World Trade Organisation - Doha Development Agenda Global Trust Fund		41100
46000	Regional Development Banks
46002	African Development Bank		46000
46003	African Development Fund		46000
46004	Asian Development Bank		46000
46005	Asian Development Fund		46000
46006	Black Sea Trade and Development Bank		46000
46007	Central American Bank for Economic Integration		46000
46008	Development Bank of Latin America		46000
46009	Caribbean Development Bank		46000
46012	Inter-American Development Bank, Inter-American Investment Corporation and Multilateral Investment Fund		46000
46013	Inter-American Development Bank, Fund for Special Operations		46000
46015	European Bank for Reconstruction and Development		46000
46016	European Bank for Reconstruction and Development – technical co-operation and special funds (ODA-eligible countries only)		46000
46017	European Bank for Reconstruction and Development – technical co-operation and special funds (all EBRD countries of operations)		46000
46018	European Bank for Reconstruction and Development - Early Transition Countries Fund		46000
46019	European Bank for Reconstruction and Development - Western Balkans Joint Trust Fund		46000
46020	Central African States Development Bank		46000
46021	West African Development Bank		46000
46022	African Export Import Bank		46000
46023	Eastern and Southern African Trade and Development Bank		46000
46024	Council of Europe Development Bank		46000
46025	Islamic Development Bank		46000
46026	Asian Infrastructure Investment Bank		46000
46027	Financial Fund for the Development of the River Plate Basin		46000
47000	Other multilateral institutions
47001	African Capacity Building Foundation		47000
47002	Asian Productivity Organisation		47000
47003	Association of South East Asian Nations: Economic Co-operation		47000
47004 (withdrawn)	ASEAN Cultural Fund		47000
47005	African Union (excluding peacekeeping facilities)		47000
47008	World Vegetable Centre		51000
47009	African and Malagasy Council for Higher Education		47000
47010	Commonwealth Agency for Public Administration and Management		32000
47011	Caribbean Community Secretariat		47000
47012	Caribbean Epidemiology Centre		47000
47013	Commonwealth Foundation		47000
47014 (withdrawn)	Commonwealth Fund for Technical Co-operation		47000
47015	CGIAR Fund		47000
47016 (withdrawn)	Commonwealth Institute		47000
47017	International Centre for Tropical Agriculture		51000
47018	Centre for International Forestry Research		51000
47019	International Centre for Advanced Mediterranean Agronomic Studies		47000
47020	International Maize and Wheat Improvement Centre		51000
47021	International Potato Centre		51000
47022	Convention on International Trade in Endangered Species of Wild Flora and Fauna		47000
47023 (withdrawn)	Commonwealth Legal Advisory Service		47000
47024 (withdrawn)	Commonwealth Media Development Fund		47000
47025	Commonwealth of Learning		47000
47026	Community of Portuguese Speaking Countries		47000
47027	Colombo Plan		47000
47028	Commonwealth Partnership for Technical Management		32000
47029	Sahel and West Africa Club		47000
47030 (withdrawn)	Commonwealth Scientific Council		47000
47031 (withdrawn)	Commonwealth Small States Office		47000
47032 (withdrawn)	Commonwealth Trade and Investment Access Facility		47000
47033 (withdrawn)	Commonwealth Youth Programme		47000
47034	Economic Community of West African States		47000
47035	Environmental Development Action in the Third World		21000
47036	European and Mediterranean Plant Protection Organisation		47000
47037	Eastern-Regional Organisation of Public Administration		47000
47038 (withdrawn)	INTERPOL Fund for Aid and Technical Assistance to Developing Countries		47000
47040	Forum Fisheries Agency		47000
47041	Food and Fertilizer Technology Centre		51000
47042	Foundation for International Training		22000
47043	Global Crop Diversity Trust		31000
47044	Global Environment Facility Trust Fund		47000
47045	Global Fund to Fight AIDS, Tuberculosis and Malaria		47000
47046	International Organisation of the Francophonie		47000
47047	International African Institute		51000
47048 (withdrawn)	Inter-American Indian Institute		47000
47049 (withdrawn)	International Bureau of Education - International Educational Reporting System (IERS)		47000
47050	International Cotton Advisory Committee		47000
47051	International Centre for Agricultural Research in Dry Areas		51000
47053	International Centre for Diarrhoeal Disease Research, Bangladesh		51000
47054	International Centre of Insect Physiology and Ecology		51000
47055	International Centre for Development Oriented Research in Agriculture		51000
47056	World AgroForestry Centre		51000
47057	International Crop Research for Semi-Arid Tropics		51000
47058	International Institute for Democracy and Electoral Assistance		47000
47059	International Development Law Organisation		47000
47060 (withdrawn)	International Institute for Cotton		47000
47061	Inter-American Institute for Co-operation on Agriculture		47000
47062	International Institute of Tropical Agriculture		51000
47063	International Livestock Research Institute		51000
47064	International Network for Bamboo and Rattan		47000
47065	Intergovernmental Oceanographic Commission		41600
47066	International Organisation for Migration		41100
47067	Intergovernmental Panel on Climate Change		47000
47068	Asia-Pacific Fishery Commission		47000
47069	Bioversity International		51000
47070	International Rice Research Institute		51000
47071	International Seed Testing Association		51000
47073	International Tropical Timber Organisation		47000
47074	International Vaccine Institute		47000
47075	International Water Management Institute		51000
47076	Justice Studies Centre of the Americas		47000
47077	Mekong River Commission		47000
47078	Multilateral Fund for the Implementation of the Montreal Protocol		41600
47079	Organisation of American States		47000
47080	Organisation for Economic Co-operation and Development (Contributions to special funds for Technical Co-operation Activities Only)		47000
47081	OECD Development Centre		47000
47082	Organisation of Eastern Caribbean States		47000
47083	Pan-American Health Organisation		41100
47084	Pan-American Institute of Geography and History		47000
47085 (withdrawn)	Pan-American Railway Congress Association		47000
47086	Private Infrastructure Development Group		47000
47087	Pacific Islands Forum Secretariat		47000
47088 (withdrawn)	Relief Net		47000
47089	Southern African Development Community		47000
47090 (withdrawn)	Southern African Transport and Communications Commission		47000
47091 (withdrawn)	(Colombo Plan) Special Commonwealth African Assistance Programme		47000
47092	South East Asian Fisheries Development Centre		47000
47093	South East Asian Ministers of Education		47000
47094 (withdrawn)	South Pacific Applied Geoscience Commission		47000
47095	South Pacific Board for Educational Assessment		47000
47096	Secretariat of the Pacific Community		47000
47097	Pacific Regional Environment Programme		47000
47098	Unrepresented Nations and Peoples’ Organisation		47000
47099	University of the South Pacific		51000
47100	West African Monetary Union		47000
47101	Africa Rice Centre		51000
47102 (withdrawn)	World Customs Organisation Fellowship Programme		47000
47103	World Maritime University		51000
47104	WorldFish Centre		51000
47105	Common Fund for Commodities		47000
47106	Geneva Centre for the Democratic Control of Armed Forces		47000
47107	International Finance Facility for Immunisation		47000
47108 (withdrawn)	Multi-Country Demobilisation and Reintegration Program		47000
47109	Asia-Pacific Economic Cooperation Support Fund (except contributions tied to counter-terrorism activities)		47000
47110	Organisation of the Black Sea Economic Cooperation		47000
47111	Adaptation Fund		47000
47112	Central European Initiative - Special Fund for Climate and Environmental Protection		47000
47113	Economic and Monetary Community of Central Africa		47000
47116	Integrated Framework for Trade-Related Technical Assistance to Least Developed Countries		47000
47117	New Partnership for Africa’s Development		47000
47118	Regional Organisation for the Strengthening of Supreme Audit Institutions of Francophone Sub-Saharan Countries		47000
47119	Sahara and Sahel Observatory		47000
47120	South Asian Association for Regional Cooperation		47000
47121	United Cities and Local Governments of Africa		47000
47122	Global Alliance for Vaccines and Immunization		47000
47123	Geneva International Centre for Humanitarian Demining		47000
47127	Latin-American Energy Organisation		47000
47128	Nordic Development Fund		47000
47129	Global Environment Facility - Least Developed Countries Fund		47000
47130	Global Environment Facility - Special Climate Change Fund		47000
47131	Organization for Security and Co-operation in Europe		47000
47132	Commonwealth Secretariat (ODA-eligible contributions only)		47000
47134	Clean Technology Fund		47000
47135	Strategic Climate Fund		47000
47136	Global Green Growth Institute		47000
47137	African Risk Capacity Group		47000
47138	Council of Europe		47000
47139	World Customs Organization Customs Co-operation Fund		47000
47140	Organisation of Ibero-American States for Education, Science and Culture		47000
47141	African Tax Administration Forum		47000
47142	OPEC Fund for International Development		47000
47143	Global Community Engagement and Resilience Fund		47000
47144	International Renewable Energy Agency		47000
47145	Center of Excellence in Finance		47000
47146	International Investment Bank		47000
47147	International Finance Facility for Education		47000
47148	World Organisation for Animal Health		47000
47400	European Space Agency (ESA) programme ‘Space in support of International Development Aid’		47000
47501	Global Partnership for Education		47000
47502	Global Fund for Disaster Risk Reduction		47000
47503	Global Agriculture and Food Security Program		47000
47504	Forest Carbon Partnership Facility		47000
50000 (withdrawn)	Others
51000	University, college or other teaching institution, research institute or think-tank
51001	International Food Policy Research Institute		51000
52000 (withdrawn)	Other
60000	Private Sector Institutions
61000	Private sector in provider country
61001	Banks (deposit taking corporations)		61000
61002 (withdrawn)	Private exporter in provider country		61000
61003	Investment funds and other collective investment institutions		61000
61004	Holding companies, trusts and Special Purpose Vehicles		61000
61005	Insurance Corporations		61000
61006	Pension Funds		61000
61007	Other financial corporations		61000
61008	Exporters		61000
61009	Other non-financial corporations		61000
61010	Retail investors		61000
62000	Private sector in recipient country
62001	Banks (deposit taking corporations except Micro Finance Institutions)		62000
62002	Micro Finance Institutions (deposit and non-deposit)		62000
62003	Investment funds and other collective investment institutions		62000
62004	Holding companies, trusts and Special Purpose Vehicles		62000
62005	Insurance Corporations		62000
62006	Pension Funds		62000
62007	Other financial corporations		62000
62008	Importers/Exporters		62000
62009	Other non-financial corporations		62000
62010	Retail investors		62000
63000	Private sector in third country
63001	Banks (deposit taking corporations except Micro Finance Institutions)		63000
63002	Micro Finance Institutions (deposit and non-deposit)		63000
63003	Investment funds and other collective investment institutions		63000
63004	Holding companies, trusts and Special Purpose Vehicles		63000
63005	Insurance Corporations		63000
63006	Pension Funds		63000
63007	Other financial corporations		63000
63008	Exporters		63000
63009	Other non-financial corporations		63000
63010	Retail investors		63000
90000	Other

Cash and Voucher Modalities

This codelist has been created by IATI following agreements and recommendations of the Tracking Cash and Voucher Assistance (CVA) Working Group. Definitions of the codes have been aligned with the CaLP Glossary:http://www.cashlearning.org/resources/glossary.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/default-aid-type/@code

• iati-activities/iati-activity/transaction/aid-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Cash Transfer	The provision of assistance in the form of money - either physical currency or e-cash - to recipients (individuals, households or communities). Cash transfers are by definition unrestricted in terms of use and distinct from restricted modalities including vouchers and in-kind assistance.
2	Voucher	A paper, token or e-voucher that can be exchanged for a set quantity or value of goods or services, denominated either as a cash value (e.g. $15) or predetermined commodities (e.g. 5 kg maize) or specific services (e.g. milling of 5 kg of maize), or a combination of value and commodities. Vouchers are restricted by default, although the degree of restriction will vary based on the programme design and type of voucher. They are redeemable with preselected vendors or in ‘fairs’ created by the implementing agency. The terms vouchers, stamps, or coupons might be used interchangeably.

Collaboration Type

OECD DAC classification used to determine the character of resource flows (bilateral or multilateral).

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/collaboration-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Bilateral
2	Multilateral (inflows)
3	Bilateral, core contributions to NGOs and other private bodies / PPPs
4	Multilateral outflows
6	Private Sector Outflows
7	Bilateral, ex-post reporting on NGOs’ activities funded through core contributions
8	Bilateral, triangular co-operation.	Activities where one or more bilateral providers of development co-operation or international organisations support South-South co-operation, joining forces with developing countries to facilitate a sharing of knowledge and experience among all partners involved. (Activities that only involve bilateral providers or multilateral agencies without a South-South co-operation element (e.g. joint programming, pooled funding or delegated co-operation) should not be assigned bi_multi 8.)

Condition Type

Condition type – e.g. policy, performance.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/conditions/condition/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Policy	The condition attached requires a particular policy to be implemented by the recipient
2	Performance	The condition attached requires certain outputs or outcomes to be achieved by the recipient
3	Fiduciary	The condition attached requires use of certain public financial management or public accountability measures by the recipient

Contact Type

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/contact-info/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	General Enquiries	General Enquiries
2	Project Management	Project Management
3	Financial Management	Financial Management
4	Communications	Communications

Country

The Country codelist is generated from the ISO 3166-1 part of the ISO 3166 standard. The standard makes allowance, alongside the officially assigned codes, for code elements to be expanded by using either reserved codes or user-assigned codes. IATI currently defines additional codes in the XA -XZ range.

External URL: http://www.iso.org/iso/home/standards/country_codes.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/recipient-country/@code

• iati-activities/iati-activity/location/administrative/@code

• iati-activities/iati-activity/transaction/recipient-country/@code

• iati-organisations/iati-organisation/recipient-country-budget/recipient-country/@code

• iati-organisations/iati-organisation/document-link/recipient-country/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
AF	Afghanistan
AX	Åland Islands
AL	Albania
DZ	Algeria
AS	American Samoa
AD	Andorra
AO	Angola
AI	Anguilla
AQ	Antarctica
AG	Antigua and Barbuda
AR	Argentina
AM	Armenia
AW	Aruba
AU	Australia
AT	Austria
AZ	Azerbaijan
BS	Bahamas (the)
BH	Bahrain
BD	Bangladesh
BB	Barbados
BY	Belarus
BE	Belgium
BZ	Belize
BJ	Benin
BM	Bermuda
BT	Bhutan
BO	Bolivia (Plurinational State of)
BQ	Bonaire, Sint Eustatius and Saba
BA	Bosnia and Herzegovina
BW	Botswana
BV	Bouvet Island
BR	Brazil
IO	British Indian Ocean Territory (the)
BN	Brunei Darussalam
BG	Bulgaria
BF	Burkina Faso
BI	Burundi
KH	Cambodia
CM	Cameroon
CA	Canada
CV	Cabo Verde
KY	Cayman Islands (the)
CF	Central African Republic (the)
TD	Chad
CL	Chile
CN	China
CX	Christmas Island
CC	Cocos (Keeling) Islands (the)
CO	Colombia
KM	Comoros (the)
CG	Congo (the)
CD	Congo (the Democratic Republic of the)
CK	Cook Islands (the)
CR	Costa Rica
CI	Côte d’Ivoire
HR	Croatia
CU	Cuba
CW	Curaçao
CY	Cyprus
CZ	Czechia
DK	Denmark
DJ	Djibouti
DM	Dominica
DO	Dominican Republic (the)
EC	Ecuador
EG	Egypt
SV	El Salvador
GQ	Equatorial Guinea
ER	Eritrea
EE	Estonia
ET	Ethiopia
FK	Falkland Islands (the) [Malvinas]
FO	Faroe Islands (the)
FJ	Fiji
FI	Finland
FR	France
GF	French Guiana
PF	French Polynesia
TF	French Southern Territories (the)
GA	Gabon
GM	Gambia (the)
GE	Georgia
DE	Germany
GH	Ghana
GI	Gibraltar
GR	Greece
GL	Greenland
GD	Grenada
GP	Guadeloupe
GU	Guam
GT	Guatemala
GG	Guernsey
GN	Guinea
GW	Guinea-Bissau
GY	Guyana
HT	Haiti
HM	Heard Island and McDonald Islands
VA	Holy See (the)
HN	Honduras
HK	Hong Kong
HU	Hungary
IS	Iceland
IN	India
ID	Indonesia
IR	Iran (Islamic Republic of)
IQ	Iraq
IE	Ireland
IM	Isle of Man
IL	Israel
IT	Italy
JM	Jamaica
JP	Japan
JE	Jersey
JO	Jordan
KZ	Kazakhstan
KE	Kenya
KI	Kiribati
KP	Korea (the Democratic People’s Republic of)
KR	Korea (the Republic of)
XK	Kosovo
KW	Kuwait
KG	Kyrgyzstan
LA	Lao People’s Democratic Republic (the)
LV	Latvia
LB	Lebanon
LS	Lesotho
LR	Liberia
LY	Libya
LI	Liechtenstein
LT	Lithuania
LU	Luxembourg
MO	Macao
MK	North Macedonia
MG	Madagascar
MW	Malawi
MY	Malaysia
MV	Maldives
ML	Mali
MT	Malta
MH	Marshall Islands (the)
MQ	Martinique
MR	Mauritania
MU	Mauritius
YT	Mayotte
MX	Mexico
FM	Micronesia (Federated States of)
MD	Moldova (the Republic of)
MC	Monaco
MN	Mongolia
ME	Montenegro
MS	Montserrat
MA	Morocco
MZ	Mozambique
MM	Myanmar
NA	Namibia
NR	Nauru
NP	Nepal
NL	Netherlands (the)
AN (withdrawn)	NETHERLAND ANTILLES
NC	New Caledonia
NZ	New Zealand
NI	Nicaragua
NE	Niger (the)
NG	Nigeria
NU	Niue
NF	Norfolk Island
MP	Northern Mariana Islands (the)
NO	Norway
OM	Oman
PK	Pakistan
PW	Palau
PS	Palestine, State of
PA	Panama
PG	Papua New Guinea
PY	Paraguay
PE	Peru
PH	Philippines (the)
PN	Pitcairn
PL	Poland
PT	Portugal
PR	Puerto Rico
QA	Qatar
RE	Réunion
RO	Romania
RU	Russian Federation (the)
RW	Rwanda
BL	Saint Barthélemy
SH	Saint Helena, Ascension and Tristan da Cunha
KN	Saint Kitts and Nevis
LC	Saint Lucia
MF	Saint Martin (French part)
PM	Saint Pierre and Miquelon
VC	Saint Vincent and the Grenadines
WS	Samoa
SM	San Marino
ST	Sao Tome and Principe
SA	Saudi Arabia
SN	Senegal
RS	Serbia
SC	Seychelles
SL	Sierra Leone
SG	Singapore
SX	Sint Maarten (Dutch part)
SK	Slovakia
SI	Slovenia
SB	Solomon Islands
SO	Somalia
ZA	South Africa
GS	South Georgia and the South Sandwich Islands
SS	South Sudan
ES	Spain
LK	Sri Lanka
SD	Sudan (the)
SR	Suriname
SJ	Svalbard and Jan Mayen
SZ	Eswatini
SE	Sweden
CH	Switzerland
SY	Syrian Arab Republic
TW	Taiwan (Province of China)
TJ	Tajikistan
TZ	Tanzania, United Republic of
TH	Thailand
TL	Timor-Leste
TG	Togo
TK	Tokelau
TO	Tonga
TT	Trinidad and Tobago
TN	Tunisia
TR	Turkey
TM	Turkmenistan
TC	Turks and Caicos Islands (the)
TV	Tuvalu
UG	Uganda
UA	Ukraine
AE	United Arab Emirates (the)
GB	United Kingdom of Great Britain and Northern Ireland (the)
US	United States of America (the)
UM	United States Minor Outlying Islands (the)
UY	Uruguay
UZ	Uzbekistan
VU	Vanuatu
VE	Venezuela (Bolivarian Republic of)
VN	Viet Nam
VG	Virgin Islands (British)
VI	Virgin Islands (U.S.)
WF	Wallis and Futuna
EH	Western Sahara
YE	Yemen
ZM	Zambia
ZW	Zimbabwe

Currency

ISO 4217 Currency used for all transactions and budgets

External URL: http://www.iso.org/iso/home/standards/currency_codes.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/budget/value/@currency

• iati-activities/iati-activity/planned-disbursement/value/@currency

• iati-activities/iati-activity/transaction/value/@currency

• iati-activities/iati-activity/crs-add/loan-status/@currency

• iati-activities/iati-activity/fss/forecast/@currency

• iati-activities/iati-activity/@default-currency

• iati-organisations/iati-organisation/total-budget/value/@currency

• iati-organisations/iati-organisation/recipient-org-budget/value/@currency

• iati-organisations/iati-organisation/recipient-org-budget/budget-line/value/@currency

• iati-organisations/iati-organisation/recipient-region-budget/value/@currency

• iati-organisations/iati-organisation/recipient-region-budget/budget-line/value/@currency

• iati-organisations/iati-organisation/recipient-country-budget/value/@currency

• iati-organisations/iati-organisation/recipient-country-budget/budget-line/value/@currency

• iati-organisations/iati-organisation/@default-currency

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
AED	UAE Dirham
AFN	Afghani
ALL	Lek
AMD	Armenian Dram
ANG	Netherlands Antillian Guilder
AOA	Kwanza
ARS	Argentine Peso
AUD	Australian Dollar
AWG	Aruban Guilder
AZN	Azerbaijanian Manat
BAM	Convertible Marks
BBD	Barbados Dollar
BDT	Taka
BGN	Bulgarian Lev
BHD	Bahraini Dinar
BIF	Burundi Franc
BMD	Bermudian Dollar
BND	Brunei Dollar
BOB	Boliviano
BOV	Mvdol
BRL	Brazilian Real
BSD	Bahamian Dollar
BTN	Ngultrum
BWP	Pula
BYR (withdrawn)	Belarussian Ruble	Withdrawn from ISO Currency codelist. Use code BYN.
BYN	Belarussian Ruble
BZD	Belize Dollar
CAD	Canadian Dollar
CDF	Congolese Franc
CHF	Swiss Franc
CLF	Unidades de fomento
CLP	Chilean Peso
CNY	Yuan Renminbi
COP	Colombian Peso
COU	Unidad de Valor Real
CRC	Costa Rican Colon
CUC	Peso Convertible
CUP	Cuban Peso
CVE	Cape Verde Escudo
CZK	Czech Koruna
DJF	Djibouti Franc
DKK	Danish Krone
DOP	Dominican Peso
DZD	Algerian Dinar
EEK (withdrawn)	Kroon	Withdrawn from ISO Currency codelist
EGP	Egyptian Pound
ERN	Nakfa
ETB	Ethiopian Birr
EUR	Euro
FJD	Fiji Dollar
FKP	Falkland Islands Pound
GBP	Pound Sterling
GEL	Lari
GHS	Cedi
GIP	Gibraltar Pound
GMD	Dalasi
GNF	Guinea Franc
GTQ	Quetzal
GYD	Guyana Dollar
HKD	Hong Kong Dollar
HNL	Lempira
HRK	Kuna
HTG	Gourde
HUF	Forint
IDR	Rupiah
ILS	New Israeli Sheqel
INR	Indian Rupee
IQD	Iraqi Dinar
IRR	Iranian Rial
ISK	Iceland Krona
JMD	Jamaican Dollar
JOD	Jordanian Dinar
JPY	Yen
KES	Kenyan Shilling
KGS	Som
KHR	Riel
KMF	Comoro Franc
KPW	North Korean Won
KRW	Won
KWD	Kuwaiti Dinar
KYD	Cayman Islands Dollar
KZT	Tenge
LAK	Kip
LBP	Lebanese Pound
LKR	Sri Lanka Rupee
LRD	Liberian Dollar
LSL	Loti
LTL (withdrawn)	Lithuanian Litas	Withdrawn from ISO Currency codelist
LVL (withdrawn)	Latvian Lats	Withdrawn from ISO Currency codelist
LYD	Libyan Dinar
MAD	Moroccan Dirham
MDL	Moldovan Leu
MGA	Malagasy Ariary
MKD	Denar
MMK	Kyat
MNT	Tugrik
MOP	Pataca
MRO (withdrawn)	Ouguiya	Withdrawn from ISO Currency codelist. Use code MRU.
MRU	Ouguiya
MUR	Mauritius Rupee
MVR	Rufiyaa
MWK	Malawi Kwacha
MXN	Mexican Peso
MXV	Mexican Unidad de Inversion (UDI)
MYR	Malaysian Ringgit
MZN	Metical
NAD	Namibia Dollar
NGN	Naira
NIO	Cordoba Oro
NOK	Norwegian Krone
NPR	Nepalese Rupee
NZD	New Zealand Dollar
OMR	Rial Omani
PAB	Balboa
PEN	Nuevo Sol
PGK	Kina
PHP	Philippine Peso
PKR	Pakistan Rupee
PLN	Zloty
PYG	Guarani
QAR	Qatari Rial
RON	Romanian Leu
RSD	Serbian Dinar
RUB	Russian Ruble
RWF	Rwanda Franc
SAR	Saudi Riyal
SBD	Solomon Islands Dollar
SCR	Seychelles Rupee
SDG	Sudanese Pound
SEK	Swedish Krona
SGD	Singapore Dollar
SHP	Saint Helena Pound
SLL	Leone
SOS	Somali Shilling
SSP	South Sudanese Pound
SRD	Surinam Dollar
STD (withdrawn)	Dobra	Withdrawn from ISO Currency codelist. Use code STN.
STN	Dobra
SVC	El Salvador Colon
SYP	Syrian Pound
SZL	Lilangeni
THB	Baht
TJS	Somoni
TMT	Manat
TND	Tunisian Dinar
TOP	Paanga
TRY	Turkish Lira
TTD	Trinidad and Tobago Dollar
TWD	New Taiwan Dollar
TZS	Tanzanian Shilling
UAH	Hryvnia
UGX	Uganda Shilling
USD	US Dollar
USN	US Dollar (Next day)
USS (withdrawn)	US Dollar (Same day)	Withdrawn from ISO Currency codelist.
UYI	Uruguay Peso en Unidades Indexadas
UYU	Peso Uruguayo
UZS	Uzbekistan Sum
VEF (withdrawn)	Bolivar
VES	Bolivar Soberano
VND	Dong
VUV	Vatu
WST	Tala
XAF	CFA Franc BEAC
XBT	Bitcoin
XCD	East Caribbean Dollar
XDR	International Monetary Fund (IMF) Special Drawing Right (SDR)
XOF	CFA Franc BCEAO
XPF	CFP Franc
YER	Yemeni Rial
ZAR	Rand
ZMK (withdrawn)	Zambian Kwacha	Withdrawn from ISO Country codelist. Use code ZMW.
ZMW	Zambian Kwacha
ZWL	Zimbabwe Dollar

Description Type

Activity decription types. (General, objectives, etc)

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/description/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	General	Unstructured, long description of the activity
2	Objectives	Specific objectives for the activity, e.g. taken from logical framework
3	Target Groups	Details of groups that are intended to benefit from the activity
4	Other	For miscellaneous use. A further classification or breakdown may be included in the narrative

Disbursement Channel

Categories of information included in published documents

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/transaction/disbursement-channel/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Money is disbursed through central Ministry of Finance or Treasury	Money is disbursed through central Ministry of Finance or Treasury
2	Money is disbursed directly to the implementing institution and managed through a separate bank account	Money is disbursed directly to the implementing institution and managed through a separate bank account
3	Aid in kind: Donors utilise third party agencies, e.g. NGOs or management companies	Aid in kind: Donors utilise third party agencies, e.g. NGOs or management companies
4	Aid in kind: Donors manage funds themselves	Aid in kind: Donors manage funds themselves

Document Category

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/document-link/category/@code

• iati-activities/iati-activity/result/document-link/category/@code

• iati-activities/iati-activity/result/indicator/document-link/category/@code

• iati-activities/iati-activity/result/indicator/baseline/document-link/category/@code

• iati-activities/iati-activity/result/indicator/period/target/document-link/category/@code

• iati-activities/iati-activity/result/indicator/period/actual/document-link/category/@code

• iati-organisations/iati-organisation/document-link/category/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
A01	Pre- and post-project impact appraisal		A
A02	Objectives / Purpose of activity		A
A03	Intended ultimate beneficiaries		A
A04	Conditions		A
A05	Budget		A
A06	Summary information about contract		A
A07	Review of project performance and evaluation		A
A08	Results, outcomes and outputs		A
A09	Memorandum of understanding (If agreed by all parties)		A
A10	Tender		A
A11	Contract		A
A12	Activity web page		A
B01	Annual report		B
B02	Institutional Strategy paper		B
B03	Country strategy paper		B
B04	Aid Allocation Policy		B
B05	Procurement Policy and Procedure		B
B06	Institutional Audit Report		B
B07	Country Audit Report		B
B08	Exclusions Policy		B
B09	Institutional Evaluation Report		B
B10	Country Evaluation Report		B
B11	Sector strategy		B
B12	Thematic strategy		B
B13	Country-level Memorandum of Understanding		B
B14	Evaluations policy		B
B15	General Terms and Conditions		B
B16	Organisation web page		B
B17	Country/Region web page		B
B18	Sector web page		B

Changelog

2.01

The following new codes were added to DocumentCategory: A12; B16; B17; B18

Document Category (category)

This codelists exists to group the Document Category codelist into categories. It is not used as a codelist in its own right.

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
A	Activity Level	The document is relevant to a specific activity
B	Organisation Level	The document is relevant to the organisation as a whole

Earmarking Category

This codelist has been created by IATI and is derived from the Grand Bargain Earmarking Modality codelist.

External URL: https://reliefweb.int/sites/reliefweb.int/files/resources/Grand_Bargain_final_22_May_FINAL-2.pdf

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/default-aid-type/@code

• iati-activities/iati-activity/transaction/aid-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Unearmarked	Any or all of the Earmarking Modality codes A,B or C.
2	Softly Earmarked	Any or all of the Earmarking Modality codes D,E or F.
3	Earmarked	Any or all of the Earmarking Modality codes G or H.
4	Tightly Earmarked	Any or all of the Earmarking Modality codes I,J or K.

File Format

File format of published documents.

External URL: http://www.iana.org/assignments/media-types

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/document-link/@format

• iati-activities/iati-activity/result/document-link/@format

• iati-activities/iati-activity/result/indicator/document-link/@format

• iati-activities/iati-activity/result/indicator/baseline/document-link/@format

• iati-activities/iati-activity/result/indicator/period/target/document-link/@format

• iati-activities/iati-activity/result/indicator/period/actual/document-link/@format

• iati-organisations/iati-organisation/document-link/@format

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
application/1d-interleaved-parityfec			application
application/3gpdash-qoe-report+xml			application
application/3gpp-ims+xml			application
application/A2L			application
application/activemessage			application
application/activemessage			application
application/alto-costmap+json			application
application/alto-costmapfilter+json			application
application/alto-directory+json			application
application/alto-endpointprop+json			application
application/alto-endpointpropparams+json			application
application/alto-endpointcost+json			application
application/alto-endpointcostparams+json			application
application/alto-error+json			application
application/alto-networkmapfilter+json			application
application/alto-networkmap+json			application
application/AML			application
application/andrew-inset			application
application/applefile			application
application/ATF			application
application/ATFX			application
application/atom+xml			application
application/atomcat+xml			application
application/atomdeleted+xml			application
application/atomicmail			application
application/atomsvc+xml			application
application/ATXML			application
application/auth-policy+xml			application
application/bacnet-xdd+zip			application
application/batch-SMTP			application
application/beep+xml			application
application/calendar+json			application
application/calendar+xml			application
application/call-completion			application
application/CALS-1840			application
application/cbor			application
application/ccmp+xml			application
application/ccxml+xml			application
application/CDFX+XML			application
application/cdmi-capability			application
application/cdmi-container			application
application/cdmi-domain			application
application/cdmi-object			application
application/cdmi-queue			application
application/cdni			application
application/CEA			application
application/cea-2018+xml			application
application/cellml+xml			application
application/cfw			application
application/clue_info+xml			application
application/cms			application
application/cnrp+xml			application
application/coap-group+json			application
application/coap-payload			application
application/commonground			application
application/conference-info+xml			application
application/cpl+xml			application
application/cose			application
application/cose-key			application
application/cose-key-set			application
application/csrattrs			application
application/csta+xml			application
application/CSTAdata+xml			application
application/csvm+json			application
application/cybercash			application
application/dash+xml			application
application/dashdelta			application
application/davmount+xml			application
application/dca-rft			application
application/DCD			application
application/dec-dx			application
application/dialog-info+xml			application
application/dicom			application
application/dicom+json			application
application/dicom+xml			application
application/DII			application
application/DIT			application
application/dns			application
application/dskpp+xml			application
application/dssc+der			application
application/dssc+xml			application
application/dvcs			application
application/ecmascript			application
application/EDI-consent			application
application/EDIFACT			application
application/EDI-X12			application
application/efi			application
application/EmergencyCallData.Comment+xml			application
application/EmergencyCallData.Control+xml			application
application/EmergencyCallData.DeviceInfo+xml			application
application/EmergencyCallData.eCall.MSD			application
application/EmergencyCallData.ProviderInfo+xml			application
application/EmergencyCallData.ServiceInfo+xml			application
application/EmergencyCallData.SubscriberInfo+xml			application
application/EmergencyCallData.VEDS+xml			application
application/emma+xml			application
application/emotionml+xml			application
application/encaprtp			application
application/epp+xml			application
application/epub+zip			application
application/eshop			application
application/example			application
application/exi			application
application/fastinfoset			application
application/fastsoap			application
application/fdt+xml			application
application/fits			application
application/font-sfnt (withdrawn)			application
application/font-tdpfr			application
application/font-woff (withdrawn)			application
application/framework-attributes+xml			application
application/geo+json			application
application/geo+json-seq			application
application/gml+xml			application
application/gzip			application
application/H224			application
application/held+xml			application
application/http			application
application/hyperstudio			application
application/ibe-key-request+xml			application
application/ibe-pkg-reply+xml			application
application/ibe-pp-data			application
application/iges			application
application/im-iscomposing+xml			application
application/index			application
application/index.cmd			application
application/index.obj			application
application/index.response			application
application/index.vnd			application
application/inkml+xml			application
application/iotp			application
application/ipfix			application
application/ipp			application
application/isup			application
application/its+xml			application
application/javascript			application
application/jose			application
application/jose+json			application
application/jrd+json			application
application/json			application
application/json-patch+json			application
application/json-seq			application
application/jwk+json			application
application/jwk-set+json			application
application/jwt			application
application/kpml-request+xml			application
application/kpml-response+xml			application
application/ld+json			application
application/lgr+xml			application
application/link-format			application
application/load-control+xml			application
application/lost+xml			application
application/lostsync+xml			application
application/LXF			application
application/mac-binhex40			application
application/macwriteii			application
application/mads+xml			application
application/marc			application
application/marcxml+xml			application
application/mathematica			application
application/mathml-content+xml			application
application/mathml-presentation+xml			application
application/mathml+xml			application
application/mbms-associated-procedure-description+xml			application
application/mbms-deregister+xml			application
application/mbms-envelope+xml			application
application/mbms-msk-response+xml			application
application/mbms-msk+xml			application
application/mbms-protection-description+xml			application
application/mbms-reception-report+xml			application
application/mbms-register-response+xml			application
application/mbms-register+xml			application
application/mbms-schedule+xml			application
application/mbms-user-service-description+xml			application
application/mbox			application
application/media_control+xml			application
application/media-policy-dataset+xml			application
application/mediaservercontrol+xml			application
application/merge-patch+json			application
application/metalink4+xml			application
application/mets+xml			application
application/MF4			application
application/mikey			application
application/mods+xml			application
application/moss-keys			application
application/moss-signature			application
application/mosskey-data			application
application/mosskey-request			application
application/mp21			application
application/mp4			application
application/mpeg4-generic			application
application/mpeg4-iod			application
application/mpeg4-iod-xmt			application
application/mrb-consumer+xml			application
application/mrb-publish+xml			application
application/msc-ivr+xml			application
application/msc-mixer+xml			application
application/msword			application
application/mud+json			application
application/mxf			application
application/n-quads			application
application/n-triples			application
application/nasdata			application
application/news-checkgroups			application
application/news-groupinfo			application
application/news-transmission			application
application/nlsml+xml			application
application/nss			application
application/ocsp-request			application
application/ocsp-response			application
application/octet-stream			application
application/oda			application
application/ODX			application
application/oebps-package+xml			application
application/ogg			application
application/oxps			application
application/p2p-overlay+xml			application
application/parityfec			application
application/patch-ops-error+xml			application
application/pdf			application
application/PDX			application
application/pgp-encrypted			application
application/pgp-keys			application
application/pgp-signature			application
application/pidf-diff+xml			application
application/pidf+xml			application
application/pkcs10			application
application/pkcs7-mime			application
application/pkcs7-signature			application
application/pkcs8			application
application/pkcs12			application
application/pkix-attr-cert			application
application/pkix-cert			application
application/pkix-crl			application
application/pkix-pkipath			application
application/pkixcmp			application
application/pls+xml			application
application/poc-settings+xml			application
application/postscript			application
application/ppsp-tracker+json			application
application/problem+json			application
application/problem+xml			application
application/provenance+xml			application
application/prs.alvestrand.titrax-sheet			application
application/prs.cww			application
application/prs.hpub+zip			application
application/prs.nprend			application
application/prs.plucker			application
application/prs.rdf-xml-crypt			application
application/prs.xsf+xml			application
application/pskc+xml			application
application/rdf+xml			application
application/qsig			application
application/raptorfec			application
application/rdap+json			application
application/reginfo+xml			application
application/relax-ng-compact-syntax			application
application/remote-printing			application
application/reputon+json			application
application/resource-lists-diff+xml			application
application/resource-lists+xml			application
application/rfc+xml			application
application/riscos			application
application/rlmi+xml			application
application/rls-services+xml			application
application/rpki-ghostbusters			application
application/rpki-manifest			application
application/rpki-publication			application
application/rpki-roa			application
application/rpki-updown			application
application/rtf			application
application/rtploopback			application
application/rtx			application
application/samlassertion+xml			application
application/samlmetadata+xml			application
application/sbml+xml			application
application/scaip+xml			application
application/scim+json			application
application/scvp-cv-request			application
application/scvp-cv-response			application
application/scvp-vp-request			application
application/scvp-vp-response			application
application/sdp			application
application/sep-exi			application
application/sep+xml			application
application/session-info			application
application/set-payment			application
application/set-payment-initiation			application
application/set-registration			application
application/set-registration-initiation			application
application/sgml			application
application/sgml-open-catalog			application
application/shf+xml			application
application/sieve			application
application/simple-filter+xml			application
application/simple-message-summary			application
application/simpleSymbolContainer			application
application/slate			application
application/smil (withdrawn)			application
application/smil+xml			application
application/smpte336m			application
application/soap+fastinfoset			application
application/soap+xml			application
application/sparql-query			application
application/sparql-results+xml			application
application/spirits-event+xml			application
application/sql			application
application/srgs			application
application/srgs+xml			application
application/sru+xml			application
application/ssml+xml			application
application/tamp-apex-update			application
application/tamp-apex-update-confirm			application
application/tamp-community-update			application
application/tamp-community-update-confirm			application
application/tamp-error			application
application/tamp-sequence-adjust			application
application/tamp-sequence-adjust-confirm			application
application/tamp-status-query			application
application/tamp-status-response			application
application/tamp-update			application
application/tamp-update-confirm			application
application/tei+xml			application
application/thraud+xml			application
application/timestamp-query			application
application/timestamp-reply			application
application/timestamped-data			application
application/trig			application
application/ttml+xml			application
application/tve-trigger			application
application/ulpfec			application
application/urc-grpsheet+xml			application
application/urc-ressheet+xml			application
application/urc-targetdesc+xml			application
application/urc-uisocketdesc+xml			application
application/vcard+json			application
application/vcard+xml			application
application/vemmi			application
application/vnd.1000minds.decision-model+xml			application
application/vnd.3gpp.access-transfer-events+xml			application
application/vnd.3gpp.bsf+xml			application
application/vnd.3gpp.mid-call+xml			application
application/vnd.3gpp.pic-bw-large			application
application/vnd.3gpp.pic-bw-small			application
application/vnd.3gpp.pic-bw-var			application
application/vnd.3gpp-prose-pc3ch+xml			application
application/vnd.3gpp-prose+xml			application
application/vnd.3gpp.sms			application
application/vnd.3gpp.sms+xml			application
application/vnd.3gpp.srvcc-ext+xml			application
application/vnd.3gpp.SRVCC-info+xml			application
application/vnd.3gpp.state-and-event-info+xml			application
application/vnd.3gpp.ussd+xml			application
application/vnd.3gpp2.bcmcsinfo+xml			application
application/vnd.3gpp2.sms			application
application/vnd.3gpp2.tcap			application
application/vnd.3lightssoftware.imagescal			application
application/vnd.3M.Post-it-Notes			application
application/vnd.accpac.simply.aso			application
application/vnd.accpac.simply.imp			application
application/vnd.acucobol			application
application/vnd.acucorp			application
application/vnd.adobe.flash.movie			application
application/vnd.adobe.formscentral.fcdt			application
application/vnd.adobe.fxp			application
application/vnd.adobe.partial-upload			application
application/vnd.adobe.xdp+xml			application
application/vnd.adobe.xfdf			application
application/vnd.aether.imp			application
application/vnd.ah-barcode			application
application/vnd.ahead.space			application
application/vnd.airzip.filesecure.azf			application
application/vnd.airzip.filesecure.azs			application
application/vnd.amazon.mobi8-ebook			application
application/vnd.americandynamics.acc			application
application/vnd.amiga.ami			application
application/vnd.amundsen.maze+xml			application
application/vnd.anki			application
application/vnd.anser-web-certificate-issue-initiation			application
application/vnd.antix.game-component			application
application/vnd.apache.thrift.binary			application
application/vnd.apache.thrift.compact			application
application/vnd.apache.thrift.json			application
application/vnd.api+json			application
application/vnd.apothekende.reservation+json			application
application/vnd.apple.mpegurl			application
application/vnd.apple.installer+xml			application
application/vnd.arastra.swi (withdrawn)			application
application/vnd.aristanetworks.swi			application
application/vnd.artsquare			application
application/vnd.astraea-software.iota			application
application/vnd.audiograph			application
application/vnd.autopackage			application
application/vnd.avistar+xml			application
application/vnd.balsamiq.bmml+xml			application
application/vnd.balsamiq.bmpr			application
application/vnd.bekitzur-stech+json			application
application/vnd.bint.med-content			application
application/vnd.biopax.rdf+xml			application
application/vnd.blueice.multipass			application
application/vnd.bluetooth.ep.oob			application
application/vnd.bluetooth.le.oob			application
application/vnd.bmi			application
application/vnd.businessobjects			application
application/vnd.cab-jscript			application
application/vnd.canon-cpdl			application
application/vnd.canon-lips			application
application/vnd.capasystems-pg+json			application
application/vnd.cendio.thinlinc.clientconf			application
application/vnd.century-systems.tcp_stream			application
application/vnd.chemdraw+xml			application
application/vnd.chess-pgn			application
application/vnd.chipnuts.karaoke-mmd			application
application/vnd.cinderella			application
application/vnd.cirpack.isdn-ext			application
application/vnd.citationstyles.style+xml			application
application/vnd.claymore			application
application/vnd.cloanto.rp9			application
application/vnd.clonk.c4group			application
application/vnd.cluetrust.cartomobile-config			application
application/vnd.cluetrust.cartomobile-config-pkg			application
application/vnd.coffeescript			application
application/vnd.collection.doc+json			application
application/vnd.collection+json			application
application/vnd.collection.next+json			application
application/vnd.comicbook+zip			application
application/vnd.commerce-battelle			application
application/vnd.commonspace			application
application/vnd.coreos.ignition+json			application
application/vnd.cosmocaller			application
application/vnd.contact.cmsg			application
application/vnd.crick.clicker			application
application/vnd.crick.clicker.keyboard			application
application/vnd.crick.clicker.palette			application
application/vnd.crick.clicker.template			application
application/vnd.crick.clicker.wordbank			application
application/vnd.criticaltools.wbs+xml			application
application/vnd.ctc-posml			application
application/vnd.ctct.ws+xml			application
application/vnd.cups-pdf			application
application/vnd.cups-postscript			application
application/vnd.cups-ppd			application
application/vnd.cups-raster			application
application/vnd.cups-raw			application
application/vnd.curl			application
application/vnd.cyan.dean.root+xml			application
application/vnd.cybank			application
application/vnd.d2l.coursepackage1p0+zip			application
application/vnd.dart			application
application/vnd.data-vision.rdz			application
application/vnd.datapackage+json			application
application/vnd.dataresource+json			application
application/vnd.debian.binary-package			application
application/vnd.dece.data			application
application/vnd.dece.ttml+xml			application
application/vnd.dece.unspecified			application
application/vnd.dece.zip			application
application/vnd.denovo.fcselayout-link			application
application/vnd.desmume.movie			application
application/vnd.dir-bi.plate-dl-nosuffix			application
application/vnd.dm.delegation+xml			application
application/vnd.dna			application
application/vnd.document+json			application
application/vnd.dolby.mobile.1			application
application/vnd.dolby.mobile.2			application
application/vnd.doremir.scorecloud-binary-document			application
application/vnd.dpgraph			application
application/vnd.dreamfactory			application
application/vnd.drive+json			application
application/vnd.dtg.local			application
application/vnd.dtg.local.flash			application
application/vnd.dtg.local.html			application
application/vnd.dvb.ait			application
application/vnd.dvb.dvbj			application
application/vnd.dvb.esgcontainer			application
application/vnd.dvb.ipdcdftnotifaccess			application
application/vnd.dvb.ipdcesgaccess			application
application/vnd.dvb.ipdcesgaccess2			application
application/vnd.dvb.ipdcesgpdd			application
application/vnd.dvb.ipdcroaming			application
application/vnd.dvb.iptv.alfec-base			application
application/vnd.dvb.iptv.alfec-enhancement			application
application/vnd.dvb.notif-aggregate-root+xml			application
application/vnd.dvb.notif-container+xml			application
application/vnd.dvb.notif-generic+xml			application
application/vnd.dvb.notif-ia-msglist+xml			application
application/vnd.dvb.notif-ia-registration-request+xml			application
application/vnd.dvb.notif-ia-registration-response+xml			application
application/vnd.dvb.notif-init+xml			application
application/vnd.dvb.pfr			application
application/vnd.dvb.service			application
application/vnd.dxr			application
application/vnd.dynageo			application
application/vnd.dzr			application
application/vnd.easykaraoke.cdgdownload			application
application/vnd.ecdis-update			application
application/vnd.ecowin.chart			application
application/vnd.ecowin.filerequest			application
application/vnd.ecowin.fileupdate			application
application/vnd.ecowin.series			application
application/vnd.ecowin.seriesrequest			application
application/vnd.ecowin.seriesupdate			application
application/vnd.efi.img			application
application/vnd.efi.iso			application
application/vnd.emclient.accessrequest+xml			application
application/vnd.enliven			application
application/vnd.enphase.envoy			application
application/vnd.eprints.data+xml			application
application/vnd.epson.esf			application
application/vnd.epson.msf			application
application/vnd.epson.quickanime			application
application/vnd.epson.salt			application
application/vnd.epson.ssf			application
application/vnd.ericsson.quickcall			application
application/vnd.espass-espass+zip			application
application/vnd.eszigno3+xml			application
application/vnd.etsi.aoc+xml			application
application/vnd.etsi.asic-s+zip			application
application/vnd.etsi.asic-e+zip			application
application/vnd.etsi.cug+xml			application
application/vnd.etsi.iptvcommand+xml			application
application/vnd.etsi.iptvdiscovery+xml			application
application/vnd.etsi.iptvprofile+xml			application
application/vnd.etsi.iptvsad-bc+xml			application
application/vnd.etsi.iptvsad-cod+xml			application
application/vnd.etsi.iptvsad-npvr+xml			application
application/vnd.etsi.iptvservice+xml			application
application/vnd.etsi.iptvsync+xml			application
application/vnd.etsi.iptvueprofile+xml			application
application/vnd.etsi.mcid+xml			application
application/vnd.etsi.mheg5			application
application/vnd.etsi.overload-control-policy-dataset+xml			application
application/vnd.etsi.pstn+xml			application
application/vnd.etsi.sci+xml			application
application/vnd.etsi.simservs+xml			application
application/vnd.etsi.timestamp-token			application
application/vnd.etsi.tsl+xml			application
application/vnd.etsi.tsl.der			application
application/vnd.evolv.ecig.theme			application
application/vnd.eudora.data			application
application/vnd.ezpix-album			application
application/vnd.ezpix-package			application
application/vnd.f-secure.mobile			application
application/vnd.fastcopy-disk-image			application
application/vnd.fdf			application
application/vnd.fdsn.mseed			application
application/vnd.fdsn.seed			application
application/vnd.ffsns			application
application/vnd.filmit.zfc			application
application/vnd.fints			application
application/vnd.firemonkeys.cloudcell			application
application/vnd.FloGraphIt			application
application/vnd.fluxtime.clip			application
application/vnd.font-fontforge-sfd			application
application/vnd.framemaker			application
application/vnd.frogans.fnc			application
application/vnd.frogans.ltf			application
application/vnd.fsc.weblaunch			application
application/vnd.fujitsu.oasys			application
application/vnd.fujitsu.oasys2			application
application/vnd.fujitsu.oasys3			application
application/vnd.fujitsu.oasysgp			application
application/vnd.fujitsu.oasysprs			application
application/vnd.fujixerox.ART4			application
application/vnd.fujixerox.ART-EX			application
application/vnd.fujixerox.ddd			application
application/vnd.fujixerox.docuworks			application
application/vnd.fujixerox.docuworks.binder			application
application/vnd.fujixerox.docuworks.container			application
application/vnd.fujixerox.HBPL			application
application/vnd.fut-misnet			application
application/vnd.fuzzysheet			application
application/vnd.genomatix.tuxedo			application
application/vnd.geo+json (withdrawn)			application
application/vnd.geocube+xml (withdrawn)			application
application/vnd.geogebra.file			application
application/vnd.geogebra.tool			application
application/vnd.geometry-explorer			application
application/vnd.geonext			application
application/vnd.geoplan			application
application/vnd.geospace			application
application/vnd.gerber			application
application/vnd.globalplatform.card-content-mgt			application
application/vnd.globalplatform.card-content-mgt-response			application
application/vnd.gmx (withdrawn)			application
application/vnd.google-earth.kml+xml			application
application/vnd.google-earth.kmz			application
application/vnd.gov.sk.e-form+xml			application
application/vnd.gov.sk.e-form+zip			application
application/vnd.gov.sk.xmldatacontainer+xml			application
application/vnd.grafeq			application
application/vnd.gridmp			application
application/vnd.groove-account			application
application/vnd.groove-help			application
application/vnd.groove-identity-message			application
application/vnd.groove-injector			application
application/vnd.groove-tool-message			application
application/vnd.groove-tool-template			application
application/vnd.groove-vcard			application
application/vnd.hal+json			application
application/vnd.hal+xml			application
application/vnd.HandHeld-Entertainment+xml			application
application/vnd.hbci			application
application/vnd.hc+json			application
application/vnd.hcl-bireports			application
application/vnd.hdt			application
application/vnd.heroku+json			application
application/vnd.hhe.lesson-player			application
application/vnd.hp-HPGL			application
application/vnd.hp-hpid			application
application/vnd.hp-hps			application
application/vnd.hp-jlyt			application
application/vnd.hp-PCL			application
application/vnd.hp-PCLXL			application
application/vnd.httphone			application
application/vnd.hydrostatix.sof-data			application
application/vnd.hyper-item+json			application
application/vnd.hyperdrive+json			application
application/vnd.hzn-3d-crossword			application
application/vnd.ibm.afplinedata			application
application/vnd.ibm.electronic-media			application
application/vnd.ibm.MiniPay			application
application/vnd.ibm.modcap			application
application/vnd.ibm.rights-management			application
application/vnd.ibm.secure-container			application
application/vnd.iccprofile			application
application/vnd.ieee.1905			application
application/vnd.igloader			application
application/vnd.imagemeter.folder+zip			application
application/vnd.imagemeter.image+zip			application
application/vnd.immervision-ivp			application
application/vnd.immervision-ivu			application
application/vnd.ims.imsccv1p1			application
application/vnd.ims.imsccv1p2			application
application/vnd.ims.imsccv1p3			application
application/vnd.ims.lis.v2.result+json			application
application/vnd.ims.lti.v2.toolconsumerprofile+json			application
application/vnd.ims.lti.v2.toolproxy.id+json			application
application/vnd.ims.lti.v2.toolproxy+json			application
application/vnd.ims.lti.v2.toolsettings+json			application
application/vnd.ims.lti.v2.toolsettings.simple+json			application
application/vnd.informedcontrol.rms+xml			application
application/vnd.infotech.project			application
application/vnd.infotech.project+xml			application
application/vnd.informix-visionary (withdrawn)			application
application/vnd.innopath.wamp.notification			application
application/vnd.insors.igm			application
application/vnd.intercon.formnet			application
application/vnd.intergeo			application
application/vnd.intertrust.digibox			application
application/vnd.intertrust.nncp			application
application/vnd.intu.qbo			application
application/vnd.intu.qfx			application
application/vnd.iptc.g2.catalogitem+xml			application
application/vnd.iptc.g2.conceptitem+xml			application
application/vnd.iptc.g2.knowledgeitem+xml			application
application/vnd.iptc.g2.newsitem+xml			application
application/vnd.iptc.g2.newsmessage+xml			application
application/vnd.iptc.g2.packageitem+xml			application
application/vnd.iptc.g2.planningitem+xml			application
application/vnd.ipunplugged.rcprofile			application
application/vnd.irepository.package+xml			application
application/vnd.is-xpr			application
application/vnd.isac.fcs			application
application/vnd.jam			application
application/vnd.japannet-directory-service			application
application/vnd.japannet-jpnstore-wakeup			application
application/vnd.japannet-payment-wakeup			application
application/vnd.japannet-registration			application
application/vnd.japannet-registration-wakeup			application
application/vnd.japannet-setstore-wakeup			application
application/vnd.japannet-verification			application
application/vnd.japannet-verification-wakeup			application
application/vnd.jcp.javame.midlet-rms			application
application/vnd.jisp			application
application/vnd.joost.joda-archive			application
application/vnd.jsk.isdn-ngn			application
application/vnd.kahootz			application
application/vnd.kde.karbon			application
application/vnd.kde.kchart			application
application/vnd.kde.kformula			application
application/vnd.kde.kivio			application
application/vnd.kde.kontour			application
application/vnd.kde.kpresenter			application
application/vnd.kde.kspread			application
application/vnd.kde.kword			application
application/vnd.kenameaapp			application
application/vnd.kidspiration			application
application/vnd.Kinar			application
application/vnd.koan			application
application/vnd.kodak-descriptor			application
application/vnd.las.las+json			application
application/vnd.las.las+xml			application
application/vnd.liberty-request+xml			application
application/vnd.llamagraphics.life-balance.desktop			application
application/vnd.llamagraphics.life-balance.exchange+xml			application
application/vnd.lotus-1-2-3			application
application/vnd.lotus-approach			application
application/vnd.lotus-freelance			application
application/vnd.lotus-notes			application
application/vnd.lotus-organizer			application
application/vnd.lotus-screencam			application
application/vnd.lotus-wordpro			application
application/vnd.macports.portpkg			application
application/vnd.macports.portpkg			application
application/vnd.mapbox-vector-tile			application
application/vnd.marlin.drm.actiontoken+xml			application
application/vnd.marlin.drm.conftoken+xml			application
application/vnd.marlin.drm.license+xml			application
application/vnd.marlin.drm.mdcf			application
application/vnd.mason+json			application
application/vnd.maxmind.maxmind-db			application
application/vnd.mcd			application
application/vnd.medcalcdata			application
application/vnd.mediastation.cdkey			application
application/vnd.meridian-slingshot			application
application/vnd.MFER			application
application/vnd.mfmp			application
application/vnd.micro+json			application
application/vnd.micrografx.flo			application
application/vnd.micrografx.igx			application
application/vnd.microsoft.portable-executable			application
application/vnd.microsoft.windows.thumbnail-cache			application
application/vnd.miele+json			application
application/vnd.mif			application
application/vnd.minisoft-hp3000-save			application
application/vnd.mitsubishi.misty-guard.trustweb			application
application/vnd.Mobius.DAF			application
application/vnd.Mobius.DIS			application
application/vnd.Mobius.MBK			application
application/vnd.Mobius.MQY			application
application/vnd.Mobius.MSL			application
application/vnd.Mobius.PLC			application
application/vnd.Mobius.TXF			application
application/vnd.mophun.application			application
application/vnd.mophun.certificate			application
application/vnd.motorola.flexsuite			application
application/vnd.motorola.flexsuite.adsi			application
application/vnd.motorola.flexsuite.fis			application
application/vnd.motorola.flexsuite.gotap			application
application/vnd.motorola.flexsuite.kmr			application
application/vnd.motorola.flexsuite.ttc			application
application/vnd.motorola.flexsuite.wem			application
application/vnd.motorola.iprm			application
application/vnd.mozilla.xul+xml			application
application/vnd.ms-artgalry			application
application/vnd.ms-asf			application
application/vnd.ms-cab-compressed			application
application/vnd.ms-3mfdocument			application
application/vnd.ms-excel			application
application/vnd.ms-excel.addin.macroEnabled.12			application
application/vnd.ms-excel.sheet.binary.macroEnabled.12			application
application/vnd.ms-excel.sheet.macroEnabled.12			application
application/vnd.ms-excel.template.macroEnabled.12			application
application/vnd.ms-fontobject			application
application/vnd.ms-htmlhelp			application
application/vnd.ms-ims			application
application/vnd.ms-lrm			application
application/vnd.ms-office.activeX+xml			application
application/vnd.ms-officetheme			application
application/vnd.ms-playready.initiator+xml			application
application/vnd.ms-powerpoint			application
application/vnd.ms-powerpoint.addin.macroEnabled.12			application
application/vnd.ms-powerpoint.presentation.macroEnabled.12			application
application/vnd.ms-powerpoint.slide.macroEnabled.12			application
application/vnd.ms-powerpoint.slideshow.macroEnabled.12			application
application/vnd.ms-powerpoint.template.macroEnabled.12			application
application/vnd.ms-PrintDeviceCapabilities+xml			application
application/vnd.ms-PrintSchemaTicket+xml			application
application/vnd.ms-project			application
application/vnd.ms-tnef			application
application/vnd.ms-windows.devicepairing			application
application/vnd.ms-windows.nwprinting.oob			application
application/vnd.ms-windows.printerpairing			application
application/vnd.ms-windows.wsd.oob			application
application/vnd.ms-wmdrm.lic-chlg-req			application
application/vnd.ms-wmdrm.lic-resp			application
application/vnd.ms-wmdrm.meter-chlg-req			application
application/vnd.ms-wmdrm.meter-resp			application
application/vnd.ms-word.document.macroEnabled.12			application
application/vnd.ms-word.template.macroEnabled.12			application
application/vnd.ms-works			application
application/vnd.ms-wpl			application
application/vnd.ms-xpsdocument			application
application/vnd.msa-disk-image			application
application/vnd.mseq			application
application/vnd.msign			application
application/vnd.multiad.creator			application
application/vnd.multiad.creator.cif			application
application/vnd.musician			application
application/vnd.music-niff			application
application/vnd.muvee.style			application
application/vnd.mynfc			application
application/vnd.ncd.control			application
application/vnd.ncd.reference			application
application/vnd.nearst.inv+json			application
application/vnd.nervana			application
application/vnd.netfpx			application
application/vnd.neurolanguage.nlu			application
application/vnd.nintendo.snes.rom			application
application/vnd.nintendo.nitro.rom			application
application/vnd.nitf			application
application/vnd.noblenet-directory			application
application/vnd.noblenet-sealer			application
application/vnd.noblenet-web			application
application/vnd.nokia.catalogs			application
application/vnd.nokia.conml+wbxml			application
application/vnd.nokia.conml+xml			application
application/vnd.nokia.iptv.config+xml			application
application/vnd.nokia.iSDS-radio-presets			application
application/vnd.nokia.landmark+wbxml			application
application/vnd.nokia.landmark+xml			application
application/vnd.nokia.landmarkcollection+xml			application
application/vnd.nokia.ncd			application
application/vnd.nokia.n-gage.ac+xml			application
application/vnd.nokia.n-gage.data			application
application/vnd.nokia.n-gage.symbian.install (withdrawn)			application
application/vnd.nokia.pcd+wbxml			application
application/vnd.nokia.pcd+xml			application
application/vnd.nokia.radio-preset			application
application/vnd.nokia.radio-presets			application
application/vnd.novadigm.EDM			application
application/vnd.novadigm.EDX			application
application/vnd.novadigm.EXT			application
application/vnd.ntt-local.content-share			application
application/vnd.ntt-local.file-transfer			application
application/vnd.ntt-local.ogw_remote-access			application
application/vnd.ntt-local.sip-ta_remote			application
application/vnd.ntt-local.sip-ta_tcp_stream			application
application/vnd.oasis.opendocument.chart			application
application/vnd.oasis.opendocument.chart-template			application
application/vnd.oasis.opendocument.database			application
application/vnd.oasis.opendocument.formula			application
application/vnd.oasis.opendocument.formula-template			application
application/vnd.oasis.opendocument.graphics			application
application/vnd.oasis.opendocument.graphics-template			application
application/vnd.oasis.opendocument.image			application
application/vnd.oasis.opendocument.image-template			application
application/vnd.oasis.opendocument.presentation			application
application/vnd.oasis.opendocument.presentation-template			application
application/vnd.oasis.opendocument.spreadsheet			application
application/vnd.oasis.opendocument.spreadsheet-template			application
application/vnd.oasis.opendocument.text			application
application/vnd.oasis.opendocument.text-master			application
application/vnd.oasis.opendocument.text-template			application
application/vnd.oasis.opendocument.text-web			application
application/vnd.obn			application
application/vnd.ocf+cbor			application
application/vnd.oftn.l10n+json			application
application/vnd.oipf.contentaccessdownload+xml			application
application/vnd.oipf.contentaccessstreaming+xml			application
application/vnd.oipf.cspg-hexbinary			application
application/vnd.oipf.dae.svg+xml			application
application/vnd.oipf.dae.xhtml+xml			application
application/vnd.oipf.mippvcontrolmessage+xml			application
application/vnd.oipf.pae.gem			application
application/vnd.oipf.spdiscovery+xml			application
application/vnd.oipf.spdlist+xml			application
application/vnd.oipf.ueprofile+xml			application
application/vnd.oipf.userprofile+xml			application
application/vnd.olpc-sugar			application
application/vnd.oma.bcast.associated-procedure-parameter+xml			application
application/vnd.oma.bcast.drm-trigger+xml			application
application/vnd.oma.bcast.imd+xml			application
application/vnd.oma.bcast.ltkm			application
application/vnd.oma.bcast.notification+xml			application
application/vnd.oma.bcast.provisioningtrigger			application
application/vnd.oma.bcast.sgboot			application
application/vnd.oma.bcast.sgdd+xml			application
application/vnd.oma.bcast.sgdu			application
application/vnd.oma.bcast.simple-symbol-container			application
application/vnd.oma.bcast.smartcard-trigger+xml			application
application/vnd.oma.bcast.sprov+xml			application
application/vnd.oma.bcast.stkm			application
application/vnd.oma.cab-address-book+xml			application
application/vnd.oma.cab-feature-handler+xml			application
application/vnd.oma.cab-pcc+xml			application
application/vnd.oma.cab-subs-invite+xml			application
application/vnd.oma.cab-user-prefs+xml			application
application/vnd.oma.dcd			application
application/vnd.oma.dcdc			application
application/vnd.oma.dd2+xml			application
application/vnd.oma.drm.risd+xml			application
application/vnd.oma.group-usage-list+xml			application
application/vnd.oma.lwm2m+json			application
application/vnd.oma.lwm2m+tlv			application
application/vnd.oma.pal+xml			application
application/vnd.oma.poc.detailed-progress-report+xml			application
application/vnd.oma.poc.final-report+xml			application
application/vnd.oma.poc.groups+xml			application
application/vnd.oma.poc.invocation-descriptor+xml			application
application/vnd.oma.poc.optimized-progress-report+xml			application
application/vnd.oma.push			application
application/vnd.oma.scidm.messages+xml			application
application/vnd.oma.xcap-directory+xml			application
application/vnd.omads-email+xml			application
application/vnd.omads-file+xml			application
application/vnd.omads-folder+xml			application
application/vnd.omaloc-supl-init			application
application/vnd.oma-scws-config			application
application/vnd.oma-scws-http-request			application
application/vnd.oma-scws-http-response			application
application/vnd.onepager			application
application/vnd.onepagertamp			application
application/vnd.onepagertamx			application
application/vnd.onepagertat			application
application/vnd.onepagertatp			application
application/vnd.onepagertatx			application
application/vnd.openblox.game-binary			application
application/vnd.openblox.game+xml			application
application/vnd.openeye.oeb			application
application/vnd.openstreetmap.data+xml			application
application/vnd.openxmlformats-officedocument.custom-properties+xml			application
application/vnd.openxmlformats-officedocument.customXmlProperties+xml			application
application/vnd.openxmlformats-officedocument.drawing+xml			application
application/vnd.openxmlformats-officedocument.drawingml.chart+xml			application
application/vnd.openxmlformats-officedocument.drawingml.chartshapes+xml			application
application/vnd.openxmlformats-officedocument.drawingml.diagramColors+xml			application
application/vnd.openxmlformats-officedocument.drawingml.diagramData+xml			application
application/vnd.openxmlformats-officedocument.drawingml.diagramLayout+xml			application
application/vnd.openxmlformats-officedocument.drawingml.diagramStyle+xml			application
application/vnd.openxmlformats-officedocument.extended-properties+xml			application
application/vnd.openxmlformats-officedocument.presentationml.commentAuthors+xml			application
application/vnd.openxmlformats-officedocument.presentationml.comments+xml			application
application/vnd.openxmlformats-officedocument.presentationml.handoutMaster+xml			application
application/vnd.openxmlformats-officedocument.presentationml.notesMaster+xml			application
application/vnd.openxmlformats-officedocument.presentationml.notesSlide+xml			application
application/vnd.openxmlformats-officedocument.presentationml.presentation			application
application/vnd.openxmlformats-officedocument.presentationml.presentation.main+xml			application
application/vnd.openxmlformats-officedocument.presentationml.presProps+xml			application
application/vnd.openxmlformats-officedocument.presentationml.slide			application
application/vnd.openxmlformats-officedocument.presentationml.slide+xml			application
application/vnd.openxmlformats-officedocument.presentationml.slideLayout+xml			application
application/vnd.openxmlformats-officedocument.presentationml.slideMaster+xml			application
application/vnd.openxmlformats-officedocument.presentationml.slideshow			application
application/vnd.openxmlformats-officedocument.presentationml.slideshow.main+xml			application
application/vnd.openxmlformats-officedocument.presentationml.slideUpdateInfo+xml			application
application/vnd.openxmlformats-officedocument.presentationml.tableStyles+xml			application
application/vnd.openxmlformats-officedocument.presentationml.tags+xml			application
application/vnd.openxmlformats-officedocument.presentationml.template			application
application/vnd.openxmlformats-officedocument.presentationml.template.main+xml			application
application/vnd.openxmlformats-officedocument.presentationml.viewProps+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.calcChain+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.chartsheet+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.comments+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.connections+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.dialogsheet+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.externalLink+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.pivotCacheDefinition+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.pivotCacheRecords+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.pivotTable+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.queryTable+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.revisionHeaders+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.revisionLog+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.sharedStrings+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet			application
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet.main+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.sheetMetadata+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.styles+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.table+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.tableSingleCells+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.template			application
application/vnd.openxmlformats-officedocument.spreadsheetml.template.main+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.userNames+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.volatileDependencies+xml			application
application/vnd.openxmlformats-officedocument.spreadsheetml.worksheet+xml			application
application/vnd.openxmlformats-officedocument.theme+xml			application
application/vnd.openxmlformats-officedocument.themeOverride+xml			application
application/vnd.openxmlformats-officedocument.vmlDrawing			application
application/vnd.openxmlformats-officedocument.wordprocessingml.comments+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.document			application
application/vnd.openxmlformats-officedocument.wordprocessingml.document.glossary+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.document.main+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.endnotes+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.fontTable+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.footer+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.footnotes+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.numbering+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.settings+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.styles+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.template			application
application/vnd.openxmlformats-officedocument.wordprocessingml.template.main+xml			application
application/vnd.openxmlformats-officedocument.wordprocessingml.webSettings+xml			application
application/vnd.openxmlformats-package.core-properties+xml			application
application/vnd.openxmlformats-package.digital-signature-xmlsignature+xml			application
application/vnd.openxmlformats-package.relationships+xml			application
application/vnd.oracle.resource+json			application
application/vnd.orange.indata			application
application/vnd.osa.netdeploy			application
application/vnd.osgeo.mapguide.package			application
application/vnd.osgi.bundle			application
application/vnd.osgi.dp			application
application/vnd.osgi.subsystem			application
application/vnd.otps.ct-kip+xml			application
application/vnd.oxli.countgraph			application
application/vnd.pagerduty+json			application
application/vnd.palm			application
application/vnd.panoply			application
application/vnd.paos.xml			application
application/vnd.pawaafile			application
application/vnd.pcos			application
application/vnd.pg.format			application
application/vnd.pg.osasli			application
application/vnd.piaccess.application-licence			application
application/vnd.picsel			application
application/vnd.pmi.widget			application
application/vnd.poc.group-advertisement+xml			application
application/vnd.pocketlearn			application
application/vnd.powerbuilder6			application
application/vnd.powerbuilder6-s			application
application/vnd.powerbuilder7			application
application/vnd.powerbuilder75			application
application/vnd.powerbuilder75-s			application
application/vnd.powerbuilder7-s			application
application/vnd.preminet			application
application/vnd.previewsystems.box			application
application/vnd.proteus.magazine			application
application/vnd.publishare-delta-tree			application
application/vnd.pvi.ptid1			application
application/vnd.pwg-multiplexed			application
application/vnd.pwg-xhtml-print+xml			application
application/vnd.qualcomm.brew-app-res			application
application/vnd.quarantainenet			application
application/vnd.Quark.QuarkXPress			application
application/vnd.quobject-quoxdocument			application
application/vnd.radisys.moml+xml			application
application/vnd.radisys.msml-audit-conf+xml			application
application/vnd.radisys.msml-audit-conn+xml			application
application/vnd.radisys.msml-audit-dialog+xml			application
application/vnd.radisys.msml-audit-stream+xml			application
application/vnd.radisys.msml-audit+xml			application
application/vnd.radisys.msml-conf+xml			application
application/vnd.radisys.msml-dialog-base+xml			application
application/vnd.radisys.msml-dialog-fax-detect+xml			application
application/vnd.radisys.msml-dialog-fax-sendrecv+xml			application
application/vnd.radisys.msml-dialog-group+xml			application
application/vnd.radisys.msml-dialog-speech+xml			application
application/vnd.radisys.msml-dialog-transform+xml			application
application/vnd.radisys.msml-dialog+xml			application
application/vnd.radisys.msml+xml			application
application/vnd.rainstor.data			application
application/vnd.rapid			application
application/vnd.rar			application
application/vnd.realvnc.bed			application
application/vnd.recordare.musicxml			application
application/vnd.recordare.musicxml+xml			application
application/vnd.RenLearn.rlprint			application
application/vnd.rig.cryptonote			application
application/vnd.route66.link66+xml			application
application/vnd.rs-274x			application
application/vnd.ruckus.download			application
application/vnd.s3sms			application
application/vnd.sailingtracker.track			application
application/vnd.sbm.cid			application
application/vnd.sbm.mid2			application
application/vnd.scribus			application
application/vnd.sealed.3df			application
application/vnd.sealed.csf			application
application/vnd.sealed.doc			application
application/vnd.sealed.eml			application
application/vnd.sealed.mht			application
application/vnd.sealed.net			application
application/vnd.sealed.ppt			application
application/vnd.sealed.tiff			application
application/vnd.sealed.xls			application
application/vnd.sealedmedia.softseal.html			application
application/vnd.sealedmedia.softseal.pdf			application
application/vnd.seemail			application
application/vnd.sema			application
application/vnd.semd			application
application/vnd.semf			application
application/vnd.shana.informed.formdata			application
application/vnd.shana.informed.formtemplate			application
application/vnd.shana.informed.interchange			application
application/vnd.shana.informed.package			application
application/vnd.sigrok.session			application
application/vnd.SimTech-MindMapper			application
application/vnd.siren+json			application
application/vnd.smaf			application
application/vnd.smart.notebook			application
application/vnd.smart.teacher			application
application/vnd.software602.filler.form+xml			application
application/vnd.software602.filler.form-xml-zip			application
application/vnd.solent.sdkm+xml			application
application/vnd.spotfire.dxp			application
application/vnd.spotfire.sfs			application
application/vnd.sss-cod			application
application/vnd.sss-dtf			application
application/vnd.sss-ntf			application
application/vnd.stepmania.package			application
application/vnd.stepmania.stepchart			application
application/vnd.street-stream			application
application/vnd.sun.wadl+xml			application
application/vnd.sus-calendar			application
application/vnd.svd			application
application/vnd.swiftview-ics			application
application/vnd.syncml.dm.notification			application
application/vnd.syncml.dmddf+xml			application
application/vnd.syncml.dmtnds+wbxml			application
application/vnd.syncml.dmtnds+xml			application
application/vnd.syncml.dmddf+wbxml			application
application/vnd.syncml.dm+wbxml			application
application/vnd.syncml.dm+xml			application
application/vnd.syncml.ds.notification			application
application/vnd.syncml+xml			application
application/vnd.tableschema+json			application
application/vnd.tao.intent-module-archive			application
application/vnd.tcpdump.pcap			application
application/vnd.tml			application
application/vnd.tmd.mediaflex.api+xml			application
application/vnd.tmobile-livetv			application
application/vnd.tri.onesource			application
application/vnd.trid.tpt			application
application/vnd.triscape.mxs			application
application/vnd.trueapp			application
application/vnd.truedoc			application
application/vnd.ubisoft.webplayer			application
application/vnd.ufdl			application
application/vnd.uiq.theme			application
application/vnd.umajin			application
application/vnd.unity			application
application/vnd.uoml+xml			application
application/vnd.uplanet.alert			application
application/vnd.uplanet.alert-wbxml			application
application/vnd.uplanet.bearer-choice			application
application/vnd.uplanet.bearer-choice-wbxml			application
application/vnd.uplanet.cacheop			application
application/vnd.uplanet.cacheop-wbxml			application
application/vnd.uplanet.channel			application
application/vnd.uplanet.channel-wbxml			application
application/vnd.uplanet.list			application
application/vnd.uplanet.listcmd			application
application/vnd.uplanet.listcmd-wbxml			application
application/vnd.uplanet.list-wbxml			application
application/vnd.uri-map			application
application/vnd.uplanet.signal			application
application/vnd.valve.source.material			application
application/vnd.vcx			application
application/vnd.vd-study			application
application/vnd.vectorworks			application
application/vnd.vel+json			application
application/vnd.verimatrix.vcas			application
application/vnd.vidsoft.vidconference			application
application/vnd.visio			application
application/vnd.visionary			application
application/vnd.vividence.scriptfile			application
application/vnd.vsf			application
application/vnd.wap.sic			application
application/vnd.wap.slc			application
application/vnd.wap.wbxml			application
application/vnd.wap.wmlc			application
application/vnd.wap.wmlscriptc			application
application/vnd.webturbo			application
application/vnd.wfa.p2p			application
application/vnd.wfa.wsc			application
application/vnd.windows.devicepairing			application
application/vnd.wmc			application
application/vnd.wmf.bootstrap			application
application/vnd.wolfram.mathematica			application
application/vnd.wolfram.mathematica.package			application
application/vnd.wolfram.player			application
application/vnd.wordperfect			application
application/vnd.wqd			application
application/vnd.wrq-hp3000-labelled			application
application/vnd.wt.stf			application
application/vnd.wv.csp+xml			application
application/vnd.wv.csp+wbxml			application
application/vnd.wv.ssp+xml			application
application/vnd.xacml+json			application
application/vnd.xara			application
application/vnd.xfdl			application
application/vnd.xfdl.webform			application
application/vnd.xmi+xml			application
application/vnd.xmpie.cpkg			application
application/vnd.xmpie.dpkg			application
application/vnd.xmpie.plan			application
application/vnd.xmpie.ppkg			application
application/vnd.xmpie.xlim			application
application/vnd.yamaha.hv-dic			application
application/vnd.yamaha.hv-script			application
application/vnd.yamaha.hv-voice			application
application/vnd.yamaha.openscoreformat.osfpvg+xml			application
application/vnd.yamaha.openscoreformat			application
application/vnd.yamaha.remote-setup			application
application/vnd.yamaha.smaf-audio			application
application/vnd.yamaha.smaf-phrase			application
application/vnd.yamaha.through-ngn			application
application/vnd.yamaha.tunnel-udpencap			application
application/vnd.yaoweme			application
application/vnd.yellowriver-custom-menu			application
application/vnd.zul			application
application/vnd.zzazz.deck+xml			application
application/voicexml+xml			application
application/vq-rtcpxr			application
application/watcherinfo+xml			application
application/whoispp-query			application
application/whoispp-response			application
application/widget			application
application/wita			application
application/wordperfect5.1			application
application/wsdl+xml			application
application/wspolicy+xml			application
application/x-www-form-urlencoded			application
application/x400-bp			application
application/xacml+xml			application
application/xcap-att+xml			application
application/xcap-caps+xml			application
application/xcap-diff+xml			application
application/xcap-el+xml			application
application/xcap-error+xml			application
application/xcap-ns+xml			application
application/xcon-conference-info-diff+xml			application
application/xcon-conference-info+xml			application
application/xenc+xml			application
application/xhtml-voice+xml (withdrawn)			application
application/xhtml+xml			application
application/xml			application
application/xml-dtd			application
application/xml-external-parsed-entity			application
application/xml-patch+xml			application
application/xmpp+xml			application
application/xop+xml			application
application/xslt+xml			application
application/xv+xml			application
application/yang			application
application/yang-data+json			application
application/yang-data+xml			application
application/yang-patch+json			application
application/yang-patch+xml			application
application/yin+xml			application
application/zip			application
application/zlib			application
audio/1d-interleaved-parityfec			audio
audio/32kadpcm			audio
audio/3gpp			audio
audio/3gpp2			audio
audio/ac3			audio
audio/AMR			audio
audio/AMR-WB			audio
audio/amr-wb+			audio
audio/aptx			audio
audio/asc			audio
audio/ATRAC-ADVANCED-LOSSLESS			audio
audio/ATRAC-X			audio
audio/ATRAC3			audio
audio/basic			audio
audio/BV16			audio
audio/BV32			audio
audio/clearmode			audio
audio/CN			audio
audio/DAT12			audio
audio/dls			audio
audio/dsr-es201108			audio
audio/dsr-es202050			audio
audio/dsr-es202211			audio
audio/dsr-es202212			audio
audio/DV			audio
audio/DVI4			audio
audio/eac3			audio
audio/encaprtp			audio
audio/EVRC			audio
audio/EVRC-QCP			audio
audio/EVRC0			audio
audio/EVRC1			audio
audio/EVRCB			audio
audio/EVRCB0			audio
audio/EVRCB1			audio
audio/EVRCNW			audio
audio/EVRCNW0			audio
audio/EVRCNW1			audio
audio/EVRCWB			audio
audio/EVRCWB0			audio
audio/EVRCWB1			audio
audio/EVS			audio
audio/example			audio
audio/fwdred			audio
audio/G711-0			audio
audio/G719			audio
audio/G7221			audio
audio/G722			audio
audio/G723			audio
audio/G726-16			audio
audio/G726-24			audio
audio/G726-32			audio
audio/G726-40			audio
audio/G728			audio
audio/G729			audio
audio/G7291			audio
audio/G729D			audio
audio/G729E			audio
audio/GSM			audio
audio/GSM-EFR			audio
audio/GSM-HR-08			audio
audio/iLBC			audio
audio/ip-mr_v2.5			audio
audio/L8			audio
audio/L16			audio
audio/L20			audio
audio/L24			audio
audio/LPC			audio
audio/MELP			audio
audio/MELP600			audio
audio/MELP1200			audio
audio/MELP2400			audio
audio/mobile-xmf			audio
audio/MPA			audio
audio/mp4			audio
audio/MP4A-LATM			audio
audio/mpa-robust			audio
audio/mpeg			audio
audio/mpeg4-generic			audio
audio/ogg			audio
audio/opus			audio
audio/parityfec			audio
audio/PCMA			audio
audio/PCMA-WB			audio
audio/PCMU			audio
audio/PCMU-WB			audio
audio/prs.sid			audio
audio/QCELP			audio
audio/raptorfec			audio
audio/RED			audio
audio/rtp-enc-aescm128			audio
audio/rtploopback			audio
audio/rtp-midi			audio
audio/rtx			audio
audio/SMV			audio
audio/SMV0			audio
audio/SMV-QCP			audio
audio/sp-midi			audio
audio/speex			audio
audio/t140c			audio
audio/t38			audio
audio/telephone-event			audio
audio/tone			audio
audio/UEMCLIP			audio
audio/ulpfec			audio
audio/VDVI			audio
audio/VMR-WB			audio
audio/vnd.3gpp.iufp			audio
audio/vnd.4SB			audio
audio/vnd.audiokoz			audio
audio/vnd.CELP			audio
audio/vnd.cisco.nse			audio
audio/vnd.cmles.radio-events			audio
audio/vnd.cns.anp1			audio
audio/vnd.cns.inf1			audio
audio/vnd.dece.audio			audio
audio/vnd.digital-winds			audio
audio/vnd.dlna.adts			audio
audio/vnd.dolby.heaac.1			audio
audio/vnd.dolby.heaac.2			audio
audio/vnd.dolby.mlp			audio
audio/vnd.dolby.mps			audio
audio/vnd.dolby.pl2			audio
audio/vnd.dolby.pl2x			audio
audio/vnd.dolby.pl2z			audio
audio/vnd.dolby.pulse.1			audio
audio/vnd.dra			audio
audio/vnd.dts			audio
audio/vnd.dts.hd			audio
audio/vnd.dvb.file			audio
audio/vnd.everad.plj			audio
audio/vnd.hns.audio			audio
audio/vnd.lucent.voice			audio
audio/vnd.ms-playready.media.pya			audio
audio/vnd.nokia.mobile-xmf			audio
audio/vnd.nortel.vbk			audio
audio/vnd.nuera.ecelp4800			audio
audio/vnd.nuera.ecelp7470			audio
audio/vnd.nuera.ecelp9600			audio
audio/vnd.octel.sbc			audio
audio/vnd.qcelp (withdrawn)			audio
audio/vnd.rhetorex.32kadpcm			audio
audio/vnd.rip			audio
audio/vnd.sealedmedia.softseal.mpeg			audio
audio/vnd.vmx.cvsd			audio
audio/vorbis			audio
audio/vorbis-config			audio
font/collection			font
font/otf			font
font/sfnt			font
font/ttf			font
font/woff			font
font/woff2			font
image/bmp			image
image/cgm			image
image/dicom-rle			image
image/emf			image
image/example			image
image/fits			image
image/g3fax			image
image/gif			image
image/ief			image
image/jls			image
image/jp2			image
image/jpeg			image
image/jpm			image
image/jpx			image
image/ktx			image
image/naplps			image
image/png			image
image/prs.btif			image
image/prs.pti			image
image/pwg-raster			image
image/svg+xml			image
image/t38			image
image/tiff			image
image/tiff-fx			image
image/vnd.adobe.photoshop			image
image/vnd.airzip.accelerator.azv			image
image/vnd.cns.inf2			image
image/vnd.dece.graphic			image
image/vnd.djvu			image
image/vnd.dwg			image
image/vnd.dxf			image
image/vnd.dvb.subtitle			image
image/vnd.fastbidsheet			image
image/vnd.fpx			image
image/vnd.fst			image
image/vnd.fujixerox.edmics-mmr			image
image/vnd.fujixerox.edmics-rlc			image
image/vnd.globalgraphics.pgb			image
image/vnd.microsoft.icon			image
image/vnd.mix			image
image/vnd.ms-modi			image
image/vnd.mozilla.apng			image
image/vnd.net-fpx			image
image/vnd.radiance			image
image/vnd.sealed.png			image
image/vnd.sealedmedia.softseal.gif			image
image/vnd.sealedmedia.softseal.jpg			image
image/vnd.svf			image
image/vnd.tencent.tap			image
image/vnd.valve.source.texture			image
image/vnd.wap.wbmp			image
image/vnd.xiff			image
image/vnd.zbrush.pcx			image
image/wmf			image
image/x-emf (withdrawn)			image
image/x-wmf (withdrawn)			image
message/CPIM			message
message/delivery-status			message
message/disposition-notification			message
message/example			message
message/external-body			message
message/feedback-report			message
message/global			message
message/global-delivery-status			message
message/global-disposition-notification			message
message/global-headers			message
message/http			message
message/imdn+xml			message
message/news (withdrawn)			message
message/partial			message
message/rfc822			message
message/s-http			message
message/sip			message
message/sipfrag			message
message/tracking-status			message
message/vnd.si.simp (withdrawn)			message
message/vnd.wfa.wsc			message
model/3mf			model
model/example			model
model/gltf+json			model
model/iges			model
model/mesh			model
model/vnd.collada+xml			model
model/vnd.dwf			model
model/vnd.flatland.3dml			model
model/vnd.gdl			model
model/vnd.gs-gdl			model
model/vnd.gtw			model
model/vnd.moml+xml			model
model/vnd.mts			model
model/vnd.opengex			model
model/vnd.parasolid.transmit.binary			model
model/vnd.parasolid.transmit.text			model
model/vnd.rosette.annotated-data-model			model
model/vnd.valve.source.compiled-map			model
model/vnd.vtu			model
model/vrml			model
model/x3d-vrml			model
model/x3d+fastinfoset			model
model/x3d+xml			model
multipart/alternative			multipart
multipart/appledouble			multipart
multipart/byteranges			multipart
multipart/digest			multipart
multipart/encrypted			multipart
multipart/example			multipart
multipart/form-data			multipart
multipart/header-set			multipart
multipart/mixed			multipart
multipart/parallel			multipart
multipart/related			multipart
multipart/report			multipart
multipart/signed			multipart
multipart/vnd.bint.med-plus			multipart
multipart/voice-message			multipart
multipart/x-mixed-replace			multipart
text/1d-interleaved-parityfec			text
text/cache-manifest			text
text/calendar			text
text/css			text
text/csv			text
text/csv-schema			text
text/directory (withdrawn)			text
text/dns			text
text/ecmascript (withdrawn)			text
text/encaprtp			text
text/enriched			text
text/example			text
text/fwdred			text
text/grammar-ref-list			text
text/html			text
text/javascript (withdrawn)			text
text/jcr-cnd			text
text/markdown			text
text/mizar			text
text/n3			text
text/parameters			text
text/parityfec			text
text/plain			text
text/provenance-notation			text
text/prs.fallenstein.rst			text
text/prs.lines.tag			text
text/prs.prop.logic			text
text/raptorfec			text
text/RED			text
text/rfc822-headers			text
text/richtext			text
text/rtf			text
text/rtp-enc-aescm128			text
text/rtploopback			text
text/rtx			text
text/sgml			text
text/strings			text
text/t140			text
text/tab-separated-values			text
text/troff			text
text/turtle			text
text/ulpfec			text
text/uri-list			text
text/vcard			text
text/vnd.a			text
text/vnd.abc			text
text/vnd.ascii-art			text
text/vnd.curl			text
text/vnd.debian.copyright			text
text/vnd.DMClientScript			text
text/vnd.dvb.subtitle			text
text/vnd.esmertec.theme-descriptor			text
text/vnd.fly			text
text/vnd.fmi.flexstor			text
text/vnd.graphviz			text
text/vnd.in3d.3dml			text
text/vnd.in3d.spot			text
text/vnd.IPTC.NewsML			text
text/vnd.IPTC.NITF			text
text/vnd.latex-z			text
text/vnd.motorola.reflex			text
text/vnd.ms-mediapackage			text
text/vnd.net2phone.commcenter.command			text
text/vnd.radisys.msml-basic-layout			text
text/vnd.si.uricatalogue (withdrawn)			text
text/vnd.sun.j2me.app-descriptor			text
text/vnd.trolltech.linguist			text
text/vnd.wap.si			text
text/vnd.wap.sl			text
text/vnd.wap.wml			text
text/vnd.wap.wmlscript			text
text/xml			text
text/xml-external-parsed-entity			text
video/1d-interleaved-parityfec			video
video/3gpp			video
video/3gpp2			video
video/3gpp-tt			video
video/BMPEG			video
video/BT656			video
video/CelB			video
video/DV			video
video/encaprtp			video
video/example			video
video/H261			video
video/H263			video
video/H263-1998			video
video/H263-2000			video
video/H264			video
video/H264-RCDO			video
video/H264-SVC			video
video/H265			video
video/iso.segment			video
video/JPEG			video
video/jpeg2000			video
video/mj2			video
video/MP1S			video
video/MP2P			video
video/MP2T			video
video/mp4			video
video/MP4V-ES			video
video/MPV			video
video/mpeg			video
video/mpeg4-generic			video
video/nv			video
video/ogg			video
video/parityfec			video
video/pointer			video
video/quicktime			video
video/raptorfec			video
video/raw			video
video/rtp-enc-aescm128			video
video/rtploopback			video
video/rtx			video
video/SMPTE292M			video
video/ulpfec			video
video/vc1			video
video/vnd.CCTV			video
video/vnd.dece.hd			video
video/vnd.dece.mobile			video
video/vnd.dece.mp4			video
video/vnd.dece.pd			video
video/vnd.dece.sd			video
video/vnd.dece.video			video
video/vnd.directv.mpeg			video
video/vnd.directv.mpeg-tts			video
video/vnd.dlna.mpeg-tts			video
video/vnd.dvb.file			video
video/vnd.fvt			video
video/vnd.hns.video			video
video/vnd.iptvforum.1dparityfec-1010			video
video/vnd.iptvforum.1dparityfec-2005			video
video/vnd.iptvforum.2dparityfec-1010			video
video/vnd.iptvforum.2dparityfec-2005			video
video/vnd.iptvforum.ttsavc			video
video/vnd.iptvforum.ttsmpeg2			video
video/vnd.motorola.video			video
video/vnd.motorola.videop			video
video/vnd.mpegurl			video
video/vnd.ms-playready.media.pyv			video
video/vnd.nokia.interleaved-multimedia			video
video/vnd.nokia.videovoip			video
video/vnd.objectvideo			video
video/vnd.radgamettools.bink			video
video/vnd.radgamettools.smacker			video
video/vnd.sealed.mpeg1			video
video/vnd.sealed.mpeg4			video
video/vnd.sealed.swf			video
video/vnd.sealedmedia.softseal.mov			video
video/vnd.uvvu.mp4			video
video/vnd.vivo			video
video/VP8			video

Finance Type

DAC/CRS transaction classification used to distinguish financial instruments, e.g. grants or loans.

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/default-finance-type/@code

• iati-activities/iati-activity/transaction/finance-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
1	GNI: Gross National Income		0
110	Standard grant	Grants are transfers in cash or in kind for which no legal debt is incurred by the recipient.	100
1100	Guarantees/insurance		1000
111 (withdrawn)	Subsidies to national private investors		100
2	ODA % GNI		0
210	Interest subsidy	A payment to soften the terms of private export credits, or loans or credits by the banking sector.	100
211 (withdrawn)	Interest subsidy to national private exporters		100
3	Total Flows % GNI		0
310	Capital subscription on deposit basis	Payments to multilateral agencies in the form of notes and similar instruments, unconditionally encashable at sight by the recipient institutions.	100
311	Capital subscription on encashment basis	Payments to multilateral agencies in the form of notes and similar instruments, unconditionally encashable at sight by the recipient institutions.	100
4	Population		0
410 (withdrawn)	Aid loan excluding debt reorganisation		400
411 (withdrawn)	Investment-related loan to developing countries		400
412 (withdrawn)	Loan in a joint venture with the recipient		400
413 (withdrawn)	Loan to national private investor		400
414 (withdrawn)	Loan to national private exporter		400
421	Standard loan	Transfers in cash or in kind for which the recipient incurs legal debt (and the resulting claim is not intended to be traded). Since payment obligations on standard loan are senior obligations, i.e. creditors are entitled to receive payments against their claims before anyone else, they are also referred to as senior loans.	420
422	Reimbursable grant	A contribution provided to a recipient institution for investment purposes, with the expectation of long-term reflows at conditions specified in the financing agreement. The provider assumes the risk of total or partial failure of the investment; it can also decide if and when to reclaim its investment.	420
423	Bonds	Fixed-interest debt instruments, issued by governments, public utilities, banks or companies, tradable in financial markets.	420
424	Asset-backed securities	Securities whose value and income payments are derived from and backed by a specific pool of underlying assets.	420
425	Other debt securities		420
431	Subordinated loan	A loan that, in the event of default, will only be repaid after all senior obligations have been satisfied. In compensation for the increased risk, mezzanine debt holders require a higher return for their investment than secured or more senior lenders.	430
432	Preferred equity	Equity that, in the event of default, will be repaid after all senior obligations and subordinated loans have been satisfied; and will be paid before common equity holders. It is a more expensive source of finance than senior debt, a less expensive source than equity.	430
433	Other hybrid instruments	Including convertible debt or equity.	430
451 (withdrawn)	Non-banks guaranteed export credits		450
452 (withdrawn)	Non-banks non-guaranteed portions of guaranteed export credits		400
453 (withdrawn)	Bank export credits		400
510	Common equity	A share in the ownership of a corporation that gives the owner claims on the residual value of the corporation after creditors’ claims have been met.	500
511 (withdrawn)	Acquisition of equity not part of joint venture in developing countries		500
512 (withdrawn)	Other acquisition of equity		500
520	Shares in collective investment vehicles	Collective undertakings through which investors pool funds for investment in financial or nonfinancial assets or both. These vehicles issue shares (if a corporate structure is used) or units (if a trust structure is used).	500
530	Reinvested earnings	This item is only applicable to Foreign Direct Investment (FDI). Reinvested earnings on FDI consist of the retained earnings of a direct foreign investment enterprise which are treated as if they were distributed and remitted to foreign direct investors in proportion to their ownership of the equity of the enterprise and then reinvested by them in the enterprise.	500
610	Debt forgiveness: ODA claims (P)		600
611	Debt forgiveness: ODA claims (I)		600
612	Debt forgiveness: OOF claims (P)		600
613	Debt forgiveness: OOF claims (I)		600
614	Debt forgiveness: Private claims (P)		600
615	Debt forgiveness: Private claims (I)		600
616	Debt forgiveness: OOF claims (DSR)		600
617	Debt forgiveness: Private claims (DSR)		600
618	Debt forgiveness: Other		600
620	Debt rescheduling: ODA claims (P)		600
621	Debt rescheduling: ODA claims (I)		600
622	Debt rescheduling: OOF claims (P)		600
623	Debt rescheduling: OOF claims (I)		600
624	Debt rescheduling: Private claims (P)		600
625	Debt rescheduling: Private claims (I)		600
626	Debt rescheduling: OOF claims (DSR)		600
627	Debt rescheduling: Private claims (DSR)		600
630	Debt rescheduling: OOF claim (DSR – original loan principal)		600
631	Debt rescheduling: OOF claim (DSR – original loan interest)		600
632	Debt rescheduling: Private claim (DSR – original loan principal)		600
633	Debt forgiveness/conversion: export credit claims (P)		600
634	Debt forgiveness/conversion: export credit claims (I)		600
635	Debt forgiveness: export credit claims (DSR)		600
636	Debt rescheduling: export credit claims (P)		600
637	Debt rescheduling: export credit claims (I)		600
638	Debt rescheduling: export credit claims (DSR)		600
639	Debt rescheduling: export credit claim (DSR – original loan principal)		600
710 (withdrawn)	Foreign direct investment, new capital outflow (includes reinvested earnings if separate identification not available)		700
711 (withdrawn)	Other foreign direct investment, including reinvested earnings		700
712 (withdrawn)	Foreign direct investment, reinvested earnings		700
810 (withdrawn)	Bank bonds		800
811 (withdrawn)	Non-bank bonds		800
910 (withdrawn)	Other bank securities/claims		900
911 (withdrawn)	Other non-bank securities/claims		900
912 (withdrawn)	Purchase of securities from issuing agencies		900
913 (withdrawn)	Securities and other instruments originally issued by multilateral agencies		900

Finance Type (category)

This codelists exists to group the Finance Type codelist into categories. It is not used as a codelist in its own right.

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
0	NON FLOW ITEMS	Non resource flow items requested on DAC table 1
100	GRANTS
1000	GUARANTEES AND OTHER UNFUNDED CONTINGENT LIABILITIES
200 (withdrawn)	INTEREST SUBSIDY	Subsidies to soften the terms of private export credits, or loans or credits by the banking sector.
300 (withdrawn)	CAPITAL SUBSCRIPTION	Payments to multilateral agencies in the form of notes and similar instruments, unconditionally cashable at sight by the recipient institutions.
400 (withdrawn)	LOAN	Transfers in cash or in kind for which the recipient incurs legal debt.
420	DEBT INSTRUMENTS
430	MEZZANINE FINANCE INSTRUMENTS
500	EQUITY AND SHARES IN COLLECTIVE INVESTMENT VEHICLES
600	DEBT RELIEF	Debt cancellations, debt conversions, debt rescheduling within or outside the framework of the Paris Club.
700 (withdrawn)	INVESTMENT	Investment made by a private entity resident in a reporting country to acquire or add to a lasting interest(1) in an enterprise in a country on the DAC List of ODA Recipients.
800 (withdrawn)	BONDS	Acquisition of bonds issued by developing countries.
900 (withdrawn)	OTHER SECURITIES/CLAIMS

Flow Type

DAC/CRS distinction between ODA (official development assistance) and other types of resource flow.

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/default-flow-type/@code

• iati-activities/iati-activity/transaction/flow-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
10	ODA	Official Development Assistance
20 (withdrawn)	OOF	Other Official Flows
21	Non-export credit OOF	Other Official Flows, excl. export credits
22	Officially supported export credits	Officially supported export credits. Covers both official direct export credits and private export credits under official guarantee or insurance
30	Private Development Finance	Financing by civil society organisations (NGOs, philantropic foundations, etc.)
35 (withdrawn)	Private Market	Private long-term (i.e. over one-year maturity) capital transactions made by residents of DAC countries
36	Private Foreign Direct Investment	Private Foreign Direct Investment
37	Other Private flows at market terms	Private long-term (i.e. over one-year maturity) capital transactions made by residents of DAC countries
40	Non flow	e.g. GNI, ODA%GNI, Population etc
50	Other flows	e.g. non-ODA component of peacebuilding operations

Gazetteer Agency

An online resource that holds coordinates and descriptions of geographic locations

This is a Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Geonames.org
2	National Geospatial-Intelligence Agency
3	Open Street Map

Changelog

2.01

The GazetteerAgency codelist was amended to numeric values

Geographic Exactness

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/location/exactness/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Exact	The designated geographic location is exact
2	Approximate	The designated geographic location is approximate

Geographic Location Class

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/location/location-class/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Administrative Region	The designated geographic location is an administrative region (state, county, province, district, municipality etc.)
2	Populated Place	The designated geographic location is a populated place (town, village, farm etc.)
3	Structure	The designated geopgraphic location is a structure (such as a school or a clinic)
4	Other Topographical Feature	The designated geographic location is a topographical feature, such as a mountain, a river, a forest

Geographic Location Reach

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/location/location-reach/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Activity	The location specifies where the activity is carried out
2	Intended Beneficiaries	The location specifies where the intended beneficiaries of the activity live

Geographic Vocabulary

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/location/location-id/@vocabulary

• iati-activities/iati-activity/location/administrative/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
A1	Global Admininistrative Unit Layers		http://www.fao.org/geonetwork/srv/en/metadata.show?id=12691
A2	UN Second Administrative Level Boundary Project	Note: the unsalb.org website is no longer accessible, and public access to the boundaries resources has been removed http://www.ungiwg.org/content/united-nations-international-and-administrative-boundaries-resources	http://www.unsalb.org/
A3	Global Administrative Areas		http://www.gadm.org/
A4	ISO Country (3166-1 alpha-2)		http://reference.iatistandard.org/codelists/Country/
G1	Geonames		http://www.geonames.org/
G2	OpenStreetMap	Note: the code should be formed by prefixing the relevant OpenStreetMap ID with node/ way/ or relation/ as appropriate, e.g. node/1234567	http://www.openstreetmap.org/

Geographical Precision

A system for clarifying the accuracy and usage of geographical coordinates

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Exact location	The coordinates corresponds to an exact location, such as a populated place or a hill. The code is also used for locations that join a location which is a line (such as a road or railroad). Lines are not coded only the points that connect lines. All points that are mentioned in the source are coded.
2	Near exact location	The location is mentioned in the source as being “near”, in the “area” of, or up to 25 km away from an exact location. The coordinates refer to that adjacent, exact, location.
3	Second order administrative division	The location is, or lies in, a second order administrative division (ADM2), such as a district, municipality or commune
4	First order administrative division	The location is, or lies in, a first order administrative division (ADM1), such as a province, state or governorate.
5	Estimated coordinates	The location can only be related to estimated coordinates, such as when a location lies between populated places; along rivers, roads and borders; more than 25 km away from a specific location; or when sources refer to parts of a country greater than ADM1 (e.g. “northern Uganda”).
6	Independent political entity	The location can only be related to an independent political entity, meaning the pair of coordinates that represent a country.
7	Unclear - capital	Unclear. The capital is assumed to be one of two possible locations. (The other option is the country level, with precision 9.)
8	Local or national capital	The location is estimated to be a seat of an administrative division (local capital) or the national capital. If aid goes to Luanda without further specification on the location, and there is an ADM1 and a capital called Luanda, then code the coordinates of the capital with precision 8. If it is not spelled out that aid goes to the capital; but if it is clear that it goes to a government ministry or to government financial institutions; and if those institutions are most likely located in the capital; then the coordinates of the capital are coded with precision 8. (However, if it can be verified that the recipient institution is located in the capital then precision 1 is used.)
9	Unclear - country	Unclear. The locations is estimated to be the country level (often paired with the capital, with precision 7)

Humanitarian Scope Type

The Humanitarian Scope Type codelist defines codes for types of humanitarian events and actions.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/humanitarian-scope/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Emergency
2	Appeal

Humanitarian Scope Vocabulary

The Humanitarian Scope Vocabulary codelist defines a range of external codelists which themselves provide codes and descriptions for humanitarian events and actions.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/humanitarian-scope/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1-2	Glide		http://glidenumber.net/glide/public/search/search.jsp
2-1	Humanitarian Plan		https://fts.unocha.org/plan-code-list-iati
99	Reporting Organisation

IATI Organisation Identifier

This is a list of organisation identifiers that is maintained by the IATI Secretariat. The prefix for organisations on this list is XI-IATI

If a bona fide organisation is not registered with any recognised or appropriate registration agency (http://iatistandard.org/202/codelists/OrganisationRegistrationAgency/) they should contact the IATI Technical Team who will exceptionally allocate an organisation identifier using the XI-IATI prefix.

While some of these identifiers have been derived from DAC codes, this ‘meaning’ is not carried forward. i.e. IATI generated identifiers have no intrinsic meaning.

For general guidance about constructing Organisation Identifiers, please see http://iatistandard.org/organisation-identifiers/

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
XI-IATI-1001	The Coca-Cola Export Corporation	Subsidiary of The Coca-Cola Company responsible for marketing and export of soft drinks, bottled water, and other beverages and with links to the various charitable initiatives of The Coca-Cola Company, its subsidiaries and affiliates Coca-Cola charitable foundation. Based in Atlanta Georgia USA	http://www.coca-colacompany.com/
XI-IATI-1002	United Mission to Nepal	The United Mission to Nepal (UMN) is a faith based INGO based in Kathmandu, and has worked in Nepal without interruption since 1954. UMN works through local partners in order to serve the people of Nepal, especially the poorest of those living in poverty, to pursue peace and justice for all and to address the root causes of their poverty. We do this by supporting communities in a transformation process focusing on health, education, sustainable livelihoods, peace-building and good governance.	http://www.umn.org.np/
XI-IATI-ACATBA	Association Centrafricaine de Traduction de la Bible et Alphabetisation	ACATBA is a charity that exists to promote local language development, Bible translation, literacy and community development in the Central African Republic. They also provide training in basic business skills; this allows beneficiaries to begin income-generating activities and small businesses.	http://www.wycliffe.net/organizations?entity=CXN&continent=AFR&country=CT
XI-IATI-ADVZ	Agência de Desenvolvimento do Vale do Zambeze	Description: The Agência do Zambeze is a public-sector agency under the Ministry of Economics and Finance in Mozambique. The mission of the Agência do Zambeze is to promote the socio-economic and sustainable development of the Lower Zambezi River Basin.	http://www.inm.gov.mz/?q=pt-pt/ag%C3%AAncia-de-desenvolvimento-do-vale-do-zambeze
XI-IATI-AGR	AgResults	AgResults is a $122 million collaborative initiative between the governments of Australia, Canada, the United Kingdom, the United States, and the Bill and Melinda Gates Foundation to incentivize the private sector to overcome market barriers and develop solutions to food security and agricultural challenges that disproportionately affect people living in poverty. The initiative designs and implements agriculture-focused prize competitions, also referred to as pay-for-results or pull mechanisms, which are innovative development finance programs that engage the private sector to work towards a defined goal to receive a monetary award.	https://agresults.org/
XI-IATI-AIAS	Administração de Infra-Estruturas de Águas e Saneamento	Description: AIAS manages the property of the secondary public systems for water supply and for the residual water drainage public systems in Mozambique promoting their autonomous efficient and financially feasible operational management through assignment to private operators or other third party entities.	http://www.aias.gov.mz/
XI-IATI-AJS	Associations des Juristes Sénégalaises (AJS)	The Association des Juristes Sénégalaises (AJS) is an association of women lawyers who promote and contribute to the protection of the rights of individuals, particularly women and children.	http://www.femmesjuristes.org
XI-IATI-ATTIC	Association of Technicians in Information Technology and Communication (ATTIC)	ATTIC, a non-political non-profit association in Republic of Chad, aims to help develop and integrate the promotion of information and communication technologies in the development policy of the formal and non-formal sectors, to fight against food insecurity and poverty, by strengthening the means of vulnerable households, refugees, returnees and internally displaced persons, and by providing socio-professional training and integration for vulnerable groups.	Website is still in progress
XI-IATI-BBDN	Bangladesh Business & Disability Network	The Bangladesh Business and Disability Network (BBDN) is a voluntary group of representatives from business, industry, employers’ organizations and selected non-governmental and disabled peoples’ organizations. BBDN has a primary purpose of facilitating disability and work place diversity in Bangladesh from the perspective of the business and human rights cases.	https://www.bbdn.com.bd/
XI-IATI-EBRD	European Bank for Reconstruction and Development	Description: Who we are - The EBRD is investing in changing peoples’ lives and environments from central Europe to Central Asia, the Western Balkans and the southern and eastern Mediterranean region. With an emphasis on working with the private sector, we invest in projects, engage in policy dialogue and provide technical advice that fosters innovation and builds sustainable and open-market economies. What we do - The EBRD provides direct financing for well structured, financially robust projects of all sizes (including many small businesses), both directly and through financial intermediaries such as local banks and investment funds. The Bank works mainly with private sector clients, but also finances municipal entities and publicly owned companies. Our principal financing instruments are loans, equity investments and guarantees.	http://www.ebrd.com/home
XI-IATI-BEH	Benedictine Eye Hospital, Tororo	Benedictine Eye Hospital (BEH) is a Private Not-For-Profit specialised hospital established by the Benedictine Fathers of Uganda for providing Eye Care and Community Based Rehabilitation (CBR) services to Persons with Disabilities (PWDs), with special emphasis on children. The hospital is registered by the Ministry of Health and serves the people of Eastern Uganda but is increasingly receiving clients from the rest of the country and neighbouring countries.	http://www.benedictineeyehospital.org
XI-IATI-CABI	CABI	CABI (Centre for Agriculture and Biosciences International) is an international not-for-profit organization that improves people’s lives worldwide by providing information and applying scientific expertise to solve problems in agriculture and the environment. It’s approach involves putting information, skills and tools into people’s hands. CABI’s member countries guide and influence our work which is delivered by scientific staff based in our global network of centres.	http://www.cabi.org/
XI-IATI-CWSEC	The Commonwealth Secretariat	The Commonwealth is a voluntary association of 52 independent and equal sovereign states. Its guiding principles are contained in their Commonwealth Charter.	http://thecommonwealth.org/
XI-IATI-DGF	Democratic Governance Facility	DGF supports state and non state partners to strengthen democratisation, protect human rights, improve access to justice and enhance accountability in Uganda. DGF’s work is built upon the principles and values enshrined in Uganda’s 1995 Constitution and reiterated in its current National Development Plan.	https://www.dgf.ug/
XI-IATI-EC_DEVCO	European Commission – Development and Cooperation	DG DEVCO is in charge of development cooperation policy in a wider framework of international cooperation with developing countries at different stages of development. DG DEVCO is responsible for formulating European Union development policy and thematic policies in order to reduce poverty in the world, to ensure sustainable economic, social and environmental development and to promote democracy, the rule of law, good governance and the respect of human rights; the work is carried out closely with Member States, other Commission services, and with the European External Action Service.	https://ec.europa.eu/europeaid/home_en
XI-IATI-EC_ECHO	European Commission - Humanitarian Aid & Civil Protection	The Directorate General for Humanitarian aid and Civil Protection (ECHO) is responsible for formulating EU humanitarian aid policy, for programming and implementing the EU’s humanitarian aid budget and for supporting the central and overall coordinating role of the United Nations in promoting a coherent international response; ECHO also works closely with Member States’ civil protection authorities to improve disaster prevention, preparedness and response and facilitates the cooperation between the 32 States participating in the Civil Protection Mechanism.	http://ec.europa.eu/echo/
XI-IATI-ESFD	Economic and Social Fund for Development	The Economic and Social Fund for Development (ESFD) is a governmental body dedicated to alleviate poverty in Lebanon through the creation of employment opportunities and through the improvement of living conditions in disadvantaged communities.	http://www.esfd.cdr.gov.lb/
XI-IATI-EC_FPI	European Commission – Service for Foreign Policy Instruments	The core task of the Service for Foreign Policy Instruments (FPI) is to run a number of EU foreign policy actions, managing operations and their financing. Such areas include crisis response and prevention measures financed under the Instrument contributing to Stability and Peace (IcSP); the Common Foreign and Security Policy (CFSP) budget; and the Partnership Instrument (PI), designed to promote the Union’s strategic interests worldwide.	http://ec.europa.eu/dgs/fpi/index_en.htm
XI-IATI-EC_NEAR	European Commission - Neighbourhood and Enlargement Negotiations	The mission of DG NEAR is to take forward the EU’s neighbourhood and enlargement policies, as well as coordinating relations with EEA-EFTA countries. By implementing assistance in Europe’s eastern and southern neighbourhood, DG NEAR supports reform and democratic consolidation, and strengthens the prosperity, stability and security around Europe. In the enlargement area, DG NEAR assists those countries with a perspective to join the EU in meeting the criteria defined by the Treaty of European Union and the European Council.	http://ec.europa.eu/enlargement/index_en.htm
XI-IATI-EFRD	Engage Foundation for Research and Dialogue	Engage Foundation for Research and Dialogue is a research and discourse generation collective that was established in 2015 and seeks to approach issues of human rights, citizenship and democratization in an interdisciplinary and inter-sectional manner with the hope that a nuanced and sensitive exploration of relevant issues will lead to engagement with an audience beyond the privileged English speaking minority of Pakistan. Engage attempts to present dense or overlooked subjects of public importance in captivating audio and visual formats with the hope that exposure to such subjects will lead to a broader public understanding of life in a modern democratic state.	http://engagepakistan.com/engage/
XI-IATI-FIABEL	Federation of Institutional Actors Belgium (FIABEL)	Fiabel is a federal association that connects Institutional Actors (IA) in Belgium. Fiabel supports her members by a) fulfilling a bridging function between the Belgian Development Cooperation and the Institutional Actors, to ensure that they are fully aware of the government legal framework, procedures and initiatives; b) representing the IA in various consultative committees with government bodies; c) setting up working groups to exchange knowledge and experiences; d) organizing trainings to strengthen the capacities of IA on strategic and operational level.	https://www.fiabel.be/nl
XI-IATI-GREDO	Gargaar Relief and Development Organization	GREDO is a national NGO that is based in Baidoa which is the capital city of South West Administration of Somalia. It exists to support and reach the most affected grass-root communities in those regions and in Somalia at large. Our support focuses on Emergency and Development programs with a key thematic sectors of Integrated Health, Nutrition and Wash, Education and FSL.	https://www.gredosom.org/
XI-IATI-IADB	Inter-American Development Bank	The Inter-American Development Bank works to improve lives in Latin America and the Caribbean. Through financial and technical support for countries working to reduce poverty and inequality, we help improve health and education, and advance infrastructure. Our aim is to achieve development in a sustainable, climate-friendly way.	http://www.iadb.org
XI-IATI-IFDC	International Fertilizer Development Center	Since 1974, IFDC has focused on increasing and sustaining food security and agricultural productivity in over 100 developing countries through the development and transfer of effective and environmentally sound crop nutrient technology and agribusiness expertise.	http://www.ifdc.org
XI-IATI-IKI	International Climate Initiative (IKI)	Since 2008, the International Climate Initiative (IKI) of the Federal Ministry for the Environment, Nature Conservation, Building and Nuclear Safety (BMUB) has been financing climate and biodiversity projects in developing and newly industrialising countries, as well as in countries in transition.	https://www.international-climate-initiative.com/
XI-IATI-KHF	The King Hussein Foundation (KHF)	Their mission is to build upon King Hussein’s lifelong commitment to peace, sustainable community development and cross-cultural understanding through national and regional programs that promote education and leadership, economic empowerment and participatory decision-making.	http://www.kinghusseinfoundation.org/
XI-IATI-LPI	Living Peace Institute	The Living Peace Institute (LPI) is a local NGO, based in Goma, Democratic Republic of Congo (DRC), and organized around the goal of achieving sustainable, gender-equitable peace at all levels of society in North and South Kivu regions of Eastern DRC.	http://www.livingpeaceinstitute.org/
XI-IATI-MIF	Multilateral Investment Fund (MIF)	The Multilateral Investment Fund serves as an innovation laboratory to promote development through the private sector by identifying, supporting, testing and piloting new solutions to development challenges and seeking to create opportunities for the poor and vulnerable populations in the LAC region.	https://www.fomin.org/
XI-IATI-NSO	Netherlands Space Office	The Netherlands Space Office (NSO) is the governmental space agency of the Netherlands. Its primary task is to develop and execute the national space policy. NSO is the main point of contact for national and international space affairs.	http://www.spaceoffice.nl/
XI-IATI-OCHASDC	United Nations Office for the Coordination of Humanitarian Affairs - Specially-Designated Contributions	The United Nations Office for the Coordination of Humanitarian Affairs (OCHA) is the part of the United Nations Secretariat responsible for bringing together humanitarian actors to ensure a coherent response to emergencies. OCHA’s activities are funded mostly through voluntary contributions from UN Member States, these contributions are reported under the IATI organisation ID XM-DAC-41127. OCHA also administers several Specially-Designated Contributions (SDCs) for projects implemented by third parties. Activities funded through SDCs will be reported under the IATI organisation ID XI-IATI-OCHASDC.	https://www.unocha.org/about-us/funding
XI-IATI-SGJ	Somali Gender Justice	Somali Gender Justice is a small NGO based in Garowe, Puntland, Somalia whose goal is to support gender equality, women’s rights, and community transformation.	https://www.facebook.com/SomaliGenderJustice/
XI-IATI-SWSC	Somali Women Study Centre	SWSC is a women led NGO, founded in 2011 and based in Mogadishu and Kismayo, Somalia. SWSC seeks to achieve gender equality and social inclusion by empowering Somali women to exert their agency and improve their socio- economic status through strengthening their leadership, mentoring, capacity building, advocacy, and research to enable them articulate their specific needs in post- conflict Somalia.	https://www.somaliwomenstudiescentre.org/
XI-IATI-UCES	Umbrella for Community Education in Somalia	UCES is a national NGO that exists to work for advancement of Somalia Education by delivering formal and non-formal, alternative Education system to improve the knowledge of the Community through active advocacy and networking to deliver quality Education.	www.UCES.org
XI-IATI-UDC	United Darfur Committees	United Darfur Committees is a non-governmental and non-profit organization established by committees of seven villages in East Dafur State, Sudan, to solve community conflict and assist the people in need.	https://twitter.com/UnitedDarfur
XI-IATI-UNPF	UN Pooled funds	The UN pooled funds are a UN inter-agency financing mechanism with three characteristics. First, UN pooled funds are designed to support a clearly defined programmatic purpose and results framework through contributions that are co-mingled, not earmarked to a specific UN entity and held by a UN fund administrator. Second, decisions on project / programmatic allocations are made by a UN-led governance mechanism, taking into account the programmatic purpose and results framework of the fund. Third, fund implementation is (fully or largely) entrusted to UN entities that assume the programmatic and financial accountability for the resources received.	https://undg.org/
XI-IATI-WARDI	Wardi Relief and Development Initiative	WARDI is a national NGO that exists to collaborate and provide assistance in all relevant sectors to the Somali communities. The key thematic intervention areas are Emergency relief, Food security and livelihood, Wash, Health and Nutrition, Education and Peace building and governance.	https://wardirelief.org/
XI-IATI-WAI	WASH Alliance International	The WASH Alliance International is a consortium of member organisations in the Netherlands and partner organisations worldwide, working on sustainable WASH for everyone.	http://wash-alliance.org/
XI-IATI-WBTF	World Bank Trust Funds (WBTF)	A trust fund (TF) is a financing arrangement established with contributions from one or more external development partner(s)/partners, and in some cases, from the World Bank Group, to support development-related activities. The World Bank acts as a trustee/administrator for development partners (donors) funds and implements the activities financed through trust funds in accordance with the signed agreements with donors. As part of fiduciary obligations, the World Bank as Trustee/administrator of trust funds maintains the records for trust funds activities distinct and separate from the activities of IBRD and IDA. The Bank also provides periodic report on the financial situation and results of the individual trust funds to donors.	https://www.worldbank.org/en/publication/trust-fund-annual-report-2019
XI-IATI-WVDRC	World Vision DRC	Our teams have been working in the DRC since 1984. Today, we are working to contribute to the measurable and sustainable improvement of well-being for 5,311,208 children and their communities through transformational development and humanitarian relief programmes focused on: health and nutrition, education, water and sanitation, protecting children, livelihoods and resilience, food aid, psychosocial support and the reintegration if displaced people.	https://www.wvi.org/congo-drc/about-us

Changelog

2.01

The IATIOrganisationIdentifier was added.

Indicator Measure

To specify how an indicator is being measured. This includes qualitative and quantitative values.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/result/indicator/@measure

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Unit	The indicator is measured in units.
2	Percentage	The indicator is measured in percentages
3	Nominal	The indicator is measured as a quantitative nominal scale.
4	Ordinal	The indicator is measured as a quantitative ordinal scale.
5	Qualitative	The indicator is qualitative.

Indicator Vocabulary

The Indicator Vocabulary codelist defines a range of external codelists which themselves provide codes and descriptions for indicators, for example to specify results.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/result/indicator/reference/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1	WHO Registry		http://apps.who.int/gho/indicatorregistry/App_Main/indicator_registry.aspx
2	Sphere Handbook		http://www.spherehandbook.org
3	US Foreign Assistance Framework		http://www.state.gov/s/d/rm/rls/dosstrat/2007/html/82981.htm
4	World Bank World Development Indicators		http://data.worldbank.org/data-catalog/world-development-indicators
5	UN Millennium Development Goals Indicators		http://mdgs.un.org/unsd/mdg/Host.aspx?Content=Indicators/OfficialList.htm
6	UNOCHA Humanitarian Response Indicators		https://www.humanitarianresponse.info/applications/ir/indicators
7	HIV/AIDS Indicator Registry		http://www.indicatorregistry.org
8	Harmonized Indicators for Private Sector (HIPSO)		https://indicators.ifipartnership.org/indicators/
9	UN Sustainable Development Goals (SDG) Indicators		https://unstats.un.org/sdgs/indicators/indicators-list/
99	Reporting Organisation

Language

External URL: http://www.iso.org/iso/home/standards/language_codes.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/reporting-org/narrative/@xml:lang

• iati-activities/iati-activity/title/narrative/@xml:lang

• iati-activities/iati-activity/description/narrative/@xml:lang

• iati-activities/iati-activity/participating-org/narrative/@xml:lang

• iati-activities/iati-activity/other-identifier/owner-org/narrative/@xml:lang

• iati-activities/iati-activity/activity-date/narrative/@xml:lang

• iati-activities/iati-activity/contact-info/organisation/narrative/@xml:lang

• iati-activities/iati-activity/contact-info/department/narrative/@xml:lang

• iati-activities/iati-activity/contact-info/person-name/narrative/@xml:lang

• iati-activities/iati-activity/contact-info/job-title/narrative/@xml:lang

• iati-activities/iati-activity/contact-info/mailing-address/narrative/@xml:lang

• iati-activities/iati-activity/recipient-country/narrative/@xml:lang

• iati-activities/iati-activity/recipient-region/narrative/@xml:lang

• iati-activities/iati-activity/location/name/narrative/@xml:lang

• iati-activities/iati-activity/location/description/narrative/@xml:lang

• iati-activities/iati-activity/location/activity-description/narrative/@xml:lang

• iati-activities/iati-activity/sector/narrative/@xml:lang

• iati-activities/iati-activity/tag/narrative/@xml:lang

• iati-activities/iati-activity/country-budget-items/budget-item/description/narrative/@xml:lang

• iati-activities/iati-activity/humanitarian-scope/narrative/@xml:lang

• iati-activities/iati-activity/policy-marker/narrative/@xml:lang

• iati-activities/iati-activity/planned-disbursement/provider-org/narrative/@xml:lang

• iati-activities/iati-activity/planned-disbursement/receiver-org/narrative/@xml:lang

• iati-activities/iati-activity/transaction/description/narrative/@xml:lang

• iati-activities/iati-activity/transaction/provider-org/narrative/@xml:lang

• iati-activities/iati-activity/transaction/receiver-org/narrative/@xml:lang

• iati-activities/iati-activity/transaction/sector/narrative/@xml:lang

• iati-activities/iati-activity/transaction/recipient-country/narrative/@xml:lang

• iati-activities/iati-activity/transaction/recipient-region/narrative/@xml:lang

• iati-activities/iati-activity/document-link/title/narrative/@xml:lang

• iati-activities/iati-activity/document-link/description/narrative/@xml:lang

• iati-activities/iati-activity/document-link/language/@code

• iati-activities/iati-activity/conditions/condition/narrative/@xml:lang

• iati-activities/iati-activity/result/title/narrative/@xml:lang

• iati-activities/iati-activity/result/description/narrative/@xml:lang

• iati-activities/iati-activity/result/document-link/title/narrative/@xml:lang

• iati-activities/iati-activity/result/document-link/description/narrative/@xml:lang

• iati-activities/iati-activity/result/document-link/language/@code

• iati-activities/iati-activity/result/indicator/title/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/description/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/document-link/title/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/document-link/description/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/document-link/language/@code

• iati-activities/iati-activity/result/indicator/baseline/document-link/title/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/baseline/document-link/description/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/baseline/document-link/language/@code

• iati-activities/iati-activity/result/indicator/baseline/comment/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/period/target/comment/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/period/target/document-link/title/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/period/target/document-link/description/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/period/target/document-link/language/@code

• iati-activities/iati-activity/result/indicator/period/actual/comment/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/period/actual/document-link/title/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/period/actual/document-link/description/narrative/@xml:lang

• iati-activities/iati-activity/result/indicator/period/actual/document-link/language/@code

• iati-activities/iati-activity/@xml:lang

• iati-organisations/iati-organisation/name/narrative/@xml:lang

• iati-organisations/iati-organisation/reporting-org/narrative/@xml:lang

• iati-organisations/iati-organisation/total-budget/budget-line/narrative/@xml:lang

• iati-organisations/iati-organisation/recipient-org-budget/recipient-org/narrative/@xml:lang

• iati-organisations/iati-organisation/recipient-org-budget/budget-line/narrative/@xml:lang

• iati-organisations/iati-organisation/recipient-region-budget/recipient-region/narrative/@xml:lang

• iati-organisations/iati-organisation/recipient-region-budget/budget-line/narrative/@xml:lang

• iati-organisations/iati-organisation/recipient-country-budget/recipient-country/narrative/@xml:lang

• iati-organisations/iati-organisation/recipient-country-budget/budget-line/narrative/@xml:lang

• iati-organisations/iati-organisation/total-expenditure/expense-line/narrative/@xml:lang

• iati-organisations/iati-organisation/document-link/recipient-country/narrative/@xml:lang

• iati-organisations/iati-organisation/document-link/title/narrative/@xml:lang

• iati-organisations/iati-organisation/document-link/description/narrative/@xml:lang

• iati-organisations/iati-organisation/document-link/language/@code

• iati-organisations/iati-organisation/@xml:lang

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
aa	Afar
ab	Abkhazian
ae	Avestan
af	Afrikaans
ak	Akan
am	Amharic
an	Aragonese
ar	Arabic
as	Assamese
av	Avaric
ay	Aymara
az	Azerbaijani
ba	Bashkir
be	Belarusian
bg	Bulgarian
bh	Bihari languages
bi	Bislama
bm	Bambara
bn	Bengali
bo	Tibetan
br	Breton
bs	Bosnian
ca	Catalan; Valencian
ce	Chechen
ch	Chamorro
co	Corsican
cr	Cree
cs	Czech
cv	Chuvash
cy	Welsh
da	Danish
de	German
dv	Divehi; Dhivehi; Maldivian
dz	Dzongkha
ee	Ewe
el	Greek
en	English
eo	Esperanto
es	Spanish; Castilian
et	Estonian
eu	Basque
fa	Persian
ff	Fulah
fi	Finnish
fj	Fijian
fo	Faroese
fr	French
fy	Western Frisian
ga	Irish
gd	Gaelic; Scottish Gaelic
gl	Galician
gn	Guarani
gu	Gujarati
gv	Manx
ha	Hausa
he	Hebrew
hi	Hindi
ho	Hiri Motu
hr	Croatian
ht	Haitian; Haitian Creole
hu	Hungarian
hy	Armenian
hz	Herero
id	Indonesian
ig	Igbo
ii	Sichuan Yi; Nuosu
ik	Inupiaq
io	Ido
is	Icelandic
it	Italian
iu	Inuktitut
ja	Japanese
jv	Javanese
ka	Georgian
kg	Kongo
ki	Kikuyu; Gikuyu
kj	Kuanyama; Kwanyama
kk	Kazakh
kl	Kalaallisut; Greenlandic
km	Central Khmer
kn	Kannada
ko	Korean
kr	Kanuri
ks	Kashmiri
ku	Kurdish
kv	Komi
kw	Cornish
ky	Kirghiz; Kyrgyz
la	Latin
lb	Luxembourgish; Letzeburgesch
lg	Ganda
li	Limburgan; Limburger; Limburgish
ln	Lingala
lo	Lao
lt	Lithuanian
lu	Luba-Katanga
lv	Latvian
mg	Malagasy
mh	Marshallese
mi	Maori
mk	Macedonian
ml	Malayalam
mn	Mongolian
mr	Marathi
ms	Malay
mt	Maltese
my	Burmese
na	Nauru
nb	Bokmål, Norwegian; Norwegian Bokmål
nd	Ndebele, North; North Ndebele
ne	Nepali
ng	Ndonga
nl	Dutch; Flemish
nn	Norwegian Nynorsk; Nynorsk, Norwegian
no	Norwegian
nr	Ndebele, South; South Ndebele
nv	Navajo; Navaho
ny	Chichewa; Chewa; Nyanja
oc	Occitan (post 1500)
oj	Ojibwa
om	Oromo
or	Oriya
os	Ossetian; Ossetic
pa	Panjabi; Punjabi
pi	Pali
pl	Polish
ps	Pushto; Pashto
pt	Portuguese
qu	Quechua
rm	Romansh
rn	Rundi
ro	Romanian; Moldavian; Moldovan
ru	Russian
rw	Kinyarwanda
sa	Sanskrit
sc	Sardinian
sd	Sindhi
se	Northern Sami
sg	Sango
si	Sinhala; Sinhalese
sk	Slovak
sl	Slovenian
sm	Samoan
sn	Shona
so	Somali
sq	Albanian
sr	Serbian
ss	Swati
st	Sotho, Southern
su	Sundanese
sv	Swedish
sw	Swahili
ta	Tamil
te	Telugu
tg	Tajik
th	Thai
ti	Tigrinya
tk	Turkmen
tl	Tagalog
tn	Tswana
to	Tonga (Tonga Islands)
tr	Turkish
ts	Tsonga
tt	Tatar
tw	Twi
ty	Tahitian
ug	Uighur; Uyghur
uk	Ukrainian
ur	Urdu
uz	Uzbek
ve	Venda
vi	Vietnamese
vo	Volapük
wa	Walloon
wo	Wolof
xh	Xhosa
yi	Yiddish
yo	Yoruba
za	Zhuang; Chuang
zh	Chinese
zu	Zulu

Loan Repayment Period

CRS Loan Repayment No of Payments

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/crs-add/loan-terms/repayment-plan/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Annual	The loan has 1 repayment per year
2	Semi-annual	The loan has 2 repayments per year
4	Quarterly	The loan has 4 repayments per year
12	Monthly	The loan has 12, monthly repayments per year

Loan Repayment Type

used in additional CRS elements

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/crs-add/loan-terms/repayment-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Equal Principal Payments (EPP)	As required and defined by CRS++ reporting format Column 44
2	Annuity	As required and defined by CRS++ reporting format Column 44
3	Lump sum	As required and defined by CRS++ reporting format Column 44
5	Other	As required and defined by CRS++ reporting format Column 44

Location Type

US NGA Feature Designation Codes

On this codelist ‘category’ is used for the Feature Class.

External URL: http://geonames.nga.mil/namesgaz/

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/location/feature-designation/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
AIRQ	abandoned airfield	abandoned airfield	S
CMPQ	abandoned camp	abandoned camp	S
CNLQ	abandoned canal	abandoned canal	H
MFGQ	abandoned factory	abandoned factory	S
FRMQ	abandoned farm	abandoned farm	S
MNQ	abandoned mine	abandoned mine	S
MSSNQ	abandoned mission	abandoned mission	S
OILQ	abandoned oil well	abandoned oil well	S
PPQ	abandoned police post	abandoned police post	S
PPLQ	abandoned populated place	abandoned populated place	P
PRNQ	abandoned prison	abandoned prison	S
RRQ	abandoned railroad	abandoned railroad	R
RSTNQ	abandoned railroad station	abandoned railroad station	S
RSTPQ	abandoned railroad stop	abandoned railroad stop	S
STMQ	abandoned watercourse	a former stream or distributary no longer carrying flowing water, but still evident due to lakes, wetland, topographic or vegetation patterns	H
WLLQ	abandoned well	abandoned well	H
ADMD	administrative division	an administrative division of a political entity, undifferentiated as to administrative level	A
ADMF	administrative facility	a government building	S
AGRC	agricultural colony	a tract of land set aside for agricultural settlement	L
AGRF	agricultural facility	a building and/or tract of land used for improving agriculture	S
RESA	agricultural reserve	a tract of land reserved for agricultural reclamation and/or development	L
SCHA	agricultural school	a school with a curriculum focused on agriculture	S
AIRB	airbase	an area used to store supplies, provide barracks for air force personnel, hangars and runways for aircraft, and from which operations are initiated	S
AIRF	airfield	a place on land where aircraft land and take off; no facilities provided for the commercial handling of passengers and cargo	S
AIRP	airport	a place where aircraft regularly land and take off, with runways, navigational aids, and major facilities for the commercial handling of passengers and cargo	S
AMTH	amphitheater	an oval or circular structure with rising tiers of seats about a stage or open space	S
STMA	anabranch	a diverging branch flowing out of a main stream and rejoining it downstream	H
ANCH	anchorage	an area where vessels may anchor	H
RDA	ancient road	the remains of a road used by ancient cultures	R
ANS	ancient site	a place where archeological remains, old structures, or cultural artifacts are located	S
WALLA	ancient wall	the remains of a linear defensive stone structure	S
BLDA	apartment building	a building containing several individual apartments	S
AQC	aquaculture facility	facility or area for the cultivation of aquatic animals and plants, especially fish, shellfish, and seaweed, in natural or controlled marine or freshwater environments; underwater agriculture	S
CNLA	aqueduct	a conduit used to carry water	H
ARCH	arch	a natural or man-made structure in the form of an arch	S
LAND	Arctic land	a tract of land in the Arctic	L
AREA	area	a tract of land without homogeneous character or boundaries	L
ISLF	artificial island	an island created by landfill or diking and filling in a wetland, bay, or lagoon	T
RNGA	artillery range	a tract of land used for artillery firing practice	L
ASPH	asphalt lake	a small basin containing naturally occurring asphalt	T
ASTR	astronomical station	a point on the earth whose position has been determined by observations of celestial bodies	S
ASYL	asylum	a facility where the insane are cared for and protected	S
ATHF	athletic field	a tract of land used for playing team sports, and athletic track and field events	S
ATOL	atoll(s)	a ring-shaped coral reef which has closely spaced islands on it encircling a lagoon	T
CTRA	atomic center	a facility where atomic research is carried out	S
BDLD	badlands	an area characterized by a maze of very closely spaced, deep, narrow, steep-sided ravines, and sharp crests and pinnacles	T
BSTN	baling station	a facility for baling agricultural products	S
ESTB	banana plantation	an estate that specializes in the growing of bananas	S
BAN	bank	an establishment for the custody, loan, exchange or issue of money, for the extension of credit, and for facilitating the transmission of funds	S
BNK	bank(s)	an elevation, typically located on a shelf, over which the depth of water is relatively shallow but sufficient for most surface navigation	H
BAR	bar	a shallow ridge or mound of coarse unconsolidated material in a stream channel, at the mouth of a stream, estuary, or lagoon and in the wave-break zone along coasts	T
BRKS	barracks	a building for lodging military personnel	S
BTL	battlefield	a site of a land battle of historical importance	L
BAY	bay	a coastal indentation between two capes or headlands, larger than a cove but smaller than a gulf	H
BAYS	bays	coastal indentations between two capes or headlands, larger than a cove but smaller than a gulf	H
BCH	beach	a shore zone of coarse unconsolidated sediment that extends from the low-water line to the highest reach of storm waves	T
RDGB	beach ridge	a ridge of sand just inland and parallel to the beach, usually in series	T
BCHS	beaches	a shore zone of coarse unconsolidated sediment that extends from the low-water line to the highest reach of storm waves	T
BCN	beacon	a fixed artificial navigation mark	S
BNCH	bench	a long, narrow bedrock platform bounded by steeper slopes above and below, usually overlooking a waterbody	T
BGHT	bight(s)	an open body of water forming a slight recession in a coastline	H
BLHL	blowhole(s)	a hole in coastal rock through which sea water is forced by a rising tide or waves and spurted through an outlet into the air	T
BLOW	blowout(s)	a small depression in sandy terrain, caused by wind erosion	T
BTYD	boatyard	a waterside facility for servicing, repairing, and building small vessels	S
BOG	bog(s)	a wetland characterized by peat forming sphagnum moss, sedge, and other acid-water plants	H
PSTB	border post	a post or station at an international boundary for the regulation of movement of people and goods	S
BLDR	boulder field	a high altitude or high latitude bare, flat area covered with large angular rocks	T
BP	boundary marker	a fixture marking a point along a boundary	S
BRKW	breakwater	a structure erected to break the force of waves at the entrance to a harbor or port	S
MFGB	brewery	one or more buildings where beer is brewed	S
BDG	bridge	a structure erected across an obstacle such as a stream, road, etc., in order to carry roads, railroads, and pedestrians across	S
ZNB	buffer zone	a zone recognized as a buffer between two nations in which military presence is minimal or absent	A
BLDG	building(s)	a structure built for permanent use, as a house, factory, etc.	S
BUR	burial cave(s)	a cave used for human burials	S
BUSH	bush(es)	a small clump of conspicuous bushes in an otherwise bare area	V
CTRB	business center	a place where a number of businesses are located	L
BUTE	butte(s)	a small, isolated, usually flat-topped hill with steep sides	T
CARN	cairn	a heap of stones erected as a landmark or for other purposes	S
CLDA	caldera	a depression measuring kilometers across formed by the collapse of a volcanic mountain	T
CMP	camp(s)	a site occupied by tents, huts, or other shelters for temporary use	S
CNL	canal	an artificial watercourse	H
CNLB	canal bend	a conspicuously curved or bent section of a canal	H
TNLC	canal tunnel	a tunnel through which a canal passes	H
STMC	canalized stream	a stream that has been substantially ditched, diked, or straightened	H
MFGC	cannery	a building where food items are canned	S
CNYN	canyon	a deep, narrow valley with steep sides cutting into a plateau or mountainous area	T
CAPE	cape	a land area, more prominent than a point, projecting into the sea and marking a notable change in coastal direction	T
PPLC	capital of a political entity	capital of a political entity	P
RTE	caravan route	the route taken by caravans	R
CSNO	casino	a building used for entertainment, especially gambling	S
CSTL	castle	a large fortified building or set of buildings	S
TNKD	cattle dipping tank	a small artificial pond used for immersing cattle in chemically treated water for disease control	S
CSWY	causeway	a raised roadway across wet ground or shallow water	R
CAVE	cave(s)	an underground passageway or chamber, or cavity on the side of a cliff	S
CMTY	cemetery	a burial place or ground	S
CHN	channel	the deepest part of a stream, bay, lagoon, or strait, through which the main current flows	H
MNCR	chrome mine(s)	a mine where chrome ore is extracted	S
CH	church	a building for public Christian worship	S
CRQ	cirque	a bowl-like hollow partially surrounded by cliffs or steep slopes at the head of a glaciated valley	T
CRQS	cirques	bowl-like hollows partially surrounded by cliffs or steep slopes at the head of a glaciated valley	T
CLG	clearing	an area in a forest with trees removed	L
CFT	cleft(s)	a deep narrow slot, notch, or groove in a coastal cliff	T
CLF	cliff(s)	a high, steep to perpendicular slope overlooking a waterbody or lower area	T
HSPC	clinic	a medical facility associated with a hospital for outpatients	S
MNC	coal mine(s)	a mine where coal is extracted	S
COLF	coalfield	a region in which coal deposits of possible economic value occur	L
CST	coast	a zone of variable width straddling the shoreline	L
STNC	coast guard station	a facility from which the coast is guarded by armed vessels	S
GRVC	coconut grove	a planting of coconut trees	V
SCHC	college	the grounds and buildings of an institution of higher learning	S
CMN	common	a park or pasture for community use	L
COMC	communication center	a facility, including buildings, antennae, towers and electronic equipment for receiving and transmitting information	S
CTRCM	community center	a facility for community recreation and other activities	S
CNS	concession area	a lease of land by a government for economic development, e.g., mining, forestry	L
CONE	cone(s)	a conical landform composed of mud or volcanic material	T
CNFL	confluence	a place where two or more streams or intermittent streams flow together	H
CRSU	continental rise	a gentle slope rising from oceanic depths towards the foot of a continental slope	U
CVNT	convent	a building where a community of nuns lives in seclusion	S
MNCU	copper mine(s)	a mine where copper ore is extracted	S
MFGCU	copper works	a facility for processing copper ore	S
RFC	coral reef(s)	a surface-navigation hazard composed of coral	H
CRRL	corral(s)	a pen or enclosure for confining or capturing animals	S
CRDR	corridor	a strip or area of land having significance as an access way	T
ESTC	cotton plantation	an estate specializing in the cultivation of cotton	S
HSEC	country house	a large house, mansion, or chateau, on a large estate	S
CTHSE	courthouse	a building in which courts of law are held	S
COVE	cove(s)	a small coastal indentation, smaller than a bay	H
LKC	crater lake	a lake in a crater or caldera	H
LKSC	crater lakes	lakes in a crater or caldera	H
CRTR	crater(s)	a generally circular saucer or bowl-shaped depression caused by volcanic or meteorite explosive action	T
CUET	cuesta(s)	an asymmetric ridge formed on tilted strata	T
CULT	cultivated area	an area under cultivation	V
CRNT	current	a horizontal flow of water in a given direction with uniform velocity	H
CSTM	customs house	a building in a port where customs and duties are paid, and where vessels are entered and cleared	S
PSTC	customs post	a building at an international boundary where customs and duties are paid on goods	S
CUTF	cutoff	a channel formed as a result of a stream cutting through a meander neck	H
DARY	dairy	a facility for the processing, sale and distribution of milk or milk products	S
DAM	dam	a barrier constructed across a stream to impound water	S
DEPU	deep	a localized deep area within the confines of a larger feature, such as a trough, basin or trench	U
DLTA	delta	a flat plain formed by alluvial deposits at the mouth of a stream	T
PCLD	dependent political entity	dependent political entity	A
DPR	depression(s)	a low area surrounded by higher land and usually characterized by interior drainage	T
DSRT	desert	a large area with little or no vegetation due to extreme environmental conditions	T
PPLW	destroyed populated place	a village, town or city destroyed by a natural disaster, or by war	P
MNDT	diatomite mine(s)	a place where diatomaceous earth is extracted	S
DIKE	dike	an earth or stone embankment usually constructed for flood or stream control	S
DIP	diplomatic facility	office, residence, or facility of a foreign government, which may include an embassy, consulate, chancery, office of charge d’affaires, or other diplomatic, economic, military, or cultural mission	S
HSPD	dispensary	a building where medical or dental aid is dispensed	S
STMD	distributary(-ies)	a branch which flows away from the main stream, as in a delta or irrigation canal	H
DTCH	ditch	a small artificial watercourse dug for draining or irrigating the land	H
DTCHM	ditch mouth(s)	an area where a drainage ditch enters a lagoon, lake or bay	H
DVD	divide	a line separating adjacent drainage basins	T
DCK	dock(s)	a waterway between two piers, or cut into the land for the berthing of ships	H
DCKB	docking basin	a part of a harbor where ships dock	H
DCKY	dockyard	a facility for servicing, building, or repairing ships	S
BSND	drainage basin	an area drained by a stream	L
CNLD	drainage canal	an artificial waterway carrying water away from a wetland or from drainage ditches	H
DTCHD	drainage ditch	a ditch which serves to drain the land	H
DCKD	dry dock	a dock providing support for a vessel, and means for removing the water so that the bottom of the vessel can be exposed	S
SBED	dry stream bed	a channel formerly containing the water of a stream	T
DUNE	dune(s)	a wave form, ridge or star shape feature composed of sand	T
RGNE	economic region	a region of a country established for economic development or for statistical purposes	L
SCRP	escarpment	a long line of cliffs or steep slopes separating level surfaces above and below	T
EST	estate(s)	a large commercialized agricultural landholding with associated buildings and other facilities	S
ESTY	estuary	a funnel-shaped stream mouth or embayment where fresh water mixes with sea water under tidal influences	H
STNE	experiment station	a facility for carrying out experiments	S
FCL	facility	a building or buildings housing a center, institute, foundation, hospital, prison, mission, courthouse, etc.	S
CTRF	facility center	a place where more than one facility is situated	S
MFG	factory	one or more buildings where goods are manufactured, processed or fabricated	S
FAN	fan(s)	a fan-shaped wedge of coarse alluvium with apex merging with a mountain stream bed and the fan spreading out at a low angle slope onto an adjacent plain	T
FRM	farm	a tract of land with associated buildings devoted to agriculture	S
PPLF	farm village	a populated place where the population is largely engaged in agricultural activities	P
FRMS	farms	tracts of land with associated buildings devoted to agriculture	S
FRMT	farmstead	the buildings and adjacent service areas of a farm	S
FY	ferry	a boat or other floating conveyance and terminal facilities regularly used to transport people and vehicles across a waterbody	S
FYT	ferry terminal	a place where ferries pick-up and discharge passengers, vehicles and or cargo	S
FLD	field(s)	an open as opposed to wooded area	L
FIRE	fire station	building housing firefighters and/or fire fighting equipment	S
ADM1	first-order administrative division	a primary administrative division of a country, such as a state in the United States	A
FISH	fishing area	a fishing ground, bank or area where fishermen go to catch fish	H
PNDSF	fishponds	ponds or enclosures in which fish are kept or raised	H
FSR	fissure	a crack associated with volcanism	T
FJD	fjord	a long, narrow, steep-walled, deep-water arm of the sea at high latitudes, usually along mountainous coasts	H
FJDS	fjords	long, narrow, steep-walled, deep-water arms of the sea at high latitudes, usually along mountainous coasts	H
FORD	ford	a shallow part of a stream which can be crossed on foot or by land vehicle	T
RESF	forest reserve	a forested area set aside for preservation or controlled use	L
STNF	forest station	a collection of buildings and facilities for carrying out forest management	S
FRST	forest(s)	an area dominated by tree vegetation	V
INLTQ	former inlet	an inlet which has been filled in, or blocked by deposits	H
MLSGQ	former sugar mill	a sugar mill no longer used as a sugar mill	S
FT	fort	a defensive structure or earthworks	S
FRSTF	fossilized forest	a forest fossilized by geologic processes and now exposed at the earth’s surface	V
FNDY	foundry	a building or works where metal casting is carried out	S
ADM4	fourth-order administrative division	a subdivision of a third-order administrative division	A
ZNF	free trade zone	an area, usually a section of a port, where goods may be received and shipped free of customs duty and of most customs regulations	S
PCLF	freely associated state	freely associated state	A
DPOF	fuel depot	an area where fuel is stored	S
GAP	gap	a low place in a ridge, not used for transportation	T
GDN	garden(s)	an enclosure for displaying selected plant or animal life	S
GOSP	gas-oil separator plant	a facility for separating gas from oil	S
GASF	gasfield	an area containing a subterranean store of natural gas of economic value	L
GATE	gate	a controlled access entrance or exit	S
GYSR	geyser	a type of hot spring with intermittent eruptions of jets of hot water and steam	H
GHAT	ghāt	a set of steps leading to a river, which are of religious significance, and at their base is usually a platform for bathing	S
GLCR	glacier(s)	a mass of ice, usually at high latitudes or high elevations, with sufficient thickness to flow away from the source area in lobes, tongues, or masses	H
MNAU	gold mine(s)	a mine where gold ore, or alluvial gold is extracted	S
RECG	golf course	a recreation field where golf is played	S
GRGE	gorge(s)	a short, narrow, steep-sided section of a stream valley	T
GRSLD	grassland	an area dominated by grass vegetation	V
GRVE	grave	a burial site	S
GVL	gravel area	an area covered with gravel	L
GRAZ	grazing area	an area of grasses and shrubs used for grazing	L
GHSE	guest house	a house used to provide lodging for paying guests	S
GULF	gulf	a large recess in the coastline, larger than a bay	H
HLT	halting place	a place where caravans stop for rest	S
HMCK	hammock(s)	a patch of ground, distinct from and slightly above the surrounding plain or wetland. Often occurs in groups	T
AIRG	hangar	a covered and usually enclosed area for housing and repairing aircraft	S
VALG	hanging valley	a valley the floor of which is notably higher than the valley or shore to which it leads; most common in areas that have been glaciated	T
HBR	harbor(s)	a haven or space of deep water so sheltered by the adjacent land as to afford a safe anchorage for ships	H
HDLD	headland	a high projection of land extending into a large body of water beyond the line of the coast	T
STMH	headwaters	the source and upper part of a stream, including the upper drainage basin	H
HTH	heath	an upland moor or sandy area dominated by low shrubby vegetation including heather	V
AIRH	heliport	a place where helicopters land and take off	S
HERM	hermitage	a secluded residence, usually for religious sects	S
HLL	hill	a rounded elevation of limited extent rising above the surrounding land with local relief of less than 300m	T
HLLS	hills	rounded elevations of limited extent rising above the surrounding land with local relief of less than 300m	T
ADMDH	historical administrative division	a former administrative division of a political entity, undifferentiated as to administrative level	A
ADM1H	historical first-order administrative division	a former first-order administrative division	A
ADM4H	historical fourth-order administrative division	a former fourth-order administrative division	A
PCLH	historical political entity	a former political entity	A
PPLH	historical populated place	a populated place that no longer exists	P
RRH	historical railroad	a former permanent twin steel-rail track on which freight and passenger cars move long distances	R
RSTNH	historical railroad station	a former facility comprising ticket office, platforms, etc. for loading and unloading train passengers and freight	S
RGNH	historical region	a former area distinguished by one or more observable physical or cultural characteristics	L
ADM2H	historical second-order administrative division	a former second-order administrative division	A
HSTS	historical site	a place of historical importance	S
ADM3H	historical third-order administrative division	a former third-order administrative division	A
UFHU	historical undersea feature	an undersea feature whose existence has been subsequently disproved	U
HMSD	homestead	a residence, owner’s or manager’s, on a sheep or cattle station, woolshed, outcamp, or Aboriginal outstation, specific to Australia and New Zealand	S
HSP	hospital	a building in which sick or injured, especially those confined to bed, are medically treated	S
SPNT	hot spring(s)	a place where hot ground water flows naturally out of the ground	H
HTL	hotel	a building providing lodging and/or meals for the public	S
HSE	house(s)	a building used as a human habitation	S
DEVH	housing development	a tract of land on which many houses of similar design are built according to a development plan	L
RESH	hunting reserve	a tract of land used primarily for hunting	L
HUT	hut	a small primitive house	S
HUTS	huts	small primitive houses	S
PSH	hydroelectric power station	a building where electricity is generated from water power	S
CAPG	icecap	a dome-shaped mass of glacial ice covering an area of mountain summits or other high lands; smaller than an ice sheet	H
DPRG	icecap depression	a comparatively depressed area on an icecap	H
DOMG	icecap dome	a comparatively elevated area on an icecap	H
RDGG	icecap ridge	a linear elevation on an icecap	H
PCLI	independent political entity	independent political entity	A
INDS	industrial area	an area characterized by industrial activity	L
INLT	inlet	a narrow waterway extending into the land, or connecting a bay or lagoon with a larger body of water	H
STNI	inspection station	a station at which vehicles, goods, and people are inspected	S
TRGD	interdune trough(s)	a long wind-swept trough between parallel longitudinal dunes	T
INTF	interfluve	a relatively undissected upland between adjacent stream valleys	T
LKI	intermittent lake	intermittent lake	H
LKSI	intermittent lakes	intermittent lakes	H
LKOI	intermittent oxbow lake	intermittent oxbow lake	H
PNDI	intermittent pond	intermittent pond	H
PNDSI	intermittent ponds	intermittent ponds	H
POOLI	intermittent pool	intermittent pool	H
RSVI	intermittent reservoir	intermittent reservoir	H
LKNI	intermittent salt lake	intermittent salt lake	H
LKSNI	intermittent salt lakes	intermittent salt lakes	H
PNDNI	intermittent salt pond(s)	intermittent salt pond(s)	H
STMI	intermittent stream	intermittent stream	H
WTLDI	intermittent wetland	intermittent wetland	H
RDIN	intersection	a junction of two or more highways by a system of separate levels that permit traffic to pass from one to another without the crossing of traffic streams	S
MNFE	iron mine(s)	a mine where iron ore is extracted	S
FLDI	irrigated field(s)	a tract of level or terraced land which is irrigated	L
CNLI	irrigation canal	a canal which serves as a main conduit for irrigation water	H
DTCHI	irrigation ditch	a ditch which serves to distribute irrigation water	H
SYSI	irrigation system	a network of ditches and one or more of the following elements: water supply, reservoir, canal, pump, well, drain, etc.	H
ISL	island	a tract of land, smaller than a continent, surrounded by water at high water	T
ISLS	islands	tracts of land, smaller than a continent, surrounded by water at high water	T
STLMT	Israeli settlement	Israeli settlement	P
ISTH	isthmus	a narrow strip of land connecting two larger land masses and bordered by water	T
JTY	jetty	a structure built out into the water at a river mouth or harbor entrance to regulate currents and silting	S
KRST	karst area	a distinctive landscape developed on soluble rock such as limestone characterized by sinkholes, caves, disappearing streams, and underground drainage	T
CMPLA	labor camp	a camp used by migrant or temporary laborers	S
LGN	lagoon	a shallow coastal waterbody, completely or partly separated from a larger body of water by a barrier island, coral reef or other depositional feature	H
LGNS	lagoons	shallow coastal waterbodies, completely or partly separated from a larger body of water by a barrier island, coral reef or other depositional feature	H
LK	lake	a large inland body of standing water	H
LBED	lake bed(s)	a dried up or drained area of a former lake	H
CHNL	lake channel(s)	that part of a lake having water deep enough for navigation between islands, shoals, etc.	H
RGNL	lake region	a tract of land distinguished by numerous lakes	L
LKS	lakes	large inland bodies of standing water	H
ISLT	land-tied island	a coastal island connected to the mainland by barrier beaches, levees or dikes	T
LNDF	landfill	a place for trash and garbage disposal in which the waste is buried between layers of earth to build up low-lying land	S
LDNG	landing	a place where boats receive or discharge passengers and freight, but lacking most port facilities	S
LAVA	lava area	an area of solidified lava	T
MNPB	lead mine(s)	a mine where lead ore is extracted	S
LTER	leased area	a tract of land leased by the United Kingdom from the People’s Republic of China to form part of Hong Kong	A
LEPC	leper colony	a settled area inhabited by lepers in relative isolation	S
HSPL	leprosarium	an asylum or hospital for lepers	S
LEV	levee	a natural low embankment bordering a distributary or meandering stream; often built up artificially to control floods	T
LTHSE	lighthouse	a distinctive structure exhibiting a major navigation light	S
MFGLM	limekiln	a furnace in which limestone is reduced to lime	S
GOVL	local government office	a facility housing local governmental offices, usually a city, town, or village hall	S
LCTY	locality	a minor area or place of unspecified or mixed character and indefinite boundaries	L
LOCK	lock(s)	a basin in a waterway with gates at each end by means of which vessels are passed from one water level to another	S
CMPL	logging camp	a camp used by loggers	S
STMSB	lost river	a surface stream that disappears into an underground channel, or dries up in an arid area	H
MVA	maneuver area	a tract of land where military field exercises are carried out	L
ISLM	mangrove island	a mangrove swamp surrounded by a waterbody	T
MGV	mangrove swamp	a tropical tidal mud flat characterized by mangrove vegetation	H
MAR	marina	a harbor facility for small boats, yachts, etc.	S
CHNM	marine channel	that part of a body of water deep enough for navigation through an area otherwise not suitable	H
SCHN	maritime school	a school at which maritime sciences form the core of the curriculum	S
MKT	market	a place where goods are bought and sold at regular intervals	S
MRSH	marsh(es)	a wetland dominated by grass-like vegetation	H
MDW	meadow	a small, poorly drained area dominated by grassy vegetation	V
NKM	meander neck	a narrow strip of land between the two limbs of a meander loop at its narrowest point	T
CTRM	medical center	a complex of health care buildings including two or more of the following: hospital, medical school, clinic, pharmacy, doctor’s offices, etc.	S
MESA	mesa(s)	a flat-topped, isolated elevation with steep slopes on all sides, less extensive than a plateau	T
STNM	meteorological station	a station at which weather elements are recorded	S
MILB	military base	a place used by an army or other armed service for storing arms and supplies, and for accommodating and training troops, a base from which operations can be initiated	L
INSM	military installation	a facility for use of and control by armed forces	S
SCHM	military school	a school at which military science forms the core of the curriculum	S
ML	mill(s)	a building housing machines for transforming, shaping, finishing, grinding, or extracting products	S
MN	mine(s)	a site where mineral ores are extracted from the ground by excavating surface pits and subterranean passages	S
MNA	mining area	an area of mine sites where minerals and ores are extracted	L
CMPMN	mining camp	a camp used by miners	S
MSSN	mission	a place characterized by dwellings, school, church, hospital and other facilities operated by a religious group for the purpose of providing charitable services and to propagate religion	S
MOLE	mole	a massive structure of masonry or large stones serving as a pier or breakwater	S
MSTY	monastery	a building and grounds where a community of monks lives in seclusion	S
MNMT	monument	a commemorative structure or statue	S
MOOR	moor(s)	an area of open ground overlaid with wet peaty soils	H
MRN	moraine	a mound, ridge, or other accumulation of glacial till	T
MSQE	mosque	a building for public Islamic worship	S
MND	mound(s)	a low, isolated, rounded hill	T
MT	mountain	an elevation standing high above the surrounding area with small summit area, steep slopes and local relief of 300m or more	T
MTS	mountains	a mountain range or a group of mountains or high ridges	T
FLTM	mud flat(s)	a relatively level area of mud either between high and low tide lines, or subject to flooding	H
MFGM	munitions plant	a factory where ammunition is made	S
MUS	museum	a building where objects of permanent interest in one or more of the arts and sciences are preserved and exhibited	S
NRWS	narrows	a navigable narrow part of a bay, strait, river, etc.	H
TNLN	natural tunnel	a cave that is open at both ends	R
RESN	nature reserve	an area reserved for the maintenance of a natural habitat	L
NVB	naval base	an area used to store supplies, provide barracks for troops and naval personnel, a port for naval vessels, and from which operations are initiated	L
CNLN	navigation canal(s)	a watercourse constructed for navigation of vessels	H
CHNN	navigation channel	a buoyed channel of sufficient depth for the safe navigation of vessels	H
MNNI	nickel mine(s)	a mine where nickel ore is extracted	S
NOV	novitiate	a religious house or school where novices are trained	S
PSN	nuclear power station	nuclear power station	S
NTK	nunatak	a rock or mountain peak protruding through glacial ice	T
NTKS	nunataks	rocks or mountain peaks protruding through glacial ice	T
NSY	nursery(-ies)	a place where plants are propagated for transplanting or grafting	S
OAS	oasis(-es)	an area in a desert made productive by the availability of water	L
OBPT	observation point	a wildlife or scenic observation point	S
OBS	observatory	a facility equipped for observation of atmospheric or space phenomena	S
OCN	ocean	one of the major divisions of the vast expanse of salt water covering part of the earth	H
BLDO	office building	commercial building where business and/or services are conducted	S
CMPO	oil camp	a camp used by oilfield workers	S
ESTO	oil palm plantation	an estate specializing in the cultivation of oil palm trees	S
OILP	oil pipeline	a pipeline used for transporting oil	R
OILJ	oil pipeline junction	a section of an oil pipeline where two or more pipes join together	S
TRMO	oil pipeline terminal	a tank farm or loading facility at the end of an oil pipeline	S
PMPO	oil pumping station	a facility for pumping oil through a pipeline	S
OILR	oil refinery	a facility for converting crude oil into refined petroleum products	S
OILW	oil well	a well from which oil may be pumped	S
OILF	oilfield	an area containing a subterranean store of petroleum of economic value	L
GRVO	olive grove	a planting of olive trees	V
MLO	olive oil mill	a mill where oil is extracted from olives	S
OCH	orchard(s)	a planting of fruit or nut trees	V
MLM	ore treatment plant	a facility for improving the metal content of ore by concentration	S
OVF	overfalls	an area of breaking waves caused by the meeting of currents or by waves moving against the current	H
LKO	oxbow lake	a crescent-shaped lake commonly found adjacent to meandering streams	H
PGDA	pagoda	a tower-like storied structure, usually a Buddhist shrine	S
PAL	palace	a large stately house, often a royal or presidential residence	S
GRVP	palm grove	a planting of palm trees	V
RESP	palm tree reserve	an area of palm trees where use is controlled	L
PAN	pan	a near-level shallow, natural depression or basin, usually containing an intermittent lake, pond, or pool	T
PANS	pans	a near-level shallow, natural depression or basin, usually containing an intermittent lake, pond, or pool	T
PRSH	parish	an ecclesiastical district	A
PRK	park	an area, often of forested land, maintained as a place of beauty, or for recreation	L
PRKGT	park gate	a controlled access to a park	S
PRKHQ	park headquarters	a park administrative facility	S
GARG	parking garage	a building or underground facility used exclusively for parking vehicles	S
PKLT	parking lot	an area used for parking vehicles	S
PASS	pass	a break in a mountain range or other high obstruction, used for transportation from one side to the other [See also gap]	T
PSTP	patrol post	a post from which patrols are sent out	S
PK	peak	a pointed elevation atop a mountain, ridge, or other hypsographic feature	T
PKS	peaks	pointed elevations atop a mountain, ridge, or other hypsographic features	T
PEAT	peat cutting area	an area where peat is harvested	L
PEN	peninsula	an elongate area of land projecting into a body of water and nearly surrounded by water	T
BSNP	petroleum basin	an area underlain by an oil-rich structural basin	L
MFGPH	phosphate works	a facility for producing fertilizer	S
PIER	pier	a structure built out into navigable water on piles providing berthing for ships and recreation	S
GRVPN	pine grove	a planting of pine trees	V
MNPL	placer mine(s)	a place where heavy metals are concentrated and running water is used to extract them from unconsolidated sediments	S
PLN	plain(s)	an extensive area of comparatively level to gently undulating land, lacking surface irregularities, and usually adjacent to a higher area	T
PLAT	plateau	an elevated plain with steep slopes on one or more sides, and often with incised streams	T
PT	point	a tapering piece of land projecting into a body of water, less prominent than a cape	T
PTS	points	tapering pieces of land projecting into a body of water, less prominent than a cape	T
PLDR	polder	an area reclaimed from the sea by diking and draining	T
PP	police post	a building in which police are stationed	S
PCL	political entity	political entity	A
PND	pond	a small standing waterbody	H
PNDS	ponds	small standing waterbodies	H
POOL	pool(s)	a small and comparatively still, deep part of a larger body of water such as a stream or harbor; or a small body of standing water	H
PPLL	populated locality	an area similar to a locality but with a small group of dwellings or other buildings	P
PPL	populated place	a city, town, village, or other agglomeration of buildings where people live and work	P
PPLS	populated places	cities, towns, villages, or other agglomerations of buildings where people live and work	P
PRT	port	a place provided with terminal and transfer facilities for loading and discharging waterborne cargo or passengers, usually located in a harbor	L
PTGE	portage	a place where boats, goods, etc., are carried overland between navigable waters	R
PO	post office	a public building in which mail is received, sorted and distributed	S
PS	power station	a facility for generating electric power	S
PRN	prison	a facility for confining prisoners	S
PRMN	promenade	a place for public walking, usually along a beach front	R
PROM	promontory(-ies)	a bluff or prominent hill overlooking or projecting into a lowland	T
PYR	pyramid	an ancient massive structure of square ground plan with four triangular faces meeting at a point and used for enclosing tombs	S
PYRS	pyramids	ancient massive structures of square ground plan with four triangular faces meeting at a point and used for enclosing tombs	S
MNQR	quarry(-ies)	a surface mine where building stone or gravel and sand, etc. are extracted	S
QUAY	quay	a structure of solid construction along a shore or bank which provides berthing for ships and which generally provides cargo handling facilities	S
QCKS	quicksand	an area where loose sand with water moving through it may become unstable when heavy objects are placed at the surface, causing them to sink	L
RECR	racetrack	a track where races are held	S
OBSR	radio observatory	a facility equipped with an array of antennae for receiving radio waves from space	S
STNR	radio station	a facility for producing and transmitting information by radio waves	S
RR	railroad	a permanent twin steel-rail track on which freight and passenger cars move long distances	R
RJCT	railroad junction	a place where two or more railroad tracks join	R
RSD	railroad siding	a short track parallel to and joining the main track	S
RSGNL	railroad signal	a signal at the entrance of a particular section of track governing the movement of trains	S
RSTN	railroad station	a facility comprising ticket office, platforms, etc. for loading and unloading train passengers and freight	S
RSTP	railroad stop	a place lacking station facilities where trains stop to pick up and unload passengers and freight	S
TNLRR	railroad tunnel	a tunnel through which a railroad passes	R
RYD	railroad yard	a system of tracks used for the making up of trains, and switching and storing freight cars	R
RNCH	ranch(es)	a large farm specializing in extensive grazing of livestock	S
RPDS	rapids	a turbulent section of a stream associated with a steep, irregular stream bed	H
RVN	ravine(s)	a small, narrow, deep, steep-sided stream channel, smaller than a gorge	H
RCH	reach	a straight section of a navigable stream or channel between two bends	H
RF	reef(s)	a surface-navigation hazard composed of consolidated material	H
PRNJ	reformatory	a facility for confining, training, and reforming young law offenders	S
CMPRF	refugee camp	a camp used by refugees	S
RGN	region	an area distinguished by one or more observable physical or cultural characteristics	L
CTRR	religious center	a facility where more than one religious activity is carried out, e.g., retreat, school, monastery, worship	S
PPLR	religious populated place	a populated place whose population is largely engaged in religious occupations	P
RLG	religious site	an ancient site of significant religious importance	S
ITTR	research institute	a facility where research is carried out	S
RESV	reservation	a tract of land set aside for aboriginal, tribal, or native populations	L
RES	reserve	a tract of public land reserved for future use or restricted as to use	L
RSV	reservoir(s)	an artificial pond or lake	H
RSRT	resort	a specialized facility for vacation, health, or participation sports activities	S
RHSE	resthouse	a structure maintained for the rest and shelter of travelers	S
RLGR	retreat	a place of temporary seclusion, especially for religious groups	S
RDGE	ridge(s)	a long narrow elevation with steep sides, and a more or less continuous crest	T
RD	road	an open way with improved surface for transportation of animals, people and vehicles	R
RDB	road bend	a conspicuously curved or bent section of a road	R
RDCUT	road cut	an excavation cut through a hill or ridge for a road	R
RDJCT	road junction	a place where two or more roads join	R
TNLRD	road tunnel	a tunnel through which a road passes	R
RDST	roadstead	an open anchorage affording less protection than a harbor	H
RK	rock	a conspicuous, isolated rocky mass	T
HMDA	rock desert	a relatively sand-free, high bedrock plateau in a hot desert, with or without a gravel veneer	T
RKFL	rockfall	an irregular mass of fallen rock at the base of a cliff or steep slope	T
RKS	rocks	conspicuous, isolated rocky masses	T
RKRY	rookery	a breeding place of a colony of birds or seals	S
ESTR	rubber plantation	an estate which specializes in growing and tapping rubber trees	S
RUIN	ruin(s)	a destroyed or decayed structure which is no longer functional	S
BDGQ	ruined bridge	a destroyed or decayed bridge which is no longer functional	S
DAMQ	ruined dam	a destroyed or decayed dam which is no longer functional	S
SBKH	sabkha(s)	a salt flat or salt encrusted plain subject to periodic inundation from flooding or high tides	H
SDL	saddle	a broad, open pass crossing a ridge or between hills or mountains	T
SALT	salt area	a shallow basin or flat where salt accumulates after periodic inundation	L
MFGN	salt evaporation ponds	diked salt ponds used in the production of solar evaporated salt	H
LKN	salt lake	an inland body of salt water with no outlet	H
LKSN	salt lakes	inland bodies of salt water with no outlet	H
MRSHN	salt marsh	a flat area, subject to periodic salt water inundation, dominated by grassy salt-tolerant plants	H
MNN	salt mine(s)	a mine from which salt is extracted	S
PNDN	salt pond	a small standing body of salt water often in a marsh or swamp, usually along a seacoast	H
PNDSN	salt ponds	small standing bodies of salt water often in a marsh or swamp, usually along a seacoast	H
SNTR	sanatorium	a facility where victims of physical or mental disorders are treated	S
SAND	sand area	a tract of land covered with sand	T
ERG	sandy desert	an extensive tract of shifting sand and sand dunes	T
STNS	satellite station	a facility for tracking and communicating with orbiting satellites	S
MLSW	sawmill	a mill where logs or lumber are sawn to specified shapes and sizes	S
SCH	school	building(s) where instruction in one or more branches of knowledge takes place	S
ADMS	school district	school district	A
STNB	scientific research base	a scientific facility used as a base from which research is carried out or monitored	S
SCRB	scrubland	an area of low trees, bushes, and shrubs stunted by some environmental limitation	V
SEA	sea	a large body of salt water more or less confined by continuous land or chains of islands forming a subdivision of an ocean	H
SCNU	seachannel	a continuously sloping, elongated depression commonly found in fans or plains and customarily bordered by levees on one or two sides	U
SCSU	seachannels	continuously sloping, elongated depressions commonly found in fans or plains and customarily bordered by levees on one or two sides	U
SMU	seamount	an elevation rising generally more than 1,000 meters and of limited extent across the summit	U
SMSU	seamounts	elevations rising generally more than 1,000 meters and of limited extent across the summit	U
AIRS	seaplane landing area	a place on a waterbody where floatplanes land and take off	H
PPLA	seat of a first-order administrative division	seat of a first-order administrative division (PPLC takes precedence over PPLA)	P
PPLA4	seat of a fourth-order administrative division	seat of a fourth-order administrative division	P
PPLA2	seat of a second-order administrative division	seat of a second-order administrative division	P
PPLA3	seat of a third-order administrative division	seat of a third-order administrative division	P
ADM2	second-order administrative division	a subdivision of a first-order administrative division	A
BNKX	section of bank	section of bank	H
CNLX	section of canal	section of canal	H
ESTX	section of estate	section of estate	S
HBRX	section of harbor	section of harbor	H
PCLIX	section of independent political entity	section of independent political entity	A
STMIX	section of intermittent stream	section of intermittent stream	H
ISLX	section of island	section of island	T
LGNX	section of lagoon	section of lagoon	H
LKX	section of lake	section of lake	H
PENX	section of peninsula	section of peninsula	T
PLNX	section of plain	section of plain	T
PLATX	section of plateau	section of plateau	T
PPLX	section of populated place	section of populated place	P
RFX	section of reef	section of reef	H
STMX	section of stream	section of stream	H
VALX	section of valley	section of valley	T
WADX	section of wadi	section of wadi	H
FLLSX	section of waterfall(s)	section of waterfall(s)	H
PCLS	semi-independent political entity	semi-independent political entity	A
SWT	sewage treatment plant	facility for the processing of sewage and/or wastewater	S
SHPF	sheepfold	a fence or wall enclosure for sheep and other small herd animals	S
SHOL	shoal(s)	a surface-navigation hazard composed of unconsolidated material	H
SHOPC	shopping center or mall	an urban shopping area featuring a variety of shops surrounding a usually open-air concourse reserved for pedestrian traffic; or a large suburban building or group of buildings containing various shops with associated passageways	S
SHOR	shore	a narrow zone bordering a waterbody which covers and uncovers at high and low water, respectively	T
SHRN	shrine	a structure or place memorializing a person or religious concept	S
SILL	sill	the low part of a gap or saddle separating basins	H
SINK	sinkhole	a small crater-shape depression in a karst area	T
ESTSL	sisal plantation	an estate that specializes in growing sisal	S
SLID	slide	a mound of earth material, at the base of a slope and the associated scoured area	T
SLP	slope(s)	a surface with a relatively uniform slope angle	T
SLCE	sluice	a conduit or passage for carrying off surplus water from a waterbody, usually regulated by means of a sluice gate	S
SNOW	snowfield	an area of permanent snow and ice forming the accumulation area of a glacier	L
SD	sound	a long arm of the sea forming a channel between the mainland and an island or islands; or connecting two larger bodies of water	H
SPA	spa	a resort area usually developed around a medicinal spring	S
CTRS	space center	a facility for launching, tracking, or controlling satellites and space vehicles	S
SPLY	spillway	a passage or outlet through which surplus water flows over, around or through a dam	S
SPIT	spit	a narrow, straight or curved continuation of a beach into a waterbody	T
SPNG	spring(s)	a place where ground water flows naturally out of the ground	H
SPUR	spur(s)	a subordinate ridge projecting outward from a hill, mountain or other elevation	T
SQR	square	a broad, open, public area near the center of a town or city	S
STBL	stable	a building for the shelter and feeding of farm animals, especially horses	S
STDM	stadium	a structure with an enclosure for athletic games with tiers of seats for spectators	S
STPS	steps	stones or slabs placed for ease in ascending or descending a steep slope	S
STKR	stock route	a route taken by livestock herds	R
REG	stony desert	a desert plain characterized by a surface veneer of gravel and stones	T
RET	store	a building where goods and/or services are offered for sale	S
SHSE	storehouse	a building for storing goods, especially provisions	S
STRT	strait	a relatively narrow waterway, usually narrower and less extensive than a sound, connecting two larger bodies of water	H
STM	stream	a body of running water moving to a lower level in a channel on land	H
BNKR	stream bank	a sloping margin of a stream channel which normally confines the stream to its channel on land	H
STMB	stream bend	a conspicuously curved or bent segment of a stream	H
STMGS	stream gauging station	named place where a measuring station for a watercourse, reservoir or other water body exists	S
STMM	stream mouth(s)	a place where a stream discharges into a lagoon, lake, or the sea	H
STMS	streams	bodies of running water moving to a lower level in a channel on land	H
ST	street	a paved urban thoroughfare	R
DAMSB	sub-surface dam	a dam put down to bedrock in a sand river	S
SUBW	subway	a railroad used for mass public transportation primarily in urban areas, all or part of the system may be located below, above, or at ground level	S
SUBS	subway station	a facility comprising ticket office, platforms, etc. for loading and unloading subway passengers	S
MLSG	sugar mill	a facility where sugar cane is processed into raw sugar	S
ESTSG	sugar plantation	an estate that specializes in growing sugar cane	S
MFGSG	sugar refinery	a facility for converting raw sugar into refined sugar	S
SPNS	sulphur spring(s)	a place where sulphur ground water flows naturally out of the ground	H
SWMP	swamp	a wetland dominated by tree vegetation	H
SYG	synagogue	a place for Jewish worship and religious instruction	S
TMTU	tablemount (or guyot)	a seamount having a comparatively smooth, flat top	U
TMSU	tablemounts (or guyots)	seamounts having a comparatively smooth, flat top	U
TAL	talus slope	a steep concave slope formed by an accumulation of loose rock fragments at the base of a cliff or steep slope	T
OILT	tank farm	a tract of land occupied by large, cylindrical, metal tanks in which oil or liquid petrochemicals are stored	S
ESTT	tea plantation	an estate which specializes in growing tea bushes	S
SCHT	technical school	post-secondary school with a specifically technical or vocational curriculum	S
TMPL	temple(s)	an edifice dedicated to religious worship	S
AIRT	terminal	airport facilities for the handling of freight and passengers	S
TRR	terrace	a long, narrow alluvial platform bounded by steeper slopes above and below, usually overlooking a waterbody	T
TERR	territory	territory	A
ADM3	third-order administrative division	a subdivision of a second-order administrative division	A
CRKT	tidal creek(s)	a meandering channel in a coastal wetland subject to bi-directional tidal currents	H
FLTT	tidal flat(s)	a large flat area of mud or sand attached to the shore and alternately covered and uncovered by the tide	H
MNSN	tin mine(s)	a mine where tin ore is extracted	S
TOLL	toll gate/barrier	highway toll collection station	S
TMB	tomb(s)	a structure for interring bodies	S
TOWR	tower	a high conspicuous structure, typically much higher than its diameter	S
RDCR	traffic circle	a road junction formed around a central circle about which traffic moves in one direction only	S
TRL	trail	a path, track, or route used by pedestrians, animals, or off-road vehicles	R
TRANT	transit terminal	facilities for the handling of vehicular freight and passengers	S
TREE	tree(s)	a conspicuous tree used as a landmark	V
TRIG	triangulation station	a point on the earth whose position has been determined by triangulation	S
TRB	tribal area	a tract of land used by nomadic or other tribes	L
TUND	tundra	a marshy, treeless, high latitude plain, dominated by mosses, lichens, and low shrub vegetation under permafrost conditions	V
TNL	tunnel	a subterranean passageway for transportation	R
TNLS	tunnels	subterranean passageways for transportation	R
CNLSB	underground irrigation canal(s)	a gently inclined underground tunnel bringing water for irrigation from aquifers	H
LKSB	underground lake	a standing body of water in a cave	H
APNU	undersea apron	a gentle slope, with a generally smooth surface, particularly found around groups of islands and seamounts	U
ARCU	undersea arch	a low bulge around the southeastern end of the island of Hawaii	U
ARRU	undersea arrugado	an area of subdued corrugations off Baja California	U
BNKU	undersea bank	an elevation, typically located on a shelf, over which the depth of water is relatively shallow but sufficient for safe surface navigation	U
BKSU	undersea banks	elevations, typically located on a shelf, over which the depth of water is relatively shallow but sufficient for safe surface navigation	U
BSNU	undersea basin	a depression more or less equidimensional in plan and of variable extent	U
BNCU	undersea bench	a small terrace	U
BDLU	undersea borderland	a region adjacent to a continent, normally occupied by or bordering a shelf, that is highly irregular with depths well in excess of those typical of a shelf	U
CNYU	undersea canyon	a relatively narrow, deep depression with steep sides, the bottom of which generally has a continuous slope	U
CNSU	undersea canyons	relatively narrow, deep depressions with steep sides, the bottom of which generally has a continuous slope	U
CDAU	undersea cordillera	an entire mountain system including the subordinate ranges, interior plateaus, and basins	U
ESCU	undersea escarpment (or scarp)	an elongated and comparatively steep slope separating flat or gently sloping areas	U
FANU	undersea fan	a relatively smooth feature normally sloping away from the lower termination of a canyon or canyon system	U
FLTU	undersea flat	a small level or nearly level area	U
FRKU	undersea fork	a branch of a canyon or valley	U
FRSU	undersea forks	a branch of a canyon or valley	U
FRZU	undersea fracture zone	an extensive linear zone of irregular topography of the sea floor, characterized by steep-sided or asymmetrical ridges, troughs, or escarpments	U
FURU	undersea furrow	a closed, linear, narrow, shallow depression	U
GAPU	undersea gap	a narrow break in a ridge or rise	U
GLYU	undersea gully	a small valley-like feature	U
HLLU	undersea hill	an elevation rising generally less than 500 meters	U
HLSU	undersea hills	elevations rising generally less than 500 meters	U
HOLU	undersea hole	a small depression of the sea floor	U
KNLU	undersea knoll	an elevation rising generally more than 500 meters and less than 1,000 meters and of limited extent across the summit	U
KNSU	undersea knolls	elevations rising generally more than 500 meters and less than 1,000 meters and of limited extent across the summits	U
LDGU	undersea ledge	a rocky projection or outcrop, commonly linear and near shore	U
LEVU	undersea levee	an embankment bordering a canyon, valley, or seachannel	U
MDVU	undersea median valley	the axial depression of the mid-oceanic ridge system	U
MESU	undersea mesa	an isolated, extensive, flat-topped elevation on the shelf, with relatively steep sides	U
MOTU	undersea moat	an annular depression that may not be continuous, located at the base of many seamounts, islands, and other isolated elevations	U
MNDU	undersea mound	a low, isolated, rounded hill	U
MTU	undersea mountain	a well-delineated subdivision of a large and complex positive feature	U
MTSU	undersea mountains	well-delineated subdivisions of a large and complex positive feature	U
PKU	undersea peak	a prominent elevation, part of a larger feature, either pointed or of very limited extent across the summit	U
PKSU	undersea peaks	prominent elevations, part of a larger feature, either pointed or of very limited extent across the summit	U
PNLU	undersea pinnacle	a high tower or spire-shaped pillar of rock or coral, alone or cresting a summit	U
PLNU	undersea plain	a flat, gently sloping or nearly level region	U
PLTU	undersea plateau	a comparatively flat-topped feature of considerable extent, dropping off abruptly on one or more sides	U
PLFU	undersea platform	a flat or gently sloping underwater surface extending seaward from the shore	U
PRVU	undersea province	a region identifiable by a group of similar physiographic features whose characteristics are markedly in contrast with surrounding areas	U
RMPU	undersea ramp	a gentle slope connecting areas of different elevations	U
RNGU	undersea range	a series of associated ridges or seamounts	U
RAVU	undersea ravine	a small canyon	U
RFU	undersea reef	a surface-navigation hazard composed of consolidated material	U
RFSU	undersea reefs	surface-navigation hazards composed of consolidated material	U
RDGU	undersea ridge	a long narrow elevation with steep sides	U
RDSU	undersea ridges	long narrow elevations with steep sides	U
RISU	undersea rise	a broad elevation that rises gently, and generally smoothly, from the sea floor	U
SDLU	undersea saddle	a low part, resembling in shape a saddle, in a ridge or between contiguous seamounts	U
SHFU	undersea shelf	a zone adjacent to a continent (or around an island) that extends from the low water line to a depth at which there is usually a marked increase of slope towards oceanic depths	U
EDGU	undersea shelf edge	a line along which there is a marked increase of slope at the outer margin of a continental shelf or island shelf	U
SHVU	undersea shelf valley	a valley on the shelf, generally the shoreward extension of a canyon	U
SHLU	undersea shoal	a surface-navigation hazard composed of unconsolidated material	U
SHSU	undersea shoals	hazards to surface navigation composed of unconsolidated material	U
SILU	undersea sill	the low part of an underwater gap or saddle separating basins, including a similar feature at the mouth of a fjord	U
SLPU	undersea slope	the slope seaward from the shelf edge to the beginning of a continental rise or the point where there is a general reduction in slope	U
SPRU	undersea spur	a subordinate elevation, ridge, or rise projecting outward from a larger feature	U
TERU	undersea terrace	a relatively flat horizontal or gently inclined surface, sometimes long and narrow, which is bounded by a steeper ascending slope on one side and by a steep descending slope on the opposite side	U
TNGU	undersea tongue	an elongate (tongue-like) extension of a flat sea floor into an adjacent higher feature	U
TRNU	undersea trench	a long, narrow, characteristically very deep and asymmetrical depression of the sea floor, with relatively steep sides	U
TRGU	undersea trough	a long depression of the sea floor characteristically flat bottomed and steep sided, and normally shallower than a trench	U
VALU	undersea valley	a relatively shallow, wide depression, the bottom of which usually has a continuous gradient	U
VLSU	undersea valleys	a relatively shallow, wide depression, the bottom of which usually has a continuous gradient	U
USGE	United States Government Establishment	a facility operated by the United States Government in Panama	S
UPLD	upland	an extensive interior region of high land with low to moderate surface relief	T
VAL	valley	an elongated depression usually traversed by a stream	T
VALS	valleys	elongated depressions usually traversed by a stream	T
VETF	veterinary facility	a building or camp at which veterinary services are available	S
VIN	vineyard	a planting of grapevines	V
VINS	vineyards	plantings of grapevines	V
VLC	volcano	a conical elevation composed of volcanic materials with a crater at the top	T
WAD	wadi	a valley or ravine, bounded by relatively steep banks, which in the rainy season becomes a watercourse; found primarily in North Africa and the Middle East	H
WADB	wadi bend	a conspicuously curved or bent segment of a wadi	H
WADJ	wadi junction	a place where two or more wadies join	H
WADM	wadi mouth	the lower terminus of a wadi where it widens into an adjoining floodplain, depression, or waterbody	H
WADS	wadies	valleys or ravines, bounded by relatively steep banks, which in the rainy season become watercourses; found primarily in North Africa and the Middle East	H
WALL	wall	a thick masonry structure, usually enclosing a field or building, or forming the side of a structure	S
MLWTR	water mill	a mill powered by running water	S
PMPW	water pumping station	a facility for pumping water from a major well or through a pipeline	S
RSVT	water tank	a contained pool or tank of water at, below, or above ground level	H
WTRC	watercourse	a natural, well-defined channel produced by flowing water, or an artificial channel designed to carry flowing water	H
FLLS	waterfall(s)	a perpendicular or very steep descent of the water of a stream	H
WTRH	waterhole(s)	a natural hole, hollow, or small depression that contains water, used by man and animals, especially in arid areas	H
WTRW	waterworks	a facility for supplying potable water through a water source and a system of pumps and filtration beds	S
WEIR	weir(s)	a small dam in a stream, designed to raise the water level or to divert stream flow through a desired channel	S
WLL	well	a cylindrical hole, pit, or tunnel drilled or dug down to a depth from which water, oil, or gas can be pumped or brought to the surface	H
WLLS	wells	cylindrical holes, pits, or tunnels drilled or dug down to a depth from which water, oil, or gas can be pumped or brought to the surface	H
WTLD	wetland	an area subject to inundation, usually characterized by bog, marsh, or swamp vegetation	H
STNW	whaling station	a facility for butchering whales and processing train oil	S
WHRF	wharf(-ves)	a structure of open rather than solid construction along a shore or a bank which provides berthing for ships and cargo-handling facilities	S
WHRL	whirlpool	a turbulent, rotating movement of water in a stream	H
RESW	wildlife reserve	a tract of public land reserved for the preservation of wildlife	L
MLWND	windmill	a mill or water pump powered by wind	S
WRCK	wreck	the site of the remains of a wrecked vessel	S
ZN	zone	zone	A
ZOO	zoo	a zoological garden or park where wild animals are kept for exhibition	S

Location Type (category)

This category is equivalent to US NGA’s “Feature Class”

External URL: http://geonames.nga.mil/ggmagaz/

This is a Replicated codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
A	Administrative Region
H	Hydrographic
L	Area
P	Populated Place
R	Streets/Highways/Roads
S	Spot Features
T	Hypsographic
U	Undersea
V	Vegetation

Organisation Identifier

As of 1.04 this list is no longer maintained. http://support.iatistandard.org/entries/28497976-Retire-the-Organisation-Identifier-codelist#view-post-25368673

For general guidance about constructing Organisation Identifiers, please see http://iatistandard.org/organisation-identifiers/

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
AT-1	Federal Ministry of Finance
AT-10	Ministry for Agriculture and Environment
AT-11	Ministry of Defense
AT-12	Ministry of Interior
AT-2	Various ministries
AT-3	Federal Government of Austria
AT-4	Oesterreichische Kontrollbank AG
AT-5	Federal Ministry of Foreign Affairs
AT-6	Provincial governments, local communities
AT-8	Austrian Development Agency
AT-9	Education and Science Ministry
AT-99	Miscellaneous
AU-5	Australian Agency for International Development
AU-72	Export Finance and Insurance Corporation
BE-10	Directorate General for Co-operation and Development
BE-20	Official Federal Service of Foreign Affairs (excl. DGCD)
BE-30	Official Federal Service of Finance
BE-31	Ducroire National Office
BE-39	Other Official Federal Services
BE-70	Flanders Official Regional Ministries
BE-80	Walloon Official Regional Ministries
BE-91	Brussels Official Regional Ministries
BE-94	German speaking Official Regional Ministries
CA-1	Canadian International Development Agency
CA-2	International Development Research Centre
CA-31	Export Development Corporation
CA-4	Department of Finance
CH-1	Federal Administration (various departments)
CH-10	Swiss Agency for the Environment, Forests and Landscape
CH-11	Municipalities
CH-4	Swiss Agency for Development and Co-operation
CH-5	State Secretariat for Economic Affairs
CH-6	Federal Department of Foreign Affairs
CH-7	State Secretariat for Education and Research
CH-8	Federal Office for Migration
CH-9	Federal Department for Defence, Civil Protection and Sports
DE-1	Bundesministerium für Wirtschaftliche Zusammenarbeit und Entwicklung
DE-11	Foreign Office
DE-12	Federal States & Local Governments
DE-14	Federal Institutions
DE-16	Federal Ministries
DE-17	Foundations/Societies/Misc. (non federal)
DE-2	Kreditanstalt für Wiederaufbau
DE-34	Hermes Kreditversicherungs-AG
DE-4	German Investment and Development Company
DE-52	Deutsche Gesellschaft für Technische Zusammenarbeit
DK-1	Ministry of Foreign Affairs
DK-2	Danish International Development Agency (Not in CRS Directives)
DK-4	Not in CRS Directives
DK-72	EKR
ES-1	Instituto de Credito Oficial
ES-10	Ministry of Environment
ES-11	Ministry of Health
ES-12	Ministry of Labour and Social Affairs
ES-13	Ministry of Interior
ES-14	Ministry of Public Administration
ES-15	Compania Espanola de Seguros de Credito a la Exportación
ES-16	Municipalities
ES-17	Miscellaneous
ES-18	Ministry of Science and Technology
ES-19	Ministry of Defense
ES-2	Autonomous Governments
ES-4	Ministry of Agriculture, Fisheries, and Food
ES-5	Ministry of Foreign Affairs
ES-6	Ministry of Economy and Finance
ES-7	Ministry of Education, Culture and Sports
ES-8	Ministry of Public Works
ES-9	Ministry of Industry and Energy
EU-1	Commission of the European Communities
EU-2	European Development Fund
EU-3	European Investment Bank
EU-4	Humanitarian Aid Office of the European Commission
FI-1	Finnish Government
FI-2	FinnFund
FI-3	Ministry of Foreign Affairs
FI-4	FIDE
FI-72	FinnVera
FR-10	Ministry of Economy, Finance and Industry
FR-17	Ministry of Education, Higher education and Research
FR-3	French Development Agency
FR-43	Coface
FR-6	Ministry of Foreign Affairs
GB-1	Department for International Development
GB-2	CDC Capital Partners PLC
GB-5	Export Credit Guarantee Department
GR-1	Ministry of Foreign Affairs
GR-2	Ministry of National Economy
GR-20	Miscellaneous
GR-3	Ministry of the Interior, Public Administration and Decentralisation
GR-4	Ministry of National Defence
GR-5	Ministry of the Environment, Land Planning and Public Works
GR-6	Ministry of National Education and Religions
GR-7	Ministry of Agriculture
GR-8	Ministry of Health - Welfare
GR-9	Ministry of Merchant Marine
IE-1	Department of Foreign Affairs
IE-71	Department of Industry and Commerce
IT-2	Agenzia Erogazioni Per l’Agricoltura
IT-4	Direzione Generale per la Cooperazione allo Sviluppo
IT-5	Not in CRS Directives
IT-7	Central administration
IT-74	Sezione Speciale per l’Assicurazione del Credito all’Esportazione
IT-8	Local administration
IT-9	Artigiancassa
JP-1	Ministry of Agriculture, Forestry and Fisheries
JP-10	Japan Overseas Development Co-operation
JP-11	Japan Bank for International Co-operation
JP-12	Other Ministries
JP-13	Public Corporations
JP-14	Prefectures
JP-15	Ordinance-designed Cities
JP-2	Ministry of Foreign Affairs
JP-7	Overseas Fishery Co-operation Foundation
JP-71	Nippon Export and Investment Insurance
JP-8	Japanese International Co-operation Agency
LU-1	Lux-Development
LU-2	Ministry of Foreign Affairs
LU-22	Ducroire Office
NL-1	Ministry of Foreign Affairs (DGIS)
NL-33	NCM Credit Management Worldwide
NL-4	Netherlands Gov. through Netherlands Investment Bank for Developing Countries
NO-1	Norwegian Agency for Development Co-operation
NO-4	Ministry of Foreign Affairs
NO-7	Statens Nærings og Distriksutviklingsfond
NO-71	Garantiinstituttet for Eksportkreditt
NO-72	Eksport Finans
NO-8	NORFUND
NZ-1	Ministry of Foreign Affairs and Trade
NZ-2	New Zealand International Aid and Development Agency
PT-1	Portuguese Government
PT-2	Institute for Portuguese Development Aid
PT-3	Other
PT-71	Conselho de garantias financeiras
SE-2	Ministry of Foreign Affairs
SE-6	Swedish International Development Authority
SE-71	Swedish Export Credits Guarantee Board
US-1	Agency for International Development
US-10	Peace Corps
US-11	State Department
US-12	Trade and Development Agency
US-13	African Development Foundation
US-15	Centers for Disease Control and Prevention
US-16	National Institutes of Health
US-17	Department of Labor
US-2	Department of Agriculture
US-31	Export Import Bank
US-5	Department of Transportation
US-6	Department of Treasury
US-7	Department of Defense
US-8	Miscellaneous
US-9	Department of Interior
41101	Convention to Combat Desertification
41102	Desert Locust Control Organisation for Eastern Africa
41103	Economic Commission for Africa
41104	Economic Commission for Latin America and the Caribbean
41105	Economic and Social Commission for Western Asia
41106	Economic and Social Commission for Asia and the Pacific
41107	International Atomic Energy Agency (Contributions to Technical Cooperation Fund Only)
41108	International Fund for Agricultural Development
41109	International Research and Training Institute for the Advancement of Women
41110	Joint United Nations Programme on HIV/AIDS
41111	United Nations Capital Development Fund
41112	United Nations Conference on Trade and Development
41114	United Nations Development Programme
41116	United Nations Environment Programme
41118	United Nations Framework Convention on Climate Change
41119	United Nations Population Fund
41120	United Nations Human Settlement Programme
41121	United Nations Office of the United Nations High Commissioner for Refugees
41122	United Nations Children’s Fund
41123	United Nations Industrial Development Organisation
41124	United Nations Development Fund for Women
41125	United Nations Institute for Training and Research
41126	United Nations Mine Action Service
41127	United Nations Office of Co-ordination of Humanitarian Affairs
41128	United Nations Office on Drugs and Crime
41129	United Nations Research Institute for Social Development
41130	United Nations Relief and Works Agency for Palestine Refugees in the Near East
41131	United Nations System Staff College
41132	United Nations System Standing Committee on Nutrition
41133	United Nations Special Initiative on Africa
41134	United Nations University (including Endowment Fund)
41135	United Nations Volunteers
41136	United Nations Voluntary Fund on Disability
41137	United Nations Voluntary Fund for Technical Co-operation in the Field of Human Rights
41138	United Nations Voluntary Fund for Victims of Torture
41140	World Food Programme
41141	United Nations Peacebuilding Fund (Window Two: Restricted Contributions Only)
41142	United Nations Democracy Fund
41143	World Health Organisation - core voluntary contributions account
41301	Food and Agricultural Organisation
41302	International Labour Organisation
41303	International Telecommunications Union
41304	United Nations Educational, Scientific and Cultural Organisation
41305	United Nations
41306	Universal Postal Union
41307	World Health Organisation - assessed contributions
41308	World Intellectual Property Organisation
41309	World Meteorological Organisation
41310	United Nations Department of Peacekeeping Operations (excluding UNTSO, UNMOGIP, UNFICYP, UNDOF)
41311	United Nations Peacebuilding Fund (Window One: Flexible Contributions Only)
41312	International Atomic Energy Agency - assessed contributions
41313	United Nations High Commissioner for Human Rights (extrabudgetary contributions only)
41314	United Nations Economic Commission for Europe (extrabudgetary contributions only)
42001	European Commission - Development Share of Budget
42003	European Commission - European Development Fund
42004	European Investment Bank (interest subsidies only)
42005	Facility for Euro-Mediterranean Investment and Partnership Trust Fund
42006	Global Energy Efficiency and Renewable Energy Fund
43001	International Monetary Fund - Poverty Reduction and Growth Facility Trust
43002	International Monetary Fund - Poverty Reduction and Growth Facility - Heavily Indebted Poor Countries Initiative Trust (includes HIPC, PRGF and PRGF-HIPC sub-accounts)
43003	International Monetary Fund - Subsidization of IMF Emergency Assistance for Natural Disasters
44001	International Bank for Reconstruction and Development
44002	International Development Association
44003	International Development Association - Heavily Indebted Poor Countries Debt Initiative Trust Fund
44004	International Finance Corporation
44005	Multilateral Investment Guarantee Agency
44006	Advance Market Commitments
44007	International Development Association - Multilateral Debt Relief Initiative
45001	World Trade Organisation - International Trade Centre
45002	World Trade Organisation - Advisory Centre on WTO Law
45003	World Trade Organisation - Doha Development Agenda Global Trust Fund
46001	African Solidarity Fund
46002	African Development Bank
46003	African Development Fund
46004	Asian Development Bank
46005	Asian Development Fund
46006	Black Sea Trade and Development Bank
46007	Central American Bank for Economic Integration
46008	Andean Development Corporation
46009	Caribbean Development Bank
46012	Inter-American Development Bank, Inter-American Investment Corporation and Multilateral Investment Fund
46013	Inter-American Development Fund for Special Operations
47001	African Capacity Building Foundation
47002	Asian Productivity Organisation
47003	Association of South East Asian Nations: Economic Co-operation
47004	ASEAN Cultural Fund
47005	African Union (excluding peacekeeping facilities)
47008	World Vegetable Centre
47009	African and Malagasy Council for Higher Education
47010	Commonwealth Agency for Public Administration and Management
47011	Caribbean Community Secretariat
47012	Caribbean Epidemiology Centre
47013	Commonwealth Foundation
47014	Commonwealth Fund for Technical Co-operation
47015	Consultative Group on International Agricultural Research
47016	Commonwealth Institute
47017	International Centre for Tropical Agriculture
47018	Centre for International Forestry Research
47019	International Centre for Advanced Mediterranean Agronomic Studies
47020	International Maize and Wheat Improvement Centre
47021	International Potato Centre
47022	Convention on International Trade in Endangered Species of Wild Flora and Fauna
47023	Commonwealth Legal Advisory Service
47024	Commonwealth Media Development Fund
47025	Commonwealth of Learning
47026	Community of Portuguese Speaking Countries
47027	Colombo Plan
47028	Commonwealth Partnership for Technical Management
47029	Sahel and West Africa Club
47030	Commonwealth Scientific Council
47031	Commonwealth Small States Office
47032	Commonwealth Trade and Investment Access Facility
47033	Commonwealth Youth Programme
47034	Economic Community of West African States
47035	Environmental Development Action in the Third World
47036	European and Mediterranean Plant Protection Organisation
47037	Eastern-Regional Organisation of Public Administration
47038	INTERPOL Fund for Aid and Technical Assistance to Developing Countries
47040	Forum Fisheries Agency
47041	Food and Fertilizer Technology Centre
47042	Foundation for International Training
47043	Global Crop Diversity Trust
47044	Global Environment Facility
47045	Global Fund to Fight AIDS, Tuberculosis and Malaria
47046	International Organisation of the Francophonic
47047	International African Institute
47048	Inter-American Indian Institute
47049	International Bureau of Education - International Educational Reporting System (IERS)
47050	International Cotton Advisory Committee
47051	International Centre for Agricultural Research in Dry Areas
47053	Centre for Health and Population Research
47054	International Centre of Insect Physiology and Ecology
47055	International Centre for Development Oriented Research in Agriculture
47056	World AgroForestry Centre
47057	International Crop Research for Semi-Arid Tropics
47058	International Institute for Democracy and Electoral Assistance
47059	International Development Law Organisation
47060	International Institute for Cotton
47061	Inter-American Institute for Co-operation on Agriculture
47062	International Institute of Tropical Agriculture
47063	International Livestock Research Institute
47064	International Network for Bamboo and Rattan
47065	Intergovernmental Oceanographic Commission
47066	International Organisation for Migration
47067	Intergovernmental Panel on Climate Change
47068	Asia-Pacific Fishery Commission
47069	Biodiversity International
47070	International Rice Research Institute
47071	International Seed Testing Association
47073	International Tropical Timber Organisation
47074	International Vaccine Institute
47075	International Water Management Institute
47076	Justice Studies Centre of the Americas
47077	Mekong River Commission
47078	Multilateral Fund for the Implementation of the Montreal Protocol
47079	Organisation of American States
47080	Organisation for Economic Co-operation and Development (Contributions to special funds for Technical Co-operation Activities Only)
47081	OECD Development Centre
47082	Organisation of Eastern Caribbean States
47083	Pan-American Health Organisation
47084	Pan-American Institute of Geography and History
47085	Pan-American Railway Congress Association
47086	Private Infrastructure Development Group
47087	Pacific Islands Forum Secretariat
47088	Relief Net
47089	Southern African Development Community
47090	Southern African Transport and Communications Commission
47091	(Colombo Plan) Special Commonwealth African Assistance Programme
47092	South East Asian Fisheries Development Centre
47093	South East Asian Ministers of Education
47094	South Pacific Applied Geoscience Commission
47095	South Pacific Board for Educational Assessment
47096	Secretariat of the Pacific Community
47097	Pacific Regional Environment Programme
47098	Unrepresented Nations and Peoples’ Organisation
47099	University of the South Pacific
47100	West African Monetary Union
47101	Africa Rice Centre
47102	World Customs Organisation Fellowship Programme
47103	World Maritime University
47104	WorldFish Centre
47105	Common Fund for Commodities
47106	Geneva Centre for the Democratic Control of Armed Forces
47107	International Finance Facility for Immunisation
47108	Multi-Country Demobilisation and Reintegration Program
47109	Asia-Pacific Economic Cooperation Support Fund (except contributions tied to counter-terrorism activities)
47110	Organisation of the Black Sea Economic Cooperation
47111	Adaptation Fund
47112	Central European Initiative - Special Fund for Climate and Environmental Protection
47113	Economic and Monetary Community of Central Africa
47116	Integrated Framework for Trade-Related Technical Assistance to Least Developed Countries
47117	New Partnership for Africa’s Development
47118	Regional Organisation for the Strengthening of Supreme Audit Institutions of Francophone Sub-Saharan Countries
47119	Sahara and Sahel Observatory
47120	South Asian Association for Regional Cooperation
47121	United Cities and Local Governments of Africa
47122	Global Alliance for Vaccines and Immunization
47123	Geneva International Centre for Humanitarian Demining
47125	European Bank for Reconstruction and Development - Early Transition Countries Initiative
47126	European Bank for Reconstruction and Development - Western Balkans Trust Fund
47127	Latin-American Energy Organisation
21001	Association of Geoscientists for International Development
21002	Agency for International Trade Information and Co-operation
21003	Latin American Council for Social Sciences
21004	Council for the Development of Economic and Social Research in Africa
21005	Consumer Unity and Trust Society International
21006	Development Gateway Foundation
21007	Environmental Liaison Centre International
21008	Eurostep
21009	Forum for Agricultural Research in Africa
21010	Forum for African Women Educationalists
21011	Global Campaign for Education
21013	Health Action International
21014	Human Rights Information and Documentation Systems
21015	International Catholic Rural Association
21016	International Committee of the Red Cross
21017	International Centre for Trade and Sustainable Development
21018	International Federation of Red Cross and Red Crescent Societies
21019	International Federation of Settlements and Neighbourhood Centres
21020	International HIV/AIDS Alliance
21021	International Institute for Environment and Development
21022	International Network for Alternative Financial Institutions
21023	International Planned Parenthood Federation
21024	Inter Press Service, International Association
21025	International Seismological Centre
21026	International Service for Human Rights
21027	International Trust Fund for Demining and Mine Victims Assistance
21028	International University Exchange Fund - IUEF Stip. in Africa and Latin America
21029	Doctors Without Borders
21030	Pan African Institute for Development
21031	PANOS Institute
21032	Population Services International
21033	Transparency International
21034	International Union Against Tuberculosis and Lung Disease
21035	World Organisation Against Torture
21036	World University Service
21037	Women’s World Banking
21038	International Alert
21039	International Institute for Sustainable Development
21040	International Women’s Tribune Centre
21041	Society for International Development
21042	International Peacebuilding Alliance
21043	European Parliamentarians for Africa
21044	International Council for the Control of Iodine Deficiency Disorders
21045	African Medical and Research Foundation
21046	Agency for Cooperation and Research in Development
21047	AgriCord
21048	Association of African Universities
21049	European Centre for Development Policy Management
21050	Geneva Call
21051	Institut Supérieur Panafricaine d’Economie Coopérative
21053	IPAS-Protecting Women’s Health, Advancing Women’s Reproductive Rights
21054	Life and Peace Institute
21055	Regional AIDS Training Network
21056	Renewable Energy and Energy Efficiency Partnership
21057	International Centre for Transitional Justice
30001	Global Alliance for Improved Nutrition
30003	Global e-Schools and Communities Initiative
30004	Global Water Partnership
30005	International AIDS Vaccine Initiative
30006	International Partnership on Microbicides
30007	Global Alliance for ICT and Development
30008	Cities Alliance
30009	Small Arms Survey
30010	International drug purchase facility
30011	International Union for the Conservation of Nature
31001	Global Development Network
31002	Global Knowledge Partnership

Organisation Registration Agency

The values from this codelist are used to identify the particular list that an organisation identifier was drawn from. The codelist provides a register of known identifier lists, including national company registers, NGO directories and international and multilateral organisation lists - along with guidance and online resources to help locate the identifiers assigned to a specific organisation.

As of 17 July 2017 this list is maintained by the org-id.guide project. Data publishers can now search for and locate the relevant list for a particular organisation identifier using the org-id.guide website. The full register of identifier sources is also available to download in XML, JSON and CSV formats.

IATI periodically replicates the codelist of identifier sources from org-id.guide, to assist those accessing IATI documentation. However, it is advised that the most up-to-date source is the org-id.guide project.

If org-id.guide does not contain an entry for the kind of organisation you need to identify, you can make a request a new list is included in the register following the guidance or by getting in touch with org-id.guide at: contact@org-id.guide.

This is a Replicated codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category	URL	Public Database?
AE-ACCI	Ajman Chamber of Commerce and Industry	There are 2 types of search available: Commercial search and Industrial search. You can also use an online enquiry form to find the required information. The contact details of Ajman Chamber and the heads of its sectors are also available.	AE	https://www.ajmanchamber.ae/en/Pages/default.aspx	False
AE-ADCD	Abu Dhabi Commercial Directory	This register includes information on companies’ Unified no., Membership no., name, address, phone number, email, activity etc.	AE	http://www.abudhabichamber.ae/English/E-Services/Pages/EServices-Page.aspx?sm=1&ty=s	False
AE-AFZ	Ajman Free Zone Authority	The authority’s website can be used to find its address, email and call center contacts. No clear search functionality directly on the website.	AE	http://www.afz.gov.ae/	False
AE-DCCI	Dubai Chamber of Commerce and Industry	This register includes information on companies name, address, phone number, website, activity and branches.	AE	http://www.dcciinfo.com/	False
AE-DFSA	Dubai Financial Services Authority	This register includes information on companies’ name, DFSA reference number, address, phone number, legal status, services.	AE	https://www.dfsa.ae/Public-Register/Firm	False
AE-DIFC	Dubai International Financial Centre	This register includes information on companies’ name, registration number, activity, phone number, address, etc.	AE	https://www.difc.ae/public-register	False
AE-DMCC	Dubai Multi Commodities Centre	Dubai Multi Commodities Centre is a Free Zone Authority established by the government of Dubai in 2002. The DMCC authority registers and licenses companies to operate in the DMCC Free Zone. N.B There is a ‘Business Directory’, however, this does not provide registration numbers[1] [1]: https://www.dmcc.ae/business-search	AE	https://www.dmcc.ae/	False
AE-FCCI	Fujairah Chamber of Commerce and Industry	There is no company information available directly from this registry, but Chamber of Commerce and Industry can be contacted via the form on the website, phone or email to request more information.	AE	http://www.fujcci.ae/	False
AE-FFZ	Fujairah Free Zone Company Listing	There is no search available in this registry, but there is a list of companies with corresponding phone and fax numbers.	AE	http://www.fujairahfreetradezone.com/appdir/company-listing.php	False
AE-HFZA	Hamriyah Free Zone Authority	A register that contains company names, addresses, phone numbers, emails, license numbers, activities, etc.	AE	http://www.hfza.ae/en-us/directory.aspx	False
AE-RAKIA	Ras al-Khaimah Investment Authority	The Ras al-Khaimah Investment Authority is the registering body for companies in the (RAK) free trade zone. There is no open registry but you can request more information via the contact form on the website or a phone call.	AE	https://www.rakez.com	False
AE-RK_CR	Ras al-Khaimah Chamber of Commerce and Industry	This entry was imported from the Open Corporates Jurisdiction List.	AE	http://www.rakchamber.ae/	False
AE-SAIF	Sharjah Airport International Free Zone	This register contains information on company name, business type, phone number, email, PO box.	AE	http://www.saif-zone.com/en/InvestorLounge/Pages/Investors.aspx	False
AE-SCCI	Sharjah Chamber of Commerce and Industry	This business directory allows you to search for company names and provides information on their address, email, phone number, activity.	AE	http://www.sharjah.gov.ae/BusinessDirectory	False
AE-UQCCI	Umm al-Quwain Chamber of Commerce and Industry	This register includes information about company name, PO box, address, activity, registration date.	AE	http://www.uaqchamber.ae/	False
AF-CBR	Afghanistan Central Business Registry	The Afghan Central Business Registry is a service which allows a single place to register a business in Afghanistan. All companies, groups and individuals are required to register at the ACBR, where they receive confirmation of their registration, become published in the ACBR Gazette and receive the Tax Identification Number. “The new Central Registry is a one stop shop to register your business. It brings together all of the functions previously done by the commercial courts, the Ministry of Justice and the Ministry of Finance.” [1] “ACBR exists to provide services to businesses in Afghanistan intending to register their names and protect their intellectual property rights.” [2] “All corporations, partnerships, limited liability companies and sole proprietorships doing Trade are required to register with ACBR, which facilitates the registration process, including assistance for completing the application form, paying fees, publishing key business information in the Official Gazette and reporting specification of businesses to the Revenue Department of MoF. Registration is required only one time unless a business makes major changes (i.e., change in ownership, executive management, or location or if the initial capital increases or decreases). Businesses are referred to ACBR from either the Trader License office located in the Ministry of Commerce and Industry, from AISA, or from any other license departments after they acquire a business license.” [3] [1] http://acbr.gov.af/FAQ.html [2] http://acbr.gov.af/index.html [3] http://acbr.gov.af/registration.html	AF	http://acbr.gov.af/	False
AF-MOE	Ministry of Economy NGO Department	NGOs wishing to operate in Afghanistan must register with the NGOs Department of the Ministry of Economy. The register contains government departments, national NGOs and international NGOs.	AF	http://moec.gov.af/en	False
AR-CENOC	The National Centre of Community Organisations (Argentina)	Law Nº 25.855, de Voluntariado Social (Social Volunteering) established in 2004 a role for El Centro Nacional de Organizaciones de la Comunidad to maintain a database of civil society organisations (CSOs). “The CSOs that receive or intend to receive public funds must be included in the database, to carry out projects financed in whole or in part with state resources, whatever the subject matter.” Registration for the database requests detailed information, including capturing a CUIT number for the organisation (where known), address and contact information. However, only a basic list of identifiers and names is currently published.	AR	http://www.cenoc.gob.ar/	True
AR-CUIT	Unique Tax Identification Code (Argentina)	Any citizen or company starting an economic activity in Argentina must register with the AFIP (Federal Administration of Public Revenues) and receive a Unique Tax Identification Code (CUIT). This is an 11 digit number, consisting two digits, hyphen, nine digits, and a one digit checksum.	AR		False
AT-FB	Austria Company Register	Available only in German. Access can be obtained by using services of special companies like http://www.advokat.at/Advokat-Online/Module/Firmenbuch.aspx that are entitled to provide it (for full list see https://www.justiz.gv.at/web2013/html/default/2c9484852308c2a601240b693e1c0860.de.html)	AT	https://www.justiz.gv.at/web2013/html/default/2c9484852308c2a601240b693e1c0860.de.html	True
AT-UID	VAT number (Austria Company Register)	“Since July 11, 2005, the records of all commercial register courts are kept electronically. The general ledger is kept by storing the entries in a central database, the so-called “Firmenbuchdatenbank” in the Federal Computing Center in Vienna.”[1] Clearing houses commissioned by the Federal Ministry of Justice (Die Österreichische Justiz) provide the only access to the database.[2] Interfaces are mostly available only in German, and access/fees vary between the different operators. Consider using the Business Register number with the prefix AT-FB (see list AT-FB) - which is a primary rather than secondary list - instead of the VAT number. [1] https://www.justiz.gv.at/web2013/html/default/2c9484852308c2a601240b693e1c0860.de.html [2] A full list of authorized clearing houses is available at https://www.justiz.gv.at/web2013/home/e-justice/firmenbuch/die_firmenbuchdatenbank~2c9484852308c2a601240b693e1c0860.de.html	AT	https://www.justiz.gv.at/web2013/html/default/2c9484852308c2a601240b693e1c0860.de.html	True
AU-ABN	Australian Business Register	“The Australian Business Number (ABN) enables businesses in Australia to deal with a range of government departments and agencies using a single identification number. The ABN is a public number which does not replace an organisations tax file number.” “ABN registration details become part of the Australian Business Register (ABR)” Each ABN should equate to a single ‘business structure’, although that structure may be used to carry out a range of business activities. A range of kinds of entity are issued ABNs, including individuals, corporations, partnerships, unincorporated associations, trusts and superannuation funds. Entities must be carrying on a business in or connection to Australia to receive an ABN.	AU	http://abr.business.gov.au/	False
AU-ACNC	Australian Charities and Not-for-profits Commission	“In Australia, charities must register with the Australian Charities and Not-for-profits Commission (ACNC) before they can receive charity tax concessions from the Australian Taxation Office (ATO).” Charity Status can be applied to organisations that have an Australian Business Number (ABN) and that take a range of legal forms [1] including Australian Private Company, Australian Public Company, State level registered ‘Other Incorporated Entity’, Discretionary Investment Trust, Fixed Trusts, Co-operatives and Other Unincorporated Identities. [1]: http://www.acnc.gov.au/ACNC/Register_my_charity/Who_can_register/Legal_structure/ACNC/Reg/Legal_structure.aspx	AU	http://www.acnc.gov.au/ACNC/	False
AZ-IVI	State Register of Commercial Entities (Ministry of Taxes of Azerbaijan Republic)	Available only in Azerbaijani	AZ	https://www.e-taxes.gov.az/ebyn/commersialChecker.jsp	True
BD-NAB	Bangladesh NGO Affairs Bureau	All NGOs wishing to carry out programmes in Bangladesh must gain permission from the Bangladesh NGO Affairs Bureau. The Bureau keeps a list of NGOs, monitors funding and ensures the accountability of NGO projects. “Its prime objective is to provide one-stop service to the NGOs operating with foreign assistance and registered under the Foreign Donations (Voluntary Activities) Regulation Ordinance, 1978. In addition, it facilitates the activities of the NGOs in the country, and ensures their accountability to the state and thereby to the people of the country” [1] “Bureau approves the project proposals submitted by NGOs” [2] “NGOs much certify in the project proposal that they receive foreign donation or contribution from legal sources.” [3] “Bureau has the responsibility to make sure that money being channelized by NGOs is from legal sources. Bureau also realizes government revenue-both tax (income tax, VAT etc) and non-tax (registration fee). Bureau always coordinates with NGOs, line ministries, different state agencies and development partners in discharging its duty as the regulatory authority. Here the spirit is to facilitate the NGO activities, not to regulate them” [4] [1][2][3][4] http://www.ngoab.gov.bd/site/page/092eab90-ba5f-4cba-933f-d9f28863d170/NGO-Bureau-at-a-glance	BD	http://www.ngoab.gov.bd	False
BE-BCE_KBO	Crossroads Bank for Enterprises	The Crossroads Bank for Enterprises (BCE, ECB, CBE) is the registration office for companies in Belgium. The ECB compiles a list of business identification numbers, maintains the database and provides the list in an available format. “The following companies must register with the ECB: 1. legal persons under Belgian law 2. institutions, organizations and Belgian law services which perform tasks of general interest or related to public order and that have a distinct financial and accounting autonomy from that of the legal person under Belgian public law governing them; 3. legal persons of foreign or international law which have a seat in Belgium or who are required to register pursuant to an obligation imposed by Belgian law; 4. to any individual as an autonomous entity: a) carries on an economic and professional activity in Belgium, as usual, the main or supplementary basis; b) or must register in fulfillment of an obligation imposed by legislation Belgium other than that covered by this Act; 5. associations without legal personality must be registered pursuant to an obligation imposed by Belgian legislation other than that covered by this Act; 6. the establishment of units of the above mentioned companies.” [3] “The Crossroads Bank for Enterprises (BCE) is a register of the Ministry of Economy which includes all the companies basic identification data and their business units. The ECB’s management department is responsible for recording, backup, manage and make available data from the ECB. The ECB is one of the authority for initiatives, application of the principle of single data collection, to simplify administrative procedures for businesses and improve the efficiency of public services.” [1] “It centralises the basic identification data of enterprises and establishment units and communicate them to the various authorities. The ECB gives each company and business unit a unique identification number that allows the authorities to exchange information about them.” [2] [1][2] http://economie.fgov.be/fr/entreprises/BCE/#.WC9BdqIrL8o [3] http://economie.fgov.be/fr/entreprises/BCE/inscription/#.WC9BAqIrL8o	BE	http://economie.fgov.be/fr/entreprises/BCE	False
BE-GTCF (withdrawn)	Au Greffe du Tribunal de Commerce Francophone de Bruxelles	‘The Registry of the Francophone Brussels Commercial Court’ does not appear to be an organisation registration agency. The one identifier we have found in use for this list appears to be derived instead from the BE-BCE_KBO register.	BE	http://www.juridat.be/tribunal_commerce/bruxelles/index.htm	False
BG-EIK	Commercial Register	This register uses Unified identification Codes (UIC) which certify the legality of one’s business and under which one’s company is signed in the National Statistics Agency.	BG	https://public.brra.bg/CheckUps/Verifications/VerificationPersonOrg.ra	True
BJ-IFU	Unique Tax Identifier	The Benin ‘Unique Fiscal Identifier’ was created by Decree No 2006-201 of 8 May 2006, and is linked to a national directory of persons, institutions and associations. “The IFU’s main objective is: * To uniquely register natural or legal persons throughout the national territory; * To avoid assigning several identifiers (INSAE number, taxpayer number, declaring code, etc.) to the same person; * Consolidate and secure information about any identified person; * To establish a reliable database for information, cross-checking and management purposes; * Improve and modernize the management of public finances with the introduction of a development tax system;”[1] Identifiers are assigned to: ” * Enterprises engaged in commercial or non-commercial activity in the territory of Benin, regardless of their form, legal status or nationality; * Employees in the public or private sector; * Corporate officers; * Embassies, international organizations and non-governmental organizations; * Landowners; * Individuals over eighteen (18) years of age engaged in self-employed or non-commercial activities; * Central government, public institutions and local authorities; * Trade unions and political parties, any natural or legal person governed by private law”[1]. An IFU is 13 characters long. The first digit indicate the type of entity identified: * 1- Individual / male * 2- Individual / female * 3- Legal entity / company * 4- Legal person / state structure * 5- Legal person / international organization and mission diplomatic * 6- Legal person / non-governmental organization The subsequent 4 digits give the year. The next six digits are a unique identifier within that year. The next digit indicates either (1) a parent company; (2-9) subsidiary or agencies; (0) other types of person or taxpayer. The final digit is a checksum. [1]: http://www.impots.finances.gouv.bj/tout-savoir-sur-lifu/ EXAMPLE: 3200901353510,	BJ	http://www.impots.finances.gouv.bj/tout-savoir-sur-lifu/	False
BW-CIPA	Companies and Intellectual Property Authority (Botswana)	The Companies and Intellectual Property Authority (CIPA) is the official register of businesses in Botwana under the Companies Act (CAP 42:01), which provides for the incorporation of companies and the Registration of Business Names Act (CAP 42:05), which provides for registration of business names and post registration notices such as change of ownership and cessation of businesses. Both domestic and foreign companies may be registered with the Registrar of Companies. [1]: http://www.cipa.co.bw/ [2]: http://www.gov.bw/en/Business/Sub-audiences/Small–Medium-Businesses/Company–Business-Name-Registration/	BW	http://www.cipa.co.bw/	True
BY-ADR	Unified State Register of Legal Entities and Individual Entrepreneurs (Ministry of Justice of the Republic of Belarus)	“The Unified State Register of Legal Entities and Individual Entrepreneurs (hereinafter referred to as the USR) has been operating since 2003. In accordance with the Resolution of the Council of Ministers of the Republic of Belarus of February 23, 2009 No. 229 “On the Unified State Register of Legal Entities and Individual Entrepreneurs”, information on legal entities, state bodies and state legal entities, provisions on which are approved by legislative acts, and also about individual entrepreneurs.”[1] “A legal entity is considered established from the moment of its state registration, unless otherwise established by the President of the Republic of Belarus.”[2] [1] http://egr.gov.by/egrn/index.jsp?content=AboutEGR [2] http://egr.gov.by/egrn/index.jsp?content=eJurReorgCreate	BY	http://egr.gov.by/egrn/index.jsp?language=en	True
CA-CC	Corporations Canada	Corporations Canada are the federal company register. CA-CC should be used for the Canada Corporation Number Companies in Canada register with their provincial authority, e.g. British Columbia. While there is currently no complete national database for companies in Canada, Corporations Canada are piloting a Business Search Registry, which allows for the search of multiple jurisdictions at once, but not all - https://www.ic.gc.ca/app/scr/ccbr/search-chercher?lang=eng Corporations Canada also provides a Federal Corporation search - https://www.ic.gc.ca/app/scr/cc/CorporationsCanada/fdrlCrpSrch.html?locale=en_CA This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.ic.gc.ca/eic/site/cd-dgc.nsf/eng/home	False
CA-CRA_ACR	Canadian Revenue Agency	Companies in Canada register with their provincial authority, e.g. British Columbia, and then they register with the Canadian Revenue Agency in order to pay corporate income tax and receive a Business Number. The code CA-CRA_ACR is used for Canadian Business Numbers. Non-profits and other kinds of legal entities may also have a Canadian Business Number. The business number is sometimes reported with a Program Account code (e.g. RP0001 to indicate a payroll program account, leading a number such as 123456789RP0001). In constructing an organisation identifier, only the first nine digits should be used. Companies can be searched by using the Business Number, as assigned by the CRA, on this incomplete registry hosted by the Canadian govt - https://www.ic.gc.ca/app/scr/cc/CorporationsCanada/fdrlCrpSrch.html?locale=en_CA ## More detail: Not all companies need a Canadian Business Number. Detailed information can be found here - http://www.cra-arc.gc.ca/tx/bsnss/tpcs/bn-ne/wrks-eng.html Not all charities need to register with the Canadian Revenue Agency. Detailed information can be found here - http://www.cra-arc.gc.ca/chrts-gvng/chrts/pplyng/rgstrtn/mnd-eng.html Not all non-profit organisations must register to become a charity. Detailed information can be found here - http://www.cra-arc.gc.ca/chrts-gvng/dnrs/rgltn/dffrnc-rc-np-eng.html “Your Business Number is a nine-digit account number that identifies your business to federal, provincial, and municipal governments.”[1] [1] http://www.canadabusiness.ca/programs/business-number-bn-1/	CA	http://www.cra-arc.gc.ca/	False
CA-GOV	List of legal department names (Government of Canada)	“The dataset includes a list of legal department names and their respective numbers. The department number is assigned by the Receiver General to an organization listed in Schedules I, 1.1 and II of the Financial Administration Act authorized to use the Consolidated Revenue Fund and interface with the central systems operated by Public Works and Government Services Canada.”	CA	http://open.canada.ca/data/en/dataset/22090865-f8a6-4b83-9bad-e9d61f26a821	True
CA_AB-ABT	Corporate Registry Office	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.servicealberta.ca/Corporate_Registry.cfm	False
CA_BC-BRC_CBR	British Columbia Corporate Registry	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.bcregistryservices.gov.bc.ca/bcreg/corppg/index.page	False
CA_MB-MTB	Manitoba Companies Office, Department of Entrepreneurship, Training and Trade	This entry was imported from the Open Corporates Jurisdiction List.	CA	https://direct.gov.mb.ca/mbohtml/html/internet/en/mb_online.html	False
CA_NB-NWB_NOB	Corporate Registry	This entry was imported from the Open Corporates Jurisdiction List.	CA	https://www.pxw1.snb.ca/snb7001/e/2000/2500e.asp	False
CA_NL-NFL_TNL	Registry of Companies, Department of Government Services	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.servicenl.gov.nl.ca/registries/companies.html	False
CA_NS-NVS_NVE	Nova Scotia Registry of Joint Stock Companies	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://novascotia.ca/sns/access/business/registry-joint-stock-companies.asp	False
CA_NT-NWT_TNO	Canadian Provincial Corporate Registration - Northwest Territories	This entry was imported from the Open Corporates Jurisdiction List.	CA	https://www.justice.gov.nt.ca/en/divisions/legal-registries-division/corporate-registries/	False
CA_NU-NNV	Nunavut Department of Justice - Corporate Registries	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://nunavutlegalregistries.ca/cr_index_en.shtml	False
CA_ON-ONT	ServiceOntario, Ministry of Government Services	This entry was imported from the Open Corporates Jurisdiction List.	CA	https://www.ontario.ca/page/business-and-economy	False
CA_PE-PEI_IPE	Prince Edward Island Corporate	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.gov.pe.ca/corporations/index.php	False
CA_QC-QBC	Quebec Business Registrar	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.registreentreprises.gouv.qc.ca/	False
CA_SK-SKN	Saskatchewan Corporate Registry	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.isc.ca/CorporateRegistry/	False
CA_YT-YKT	Yukon Corporate Affairs	This entry was imported from the Open Corporates Jurisdiction List.	CA	http://www.community.gov.yk.ca/corp/index.html	False
CH-FDJP	Commercial Registry, Federal Office of Justice (Switzerland)	The Swiss Commercial Register is administered by the cantons under the supervision of the Swiss Confederation. All the commercial register entries made by the cantonal register offices are published in the Swiss Official Gazette of Commerce (SOGC) after having been checked and approved by the Federal Commercial Registry Office. Since January 2011, all companies, foreign branches and associations / foundations registered in the various Swiss Commerce Registries are assigned a unique federal Company Identification Number, locally known as IDE (French), UID (German), IDI (Italian). Previously, identifiers were of the format CH-RRR.X.XXX.XXX-P, where RRR is the canton number, X.XXX.XXX is the company number, and P is a check-digit. Some older or inactive companies may still have identifiers of this form. [1]: https://opencorporates.com/registers/250	CH	https://www.zefix.ch/de/search/entity/welcome	True
CN-SAIC	State Administration for Industry and Commerce (SAIC)	The SAIC is the national body which ensures business rights in China, for both domestic and foreign enterprises. Businesses must register with the SAIC. The Enterprise Registration Bureau is the department responsible for enterprise registration. For further details on the procedure for starting a business entity, see this WikiProcedure - https://www.wikiprocedure.com/index.php/China_-_Start_a_Business_Entity The database is only available in Chinese language “The State Administration for Industry & Commerce (SAIC) of the People’s Republic of China is the competent authority of ministerial level directly under the State Council in charge of market supervision/regulation and related law enforcement through administrative means. With creating a regulated and harmonized market environment of fairness, justice and faithfulness for the coordinated socioeconomic development as its objective, SAIC functions in maintaining market order and protecting the legitimate rights and interests of businesses and consumers by carrying out regulations in the fields of enterprise registration, competition, consumer protection, trademark protection and combating economic illegalities.” [1] “Our responsibilities: 2. Carry out and administer registration of enterprises (including foreign-invested enterprises), agricultural cooperatives, entities or individuals engaged in business operation and resident representative offices of foreign companies; and take charge of the investigation and ban on unlicensed business operation according to law.” [2] “Enterprise Registration Bureau - Draft measures and practice directions regarding enterprise registration; - Coordinate and guide enterprise registration nationwide; - Take charge of registration of certain enterprises and supervises the registrants’ registration practices; - Organize and guide credit rating of businesses; - Establish and maintain the national database of enterprise registration information, and analyze and publish registration information of domestic enterprises.” [3] [1][2] http://www.saic.gov.cn/english/aboutus/Mission/index.html [3] http://www.saic.gov.cn/english/aboutus/Departments/	CN	http://gsxt.saic.gov.cn/	False
CO-CCB	Bogota Chamber of Commerce	Each region of Colombia has a Chamber of Commerce to which all corporate entities must register. Bogota Chamber of Commerce (CCB) is responsible for Bogota. Users should refer to CO-RUE for unique identifiers for Colombia. CO-CCB has ben deprecated in favour of CO-RUE. “We are a private, non-for-profit organization whose goal is to foster a sustainable Bogota-Region in the long term, by promoting its residents’ prosperity, through services which enhance and strengthen the enterprise capabilities present in the region, and which improve the business environment with an impact over public policies.” [1] [1] http://www.ccb.org.co/en/Clusters/20th-TCI-Global-Conference-Bogota-Colombia/Bogota-Chamber-of-Commerce	CO	http://www.ccb.org.co/	False
CO-RUE	Unified Commercial and Social Registry (RUES)	The Unified Commercial and Social Registry (RUES) integrates multiple commercial registries, including the NIT (Número de Identificación Tributaria) which can be used as the unique identifier. This database can be searched online for free. “The CCB hereby informs that, in accordance with Resolution 71029 issued by the Superintendence of Industry and Commerce, starting as of November 13, 2013, entrepreneurs must fill out the new Unified Commercial and Social Registry (RUES), a form that integrates the information from the following forms and records: * Merchant’s Certificate. * Unified Offeror Registry. * Non-For-Profit Organizations Registry. * Common Regime (Associations, Foundations and Corporations) and * Solidary Economy Institutions (Cooperatives, Precooperatives, Employee Funds and Mutual Associations). * Activity, games and gambling Registry. * Citizen Oversight Associations Registry (applicable only when registering or signing-up). * Solidarity Economy Registry.” [1] [1] http://www.ccb.org.co/en/Registrations-and-renewals/Merchant-s-certificate/Unified-Commercial-and-Social-Registry-RUES	CO	http://www.rues.org.co/RUES_Web/	False
CY-DRCOR	Cyprus Department of Registrar of Companies and Official Receiver (DRCOR)	Department of Registrar of Companies and Official Receiver maintains the register of companies, partnerships, business names, and overseas companies.	CY	https://efiling.drcor.mcit.gov.cy/DrcorPublic/Default.aspx?cultureInfo=en-AU	True
CZ-DIC	Tax ID (DIČ) Czech Republic	A VAT registration number (DIČ) is a unique and unambiguous identification of each tax entity, a legal or natural person who is a taxpayer (taxpayer). The tax identification number is assigned only after the entity, natural or legal person, obtains its IČO - its unique identification number. Note that the list [CZ-ICO](/list/CZ-ICO) might therefore provide a better set of identifiers for legal entities. You can search by VAT (DIČ) number for a of the VAT payer registered in the Czech Republic. You can also use your company ID or company name or your business name and surname if you want to verify your VAT payer details.	CZ	http://www.kurzy.cz/dic/	True
CZ-ICO	Access to Registers of Economic Subjects	The ARES is an information system which collates data from several public registers in the Czech Republic. These include: Public registers comprising: the Commercial Register Federal Register, the Register of Foundations Register’s Institute, Register of Public Service Companies, Trade Register, and the Register of Economic Entities. Enterprises do not register with the ARES. They must be register with the relevant registration authority. “The purpose of the ARES web sites of the Ministry of Finance is to provide a single-point access to all data concerning economic entities kept in particular registers or maintained in files of the state administration. ARES provides an easy access to the data transferred from the source registers to the ARES database. It allows also to switch directly to www applications of the state administration bodies provided that such applications already exist.” [1] “It is not possible to make a registration in the Information System ARES directly. It is necessary to proceed in accordance with applicable laws and to make a registration at the registration points of the public administration authorities. Likewise, data changes or termination of the registration must be reported to the institution that maintains the source registry. List of source registers and responsible institutions is presented in the tab REGISTRATION AUTHORITIES.” [2] Information on companies is searchable in English and is free-of-charge. [1] http://wwwinfo.mfcr.cz/ares/ares_es.html.en [2] http://wwwinfo.mfcr.cz/ares/ares.html.en	CZ	http://wwwinfo.mfcr.cz/ares/ares_es.html.en	False
DE-CR	Common Register Portal of the German Federal States (CRP)	Common register portal of the German federal states provides the registers of companies, cooperatives and partnerships and, to some extent, also of associations registered in all federal states in Germany as well as announcements for the register (publications).	DE	https://www.handelsregister.de/rp_web/welcome.do	True
DK-CVR	Danish Central Business Register	The CBR is the national body for registering companies and maintaining this information in Denmark. The Central Business Register at Virk is available with English headings and categories. It can be used to search for information on all Danish businesses. “The Danish Central Business Register (aka CVR — Det Centrale Virksomhedsregister) is the central government register containing primary data on all businesses in Denmark, regardless of economic and organizational structure, except personally owned companies with an annual turnover of less than 50,000 Danish krones.” [1] [1] https://en.wikipedia.org/wiki/Central_Business_Register_(Denmark)	DK	https://datacvr.virk.dk/data/	False
EE-KMKR	e-Business Register (Estonia)	“Central Commercial Register is an online service based on the central database of Estonian registration department of the court. The central database includes digital data from the commercial register, the commercial pledge register, the register of state agencies and local government institutions, the register of non-profit associations and foundations. “[1] Records contain information about the legal entity including e.g. annual reports, address, registration status, tax debt information and legal form. It also includes a Registry Code (“Registrikood”). [1] http://www.rik.ee/en/e-business-register	EE	http://www.rik.ee/en/e-business-register	True
EE-RIK	Centre of Registers and Information Systems (RIK)	The Centre of Registers and Information Systems (RIK) provides a number of services for Estonian individuals and business, in particular electronic services. These include the maintenance of the land registry database, criminal records database, company registry database and more. They also have a portal for the online registration of companies. “COMPANY REGISTRATION PORTAL This environment allows companies to submit electronic documents to the Business Register without using the services of a notary. The portal allows submitting applications for registering a new company, for amending the registry data, for liquidating and for deleting a company from the registry. You can view the data related to you free-of-charge by logging in with your ID-card.” [1] [1] http://www.rik.ee/en	EE	http://www.rik.ee/en/e-business-register	False
EG-MOSS	Ministry of Social Solidarity and Justice (Egypt)	The Ministry of Social Solidarity and Justice is the main registration body for associations and foundations in Egypt.	EG	http://www.moss.gov.eg/	False
ES-DIR3	Common Directory of Organizational Units and Offices - DIR3	The Common Directory of Organizational Units and Offices (DIR3) is a project to improve interoperability between public administration units in Spain. As a part of this, a list of all the public bodies is maintained by the Centro de Transferencia de Tecnología (Technology Transfer Centre). “The Common Directory is conceived as a Inventory information on the organizational structure of the public administration, and its citizens care offices. That is, a catalogue of functional units, public agencies and registry offices and attention to the citizen of the administration” [1] [1] http://administracionelectronica.gob.es/pae_Home/pae_Estrategias/Racionaliza_y_Comparte/sistemas_informacion_transversales/DIR3.html?idioma=en#.WDTAPaIrL8o EXCEL Tables: http://administracionelectronica.gob.es/ctt/resources/Soluciones/238/Area%20descargas/Listado%20Oficinas%20AGE.xlsx?idIniciativa=238&idElemento=2745	ES	http://administracionelectronica.gob.es/ctt/dir3/descargas	False
ES-RMC	Central Commercial Register of the Kingdom of Spain	The Central Mercantile Register (1) provides the access to the companies information supplied by the Regional Mercantile Registers after the 1 January 1990, once the data has been organized and processed in accordance with Section 379 of the Mercantile Register Regulations currently in effect. (1) Central Commercial Register - Central Corporate Register - Central Business Register	ES	http://www.rmc.es/Home.aspx	True
ET-CSA	Charities and Societies Agency (Ethiopia)	Most Charities and Societies which operate in Ethiopia are required to register with the Charities and Societies Agency, an institution of the Federal Government, which issues certificates of legal personality to those registered.	ET	http://www.chsa.gov.et/	False
ET-MFA	Ministry of Foreign Affairs	All charities wishing to operate in Ethiopia must register with the Ministry of Foreign Affairs (MFA). Details for how they register can be found in this document - http://mfa.gov.et/documents/10184/70245/NGO_Rule_English%5B1%5D%281%29.pdf/d20c730a-591e-4d3a-b9d8-a25aeb664904 Charities are registered but no openly searchable database yet available.	ET	http://www.mfa.gov.et/	False
ET-MOT	Ministry of Trade (Ethiopia)	The Ministry of Trade is the official ministry for business registration in Ethiopia. “The Ministry of Trade was re-established in August1995 under – proclamation No 4/1995 issued to provide for the definition of powers and duties of the executive organs of the Federal Democratic Republic ofEthiopia (FDRE). The Ministry was again reorganized with a proclamation No 619/2003 issued to amend the reorganization of the executive organs of the Federal Democratic Republic Ethiopia Proclamation No 256/2001. With this proclamation and by other laws, the Ministry has been given the power to supervise and coordinate five government institutions that are involved in the promotion & development of trade, industry and investment activities. The Ministry of Trade shall have the powers and duties to: Encourage and register the establishment of chambers of commerce and sectorial associations including consumers associations and strengthen those already established(Chambers of Commerce and Sectorial Association Establishment Proclamation No.341/2003).” [1] [1]: http://www.mot.gov.et/documents/27281/0/Proc+No.+341-2003+Chamber+of+commerce+and+sectorial+Associa.pdf/50798768-2b9d-4f20-990f-1d4298f16f08?version=1.1	ET	http://www.mot.gov.et	False
FI-PRO	Finnish Patent and Registration Office	All business operating in Finland must be registered with the Finnish Trade Register. The Finnish Trade Register is maintained by the Finnish Patent and Registration Office (PRO), whom are also responsible for maintaining the Business Information System, which can be used to search for all companies in Finland, and the API which allows users to download company information in bulk. “The Finnish Trade Register (Finnish: Kaupparekisteri, Swedish: Handelsregistret) is a company register in Finland. It provides official information on businesses in the whole country, including data from current and old register entries, articles of association, partnership agreements or rules.” [1] “The Finnish Trade Register is a public register that contains information about businesses and companies. As a rule, all businesses have to be registered at the Trade Register. Businesses also have to notify the register of any changes in their registered details. Most businesses must also submit their financial statements (annual accounts) to the register. ” [2] “The Business Information System BIS (“YTJ” in Finnish) is a service jointly maintained by the Finnish Patent and Registration Office (PRH) and the Finnish Tax Administration, enabling you to file information to both authorities using one single notification. You can use the BIS to: start a business or an organization report changes close down a business or an organization search for basic details of companies and organizations using the company search” [3] [1] https://en.wikipedia.org/wiki/Finnish_Trade_Register [2] https://www.prh.fi/en/kaupparekisteri/rekisterointipalvelut.html [3] https://www.ytj.fi/en/index/whatisbis.html	FI	http://www.prh.fi/en/index.html	False
FR-INSEE (withdrawn)	The National Institute of Statistics and Economic Studies	The National Institute of Statistics and Economic Studies provide a registration service for companies and associations with details being held on the SIRENE database. Information from INSEE is also contained in the RCS dataset, and so this organisation list is deprecated in favour of FR-RCS.	FR	http://www.insee.fr/fr/service/default.asp?page=entreprises/entreprise.htm	False
FR-RCS	Trade and Companies Register	In France, companies register through a number of institutions, predominantly the local centres de formalités des entreprises, but all companies must eventually be registered with the Trade and Companies Register. Once registered, companies receive a SIREN or SIRET number, which is a unique business identifier. This information is maintained by Infogreffe. Infogreffe provide a basic overview of company information for free, and bulk download of data for a fee. A note on identifiers: - A SIRET number is constituted by the SIREN number, plus the NIC code. - The SIREN number relates to a business, whereas a SIRET number relates to a specific geographically located establishment which will be owned by a business. - “A SIREN number is your unique French business identification number. This 9 digit number will be requested by all French administration when dealing with you.. It is a proof that you are a fully registered French business” [1] “The SIRET code/number is an INSEE code which allows the geographic identification of any French establishment or business. The 14-digit number consists of three parts: - first, the SIREN code of the business (or legal unit or person) that owns the unit represented by the SIRET code, - second, the NIC (French: Numéro interne de classement), is a sequential four-digit number unique to the establishment, - and finally, a check digit that verifies the entire SIRET number. For example, 732 829 320 00074 would refer to the seventh establishment of the business with SIREN number 732 829 320.” [2] “Registration is administered by local centres de formalités des entreprises ( CFE), which checks your application and submits details to the relevant agencies (for a small fee). The CFE will provide you with a form M0, which is for the creation of a company.” [3] “Creating a company requires that it is registered with the Trade and Companies Register (RCS).” [4] “WHAT SOURCE IS USED FOR INFORMATION AVAILABLE ON THE INFOGREFFE WEBSITE? Information concerning companies entered on the Trade and Companies Register with Registries of the Commercial Courts is taken directly from public registers held by said registries. Information concerning companies entered on the Trade and Companies Register with other jurisdictions (district courts with commercial jurisdiction, mixed commercial courts in the overseas departments and territories) is provided by the National Industrial Property Institute (INPI). Information concerning companies not entered on the Trade and Companies Register is taken from data on the SIRENE listing held by INSEE.” [5] “WHAT DOCUMENTS ARE AVAILABLE ON THE INFOGREFFE WEBSITE? Infogreffe makes the following information available to the general public: Free information • Company search and information form • Key figures concerning a company • Implementing tracking (free alert, paid consultation). • Lists of articles of association and company deeds available. • Your formalities with online help to be incorporated on the Trade and Companies Register. Paid information View, download, order” [6] [1] http://www.startbusinessinfrance.com/blog/post/tip-what-is-a-siren-or-siret-number [2] https://en.wikipedia.org/wiki/SIRET_code [3] https://www.justlanded.com/english/France/France-Guide/Business/Paperwork [4][5] https://www.infogreffe.com/societes/formalites-entreprise/immatriculation-entreprise.html [6] https://www.infogreffe.com/societes/informations-et-dossiers-entreprises/aide-faq.html#1	FR	http://www.infogreffe.fr	False
GB-CHC	Charity Commission	There are four main types of charity structure in the UK: (1) Charitable incorporated organisation (CIO) (2) charitable company (limited by guarantee) (3) unincorporated association (4) trust	GB	http://www.charity-commission.gov.uk/	True
GB-COH	Companies House	Companies House is the United Kingdom’s register of companies. It contains entries for many kinds of companies, including: * Public limited company (PLC) * Private company limited by shares (Ltd, Limited) * Private company limited by guarantee, typically a non-commercial membership body such as a charity * Private unlimited company (either with or without a share capital) * Limited liability partnership (LLP) * Limited partnership (LP) * Societas Europaea (SE): European Union-wide company structure * Companies incorporated by Royal Charter (RC) * Community interest company	GB	http://www.companieshouse.gov.uk/	True
GB-EDU	Register of Schools (England and Wales)	Schools and Colleges in England must be registered with the Department of Education, and in Wales with the Welsh Government.[1] The Register of Schools is maintained by the Department of Education and provides a URN for each school, university and other educational establishment in England and Wales. The full Register of Schools in England is available (Alpha version) on https://registers.cloudapps.digital/registers?phase=in+progress. The register for Welsh Schools is not yet launched and so all schools in Wales may not yet be present on this list. [1] This includes independent schools which meet the criteria on https://www.gov.uk/independent-school-registration	GB	https://get-information-schools.service.gov.uk	True
GB-GOR	Government Organisation Register	The UK Government Organisation Register contains an identifier for every government body with a presence on the gov.uk single domain. This covers government departments, agencies and Arms Length Bodies (ALBs). Each organisation is assigned an alphanumeric identifier, and the register also includes website addresses, that can be mapped to entries in the GB-GOVUK identifier list. Due to the stable identifiers given in the Government Organisation Register, it should be preferred over codes from the GB-GOVUK list.	GB	https://government-organisation.register.gov.uk/records	True
GB-GOV	UK Government Departments Reference Numbers (IATI Standard)	IATI Version 2.x codes for use by IATI for UK Government Departments. Users looking for non-IATI codes for government organsiations should use the UK Government Organsiation Register GB-GOR	GB	http://data.gov.uk/dataset/iati-organisation-identifier-for-uk-government-bodies	False
GB-GOVUK (withdrawn)	GOV.UK - UK Government Departments, Agencies & Public Bodies	This list is deprecated in favour of GB-GOR, the Government Organisation Registry which assigns a unique code to each agency with a page at www.gov.uk. To construct a legacy GB-GOVUK identifier, use the final segment of the url of a body at http://www.gov.uk (below /organisations) as the “registration number”, converting all “-” to “_”. Keep “registration number” portion all lowercase. It should be possible to map form GB-GOVUK to GB-GOR identifiers.	GB	https://www.gov.uk/government/organisations	False
GB-IRN	Schools Plus, Department of Education (Northern Ireland)	Schools Plus is a directory of institutions, including schools, youth clubs, containing contact information and relevant statistics. Only Open schools seem to be on the list currently.	GB	https://www.education-ni.gov.uk/services/schools-plus	True
GB-LAE	Local Authorities for England Register	The Local Authorities for England Register has been developed with the UK Department for Communities and Local Government (DCLG), and contains identifiers for 350+ local authorities. It also includes the ‘local authority type’ (e.g. Unitary Authority, London Borough) for each. It uses the second portion of [ISO_3166-2](https://en.wikipedia.org/wiki/ISO_3166-2:GB) codes where these are available, and creates new codes where they are not. For more information on GOV.UK Registers, visit https://registers.cloudapps.digital/	GB	https://local-authority-eng.register.gov.uk/records?page-index=1&page-size=5000	True
GB-LAS	Scottish Local Authority Register	The Local Authority SCT Register has been developed with the Scottish Government and Government Digital Service (GDS), and contains identifiers for 32 local authorities. It uses the second portion of [ISO_3166-2](https://en.wikipedia.org/wiki/ISO_3166-2:GB) codes and includes all codes listed for Scotland (SCT).	GB	https://local-authority-sct.register.gov.uk/	True
GB-MPR	Mutuals Public Register	The Mutuals Public Register is the public record of registered mutual societies: * building societies * credit unions * friendly societies * registered societies It contains: * details of societies’ registered offices and contact information the services they offer * public documents such as yearly returns and accounts	GB	https://mutuals.fsa.gov.uk/	False
GB-NHS	NHS Digital - Organisation Data Service	“The Organisation Data Service (ODS) is responsible for publishing organisation and practitioner codes, along with related national policies and standards. We’re also responsible for the ongoing maintenance of the organisation and person nodes of the Spine Directory Service, the central data repository used within various NHS systems and services. Find out more about Organisation Reference data by reading the fundamental standard.”[1][2] Codes are allocated for:[3] * Independent Sector Healthcare Providers (ISHP) * NHS organisations * Non-NHS organisations * optical organisations * private dental practices * system suppliers [1]: https://digital.nhs.uk/organisation-data-service [2]: Information standard SCCI0090 (Health and Social Care Organisation Reference Data): http://content.digital.nhs.uk/isce/publication/scci0090 [3]: List from https://digital.nhs.uk/organisation-data-service/our-services#code allocation	GB	https://digital.nhs.uk/organisation-data-service	True
GB-NIC	The Charity Commission for Northern Ireland	The Register of Charities is an accurate and up-to-date list of all organisations in Northern Ireland considered by law to be charitable. Currently, registration is a managed process and only organisations called forward by the Commission are considered eligible to register. For more information on the Register please visit http://www.charitycommissionni.org.uk/manage-your-charity/register-your-charity/charity-registration-faqs/.	GB	http://www.charitycommissionni.org.uk/charity-search/	True
GB-PLA	Principal Local Authority Register for Wales	The Principal Local Authority Register has been developed with the Welsh Government and Government Digital Service (GDS), and contains identifiers for 22 county and county borough councils. The register may not cover all local authorities as it focuses on bodies providing mainstream local government services. It uses the second portion of [ISO_3166-2](https://en.wikipedia.org/wiki/ISO_3166-2:GB) codes and includes all codes listed for Wales (WLS).	GB	https://principal-local-authority.register.gov.uk/records	True
GB-REV	HM Revenue and Customs	Some UK charitable organisations are exempt or excepted from registering with the Charity Commission. This may be due to the nature of the organisation, it’s historical status, or income threshold. However, these organisations can register for tax purposes with HM Revenue and Customs, and receive a registration number. This may be reported prefixed with XC (for eXempt Charity).	GB	http://www.hmrc.gov.uk/	False
GB-SC	Scottish Charity Register	The Office of the Scottish Charity Register (OSCR) regulates charities in Scotland and maintains a public registry of these charities. “The OSCR perform a range of functions which includes:[5] Determining whether bodies are charities. Keeping a public Register of charities. Facilitating compliance by charities with the legislation. Investigating any apparent misconduct in the administration of charities. Giving information or advice to Scottish Ministers.” [1] [1] https://en.wikipedia.org/wiki/Office_of_the_Scottish_Charity_Regulator	GB	http://www.oscr.org.uk/	False
GB-SHPE	Registered Social Housing Providers (England)	A statutory register of not-for-profit (housing associations), for-profit private, and local authority social housing providers, who are registered to operate in England. The Homes and Communities Agency (HCA)[1] is the regulator for social housing providers in England and maintains the list. Fields indicate the designation of the social housing provider (e.g. private, non-profit, local authority) and the legal entity type (by their inclusion on the FCA Mutual Register, the Charity Register and Companies House). A monthly published list also appears on the HCA website, which includes new registrations and deregistrations https://www.gov.uk/government/publications/current-registered-providers-of-social-housing [1]: https://www.gov.uk/government/organisations/homes-and-communities-agency	GB	https://social-housing-provider-eng.alpha.openregister.org/	True
GB-UKPRN	UK Register of Learning Providers	A UKPRN is a unique number allocated to a provider on successful registration on the UK Register of Learning Providers.	GB	https://www.ukrlp.co.uk/	False
GE-NAPR	Register of Entrepreneurial and Non-Entrepreneurial Legal Entities, Georgia	The National Agency of Public Registry (NAPR) of Georgia registers all legal entities in Georgia. This includes government and non-government bodies (including the private sector). The Identification Code assigned by NAPR is the same as the VAT number in Georgia. NAPR assigns codes for government bodies in addition to all non-governmental organisations (private and non-profit).	GE	https://enreg.reestri.gov.ge/main.php?m=new_index	False
GG-RCE	Guernsey Registry	All companies in Guernsey must register with the Guernsey Registry. This also applies to most charities and NPOs. The Guernsey Registry maintain a registry of all companies, charities and all NPOs in Guernsey. These are recorded in a publicly searchable webpage database for companies and also two separate lists for charities and NPOs. Please Note: According to OpenCorporates, the identifiers are not unique across the Guernsey Registry, as there a five separate registries that can be assigned to organisation information and up to five companies my have the same identifier. OC have thus added their own identifier number based on each registry type. Further details available here - qa_public/register_problems/guernsey “All Guernsey companies must file an Annual Validation submission with the Registry during January 2017 (unless incorporated in December 2016). Submissions received after 31 January 2017 will be subject to a £100 late filing fee.” [1] “The Charities and Non Profit Organisation (Registration) (Guernsey) Law, 2008 requires all Non Profit organisations based in the Islands of Guernsey, Alderney, Herm and Jethou to register with the Office of the Registrar. A failure to do so is an offence. However there is an exemption from this requirement. This applies to Non Profit organisations based in the Islands of Guernsey, Alderney, Herm and Jethou with gross assets and funds of less than £10,000, or gross annual income of less than £5,000.” [2] [1] http://www.guernseyregistry.com/ [2] http://www.guernseyregistry.com/article/112911/Do-I-need-to-register-a-Charity-or-Non-Profit-organisation-	GG	http://www.guernseyregistry.com/	False
GH-DSW	Department of Social Developments	All NGOs wishing to operate in Ghana must first register with the General Registrar’s Office, and then apply for NGO status from the Department of Social Welfare (DSW). NGOs are then issued with a certificate that contains their registration number. There is no database available for search. “The Social Welfare Department is the regulator of NGOs in Ghana and is therefore mandated to issue certificates of recognition to organizations to operate as NGOs. ” [1] [1] http://g-lishfoundation.org/wp-content/uploads/2011/02/HOW-TO-START-AN-NGO-IN-GHANA.pdf	GH	http://mogcsp.gov.gh/department-of-social-developments/	False
HK-CR	Hong Kong Companies Register	All businesses operating in Hong Kong, including non-Hong Kong businesses with a place of business in Hong Kong must register with the Companies Register. This includes Sole-proprietorship, Partnership and Unincorporated body of persons, Non-Hong Kong company, and Branch business, as well as companies incorporated under the Companies Ordinance. Businesses are issued with a registration certificate that is valid for three years, and which can be renewed.	HK	https://www.icris.cr.gov.hk/csci/	True
HR-MBS	Croatian Court Business Register	The court business register is maintained by the Croatian Ministry of Justice (Ministarstvo Pravosuda Republike Hrvatske). Registered corporations each have a court-assigned company registration number (matični broj poslovnog subjekta - MBS)	HR	https://sudreg.pravosudje.hr/registar	True
HR-OIB	Croatia Court Register	Maintained by the Ministry of Justice of the Republic of Croatia.	HR	https://sudreg.pravosudje.hr/registar/f?p=150:1	True
HU-AFA	Information and Electronic Company Registration Service	The Ministry of Justice Information and Electronic Company Registration Service website provides free accesss to individual company data online from 1 January 2008. Only available in Hungarian.	HU	http://www.e-cegjegyzek.hu/?cegkereses	True
ID-KDN (withdrawn)	Ministry of Home Affairs	The Ministry of Home Affairs conducts a series of tasks in relation to legal practice and administration within Indonesia. However, no link has been found between the Ministry of Home Affairs and NGO/company registration. As a result, this code has been deprecated. Users can refer to ID-KLN (Ministry of Foreign Affairs) and ID-PRO for the registration of NGOs. Users can refer to ID-SMR (SMERU) for an independent body that maintains a database of NGOs. “The Ministry of Home Affairs has the task of conducting government affairs in the country to assist the President in running the state government. The Ministry of Interior has the functions: 1. formulation, determination and implementation of policies in the field of politics and public governance, decentralization, development of the regional administration, coaching village government, formation of government affairs and regional development, development of local finance, as well as the population and civil registration, in accordance with the provisions of the legislation; 2. coordinating the implementation of tasks, coaching, and providing administrative support to all elements of the organization within the Ministry of the Interior; 3. management of property / wealth of the country is the responsibility of the Ministry of the Interior; 4. supervise the execution of duties in the Ministry of the Interior; 5. implementation of the technical guidance and supervision over the implementation of the affairs of the Interior Ministry in the area; 6. coordinating, coaching and general supervision, facilitation, and evaluation of the regional administration in accordance with the provisions of the legislation; 7. implementation of research and development in the field of governance in the country; 8. implementation of human resource development in the field of governance in the country; 9. implementation of the technical activities of the center to the regions; and 10. the implementation of a substantial support to all elements of the organization within the Ministry of Interior.” [1] [1] http://www.kemendagri.go.id/profil/tugas-dan-fungsi NGO registration can also be done through Ministry Home affairs/ Kementerian Dalam Negeri	ID	http://www.kemendagri.go.id/	False
ID-KHH	Ministry of Justice & Human Rights	Company registration is done through Ministry of Justice & Human Rights.	ID	http://www.kemenkumham.go.id/	False
ID-KLN	Ministry of Foreign affairs	All NGOs foreign to Indonesia who wish to operate in the country must register through the Ministry of Foreign affairs/ Kementerian Luar Negeri. “Registration Process: 1. INGO submit complete application documents to the Government of the Republic of Indonesia through the Ministry of Foreign Affairs” [1] [1] http://www.kemlu.go.id/en/berita/informasi-penting/Pages/Registration-Guidelines-for-International-Non-Governmental-Organizations-in-Indonesia.aspx	ID	http://www.kemlu.go.id/	False
ID-PRO (withdrawn)	Indonesia - NGOs registered at Provinicial Level	Registration for NGO in Indonesia can be done at the provincial level. Because there is regional autonomy, each provincial has different requirements. This list was in the original IATI list, but current research has not been able to identify any publicly accessible registries nor lists of unique identifiers. A search of the IATI database finds no instances of use of ID-PRO as part of an identifier. For these reasons the list has been deprecated.	ID	http://www.satulayanan.net/layanan/pendaftaran-lsm-atau-ormas/perizinan-lsm-atau-ormas-baru	False
ID-SMR	The SMERU Research Institute	The SMERU Research Institute is an independent body which conducts research on social issues in Indonesia. They also maintains a database of NGOs working in Indonesia. “The SMERU Research Institute is an independent institution for research and public policy studies. We professionally and proactively provide accurate and timely information, as well as objective analyses, on various socioeconomic and poverty issues considered most urgent and relevant for the people of Indonesia.” [1] “SMERU manages Indonesia’s most comprehensive online database of national and regional non-governmental organizations (NGOs). Currently, there are almost 3,000 NGOs in the database, which provides information on the NGOs’ name, address, contact person, vision, mission, legal form, activities, and sector.” [2] [1] http://www.smeru.or.id/en/about [2] http://www.smeru.or.id/en/content/ngo-database	ID	http://www.smeru.or.id/en	False
IE-CHY	Charities Regulatory Authority of Ireland	All charities operating in Ireland must register with the Charities Regulatory Authority. The Charities Regulator maintains a publicly searchable database of these organisations, in webpage and Excel form. “Our work as a Regulator is to increase public trust and confidence in the management and administration of charitable organisations and to ensure the accountability of charitable organisations to donors, beneficiaries and the public. All charitable organisations carrying out activities in the state are required to be registered with the Charities Regulator. All registered charities are required to report on their activities and finances to the Regulator on an annual basis. ” [1] [1] https://www.charitiesregulatoryauthority.ie/en/CRA/Pages/WP16000071	IE	https://www.charitiesregulatoryauthority.ie/	False
IE-CRO	Irish CompaniesRegistration Office	The Companies Registration Office of Ireland is responsible for the incorporation of business operating in Ireland and maintaining an online database of the information. Data is provided for free and also for a fee, depending on the amount/type requested. “The CRO has a number of core functions: * The incorporation of companies and the registration of business names. * The receipt and registration of post incorporation documents. * The enforcement of the Companies Act 2014 in relation to the filing obligations of companies. * Making information available to the public.” [1] [1] https://www.cro.ie/About-CRO/Functions-of-the-CRO	IE	http://www.cro.ie/	False
IL-ROC	Registrar of Companies (Israel)	The Register of Companies is maintained by the Israeli Corporations Authority and can be searched using part or all of a company name in English or Hebrew, or by entering the company number. The search interface and the results are in Hebrew. Free information on a company includes type of company, address, legal status and purpose of the company. Additional information such as details of directors, total authorized capital, division of share capital, shareholders, charges and liabilities is priced.	IL	http://www.justice.gov.il/Units/RasutHataagidim/units/RashamHachvarot/Pages/default.aspx	True
IM-CR	Isle of Man Companies Registry	The Isle of Man Companies Registry provides registration for domestic and foreign companies registered or operating on the Isle of Man.	IM	https://www.gov.im/categories/business-and-industries/companies-registry	False
IM-GR	Isle of Man Index of Registered Charities	All charities in the Isle of Man must be registered with the General Registry. The General Registry maintain information about charities in the Index of Registered Isle of Man Charities “The General Registry has specific statutory roles in relation to the registration of charities and the receipt of statutory statements, accounts and other documents in relation to charities.” [1] “The General Registry is the department which administers – the civil and criminal Courts of the Isle of Man the High Court of Justice of the Isle of Man Courts of General Gaol Delivery courts of summary jurisdiction the Registries Deeds and Probate Registry Land Registry Civil Registry, responsible for registration of births, deaths and marriages registration of charities Legal Aid the Public Record Office criminal injuries compensation registration of legal practitioners (other than advocates)” [2] [1] https://www.gov.im/registries/courts/charities/ [2] https://en.wikipedia.org/wiki/General_Registry_(Isle_of_Man)	IM	http://www.gov.im/registries/courts/charities/	True
IN-MCA	Government of India, Ministry of Corporate Affairs	Companies in India register with the Registrar of Companies in their state. While each Registrar of Companies maintains their own database, the Ministry of Corporate Affairs regulates the corporate sector and maintains a database of national company information. This information is accessible in data.gov.in “The Registrar of Companies (ROC) is an office under the Indian Ministry of Corporate Affairs that deals with administration of the Companies Act 1956 and Companies Act, 2013. There are currently 22 Registrars of Companies (ROC) operating from offices in all major states of India. Some states, such as Maharashtra and Tamil Nadu, have two ROCs each. Section 609 of the Companies Act, 1956 tasks the ROCs with the primary duty of registering companies and LLPs floated in the respective states and the union territories under their administration. The Registrar of Company takes care of company registration (also known as incorporation) in India, completes reporting and regulation of companies and their directors and shareholders, and also oversees government reporting of various matters including the annual filling of various documents.” [1] [1] https://en.wikipedia.org/wiki/Registrar_of_Companies,_India	IN	http://www.mca.gov.in/	False
IN-MHA	Ministry of Home Affairs (India) Foreign Contributions (Regulation) Act Register	The Foreign Contributions (Regulation) Act required NGOs in receipt of foreign funding in India to register with the government. They are assigned an FRCA Registration Number.	IN	https://fcraonline.nic.in/	False
IT-CF	Italian Tax Code / VAT Number	Companies (and some other entities) in Italy must register with the Business Register of the Chambers of Commerce. They are assigned a Codice Fiscale (CF) or Tax Code which also acts as their Partitia IVA (P.IVA) or VAT Number. Entities may also be assigned an Economic and Administrative Directory (REA) identifier.	IT	http://www.registroimprese.it/	True
IT-RI (withdrawn)	Business Register of the Italian Chambers of Commerce	Companies (and some other entities) in Italy must register with the Business Register of the Chambers of Commerce. They are assigned a Codice Fiscale (CF) or Tax Code. Entities may also be assigned an Economic and Administrative Directory (REA) identifier.	IT	http://www.registroimprese.it/	True
JE-FSC	Jersey Financial Services Commission (JFSC)	Companies and Non Profit Organisations operating in Jersey register with the Financial Services Commission (JFSC). A search of company information is freely available on the Commission website. There was no search available for NPOs at the time of last checks. Users should be aware that the identifier numbers are not unique, as there are multiple types of companies and identifiers can be repeated. For example, there are two companies with the number ‘1381’ - an LP (limited partnership) and an RC (Registered Private Company) It is recommended that those creating identifiers for JSFC use the business codes as part of the identifier. For example, the limited partnership company described above should have the identifier: JE-FSC-LP_1381 “The Non-Profit Organizations (Jersey) Law 2008 (the “NPO Law”) was registered by the Royal Court on 25 July 2008 and came into effect on 8 August 2008. This legislation requires NPOs to register with the Commission in certain circumstances. The definition of an NPO, as provided by Article 1 of the NPO Law, is given below: “An organization is a non-profit organization for the purposes of this Law if – (a) it is established solely or primarily for charitable, religious, cultural, educational, social, or fraternal purposes with the intention of benefiting the public or a section of the public; and (b) it raises or disburses funds in pursuance of those purposes.” ” [1] [1] http://www.jerseyfsc.org/anti-money_laundering/forms/NPO/index.asp	JE	http://www.jerseyfsc.org/index.asp	False
JE-OAC (withdrawn)	Jersey Overseas Aid Commission	The Jersey Overseas Aid Commission is responsible for distributing international development funds from Jersey. But they are not responsible for registration of NGOs. No database for organisation identifiers has been found. “Jersey has been funding international aid and development since 1968, but the current ‘Jersey Overseas Aid Commission’ was established by law in 2005. It is an independent body within the responsibilities of the Chief Minister. It is governed by three States Commissioners and three non-States Commissioners, all of whom are appointed by the States of Jersey.” [1] “The Non-Profit Organizations (Jersey) Law 2008 (the “NPO Law”) was registered by the Royal Court on 25 July 2008 and came into effect on 8 August 2008. This legislation requires NPOs to register with the Commission in certain circumstances. ” [2] [1] https://www.joa.je/the-commission/ [2] http://www.jerseyfsc.org/anti-money_laundering/forms/NPO/index.asp	JE	http://www.jerseyoverseasaid.org.je/	False
JO-CCD	Companies Control Department (Jordan)	The Companies Control Department is an independent national financial and administrative institution affiliated to the Minister of Industry and Trade in Jordan under the provisions of the amended Companies Law No. (40) of 2002. The work of the department is governed by the 1997 Companies Law No. The Department is responsible for registration of various types of companies within the Hashemite Kingdom of Jordan, including non-profit companies. It maintains a number of online services for searching company information at http://www.ccd.gov.jo/e-services/home/db available in Arabic only.	JO	http://www.ccd.gov.jo/	True
JO-MSD	Register of Associations, Jordan	“The register of associations was established in the Ministry of Social Development in the Hashemite Kingdom of Jordan by virtue of the Associations Law No. (51) of 2008 and its amendments which abolished the Law of Associations and Voluntary Organizations No. 33 of 1966 and its amendments. The register of associations is the regulator of the associations sector in the Kingdom and in line with the legislation in force.”[1] [1]: http://www.societies.gov.jo/SitePage.aspx?PageId=107 (translated from Arabic)	JO	http://www.societies.gov.jo/	True
JP-JCN	National Tax Agency Corporate Number Publication Site	On this website, the Corporate Number of each organization that has such number designated, and the name and the address of the head office or principal place of business of each organization that has registered its indications in English are made public. The registry is open and searchable by Japanese Corporate Number (JCN) (in Japanese only), but only limited information is available. More information on the corporate number (JCN) can be found here - http://www.nta.go.jp/foreign_language/corporate_number/ (National Tax Agency website).	JP	http://www.houjin-bangou.nta.go.jp/	True
KE-NCB	NGO’s Coordination Board	The NGO Coordination Board of Kenya registers NGOs and maintains a registry of organisation information. This information can be accessed by through request and after paying a fee. “The Board has the responsibility of regulating and enabling the NGO sector in Kenya. Our Mandate: To maintain the register of National and International NGOs operating in Kenya, with the precise sectors, affiliations and locations of their activities.” [1] “Under section 31 of the NGOs Regulations 1992, any member of the public is allowed to inspect the files and the documents therein of any registered organization during normal working hours. They can also obtain copies of documents in the files. To conduct a records search a letter should be written to the ED of the NGOB stating the name of the applicant as well as the organization whose details they wish to search and the information they seek. The applicant can decide whether to carry out the records search themselves or have the Board conduct it on their behalf. This will be upon a requisite payment of Kenya Shillings Three Thousand (KES 3000)” [2] [1] http://www.ngobureau.or.ke/ [2] http://www.ngobureau.or.ke/?page_id=408	KE	http://www.ngobureau.or.ke/	False
KE-RCO	Registar of Companies	The Registrar of Companies is under the remit of the Registrar General, which is a part of the Office of the Attorney General and Department of Justice. This Registrar is responsible for the registration of companies within Kenya, and maintains a database, the records of which can be accessed on request for a fee.	KE	http://www.attorney-general.go.ke/	False
KE-RSO (withdrawn)	Registrar of Societies	The Registrar of Societies is held under the Office of the Attorney General and Department of Justice. Interest groups in Kenya apply to the Registrar of Societies for both registration and exemption from registration of being a ‘society’. But there is no indication that societies have legal/corporate foundation. There is also no publicly available database of the Registrar of Societies. For Kenya’s NGO registry list, users should look to KE-NCB. Please note there is currently no publicly available dataset for this registry. “In summary, State Law Office and Department of Justice is mandated to promote the rule of law and public participation; support Government’s investment in socio-economic development; promote transparency, accountability, ethics and integrity; spearhead policy, legal and institutional reforms; promote economic governance and empowerment; promotion, fulfillment and protection of human rights; undertake administrative management; capacity building; and enhance access to justice.” [1] [1] http://www.statelaw.go.ke/about-office-of-the-attorney-general-and-department-of-justice/	KE	http://www.attorney-general.go.ke/	False
KG-ID	Electronic database of legal entities and branches (Krygyzstan)	The Ministry of Justice of the Republic of Kyrgyz maintains the register of legal entities.	KG	http://register.minjust.gov.kg/register/SearchAction.seam?logic=and&cid=204	True
KG-INN	Kyrgyz Republic Register of Legal Entities	The Ministry of Justice of the Kyrgyz Republic maintains the register of legal entities. Only Russian and Kyrgyz interfaces are available.	KG	http://register.minjust.gov.kg/register/SearchAction.seam?logic=and&cid=205	True
KZ-BIN	Business Identification Number (BIN)	“Business Identification Number (BIN) is a unique number consisting of 12 digits created for legal person (branch and agency) and individual entrepreneur operating in form of joint entrepreneurship. […] as from January 1, 2013 […] BIN (Business Identification Number) will be implemented in the Republic of Kazakhstan instead of Taxpayer’s Registration Number (TRN).”[1] The Ministry of Finance of the Republic of Kazakhstan maintains the business register. [1] https://www.norvik.eu/en/iin-and-bin-implementation-in-the-republic-of-kazakhstan/?print=1	KZ	http://kgd.gov.kz/en/services/taxpayer_search/legal_entity	True
LB-CR	Lebanese Ministry of Justice, Commercial Register	‘Article 23 of the Lebanese Trade Law stipulates that ‘every court of first instance shall have a record carefully recorded by the author under the supervision of the President or a judge appointed by the President specifically in each year’. The Clerk of the Court is limited to the recording of data submitted by stakeholders without examination or scrutiny and without verifying their validity. The Commercial Register is divided into two types: - a general register in which traders and companies register. - A special register in which commercial establishments and contracts are registered’[1] [1]: http://cr.justice.gov.lb/desc/desc.aspx (translated)	LB	http://cr.justice.gov.lb/desc/desc.aspx	True
LB-MOI	Ministry of Interior (Lebanon)	The Ministry of Interior is the main registration body in Lebanon. All NGOs are required to register with the Ministry of Interior.	LB	http://www.interior.gov.lb/	False
LS-LCN (withdrawn)	Lesotho Council of Non Governmental Organisations	The Lesotho Council of NGOs provides a range of support services and advocacy to civil society organisations in Lesotho. They do not appear to have the responsibility of either registering NGOs or maintaining a database of identifiers. “The Lesotho Council of Non-Governmental Organisations (LCN) is an umbrella organizations for NGOs in Lesotho. It was established in May 1990 with an objective of providing supportive services to the NGO Community. The Council implements this through networking and leadership training and development, information dissemination, capacity building, coordination, advocacy and representation when dealing with the government and the international community.” [1] [1] http://www.lcn.org.ls/about/default.php	LS	http://www.lcn.org.ls/	False
LT-PVM	Lithuania Register of Legal Entities	The Register of Legal Entities registers businesses, institutions and NGOs and collects detailed data about Lithuanian legal entities as well as branches and representative offices of foreign companies and organizations. The Register contains complete information (and historical data) about legal form and status of legal entities, fields of its activity, size and structure of the authorized capital, members of sole and collective management bodies, licenses acquired, etc. It is obligatory for the most of business companies to submit annual financial statements to the Register of Legal Entities since 2004. Starting from March 2010 private limited liability companies are obliged to declare current list of shareholders to the Register.	LT	http://www.registrucentras.lt/jar/index_en.php	True
LT-RC	Information Platform of Legal Entities (Lithuania)	“The Register of Legal Entities registers businesses, institutions and NGOs and collects detailed data about Lithuanian legal entities as well as branches and representative offices of foreign companies and organizations. The Register contains complete information (and historical data) about legal form and status of legal entities, fields of its activity, size and structure of the authorized capital, members of sole and collective management bodies, licenses acquired, etc. It is obligatory for the most of business companies to submit annual financial statements to the Register of Legal Entities since 2004. Starting from March 2010 private limited liability companies are obliged to declare current list of shareholders to the Register. “[1] Government agencies are also included in the register. [1] http://www.registrucentras.lt/jar/index_en.php	LT	http://www.registrucentras.lt/jar/index_en.php	True
LV-RE	Register of Enterprises of the Republic of Latvia	The Register of Enterprises registers companies and maintains a database of organisation information. This information is searchable on the website and can be found in CSV form. “Register of Enterprises is the central institution which keeps all data and records up to date. It is mandatory to submit incorporation documents with the registry at the moment of company establishment, as well as to file all amendments in the company board (directors) or shareholder registry. The unified register is also available electronically. The Register of Enterprises has the following functions: to register undertakings and their branches, representative offices and representatives of foreign undertakings and organisations, co-operative companies,” [1] [1] http://www.baltic-legal.com/commercial-register-of-latvia-eng.htm Free of charge information includes type of legal entity; registered office; new or current name or trade name and previously registered or historical name or trade name; registration number; Single Euro Payment Area beneficiary identification code (if allocated); registration date; date of deletion of the legal entity from the register (or the date of reorganisation if the reason for the deletion is a reorganisation); deadline for registration of religious organisations that are subject to re-registration.	LV	http://www.ur.gov.lv/	True
MD-IDNO	Legal entity registration number (IDNO) Moldova	“General information about the legal entities incorporated on the Republic of Moldova’s territory, except political parties, non-governmental organizations and press agencies. Data from the State Chamber of Registration is published once per month on the Government Portal of Open Data (http://www.date.gov.md/en) and can be searched in a convenient way via dedicated platform http://www.idno.md/.”[1] The unique state identification number (IDNO) assigned to the legal entity also constitutes its fiscal code. “The idno.md platform has been developed to facilitate access to open government data and to help citizens gain added value by using them. The project is based on the reuse of public data about registered companies in the Republic of Moldova, presenting them in a user-friendly way so that everyone can easily analyze and process them. The platform allows users to search through data, track company history, and generate infotainment based on available data. At present, information is available about over 215,000 companies that have been registered in Moldova since 1991. The data on idno.md is updated monthly, automatically. The idno.md team has long envisioned to integrate other information that will be available to the public, including information on public procurement connected with companies that have won tenders over the years.”[1] More information about companies and their administrators / founders can be requested at the State Registration Chamber. [1] http://www.idno.md/page?id=2 (Nov, 2017) [2] http://www.idno.md/page?id=5 (Nov, 2017)	MD	http://www.idno.md/	True
ML-CCIM	The Chamber of Commerce and Industry of Mali	The Chamber of Commerce and Industry of Mali (CCIM) is responsible for the organization and professional representation of organisations and legal persons working in the various branches of commercial, industrial and service activities in Mali.	ML	http://www.cci.ml/	False
ML-NIF	Tax Identification Number	The Tax Identification Number (Numero d’Identification Fiscale) is issued to registered companies, and to branches of foreign organisations operating in Mali. There is publicly available register of assigned Tax Identification Numbers.	ML	http://demarchesadministratives.gouv.ml/demarches/afficher/Numero-d-Identification-Fiscale-NIF	False
MM-MHA	Ministry of Home Affairs - Central Committee for the Registration and Supervision of Organisations	The MHA assigns a registration number to each NGO - this number is time limited, for example 4 years, after which the registration is reviewed. There is no URL for the Ministry, nor is there a publicly available database of NGO information.	MM		False
MU-CR	Companies and Businesses Registration Integrated System, Mauritius	The Corporate and Business Registration Department has the following main functions: - The incorporation, registration and striking-off of companies - The registration of documents that must be filed under the Companies Act 2001 - The provision of company information to the public - The enforcement of compliance with the legal requirements - Registration of Businesses - The Insolvency Service - Registration of Limited Partnerships and Foundations	MU	http://companies.govmu.org/	True
MW-CNM (withdrawn)	The Council for Non Governmental Organisations in Malawi	The Council for NGOs in Malawi provides a range of support services and advocacy initiatives to NGOs working in Malawi. They do not appear to have the responsibility of registering organisations or maintaining a database with information. “Objectives: 1. To represent the collective interests of NGOs in Malawi. 2. To enhance and improve the operational environment within which NGOs function. 3. To promote and facilitate networking, coordination and collaboration within the NGO community, and between the NGOs and government, donor community and private sector. 4. To further the standing of NGOs as competent, professional and suitable agents of development. 5. To support member NGOs to build and strengthen their institutional capacity. 6. To support NGOs carry out their functions under the NGO Act 2000.” [1] [1] http://www.congoma.mw/about-us/objectives/	MW	http://www.congoma.mw	False
MW-MRA (withdrawn)	Malawi Revenue Authority	The Malawi Revenue Authority is responsible for processing tax payments and investigating cases of tax evasion in Malawi. They do not appear to be responsible for the registration of companies or maintaining a database of organisations. Company registration in Malawi is done through the Department of Registrar General, under the Ministry of Justice and Constitutional Affairs. “The Ministry of Industry and Trade is responsible for providing application forms for Registration of Business Name. Applications may be submitted to the Department of Registrar General’s Head Office in Blantyre and its Regional Office in Lilongwe.” [1] [1] https://www.wikiprocedure.com/index.php/Malawi_-_Register_Business_Name	MW	http://www.mra.mw/	False
MW-NBM	NGO Board of Malawi	All NGOs operating in Malawi must register with the NGO Board of Malawi. All NPOs must also register with the Registrar General. There is a pdf file with a list of registered NGOs, but they do not have registration numbers. New database is planned. “In line with Section 20 of the NGO Act, every organization that wishes to operate or is operating in Malawi as an NGO must register with the NGO Board of Malawi. The Board is a regulatory Body for NGOs in Malawi and failure to register with it means the NGO will be operating illegally.” [1] “We are currently improving our directory which will not only show a list of registered NGOs when this process is completed, but will also provide an overview of each registered NGO, contacts, and will be searchable by sector and/or location (District).” [2] “The Registrar General is responsible for the registration and the administration non-profit entities under the Trustees Incorporation Act Cap. 5:03. ” [3] [1][2] http://ngoboardmalawi.mw/directory.php [3] https://www.registrargeneral.gov.mw/services/registration-of-businesses.html	MW	http://ngoboardmalawi.mw/directory.php	False
MW-RG	Registrar General, Department of Justice	The Department of Registrar General under the Department of Justice and Constitutional Affairs is where companies and NPOs register in Malawi. They do not have a database of company information available online. “We are a government department under the Ministry of Justice and Constitutional Affairs responsible for the registration and administration of business entities, Non Profit Organizations and Industrial Property Rights” [1] [1] https://www.registrargeneral.gov.mw/index.html	MW	https://www.registrargeneral.gov.mw/index.html	False
MX-CPA	Budget Classification of Public Entities (Mexico)	This list provides Mexico’s administrative classification, which includes the following concepts: * Ramo: a concept that groups all the specific organizations from Mexico’s Public Administration. * Unidad Responsable: the specific organizations from Mexico’s Public Administration By combining the Ramo, and Unidad Responsable codes, a unique identifier can be created for government entities. For example: 4-121 for Dirección General de Protección Civil	MX	http://www.transparenciapresupuestaria.gob.mx/work/models/PTP/DatosAbiertos/Metadatos/catalogos_presupuestarios.xlsx	True
MX-RFC	Federal Taxpayers Registry	The Registro Federal de Contribuyentes de México assigns an RFC identifier to both individual and corporate taxpayers. Registration takes place through Servicio de Administración Tributaria (SAT) and registrants are provided with their RFC. Whilst there is no public database of RFCs available, a web service to validate RFCs is available at https://portalsat.plataforma.sat.gob.mx/ConsultaRFC/ The structure of an RFC encodes information about the initials and date of registration of a company	MX	https://portalsat.plataforma.sat.gob.mx/ConsultaRFC/	False
MY-SSM	Companies Commission of Malaysia	The Companies Commission of Malaysia (SSM) is a statutory body formed as a result of a merger between the Registrar of Companies (ROC) and the Registrar of Businesses (ROB) in Malaysia which regulates companies and businesses. SSM came into operation on 16 April 2002.	MY	http://www.ssm.com.my/ms	True
MZ-CR	Mozambique Commercial Registry	The purpose of the Commercial Registry is to make known the status of merchant of natural and legal persons, being defined as mandatory for the formation of companies.	MZ	http://www.portaldogoverno.gov.mz/Empresas/Registos/Registo-de-Sociedades	False
MZ-MOJ	Mozambique Ministry of Justice	‘Domestic NGOs are required to register with the Ministry of Justice.’[1] [1] http://www.commonwealthofnations.org/sectors-mozambique/civil_society/national_ngos_civil_society/	MZ	http://www.commonwealthofnations.org/sectors-mozambique/civil_society/	False
MZ-NUIT	Taxpayer Single Identification Number (Mozambique)	NUIT is the Mozambique Taxpayer Single Identification Number. It is made up of 9 digits split into 3 parts: the first digit stands for the type of entity, the middle part is a sequential number, and the last digit provides a checksum. Both individuals and corporate entities are assigned an NUIT.	MZ	http://www.at.gov.mz/eng/Internacional-Trade/FAQ-s/NUIT	False
NG-BPP	Bureau of Public Procurement (BPP) Contractor Registration System (Nigeria)	The Nigerian Bureau of Public Procurement are responsible for monitoring and oversight of public procurement in Nigeria. The Contractor and Service Provider Database System is a government vendor registration database system that assigns a unique contractor identification number, categories, and classification of firms who have applied for, or been involved in, government contracts.	NG	http://federalcontractors.bpp.gov.ng/	True
NG-CAC	Nigerian Corporate Affairs Commission	All companies operating in Nigeria must register with the Corporate Affairs Commission. NGOs also register with the Commission. This database is available through a searchable webpage. “The Corporate Affairs Commission (CAC) of Nigeria was established in 1990 vide Companies and Allied Matters Decree no 1 (CAMD) 1990 as amended, now on Act cap C20 Laws of federation of Nigeria. It is an autonomous body charged with the responsibility to regulate the formation and management of companies in Nigeria.” [1] “In Nigeria NGOs may be registered as a company limited by guarantee or as incorporated trustees (by which trustees of the NGO, rather than the NGO itself, obtains the status of a body corporate)… The duly completed application is then submitted to the Corporate Affairs Commission.” [2] [1] https://en.wikipedia.org/wiki/Corporate_Affairs_Commission,_Nigeria [2] http://www.nigeriaformations.com/charities-and-NGOs.php	NG	http://new.cac.gov.ng/home/	False
NL-KVK	Chamber of Commerce (Netherlands)	All companies and entities (including most NGOs) in the Netherlands must enrol with the Commercial Register, which is hosted by the Dutch Chamber of Commerce. Each entity receives a Chamber of Commerce number upon registration, which is the appropriate identifier Dutch companies and NPOs. Basic company information is available for free, detailed info can be downloaded for a fee. “All companies and entities in the Netherlands must enroll in the Commercial Register. By law, you have a business if you provide common goods or services to others with the intent to make a profit.” [1] “Recipient companies can consult www.kvk.nl/waadi to check if agencies are registered on the Chamber of Commerce website. They can do this simply by entering their Chamber or Commerce number, which is assigned to all companies and legal entities upon registration in the Business Register.” [2] “The major forms of Dutch non-profit organization are the associations, the foundations and the churches… Associations registered in The Netherlands are unions between two or more individuals, physical persons or corporate bodies that pursue certain goals stated in the Articles of Association and that cannot divide profit among its members… There are two types of associations that can be set up in the Netherlands: with complete authority under the law (in this case the articles of associations are drawn by a civil notary and it’s mandatory in this case that the association is registered at the Dutch Chamber of Commerce trade register) and with limited authority under the law (when the articles are not drawn up by a notary and the registration is not mandatory).” [3] [1] https://www.kvk.nl/inschrijven-en-wijzigen/inschrijven/?block=420250 [2] https://www.kvk.nl/english/how-to-register-deregister-and-report-changes/registering-with-the-chamber-of-commerce/hiring-or-provision-of-workers-in-the-netherlands/ [3] http://www.bridgewest.eu/article/register-non-profit-organization-netherlands	NL	https://www.kvk.nl/english/	False
NL-OWMS	Overheid.nl Web Metadata Standard	Overheid.nl is the central access point to all information about government organisations of the Netherlands. The Overheid.nl Web Metadata Standard ( OWMS ) is the metadata standard for information from the Dutch government on the Internet. It contains URIs for a wide range of government bodies, including national, local and regional government and water boards. It provides a linked open dataset which contains ontological information about the relationship between those organisations (e.g. listing parent agencies, or noting organisations that succeed previous organisations). A management plan is in place for updating of the information [1]. [1]: http://standaarden.overheid.nl/owms/beheer	NL	http://standaarden.overheid.nl/owms/4.0/doc/waardelijsten	False
NO-BRC	Brønnøysundregistrene	Companies in Norway must be Registered with the Register of Business Enterprises. Non-profits are eligible for registry with the Register of Non-Profit Organizations. These registries are maintained by the Brønnøysundregistrene. Businesses can be incorporated by applying to the online ‘coordinated register notification’ - Altinn, which is also maintained by Brønnøysundregistrene. This database can be searched by the public for free from the organisation homepage, and can be downloaded in various data format. “The Register of Business Enterprises registers all Norwegian and foreign businesses in Norway, ensuring legal protection and financial overview.” [1] “Non-profit organizations that run voluntary activities not motivated by profit are eligible to register. Examples of such organizations are: - associations - non-commercial foundations that do not distribute funds, or that only - distribute funds to non-profit activities - commercial foundations that only distribute funds to non-profit activities - limited liability companies that only distribute funds to non-profit activities.” [2] “Brønnøysund Register Centre (Norwegian Bokmål: Brønnøysundregistrene, Norwegian Nynorsk: Brønnøysundregistra) is a Norwegian government agency that is responsible for the management of numerous public registers for Norway, and governmental systems for digital exchange of information.” [3] [1][2] https://www.brreg.no/home/about-us/the-registers-and-their-timeline/ [3] https://en.wikipedia.org/wiki/Br%C3%B8nn%C3%B8ysund_Register_Centre	NO	http://www.brreg.no/	False
NP-CRO	Company Registrar Office	All companies operating in Nepal must register with the Office of the Company Registrar Office. This database is available for search on the Office homepage. “To register a company, the promoter must submit an application as prescribed by the Ministry of Industry, Commerce, and Supplies. Online filing of the required documents has been introduced and made mandatory. After the online filing, entrepreneurs are required to visit the Office of Company Registrar and submit all the original documents for further verification.” [1] [1] http://www.doingbusiness.org/data/exploreeconomies/nepal#starting-a-business	NP	http://www.cro.gov.np/	False
NP-SWC	Social Welfare Council Nepal	International NGOs wishing to operate in Nepal must register with the Social Welfare Council. Upon registration, these INGOs receive an Affiliation Certificate and an SWC Affiliation Number. This database can be searched on the website. Local NGOs do not need to be associated with the SWC, but may register with their local District Administration Office (DAO). The SWC list is thus not a complete list of all NGOs working in Nepal. “1. As laid down in article 12, Section 1, of the Social Welfare Act 2049, the international non-governmental organizations (INGOs) seeking to work in the Kingdom of Nepal must apply to the Social Welfare Council and seek permission prior to starting work.” [1] [1] Document available for download at - http://www.swc.org.np/?page_id=47	NP	http://www.swc.org.np/	False
PE-SUNARP	Peruvian National Superintendency of Public Registries - Registered Legal Entities	The SUNARP is an autonomous decentralized body of the Justice Sector in Peru and the governing body of the National System of Public Registries. It maintains the register of Legal Entities (“Registro De Personas Juridicas”) which covers corporate and non-corporate bodies including: * Non Corporate * Associations * Foundations * Committees * Peasant and native communities * Cooperatives * Grassroots social organizations * Corporate * Public Limited Companies (open and closed) * Collective Societies * Limited Partnerships * Limited Liability Company * Civil Companies	PE	https://www.sunarp.gob.pe/dn-personas-juridicas.asp	True
PH-SEC	Securities and Exchange Commission (Philippines)	The Securities and Exchange Commission in the Philippines provides licenses so that corporations, partnerships or associations can transact business in the Philippines. For domestic companies, this may come in the form of a ‘Certificate of Incorporation’. For foreign firms or organisations, branches may obtain a ‘License to transact business’.	PH	http://www.sec.gov.ph/	False
PK-PCP (withdrawn)	Pakistan Centre for Philanthropy	The Pakistan Centre for Philanthropy provides certification for NGOs working in Pakistan. Registration with the PCP is not obligatory for working in Pakistan and therefore not all NGOs will be recorded on the ‘PCP Certified CSO List’. However, this list can be searched online. All NGOs are required to register with their local Voluntary Social Welfare department. “This voluntary assessment aims to enhance a CSOs’ credibility and resultantly its access to funding. Through the allied activities of this programme, PCP promotes certified CSOs in an annual directory and on its website and also builds capacities of civil society organisations for greater effectiveness.” [1] [1] http://pcp.org.pk/page.php?pid=19	PK	http://pcp.org.pk/index.php	False
PK-VSWA	Pakistan Voluntary Social Welfare Agency	All NGOs are required to register with their local Voluntary Social Welfare (VSWA) department. The VSWA assigns each organisation with an organisation identifier that is made up of a number and the year of registration. There is no searchable database. The VSWA number should be used as a unique identifier, but users should be aware that the entire sequence is needed (number and year), as it is possible that the number is unique to the year of registration, but is repeated for other years, i.e, 511-2007 is ASFP, but there may be another org with 511-1998. “Any person intending to establish an agency, and any person intending that an agency already in existence should be continued as such, shall, in the prescribed form, and on payment of the prescribed fee, make an application to the Registration Authority” [1] “9.Registration, professional guidance and financial assistance to voluntary Social Welfare agencies for strengthening, improving and promoting their activities, coordination amongst NGOs / Donors and concerned government departments.” [2] [1] http://www.ilo.org/dyn/natlex/docs/ELECTRONIC/81785/88956/F1282834913/PAK81785.pdf [2] http://www.swkpk.gov.pk/	PK	http://social_welfare.kp.gov.pk/	False
PL-KRS	The National Court Register (Poland)	The National Court Register (KRS standing for Krajowy Rejestr Sądowy) number is required to be acquired by several types of organizations: companies (without Sole Proprietorships that register in CEiDG), non-profits (associations, foundations, charities), unions and public health institutions. An organization has to apply for a KRS number and pay a fee (around 25$).	PL	https://ems.ms.gov.pl/krs/wyszukiwaniepodmiotu	True
PL-NIP	Tax Identification Number (Poland)	The Tax Identification Number (NIP) is used for tax purposes and can be assigned to any organization: companies including sole proprietorships, non-profits, government agencies. NIP is assigned to organizations in process of their registration. Till 2011 NIP number was also assigned to natural people (tax payers).	PL	https://pl.wikipedia.org/wiki/NIP	True
PL-REGON	REGON - Statistical number of an economy entity	A unique number assigned to national economic entities, and to the local units of these entities in the national official register of national economy entities, REGON. The identifier provides no implicit or explicit information on the features of an entity. Every organization receives REGON number during the registration phase. Looking at REGON/NIP relations: most often all organizations having NIP (PL-NIP) will have REGON (PL-REGON) and vice-versa. One of a few exceptions are, for example, schools that will have REGON numbers (for statistical purposes), but they are not required to have NIP tax id number (because they are executing municipalities’ budgets).	PL	http://stat.gov.pl/en/metainformations/glossary/terms-used-in-official-statistics/2963,term.html	True
PS-MOI	Ministry of Interior (Palestine)	The Palestine Ministry of Interior provide a registration list of NGOs, divided by province and responsible ministry.	PS	http://www.moi.pna.ps/NGOs/List	False
PT-NIPPC	Portal of Public Services	The business register is governed by the Business Registry Code, adopted by Decree-Law No 403/86 of 3 December 1986, and is the responsibility of the business registry offices throughout the country; these offices are external services of the Institute of Registrars and Notaries (IRN), a public body supported by the Ministry of Justice.	PT	https://www.portaldocidadao.pt/	True
PY-PGN	Classification of Entities in the National Budget for Paraguay	Provides identifiers for organizations and institutions from the Paraguayan State, including national public bodies, administrative departments, and municipalities. From the National Budget Law (Presupuesto General de la Nación (PGN)) of 2016 from Paraguay: “The objective of the classification by entities is to organize information related income, spending and budgetary credits from the different state organisms and entities at various institutional levels according to their functions, nature, characteristics and dependencies.”[1] The list is yearly updated given each the yearly national budget law. N.B. Please note, many government organisations also have an ‘RUC’ code (list [PY-RUC](/list/PY-RUC)), which is preferred to this list. [1]: http://bit.ly/PGNPY2016	PY	http://www.hacienda.gov.py/web-hacienda/archivo.php?a=keke1117221b211c20db1d141bdedcdde2db1019ke2016131610ke111c1fdedcdde2da1d1113ke0ac&x=6262001&y=keke0ac	True
PY-RUC	Unique Taxpayer Registry, Paraguay	The Registro Único del Contribuyente (RUC) is the unique taxpayer registry that maintains the personal, non-transferable, identification number for all those physical persons (national or foreign) and legal entities (for-profit and non-profit) that carry out economic activities in the Paraguayan territory. The identification number is created primarily for tax purposes.	PY	http://www.hacienda.gov.py/web-hacienda/index.php?c=77	True
RO-CUI	National Trade Register (Romania)	The National Trade Register Office (NTRO) is a public institution with legal personality, subordinated to the Ministry of Justice, entirely financed from the state budget, whose activity is regulated by the Law no. 26/1990 on trade register, as republished and subsequently amended and supplemented. The National Trade Register Office carries out the following activities: * keeping the trade register; * providing documents and information; * archiving documents based on which the registrations in the trade register are made; * assisting legal and natural persons subject to registration in the trade register; * editing and publishing the Insolvency Proceedings Bulletin.	RO	http://www.onrc.ro/index.php/ro/	True
RS-APR	Serbian Business Registrations Agency	The Serbian Business Registrations Agency (APR) provides a single place of registration for all companies and individuals - domestic and foreign - operating in Serbia. Each entity is given an identification number and a tax number in the Business Entities Register. The Матични број / identification number should be used for identifiers. A searchable database of the Business Entities Register is available online. “The SBRA runs business registers as single, centralized, public electronic databases: The Business Register, in accordance with the Law on Business Entities Registration (operative as of 1/1/2005): *Register of Companies (in effect as of 1 January 2005) * Register of Entrepreneurs (in effect as of 1 January 2006) * Register of foreign parties (in effect as of 1 January 2006)” [1] “Serbian term or phrase: matični broj / identification number This is the identification number contained in the Company Register ” [2] [1] http://www.apr.gov.rs/eng/AboutAgency/AllRegistersatOnePlace.aspx [2] http://www.proz.com/kudoz/serbian_to_english/law_contracts/2614508-maticni_broj.html	RS	http://www.apr.gov.rs/eng/Home.aspx	False
RS-PIB	Tax identification number register	Ordinary taxpayer registration numbers start from the number 10000001 and end with the number 99999999. The PIB is determined so that the first eight digits are the regular registration number of the taxpayer, and the last digit is the control number.	RS	http://www.poreskauprava.gov.rs/pib.html	True
RU-INN	Uniform State Register of Legal Entities of Russian Federation	This register offers information reports on any legal entity registered on the territory of the Russian Federation in the on-line mode directly from the respective registers. There are following types of products available at this moment: * Extract from USRLE - price 1 credit (1 credit is equal to 10.8 Euro, discounts available, see Rates/Prices) * Annual Accounts - price 2 credits * Extended Report - price 2 credits * Extended Report + Finances - price 4 credits * Court records + Enforcement proceedings - price 4 credits	RU	https://russianpartner.biz/	True
RU-OGRN	Unified State Register of Legal Entities (USRLE), Russian Federation	“The USRLE (Uniform State Register of Legal Entities) (also EGRUL) is a federal information resource. The USRLE recording is performed by the registering authorities according to the procedure established by the Government of the Russian Federation. Here you can get information about any legal entity registered in the territory of the Russian Federation in the form of an information extract from the Unified State Register of Legal Entities. In addition, access to foreign state registers of more than 200 countries of the world is open, including to most European countries. Information is provided from the Unified State Register of Legal Entities in the form of an electronic document.”	RU	https://www.egrul.ru/	True
SE-BLV (withdrawn)	Bolagsverket	The Swedish Companies Registration Office (Bolagsverket) registers all business operating in Sweden, except for sole traders. This registry is available to search online. All entities are given an organisation number that can be used as an identifer. “All forms of business enterprise except for sole traders have to be registered with the Swedish Companies Registration Office before starting to operate.” [1] [1] https://www.verksamt.se/en/web/international/starting/get-started-business-registration-and-tax	SE	http://www.bolagsverket.se/	False
SE-KK (withdrawn)	Legal, Financial and Administrative Services Agency (Sweden)	A Swedish administrative authority under the Ministry of Finance, which is responsible for the registration of religious communities and organisational units of religious communities.	SE	https://www.kammarkollegiet.se/	False
SE-ON	Business Registration Number (Organisationsnummer), Sweden	“The organization number is a unique identifier assigned to legal entities, such as companies and associations. The authority that registers the company or association when it is to be started assigns the organizational number. Most companies and associations have their organization number from the Swedish Companies Registration Office [Bolagsverket](http://www.bolagsverket.se). But also, for example, the Swedish Tax Agency and Land Survey allocate organizational numbers. From the Swedish Companies Registration Office, the company or association has its organization number when we have decided to register. The organization number is on the registration certificate that we send out.”[1] “The first digit of the organization number is called “Group Number” and specifies the company form or other legal form to which the legal entity is grouped. The following group numbers may occur. 1 - Death certificate 2 - State, county council, municipalities, parishes 3 - Foreign companies engaged in business activities or own real estate in Sweden 5 - Aktiebolag 6 - Single company 7 - Economic associations , tenant-owner associations 8 - Ideal associations and foundations 9 - Trading companies , limited companies and simple companies”[2] Non-commerical organsiation are searchable through other third-party applications, e.g. https://www.allabolag.se/ [1] http://www.bolagsverket.se/ff/foretagsformer/organisationsnummer-1.7902 [2] https://sv.wikipedia.org/wiki/Organisationsnummer#Organisationsnummer	SE	http://www.bolagsverket.se/ff/foretagsformer/organisationsnummer-1.7902	True
SG-ACRA	Accounting and Corporate Regulatory Authority (ACRA)	The Accounting and Corporate Regulatory Authority (ACRA) is the national regulator of business entities, public accountants and corporate service providers in Singapore. Each corporate entity receives a Unique Entity Number (UEN), which should be used as the identifier. “Registering or setting up a company in Singapore is accomplished through contacting Accounting and Corporate Regulatory Authority (ACRA).” [1] “From 1 January 2009, all entities that are registered in Singapore, such as businesses, local companies, limited liability partnerships (LLPs), societies, representative offices, healthcare institutions and trade unions, will have a Unique Entity Number (UEN) as its identification number. ” [2] [1] https://www.wikiprocedure.com/index.php/Singapore_-_Registering_or_Setting_up_Local_Company [2] https://www.ipos.gov.sg/Portals/0/about%20IP/copyrights/UENFAQs2.pdf	SG	http://www.acra.gov.sg/	False
SI-PRS	Slovenian Business Register	The Slovenian Business Register (PRS) is a central database containing information about all business entities involved in a profit or non-profit activity having their principal place of business located on the territory of the Republic of Slovenia, as well as information on their subsidiaries and other divisions of business entities performing business activities in the territory of the Republic of Slovenia.	SI	http://www.ajpes.eu/prs/	True
SI-TIN	Tax Identification Number (Slovenia)	A unique tax identifier code (Davčna številka) which every legal entity or an individual entrepreneur must obtain. These are entered on to the Slovenian Business Register (Poslovni register Slovenije)	SI	https://www.ajpes.eu/	True
SK-ORSR	Ministry of Justice Business Register	“The companies register is administered by the Ministry of Justice. Entry to the register is obligatory for companies, cooperatives and for some specific physical entities stated by law. Information in the register is searchable by trade name, identification number, registered office, registration number and name of a person.” [1] “The Obchodný register (commercial register) is a public list containing statutory data concerning entrepreneurs, companies and other legal entities, where this is laid down by separate legislation. The list is administered by the Ministry of Justice of the Slovak Republic.” [2] [1] http://www.company-registers.info/en/european-union/slovakia.html [2] https://e-justice.europa.eu/content_business_registers_in_member_states-106-sk-en.do?member=1	SK	http://www.orsr.sk/search_subjekt.asp?lan=en	False
SK-ZRSR (withdrawn)	Slovakia Ministry Of Interior Trade Register	The Ministry of Interior Trade Register does have a database of companies, but users should refer to the Ministry of Justice Business Register in SK-ORSR for the unique identifier list for Slovakia. The Ministry of Justice has been shown to be the organisation responsible for company registration, and thus SK-ZRSR has been deprecated in favour of SK-ORSR.	SK	http://www.orsr.sk/search_subjekt.asp?lan=en	False
SN-NINEA	National Identification Number of Companies and Associations (NINEA), Senegal	Any organization (company, association, NGO) operating in Senegal must be included in a directory of legal entities ([Source](http://www.impotsetdomaines.gouv.sn/fr/demander-un-ninea)). Registration takes place through several agencies, and a Numéro d’Identification National des Entreprises et des Associations (NINEA) (National Identification Number for Companies and Associations) is provided to incorporated bodies. A directory or lookup of companies and numbers is not available online, however most legal entities will have an NINEA which can be used as an identifier.	SN	http://creationdentreprise.sn/en/finding-business	True
SS-RRC	South Sudan Relief and Rehabilitation Commission	The South Sudan Relief and Rehabilitation Commission (SSRRC) is an agency of the Government of South Sudan. It is the operational arm of the Ministry of Humanitarian Affairs and Disaster Management. The NGO Act 2016 added additional powers to the agency to register any NGO interested in operating in South Sudan.	SS		False
TR-MERSIS	MERSIS - Central Trade Registry System	Central Trade Registry System (MERSIS) is a centralized information system allowing for the implementation of the commercial registry processes and storing them and commercial registry data electronically. MERSIS can be accessed by registered users or using the e-signature from the website of the Ministry of Customs and Trade. It contains titles of companies, addresses, contact information, capital information, companies’ partners, joint capital information, field of business, executive bodies of companies. Some information can also be found at http://www.ticaretsicil.gov.tr/english/index.php	TR	https://mersis.gtb.gov.tr/	True
TR-MOI	Department of Associations (Ministry of Interior, Turkey)	All non-profit associations operating in Turkey should register with the Department of Associations. During registration, they will be given a registration number.	TR	https://www.dernekler.gov.tr/	False
TZ-BRLA	Tanzania Business Registrations and Licensing Agency	The Business Registrations and Licensing Agency (BRELA)[ (http://www.brela.go.tz/] registers companies in Tanzania. Based on the data available on Open Corporates, it appears that BRELA assigns each organisation with a unique identifier . “The Business Registrations and Licensing Agency (BRELA) is an Executive Agency under the Ministry of Industry and Trade responsible for business administration and regulation of the laws; namely Companies Registration, Business Names Registration, Trade and Service Marks Registration, granting of Patents and issuing of Industrial License.” [1] The Business Registrations and Licencing Agency (BRELA) has started to list registered companies in Tanzania through the Online Registration System (ORS) which can be searched for business and company names by the general public. Please note, however, that not all businesses may yet be present on the ORS as updated data or annual returns are required in order to populate the database.[2] [1] http://www.brela.go.tz/index.php/about/introduction [2] https://ors.brela.go.tz/orsreg/searchbusinesspublic#	TZ	http://www.brela.go.tz/	False
TZ-TRA	Tanzania Revenue Agency	“The Tanzania Revenue Authority (TRA) was established by Act of Parliament No. 11 of 1995, and started its operations on 1st July 1996. In carrying out its statutory functions, TRA is regulated by law, and is responsible for administering impartially various taxes of the Central Government.”[1] The Tanzanian Revenue Authority provides Taxpayer Identification Numbers (TIN) for organisations registered in Tanzania. This is issued under section 3A(4) of the Income Tax Act no. 33 of 1973. As amended by the financial laws (miscellaneous amendments) 2000. There is no searchable database for TIN. It’s possible that a company with a TIN could be on the Tanzanian Business Registrations and Licensing Agency (BRELA) Online Registration System, which can be searched free of charge. It is worth checking list TZ-BRLA before deciding to use this list. [1]: https://www.tra.go.tz/index.php/about-tra/corporate-news	TZ	https://www.tra.go.tz/index.php	False
UA-EDR	United State Register	The Ministry of Justice hosts the United State Register for all corporate entities, individuals and community groups who are registered in Ukraine. Each corporate entity is assigned an identification code which can be used as a unique identifier. The is a free search and a paid search of the database, and there is a third party search in Russian. “The Ministry of Justice of Ukraine introduced online service to obtain information from the Unified State Register of Legal Entities, individual entrepreneurs and community groups” [1] [1] https://usr.minjust.gov.ua/ua/home	UA	https://usr.minjust.gov.ua/ua/home	False
UG-NGB	NGO Board, Ministry of Internal Affairs	All NGOs wishing to operate in Uganda must register with the NGO Board of the Ministry of Internal Affairs. “The National NGO Board under the Ministry of Internal Affairs, which is the lead Ministry, is legally mandated to register, regulate, coordinate and monitor NGOs in Uganda.”	UG	http://www.mia.go.ug/?page_id=62	False
UG-RSB	Registration Services Bureau	Businesses and NGOs register with the Registration Services Bureau and receive an identification number. This number can be used as an identifier. A publicly available database can be search on the Bureau website.	UG	http://www.ursb.go.ug/	False
US-DOS (withdrawn)	Corporation registration is the responsibility of each state (see link)	This code was present in the IATI Organization Registration Agency codelist. It should no longer be used.	US	http://www.companieshouse.gov.uk/links/usaLink.shtml	False
US-EIN	Employer Identification Number - Internal Revenue Service	The Internal Revenue Service (IRS) assigns companies an Employer Identification Number (EIN) upon application. However, not all corporate entities are required to have an EIN. For tax-exempt entities (non-profits, charities etc.) the IRS maintains a list of EINs. Public listed company EINs are available via the Securities and Exchange Commission (SEC). Other EINs may be available by asking the organisation concerned, and are sometimes published on their websites. “An Employer Identification Number (EIN) is also known as a Federal Tax Identification Number, and is used to identify a business entity. Generally, businesses need an EIN. ” [1] “An employer identification number (EIN), also called a tax ID number or taxpayer ID, is required for most business entities… A tax ID number is not required if you operate a sole proprietorship or an LLC with no employees, in which case you would simply use your own Social Security Number as a tax ID.” [2] “In the US, corporate registration happens at the state level. The timeliness, availability, and licensing of this data varies among all 50 states. There is no federal dataset that contains all corporate registrations. It would be possible to create a unified open registry for all US corporations (even if only via aggregation from state ones) but this does not exist at this time. Across those states performance varies widely and in many cases data is not available in bulk, is not machine readable, is not openly licensed etc. For more detail, see the per state summary on Open Corporates.” [3] “The Employer Identification Number (EIN), also known as the Federal Employer Identification Number (FEIN) or the Federal Tax Identification Number, is a unique nine-digit number assigned by the Internal Revenue Service (IRS) to business entities operating in the United States for the purposes of identification. When the number is used for identification rather than employment tax reporting, it is usually referred to as a Taxpayer Identification Number (TIN), and when used for the purposes of reporting employment taxes, it is usually referred to as an EIN. [4] [1] https://www.irs.gov/businesses/small-businesses-self-employed/employer-id-numbers-eins [2] http://tax.findlaw.com/federal-taxes/is-a-tax-id-required-for-my-business-.html [3] https://www.irs.gov/businesses/small-businesses-self-employed/employer-id-numbers-eins [4] https://en.wikipedia.org/wiki/Employer_Identification_Number	US	https://apps.irs.gov/app/eos/	False
US-USAGOV	Index of U.S. Government Departments and Agencies	The U.S. Government website has an index of departments and agencies. This index can be searched, and the URL paths for agencies used to construct government agency identifiers.	US	https://www.usa.gov/	False
UZ-KTUT	United State Register of Corporate Entites	The State Statistics Committee of the Republic of Uzbekistan maintans the United State Register of Corporate Entites and organizations (Корхоналар ва ташкилотларнинг ягона давлат)	UZ	https://my.gov.uz/uz/regService/413	False
XE-EXAMPLE	Example Data Prefix	List code prefix reserved for use in example data which require a valid org-id.guide prefix (e.g. for use in data validator testing).	-		False
XI-EORI	Economic Operators Identification and Registration system	This site allows to validate EORI numbers and provides access to the information related to Authorised Economic Operators (AEO). An EORI number is unique throughout the EU, assigned by a customs authority in a member state to economic operators (businesses) or persons.	XI	http://ec.europa.eu/taxation_customs/dds2/eos/eori_validation.jsp	False
XI-GRID	Global Research Identifiers Database	The Global Research Identifiers Database collects information on research institutions and assigns them a unique identifier. It draws on information from funding datasets, and claims over 90% coverage of institutions. It records information on the nature of the research organisation, covering companies, education establishments, healthcare, non-profits, government and other entity types. GRID also records parent-child relationships between entities, and ‘related relationships’ for cross-linkages. It includes cross-linkages to a range of other identifier sources.	-	https://www.grid.ac/	False
XI-IATI	International Aid Transparency Initiative Organisation Identifier	XI-IATI is a list of organisation identifiers that is maintained by the IATI Secretariat. Any publisher may apply to the IATI Technical Team for an identifier to be generated. “If a bona fide organisation is not registered with any recognised or appropriate registration agency (http://iatistandard.org/202/codelists/OrganisationRegistrationAgency/) they should contact the IATI Technical Team who will exceptionally allocate an organisation identifier using the XI-IATI prefix. While some of these identifiers have been derived from DAC codes, this ‘meaning’ is not carried forward. i.e. IATI generated identifiers have no intrinsic meaning. For general guidance about constructing Organisation Identifiers, please see http://iatistandard.org/organisation-identifiers/” [1] [1] http://iatistandard.org/202/codelists/IATIOrganisationIdentifier/	-	http://iatistandard.org/codelists/IATIOrganisationIdentifier/	False
XI-PB	Public Bodies - Open Knowledge Foundation	Public Bodies is an Open Knowledge Foundation (OKF) project that aims to provide a unique ID for every part of every government. The main website is a portal for linking to profile pages for countries whose public bodies OKF has recorded. There are also links to directly download CSVs of this information. Data available on the following countries/regions - Brazil, European Union, Germany, Greece, New Zealand, Switzerland, United Kingdom, United States	BR	http://publicbodies.org/	False
XI-PID	PermID: Thompson Reuters Permanent Identifier	Thomson Reuters Permanent Identifier (PermID) is a machine readable identifier that provides a unique reference for data item. PermID provides comprehensive identification across a wide variety of entity types including organizations, instruments, funds, issuers and people. PermID never changes and is unambiguous, making it ideal as a reference identifier.	XI	https://permid.org	False
XI-WIKIDATA	Wikidata	Wikidata is a free knowledge base that anyone can edit. It holds linked open data about tens of millions of entities and more than one million of them are organizations. Each instition item can hold a wide range of statements, names in hundreds of languages and identifiers in other databases.	XI	https://www.wikidata.org/	True
XM-DAC	OECD Development Assistance Committee	The Organisation for Economic Co-operation and Development (OECD) Development Assistance Committee (DAC) has created a list of organisations whom are involved in the transfer of financial flows within the work of the OECD DAC. A list of all the Donors, Agencies and Recipients can be downloaded from the OECD website. This list is updated every three years. See Donor, Agency and Delivery Channel codes. “The overarching objective of the DAC for 2011-2015 is to promote development co-operation and other policies so as to contribute to sustainable development, including pro-poor economic growth, poverty reduction, improvement of living standards in developing countries, and to a future in which no country will depend on aid.” [1] “The DAC revises the list every three years. Countries that have exceeded the high-income threshold for three consecutive years at the time of the review are removed.” [2] [1] http://www.oecd.org/dac/thedevelopmentassistancecommitteesmandate.htm [2] http://www.oecd.org/dac/stats/daclist.htm	-	http://www.oecd.org/dac/stats/dacandcrscodelists.htm	False
XM-OCHA	United Nations Office for the Coordination of Humanitarian Affairs - Financial Tracking Services Identifiers	OCHA (Office for the Coordination of Humanitarian Affairs) is the part of the United Nations Secretariat responsible for bringing together humanitarian actors to ensure a coherent response to emergencies. The Financial Tracking Service assigns it’s own organisation identifiers to parties involved in funding or delivery of humanitarian work, which are used in UN OCHA data, and may be used by some third-parties.	-	http://www.unocha.org	False
XR-NUTS	NUTS - European Union Nomenclature of Territorial Units for Statistics	The European Union’s Nomenclature of Territorial Units for Statistics (NUTS) provides codes for territorial areas at a number of different levels. Where no primary identifiers for regional and local government entities are available, then NUTS level 2 and 3 codes, and Local Administrative Unit (LAU 1 and LAU 2 level) codes could be used as a proxy for the primary local government body responsible for that area. EuroStat currently maintain a cross-walk between different levels, codes and area names for each jurisdiction. To construct an identifier: For NUTS 2 and 3 codes, use the prefix (XR-NUTS-) and then the NUTS code provided. For LAU1 and 2 codes (Local authority/ward), use the prefix (XR-NUTS-), the country prefix and underscore (e.g. UK_) , and then the LAU_NAT_Code provided (e.g. E05004874) For example: XR-NUTS-UK_E07000105	HR	http://ec.europa.eu/eurostat/web/nuts/local-administrative-units	False
ZA-CIP	Companies and Intellectual Property Commission (CIPC)	The Companies and Intellectual Property Commission (CIPC) is responsible for company registration in South Africa. There is a basic free database search, or users can subscribe to the CIPC website. “Functions of the Commission Registration of Companies, Co-operatives and Intellectual Property Rights (trade marks, patents, designs and copyright) and maintenance thereof Disclosure of Information on its business registers” [1] [1] http://www.cipc.co.za/index.php/about/our-functions/	ZA	http://www.cipro.gov.za/	False
ZA-NPO	Nonprofit Organisation Directorate - South African Department of Social Development	The Nonprofit Organisation Directorate is held under the South African Department of Social Development. NPOs register with the Nonprofit Organisation Directorate and are assigned a registration number. Users can refer to ZA-NPO for unique identifiers for NGOs in South Africa. The database can be searched for free. Users should note that they should not include “NPO” to the end of the identifier. “The Nonprofit Organisations Directorate was established in terms of the Nonprofit Organisations Act 71 of 1997 to essentially administer the Register of Nonprofit Organisations in South Africa. The Register of Nonprofit Organisations (NPOs) is a voluntary registration facility that enhances the credibility of the registered NPO as it reports to a public office. The NPO Directorate, as a public office, holds information about registered NPOs for the public to access. ” [1] [1] http://www.dsd.gov.za/npo/	ZA	http://www.npo.gov.za/	False
ZA-PBO (withdrawn)	SA Revenue Service Tax Exemption Unit	Non-profit organisations (NPOs) can apply for Public Benefit Organisation (PBO) status from the South Africa Revenue Service in order to become tax exempt. However, not all NPOs will be awarded this status, therefore the ZA-PBO should not be referred to as the Primary list of unique identifiers for NPOs in South Africa. No searchable database of PBOs has been found. “The mere fact that an organisation has a non-profit motive or is established or registered as an NPO registered under the NPO Act, or is established as an NPC, does not mean that it automatically qualifies for preferential tax treatment or approval as a PBO. An organisation will enjoy preferential tax treatment only after it has applied for and been granted approval as a PBO by the Commissioner, and continues to comply with the relevant prescribed requirements. ” [1] [1] http://www.sars.gov.za/AllDocs/OpsDocs/Guides/LAPD-IT-G16%20-%20Basic%20Guide%20to%20Income%20Tax%20for%20Public%20Benefit%20Organisations%20-%20External%20Guide.pdf	ZA	http://www.sars.gov.za/home.asp?pid=170	False
ZM-PCR	Patents and Companies Registration Agency	The Patents and Companies Registration Agency (PACRA) is responsible for company registration in Zambia. “The Patents and Companies Registration Agency (PACRA) is a semi-autonomous executive agency of the Zambian Ministry of Commerce, Trade and Industry. Its principal functions are to operate a legal system for registration and protection of commercial and industrial property and to serve as a legal depository of the information tendered for registration..” [1] [1] https://www.pacra.org.zm/#/html/About/	ZM	http://www.pacra.org.zm/	False
ZW-PVO	Private Voluntary Organisations Council (Zimbabwe)	“NGOs in Zimbabwe are mainly registered under the Private Voluntary Organization Act (PVO Act). Registration is done through the Department of Social Welfare under the Ministry of Public Service Labour and Social Welfare.” [1] [1] http://www.kanokangalawfirm.net/setting-ngo-zimbabwe/	ZW		False
ZW-ROD	Registrar of Deeds	Companies in Zimbabwe must register with the Registrar of Deeds. Currently, all Zimbabwe government websites appear not to be working. “Reserve the company name with the Chief Registrar of Companies Agency: Chief Registrar of Companies Forms are available online but all documents must be physically lodged at Companies and Deeds Registry. The reservation is valid for 30 days and can be extended for another 30 days for an additional fee.” [1] [1] http://www.doingbusiness.org/data/exploreeconomies/zimbabwe#starting-a-business	ZW	http://www.dcip.gov.zw/	False

Organisation Role

IATI codes for the role of an organisation within an activity. An organisation can play more than one role within an activity.

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/participating-org/@role

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Funding	The government or organisation which provides funds to the activity.
2	Accountable	An organisation responsible for oversight of the activity and its outcomes
3	Extending	An organisation that manages the budget and direction of an activity on behalf of the funding organisation
4	Implementing	The organisation that physically carries out the activity or intervention.

Changelog

2.01

The OrganisationRole codelist was amended to numeric values

Organisation Type

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/reporting-org/@type

• iati-activities/iati-activity/participating-org/@type

• iati-activities/iati-activity/planned-disbursement/provider-org/@type

• iati-activities/iati-activity/planned-disbursement/receiver-org/@type

• iati-activities/iati-activity/transaction/provider-org/@type

• iati-activities/iati-activity/transaction/receiver-org/@type

• iati-organisations/iati-organisation/reporting-org/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
10	Government
11	Local Government	Any local (sub national) government organisation in either donor or recipient country.
15	Other Public Sector
21	International NGO
22	National NGO
23	Regional NGO
24	Partner Country based NGO	Local and National NGO / CSO based in aid/assistance recipient country
30	Public Private Partnership
40	Multilateral
60	Foundation
70	Private Sector
71	Private Sector in Provider Country	Is in provider / donor country.
72	Private Sector in Aid Recipient Country	Is in aid recipient country.
73	Private Sector in Third Country	Is not in either a donor or aid recipient country.
80	Academic, Training and Research
90	Other

Other Identifier Type

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/other-identifier/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
A1	Reporting Organisation’s internal activity identifier
A2	CRS Activity identifier
A3	Previous Activity Identifier	The standard insists that once an activity has been reported to IATI its identifier MUST NOT be changed, even if the reporting organisation changes its organisation identifier. There may be exceptional circumstances in which this rule cannot be followed, in which case the previous identifier should be reported using this code.
A9	Other Activity Identifier
B1	Previous Reporting Organisation Identifier
B9	Other Organisation Identifier

Changelog

2.01

The OtherIdentifierType codelist was added.

Policy Marker

The Policy Marker codelist is derived from the policy markers declared by the WP-STAT. The codes themselves are created by IATI.

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/policy-marker/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Gender Equality
2	Aid to Environment
3	Participatory Development/Good Governance
4	Trade Development
5	Aid Targeting the Objectives of the Convention on Biological Diversity
6	Aid Targeting the Objectives of the Framework Convention on Climate Change - Mitigation
7	Aid Targeting the Objectives of the Framework Convention on Climate Change - Adaptation
8	Aid Targeting the Objectives of the Convention to Combat Desertification
9	Reproductive, Maternal, Newborn and Child Health (RMNCH)
10	Disaster Risk Reduction(DRR)
11	Disability
12	Nutrition

Policy Marker Vocabulary

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/policy-marker/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1	OECD DAC CRS	The policy marker is an OECD DAC CRS policy marker, Reported in columns 20-23, 28-31 and 54 of CRS++ reporting format.	http://reference.iatistandard.org/codelists/PolicyMarker/
99	Reporting Organisation	The policy marker is one that is defined and tracked by the reporting organisation

Changelog

2.01

The PolicyMarkerVocabulary codelist was added, with the Vocabulary codelist being split.

Policy Significance

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/policy-marker/@significance

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
0	not targeted	The score “not targeted” means that the activity was examined but found not to target the policy objective.
1	significant objective	Significant (secondary) policy objectives are those which, although important, were not the prime motivation for undertaking the activity.
2	principal objective	Principal (primary) policy objectives are those which can be identified as being fundamental in the design and impact of the activity and which are an explicit objective of the activity. They may be selected by answering the question “Would the activity have been undertaken without this objective?”
3	principal objective AND in support of an action programme	For desertification-related aid only
4	Explicit primary objective

Guidance

Policy Significance code = 4 (Explicit primary objective) SHOULD ONLY be used in conjunction with Policy Marker code = 9 (Reproductive, Maternal, Newborn and Child Health)

Publisher Type

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Aid Provider	A government, organisation, agency or institution that provides aid funds.
2	Aid Recipient	A government, organisation, agency or institution that recieves aid funds.
3	Aggregator	An organisation that collects and reproduces information from other providers or recipients

Region

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/recipient-region/@code

• iati-activities/iati-activity/transaction/recipient-region/@code

• iati-organisations/iati-organisation/recipient-region-budget/recipient-region/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
88	States Ex-Yugoslavia unspecified
89	Europe, regional
189	North of Sahara, regional
289	South of Sahara, regional
298	Africa, regional
380 (withdrawn)	West Indies, regional
389	North & Central America, regional
489	South America, regional
498	America, regional
589	Middle East, regional
619	Central Asia, regional
679	South Asia, regional
689	South & Central Asia, regional
789	Far East Asia, regional
798	Asia, regional
889	Oceania, regional
998	Developing countries, unspecified
1027	Eastern Africa, regional
1028	Middle Africa, regional
1029	Southern Africa, regional
1030	Western Africa, regional
1031	Caribbean, regional
1032	Central America, regional
1033	Melanesia, regional
1034	Micronesia, regional
1035	Polynesia, regional

Region Vocabulary

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/recipient-region/@vocabulary

• iati-activities/iati-activity/transaction/recipient-region/@vocabulary

• iati-organisations/iati-organisation/recipient-region-budget/recipient-region/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1	OECD DAC	Supra-national regions according to OECD DAC CRS recipient codes	http://reference.iatistandard.org/codelists/Region/
2	UN	Supra-national regions maintained by UN Statistics Division (M49 standard)	https://unstats.un.org/unsd/methodology/m49/
99	Reporting Organisation	The region reported corresponds to a region vocabulary maintained by the reporting organisation for this activity.

Related Activity Type

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/related-activity/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Parent	An activity that contains sub-activities (sub-components) which are reported separately to IATI
2	Child	A sub-activity (or sub-component) that sits within a larger activity (parent) which is also reported to IATI
3	Sibling	A sub-activity (or sub-component) that is related to another sub-activity with the same parent
4	Co-funded	An activity that receives funding from more than one organisation
5	Third Party	A report by another organisation on the same activity you are reporting (excluding activities reported as part of a financial transaction - e.g. provider-activity-id or a co-funded activity, using code 4)

Changelog

2.01

The following new code was added to RelatedActivityType: 5 (Third Party)

Result Type

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/result/@type

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Output	Results of the activity that came about as a direct effect of your work and specific, what is done, and what communities are reached. For example, X number of individuals.
2	Outcome	Results of the activity that produce an effect on the overall communities or issues you serve. For example lower rate of infection after a vaccination programme.
3	Impact	The long term effects of the outcomes, that lead to larger, over arching results, such as improved life-expectancy.
9	Other	Another type of result, not specified above.

Result Vocabulary

The ResultVocabulary codelist currently includes only 1 code (99) that can be used by organisations to define different results frameworks they are using.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/result/reference/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
99	Reporting Organisation

DAC 5 Digit Sector

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/sector/@code

• iati-activities/iati-activity/transaction/sector/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	Category
11110	Education policy and administrative management	Education sector policy, planning and programmes; aid to education ministries, administration and management systems; institution capacity building and advice; school management and governance; curriculum and materials development; unspecified education activities.	111
11120	Education facilities and training	Educational buildings, equipment, materials; subsidiary services to education (boarding facilities, staff housing); language training; colloquia, seminars, lectures, etc.	111
11130	Teacher training	Teacher education (where the level of education is unspecified); in-service and pre-service training; materials development.	111
11182	Educational research	Research and studies on education effectiveness, relevance and quality; systematic evaluation and monitoring.	111
11220	Primary education	Formal and non-formal primary education for children; all elementary and first cycle systematic instruction; provision of learning materials.	112
11230	Basic life skills for adults	Formal and non-formal education for basic life skills for adults (adults education); literacy and numeracy training. Excludes health education (12261) and activities related to prevention of noncommunicable diseases. (123xx).	112
11231	Basic life skills for youth	Formal and non-formal education for basic life skills for young people.	112
11232	Primary education equivalent for adults	Formal primary education for adults.	112
11240	Early childhood education	Formal and non-formal pre-school education.	112
11250	School feeding	Provision of meals or snacks at school; other uses of food for the achievement of educational outcomes including ‘take-home’ food rations provided as economic incentives to families (or foster families, or other child care institutions) in return for a child’s regular attendance at school; food provided to adults or youth who attend literacy or vocational training programmes; food for pre-school activities with an educational component. These activities may help reduce children’s hunger during the school day if provision of food/meals contains bioavailable nutrients to address specific nutrition needs and have nutrition expected outcomes in school children, or if the rationale mainstream nutrition or expected outcome is nutrition-linked.	112
11260	Lower secondary education	Second cycle systematic instruction at junior level.	112
11320	Upper Secondary Education (modified and includes data from 11322)	Second cycle systematic instruction at senior levels.	113
11321 (withdrawn)	Lower secondary education	Second cycle systematic instruction at junior level.	113
11322 (withdrawn)	Upper secondary education	Second cycle systematic instruction at senior level.	113
11330	Vocational training	Elementary vocational training and secondary level technical education; on-the job training; apprenticeships; including informal vocational training.	113
11420	Higher education	Degree and diploma programmes at universities, colleges and polytechnics; scholarships.	114
11430	Advanced technical and managerial training	Professional-level vocational training programmes and in-service training.	114
12110	Health policy and administrative management	Health sector policy, planning and programmes; aid to health ministries, public health administration; institution capacity building and advice; medical insurance programmes; including health system strengthening and health governance; unspecified health activities.	121
12181	Medical education/training	Medical education and training for tertiary level services.	121
12182	Medical research	General medical research (excluding basic health research and research for prevention and control of NCDs (12382)).	121
12191	Medical services	Laboratories, specialised clinics and hospitals (including equipment and supplies); ambulances; dental services; medical rehabilitation. Excludes noncommunicable diseases (123xx).	121
12196	Health statistics and data	Collection, production, management and dissemination of statistics and data related to health. Includes health surveys, establishment of health databases, data collection on epidemics, etc.	121
12220	Basic health care	Basic and primary health care programmes; paramedical and nursing care programmes; supply of drugs, medicines and vaccines related to basic health care; activities aimed at achieving universal health coverage.	122
12230	Basic health infrastructure	District-level hospitals, clinics and dispensaries and related medical equipment; excluding specialised hospitals and clinics (12191).	122
12240	Basic nutrition	Micronutrient deficiency identification and supplementation; Infant and young child feeding promotion including exclusive breastfeeding; Non-emergency management of acute malnutrition and other targeted feeding programs (including complementary feeding); Staple food fortification including salt iodization; Nutritional status monitoring and national nutrition surveillance; Research, capacity building, policy development, monitoring and evaluation in support of these interventions. Use code 11250 for school feeding and 43072 for household food security.	122
12250	Infectious disease control	Immunisation; prevention and control of infectious and parasite diseases, except malaria (12262), tuberculosis (12263), COVID-19 (12264), HIV/AIDS and other STDs (13040). It includes diarrheal diseases, vector-borne diseases (e.g. river blindness and guinea worm), viral diseases, mycosis, helminthiasis, zoonosis, diseases by other bacteria and viruses, pediculosis, etc.	122
12261	Health education	Information, education and training of the population for improving health knowledge and practices; public health and awareness campaigns; promotion of improved personal hygiene practices, including use of sanitation facilities and handwashing with soap.	122
12262	Malaria control	Prevention and control of malaria.	122
12263	Tuberculosis control	Immunisation, prevention and control of tuberculosis.	122
12264	COVID-19 control	All activities related to COVID-19 control e.g. information, education and communication; testing; prevention; immunisation, treatment, care.	122
12281	Health personnel development	Training of health staff for basic health care services.	122
12310	NCDs control, general	Programmes for the prevention and control of NCDs which cannot be broken down into the codes below.	123
12320	Tobacco use control	Population/individual measures and interventions to reduce all forms of tobacco use in any form. Includes activities related to the implementation of the WHO Framework Convention on Tobacco Control, including specific high-impact demand reduction measures for effective tobacco control.	123
12330	Control of harmful use of alcohol and drugs	Prevention and reduction of harmful use of alcohol and psychoactive drugs; development, implementation, monitoring and evaluation of prevention and treatment strategies, programmes and interventions; early identification and management of health conditions caused by use of alcohol and drugs [excluding narcotics traffic control (16063)].	123
12340	Promotion of mental health and well-being	Promotion of programmes and interventions which support mental health and well-being resiliency; prevention, care and support to individuals vulnerable to suicide. Excluding treatment of addiction to tobacco, alcohol and drugs (included in codes 12320 and 12330).	123
12350	Other prevention and treatment of NCDs	Population/individual measures to reduce exposure to unhealthy diets and physical inactivity and to strengthen capacity for prevention, early detection, treatment and sustained management of NCDs including: Cardiovascular disease control: Prevention, screening and treatment of cardiovascular diseases (including hypertension, hyperlipidaemia, ischaemic heart diseases, stroke, rheumatic heart disease, congenital heart disease, heart failure, etc.). Diabetes control: Prevention, screening, diagnosis, treatment and management of complications from all types of diabetes. Exposure to physical inactivity: Promotion of physical activity through supportive built environment (urban design, transport), sports, health care, schools and community programmes and mass media campaign. Exposure to unhealthy diet: Programmes and interventions that promote healthy diet through reduced consumption of salt, sugar and fats and increased consumption of fruits and vegetables e.g. food reformulation, nutrient labelling, food taxes, marketing restriction on unhealthy foods, nutrition education and counselling, and settings-based interventions (schools, workplaces, villages, communities). Cancer control: Prevention (including immunisation, HPV and HBV), early diagnosis (including pathology), screening, treatment (e.g. radiotherapy, chemotherapy, surgery) and palliative care for all types of cancers. Implementation, maintenance and improvement of cancer registries are also included. Chronic respiratory diseases: Prevention, early diagnosis and treatment of chronic respiratory diseases, including asthma. Excludes: Tobacco use control (12320), Control of harmful use of alcohol and drugs (12330), research for the prevention and control of NCDs (12382).	123
12382	Research for prevention and control of NCDs	Research to enhance understanding of NCDs, their risk factors, epidemiology, social determinants and economic impact; translational and implementation research to enhance operationalisation of cost-effective strategies to prevent and control NCDs; surveillance and monitoring of NCD mortality, morbidity, risk factor exposures, and national capacity to prevent and control NCDs.	123
13010	Population policy and administrative management	Population/development policies; demographic research/analysis; reproductive health research; unspecified population activities. (Use purpose code 15190 for data on migration and refugees. Use code 13096 for census work, vital registration and migration data collection.)	130
13020	Reproductive health care	Promotion of reproductive health; prenatal and postnatal care including delivery; prevention and treatment of infertility; prevention and management of consequences of abortion; safe motherhood activities.	130
13030	Family planning	Family planning services including counselling; information, education and communication (IEC) activities; delivery of contraceptives; capacity building and training.	130
13040	STD control including HIV/AIDS	All activities related to sexually transmitted diseases and HIV/AIDS control e.g. information, education and communication; testing; prevention; treatment, care.	130
13081	Personnel development for population and reproductive health	Education and training of health staff for population and reproductive health care services.	130
13096	Population statistics and data	Collection, production, management and dissemination of statistics and data related to Population and Reproductive Health. Includes census work, vital registration, migration data collection, demographic data, etc.	130
14010	Water sector policy and administrative management	Water sector policy and governance, including legislation, regulation, planning and management as well as transboundary management of water; institutional capacity development; activities supporting the Integrated Water Resource Management approach (IWRM: see box below).	140
14015	Water resources conservation (including data collection)	Collection and usage of quantitative and qualitative data on water resources; creation and sharing of water knowledge; conservation and rehabilitation of inland surface waters (rivers, lakes etc.), ground water and coastal waters; prevention of water contamination.	140
14020	Water supply and sanitation - large systems	Programmes where components according to 14021 and 14022 cannot be identified. When components are known, they should individually be reported under their respective purpose codes: water supply [14021], sanitation [14022], and hygiene [12261].	140
14021	Water supply - large systems	Potable water treatment plants; intake works; storage; water supply pumping stations; large scale transmission / conveyance and distribution systems.	140
14022	Sanitation - large systems	Large scale sewerage including trunk sewers and sewage pumping stations; domestic and industrial waste water treatment plants.	140
14030	Basic drinking water supply and basic sanitation	Programmes where components according to 14031 and 14032 cannot be identified. When components are known, they should individually be reported under their respective purpose codes: water supply [14031], sanitation [14032], and hygiene [12261].	140
14031	Basic drinking water supply	Rural water supply schemes using handpumps, spring catchments, gravity-fed systems, rainwater collection and fog harvesting, storage tanks, small distribution systems typically with shared connections/points of use. Urban schemes using handpumps and local neighbourhood networks including those with shared connections.	140
14032	Basic sanitation	Latrines, on-site disposal and alternative sanitation systems, including the promotion of household and community investments in the construction of these facilities. (Use code 12261 for activities promoting improved personal hygiene practices.)	140
14040	River basins development	Infrastructure-focused integrated river basin projects and related institutional activities; river flow control; dams and reservoirs [excluding dams primarily for irrigation (31140) and hydropower (23220) and activities related to river transport (21040)].	140
14050	Waste management/disposal	Municipal and industrial solid waste management, including hazardous and toxic waste; collection, disposal and treatment; landfill areas; composting and reuse.	140
14081	Education and training in water supply and sanitation	Education and training for sector professionals and service providers.	140
15110	Public sector policy and administrative management	Institution-building assistance to strengthen core public sector management systems and capacities. This includes general public policy management, co-ordination, planning and reform; human resource management; organisational development; civil service reform; e-government; development planning, monitoring and evaluation; support to ministries involved in aid co-ordination; other ministries and government departments when sector cannot be specified. (Use specific sector codes for development of systems and capacities in sector ministries. For macro-economic policy use code 15142. For public procurement use code 15125.)	151
15111	Public finance management (PFM)	Fiscal policy and planning; support to ministries of finance; strengthening financial and managerial accountability; public expenditure management; improving financial management systems; budget drafting; inter-governmental fiscal relations, public audit, public debt. (Use code 15114 for domestic revenue mobilisation and code 33120 for customs).	151
15112	Decentralisation and support to subnational government	Decentralisation processes (including political, administrative and fiscal dimensions); intergovernmental relations and federalism; strengthening departments of regional and local government, regional and local authorities and their national associations. (Use specific sector codes for decentralisation of sector management and services.)	151
15113	Anti-corruption organisations and institutions	Specialised organisations, institutions and frameworks for the prevention of and combat against corruption, bribery, money-laundering and other aspects of organised crime, with or without law enforcement powers, e.g. anti-corruption commissions and monitoring bodies, special investigation services, institutions and initiatives of integrity and ethics oversight, specialised NGOs, other civil society and citizens’ organisations directly concerned with corruption.	151
15114	Domestic revenue mobilisation	Support to domestic revenue mobilisation/tax policy, analysis and administration as well as non-tax public revenue, which includes work with ministries of finance, line ministries, revenue authorities or other local, regional or national public bodies. (Use code 16010 for social security and other social protection.)	151
15116	Tax collection	Operation of the inland revenue authority.	151
15117	Budget planning	Operation of the budget office and planning as part of the budget process.	151
15118	National audit	Operation of the accounting and audit services.	151
15119	Debt and aid management	Management of public debt and foreign aid received (in the partner country). For reporting on debt reorganisation, use codes 600xx.	151
15120 (withdrawn)	Public sector financial management	Strengthening financial and managerial accountability; public expenditure management; improving financial management systems; tax assessment procedures; budget drafting; field auditing; measures against waste, fraud and corruption.	151
15121	Foreign affairs	Administration of external affairs and services.	151
15122	Diplomatic missions	Operation of diplomatic and consular missions stationed abroad or at offices of international organisations.	151
15123	Administration of developing countries’ foreign aid	Support to administration of developing countries’ foreign aid (including triangular and south-south cooperation).	151
15124	General personnel services	Administration and operation of the civil service including policies, procedures and regulations.	151
15125	Public Procurement	Support to public procurement, including to create and evaluate legal frameworks; advice in establishing strategic orientation of public procurement policies and reforms; advice in designing public procurement systems and processes; support to public procurement institutions (including electronic procurement) as well as structures or initiatives to assess public procurement systems; and development of professional capacity of public procurement bodies and staff.	151
15126	Other general public services	Maintenance and storage of government records and archives, operation of government-owned or occupied buildings, central motor vehicle pools, government-operated printing offices, centralised computer and data processing services, etc.	151
15127	National monitoring and evaluation	Operation or support of institutions providing national monitoring and evaluation.	151
15128	Local government finance	Financial transfers to local government; support to institutions managing such transfers. (Use specific sector codes for sector-related transfers.)	151
15129	Other central transfers to institutions	Transfers to non sector-specific autonomous bodies or state-owned enterprises outside of local government finance; support to institutions managing such transfers. (Use specific sector codes for sector-related transfers.)	151
15130	Legal and judicial development	Support to institutions, systems and procedures of the justice sector, both formal and informal; support to ministries of justice, the interior and home affairs; judges and courts; legal drafting services; bar and lawyers associations; professional legal education; maintenance of law and order and public safety; border management; law enforcement agencies, police, prisons and their supervision; ombudsmen; alternative dispute resolution, arbitration and mediation; legal aid and counsel; traditional, indigenous and paralegal practices that fall outside the formal legal system. Measures that support the improvement of legal frameworks, constitutions, laws and regulations; legislative and constitutional drafting and review; legal reform; integration of formal and informal systems of law. Public legal education; dissemination of information on entitlements and remedies for injustice; awareness campaigns. (Use codes 152xx for activities that are primarily aimed at supporting security system reform or undertaken in connection with post-conflict and peace building activities. Use code 15190 for capacity building in border management related to migration.)	151
15131	Justice, law and order policy, planning and administration	Judicial law and order sectors; policy development within ministries of justice or equivalents.	151
15132	Police	Police affairs and services.	151
15133	Fire and rescue services	Fire-prevention and fire-fighting affairs and services.	151
15134	Judicial affairs	Civil and criminal law courts and the judicial system, including enforcement of fines and legal settlements imposed by the courts and operation of parole and probation systems.	151
15135	Ombudsman	Independent service representing the interests of the public by investigating and addressing complaints of unfair treatment or maladministration.	151
15136	Immigration	Immigration affairs and services, including alien registration, issuing work and travel documents to immigrants.	151
15137	Prisons		151
15140 (withdrawn)	Government administration	Systems of government including parliament, local government, decentralisation; civil service and civil service reform. Including general services by government (or commissioned by government) not elsewhere specified e.g. police, fire protection; cartography, meteorology, legal metrology, aerial surveys and remote sensing; administrative buildings.	151
15142	Macroeconomic policy	Support to macroeconomic stability, debt sustainability and structural reforms. Includes technical assistance for strategic formulation of policies, laws and regulation; capacity building to enhance public sector development; policy-based funding. For fiscal policy and domestic revenue mobilisation use codes 15111 and 15114.	151
15143	Meteorological services	Operation or support of institutions dealing with weather forecasting.	151
15144	National standards development	Operation or support of institutions dealing with national standards development. (Use code 16062 for statistical capacity-building.)	151
15150	Democratic participation and civil society	Support to the exercise of democracy and diverse forms of participation of citizens beyond elections (15151); direct democracy instruments such as referenda and citizens’ initiatives; support to organisations to represent and advocate for their members, to monitor, engage and hold governments to account, and to help citizens learn to act in the public sphere; curricula and teaching for civic education at various levels. (This purpose code is restricted to activities targeting governance issues. When assistance to civil society is for non-governance purposes use other appropriate purpose codes.)	151
15151	Elections	Electoral management bodies and processes, election observation, voters’ education. (Use code 15230 when in the context of an international peacekeeping operation.)	151
15152	Legislatures and political parties	Assistance to strengthen key functions of legislatures/ parliaments including subnational assemblies and councils (representation; oversight; legislation), such as improving the capacity of legislative bodies, improving legislatures’ committees and administrative procedures,; research and information management systems; providing training programmes for legislators and support personnel. Assistance to political parties and strengthening of party systems.	151
15153	Media and free flow of information	Activities that support free and uncensored flow of information on public issues; activities that increase the editorial and technical skills and the integrity of the print and broadcast media, e.g. training of journalists. (Use codes 22010-22040 for provision of equipment and capital assistance to media.)	151
15154	Executive office	Administration, operation or support of executive office. Includes office of the chief executive at all levels of government (monarch, governor-general, president, prime minister, governor, mayor, etc.).	151
15155	Tax policy and administration support		151
15156	Other non-tax revenue mobilisation	Non-tax public revenue, which includes line ministries, revenue authorities or other local, regional or national public bodies.	151
15160	Human rights	Measures to support specialised official human rights institutions and mechanisms at universal, regional, national and local levels in their statutory roles to promote and protect civil and political, economic, social and cultural rights as defined in international conventions and covenants; translation of international human rights commitments into national legislation; reporting and follow-up; human rights dialogue. Human rights defenders and human rights NGOs; human rights advocacy, activism, mobilisation; awareness raising and public human rights education. Human rights programming targeting specific groups, e.g. children, persons with disabilities, migrants, ethnic, religious, linguistic and sexual minorities, indigenous people and those suffering from caste discrimination, victims of trafficking, victims of torture. (Use code 15230 when in the context of a peacekeeping operation and code 15180 for ending violence against women and girls. Use code 15190 for human rights programming for refugees or migrants, including when they are victims of trafficking.Use code 16070 for Fundamental Principles and Rights at Work, i.e. Child Labour, Forced Labour, Non-discrimination in employment and occupation, Freedom of Association and Collective Bargaining.)	151
15161 (withdrawn)	Elections	Electoral assistance and monitoring, voters’ education [other than in connection with UN peace building (15230)].	151
15162 (withdrawn)	Human rights	Monitoring of human rights performance; support for national and regional human rights bodies; protection of ethnic, religious and cultural minorities [other than in connection with un peace building (15230)].	151
15163 (withdrawn)	Free flow of information	Uncensored flow of information on public issues, including activities that increase the professionalism, skills and integrity of the print and broadcast media (e.g. training of journalists).	151
15164 (withdrawn)	Women’s equality organisations and institutions	Support for institutions and organisations (governmental and non-governmental) working for gender equality and women’s empowerment.	151
15170	Women’s rights organisations and movements, and government institutions	Support for feminist, women-led and women’s rights organisations and movements, and institutions (governmental and non-govermental) at all levels to enhance their effectiveness, influence and substainability (activities and core-funding). These organisations exist to bring about transformative change for gender equality and/or the rights of women and girls in developing countries. Their activities include agenda-setting, advocacy, policy dialogue, capacity development, awareness raising and prevention, service provision, conflict-prevention and peacebuilding, research, organising, and alliance and network building	151
15180	Ending violence against women and girls	Support to programmes designed to prevent and eliminate all forms of violence against women and girls/gender-based violence. This encompasses a broad range of forms of physical, sexual and psychological violence including but not limited to: intimate partner violence (domestic violence); sexual violence; female genital mutilation/cutting (FGM/C); child, early and forced marriage; acid throwing; honour killings; and trafficking of women and girls. Prevention activities may include efforts to empower women and girls; change attitudes, norms and behaviour; adopt and enact legal reforms; and strengthen implementation of laws and policies on ending violence against women and girls, including through strengthening institutional capacity. Interventions to respond to violence against women and girls/gender-based violence may include expanding access to services including legal assistance, psychosocial counselling and health care; training personnel to respond more effectively to the needs of survivors; and ensuring investigation, prosecution and punishment of perpetrators of violence.	151
15185	Local government administration	Decentralisation processes (including political, administrative and fiscal dimensions); intergovernmental relations and federalism; strengthening local authorities.	151
15190	Facilitation of orderly, safe, regular and responsible migration and mobility	Assistance to developing countries that facilitates the orderly, safe, regular and responsible migration and mobility of people. This includes:• Capacity building in migration and mobility policy, analysis, planning and management. This includes support to facilitate safe and regular migration and address irregular migration, engagement with diaspora and programmes enhancing the development impact of remittances and/or their use for developmental projects in developing countries.• Measures to improve migrant labour recruitment systems in developing countries.• Capacity building for strategy and policy development as well as legal and judicial development (including border management) in developing countries. This includes support to address and reduce vulnerabilities in migration, and strengthen the transnational response to smuggling of migrants and preventing and combating trafficking in human beings.• Support to effective strategies to ensure international protection and the right to asylum.• Support to effective strategies to ensure access to justice and assistance for displaced persons.• Assistance to migrants for their safe, dignified, informed and voluntary return to their country of origin (covers only returns from another developing country; assistance to forced returns is excluded from ODA).• Assistance to migrants for their sustainable reintegration in their country of origin (use code 93010 for pre-departure assistance provided in donor countries in the context of voluntary returns). Activities that pursue first and foremost providers’ interest are excluded from ODA. Activities addressing the root causes of forced displacement and irregular migration should not be coded here, but under their relevant sector of intervention. In addition, use code 15136 for support to countries’ authorities for immigration affairs and services (optional), code 24050 for programmes aiming at reducing the sending costs of remittances, code 72010 for humanitarian aspects of assistance to refugees and internally displaced persons (IDPs) such as delivery of emergency services and humanitarian protection. Use code 93010 when expenditure is for the temporary sustenance of refugees in the donor country, including for their voluntary return and for their reintegration when support is provided in a donor country in connection with the return from that donor country (i.e. pre-departure assistance), or voluntary resettlement in a third developed country.	151
15196	Government and civil society statistics and data	Collection, production, management and dissemination of statistics and data related to Government & Civil Society. Includes macroeconomic statistics, government finance, fiscal and public sector statistics, support to development of administrative data infrastructure, civil society surveys.	151
15210	Security system management and reform	Technical co-operation provided to parliament, government ministries, law enforcement agencies and the judiciary to assist review and reform of the security system to improve democratic governance and civilian control; technical co-operation provided to government to improve civilian oversight and democratic control of budgeting, management, accountability and auditing of security expenditure, including military budgets, as part of a public expenditure management programme; assistance to civil society to enhance its competence and capacity to scrutinise the security system so that it is managed in accordance with democratic norms and principles of accountability, transparency and good governance. [Other than in the context of an international peacekeeping operation (15230)].	152
15220	Civilian peace-building, conflict prevention and resolution	Support for civilian activities related to peace building, conflict prevention and resolution, including capacity building, monitoring, dialogue and information exchange. Bilateral participation in international civilian peace missions such as those conducted by the UN Department of Political Affairs (UNDPA) or the European Union (European Security and Defence Policy), and contributions to civilian peace funds or commissions (e.g. Peacebuilding Commission, Peacebuilding thematic window of the MDG achievement fund etc.). The contributions can take the form of financing or provision of equipment or civilian or military personnel (e.g. for training civilians).(Use code 15230 for bilateral participation in international peacekeeping operations).	152
15230	Participation in international peacekeeping operations	Bilateral participation in peacekeeping operations mandated or authorised by the United Nations (UN) through Security Council resolutions, and conducted by international organisations, e.g. UN, NATO, the European Union (Security and Defence Policy security-related operations), or regional groupings of developing countries. Direct contributions to the UN Department for Peacekeeping Operations (UNDPKO) budget are excluded from bilateral ODA (they are reportable in part as multilateral ODA, see Annex 9). The activities that can be reported as bilateral ODA under this code are limited to: human rights and election monitoring; reintegration of demobilised soldiers; rehabilitation of basic national infrastructure; monitoring or retraining of civil administrators and police forces; security sector reform and other rule of law-related activities; training in customs and border control procedures; advice or training in fiscal or macroeconomic stabilisation policy; repatriation and demobilisation of armed factions, and disposal of their weapons; explosive mine removal. The enforcement aspects of international peacekeeping operations are not reportable as ODA. ODA-eligible bilateral participation in peacekeeping operations can take the form of financing or provision of equipment or military or civilian personnel (e.g. police officers). The reportable cost is calculated as the excess over what the personnel and equipment would have cost to maintain had they not been assigned to take part in a peace operation. Costs for military contingents participating in UNDPKO peacekeeping operations are not reportable as ODA. International peacekeeping operations may include humanitarian-type activities (contributions to the form of equipment or personnel), as described in codes 7xxxx. These should be included under code 15230 if they are an integrated part of the activities above, otherwise they should be reported as humanitarian aid. NB: When using this code, indicate the name of the operation in the short description of the activity reported.	152
15240	Reintegration and SALW control	Reintegration of demobilised military personnel into the economy; conversion of production facilities from military to civilian outputs; technical co-operation to control, prevent and/or reduce the proliferation of small arms and light weapons (SALW) – see para. 80 of the Directives for definition of SALW activities covered. [Other than in the context of an international peacekeeping operation (15230) or child soldiers (15261)].	152
15250	Removal of land mines and explosive remnants of war	All activities related to land mines and explosive remnants of war which have benefits to developing countries as their main objective, including removal of land mines and explosive remnants of war, and stockpile destruction for developmental purposes [other than in the context of an international peacekeeping operation (15230)]; risk education and awareness raising; rehabilitation, reintegration and assistance to victims, and research and development on demining and clearance. Only activities for civilian purposes are ODA-eligible.	152
15261	Child soldiers (prevention and demobilisation)	Technical co-operation provided to government – and assistance to civil society organisations – to support and apply legislation designed to prevent the recruitment of child soldiers, and to demobilise, disarm, reintegrate, repatriate and resettle (DDR) child soldiers.	152
16010	Social Protection	Social protection or social security strategies, legislation and administration; institution capacity building and advice; social security and other social schemes; support programmes, cash benefits, pensions and special programmes for older persons, orphans, persons with disabilities, children, mothers with newborns, those living in poverty, without jobs and other vulnerable groups; social dimensions of structural adjustment.	160
16011	Social protection and welfare services policy, planning and administration	Administration of overall social protection policies, plans, programmes and budgets including legislation, standards and statistics on social protection.	160
16012	Social security (excl pensions)	Social protection shemes in the form of cash or in-kind benefits to people unable to work due to sickness or injury.	160
16013	General pensions	Social protection schemes in the form of cash or in-kind benefits, including pensions, against the risks linked to old age.	160
16014	Civil service pensions	Pension schemes for government personnel.	160
16015	Social services (incl youth development and women+ children)	Social protection schemes in the form of cash or in-kind benefits to households with dependent children, including parental leave benefits.	160
16020	Employment creation	Employment policy and planning; institution capacity building and advice; employment creation and income generation programmes; including activities specifically designed for the needs of vulnerable groups.	160
16030	Housing policy and administrative management	Housing sector policy, planning and programmes; excluding low-cost housing and slum clearance (16040).	160
16040	Low-cost housing	Including slum clearance.	160
16050	Multisector aid for basic social services	Basic social services are defined to include basic education, basic health, basic nutrition, population/reproductive health and basic drinking water supply and basic sanitation.	160
16061	Culture and recreation	Including libraries and museums.	160
16062	Statistical capacity building	All statistical activities, such as data collection, processing, dissemination and analysis; support to development and management of official statistics including demographic, social, economic, environmental and multi-sectoral statistics; statistical quality frameworks; development of human and technological resources for statistics, investments in data innovation. Activities related to data and statistics in the sectors 120, 130 or 150 should preferably be coded under the voluntary purpose codes 12196, 13096 and 15196. Activities with the sole purpose of monitoring development co-operation activities, including if performed by third parties, should be coded under 91010 (Administrative costs).	160
16063	Narcotics control	In-country and customs controls including training of the police; educational programmes and awareness campaigns to restrict narcotics traffic and in-country distribution. ODA recording of narcotics control expenditures is limited to activities that focus on economic development and welfare including alternative development programmes and crop substitution (see 31165 and 43050). Activities by the donor country to interdict drug supplies destroy crops or train or finance military personnel in anti-narcotics activities are not reportable.	160
16064	Social mitigation of HIV/AIDS	Special programmes to address the consequences of HIV/AIDS, e.g. social, legal and economic assistance to people living with HIV/AIDS including food security and employment; support to vulnerable groups and children orphaned by HIV/AIDS; human rights of HIV/AIDS affected people.	160
16065	Recreation and sport		160
16066	Culture		160
16070	Labour rights	Advocacy for international labour standards, labour law, fundamental principles and rights at work (child labour, forced labour, non-discrimination in the workplace, freedom of association and collective bargaining); formalisation of informal work, occupational safety and health.	160
16080	Social dialogue	Capacity building and advice in support of social dialogue; support to social dialogue institutions, bodies and mechanisms; capacity building of workers’ and employers’ organisations.	160
21010	Transport policy and administrative management	Transport sector policy, planning and programmes; aid to transport ministries; institution capacity building and advice; unspecified transport; activities that combine road, rail, water and/or air transport. Includes prevention of road accidents. Whenever possible, report transport of goods under the sector of the good being transported.	210
21011	Transport policy, planning and administration	Administration of affairs and services concerning transport systems.	210
21012	Public transport services	Administration of affairs and services concerning public transport.	210
21013	Transport regulation	Supervision and regulation of users, operations, construction and maintenance of transport systems (registration, licensing, inspection of equipment, operator skills and training; safety standards, franchises, tariffs, levels of service, etc.).	210
21020	Road transport	Road infrastructure, road vehicles; passenger road transport, motor passenger cars.	210
21021	Feeder road construction	Construction or operation of feeder road transport systems and facilities.	210
21022	Feeder road maintenance	Maintenance of feeder road transport systems and facilities.	210
21023	National road construction	Construction or operation of national road transport systems and facilities.	210
21024	National road maintenance	Maintenance of national road transport systems and facilities.	210
21030	Rail transport	Rail infrastructure, rail equipment, locomotives, other rolling stock; including light rail (tram) and underground systems.	210
21040	Water transport	Harbours and docks, harbour guidance systems, ships and boats; river and other inland water transport, inland barges and vessels.	210
21050	Air transport	Airports, airport guidance systems, aeroplanes, aeroplane maintenance equipment.	210
21061	Storage	Whether or not related to transportation. Whenever possible, report storage projects under the sector of the resource being stored.	210
21081	Education and training in transport and storage		210
22010	Communications policy and administrative management	Communications sector policy, planning and programmes; institution capacity building and advice; including postal services development; unspecified communications activities.	220
22011	Communications policy, planning and administration		220
22012	Postal services	Development and operation of postal services.	220
22013	Information services	Provision of information services.	220
22020	Telecommunications	Telephone networks, telecommunication satellites, earth stations.	220
22030	Radio/television/print media	Radio and TV links, equipment; newspapers; printing and publishing.	220
22040	Information and communication technology (ICT)	Computer hardware and software; internet access; IT training. When sector cannot be specified.	220
23010 (withdrawn)	Energy policy and administrative management	Energy sector policy, planning and programmes; aid to energy ministries; institution capacity building and advice; unspecified energy activities including energy conservation.	230
23020 (withdrawn)	Power generation/non-renewable sources	Thermal power plants including when heat source cannot be determined; combined gas-coal power plants.	230
23030 (withdrawn)	Power generation/renewable sources	Including policy, planning, development programmes, surveys and incentives. Fuelwood/ charcoal production should be included under forestry (31261).	230
23040 (withdrawn)	Electrical transmission/ distribution	Distribution from power source to end user; transmission lines.	230
23050 (withdrawn)	Gas distribution	Delivery for use by ultimate consumer.	230
23061 (withdrawn)	Oil-fired power plants	Including diesel power plants.	230
23062 (withdrawn)	Gas-fired power plants		230
23063 (withdrawn)	Coal-fired power plants		230
23064 (withdrawn)	Nuclear power plants	Including nuclear safety.	230
23065 (withdrawn)	Hydro-electric power plants	Including power-generating river barges.	230
23066 (withdrawn)	Geothermal energy		230
23067 (withdrawn)	Solar energy	Including photo-voltaic cells, solar thermal applications and solar heating.	230
23068 (withdrawn)	Wind power	Wind energy for water lifting and electric power generation.	230
23069 (withdrawn)	Ocean power	Including ocean thermal energy conversion, tidal and wave power.	230
23070 (withdrawn)	Biomass	Densification technologies and use of biomass for direct power generation including biogas, gas obtained from sugar cane and other plant residues, anaerobic digesters.	230
23081 (withdrawn)	Energy education/training	Applies to all energy sub-sectors; all levels of training.	230
23082 (withdrawn)	Energy research	Including general inventories, surveys.	230
23110	Energy policy and administrative management	Energy sector policy, planning; aid to energy ministries and other governmental or nongovernmental institutions for activities related to the SDG7; institution capacity building and advice; tariffs, market building, unspecified energy activities; energy activities for which a more specific code cannot be assigned.	231
23111	Energy sector policy, planning and administration		231
23112	Energy regulation	Regulation of the energy sector, including wholesale and retail electricity provision.	231
23181	Energy education/training	All levels of training not included elsewhere.	231
23182	Energy research	Including general inventories, surveys.	231
23183	Energy conservation and demand-side efficiency	Support for energy demand reduction, e.g. building and industry upgrades, smart grids, metering and tariffs. For clean cooking appliances use code 32174.	231
23210	Energy generation, renewable sources - multiple technologies	Renewable energy generation programmes that cannot be attributed to one single technology (codes 23220 through 23280 below). Fuelwood/charcoal production should be included under forestry 31261.	232
23220	Hydro-electric power plants	Including energy generating river barges.	232
23230	Solar energy for centralised grids	Including photo-voltaic cells, concentrated solar power systems connected to the main grid and net-metered decentralised solutions.	232
23231	Solar energy for isolated grids and standalone systems	Solar power generation for isolated mini-grids, solar home systems (including integrated wiring and related appliances), solar lanterns distribution and commercialisation. This code refers to the power generation component only.	232
23232	Solar energy - thermal applications	Solar solutions for indoor space and water heating (except for solar cook stoves 32174).	232
23240	Wind energy	Wind energy for water lifting and electric power generation.	232
23250	Marine energy	Including ocean thermal energy conversion, tidal and wave power.	232
23260	Geothermal energy	Use of geothermal energy for generating electric power or directly as heat for agriculture, etc.	232
23270	Biofuel-fired power plants	Use of solids and liquids produced from biomass for direct power generation. Also includes biogases from anaerobic fermentation (e.g. landfill gas, sewage sludge gas, fermentation of energy crops and manure) and thermal processes (also known as syngas); waste-fired power plants making use of biodegradable municipal waste (household waste and waste from companies and public services that resembles household waste, collected at installations specifically designed for their disposal with recovery of combustible liquids, gases or heat). See code 23360 for non-renewable waste-fired power plants.	232
23310	Energy generation, non-renewable sources, unspecified	Thermal power plants including when energy source cannot be determined; combined gas-coal power plants.	233
23320	Coal-fired electric power plants	Thermal electric power plants that use coal as the energy source.	233
23330	Oil-fired electric power plants	Thermal electric power plants that use fuel oil or diesel fuel as the energy source.	233
23340	Natural gas-fired electric power plants	Electric power plants that are fuelled by natural gas; related feed-in infrastructure (LNG terminals, gasifiers, pipelines to feed the plant).	233
23350	Fossil fuel electric power plants with carbon capture and storage (CCS)	Fossil fuel electric power plants employing technologies to capture carbon dioxide emissions. CCS not related to power plants should be included under 41020. CCS activities are not reportable as ODA.	233
23360	Non-renewable waste-fired electric power plants	Electric power plants that use non-biodegradable industrial and municipal waste as the energy source.	233
23410	Hybrid energy electric power plants	Electric power plants that make use of both non-renewable and renewable energy sources.	234
23510	Nuclear energy electric power plants and nuclear safety	See note regarding ODA eligibility of nuclear energy.	235
23610	Heat plants	Power plants which are designed to produce heat only.	236
23620	District heating and cooling	Distribution of heat generated in a centralised location, or delivery of chilled water, for residential and commercial heating or cooling purposes.	236
23630	Electric power transmission and distribution (centralised grids)	Grid distribution from power source to end user; transmission lines. Also includes storage of energy to generate power (e.g. pumped hydro, batteries) and the extension of grid access, often to rural areas.	236
23631	Electric power transmission and distribution (isolated mini-grids)	Includes village grids and other electricity distribution technologies to end users that are not connected to the main national grid. Also includes related electricity storage. This code refers to the network infrastructure only regardless of the power generation technologies.	236
23640	Retail gas distribution	Includes urban infrastructure for the delivery of urban gas and LPG cylinder production, distribution and refill. Excludes gas distribution for purposes of electricity generation (23340) and pipelines (32262).	236
23641	Retail distribution of liquid or solid fossil fuels		236
23642	Electric mobility infrastructures	Includes electricity or hydrogen recharging stations for private and public transport systems and related infrastructure (except for rail transport 21030).	236
24010	Financial policy and administrative management	Finance sector policy, planning and programmes; institution capacity building and advice; financial markets and systems.	240
24020	Monetary institutions	Central banks.	240
24030	Formal sector financial intermediaries	All formal sector financial intermediaries; credit lines; insurance, leasing, venture capital, etc. (except when focused on only one sector).	240
24040	Informal/semi-formal financial intermediaries	Micro credit, savings and credit co-operatives etc.	240
24050	Remittance facilitation, promotion and optimisation	Includes programmes aiming at reducing the sending costs of remittances.	240
24081	Education/training in banking and financial services		240
25010	Business policy and administration	Public sector policies and institution support to the business environment and investment climate, including business regulations, property rights, non-discrimination, investment promotion, competition policy, enterprises law, private-public partnerships.	250
25020	Privatisation	When sector cannot be specified. Including general state enterprise restructuring or demonopolisation programmes; planning, programming, advice.	250
25030	Business development services	Public and private provision of business development services, e.g. incubators, business strategies, commercial linkages programmes and matchmaking services. Includes support to private organisations representing businesses, e.g. business associations; chambers of commerce; producer associations; providers of know-how and other business development services. For financial services use CRS codes 24030 or 24040. For SME development and for support to companies in the industrial sector use codes 32130 through 32172. For support to companies in the agricultural sector use code 31120.	250
25040	Responsible business conduct	Support to policy reform, implementation and enforcement of responsible business conduct (RBC) principles and standards as well as facilitation of responsible business practices by companies. Includes establishing and enforcing a legal and regulatory framework to protect stakeholder rights and the environment, rewarding best performers; exemplifying RBC in government economic activities, such as state-owned enterprises’ operations or public procurement; support to the implementation of the OECD Guidelines for MNEs, including disclosure, human rights, employment and industrial relations, environment, combating bribery, consumer interests, science and technology, competition and taxation.	250
31110	Agricultural policy and administrative management	Agricultural sector policy, planning and programmes; aid to agricultural ministries; institution capacity building and advice; unspecified agriculture.	311
31120	Agricultural development	Integrated projects; farm development.	311
31130	Agricultural land resources	Including soil degradation control; soil improvement; drainage of water logged areas; soil desalination; agricultural land surveys; land reclamation; erosion control, desertification control.	311
31140	Agricultural water resources	Irrigation, reservoirs, hydraulic structures, ground water exploitation for agricultural use.	311
31150	Agricultural inputs	Supply of seeds, fertilizers, agricultural machinery/equipment.	311
31161	Food crop production	Including grains (wheat, rice, barley, maize, rye, oats, millet, sorghum); horticulture; vegetables; fruit and berries; other annual and perennial crops. [Use code 32161 for agro-industries.]	311
31162	Industrial crops/export crops	Including sugar; coffee, cocoa, tea; oil seeds, nuts, kernels; fibre crops; tobacco; rubber. [Use code 32161 for agro-industries.]	311
31163	Livestock	Animal husbandry; animal feed aid.	311
31164	Agrarian reform	Including agricultural sector adjustment.	311
31165	Agricultural alternative development	Projects to reduce illicit drug cultivation through other agricultural marketing and production opportunities (see code 43050 for non-agricultural alternative development).	311
31166	Agricultural extension	Non-formal training in agriculture.	311
31181	Agricultural education/training		311
31182	Agricultural research	Plant breeding, physiology, genetic resources, ecology, taxonomy, disease control, agricultural bio-technology; including livestock research (animal health, breeding and genetics, nutrition, physiology).	311
31191	Agricultural services	Marketing policies & organisation; storage and transportation, creation of strategic reserves.	311
31192	Plant and post-harvest protection and pest control	Including integrated plant protection, biological plant protection activities, supply and management of agrochemicals, supply of pesticides, plant protection policy and legislation.	311
31193	Agricultural financial services	Financial intermediaries for the agricultural sector including credit schemes; crop insurance.	311
31194	Agricultural co-operatives	Including farmers’ organisations.	311
31195	Livestock/veterinary services	Animal health and management, genetic resources, feed resources.	311
31210	Forestry policy and administrative management	Forestry sector policy, planning and programmes; institution capacity building and advice; forest surveys; unspecified forestry and agro-forestry activities.	312
31220	Forestry development	Afforestation for industrial and rural consumption; exploitation and utilisation; erosion control, desertification control; integrated forestry projects.	312
31261	Fuelwood/charcoal	Sustainable forestry development whose primary purpose is production of fuelwood and charcoal. Further transformation of biomass in biofuels is coded under 32173.	312
31281	Forestry education/training		312
31282	Forestry research	Including artificial regeneration, genetic improvement, production methods, fertilizer, harvesting.	312
31291	Forestry services		312
31310	Fishing policy and administrative management	Fishing sector policy, planning and programmes; institution capacity building and advice; ocean and coastal fishing; marine and freshwater fish surveys and prospecting; fishing boats/equipment; unspecified fishing activities.	313
31320	Fishery development	Exploitation and utilisation of fisheries; fish stock protection; aquaculture; integrated fishery projects.	313
31381	Fishery education/training		313
31382	Fishery research	Pilot fish culture; marine/freshwater biological research.	313
31391	Fishery services	Fishing harbours; fish markets; fishery transport and cold storage.	313
32110	Industrial policy and administrative management	Industrial sector policy, planning and programmes; institution capacity building and advice; unspecified industrial activities; manufacturing of goods not specified below.	321
32120	Industrial development		321
32130	Small and medium-sized enterprises (SME) development	Direct support to improve the productive capacity and business management of micro, small and medium-sized enterprises in the industrial sector, including accounting, auditing, advisory services, technological transfer and skill upgrading. For business policy and institutional support use code 25010. For business development services through business intermediary organisations (e.g. business associations; chambers of commerce; producer associations; incubators; providers of know-how and other business development services) use CRS code 250xx. For farm and agricultural development use code 31120.	321
32140	Cottage industries and handicraft		321
32161	Agro-industries	Staple food processing, dairy products, slaughter houses and equipment, meat and fish processing and preserving, oils/fats, sugar refineries, beverages/tobacco, animal feeds production.	321
32162	Forest industries	Wood production, pulp/paper production.	321
32163	Textiles, leather and substitutes	Including knitting factories.	321
32164	Chemicals	Industrial and non-industrial production facilities; includes pesticides production.	321
32165	Fertilizer plants		321
32166	Cement/lime/plaster		321
32167	Energy manufacturing (fossil fuels)	Including gas liquefaction; petroleum refineries, wholesale distribution of fossil fuels. (Use 23640 for retail distribution of gas and 23641 for retail distribution of liquid or solid fossil fuels.)	321
32168	Pharmaceutical production	Medical equipment/supplies; drugs, medicines, vaccines; hygienic products.	321
32169	Basic metal industries	Iron and steel, structural metal production.	321
32170	Non-ferrous metal industries		321
32171	Engineering	Manufacturing of electrical and non-electrical machinery, engines/turbines.	321
32172	Transport equipment industry	Shipbuilding, fishing boats building; railroad equipment; motor vehicles and motor passenger cars; aircraft; navigation/guidance systems.	321
32173	Modern biofuels manufacturing	Includes biogas, liquid biofuels and pellets for domestic and non-domestic use. Excludes raw fuelwood and charcoal (31261).	321
32174	Clean cooking appliances manufacturing	Includes manufacturing and distribution of efficient biomass cooking stoves, gasifiers, liquid biofuels stoves, solar stoves, gas and biogas stoves, electric stoves.	321
32182	Technological research and development	Including industrial standards; quality management; metrology; testing; accreditation; certification.	321
32210	Mineral/mining policy and administrative management	Mineral and mining sector policy, planning and programmes; mining legislation, mining cadastre, mineral resources inventory, information systems, institution capacity building and advice; unspecified mineral resources exploitation.	322
32220	Mineral prospection and exploration	Geology, geophysics, geochemistry; excluding hydrogeology (14010) and environmental geology (41010), mineral extraction and processing, infrastructure, technology, economics, safety and environment management.	322
32261	Coal	Including lignite and peat.	322
32262	Oil and gas (upstream)	Petroleum, natural gas, condensates, liquefied petroleum gas (LPG), liquefied natural gas (LNG); including drilling and production, oil and gas pipelines.	322
32263	Ferrous metals	Iron and ferro-alloy metals.	322
32264	Nonferrous metals	Aluminium, copper, lead, nickel, tin, zinc.	322
32265	Precious metals/materials	Gold, silver, platinum, diamonds, gemstones.	322
32266	Industrial minerals	Baryte, limestone, feldspar, kaolin, sand, gypsym, gravel, ornamental stones.	322
32267	Fertilizer minerals	Phosphates, potash.	322
32268	Offshore minerals	Polymetallic nodules, phosphorites, marine placer deposits.	322
32310	Construction policy and administrative management	Construction sector policy and planning; excluding construction activities within specific sectors (e.g., hospital or school construction).	323
33110	Trade policy and administrative management	Trade policy and planning; support to ministries and departments responsible for trade policy; trade-related legislation and regulatory reforms; policy analysis and implementation of multilateral trade agreements e.g. technical barriers to trade and sanitary and phytosanitary measures (TBT/SPS) except at regional level (see 33130); mainstreaming trade in national development strategies (e.g. poverty reduction strategy papers); wholesale/retail trade; unspecified trade and trade promotion activities.	331
33120	Trade facilitation	Simplification and harmonisation of international import and export procedures (e.g. customs valuation, licensing procedures, transport formalities, payments, insurance); support to customs departments and other border agencies, including in particular implementation of the provisions of the WTO Trade Facilitation Agreement; tariff reforms.	331
33130	Regional trade agreements (RTAs)	Support to regional trade arrangements [e.g. Southern African Development Community (SADC), Association of Southeast Asian Nations (ASEAN), Free Trade Area of the Americas (FTAA), African Caribbean Pacific/European Union (ACP/EU)], including work on technical barriers to trade and sanitary and phytosanitary measures (TBT/SPS) at regional level; elaboration of rules of origin and introduction of special and differential treatment in RTAs.	331
33140	Multilateral trade negotiations	Support developing countries’ effective participation in multilateral trade negotiations, including training of negotiators, assessing impacts of negotiations; accession to the World Trade Organisation (WTO) and other multilateral trade-related organisations.	331
33150	Trade-related adjustment	Contributions to the government budget to assist the implementation of recipients’ own trade reforms and adjustments to trade policy measures by other countries; assistance to manage shortfalls in the balance of payments due to changes in the world trading environment.	331
33181	Trade education/training	Human resources development in trade not included under any of the above codes. Includes university programmes in trade.	331
33210	Tourism policy and administrative management		332
41010	Environmental policy and administrative management	Environmental policy, laws, regulations and economic instruments; administrational institutions and practices; environmental and land use planning and decision-making procedures; seminars, meetings; miscellaneous conservation and protection measures not specified below.	410
41020	Biosphere protection	Air pollution control, ozone layer preservation; marine pollution control.	410
41030	Biodiversity	Including natural reserves and actions in the surrounding areas; other measures to protect endangered or vulnerable species and their habitats (e.g. wetlands preservation).	410
41040	Site preservation	Applies to unique cultural landscape; including sites/objects of historical, archeological, aesthetic, scientific or educational value.	410
41050 (withdrawn)	Flood prevention/control	Floods from rivers or the sea; including sea water intrusion control and sea level rise related activities.	410
41081	Environmental education/training		410
41082	Environmental research	Including establishment of databases, inventories/accounts of physical and natural resources; environmental profiles and impact studies if not sector specific.	410
43010	Multisector aid		430
43030	Urban development and management	Integrated urban development projects; local development and urban management; urban infrastructure and services; municipal finances; urban environmental management; urban development and planning; urban renewal and urban housing; land information systems.	430
43031	Urban land policy and management	Urban development and planning; urban management, land information systems.	430
43032	Urban development	Integrated urban development projects; local development; urban infrastructure and services; municipal finances; urban environment systems; urban renewal and urban housing.	430
43040	Rural development	Integrated rural development projects; e.g. regional development planning; promotion of decentralised and multi-sectoral competence for planning, co-ordination and management; implementation of regional development and measures (including natural reserve management); land management; land use planning; land settlement and resettlement activities [excluding resettlement of refugees and internally displaced persons (72010)]; functional integration of rural and urban areas; geographical information systems.	430
43041	Rural land policy and management	Regional development planning; promotion of decentralised and multi-sectoral competence for planning, co-ordination and management; land management; land use planning; geographical information systems.	430
43042	Rural development	Integrated rural development projects; implementation of regional development and measures (including natural reserve management); land settlement and resettlement activities [excluding resettlement of refugees and internally displaced persons (72010)]; functional integration of rural and urban areas.	430
43050	Non-agricultural alternative development	Projects to reduce illicit drug cultivation through, for example, non-agricultural income opportunities, social and physical infrastructure (see code 31165 for agricultural alternative development).	430
43060	Disaster Risk Reduction	Disaster risk reduction activities if not sector specific. Comprises risk assessments, structural prevention measures (e.g. flood prevention infrastructure), preparedness measures (e.g. early warning systems) normative prevention measures (e.g. building codes, land-use planning), and risk transfer systems (e.g. insurance schemes, risk funds). Also includes building local and national capacities and supporting the establishment of efficient and sustainable national structures able to promote disaster risk reduction.	430
43071	Food security policy and administrative management	Food security policy, programmes and activities; institution capacity strengthening; policies, programmes for the reduction of food loss/waste; food security information systems, data collection, statistics, analysis, tools, methods; coordination and governance mechanisms; other unspecified food security activities.	430
43072	Household food security programmes	Short or longer term household food security programmes and activities that improve the access of households to nutritionally adequate diets (excluding any cash transfers within broader social welfare programmes that do not have a specific food security, food acquisition or nutrition focus which should be reported under code 16010).	430
43073	Food safety and quality	Food safety and quality policies, programmes and activities, including food inspection and certification; strengthening food safety/quality capacities and development of standards along the value chain; monitoring/surveillance and laboratory capacities; and delivery of information, communication, education.	430
43081	Multisector education/training	Including scholarships.	430
43082	Research/scientific institutions	When sector cannot be identified.	430
51010	General budget support-related aid	Unearmarked contributions to the government budget; support for the implementation of macroeconomic reforms (structural adjustment programmes, poverty reduction strategies); general programme assistance (when not allocable by sector).	510
52010	Food assistance	Supply of edible human food under national or international programmes including transport costs, cash payments made for food supplies; project food assistance aid and food assistance aid for market sales when benefiting sector not specified. Excludes food security policy and administrative management (43071), household food security programmes (43072) and emergency food assistance aid (72040). Report as multilateral: i) food assistance aid by EU financed out of its budget and allocated pro rata to EU member countries; and ii) core contributions to the World Food Programme.	520
53030	Import support (capital goods)	Capital goods and services; lines of credit.	530
53040	Import support (commodities)	Commodities, general goods and services, oil imports.	530
60010	Action relating to debt	Actions falling outside the code headings below.	600
60020	Debt forgiveness		600
60030	Relief of multilateral debt	Grants or credits to cover debt owed to multilateral financial institutions; including contributions to Heavily Indebted Poor Countries (HIPC) Trust Fund.	600
60040	Rescheduling and refinancing		600
60061	Debt for development swap	Allocation of debt claims to use for development (e.g., debt for education, debt for environment).	600
60062	Other debt swap	Where the debt swap benefits an external agent i.e. is not specifically for development purposes.	600
60063	Debt buy-back	Purchase of debt for the purpose of cancellation.	600
72010	Material relief assistance and services	Shelter, water, sanitation, education, health services including supply of medicines and malnutrition management, including medical nutrition management; supply of other nonfood relief items (including cash and voucher delivery modalities) for the benefit of crisisaffected people, including refugees and internally displaced people in developing countries, Includes assistance delivered by or coordinated by international civil protection units in the immediate aftermath of a disaster (in-kind assistance, deployment of specially-equipped teams, logistics and transportation, or assessment and coordination by experts sent to the field). Also includes measures to promote and protect the safety, well-being, dignity and integrity of crisis-affected people including refugees and internally displaced persons in developing countries. (Activities designed to protect the security of persons or properties through the use or display of force are not reportable as ODA.)	720
72011	Basic Health Care Services in Emergencies	Provision of health services (basic health services, mental health, sexual and reproductive health), medical nutritional intervention (therapeutic feeding and medical interventions for treating malnutrition) and supply of medicines for the benefit of affected people. Excludes supplemental feeding (72040).	720
72012	Education in emergencies	Support for education facilities (including restoring pre-existing essential infrastructure and school facilities), teaching, training and learning materials (including digital technologies, as appropriate) and immediate access to quality basic and primary education (including formal and non-formal education), and secondary education (including vocational training and secondary level technical education) in emergencies for the benefit of affected children and youth, particularly targeting girls and women and refugees, life skills for youth and adults, and vocational training for youth and adults	720
72040	Emergency food assistance	Provision and distribution of food; cash and vouchers for the purchase of food; non-medical nutritional interventions for the benefit of crisis-affected people, including refugees and internally displaced people in developing countries in emergency situations. Includes logistical costs. Excludes non-emergency food assistance (52010), food security policy and administrative management (43071), household food programmes (43072) and medical nutrition interventions (therapeutic feeding) (72010 and 72011).	720
72050	Relief co-ordination and support services	Measures to co-ordinate the assessment and safe delivery of humanitarian aid, including logistic, transport and communication systems; direct financial or technical support to national governments of affected countries to manage a disaster situation; activities to build an evidence base for humanitarian financing and operations, sharing this information and developing standards and guidelines for more effective response; funding for identifying and sharing innovative and scalable solutions to deliver effective humanitarian assistance.	720
73010	Immediate post-emergency reconstruction and rehabilitation	Social and economic rehabilitation in the aftermath of emergencies to facilitate recovery and resilience building and enable populations to restore their livelihoods in the wake of an emergency situation (e.g. trauma counselling and treatment, employment programmes). Includes infrastructure necessary for the delivery of humanitarian aid; restoring pre-existing essential infrastructure and facilities (e.g. water and sanitation, shelter, health care services, education); rehabilitation of basic agricultural inputs and livestock. Excludes longer-term reconstruction (‘build back better’) which is reportable against relevant sectors.	730
74010 (withdrawn)	Disaster prevention and preparedness	Disaster risk reduction activities (e.g. developing knowledge, natural risks cartography, legal norms for construction); early warning systems; emergency contingency stocks and contingency planning including preparations for forced displacement.	740
74020	Multi-hazard response preparedness	Building the responsiveness, capability and capacity of international, regional and national humanitarian actors to disasters. Support to the institutional capacities of national and local government, specialised humanitarian bodies, and civil society organisations to anticipate, respond and recover from the impact of potential, imminent and current hazardous events and emergency situations that pose humanitarian threats and could call for a humanitarian response. This includes risk analysis and assessment, mitigation, preparedness, such as stockpiling of emergency items and training and capacity building aimed to increase the speed and effectiveness of lifesaving assistance delivered in the occurrence of crisis.	740
91010	Administrative costs (non-sector allocable)		910
92010 (withdrawn)	Support to national NGOs	In the donor country.	920
92020 (withdrawn)	Support to international NGOs		920
92030 (withdrawn)	Support to local and regional NGOs	In the recipient country or region.	920
93010	Refugees/asylum seekers in donor countries (non-sector allocable)	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months, when costs cannot be disaggregated. See section II.6 and Annex 17.	930
93011	Refugees/asylum seekers in donor countries - food and shelter	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months – food and shelter: - Food and other essential temporary sustenance provisions such as clothing. - Temporary accommodation facilities (e.g. reception centres, containers, tent camps). In respect of buildings, only the costs of maintenance and upkeep may be reported as ODA. The cost of renting temporary accommodation facilities is eligible. (All construction costs are excluded).	930
93012	Refugees/asylum seekers in donor countries - training	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months – training: - Early childhood education, primary and secondary education for children (this includes school costs but excludes vocational training), as part of temporary sustenance. - Language training and other ad-hoc basic training for refugees e.g. basic life skills for youth and adults (literacy and numeracy training).	930
93013	Refugees/asylum seekers in donor countries - health	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months: basic health care and psycho-social support for persons with specific needs e.g. unaccompanied minors, persons with disabilities, survivors of violence and torture.	930
93014	Refugees/asylum seekers in donor countries - other temporary sustenance	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months: temporary sustenance other than food and shelter (code 93011), training (93012) and health (93013), i.e. cash ‘pocket money’ to cover subsistence costs and assistance in the asylum procedure: translation of documents, legal and administrative counselling, interpretation services.	930
93015	Refugees/asylum seekers in donor countries - voluntary repatriation	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months: voluntary repatriation of refugees to a developing country during first twelve months.	930
93016	Refugees/asylum seekers in donor countries - transport	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months: transport to the host country in the case of resettlement programmes and transport within the host country.	930
93017	Refugees/asylum seekers in donor countries - rescue at sea	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months: rescue of refugees at sea when it is the main purpose of the operation. Only the additional costs related to the operation may be counted.	930
93018	Refugees/asylum seekers in donor countries - administrative costs	Costs incurred in donor countries for basic assistance to asylum seekers and refugees from developing countries, up to 12 months: administrative costs. Only overhead costs attached to the direct provision of temporary sustenance to refugees are eligible. This includes costs of personnel assigned to provide eligible services to refugees, but does not include costs of personnel who are not involved in the direct execution of these services, e.g. management, human resources, information technology.	930
99810	Sectors not specified	Contributions to general development of the recipient should be included under programme assistance (51010).	998
99820	Promotion of development awareness (non-sector allocable)	Spending in donor country for heightened awareness/interest in development co-operation (brochures, lectures, special research projects, etc.).	998

DAC 3 Digit Sector

External URL: http://www.oecd.org/dac/stats/dacandcrscodelists.htm

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/sector/@code

• iati-activities/iati-activity/transaction/sector/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
111	Education, Level Unspecified	The codes in this category are to be used only when level of education is unspecified or unknown (e.g. training of primary school teachers should be coded under 11220).
112	Basic Education
113	Secondary Education
114	Post-Secondary Education
121	Health, General
122	Basic Health
123	Non-communicable diseases (NCDs)
130	Population Policies/Programmes & Reproductive Health
140	Water Supply & Sanitation
151	Government & Civil Society-general	N.B. Use code 51010 for general budget support.
152	Conflict, Peace & Security	N.B. Further notes on ODA eligibility (and exclusions) of conflict, peace and security related activities are given in paragraphs 76-81 of the Directives.
160	Other Social Infrastructure & Services
210	Transport & Storage	Note: Manufacturing of transport equipment should be included under code 32172.
220	Communications
230 (withdrawn)	ENERGY GENERATION AND SUPPLY	Energy sector policy, planning and programmes; aid to energy ministries; institution capacity building and advice; unspecified energy activities including energy conservation.
231	Energy Policy
232	Energy generation, renewable sources
233	Energy generation, non-renewable sources
234	Hybrid energy plants
235	Nuclear energy plants
236	Energy distribution
240	Banking & Financial Services
250	Business & Other Services
311	Agriculture
312	Forestry
313	Fishing
321	Industry
322	Mineral Resources & Mining
323	Construction
331	Trade Policies & Regulations
332	Tourism
410	General Environment Protection	Covers activities concerned with conservation, protection or amelioration of the physical environment without sector allocation.
430	Other Multisector
510	General Budget Support	Budget support in the form of sector-wide approaches (SWAps) should be included in the respective sectors.
520	Development Food Assistance
530	Other Commodity Assistance	Non-food commodity assistance (when benefiting sector not specified).
600	Action Relating to Debt
720	Emergency Response	An emergency is a situation which results from man made crises and/or natural disasters.
730	Reconstruction Relief & Rehabilitation	This relates to activities during and in the aftermath of an emergency situation. Longer-term activities to improve the level of infrastructure or social services should be reported under the relevant economic and social sector codes. See also guideline on distinguishing humanitarian from sector-allocable aid.
740	Disaster Prevention & Preparedness	See code 43060 for disaster risk reduction.
910	Administrative Costs of Donors
920 (withdrawn)	SUPPORT TO NON- GOVERNMENTAL ORGANISATIONS (NGOs)	In the donor country.
930	Refugees in Donor Countries
998	Unallocated / Unspecified	Contributions to general development of the recipient should be included under programme assistance (51010).

Sector Vocabulary

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/sector/@vocabulary

• iati-activities/iati-activity/transaction/sector/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1	OECD DAC CRS Purpose Codes (5 digit)	The sector reported corresponds to an OECD DAC CRS 5-digit purpose code	http://reference.iatistandard.org/codelists/Sector/
2	OECD DAC CRS Purpose Codes (3 digit)	The sector reported corresponds to an OECD DAC CRS 3-digit purpose code	http://reference.iatistandard.org/codelists/SectorCategory/
3	Classification of the Functions of Government (UN)	The sector reported corresponds to the UN Classification of the Functions of Government (CoFoG)	http://unstats.un.org/unsd/cr/registry/regcst.asp?Cl=4
4	Statistical classification of economic activities in the European Community	The sector reported corresponds to the statistical classifications of economic activities in the European Community	http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NACE_REV2&StrLanguageCode=EN
5	National Taxonomy for Exempt Entities (USA)	The sector reported corresponds to the National Taxonomy for Exempt Entities (NTEE) - USA	https://nccs.urban.org/publication/irs-activity-codes
6	AidData	The sector reported corresponds to AidData classifications
7	SDG Goal	A value from the top-level list of UN sustainable development goals (SDGs) (e.g. ‘1’)	http://reference.iatistandard.org/codelists/unsdg-goals
8	SDG Target	A value from the second-level list of UN sustainable development goals (SDGs) (e.g. ‘1.1’)	http://reference.iatistandard.org/codelists/unsdg-targets
9	SDG Indicator	A value from the second-level list of UN sustainable development (SDG) indicators	http://unstats.un.org/sdgs/indicators/indicators-list/
10	Humanitarian Global Clusters (Inter-Agency Standing Committee)	The sector reported corresponds to an Inter-Agency Standard Committee Humanitarian Global Cluster code	https://data.humdata.org/dataset/global-coordination-groups-beta
11	North American Industry Classification System (NAICS)	The sector reported corresponds to the NAICS codelist	https://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2017
12	UN System Function	The sector reported corresponds to the UN System Function codelist	https://unsceb.org/sites/default/files/2021-04/UN_DataStandards_Digital_20210420.pdf
99	Reporting Organisation	The sector reported corresponds to a sector vocabulary maintained by the reporting organisation for this activity
98	Reporting Organisation 2	The sector reported corresponds to a sector vocabulary maintained by the reporting organisation for this activity (if they are referencing more than one)

Changelog

2.01

The SectorVocabulary codelist was added, with the Vocabulary codelist being split.

Tag Vocabulary

The Tag Vocabulary codelist defines external codelists which themselves provide codes and descriptions for tag elements.

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/tag/@vocabulary

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1	Agrovoc	A controlled vocabulary covering all areas of interest of the Food and Agriculture Organization (FAO) of the United Nations, including food, nutrition, agriculture, fisheries, forestry, environment etc.	http://agrovoc.uniroma2.it/agrovoc/agrovoc/en/
2	UN Sustainable Development Goals (SDG)	A value from the top-level list of UN sustainable development goals (SDGs) (e.g. ‘1’)	http://reference.iatistandard.org/codelists/UNSDG-Goals/
3	UN Sustainable Development Goals (SDG) Targets	A value from the second-level list of UN sustainable development goals (SDGs) (e.g. ‘1.1’)	http://reference.iatistandard.org/codelists/UNSDG-Targets/
99	Reporting Organisation

Tied Status

This is a Non-Core codelist.

Use this codelist for

• iati-activities/iati-activity/default-tied-status/@code

• iati-activities/iati-activity/transaction/tied-status/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
3	Partially tied	Official Development Assistance for which the associated goods and services must be procured from a restricted number of countries, which must however include substantially all aid recipient countries and can include the donor country.
4	Tied	Official grants or loans where procurement of the goods or services involved is limited to the donor country or to a group of countries which does not include substantially all aid recipient countries.
5	Untied	Untied aid is defined as loans and grants whose proceeds are fully and freely available to finance procurement from all OECD countries and substantially all developing countries.

Transaction Type

This is a Core codelist.

Use this codelist for

• iati-activities/iati-activity/transaction/transaction-type/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Incoming Funds	Funds recieved for use on the activity, which can be from an external or internal source.
2	Outgoing Commitment	A firm, written obligation from a donor or provider to provide a specified amount of funds, under particular terms and conditions, for specific purposes, for the benefit of the recipient.
3	Disbursement	Outgoing funds that are placed at the disposal of a recipient government or organisation, or funds transferred between two separately reported activities.
4	Expenditure	Outgoing funds that are spent on goods and services for the activity.
5	Interest Payment	The actual amount of interest paid on a loan or line of credit, including fees.
6	Loan Repayment	The actual amount of principal (amortisation) repaid, including any arrears.
7	Reimbursement	A type of disbursement that covers funds that have already been spent by the recipient, as agreed in the terms of the grant or loan
8	Purchase of Equity	Outgoing funds that are used to purchase equity in a business
9	Sale of Equity	Incoming funds from the sale of equity.
10	Credit Guarantee	A commitment made by a funding organisation to underwrite a loan or line of credit entered into by a third party.
11	Incoming Commitment	A firm, written obligation from a donor or provider to provide a specified amount of funds, under particular terms and conditions, reported by a recipient for this activity.
12	Outgoing Pledge	Indicative, non-binding advice of an intended outgoing commitment.
13	Incoming Pledge	Indicative, non-binding advice of an intended incoming commitment.

Changelog

2.02

The TransactionType codelist had code 11 (Incoming Commitments) added.

2.01

The TransactionType codelist was amended to numeric values.

UN Sustainable Development Goals (SDG)

A value from the top-level list of UN sustainable development goals (SDGs) (e.g. ‘1’)

External URL: https://sustainabledevelopment.un.org/?menu=1300

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/sector/@code

• iati-activities/iati-activity/tag/@code

• iati-activities/iati-activity/transaction/sector/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1	Goal 1. End poverty in all its forms everywhere
2	Goal 2. End hunger, achieve food security and improved nutrition and promote sustainable agriculture
3	Goal 3. Ensure healthy lives and promote well-being for all at all ages
4	Goal 4. Ensure inclusive and equitable quality education and promote lifelong learning opportunities for all
5	Goal 5. Achieve gender equality and empower all women and girls
6	Goal 6. Ensure availability and sustainable management of water and sanitation for all
7	Goal 7. Ensure access to affordable, reliable, sustainable and modern energy for all
8	Goal 8. Promote sustained, inclusive and sustainable economic growth, full and productive employment and decent work for all
9	Goal 9. Build resilient infrastructure, promote inclusive and sustainable industrialization and foster innovation
10	Goal 10. Reduce inequality within and among countries
11	Goal 11. Make cities and human settlements inclusive, safe, resilient and sustainable
12	Goal 12. Ensure sustainable consumption and production patterns
13	Goal 13. Take urgent action to combat climate change and its impacts
14	Goal 14. Conserve and sustainably use the oceans, seas and marine resources for sustainable development
15	Goal 15. Protect, restore and promote sustainable use of terrestrial ecosystems, sustainably manage forests, combat desertification, and halt and reverse land degradation and halt biodiversity loss
16	Goal 16. Promote peaceful and inclusive societies for sustainable development, provide access to justice for all and build effective, accountable and inclusive institutions at all levels
17	Goal 17. Strengthen the means of implementation and revitalize the Global Partnership for Sustainable Development

UN Sustainable Development Goals (SDG) Targets

A value from the second-level list of UN sustainable development goals (SDGs) (e.g. ‘1.1’)

External URL: https://unstats.un.org/sdgs/indicators/indicators-list/

This is a Replicated codelist.

Use this codelist for

• iati-activities/iati-activity/sector/@code

• iati-activities/iati-activity/tag/@code

• iati-activities/iati-activity/transaction/sector/@code

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
1.1	By 2030, eradicate extreme poverty for all people everywhere, currently measured as people living on less than $1.25 a day
1.2	By 2030, reduce at least by half the proportion of men, women and children of all ages living in poverty in all its dimensions according to national definitions
1.3	Implement nationally appropriate social protection systems and measures for all, including floors, and by 2030 achieve substantial coverage of the poor and the vulnerable
1.4	By 2030, ensure that all men and women, in particular the poor and the vulnerable, have equal rights to economic resources, as well as access to basic services, ownership and control over land and other forms of property, inheritance, natural resources, appropriate new technology and financial services, including microfinance
1.5	By 2030, build the resilience of the poor and those in vulnerable situations and reduce their exposure and vulnerability to climate-related extreme events and other economic, social and environmental shocks and disasters
1.a	Ensure significant mobilization of resources from a variety of sources, including through enhanced development cooperation, in order to provide adequate and predictable means for developing countries, in particular least developed countries, to implement programmes and policies to end poverty in all its dimensions
1.b	Create sound policy frameworks at the national, regional and international levels, based on pro-poor and gender-sensitive development strategies, to support accelerated investment in poverty eradication actions
2.1	By 2030, end hunger and ensure access by all people, in particular the poor and people in vulnerable situations, including infants, to safe, nutritious and sufficient food all year round
2.2	By 2030, end all forms of malnutrition, including achieving, by 2025, the internationally agreed targets on stunting and wasting in children under 5 years of age, and address the nutritional needs of adolescent girls, pregnant and lactating women and older persons
2.3	By 2030, double the agricultural productivity and incomes of small-scale food producers, in particular women, indigenous peoples, family farmers, pastoralists and fishers, including through secure and equal access to land, other productive resources and inputs, knowledge, financial services, markets and opportunities for value addition and non-farm employment
2.4	By 2030, ensure sustainable food production systems and implement resilient agricultural practices that increase productivity and production, that help maintain ecosystems, that strengthen capacity for adaptation to climate change, extreme weather, drought, flooding and other disasters and that progressively improve land and soil quality
2.5	By 2020, maintain the genetic diversity of seeds, cultivated plants and farmed and domesticated animals and their related wild species, including through soundly managed and diversified seed and plant banks at the national, regional and international levels, and promote access to and fair and equitable sharing of benefits arising from the utilization of genetic resources and associated traditional knowledge, as internationally agreed
2.a	Increase investment, including through enhanced international cooperation, in rural infrastructure, agricultural research and extension services, technology development and plant and livestock gene banks in order to enhance agricultural productive capacity in developing countries, in particular least developed countries
2.b	Correct and prevent trade restrictions and distortions in world agricultural markets, including through the parallel elimination of all forms of agricultural export subsidies and all export measures with equivalent effect, in accordance with the mandate of the Doha Development Round
2.c	Adopt measures to ensure the proper functioning of food commodity markets and their derivatives and facilitate timely access to market information, including on food reserves, in order to help limit extreme food price volatility
3.1	By 2030, reduce the global maternal mortality ratio to less than 70 per 100,000 live births
3.2	By 2030, end preventable deaths of newborns and children under 5 years of age, with all countries aiming to reduce neonatal mortality to at least as low as 12 per 1,000 live births and under‑5 mortality to at least as low as 25 per 1,000 live births
3.3	By 2030, end the epidemics of AIDS, tuberculosis, malaria and neglected tropical diseases and combat hepatitis, water-borne diseases and other communicable diseases
3.4	By 2030, reduce by one third premature mortality from non-communicable diseases through prevention and treatment and promote mental health and well-being
3.5	Strengthen the prevention and treatment of substance abuse, including narcotic drug abuse and harmful use of alcohol
3.6	By 2020, halve the number of global deaths and injuries from road traffic accidents
3.7	By 2030, ensure universal access to sexual and reproductive health-care services, including for family planning, information and education, and the integration of reproductive health into national strategies and programmes
3.8	Achieve universal health coverage, including financial risk protection, access to quality essential health-care services and access to safe, effective, quality and affordable essential medicines and vaccines for all
3.9	By 2030, substantially reduce the number of deaths and illnesses from hazardous chemicals and air, water and soil pollution and contamination
3.a	Strengthen the implementation of the World Health Organization Framework Convention on Tobacco Control in all countries, as appropriate
3.b	Support the research and development of vaccines and medicines for the communicable and non‑communicable diseases that primarily affect developing countries, provide access to affordable essential medicines and vaccines, in accordance with the Doha Declaration on the TRIPS Agreement and Public Health, which affirms the right of developing countries to use to the full the provisions in the Agreement on Trade-Related Aspects of Intellectual Property Rights regarding flexibilities to protect public health, and, in particular, provide access to medicines for all
3.c	Substantially increase health financing and the recruitment, development, training and retention of the health workforce in developing countries, especially in least developed countries and small island developing States
3.d	Strengthen the capacity of all countries, in particular developing countries, for early warning, risk reduction and management of national and global health risks
4.1	By 2030, ensure that all girls and boys complete free, equitable and quality primary and secondary education leading to relevant and effective learning outcomes
4.2	By 2030, ensure that all girls and boys have access to quality early childhood development, care and pre‑primary education so that they are ready for primary education
4.3	By 2030, ensure equal access for all women and men to affordable and quality technical, vocational and tertiary education, including university
4.4	By 2030, substantially increase the number of youth and adults who have relevant skills, including technical and vocational skills, for employment, decent jobs and entrepreneurship
4.5	By 2030, eliminate gender disparities in education and ensure equal access to all levels of education and vocational training for the vulnerable, including persons with disabilities, indigenous peoples and children in vulnerable situations
4.6	By 2030, ensure that all youth and a substantial proportion of adults, both men and women, achieve literacy and numeracy
4.7	By 2030, ensure that all learners acquire the knowledge and skills needed to promote sustainable development, including, among others, through education for sustainable development and sustainable lifestyles, human rights, gender equality, promotion of a culture of peace and non-violence, global citizenship and appreciation of cultural diversity and of culture’s contribution to sustainable development
4.a	Build and upgrade education facilities that are child, disability and gender sensitive and provide safe, non-violent, inclusive and effective learning environments for all
4.b	By 2020, substantially expand globally the number of scholarships available to developing countries, in particular least developed countries, small island developing States and African countries, for enrolment in higher education, including vocational training and information and communications technology, technical, engineering and scientific programmes, in developed countries and other developing countries
4.c	By 2030, substantially increase the supply of qualified teachers, including through international cooperation for teacher training in developing countries, especially least developed countries and small island developing States
5.1	End all forms of discrimination against all women and girls everywhere
5.2	Eliminate all forms of violence against all women and girls in the public and private spheres, including trafficking and sexual and other types of exploitation
5.3	Eliminate all harmful practices, such as child, early and forced marriage and female genital mutilation
5.4	Recognize and value unpaid care and domestic work through the provision of public services, infrastructure and social protection policies and the promotion of shared responsibility within the household and the family as nationally appropriate
5.5	Ensure women’s full and effective participation and equal opportunities for leadership at all levels of decision-making in political, economic and public life
5.6	Ensure universal access to sexual and reproductive health and reproductive rights as agreed in accordance with the Programme of Action of the International Conference on Population and Development and the Beijing Platform for Action and the outcome documents of their review conferences
5.a	Undertake reforms to give women equal rights to economic resources, as well as access to ownership and control over land and other forms of property, financial services, inheritance and natural resources, in accordance with national laws
5.b	Enhance the use of enabling technology, in particular information and communications technology, to promote the empowerment of women
5.c	Adopt and strengthen sound policies and enforceable legislation for the promotion of gender equality and the empowerment of all women and girls at all levels
6.1	By 2030, achieve universal and equitable access to safe and affordable drinking water for all
6.2	By 2030, achieve access to adequate and equitable sanitation and hygiene for all and end open defecation, paying special attention to the needs of women and girls and those in vulnerable situations
6.3	By 2030, improve water quality by reducing pollution, eliminating dumping and minimizing release of hazardous chemicals and materials, halving the proportion of untreated wastewater and substantially increasing recycling and safe reuse globally
6.4	By 2030, substantially increase water-use efficiency across all sectors and ensure sustainable withdrawals and supply of freshwater to address water scarcity and substantially reduce the number of people suffering from water scarcity
6.5	By 2030, implement integrated water resources management at all levels, including through transboundary cooperation as appropriate
6.6	By 2020, protect and restore water-related ecosystems, including mountains, forests, wetlands, rivers, aquifers and lakes
6.a	By 2030, expand international cooperation and capacity-building support to developing countries in water- and sanitation-related activities and programmes, including water harvesting, desalination, water efficiency, wastewater treatment, recycling and reuse technologies
6.b	Support and strengthen the participation of local communities in improving water and sanitation management
7.1	By 2030, ensure universal access to affordable, reliable and modern energy services
7.2	By 2030, increase substantially the share of renewable energy in the global energy mix
7.3	By 2030, double the global rate of improvement in energy efficiency
7.a	By 2030, enhance international cooperation to facilitate access to clean energy research and technology, including renewable energy, energy efficiency and advanced and cleaner fossil-fuel technology, and promote investment in energy infrastructure and clean energy technology
7.b	By 2030, expand infrastructure and upgrade technology for supplying modern and sustainable energy services for all in developing countries, in particular least developed countries, small island developing States and landlocked developing countries, in accordance with their respective programmes of support
8.1	Sustain per capita economic growth in accordance with national circumstances and, in particular, at least 7 per cent gross domestic product growth per annum in the least developed countries
8.2	Achieve higher levels of economic productivity through diversification, technological upgrading and innovation, including through a focus on high-value added and labour-intensive sectors
8.3	Promote development-oriented policies that support productive activities, decent job creation, entrepreneurship, creativity and innovation, and encourage the formalization and growth of micro-, small- and medium-sized enterprises, including through access to financial services
8.4	Improve progressively, through 2030, global resource efficiency in consumption and production and endeavour to decouple economic growth from environmental degradation, in accordance with the 10‑Year Framework of Programmes on Sustainable Consumption and Production, with developed countries taking the lead
8.5	By 2030, achieve full and productive employment and decent work for all women and men, including for young people and persons with disabilities, and equal pay for work of equal value
8.6	By 2020, substantially reduce the proportion of youth not in employment, education or training
8.7	Take immediate and effective measures to eradicate forced labour, end modern slavery and human trafficking and secure the prohibition and elimination of the worst forms of child labour, including recruitment and use of child soldiers, and by 2025 end child labour in all its forms
8.8	Protect labour rights and promote safe and secure working environments for all workers, including migrant workers, in particular women migrants, and those in precarious employment
8.9	By 2030, devise and implement policies to promote sustainable tourism that creates jobs and promotes local culture and products
8.10	Strengthen the capacity of domestic financial institutions to encourage and expand access to banking, insurance and financial services for all
8.a	Increase Aid for Trade support for developing countries, in particular least developed countries, including through the Enhanced Integrated Framework for Trade-related Technical Assistance to Least Developed Countries
8.b	By 2020, develop and operationalize a global strategy for youth employment and implement the Global Jobs Pact of the International Labour Organization
9.1	Develop quality, reliable, sustainable and resilient infrastructure, including regional and transborder infrastructure, to support economic development and human well-being, with a focus on affordable and equitable access for all
9.2	Promote inclusive and sustainable industrialization and, by 2030, significantly raise industry’s share of employment and gross domestic product, in line with national circumstances, and double its share in least developed countries
9.3	Increase the access of small-scale industrial and other enterprises, in particular in developing countries, to financial services, including affordable credit, and their integration into value chains and markets
9.4	By 2030, upgrade infrastructure and retrofit industries to make them sustainable, with increased resource-use efficiency and greater adoption of clean and environmentally sound technologies and industrial processes, with all countries taking action in accordance with their respective capabilities
9.5	Enhance scientific research, upgrade the technological capabilities of industrial sectors in all countries, in particular developing countries, including, by 2030, encouraging innovation and substantially increasing the number of research and development workers per 1 million people and public and private research and development spending
9.a	Facilitate sustainable and resilient infrastructure development in developing countries through enhanced financial, technological and technical support to African countries, least developed countries, landlocked developing countries and small island developing States
9.b	Support domestic technology development, research and innovation in developing countries, including by ensuring a conducive policy environment for, inter alia, industrial diversification and value addition to commodities
9.c	Significantly increase access to information and communications technology and strive to provide universal and affordable access to the Internet in least developed countries by 2020
10.1	By 2030, progressively achieve and sustain income growth of the bottom 40 per cent of the population at a rate higher than the national average
10.2	By 2030, empower and promote the social, economic and political inclusion of all, irrespective of age, sex, disability, race, ethnicity, origin, religion or economic or other status
10.3	Ensure equal opportunity and reduce inequalities of outcome, including by eliminating discriminatory laws, policies and practices and promoting appropriate legislation, policies and action in this regard
10.4	Adopt policies, especially fiscal, wage and social protection policies, and progressively achieve greater equality
10.5	Improve the regulation and monitoring of global financial markets and institutions and strengthen the implementation of such regulations
10.6	Ensure enhanced representation and voice for developing countries in decision-making in global international economic and financial institutions in order to deliver more effective, credible, accountable and legitimate institutions
10.7	Facilitate orderly, safe, regular and responsible migration and mobility of people, including through the implementation of planned and well-managed migration policies
10.a	Implement the principle of special and differential treatment for developing countries, in particular least developed countries, in accordance with World Trade Organization agreements
10.b	Encourage official development assistance and financial flows, including foreign direct investment, to States where the need is greatest, in particular least developed countries, African countries, small island developing States and landlocked developing countries, in accordance with their national plans and programmes
10.c	By 2030, reduce to less than 3 per cent the transaction costs of migrant remittances and eliminate remittance corridors with costs higher than 5 per cent
11.1	By 2030, ensure access for all to adequate, safe and affordable housing and basic services and upgrade slums
11.2	By 2030, provide access to safe, affordable, accessible and sustainable transport systems for all, improving road safety, notably by expanding public transport, with special attention to the needs of those in vulnerable situations, women, children, persons with disabilities and older persons
11.3	By 2030, enhance inclusive and sustainable urbanization and capacity for participatory, integrated and sustainable human settlement planning and management in all countries
11.4	Strengthen efforts to protect and safeguard the world’s cultural and natural heritage
11.5	By 2030, significantly reduce the number of deaths and the number of people affected and substantially decrease the direct economic losses relative to global gross domestic product caused by disasters, including water-related disasters, with a focus on protecting the poor and people in vulnerable situations
11.6	By 2030, reduce the adverse per capita environmental impact of cities, including by paying special attention to air quality and municipal and other waste management
11.7	By 2030, provide universal access to safe, inclusive and accessible, green and public spaces, in particular for women and children, older persons and persons with disabilities
11.a	Support positive economic, social and environmental links between urban, peri-urban and rural areas by strengthening national and regional development planning
11.b	By 2020, substantially increase the number of cities and human settlements adopting and implementing integrated policies and plans towards inclusion, resource efficiency, mitigation and adaptation to climate change, resilience to disasters, and develop and implement, in line with the Sendai Framework for Disaster Risk Reduction 2015–2030, holistic disaster risk management at all levels
11.c	Support least developed countries, including through financial and technical assistance, in building sustainable and resilient buildings utilizing local materials
12.1	Implement the 10‑Year Framework of Programmes on Sustainable Consumption and Production Patterns, all countries taking action, with developed countries taking the lead, taking into account the development and capabilities of developing countries
12.2	By 2030, achieve the sustainable management and efficient use of natural resources
12.3	By 2030, halve per capita global food waste at the retail and consumer levels and reduce food losses along production and supply chains, including post-harvest losses
12.4	By 2020, achieve the environmentally sound management of chemicals and all wastes throughout their life cycle, in accordance with agreed international frameworks, and significantly reduce their release to air, water and soil in order to minimize their adverse impacts on human health and the environment
12.5	By 2030, substantially reduce waste generation through prevention, reduction, recycling and reuse
12.6	Encourage companies, especially large and transnational companies, to adopt sustainable practices and to integrate sustainability information into their reporting cycle
12.7	Promote public procurement practices that are sustainable, in accordance with national policies and priorities
12.8	By 2030, ensure that people everywhere have the relevant information and awareness for sustainable development and lifestyles in harmony with nature
12.a	Support developing countries to strengthen their scientific and technological capacity to move towards more sustainable patterns of consumption and production
12.b	Develop and implement tools to monitor sustainable development impacts for sustainable tourism that creates jobs and promotes local culture and products
12.c	Rationalize inefficient fossil-fuel subsidies that encourage wasteful consumption by removing market distortions, in accordance with national circumstances, including by restructuring taxation and phasing out those harmful subsidies, where they exist, to reflect their environmental impacts, taking fully into account the specific needs and conditions of developing countries and minimizing the possible adverse impacts on their development in a manner that protects the poor and the affected communities
13.1	Strengthen resilience and adaptive capacity to climate-related hazards and natural disasters in all countries
13.2	Integrate climate change measures into national policies, strategies and planning
13.3	Improve education, awareness-raising and human and institutional capacity on climate change mitigation, adaptation, impact reduction and early warning
13.a	Implement the commitment undertaken by developed-country parties to the United Nations Framework Convention on Climate Change to a goal of mobilizing jointly $100 billion annually by 2020 from all sources to address the needs of developing countries in the context of meaningful mitigation actions and transparency on implementation and fully operationalize the Green Climate Fund through its capitalization as soon as possible
13.b	Promote mechanisms for raising capacity for effective climate change-related planning and management in least developed countries and small island developing States, including focusing on women, youth and local and marginalized communities
14.1	By 2025, prevent and significantly reduce marine pollution of all kinds, in particular from land-based activities, including marine debris and nutrient pollution
14.2	By 2020, sustainably manage and protect marine and coastal ecosystems to avoid significant adverse impacts, including by strengthening their resilience, and take action for their restoration in order to achieve healthy and productive oceans
14.3	Minimize and address the impacts of ocean acidification, including through enhanced scientific cooperation at all levels
14.4	By 2020, effectively regulate harvesting and end overfishing, illegal, unreported and unregulated fishing and destructive fishing practices and implement science-based management plans, in order to restore fish stocks in the shortest time feasible, at least to levels that can produce maximum sustainable yield as determined by their biological characteristics
14.5	By 2020, conserve at least 10 per cent of coastal and marine areas, consistent with national and international law and based on the best available scientific information
14.6	By 2020, prohibit certain forms of fisheries subsidies which contribute to overcapacity and overfishing, eliminate subsidies that contribute to illegal, unreported and unregulated fishing and refrain from introducing new such subsidies, recognizing that appropriate and effective special and differential treatment for developing and least developed countries should be an integral part of the World Trade Organization fisheries subsidies negotiation3
14.7	By 2030, increase the economic benefits to small island developing States and least developed countries from the sustainable use of marine resources, including through sustainable management of fisheries, aquaculture and tourism
14.a	Increase scientific knowledge, develop research capacity and transfer marine technology, taking into account the Intergovernmental Oceanographic Commission Criteria and Guidelines on the Transfer of Marine Technology, in order to improve ocean health and to enhance the contribution of marine biodiversity to the development of developing countries, in particular small island developing States and least developed countries
14.b	Provide access for small-scale artisanal fishers to marine resources and markets
14.c	Enhance the conservation and sustainable use of oceans and their resources by implementing international law as reflected in the United Nations Convention on the Law of the Sea, which provides the legal framework for the conservation and sustainable use of oceans and their resources, as recalled in paragraph 158 of “The future we want”
15.1	By 2020, ensure the conservation, restoration and sustainable use of terrestrial and inland freshwater ecosystems and their services, in particular forests, wetlands, mountains and drylands, in line with obligations under international agreements
15.2	By 2020, promote the implementation of sustainable management of all types of forests, halt deforestation, restore degraded forests and substantially increase afforestation and reforestation globally
15.3	By 2030, combat desertification, restore degraded land and soil, including land affected by desertification, drought and floods, and strive to achieve a land degradation-neutral world
15.4	By 2030, ensure the conservation of mountain ecosystems, including their biodiversity, in order to enhance their capacity to provide benefits that are essential for sustainable development
15.5	Take urgent and significant action to reduce the degradation of natural habitats, halt the loss of biodiversity and, by 2020, protect and prevent the extinction of threatened species
15.6	Promote fair and equitable sharing of the benefits arising from the utilization of genetic resources and promote appropriate access to such resources, as internationally agreed
15.7	Take urgent action to end poaching and trafficking of protected species of flora and fauna and address both demand and supply of illegal wildlife products
15.8	By 2020, introduce measures to prevent the introduction and significantly reduce the impact of invasive alien species on land and water ecosystems and control or eradicate the priority species
15.9	By 2020, integrate ecosystem and biodiversity values into national and local planning, development processes, poverty reduction strategies and accounts
15.a	Mobilize and significantly increase financial resources from all sources to conserve and sustainably use biodiversity and ecosystems
15.b	Mobilize significant resources from all sources and at all levels to finance sustainable forest management and provide adequate incentives to developing countries to advance such management, including for conservation and reforestation
15.c	Enhance global support for efforts to combat poaching and trafficking of protected species, including by increasing the capacity of local communities to pursue sustainable livelihood opportunities
16.1	Significantly reduce all forms of violence and related death rates everywhere
16.2	End abuse, exploitation, trafficking and all forms of violence against and torture of children
16.3	Promote the rule of law at the national and international levels and ensure equal access to justice for all
16.4	By 2030, significantly reduce illicit financial and arms flows, strengthen the recovery and return of stolen assets and combat all forms of organized crime
16.5	Substantially reduce corruption and bribery in all their forms
16.6	Develop effective, accountable and transparent institutions at all levels
16.7	Ensure responsive, inclusive, participatory and representative decision-making at all levels
16.8	Broaden and strengthen the participation of developing countries in the institutions of global governance
16.9	By 2030, provide legal identity for all, including birth registration
16.10	Ensure public access to information and protect fundamental freedoms, in accordance with national legislation and international agreements
16.a	Strengthen relevant national institutions, including through international cooperation, for building capacity at all levels, in particular in developing countries, to prevent violence and combat terrorism and crime
16.b	Promote and enforce non-discriminatory laws and policies for sustainable development
17.1	Strengthen domestic resource mobilization, including through international support to developing countries, to improve domestic capacity for tax and other revenue collection
17.2	Developed countries to implement fully their official development assistance commitments, including the commitment by many developed countries to achieve the target of 0.7 per cent of gross national income for official development assistance (ODA/GNI) to developing countries and 0.15 to 0.20 per cent of ODA/GNI to least developed countries; ODA providers are encouraged to consider setting a target to provide at least 0.20 per cent of ODA/GNI to least developed countries
17.3	Mobilize additional financial resources for developing countries from multiple sources
17.4	Assist developing countries in attaining long-term debt sustainability through coordinated policies aimed at fostering debt financing, debt relief and debt restructuring, as appropriate, and address the external debt of highly indebted poor countries to reduce debt distress
17.5	Adopt and implement investment promotion regimes for least developed countries
17.6	Enhance North-South, South-South and triangular regional and international cooperation on and access to science, technology and innovation and enhance knowledge-sharing on mutually agreed terms, including through improved coordination among existing mechanisms, in particular at the United Nations level, and through a global technology facilitation mechanism
17.7	Promote the development, transfer, dissemination and diffusion of environmentally sound technologies to developing countries on favourable terms, including on concessional and preferential terms, as mutually agreed
17.8	Fully operationalize the technology bank and science, technology and innovation capacity-building mechanism for least developed countries by 2017 and enhance the use of enabling technology, in particular information and communications technology
17.9	Enhance international support for implementing effective and targeted capacity-building in developing countries to support national plans to implement all the Sustainable Development Goals, including through North-South, South-South and triangular cooperation
17.10	Promote a universal, rules-based, open, non‑discriminatory and equitable multilateral trading system under the World Trade Organization, including through the conclusion of negotiations under its Doha Development Agenda
17.11	Significantly increase the exports of developing countries, in particular with a view to doubling the least developed countries’ share of global exports by 2020
17.12	Realize timely implementation of duty-free and quota-free market access on a lasting basis for all least developed countries, consistent with World Trade Organization decisions, including by ensuring that preferential rules of origin applicable to imports from least developed countries are transparent and simple, and contribute to facilitating market access
17.13	Enhance global macroeconomic stability, including through policy coordination and policy coherence
17.14	Enhance policy coherence for sustainable development
17.15	Respect each country’s policy space and leadership to establish and implement policies for poverty eradication and sustainable development
17.16	Enhance the Global Partnership for Sustainable Development, complemented by multi-stakeholder partnerships that mobilize and share knowledge, expertise, technology and financial resources, to support the achievement of the Sustainable Development Goals in all countries, in particular developing countries
17.17	Encourage and promote effective public, public-private and civil society partnerships, building on the experience and resourcing strategies of partnerships
17.18	By 2020, enhance capacity-building support to developing countries, including for least developed countries and small island developing States, to increase significantly the availability of high-quality, timely and reliable data disaggregated by income, gender, age, race, ethnicity, migratory status, disability, geographic location and other characteristics relevant in national contexts
17.19	By 2030, build on existing initiatives to develop measurements of progress on sustainable development that complement gross domestic product, and support statistical capacity-building in developing countries

Verification Status

This is a Non-Core codelist.

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description
0	Not verified	The data published for the activity has not been verified
1	Verified	The data published for the activity has been verified.

Version

Version of the IATI Standard

This is a Non-Core codelist.

Use this codelist for

• iati-activities/@version

• iati-organisations/@version

Download this codelist

CLv1:	CLv2:	CLv3:	CLv3 (french):
CSV	CSV	CSV	CSV
JSON	JSON	JSON	JSON
XML	XML	XML	XML

GitHub Source

Codes

Code	Name	Description	URL
1.01			http://iatistandard.org/101/
1.02			http://iatistandard.org/102/
1.03			http://iatistandard.org/103/
1.04			http://iatistandard.org/104/
1.05			http://iatistandard.org/105/
2.01			http://iatistandard.org/201/
2.02			http://iatistandard.org/202/
2.03			http://iatistandard.org/203/

Changelog

2.01

The Version codelist was added.

Vocabulary

This codelist was split into the SectorVocabulary and PolicyMarkerVocabulary codelists in 2.01.

Schema

The IATI standard consists of a number of schema, the main ones being Organisation and Activity.

Summary tables of the Activity Schema and of the Organisation Schema are also available.

Core Schema

The current suite IATI XML schemas consists of the following components:

• iati-organisations-schema.xsd - XML schema for describing an organisation involved in any stage development cooperation (funding, implementing etc.).

• iati-activities-schema.xsd - XML Schema for describing the details of individual development cooperation activities/projects.

Supplementary Schema

In addition to the Organisation and Activity. core terms are described in the following:

• iati-common.xsd - A supplementary schema with common IATI markup.  Must be in the same directory as the Organisation and Activity schema.

• xml.xsd -  A supplementary schema that must be in the same directory as the Organisation and Activity schema.

Metadata Schema

The Registry Record provides a common format for the reporting of metadata to the IATI Registry.

Please note: Usage of this schema is not mandatory.

• iati-registry-record-schema.xsd - An application-specific extension schema for importing documents into the IATI registry

Updates to IATI Schema

The IATI standard is a living entity that requires improvement over time.

A CHANGES.txt -  provides a comprehensive change log.

Previous schemas

Previous versions of the IATI Schema are available:

• Version 2.02 of IATI Standard

• Version 2.01 of IATI Standard

• Version 1.05 of IATI Standard

• Version 1.04 of IATI Standard

• Version 1.03 of IATI Standard

• Version 1.02 of IATI Standard

• Version 1.01 of IATI Standard

Rulesets

The IATI rulesets provide additional instructions for IATI publishers.

Data published to meet the IATI Standard is created as XML. IATI maintain a number of XML schema that describe the structure of an IATI XML document. However, the design of IATI means that these XML schema cannot enforce all of the rules inherent in the IATI Standard on their own.

For example, the schema, as it stands, cannot check to see if an activity has a start date that occurs before its end date.

The IATI Standard has many rules such as the above, that machines are able to test for, given the correct instructions.

IATI has created ‘Rulesets’ as a way of agreeing what those instructions should be, and grouping them into meaningful collections.

Rulesets are constructed as follows:

• Individual rules detail any constraint or condition.

• Collectively, these rules then make up a ruleset.

This section details the current Standard Ruleset, and provides information around how to utilise and develop rules.

More info

Standard Ruleset

The Standard Ruleset is a collection of rules that cover some of the basic requirements of the IATI Standard and that a computer could, in principle, test. Typically, these are rules about the data that cannot be enforced by the schema alone. It covers for example, the ordering of dates, and checks on the format of an iati-identifier.

There are some things given in definitions of elements that really only a human can interpret, such as “Is a title meaningful?”. The Standard Ruleset does not even try to deal with cases such as this.

We have created a generic framework that allows us to express many of these rules in a way that both humans and machines can understand. We call rules in this generic format our “Machine Readable” rules.

We have already written some code to interpret these rules, and hope that they will be useful, for example, for someone that wanted to build a web application that tested people’s data against these rules. They should be easy to implement.

Some rules do not fit into this format, we call them “Non-Machine Readable Rules”. It should be possible to write bespoke computer code to test each rule, but it requires a bit more work, both in terms of understanding what the rule means and the effort required to check.

Using the Standard Ruleset

The current Standard Ruleset is a collection of rules that can be used to test the data in a single iati-activity or iati-organisation record. IATI data is often found as large files containing collections of (for example) activities, so to test a file of IATI data against the Standard Ruleset means running the tests on each iati-activity or iati-organisation record in that file.

Every iati-activity or iati-organisation record has the option to use different elements of the IATI Standard, and to also repeat certain elements, so in defining a Standard Ruleset it is necessary to include rules that may or may not need to apply for each individual iati-activity or iati-organisation record.

If we take a transaction from an iati-activity record as an example, we can see that this element does not have to be reported. However, it may also be reported many times. There are rules in the Standard Ruleset to check that some of the data reported in transactions makes sense, so these tests could either be run many times, or not at all on a single iati-activity record.

Hence, the minimum and maximum number of tests undertaken on an iati-activity or iati-organisation can fluctuate according to the content.

Non-Machine Readable Rules

reporting-org/@ref

• The agency prefix MUST be a valid code in the IATI code list

• The identifier MUST be the same as that recorded by the publisher on the IATI Registry

participating-org/@ref

• When using this attribute, it must be a valid organisation identifier.

transaction/provider-org/@ref

• When using this attribute, it must be a valid organisation identifier.

transaction/receiver-org/@ref

• When using this attribute, it must be a valid organisation identifier.

iati-identifier

• It MUST be globally unique among all activities published through the IATI Registry

• Once an activity has been reported to IATI its identifier MUST NOT be changed in subsequent updates

• It MUST be prefixed with EITHER the organisation identifier found in reporting-org/@ref OR a previous reporting-org identifier reported in other-identifier

budget

• The budget element should be repeated for each year of the activity’s duration

• Each budget should cover a period no longer than 1 year

sector

• Sector MUST be reported at either activity level or transaction level but not both

• At transaction level, only one sector per vocabulary should be reported

recipient-country and recipient-region

• Either recipient-country or recipient-region MUST be reported at activity level or transaction level but not both.

Machine Readable Rules

These rules are defined in a JSON file <https://github.com/IATI/IATI-Rulesets/blob/version-2.01/rulesets/standard.json> as part of our Single Source of Truth that can be consumed programatically. The list below has been generated from that source.

//iati-activity

• activity-date[@type='1' or @type='2'] must be present.

• Either sector or transaction/sector must be present.

• @xml:lang must exist, otherwise all lang must exist.

• sector must exist, otherwise all sector must exist.

• @default-currency must exist, otherwise all currency must exist.

• transaction/recipient-country must not be present alongisde recipient-region and recipient-country.

• transaction/recipient-region must not be present alongisde recipient-region and recipient-country.

• @last-updated-datetime must not be more recent than the current date

• activity-date[@type='1']/@iso-date must be before or the same as activity-date[@type='3']/@iso-date

• activity-date[@type='2']/@iso-date must be before or the same as activity-date[@type='4']/@iso-date

• activity-date[@type='2']/@iso-date must not be in the future.

• activity-date[@type='4']/@iso-date must not be in the future.

• reporting-org/@ref should match the regex [^\/\&\|\?]+

• iati-identifier should match the regex [^\/\&\|\?]+

• participating-org/@ref should match the regex [^\/\&\|\?]+

• transaction/provider-org/@ref should match the regex [^\/\&\|\?]+

• transaction/receiver-org/@ref should match the regex [^\/\&\|\?]+

• The sum of values matched at recipient-country/@percentage and recipient-region/@percentage must be 100.

• The sum of values matched at sector[@vocabulary = '1' or not(@vocabulary)]/@percentage must be 100.

• The value of each of the elements described by recipient-country/@percentage must be at least 0.0 no more than 100.0 (inclusive).

• The value of each of the elements described by recipient-region/@percentage must be at least 0.0 no more than 100.0 (inclusive).

• The value of each of the elements described by sector/@percentage must be at least 0.0 no more than 100.0 (inclusive).

• The value of each of the elements described by capital-spend/@percentage must be at least 0.0 no more than 100.0 (inclusive).

• The value of each of the elements described by country-budget-items/budget-item/@percentage must be at least 0.0 no more than 100.0 (inclusive).

• If count(sector[@vocabulary=98 or @vocabulary=99]) > 0 evaluates to true, then count(sector[@vocabulary=98 or @vocabulary=99]/narrative) >= count(sector[@vocabulary=98 or @vocabulary=99]) must evaluate to true.

//iati-activity/other-identifier/owner-org

• Either @ref or narrative must be present.

//iati-activity/transaction/provider-org

• Either @ref or narrative must be present.

//iati-activity/transaction/receiver-org

• Either @ref or narrative must be present.

//policy-marker

• @significance must be present if @vocabulary=’1’ or not(@vocabulary)

• narrative must be present if @vocabulary=’99’

//iati-organisation

• reporting-org/@ref should match the regex [^\/\&\|\?]+

• organisation-identifier should match the regex [^\/\&\|\?]+

• @last-updated-datetime must not be more recent than the current date

• @xml:lang must exist, otherwise all lang must exist.

• @default-currency must exist, otherwise all currency must exist.

//participating-org

• Either @ref or narrative must be present.

//transaction

• transaction-date/@iso-date must not be in the future.

• value/@value-date must not be in the future.

//planned-disbursement

• period-start/@iso-date must be before or the same as period-end/@iso-date

//budget

• period-start/@iso-date must be before or the same as period-end/@iso-date

• The time between period-start/@iso-date and period-end/@iso-date must not be over a year

//total-budget

• period-start/@iso-date must be before or the same as period-end/@iso-date

• The time between period-start/@iso-date and period-end/@iso-date must not be over a year

//recipient-country-budget

• period-start/@iso-date must be before or the same as period-end/@iso-date

• The budget-line/value/@value-date must be between the period-start/@iso-date and period-end/@iso-date dates.

• The time between period-start/@iso-date and period-end/@iso-date must not be over a year

//recipient-org-budget

• period-start/@iso-date must be before or the same as period-end/@iso-date

• The time between period-start/@iso-date and period-end/@iso-date must not be over a year

//recipient-region-budget

• period-start/@iso-date must be before or the same as period-end/@iso-date

• The time between period-start/@iso-date and period-end/@iso-date must not be over a year

//result/indicator

• There must be no more than one element or attribute matched at reference[1] or ../reference[1].

• There must be no more than one element or attribute matched at ../reference[1] or reference[1].

//result/indicator/period

• period-start/@iso-date must be before or the same as period-end/@iso-date

//total-expenditure

• The time between period-start/@iso-date and period-end/@iso-date must not be over a year

• period-start/@iso-date must be before or the same as period-end/@iso-date

//result/indicator[@measure=’1’ or @measure=’2’ or @measure=’3’ or @measure=’4’]/baseline

• @value must be present.

//result/indicator[@measure=’1’ or @measure=’2’ or @measure=’3’ or @measure=’4’]/period/target

• @value must be present.

//result/indicator[@measure=’1’ or @measure=’2’ or @measure=’3’ or @measure=’4’]/period/actual

• @value must be present.

IATI Ruleset Spec

An IATI Ruleset is a JSON document. The structure is described below.

A JSON schema is availible to test that the structure of a Ruleset is correct.

Each JSON document has the form.:

{
    "CONTEXT": {
        "RULE_NAME": {
            "cases": CASE_DICT_ARRAY
        }
    }

}

Where CONTEXT is an xpath expression. This will be used to select the XML elements that the contained rules will be tested against. RULE_NAME is one of rule names listed below CASE_DICT is a dictionary where the contents depend on RULE_NAME CASE_DICT_ARRAY is an array of case dictionaries. The contents of each dictionary depend on the RULE_NAME

The possible keys in a case dictionary are:

condition

An xpath string. If this evaluates to True, the rule will be ignored.

eval

An xpath string. Can evaluate to True or False.

paths

An array of xpath strings. These are evaluated to give a list of elements that the named rule then operates upon.

less

A string containing the xpath of the smaller value (or older value when working with dates).

more

A string containing the xpath of the larger value (or more recent value when working with dates).

regex

A string containing a perl style regular expression.

sum

A number.

excluded

An array of xpath strings. Evaluate which elements should not coexist with other elements.

date

A string containing the xpath to a date.

start

A string containing the xpath to a start date.

end

A string containing the xpath to an end date.

one

A string containing the xpath of something that must exist or all must be followed.

all

A string containing the condition that must be met for all elements if one is not met.

foreach

An array of xpath strings. Containing a set of xpaths to be evaluated under a different rule.

do

An array of rules. To evaluate with foreach.

subs

An array of xpath strings. These are to be evaluated with the rules in do.

Rule Names

Rule names are listed in bold

Keys: The keys for each rule are then listed.

Followed by a brief description of the rule’s function.

no_more_than_one

Keys: condition, paths

There must be no more than one element described by the given paths.

atleast_one

Keys: condition, paths

There must be at least one element described by the given paths.

only_one_of

Keys: excluded, paths

If there’s a match of the elements in excluded, there must not be any matches in paths, if there are no matches in excluded, there must be exactly one element from paths.

one_or_all

Keys: one, all

one must exist otherwise all other attributes or elements must exist.

dependent

Keys: condition, paths

If one of the provided paths exists, they must all exist.

sum

Keys: condition, paths, sum

The numerical sum of the values of elements matched by paths must match the value for the sum key

date_order

Keys: condition, less, more

The date matched by less must not be after the date matched by more. If either of these dates is not found, the rule is ignored.

date_now

Keys: date

The date must not be after the current date.

time_limit

Keys: start, end

The difference between the start date and the end date must not be greater than a year.

between_dates

Keys: date, start, end

The date must be between the start and end dates.

regex_matches

Keys: condition, paths, regex

The provided regex must match the text of all elements matched by paths

regex_no_matches

Keys: condition, paths, regex

The provided regex must match the text of none of the elements matched by paths

startswith

Keys: condition, paths, start

The text of each element matched by paths must start with the text of the element matched by start

unique

Keys: condition, paths

The text of each of the elements described by paths must be unique

if_then

Keys: condition, cases, if, then

If the condition evaluated in if is true, then then must resolve to true as well

loop

Keys: foreach, do, cases, subs

All elements in foreach are evaluated under the rules inside do

strict_sum

Keys: paths, sum

The decimal sum of the values of elements matched by paths must match the value for the sum key

Ruleset development

IATI rules and rulesets can be developed and deployed in a number of possible ways.

Different types of rules

So far, the Standard Ruleset deploys two types of rules:

• Starts with - conditions around the formation of the iati-identifier

• Date order - logics around the ordering of various date elements.

Other rules are also possible / feasible.

Making new rulesets

Individual rules can be used and re-used in various collections of Rulesets.

The Standard Ruleset could be extended by adding rules particular to a single publisher, to allow them, and others, to check the data they are producing matches a certain criteria.

Limitations of rulesets

Via the IATI Validator, Rulesets do not currently apply to an entire dataset, consisting of several files. Hence, a ruleset cannot test if an activity identifier has been used once, and only once, by a publisher across their entire dataset.

Rulesets do not allow for checks such as whether or not supplied text contains meaningful information.

Rulesets do not check codes against codelists.

Organisation Identifiers

The IATI standard allows for the recording of information on all organisations that participate in any part of the lifecycle of an aid activity: inter alia donors, beneficiaries, extending and implementing agencies.

Crucial to this, is a common process through which to identify and declare identifiers for these organisations.

Introduction

Organisational identifiers have two uses in IATI.

In the IATI organisation standard:

• They are used to identify organisations as reporting organisations (reporting-org), as receiving budgets (recipient-org), and of course as an iati-organisation.

• They form the iati-identifier - used to declare a globally unique identifier for the specific iati-organisation

In the IATI activity standard:

• They are used to identify organisations as reporting organisations (reporting-org), receiving funds (receiver-org), providing funds (provider-org), or otherwise involved in iati-activities (using participating-org)

• They form the basis of the iati-identifier - used to declare a globally unique activity identifier for the specific iati-activity - composed of the reporting organisation Organisation ID, and an Activity ID.

Two components of IATI Organisation Identifiers

The two components of IATI Organisation Identifiers

The IATI Organisational Identifier scheme is based on re-using existing known identifiers for an organisation.

Identifier strings consist of two components:

1. The namespace code - a code that creates and maintains a given organisational identifier registry

2. The base identifier – re-use of an existing identifier from that namespace/registry

1 and 2 are separated by a dash -.

The namespace code (1) may contain a dash -.

Worked example

GB-COH is the namespace code to the UK Companies Registrar which issues numerical company identifiers to legally constituted limited companies in the United Kingdom of Great Britain and Northern Ireland:

• Companies House..

06368740 is the company number (base identifier) issued to Development Initiatives Poverty Research Limited.

• Development Initiatives Poverty Research Limited record on Companies House..

Combining these we get an IATI Organisational Identifier of: GB-COH-06368740

Organisation Registration Agencies

To assist with creating and de-referencing IATI Organisation Identifiers, the codelist Organisation Registration Agency is available.

This codelist provides the namespace codes for a number of Registration Agencies. This list is non-embedded in the IATI Standard, which means changes and additions may be made at short notice, outside of published decimal and integer upgrade schedules. If a Registation Agency that you wish to use is not on this list, please contact support@iatistandard.org.

Guidance on selecting an Organisation Registration Agencies (namespace)

An IATI Organisation Identifier should:

• Use an existing registration number/identifier that has been given to an organisation by an official registry of organisations (for example, a national company registrar, or drawn from a government register of charities). Registries that provide machine readable access to the data about organisations are generally preferred over those that do not (subject to (3) below).

• Use a namespace/registry code from the existing IATI list of namespaces and registration agency codes. This is currently available as a codelist. If no existing code is available then you should contact IATI Support with details of the registration agency you wish to re-use a code from in order to have a code set up.

• Where an organisation has multiple registration numbers, prefer those identifiers which uniquely pick out the organisation itself, rather than properties of the organisation. For example, a VAT/Tax registration number describes that an entity is registered for tax, but may not map directly onto a single legal entity – as – for example – groups of companies may share a VAT registration number. For this reason, an identifier such as GB-COH-123456 would be preferred to GB-VAT-987765.

• Where an organisation is not identified in an official national registry, but it is identified on the (deprecated since v1.04 of the standard) ``OrganisationIdentifier`` codelist, these codes should be used as given..

• Where none of the above provide an appropriate identifier, third-parties may provide appropriate lists of organisations. Consult with IATI Support to identify appropriate identifier lists.

• Where no other identifiers are held or available, please contact IATI support.

If you are unsure of which registration agency to prefer, please consult IATI Support. If no authoritative registration agency information is currently collected (e.g. internal identifiers and supplier numbers are recorded, but no external identifiers) IATI publishers are encouraged to identify opportunities to collect an authoritative public identifier.

Example Usage

Once determined, the IATI Organisational Identifier can be used:

• IATI organisation standard: as the iati-identifier, in the @ref attribute of reporting-org and recipient-org-budget/recipient-org.

• IATI activity standard: in the @ref attribute of reporting-org and participating-org, and should be used in @ref attribute of transaction/provider-org and transaction/recipient-org.

The string value name within any organisational identifier XML tag is provided for convenience of consuming applications only, and should not be treated as definitive.