[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl-dev] Invoice - Head Office Party
> Hi Roberto,
>
> Thank you for the response to my query last week. Unfortunately the
> branch making the sale is both the legal address for the sale, and the
> accounting address.
Why unfortunately, this seems to me the most simple case when a business
has all administrative, operative and legal function in one.
>Most of the branches are individually owned, though
> they are each grouped into one of 10 parent organisations.
>
> - Parent 1 (This is the level I'm unsure of how to model)
> -- Branch 1 (Seller Customer Party / Accounting Supplier Party)
> -- Branch 2
> - Parent 2
> -- Branch 3
> ... etc
>
If the Grouping company is a separated legal entity you do not have to
mention it fully on your invoices, but maybe you need just to mention the
Company group name. (e.g. an additional PartyName)
The relationship between a branch site and the head grouping company it
seems to me just a ownership misured with a quantity of shares, but it is
not related to invoicing.
I suggest also you add a PartyIdentification using an ID meaninful whithin
your group of companies.
So the additional PartyName will be useful for printing the group name
together the branch business name and address.
The PartyIdentification will be a machine-friendly ID to univocally
distinguish your branches within your groups (for your internal uses).
> I suspect that you are correct in your comment that I will need to use
> the UBL Extensions to achieve this - I just thought I might be missing
> something as the concept of Head Office Party is not uncommon. I'm sure
> that I could use one of the other party elements that you mentioned, but
> I'm concerned that using one that doesn't quite fit will cause problems
> in future if any of these partner organisations start using UBL for
> their own purposes.
UBL Extensions can be used if strictly necessary, but electronically
speaking the e-Invoicing do not need always to mention all human
descriptions, notes.. so on, but coded values, unique IDs.
Is the receiver of the invoice interested into the Grouping company full
address ? I think not.
Is your company interested into univocally recognize the invoices
generated by a branch and related to a specific group by means of an ID ?
I think yes.
>
> Thanks again for your comments.
yes just comments, you have to decide what is better for your use case.
>
> Cheers,
>
> Nick
Best regards
Roberto
>
> PS. I wasn't aware of the UBL Swinger tool that you mentioned, so that
> you for pointing that out.
>
> -----Original Message-----
> From: Roberto Cisternino [mailto:roberto@javest.com]
> Sent: Friday, 5 December 2008 11:56 p.m.
> To: Nick Hoggard
> Cc: ubl-dev@lists.oasis-open.org
> Subject: Re: [ubl-dev] Invoice - Head Office Party
>
> Hi Nick,
>
> there are several parts where you can specify Party's information.
>
> But you need to distinct the role of each party to understand where you
> can put the information.
>
> Is your Head Office the Accounting centre ?
> Is your Head Office the Legal Address ?
>
> Below some samples for the Customer side:
>
> cac:AccountingCustomerParty
>
> cac:Party (the accounting customer party)
>
> cac:Party Tax Scheme (to specify the Party registered address for
> tax purposes)
>
> cac:Party Legal Entity (to specify the Legal address of a company)
>
> cac:Agent Party (a party who acts as an agent of this party)
>
> cac:BuyerCustomerParty (a party who is different from the accounting
> party)
> ... same structure of the AccountinCustomerParty
>
> If your Party is just a Delivery address you will have to use the
> Delivery
> party available below in the UBL document structure.
>
>
> If your organization is more wide, you will have to use the
> UBLExtensions
> where you can pratically specify any content from any namespace, even
> from
> UBL itself. So you could reuse an UBL Party aggregate (ABIE) as an
> extension.
>
> Best regards
>
> Roberto Cisternino
>
> P.S. you could benefit of using the free UBL Swinger tool to prototype
> your UBL instances (www.javest.com)
>
>> Hello,
>>
>>
>>
>> I'm currently using the UBL 2.0 specification as part of an
> integration
>> project. So far we have avoided the need to customise the
>> specifications in any way, however I'm struggling with finding the
>> correct location to populate the Head Office Party details for the
>> Seller Customer Party or Accounting Supplier Party elements of the
>> Invoice schema.
>>
>>
>>
>> The scenario we working through is that the Seller Customer Party is a
>> branch of a larger organisation. It is important to us to know the
>> organisation that the branch is affiliated with, however it is not
>> immediately obvious how to achieve this using the standard UBL specs.
>>
>>
>>
>> Does anybody have any suggestions on how this could be approached?
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Nick Hoggard
>>
>>
>>
>>
>> This communication, including any attachments, is confidential. If you
> are
>> not the intended recipient, you should not read it - please contact me
>> immediately, destroy it, and do not copy or use any part of this
>> communication or disclose anything about it. Thank you. Please note
> that
>> this communication does not designate an information system for the
>> purposes of the Electronic Transactions Act 2002.
>>
>
>
> --
> * Document Engineering Services Ltd. - Associate Director
> * UBL Italian Localization SubCommittee (ITLSC), co-Chair
> * UBL Online Community editorial board member (ubl.xml.org)
> * Italian UBL Advisor
> * OASIS NEWS Italian translator
>
> Roberto Cisternino
>
> mobile: +39 328 2148123
> skype: roberto.cisternino.ubl-itlsc
>
> [UBL Technical Committee]
> http://www.oasis-open.org/committees/ubl
>
> [UBL Italian Localization Subcommittee]
> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl-itlsc
>
> [Iniziativa divulgativa UBL Italia]
> http://www.ubl-italia.org
>
> [UBL Online Community]
> http://ubl.xml.org
>
> [Gruppo Esperti UBL] (...in avviamento)
> http://www.ublguild.org/
>
> [Free UBL Writer @ JAVEST]
> http://www.javest.com
>
>
>
>
> This communication, including any attachments, is confidential. If you are
> not the intended recipient, you should not read it - please contact me
> immediately, destroy it, and do not copy or use any part of this
> communication or disclose anything about it. Thank you. Please note that
> this communication does not designate an information system for the
> purposes of the Electronic Transactions Act 2002.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org
>
>
--
* Document Engineering Services Ltd. - Associate Director
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor
* OASIS NEWS Italian translator
Roberto Cisternino
mobile: +39 328 2148123
skype: roberto.cisternino.ubl-itlsc
[UBL Technical Committee]
http://www.oasis-open.org/committees/ubl
[UBL Italian Localization Subcommittee]
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl-itlsc
[Iniziativa divulgativa UBL Italia]
http://www.ubl-italia.org
[UBL Online Community]
http://ubl.xml.org
[Gruppo Esperti UBL] (...in avviamento)
http://www.ublguild.org/
[Free UBL Writer @ JAVEST]
http://www.javest.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]