[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-dev] US Taxes
For every tax scheme (relating to tax jurisdiction) there would be 1) at document header level, inside taxtotal : a tax subtotal with an (perhaps arbitrary) tax category tax type code 2) at document header level, inside supplier party: a party tax scheme possibly with relevant jurisdiction address and with a tax type code corresponding to that in 1) example (from UBL 2.0) for two tax types (maybe state and county) 1) Invoice would have two tax total subtotals at document level <TaxTotal xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxSubtotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxCategory> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">A</TaxTypeCode> </TaxScheme> </TaxCategory> </TaxSubtotal> <TaxSubtotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxCategory> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">B</TaxTypeCode> </TaxScheme> </TaxCategory> </TaxSubtotal> </TaxTotal> 2) would have two corresponding party tax schemes <AccountingSupplierParty xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"> <Party> <PartyTaxScheme> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">A</TaxTypeCode> <JurisdictionRegionAddress> <AddressLine> <Line xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">foo</Line> </AddressLine> </JurisdictionRegionAddress> </TaxScheme> </PartyTaxScheme> <PartyTaxScheme> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">B</TaxTypeCode> <JurisdictionRegionAddress> <AddressLine> <Line xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">bar</Line> </AddressLine> </JurisdictionRegionAddress> </TaxScheme> </PartyTaxScheme> </Party> </AccountingSupplierParty> It is optional (in UBL) to have corresponding tax details at line level (or is that mandatory in any US states? I don't know). Here is an example of having one line with tax for one tax scheme and another invoice line with tax for another scheme (not sure if that ever happens) <InvoiceLine xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"> <ID xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"></ID> <LineExtensionAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">50</LineExtensionAmount> <TaxTotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxSubtotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxCategory> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">A</TaxTypeCode> </TaxScheme> </TaxCategory> </TaxSubtotal> </TaxTotal> <Item>...</Item> </InvoiceLine> <InvoiceLine xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"> <ID xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"></ID> <LineExtensionAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">50</LineExtensionAmount> <TaxTotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxSubtotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxCategory> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">B</TaxTypeCode> </TaxScheme> </TaxCategory> </TaxSubtotal> </TaxTotal> <Item>...</Item> </InvoiceLine> Or one line might have tax for both tax schemes <InvoiceLine xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"> <ID xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"></ID> <LineExtensionAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">50</LineExtensionAmount> <TaxTotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">20</TaxAmount> <TaxSubtotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxCategory> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">A</TaxTypeCode> </TaxScheme> </TaxCategory> </TaxSubtotal> <TaxSubtotal> <TaxAmount xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" currencyID="USD">10</TaxAmount> <TaxCategory> <TaxScheme> <TaxTypeCode xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">B</TaxTypeCode> </TaxScheme> </TaxCategory> </TaxSubtotal> </TaxTotal> <Item>...</Item> </InvoiceLine> hope that helps ---- Stephen D Green On 18 March 2011 13:50, GORON Magali <MAGALI.Goron@atosorigin.com> wrote: > Hi All, > > We need to implement US taxes in UBL 2.1. > > So we need to describe tax at city level, tax of county level, tax at state > level and tax at country level. > > Is there any example of that kind of implementation? > > > > Thanks in advance, > > > > Magali. > > ________________________________ > > Ce message et les pièces jointes sont confidentiels et réservés à l'usage > exclusif de ses destinataires. Il peut également être protégé par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immédiatement l'expéditeur et de le détruire. L'intégrité du message ne > pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin > ne pourra être recherchée quant au contenu de ce message. Bien que les > meilleurs efforts soient faits pour maintenir cette transmission exempte de > tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa > responsabilité ne saurait être recherchée pour tout dommage résultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended solely > for the addressee; it may also be privileged. If you receive this e-mail in > error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Atos Origin group liability cannot be > triggered for the message content. Although the sender endeavours to > maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]