You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The definition of ID and GlobalID of seller, buyer and other partys is defined as "0 .. unbounded", so there should be able to write more than one ID and more than one GlobalID for an address.
Here is an example of a valid invoice (EXTENDED format):
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The definition of ID and GlobalID of seller, buyer and other partys is defined as "0 .. unbounded", so there should be able to write more than one ID and more than one GlobalID for an address.
Here is an example of a valid invoice (EXTENDED format):
ram:ApplicableHeaderTradeAgreement
ram:BuyerReference378149</ram:BuyerReference>
ram:SellerTradeParty
ram:IDB 2017</ram:ID>
ram:IDDE811135476</ram:ID>
ram:ID316239045</ram:ID>
ram:ID4399901831414</ram:ID>
<ram:GlobalID schemeID="0206">B 2017</ram:GlobalID>
<ram:GlobalID schemeID="0223">DE811135476</ram:GlobalID>
<ram:GlobalID schemeID="0060">316239045</ram:GlobalID>
<ram:GlobalID schemeID="0088">4399901831414</ram:GlobalID>
...
It would be great if further versions of ZUGFeRD-csharp can write and read more ID's per party.
Beta Was this translation helpful? Give feedback.
All reactions