From @myroslav:
In our Moldova implementation we have need for extra details of
organization identification. It is not just different way of identification
(like different registry or different jurisdiction, that would natively map
to additionalIdentifications) but a way to detail the already present
primary one.
In Moldova there is inter-ministry registry that we use MD-IDNO schema for.
For taxation, banking and accounting purposes big organizations that have
divisions have additional so called divisionCode, that is normally
sequential number from 1 to number of divisions organization has. For bank
kind of organization every branch would have such number, for big national
corporation, regional representative offices would have similar sequential
numbers.
These divisionCode is normally used in accounting, in bank transactions
when specifying receiver altogether with MD-IDNO, and mandatory for
taxation, since tax office is handling taxation of branches independently
of primary organization. At least we were told so. Additional information
we have us that tax office is maintaining the registry, but that registry
of Organization Divisions is not public.
Please help us define rules of how to express that additional divisionCode in
OCDS, or its extension.
- The first proposal was to add extra divisionCode/divisionName attributes
to Identification.
- The other was to introduce something like MD-TAXDC (Moldova Taxation
Division Code) schema and add it as additionalIdentification for
organizations having more then only primary division. But this approach is
still not elegant enough.
Are there other options to the challenge we have?
From @myroslav: