CiviCRM Community Forums (archive)

Ok. My testbed is all updated and I'm digging into the code.

My extension has its own UI with fields to define tax types, rates and what contribution types are subject to being taxed. This will need to be changed to use the Tax Fields we have available in Accounts. There were some limitations to the Tax fields in accounts last time I looked so I'll have to check my notes and see if they have been improved upon since then. I'm pretty sure I commented on that in the Wiki somewhere.

So moving forward, I should be able to take the guts of what I've done with my extension and remove my UI and instead leverage the tax fields within the accounts framework. The tough part will still be adding our tax into the equation at checkout.

My earlier method for adding a tax was by modifying the public preProcess() function that is used in the confirm.php pages (ie: /sites/all/modules/civicrm/CRM/Contribute/Form/Contribution/Confirm.php). I pulled the total amount out, calculated my tax (saved it to DB), added it to the total and sent it off for payment.   

Moving forward, I think I'd like to be able to add the tax as a line item if I can which is then added to the total without having to influence the preProcess() function.

@lolas: With your tax modifications, how did you add your tax to the total cost? Was it treated as a line item in the invoice or was it added behind the scenes. If it's worthwhile, I'd really like to not have to reinvent the wheel.

Cheers,
Andrew

PS: If anyone wants to help, by all means chip in.

Hi all,

We have a client with an immediate need and are planning to work with Webaccess to get this into core. We are working per the specification here:

http://wiki.civicrm.org/confluence/pages/viewpage.action?pageId=83493410

Which I have been updating in the past 2-3 weeks to take into account producing legal VAT invoices/receipts (which I assume will be pretty close in nature to most countries requirements).

The current approach would cover taxes which are applied as a %, and multiple taxes applied based on the financial type but not levees or flat rate taxes.

I have some question marks about how we would interact with refunds, webforms and a few other points, but I'm hoping to work these through with Webaccess once we get clarification from the client that we are meeting their needs.

We are looking to get this signed off with the client in the next week or two so if anyone does have any feedback do let me know as soon as possible.

Best

J

 

Hi All,

As a few of you know, my tax field extension is ready for testing (https://github.com/awasson/civiTAX). It still has a few rough edges but it does indeed allow for establishing taxes, applying them to contribution types and reporting tax information in the detailed transaction report. There are no mods required to CiviCRM.

I'm in the process of writing a "roadmap" for it starting where it is today, areas that need work, the next iteration (features and improvements) and where I would like it to be long-term.

This is separate from Jamie's project but I think it might still be handy to take it for a spin on a test site to help model user journeys and look at what works and what problems may crop up. I welcome any feedback you may have and if you see anything that will be helpful in your projects I'd be happy to explain what I did and why so you can adapt it. More than likely it will be more helpful conceptually.

Cheers,
Andrew