SQL-Ledger Evaluation

[Federico S. I. <ji...@le...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi everyone,

I'm the network administrator for our company, an SME based in the
Philippines. I'm working with our accounting department to hopefully get
SQL Ledger in place. We are currently using SQL-Ledger v1.4.13, slightly
patched to fix the previous issue I mentioned with the "ORDER BY" and
PostgreSQL v7.1. I intend to upgrade this system to SQL-Ledger v1.6.0 as
soon as possible, but in the meantime I'd like to share the report sent to
me by our company's accounting manager.

I have very minimal knowledge as far as accounting procedures are
concerned, so I hope those in the list who know more than me will be
patient. I'd like to get help validating the points of our accounting
manager, in the hopes that we will see if these can actually be
implemented with SQL Ledger but he just hasn't figured out how, yet.
Alternatively some of the points may be useful to the development team for
the next versions to come.

I am not giving up on SQL Ledger and will keep upgrading and pushing for
its evaluation lest someone here buy Quickbooks (ugh, but the guy's good
at Quickbooks it seems although we don't have that installed here in the
office [yet, and I hope it will stay that way]) and need me to maintain
yet more Windows computers. I hope fellow list members can help me in my
"crusade". :)

Here's the report (sometimes it looks like more of a wishlist):

- -----[ Start of Report ]-----
I. Recording
   A. A/R A/P
      1. Although it supports Double entry accounting it has no feature
         that shows the accounting entry behind the transaction posted.
         This is critical for audit trail.
      2. We were not able to enter transactions with compound entries.
         Without this feature it will double our accounting work.
      3. VAT & Withholding tax automatic computation or recalculation.
      4 Limited search function.
      5. Due date recalculation.
      6. Add transaction is not linked with the complete cycle of a
         transaction to eliminate redundancy of accounting work. Eg. for
         AR transaction, SO is linked with SI and the journal entry behind
         the transaction.
      7. Add transaction template can not be edited for additional field for
         reporting purposes.
II. Reporting
   A. Customizable reports
      1. Limited customizable reports templates.
      2. Additional fields for filtering report purposes.
      3. Linking of SO, SI, and journal entry transaction to eliminate
         redundancy.
      4. Segment Reporting, & Cost center reporting???

III. Inventory
   A. Inventory Tracking and Costing
      1. Costing by FIFO, LIFO or average costing?

IV. Fixed asset monitoring
   A. Lapsing schedule

V. Audit Trail
   A. Account analysis for audit review and schedule preparation.

Comments:
The version we are evaluating basically supports bookkeeping and standard
reporting. Although I have not seen the changes in the new version, these
changes are basic accounting features in a computerized environment. We
may need a lot of time in the development before we can migrate to the
system.
- -----[ End of Report ]-----

Thanks in advance, everyone!

 --> Jijo

- --
Federico Sevilla III  :: ji...@le...
Network Administrator :: The Leather Collection, Inc.
GnuPG Key: <http://jijo.leathercollection.ph/jijo.gpg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7fdsw5rCBSJO3Rr4RAp6IAJoCBZXyGhUFkX/1cCBvq68ExqnZAACfbJln
HCVvbrlMqrhtQznsK/gkFS0=
=prie
-----END PGP SIGNATURE-----