[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changing tax.pm in 1.21 for a new tax which replaces two old taxes



On Fri, Jul 9, 2010 at 8:03 AM, Gerald Chudyk <..hidden..> wrote:
> On Wed, Jul 7, 2010 at 10:39 AM, Chris Travers <..hidden..> wrote:
>> I'll look into it this afternoon.
>>
>
> No luck with this one yet?
>
> Regards,
> Gerald.

Hi Gerald,

I have found a sort of work-around to this problem. We're in BC as
well, and I was getting a little desperate so I started playing around
with the tax table. Here is my tax table now:

fred_ledger_db=# select * from tax;
 chart_id | rate | taxnumber |  validto   | pass | taxmodule_id
----------+------+-----------+------------+------+--------------
    10037 | 0.05 | 816261424 | 2010-06-30 |    0 |            1
    10037 |    0 |           |            |    0 |            1
    11106 |    0 | 816261424 | 2010-06-30 |    0 |            1
    11106 | 0.12 | 816261424 |            |    0 |            1
    10039 | 0.07 | R470251   | 2010-06-30 |    0 |            1
    10039 |    0 |           |            |    0 |            1
(6 rows)


10037 - GST
10039 - PST
11106 - HST

What this basically does is put $0.00 HST line item on all old
invoices before the HST switch. Then, for all new invoices July 1st
forward, the 12% tax is applied for new invoices...

It appears to be working, but I'm still testing.

The only issue is that I had to do this directly in the database. The
application would not allow me to change the taxes around this way (I
was getting the same error you initially were asking about)...but this
may be due to something that I did here, who knows.

I read through the thread and perhaps I missed it, but I didn't see
that this was tried already. If you find any issues with this setup,
could you let me know? I will do the same.

Cheers,
Angus