taxes

Special thanks to CalvinHP, Claytron, and ChrisW for enthusiasm for taking on the taxes in GetPaid.

At the Plone Symposium in New Orleans, we did some collaborative design of the needs and requirements for tax infrastructure. Then, on last Friday, Calvin, Clayton, and Chris busted out the infrastructure!

Calvin's update reports:

During the NOLA sprint we put in place a few notable changes to the checkout/cart/order totaling so we can support the diverse ecosphere of taxing models around the world.

The old API used to just return a float for the call to the Tax Utility. Now the same call will return a list of dictionaries with one dict per each tax that is potentially applied to the order or configured in the system.

The next step from here would be to finish a default implementation of a ITax policy that can be registered in the site.  I would suggest we just do a simple flat tax one so people get the idea of how to develop and register their own.

That is pretty much our current status for now.  Let me if there are any other ideas floating around that we haven't thought of.



Please join the mailing list to connect around tax use cases.


You can check out the code in the repository or via buildout. This work will be part of GetPaid's next release.

Ok, so maybe it was inevitable...like death...and taxes are upon us. But this year it's different - the government is sending us money. Yes, that's right, if you've gotten your Economic Stimulus check from the IRS, please consider contributing to GetPaid!

Oh, and we are going to sprint on tax handling in GetPaid tomorrow (Friday) during the sprint day of the Plone Symposium in New Orleans. If you are interested in this, please see our evolving notes/design info and join us in #getpaid (or share your views/experience on the getpaid-dev mailing list).