Project level information

1. Structure of IATI XML file Project level information Includes: Activity identifier (project id) Reporting organization Participating organization Activity title Recipient country/region Activity description Activity website Contact information Sectors and themes Aid type Activity status and so forth Transaction level information Includes: Transaction type Providing organization Transaction amount and date Transaction type Aid type Finance type and so forth

2. Process of World Bank’s reporting to IATI: Phase 1 (Semi-automated) Source: CTR Source: CTR/ Loan kiosk Source: Project Database DEC DEC DEC Data on debt relief Financial data (commitments, disbursements, repayments, interest and fees) Project id recipient country DEC Roll loan level data to project level by quarter; make debt relief adjustments; map to IATI country code; map flow-type, finance-type, aid-type, and descriptions at the transaction level : DEC DEC DEC Source: Business Warehouse Source: Project Database/ Data mart OPCS DEC ISG Project level information in Excel (sectors , themes, percentages) Transaction level data in Excel Other project level information (abstract, URL, contact info etc) DEC DEC OPCS ISG Creation of input file: ISG Mapping of each World Bank inputs to IATI fields: DEC, OPCS Check input files for accuracy: CTR, DEC, OPCS Creation of XML files: ISG Check XML files for accuracy: CTR, DEC, OPCS XML files by country Web files/ links created in e-publish for each country file: OPCS URLs posted to IATI registry: ISG, OPCS

3. Automation Highlights – Requirements and Expected Benefits • Currently a manual, complicated, time-consuming, and potentially error-prone process • However, IATI data extracts, adjustment processes, data verification, and XML file generation and publishing can be substantially automated allowing for automated nightly reporting for projects and monthly for financials. • The initial automation process is fairly complex and resource intensive and will require continued participation from the core team as well as clearance from management to proceed with the outlined approach • Decisions on specific business rules and extracts (e.g. handling debt relief reporting) will need to be addressed as part of the initiative • The core team will address data and other issues as they arise and escalate to management if needed • Extensive initial data verification will be required until processes are certified. After this point data reviews can be done on a sampling basis • Once the approach has been automated it will improve our ability to reliably and accurately report activity data to IATI in a timely and cost efficient manner.

4. Quality Sampling Country Files IATI Registry Automating IATI Reporting Publish XML Files 6 Customized Projects API for IATI Automated nightly project data loads eliminate current manual downloads of core project data from SAP/BW. Automated monthly loads (cleared Statement of Loans & Credits) eliminate manual downloads of financial data from Loan Kiosk. Automated monthly extracts of Debt Relief data need to be designed and built. Core institutional data will be consolidated into enterprise BI platform layer and made accessible to External Operations application via data services and other automated tools. External Operations application will process the institutional data based on IATI requirements (e.g. merge data at required granularity, add document URLs and abstracts , field descriptors and labels, mapping to IATI codes, etc) External Operations application will generate IATI-formatted XML data programmatically available to IATI via a customized Projects API. Sampling for quality will be conducted. Appropriate country specific URLs will be registered in the IATI registry. Also provides foundation for subsequent work, e.g. CRS 1 Operations Portal Application Layer 5 2 Institutional Core Data IATI Processing IATI Data 3 4 Enterprise Business Intelligence Layer 4 Project Data Loans Data Debt Data 5 1 2 3 6 Operations Portal iLAP/Loan Kiosk Debt Relief Data