The IATI activity standard enables
transaction information to be published.
transaction data is a core component to IATI, detailing the flow of monies between organisations.
When using the IATI activity standard to declare transaction, the following should be considered:
iati-activityshould contain at least one
transaction. However, this may not always be possible for early-stage activities, for example.
transactionmust contain a
transactiona 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.
valueof a transaction can be positive or negative, and contain decimals. It should not contain comma separators (eg: 3,000)
value-datemust be in ISO 8601 format (YYYY-MM-DD), eg: 2014-03-21.
value-datecan be in the “future”. A
transactionalways describes something that has taken place.
transactioncan be declared in any currency on the Currency codelist.
transactioncan also include
tied-statuscan be set as defaults in the
iati-activityelement. There is no requirement to restate these within a
transactionif they are the same.
transactioncan also contain information on the source and destination organisation. When describing these the
receiver-orgshould be used. Ideally, the unique organisation identifier would be included.
Where possible, it is recommended that a
receiver-activity-idto reference the
iati-activityfrom which funds flow from/to.
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.
recipient-country, recipient-region` and
sectorcan also be published as child elements of a
transaction. When this is done, it is expected that all
transactioninclude such data, whilst the relevant element is subsequently not included at the
iati-activitylevel. Also none of these elements when published as child elements of a
transactionneed or use a percentage attribute as they do at the