1 / 8

Implementation Issues

Explore real examples of traceability issues in IATI transactions and how to prevent double counting through segmentation strategies.

ermal
Download Presentation

Implementation Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Traceability – a real example

  3. Traceability

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

  5. 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>

  6. Double counting – you can’t count the whole of IATI .

  7. Double counting – Publisher rules

  8. Segmentation

More Related