Community mailing list archives
Re: Tax Retencion / Tax Withholding :: Common approachby
El 18/10/2014, a las 19:40, Juan José Scarafía (ADHOC) <email@example.com> escribió:
Hi David,We are from Argentina and would like to colaborate and participate on this developement.Actually we are managin retentions in account.vouchers, with specific journals. To group retentions in one payment, we are using account_voucher_receipt.Looking into your graphs I think that in Argentina we use different terms. With:* Retentions / withholdings: we refer to amounts been retained on PAYMENTS. It depends in receiver, issuer and sum of amount that has been paid on month or similar.* Perceptions: amounts being "retained" on INVOICE (depends on receiver, issuer and invoice amounts)Retentions and percepectiosn can be from different taxes (national, provincial or municipal)Best Regards,Juan2014-10-18 18:03 GMT-03:00 David Arnold <firstname.lastname@example.org>:Hi Community in South America and elsewhereif 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 propose to make some kind of comprehensive retention framework. The situation right now is rather unconsolidated.This is not good enough.I want to invite you to work on this subject together. Please find annexed a first mock-up of some basic models (invoice/partner). The idea is to depart from mock-ups of views of important models and refine a common perception of how thigs should be presented. Models to inlude are: Invoice and derivatives (PO/SO/etc), Partner, ProductOnce we have that, it will be very easy to see how far common rings of abstraction could go as far as to the logic and where the task could be handed over to local maintainers.Please give feedback prefereably with annotated screenshots.Saludos CordialesDavid Arnold
David Arnold BA HSG / Analista
315 304 13 68/ email@example.com
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.