openerp-expert-accounting team mailing list archive
-
openerp-expert-accounting team
-
Mailing list archive
-
Message #00309
Re: cash book / petty cash
If really the point is "I don't want to input an analytic value for petty cash", my proposal should be : then at least give a default value ! the accountant can change it if he has directly the information. If not, he can see the posting in the analytics & do corrections if there is a need
Regards
Alain
Alain Rivet
Partner
High-SEA scrl
alain.rivet@xxxxxxxxxxx
+32 476 328 784
Av Voltaire, 3
1300 Wavre
Belgium
www.high-sea.be
-----Message d'origine-----
De : openerp-expert-accounting-bounces+alain.rivet=high-sea.be@xxxxxxxxxxxxxxxxxxx [mailto:openerp-expert-accounting-bounces+alain.rivet=high-sea.be@xxxxxxxxxxxxxxxxxxx] De la part de Ferdinand Gassauer
Envoyé : vendredi 9 avril 2010 14:41
À : openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
Objet : Re: [Openerp-expert-accounting] cash book / petty cash
Am Freitag 09 April 2010 12:29:13 schrieb Davide Corio:
> Il giorno gio, 08/04/2010 alle 19.50 +0200, Claude Brulé ha scritto:
> > Most of sotware I've seen are doing this.
> > I doesn't meam that we should do the same as the others, but we shout
> > think about it.
>
> Exactly, moreover because SMEs accountants often deal with petty cash
> management and not with analytic accounting.
>
> There's no easy way at the moment to manage very common things like "i
> bought the train ticket and now how can i register it on OpenERP?"
That's exactly the point !!!
--
Best Regards
ChriCar Beteiligungs- und Beratungs- GmbH
http://www.chricar.at/ChriCar/index.html
Dr. Ferdinand Gassauer
Official Tiny Partner
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-accounting
Post to : openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-expert-accounting
More help : https://help.launchpad.net/ListHelp
Ce message entrant est certifié sans virus connu.
Analyse effectuée par AVG - www.avg.fr
Version: 9.0.801 / Base de données virale: 271.1.1/2799 - Date: 04/08/10 20:32:00
Follow ups
References