omfgppc - 2009-02-27

You have subscribed to a wiki page or wiki category on "xTuple" for change =
notification.

The "EnhancedTaxInternationalization" page has been changed by jrogelstad:

   * Maintenance should be streamlined where possible.
  =

  =3D=3D New Terms and Definitions =3D=3D
- Specific information concerning United Kingdom Tax reporting requirements=
may be found here: General Information and Links:
- =

- [[http://www.hmrc.gov.uk/vat/vat-international.htm|http://www.hmrc.gov.uk=
/vat/vat-introduction.htm]]
- =

- http://www.hmrc.gov.uk/vat/vat-international.htm
- =

- http://www.hmrc.gov.uk/vat/records-keeping.htm
- =

- Record Keeping
- =

- http://www.hmrc.gov.uk/vat/records-keeping.htm#3
- =

- Sales and Invoicing
- =

- http://www.hmrc.gov.uk/vat/records-valid-invoice.htm#2
- =

- Purchase and Vouchering
- =

- http://www.hmrc.gov.uk/vat/records-valid-receipt.htm#5
- =

- http://www.hmrc.gov.uk/vat/records-valid-receipt.htm#5
- =

- This is the place to define new words and phrases to be used in the appli=
cation and the documentation. If this feature introduces a new concept or c=
hanges the semantics of an existing concept in the application then define =
it here. Define it even if you think the definition should be obvious, sinc=
e your definition might not match the definition used by the reader, like s=
o:
- =

   . '''Tax Assignments'''
    * Tax assignments map tax authority and tax type combinations to multip=
le tax codes. Formerly known as tax selections.
   . '''Tax Code'''
@@ -65, +41 @@

  [[http://www.xtuple.org/mantis/view.php?id=3D8274|8274]] Add tax calculat=
ions to purchase orders.
  =

  [[http://www.xtuple.org/mantis/view.php?id=3D8411|8411]], [[http://www.xt=
uple.org/mantis/view.php?id=3D8496|8496]], [[http://www.xtuple.org/mantis/v=
iew.php?id=3D8221|8221]] Rounding problems on tax calculations
+ =

+ There is a forum posting on the topic of VAT handling [[javascript:void(0=
);/*1235594832210*/|here]].
  =

  =3D=3D Conflicting Features =3D=3D
  This specification will call for creating a one to many relationship betw=
een tax types and tax codes which is a major paradigm shift from the curren=
t 3 element A, B, C field code method. Tax codes will be specified to only =
include only one G/L Account mapping. A large amount of historical data usi=
ng the field based paradigm would have to be converted in sales orders, inv=
oices and sales history to complete this transition. In large databases thi=
s will likely require substantial upgrade time. In addition, a complete swi=
tchover to this methodology will likely "break" existing reports and forms =
that users have customized that rely on existing tax calculations. These ob=
stacles will make upgrading to this version a substantial task for some use=
rs. In order to defray that effort it will be necessary to support the lega=
cy structure for at least one version and provide a mechanism to convert da=
ta and report structures over extended period while still being able to use=
the system with the new method moving forward.