provider-org¶

iati-activities/iati-activity/transaction/provider-org

This is the reference page for the XML element provider-org.

Definition¶

For incoming funds this is the organisation from which the transaction originated. If omitted on outgoing funds the reporting-org is assumed.

Rules¶

This element must occur no more than once (within each parent element).

Attributes¶

@ref

Machine-readable identification string for the organisation issuing the report. Must be in the format {RegistrationAgency}-{RegistrationNumber} where {RegistrationAgency} is a valid code in the Organisation Registration Agency code list and {RegistrationNumber} is a valid identifier issued by the {RegistrationAgency}. If this is not present then the narrative MUST contain the name of the organisation.

This value must be of type xsd:string.

transaction/provider-org/@ref should match the regex [^\/\&\|\?]+

Either @ref or narrative must be present.

@provider-activity-id

If incoming funds are being provided from the budget of another activity that is reported to IATI, it if STRONGLY RECOMMENDED that this should record the provider’s unique IATI activity identifier for that activity.

This value must be of type xsd:string.

@type

The type of organisation providing the funds.

This value must be of type xsd:string.

This value must be on the OrganisationType codelist.

Example Usage¶

Example usage of provider-org of a transaction in an iati-activity.

This example declares the organisation identifier with the @ref attribute.

This example declares the type of organisation who provided the funds, using the @type attribute.

<provider-org ref="BB-BBB-123456789-1234AA" type="10">
  <narrative>Agency B</narrative>
</provider-org>

This example additionally declares the unique iati-identifier of the reported iati-activity from where the transaction is provided, with the @provider-activity-id attribute.

<provider-org ref="BB-BBB-123456789" type="10" provider-activity-id="BB-BBB-123456789-1234AA">
  <narrative>Agency B</narrative>
</provider-org>

Full example, within a transaction.

  <transaction ref="1234" humanitarian="1">
   <transaction-type code="1" />
   <transaction-date iso-date="2012-01-01" />
   <value currency="EUR" value-date="2012-01-01">1000</value>
   <description>
    <narrative>Transaction description text</narrative>
   </description>
   <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>
   <disbursement-channel code="1" />
   <sector vocabulary="2" code="111" />
   <!--Note: only a recipient-region OR a recipient-country is expected-->
   <recipient-country code="TM" />
   <recipient-region code="616" vocabulary="1" />
   <flow-type code="10" />
   <finance-type code="110" />
   <aid-type code="A01" vocabulary="1" />
   <aid-type code="1" vocabulary="2" />
   <tied-status code="3" />
  </transaction>

Changelog¶

2.03¶

The definition of the @ref attribute was updated.

2.02¶

The attribute @type was added.

2.01¶

Freetext is no longer allowed with this element. It should now be declared with the new child narrative element.

Developer tools¶

Find the source of this documentation on github:

Subelements¶

narrative