Community mailing list archives

Tax Retencion / Tax Withholding :: Common approach

El Aleman, David Arnold
- 10/18/2014 11:33:34
Hi Community in South America and elsewhere

if you know, what retentions / withholdings are read on, else skip that mail.

As discussions in the past have been rather technical on this subject, I wanted to propose the idea to make some kind of comprehensive Retention Framework. The situation right now is, that every localization project has more or less his own approach and coordination is still at a low level.

My idea is to define requirements as a Screen MockUp as Odoo recently does, as communication is simply more effective among non-technical people.

A good starting point would be to define three forms and annexed search and tree views. Those are:
- Product
- Partner
- Invoice

I'm looking for a good tool with adequate sharing capabilities in order to built a first mock-up and will then invite anyone to join. Any hints?

The idea is that participants try to hide away every country specific logic and try to identify a common framework of presentation (in invoices, parters, products, etc.)

It would be a test, not sure if it will work...

Saludos Cordiales
David Arnold

David Arnold BA HSG / Analista
315 304 13 68/

devCO - empresa de consultoría de sistemas (en fundación)

This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. devCO is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.