[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl] Change request for UBL- clarification requested
Dear Tim, Please have a look in the attachement for examples and additional explanations. More info can be provided if needed. thanks /Anders Tim McGrath wrote: > On behalf of the UBL TC I would like to ask you about two items in > the Swedish Association of Local Authorities' submission for UBL 1.1 > > Firstly, you have requested a BIE called AllowanceChargeBaseAmount in > the Object Class called Allowance Charge. We are not completly clear > about what is required here so we were hoping you might be able to > give some worked examples. > > Secondly, the BIE called TaxCurrencyTaxAmount in the Object Class > called Tax Sub Total. Are you stating that any tax amounts need to be > explicitly stated in both paying and local currencies? Again, an > example may be helpful. > > Meanwhile we are working through the other items in the submission and > will get back to you as the need arises. > > > Anders W. Tell wrote: > >> Dear UBL Team >> >> Please accept the following change request for UBL, summitted on >> behalf of >> Swedish Association of Local Authorities, Swedish Agency of Public >> Management, The Swedish Association of County Councils and Legal, >> Financial and Administrative Services Agency and its Single Face To >> Industry (SFTI) initiative. >> >> The change request should be added to the existing list of SFTI >> requests. >> >> -------------------------- >> >> UBL Name: ReasonCode >> >> Object class: ChargeIndicator >> >> Problem statement: In SFTI we need a mechanism to identify a few >> basic allowance/charge items at invoice level, as listed below. We >> have tried to apply the current UBL ReasonCode >> >> xmlns="urn:oasis:names:tc:ubl:codelist:AllowanceChargeReasonCode:1:0" >> >> which essentially appears to copy UN/Cefact 4465 Adjustment reason >> coded, but these reason codes do not seem fit well in ordinary >> invoicing situations. Instead, a more appropriate approach might be >> to take inspiration from the Edifact INVOIC ALC segment and use 7161, >> Special service description code. >> >> Should it not be possible to replace the code list, SFTI would need >> code values corresponding to the following ones >> >> - AEL = Small order processing service >> >> - EP = Expediting >> >> - IS = Invoicing >> >> - RAA = Rebate (or trade rebate, which is the only one available in >> 4465) >> >> - TV = Transportation by vendor. >> >> (the 2/3-alpha codes are drawn from the 7161 code list, but of course >> we are prepared to adjust them as deemed necessary by the Technical >> Committee) >> -------------------------------- >> >> >> >> Anders W. Tell >> >> /anders >> >> >> To unsubscribe from this mailing list (and be removed from the roster >> of the OASIS TC), go to >> http://www.oasis-open.org/apps/org/workgroup/ubl/members/leave_workgroup.php. >> >> >
SFTI_UBL_Clarification_20050101.doc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]