[Web-erp-developers] Understanding Tax structure

[Phil D. <ph...@du...>]

In the example Gouda is alway TaxLevel 2 - from the single stockmaster
entry.
Tulips always taxLevel 3. These levels are not unique to each stock item -
daffodils would probably also be level 3 and any other item that is taxed in
the same manner as daffodils and tulips. Similarly TaxLevel 2 is for all
those items that should be taxed at 6% VAT for sales within TaxAuthority 1 -
VAT, 0% in TaxAuthority 2 and 0% in TaxAuthority3.


Dick, I have actually already coded all this up and it seems to work ok. I
take your point in that the difficulty is in explaining how it works and how
to set it up - I will start work on that perhaps using some of our examples
from our discussion. Perhaps if I send you the latest scripts together with
our example stock items you may start to feel more comfortable with this? I
am happy to change anything that you're not happy with.

There are a number of changes to the db too so I made up an SQL script to
allow the upgrade from 2.7 to 2.8 more without losing the data. I think I
should make such a script with each new release and update the install
instructions.

What I haven't done is the script to modify the tax rates and adding and
deleting of tax levels -ie the manipulation of the data in TaxAuthLevels.


Phil

----- Original Message -----
From: "Stins, D.R." <d.r...@wo...>
To: "Phil Daintree" <ph...@du...>
Sent: Thursday, February 12, 2004 7:38 PM
Subject: Re: Re(2): [Web-erp-developers] Re: Level Description


> Phil,
>
> I will setup the tables (later)
>
> In you example, what are you doing when Gouda is related in taxauthority 1
> to level 1
> and in taxuthority level 2 and Gouda is related in taxauthority to level
3?
>
> When I understand you quite well you want to setup a special dedicated
level
> for Gouda.
>
> With best regards,
>
> Dick Stins
>
> ----- Original Message -----
> From: "Phil Daintree" <ph...@du...>
> To: "Web ERP Developers" <Web...@li...>
> Sent: Thursday, February 12, 2004 3:33 AM
> Subject: Re: Re(2): [Web-erp-developers] Re: Level Description
>
>
> > Dick,
> >
> > I'm getting a little lost ...
> >
> > Could you make up the SQL for the tables as you think best and the
schema
> > for how it might work and then I can get the whole picture. I am sorry
to
> be
> > a bit stupid on this. I have in my mind how I think it should work but
> > clearly this does not work for you. I must understand what you have in
> mind
> > and the SQL is much easier than a whole lot of words!!
> >
> > > Now back to the functional discussion:
> > > - one taxlevel per stock item is not good enough. This might be only
> > > appropriate when you have to deal with one and only one taxauthority
per
> > > stock item.
> > >
> > > When we decide that one taxauthority is appropriate, we can create a
> > unique
> > > index at the level column in the taxauthlevel table. This implies that
> we
> > > follow the theory: a unique key level in the authtaxlevel table and a
> > detail
> > > level key in the stockmaster.
> >
> > What I am proposing is as follows:
> >
> > Tax Authorities
> > Tax ID  TaxAuthorityDescription
> > 1                VAT
> > 2                Export
> > 3                Customer Pays VAT
> >
> > the field TaxID has a matching field in CustBranch
> >
> >
> > TaxAuthLevels
> >
> > Level    TaxAuthority    Rate
> > 1                1                    0
> > 2                1                    .06
> > 3                1                    .15
> > 1                2                    0
> > 2                2                    0
> > 3                2                    0
> > 1                3                     0
> > 2                3                    0
> > 3                3                    0
> >
> > The field Level has a matching field in StockMaster
> >
> > Consider Gouda cheese which is defined as having a tax level 2 in the
> stock
> > master. We sell Gouda to a customer's branch in Amsterdam who is set up
as
> > belonging to TaxAuth 1 - VAT.
> >
> > The tax rate is found:
> >
> > SELECT Rate FROM TaxAuthLevels WHERE Level=2 AND TaxAuthority=1 - VAT;
> >
> > and returns 6%.
> >
> > Consider tulips which are defined as having a tax level 3 in the stock
> > master. We sell tulips to the same customer in Amsterdam who is set up
as
> > belonging to TaxAuth 1 - VAT.
> >
> > The tax rate is found:
> >
> > SELECT Rate FROM TaxAuthLevels WHERE Level=3 AND TaxAuthority=1;
> >
> > and returns 15%.
> >
> > We also sell tulips to the same customer but to their branch in Zurich -
> > these are special none perishable tulips - the Zurich branch is set up
as
> > belonging to TaxAuth 2 - Export.
> >
> > The tax rate is found:
> >
> > SELECT Rate FROM TaxAuthLevels WHERE Level=3 AND TaxAuthority=2;
> >
> > and returns 0%.
> >
> > So whilst TaxLevel is only one per item in the StockMaster, there are
> > several in the TaxAuthLevels table it is only in combination with the
> > TaxAuthority that we get a unique rate - hence the table definition.
> > TaxLevel in the TaxAuthLevels is not unique.
> >
> > Still nervous ?
> >
> > Phil
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Web-erp-developers mailing list
> > Web...@li...
> > https://lists.sourceforge.net/lists/listinfo/web-erp-developers
> >
>
>