Implementation Issues Traceability, Double Counting, Segmentation IATI TAG Cookham, 14 May 2012 Bill Anderson – IATI Technical Advisory Group

Traceability – a real example

Traceability Disbursements are transactions for another accountable organisation to spend Expenditures are transactions for goods and services with an unaccountable organisation Disbursements vs Expenditures Between reporting organisations Between activities reported by the same organisation Traceability tracks Incoming Funds and Disbursements

Traceability: IATI transactions (1) <transaction-type code=“D"/> <value value-date="2012-02-27">25000</value> <transaction-date iso-date="2012-02-27"/> </transaction>

Traceability: IATI transactions (2) <transaction ref=“aX556”> <transaction-type code=“D"/> <provider-org ref=“GB-123” provider- activity-id="GB-123-10538"/> <receiver-org ref=“NP-234” receiver-org- activity-id=“NP-234-99876”/> <value value-date="2012-02-27">25000</value> <transaction-date iso-date="2012-02-27"/> </transaction>

Double counting – you can’t count the whole of IATI . IATI is not a single dataset The same activity can be reported by donor, implementers, third-parties Counters need to choose their datasets and their point of view

Double counting – Publisher rules Report transactions only at the lowest hierarchical level Only report your own transactions Define disbursements and expenditures correctly Report the provider of incoming funds Report the receiver of disbursements

Segmentation File size Easy access to Country/Region data Pros Not every does Multi-country activities (duplication not allowed) Cons ??? Solution