Extension: Line item funding sources

[timgdavies]

From the Quinta Group team working on OCDS implementation in Moldova:

The Moldovan Register of IBAN codes is used to ensure quality control over the accuracy
of national public budget revenues.

See http://www.bulr.com/legal-updates/iban-registry-implementation.html for background on how this operates.

Typically, in paper tenders PE would indicate budget line number (IBAN
code) to indicate what is the procurement's funding source if it applies.

This has led to an extension request to extend item with fundingSource, combining a 'scheme' and 'identifier' to allow cross-referencing of the budget sources for line item funding.

We considered use of extensions within the budget block, but due to (a) the point in time at which the budget-item linkage is known; and (b) the specific linkage between funding source and line-item, have suggested the line item extension as below.

Outstanding questions are whether fundingSource should be an array, or a single item - and what interpretation would be placed on an array (e.g. two different identifiers for the same funding source? Or indicating funding sources being blended for a single item... which might then require some percentage apportionment of sourcing...)

{
   "id": "0001",    
   "description":"Highways construction",
   "classification": {
        "description": "Construction work for highways",
        "id": "45233130",
        "scheme": "CPV",
        "uri": "http://cpv.data.ac.uk/code-45233130"
    },
    "description": "Construction work",
    "fundingSources":{
         "scheme":"IBAN",
         "id":"MD42TRGAAA14311201300000",
         "uri":"",
    }
}

Views on this issue welcome.

[timgdavies]

This requirement has only come up once, and any future similar cases should explore whether needs can be met by the ocds_budget_and_spend extension.