Slashdot Mirror


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?"

4 of 399 comments (clear)

  1. Compliance by RazzleFrog · · Score: 5, Insightful

    I know that there are several accounting packages out there that support Linux (Computron being one) but they are mostly expensive.

    The one problem with an open-source accounting package is that accounting standards are constantly changing and the software would often have to be changed to reflect new standards. Anyone working on such a project would have to be well-versed in each of the new SFAS (Statements of Financial Accounting Standards) as they come out. That's not a fun project for a CPA let alone a layperson.

  2. Ease of Installation is important by Christopher+B.+Brown · · Score: 5, Insightful
    I've not tried installing NOLA, but keep SQL-Ledger around. I'd say you're bang-on in assessing that it's important to have the technology be readily installed.

    A prime problem with GnuCash vis-a-vis trying to get the "bleeding edge" functionality is that it is an absolute pain to get compiled. The functionality may be worth it, but if it's daunting to build, that's a problem.

    In exactly the same manner, there are all sorts of projects out there to build some really cool JavaEnterprize-Foo-Beans- Coffee-Espresso-Transactional- EE goodness; if it takes someone who's an expert in all of:

    • Apache;
    • Some Server Extension;
    • Some Java Framework Atop a Server Extension;
    • Some Application Framework that doesn't do squat until all the above pieces are running perfectly along with an interface to an RDBMS

    Excuse me if I don't jump up and down cheering at the vast complexity of this.

    In contrast, SQL-Ledger is indeed quite straightforward to set up. A bit more manually-involved than I'd like, but certainly not badly so.

    --
    If you're not part of the solution, you're part of the precipitate.
  3. Re:At the heart of the matter... by elefantstn · · Score: 5, Insightful
    "When my accounting system suddenly fails without notice, effectively putting my business OUT OF BUSINESS immediately, WHO DO I SUE?"


    The same fucking person you sue when your closed-source app running on Windows fails: NOBODY. Jesus, have you ever read a EULA? You sue absolutely NOBODY. This comment needs to be rated -1 Troll or -1 Total Idiot immediately.
    --
    If it ain't broke, you need more software.
  4. Re:SQL Ledger and Security. by jayed_99 · · Score: 5, Insightful

    His comment was more along the line of accountants are not script kiddies, so we don't need to worry too much. That is probably reasonable, too.

    Sorry, but I have to disagree. Accountants are worse than script kiddies. When they go bad they know exactly what they're looking for, and they know how to manipulate the data to hide any unusual transactions. Maybe the mythical bad accountant doesn't personally have the skillz to crack a system, but -- I assure you -- they are more than capable of finding a partner to help them.

    I've been doing SAP R/3 security for a handful of years, and I could tell stories that would make every CFO in the world crap their pants.

    You have to realize that we're talking about being able to manipulate real money. You can't treat it like monopoly money because it's just a bunch of numbers on a UI. You need to control (and be able to audit) access to an enterprise accounting system just like you would protect and audit access to a giant pile of dollar bills that is equivalent to your company's net worth. You've also got to realize that admin-style access to an accounting system means that you can make changes to things that happened in the past. So I could go back two months ago and insert a bogus purchase order for $99.00 (or any other small amount that misses the executive-approval-radar). Then, this month, I could pay it -- to that anonymous bank account I have. I could do this over and over with multiple fake purchase orders for months and months. And since no one could audit the transactions, they would only know that they were missing an ass-load of $99.00 transactions. (The real-world implementation is a bit more complicated, but you get the idea).

    If your company has $500,000 of revenue a year, and the two accounting people are personal friends, you probably don't need to worry about embezzelment, fraud, fake purchase orders, etc. (I personally would worry about them, but I'm a paranoid security guy).

    If your company is pulling in a few million dollars a year, and you hire random accounting people then, yes, you need to be able to audit their activities.