Accounting Systems on Linux?

cuebei asks: "OK, Slashdotters - let's talk accounting systems for small-mid sized businesses. With the popularity of Linux servers running various e-business services such as web, directory, mail, commerce, etc, it only makes sense for Linux to become a more mainstream platform in the business world. One of the areas where I can foresee Linux being used extensively is in the area of accounting. Linux is both reliable and scalable, two key requirements for any accounting package. So who uses Linux for HR/Accounting? What options are out there? Open-source or commercial? If you were starting your own business and standardized on Linux as a platform, what accounting package would you use and why?"

Comments

Accounting is not the driving software package!

[MantridDronemaker]

In my experience (manufacturing, specifcially chemcial manufacturing), the accounting software is almost irrelevant. The trick is finding a suitable manufacturing package and then you just use whatever accounting package that works with it.

That being said I'd be ecstatic if there was good process manufacturing software available for Linux! But the gamut of features would be rather daunting- solid flexible modules for inventory with lot tracking, formulations, hazmat and environmental reporting as well as MSDS and labelling, production BOM, scheduling, heck throw in HR...and of course the mentioned accounting package.

Heh, give me all of this and our company switches to Linux!

KBooks

[Dan D.]

I'm building an application to work like quickbooks (for kde, as if you couldn't guess). I probably shouldn't post this because its completely unusable and I don't want to give anyone the wrong impression. :) But its on topic, and I figure its a good place to beg for helpers. If you'd like to help me, I'll hook you up with the GPL'd source when you drop me an email. Especially anyone that has the gumption to maintain the sourceforge front-end.

Nathan.

SAP-DB as DBMS

[Christopher B. Brown]

I've pointed it out several times, and apparently those that decide what stories are "interesting" consisidered it not to be of any interest.

The one problem with SAP-DB at this point, from the "can we make it ubiquitous" perspective, is that it's a real pain to compile.

It was coded on mainframes, and the suite of compilation tools are based on that approach. Thus the code base (and compile process) is "cryptic upper-case 8 character names everywhere."

It's a desparate pain to try to compile it, so it has not quickly moved towards being ubiquitously available. Red Hat doesn't include it in trivially-installable manner in the manner of MySQL or PostgreSQL. Debian folk can't do apt-get install sapdb .

Give it some more time, and get some more public input, and it'll get more attention.

Of course, that would merely bring us to the point where it would start being an interesting "data storage" substrate for an accounting application. Then comes the 'real" work of determining what tables, fields, relationships, and such exist, and how to manage UIs...

Finally, a Slashdot topic I know too much about

[PMCausey]

I am a CPA in private practice, and for many years I sold accounting software to small and medium sized businesses. At the risk of trolling for flames, I would have to STRONGLY suggest that you not use Linux for accounting in a small to medium sized business environment. (Note: This is defined a company up to $50,000,000 U.S. in revenue) Why?

1. Unless you are blessed with outside accountants like me who read Slashdot and know the difference between Debian and Mandrake, your choice may create significant problems at month/year end when one of my many slightly to nearmost completely computer illiterate colleagues tries to either download/extract your data or wants you to generate a file that to import into either Excel or their audit/trial balance package. Reason: 99.9999% of tax programs/CPA audit software/CPA trial balance software is written in Windows, and all of it takes an Excel file. (Hint: Not being able to do this quickly/easily = higher costs (annually)).

2. Your CFO/controller will have a lot easier time finding people who can work in the Windows environment to do the basic grunt work of entering invoices, bills, and time so the system can print checks (including your own paycheck). In some 15 years in public accounting, highly computer literate, easily trained, low cost clerks are about as easy to find as naturally occurring penguins in the Sahara. Not everybody runs (or wants to run Linux). Most everybody knows Windows, and your clerks will also know some Excel and at least one or two Windows accounting packages.

3. As much value as I see in open source, I would have a very hard time accepting an open source accounting solution as a CPA auditing a set of books. Unless the company is one of the Generals (Foods, Tire, Motors) or equivalent and possesses the internal programming staff and the full time accounting staff to verify that the stuff works right, it's not worth the risk to be a beta site and discover the bugs. Folks, were talking about real money here, and most of my colleagues would be real skittish about any system that "somebody downloaded from the Internet" (It's bad enough to do that with established, old-line accounting sofware companies, and I've got the scars to prove it.) And if you can't convince us that the books aren't bogus (intentionally or otherwise), good luck with the banker.

In short, yes, accountants are conservative and prefer things that we KNOW will work consistently and correctly all of the time. We also like things that have a low total cost of ownership, and unfortunately, Linux and accounting packages don't have it right now. My "as close as I'm gonna get to a professional recommendation without sending a bill" is live with an off-the-shelf, low cost, Windows (there, I've said it) package such as DacEasy, Best BusinessWorks, or Peachtree. Just promise me no QuickBooks, OK?