The proposal is to add 'Incoming commitment' as a transaction type to the 1.x and 2.01 codelists. This is a crucial element for full 'chain transparency'.
In the current 2.01 standard the 'Incoming commitment' is missing in the Transaction Type codelist. In the Netherlands there are a lot of organisations which both have incoming commitments and outgoing commitments. Since the current standard only supports the 'Commitment' as a transaction type, it is impossible to distinguish between incoming and outgoing commitments. Without this element full chain transparency is therefore not possible.
This change should span both 1.0x and 2.01 since it is a crucial element for chain transparency for all publishers. I suggest to use ‘IC’ as a code for the 1.x codelist and 11 (numeric) for 2.x codelist.
This proposal has been discussed and agreed with Bill Anderson during the 2015 TAG in Ottawa for implementation in the 2.02 decimal upgrade before 1 December 2015.