[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-dev] Multiple supplier account invoice
Hi Diogo As I remember it from the UBL TC at time of UBL 1.0, the TC added AdditionalAccountID for this kind of reason so it should be that you can use it. In UBL 2.0 the definition was refined at a late stage (after the first committee spec): I think that may mean that your comment should be considered for future versions of UBL. Some would say that using the AdditionalAccountID would be 'scope creep' but that means it would just be a form of customisation. The UBL principle agreed at an early date in UBL history was to cater for the 80% of requirements met by 20% of all the possible development that could have been done on UBL. Then to allow customisation to meet the other 20% of requirments. I think, personally, and you might agree, that an invoice covering multiple customer accounts for a single customer party is one of the 20% requirements best met by customisation. My gut feeling is that it would be clearer for the customer to have separate invoices but I haven't seen the exact requirements of your situation or scenario. If you have the opportunity to customise the invoice, either its structure or its semantics or both then, after considering the guidelines (in progress) http://www.oasis-open.org/committees/download.php/29194/custguide091d.pdf (which might be being updated as I write - warning) I would just try applying your modified semantics to AdditionalAccountID or (if you prefer not to change the semantics) extend the SupplierParty structurally so that semantics do not have to change. Maybe you might consider adding a comment about this on the UBL comment list too if you are not a UBL TC member. http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl Anyway, the choice is yours how you deal with this. I would think that it might be tricky to identify which parts of the invoice correspond to which account ID so it seems safest to me to use separate invoices for each account ID. Then you can just use the Standard UBL invoice with just some subsetting (perhaps Northern European Subset or SystML or whatever). Best regards Steve -- Stephen D. Green Document Engineering Services Ltd http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice 2009/1/29 Diogo Almeida <diogo.borges.almeida@gmail.com>: > Good evening, > > In the process of creating an UBL 2.0 Invoice I ran into an issue regarding > the supplier assigned accounts. > > If I wish to create an Invoice where CompanyA bills CompanyB accounts 1 and > 2, where would I place such information within the invoice schema? > > The SupplierAssignedAccountID is an optional element that can only be > present one time per invoice. A somewhat possible option would be to use the > AddicionalAccount array element, provided that you ignore the fact that they > should be used for third party account identification, instead of additional > supplier account IDs. > > How could I represent this multiple account invoice notion in the UBL > Invoice schema, without the creation of an extension? I'm guessing that > either I've missed some place where this information can be placed, or just > its not a common scenario. Hopping for the first option, though. > > Has someone experienced similar requirement or situation? > > Would be very interested to know how would you approach this situation. > > Best regards, > Diogo Almeida >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]