This version is DEPRECATED, v2.03 is the latest version
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
- For every
transactiona type contained on the
TransactionTypecodelist is required,
- There are several types of transactions. The most common are:
- Commitment - the total agreed budget for the activity.
- Disbursement - the amount transferred to another organisation in the aid delivery chain (e.g. a partner organisation being funded).
- Expenditure - the outlay on goods and services and project overheads.
- Incoming funds - the funds received from a funding source (e.g. a donor).
valueof a transaction can be positive or negative, and contain decimals. It must not contain comma seperators (eg: 3,000):
- Both the
value-datemust be in ISO 8601 format (YYYY-MM-DD), eg: 2014-03-21.
- Neither of
value-datecan be in the “future”. A
transactionalways describes something that has taken place.
transactioncan be declared in any currency on the
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 refernce the
iati-activityfrom which funds flow from/to.