planned-disbursement

Definition

The planned disbursement element should only be used to report specific planned cash transfers. These should be reported for a specific date or a meaningfully predictable period. These transactions should be reported in addition to budgets - which are typically annual breakdowns of the total activity commitment.

Rules

This element may occur any number of times.

Attributes

@type

Whether this is an original plan (prepared when the original commitment was made) or has subsequently been revised.

This value must be of type xsd:string.

This value must be on the BudgetType codelist.

Usage in practice

The purpose of planned-disbursement is to describe any predefined payment schedule.

Planned disbursements should relate to an actual transfer of funds.

Planned disbursements do not replace the activity-budget.

Example Usage

Example planned-disbursement for an iati-activity.

This element is a parent for other child elements.

The @type attribute declares a valid code (1) from the BudgetType codelist.

<planned-disbursement type="1">
...
</planned-disbursement>

Note: If omitted, then BudgetType code 1 (Original) is assumed.

Full example with all child elements:

  <planned-disbursement type="1">
   <period-start iso-date="2014-01-01" />
   <period-end iso-date="2014-12-31" />
   <value currency="EUR" value-date="2014-01-01">3000</value>
   <provider-org provider-activity-id="BB-BBB-123456789-1234AA" type="10" ref="BB-BBB-123456789">
    <narrative>Agency B</narrative>
   </provider-org>
   <receiver-org receiver-activity-id="AA-AAA-123456789-1234" type="23" ref="AA-AAA-123456789">
    <narrative>Agency A</narrative>
   </receiver-org>
  </planned-disbursement>

Note: multiple planned disbursements are expressed by repeating the planned-disbursement element.

Changelog

Developer tools

Find the source of this documentation on github:

• Schema

• Extra Documentation

Subelements

• period-start
• period-end
• value
• provider-org
• receiver-org