Organisation level |
Organisation |
Organisation documents |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Organisation |
Recipient country budgets |
Partially compliant
|
|
Our actual work processes don't allow for 3 year-budgets on a rolling basis.
We work however with 4-5 year cycles of "Indicative Cooperation Programmes" which define a budget framework for all of our 18 priority partner countries, so in practice there won't be much difference.
Besides, the focus remains on the same sectors during several of such cycles, which enhances continuity and predictability.
|
1 |
|
Organisation |
Organisation budget |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Organisation |
Funded institution budgets |
Partially compliant
|
|
Our actual work processes don't allow for 3 year-budgets on a rolling basis. We do however practice multi-year budgeting, so in practice there won't be much difference. |
1 |
|
Identification |
Activity |
Reporting organisation |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
IATI Identifier |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Other Identifier |
Fully compliant
|
2014-06-01 |
|
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Basic activity information |
Activity |
Activity dates (End Date) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Activity dates (Start Date) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Participating organisation (Accountable) |
Fully compliant
|
2014-06-01 |
|
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Participating organisation (Funding) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Participating organisation (Implementing) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Participating organisation (Extending) |
Fully compliant
|
2014-06-01 |
|
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Title (Agency language) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
|
Fully compliant |
Information assumed |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Title (Recipient language) |
|
|
|
|
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
|
Information assumed |
Date |
None |
None |
No change |
Notes |
|
|
No change |
|
Activity |
Description (Agency language) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
|
Fully compliant |
Information assumed |
Date |
None |
2014-06-01 |
Information assumed |
Notes |
|
|
No change |
|
Activity |
Description (Recipient language) |
|
|
|
|
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
|
Information assumed |
Date |
None |
None |
No change |
Notes |
|
|
No change |
|
Activity |
Contact information |
Future publication
|
2014-06-01 |
Generic contact |
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Future publication |
Future publication |
No change |
Date |
2013-06-01 |
2014-06-01 |
Initial date later |
Notes |
Generic contact |
Generic contact |
No change |
|
Activity |
Activity status |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Geopolitical information |
Activity |
Recipient country |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Recipient region |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Sub-national geographic location |
Fully compliant
|
2014-06-01 |
We can momentarily specify first administrative subdiv ision (province or district etc).
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
We can momentarily specify first administrative subdiv ision (province or district etc).
|
We can momentarily specify first administrative subdiv ision (province or district etc).
|
No change |
|
Classifications |
Activity |
Flow type |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Sector (DAC CRS) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Sector (Agency specific) |
Not applicable
|
|
We don't use agency-specific sector codes. |
N/A |
|
Activity |
Tied aid status |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Policy marker |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Collaboration type |
|
2014-06-01 |
Can be deducted from the combination of "type of aid" and "channel of delivery" |
|
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
|
Status/notes inconsistent |
Date |
None |
2014-06-01 |
No date provided |
Notes |
Can be deducted from the combination of "type of aid" and "channel of delivery" |
Can be deducted from the combination of "type of aid" and "channel of delivery" |
No change |
|
Activity |
Finance type |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Aid type |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Financial |
Activity |
Budget identifier (Administrative/functional) |
Fully compliant
|
2014-06-01 |
|
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Budget identifier (Economic) |
Fully compliant
|
2014-06-01 |
|
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Budget |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Planned disbursement |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Financial transaction |
Activity |
Transactions (Reimbursement) |
Fully compliant
|
2014-06-01 |
|
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Transactions (Disbursement / Expenditure) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Transactions (Incoming Funds) |
Not applicable
|
|
|
|
|
Activity |
Transactions (Commitment) |
Fully compliant
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Activity |
Transactions (Loan repayment / interest repayment) |
Fully compliant
|
2014-06-01 |
|
N/A |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Fully compliant |
Fully compliant |
No change |
Date |
None |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Related documents |
Activity |
Activity website |
Partially compliant
|
2015-01-01 |
Our website does contain information at activity-level for the general public, accessible through a search engine.
However, until now, it contains only activities with a disbursement in the previous years, i.e. information that has already passed our yearly overall screening and quality-control during the first months of each year in order to obtain a complete and accurate data-set for DAC-CRS reporting.
In the future we will extend coverage to include actual new activities and planned activities as well. |
N/A |
|
Activity |
Related activity |
Not applicable
|
|
|
N/A |
|
Activity |
Activity documents |
Future publication
|
2014-06-01 |
|
1 |
changes
Implementation schedules were amended when information provided was incomplete, not parsed properly or required interpretation.
Component | Initial | Corrected | Change reason |
Status |
Future publication |
Future publication |
No change |
Date |
2015-01-01 |
2014-06-01 |
No date provided |
Notes |
|
|
No change |
|
Performance |
Activity |
Conditions (Attached Y/N) |
Future publication
|
2015-01-01 |
|
1 |
|
Activity |
Conditions (Text) |
Future publication
|
2015-01-01 |
|
1 |
|
Activity |
Results |
Future publication
|
2015-01-01 |
We will adapt our workprocesses and internal systems in order to be able to allow such publication in the future. |
1 |
|