Announce ! Accounting software module

I've taken a look at the code.

1) Be sure to follow the Drupal coding guidelines. I noticed that not all functions are prefixed with the module name, that you're missing braces for if-else statements, etc.

2) You are outputting HTML in a few functions, but those are not theme functions.
Use theme functons / theme files (tpl.php) for presentation.

3) Avoid the use of globals if you can

4) No need for the GPL notice at the beginning of each file, all Drupal modules are GPL by default (and a license file is added by the d.o packaging script)

Fixing those will help you get the code into drupal.org, and receive more feedback.

This is interesting.

Try to make it modular, so people can add things to it they need via an API, for example an Invoicing module to send invoices by email (perhaps PDF), a Salary module, a Tax module, Manufacturing, ...etc.

This will allow it to develop into a full accounting system, customizable to people's needs without hacking its code, only adding to it modules as needed.

It is far better if this is made into a module that lives on Drupal.org itself. Many more people will see it, will report bugs, will submit patches, and you can have co-maintainers as well.

This means you have to use CVS for sometime, until Drupal.org moves to Git, then you will be back to Git after that.

But the price is worth it in the long run. Apply for a CVS account now.

Funny, I just started writing my own Drupal double-entry accounting system, basically aiming for a web-based version of GnuCash- I was going to call it DruCash :) But it looks like you've made more progress than me. I'm interested to see where this goes.

Looks promising, one feedback is currently you number voucher but don't allow for a descriptive text. It seems showing text instead of (or in addition to) the voucher id would make for a friendlier interface when looking at lists.

There are 3 important things I think is important to remember/consider -

1) yes, do it, many people including me now, are looking for a solution like this, we are willing to help on code and support you on your quest

2) join forces - always look for similar modules and see how and if you can work out common roadmap, exchange ideas and build kick ass product in cooperation with other tallents and

3) use all powers of existing modules - views 3, cck 3, flags, rules, tokens, Ctools and all the rest of super modules and APIs that has most of work done for you so far, be careful with modules like ubercart, its awesome module, but does not exploit other modules as much as it could and use a lot of own/custom/legacy approaches.