Re: Tax account creation: how to 'detect' tax accounts?

[John Locke <..hidden..>]

Hi,

To summarize what the system currently has available (and how I think
it's supposed to work) the "tax" stuff is controlled at several levels:

1. COA account -- whether an account contains tax transactions (and
which screens to make it available on)

2. Customer/Vendor account -- whether a particular tax applies to a customer

3. Parts/Services -- whether a particular account applies to a part or
service

... and then if a tax applies to both part and customer, the resulting
calculation is applied to an invoice/order.

I hear people saying (and we need this too) that we want to be able to
change the above for a particular line item, adding

4. Line item is taxable.


In 1.3, there is a new "taxform" checkbox on invoice lines, but I have
no idea what that's for -- is that to override the default behavior? If
not, I think it would be useful to have something like this -- generally
to exclude tax from an item that would normally include tax. In our
case, for customers who purchase both wholesale and retail -- sales tax
applies to wholesale but not retail. But then we get into the reporting
issue, because revenue from these sales would need to get reported to
the state in a different account. So better might just be to make
wholesale a completely different part, associated with a different account.

But there is one other case -- destination-based sales tax. Currently
our e-commerce system correctly does an address lookup with the state to
get the correct sales tax rate and location code we need to report for
taxable sales. LSMB of course does not. And since Washington currently
has something like ~2000 individual locations, with varying tax rates, I
think the other scenario, until we can build the appropriate tax module,
is to just allow a person to calculate the appropriate tax (or in our
case, post it from the other system that already handles it correctly)
and add it as a separate line item to the invoice so everything matches
up. So I guess I'd like to see some sort of invoice-level setting for
"apply tax automatically" vs. "add tax manually", and with the latter, a
spot to put in the tax and enter an appropriate location code and rate
that can be correlated in the future, in a spreadsheet download if
nothing else.


Cheers,
John

On 06/20/2011 05:55 AM, Chris Travers wrote:
> On Mon, Jun 20, 2011 at 5:24 AM, Michael Richardson <..hidden..> wrote:
>>>>>>> "Luke" == Luke  <..hidden..> writes:
>>    Luke> Why?
>>
>>    Luke> I mean, I know it would be kind of nonsensical to uncheck that box after
>>    Luke> the fact, but if for some reason someone really wanted to, maybe they
>>    Luke> should be able to.
>>
>>    Luke> So I'll ask the question: is there any conceivable reason why someone
>>    Luke> might want to uncheck a tax account?
>>
>> Because the tax in question has been abolished or it applicability has
>> changed, and new stuff shouldn't have it applied ever.  But, alas, there
>> are things that need to be back dated or which a government tells you
>> that you should have done it to.
>>
> The only legitimate reason I can see would be if someone checked it by
> accident and wanted to uncheck it before things were really
> configured.  It seems to me the simple answer is to disallow
> unchecking when the account exists in the tax table, i.e. has already
> been configured as a tax account.
>
> Best Wishes,
> Chris Travers
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Ledger-smb-devel mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel