Archive for the 'Bookkeeping Notes' Category

NetSuite Goes Public

Congratulations to the team at NetSuite, the ERP, CRM and e-commerce software company which went public recently. I just read a little bit about them and it appears that they are targeting companies with between 100 and 1000 employees, whereas Quickbooks targets 100 employees or less.

Where does PBooks fit in? Well the database should be scalable to support companies of that size, however since I have very little experience with the accounting systems of larger companies, basic things like the user interface might not make sense when you dramatically ramp up the number of accounts, transactions, and so on. Its interesting to think about - even at my small company, the number of transactions is fairly significant, and its pretty easy to get lost in the sea of data if you’re not paying attention.

Dogfooding

If you are unfamiliar with the concept of “dogfooding”, see here.

It makes a big difference in the start of a project to have a ready use case, and thanks to my own personal use of PBooks, I just added a terrific new feature. Well, I think its terrific. :-)

The feature is similar to the matching process, which is used to match transactions to additional accounts. For example, if you have a CSV file containing credit card transactions, in bookkeeping terms, those only represent half the journal entry. You can import those transactions into the ledger, and the matching page will show ledger transactions without a corresponding entry.

On the flip side, the posting page will display only the journal entries which need to have entries posted to the ledger.

If your more of a business process user as opposed to a accounting / bookkeeping user, this might not sound too exciting, but I think its pretty cool. I was able to implement this feature fairly easily thanks to the relatively new journal entry status field, which is a tiny int so it shouldn’t have too much of an increase on the database size.

Also, in my personal use of pbooks, I’ve ironed out several bugs which were hiding from general view. Since most of the bookkeeping work I’m doing is prior, I haven’t worked too much with the new business process models, but I will next week when my company sends out invoices, as well as whenever we receive a payment and / or make a deposit.

PBooks Usage Notes




I just spent a few hours working on PBooks and I took these notes:

* Would it be helpful when viewing the ledger to have the start default to the start of the accounting period? It would help me.

* Creating invoices through PBooks is the way to go so that you don’t have to split payments based on revenue source - i.e. some invoices include hosting and professional services.

* Absolutely need a way to isolate entries which need to be posted to the ledger

* Found myself going back and forth between the journal and the ledger, having to fix entries and then repost to the ledger. Not fun.

I mostly spent the time entering data from bank statements and double checking the running balance. I also made several split transactions based on deposits, which reminds me, I want to share with prospective pbooks users how helpful photocopies of deposits are. When I was entering the bank transactions, I would look at a deposit and wonder, “Huh, I wonder what that was?” Several times the photocopy I made of the deposit was incredibly useful, reminding me that the deposit was made up of four or five items.

Everything ran OK, I hit and fixed a couple of small bugs, but in the end I’m quite pleased with how the software is performing.

Super Administration

Limited privileges are key to a well setup accounting system. Some people will have data entry capabilities, others will have audit and approval capabilities. Currently Pbooks is not setup with divisions of privilege, but it is most definitely designed to provide this type of functionality. One of the tasks I’ve listed in the trac is to setup some basic ids for functions which will likely be isolated to different users or groups.

That task is currently slated for “the future”, and PBooks will need something in the meantime to separate more complex administration tasks from the standard bookkeeping tasks. Right now I’m leaning towards writing a command line administrator script, similar to the trac-admin script which is used to setup user permissions. Just an idea I wanted to jot down….

UPDATE: Actually I have been working on this task a little bit the past few days (mid-October 2007). First I was stumped by the lack of php5-readline in the debian repositories, but I’ve since worked that out. I’m moving this task up in priority because having such a tool will most definitely assist in development, testing, and debugging. Chances are the initial consumers of PBooks will be most likely technically capable, they might even appreciate such a resource. I hope so!

Invoices




Here’s my current, incredibly inefficient, invoicing process:

  1. Tally up work times for each client (we use a client specific time tracker - this is easy)
  2. Create a spreadsheet for each client, sum up the rates, discounts and totals (could easily be done using our time tracking software, except for rates and discounts)
  3. Create invoices in Quickbooks using Parallels - definitely need to take this step out of the loop!
  4. Export Quickbooks invoices to PDF
  5. Mark the work tallied in step one as invoiced, noting the invoice number on each (super easy)
  6. Enter the invoices into PBooks

Each month it takes me about four hours, when it could be done in about 1 hour. With regards to bookkeeping and invoicing, its a good time to dedicate to bookkeeping, paperwork, and bank reconciliation. That stuff isn’t as pressing as invoices (if you don’t send invoices, you don’t get paid), but is a similar process to go through (tally, categorize, data entry, etc.) you might as well do them at the same time. I’ll do it that way next month! :-)

I did make some really nice progress on the invoice form though, here’s a quick screen shot:

PBooks Invoices Form Screenshot

Before you ask, PDF invoices are in the works too!

Donations to PBooks?

Howdy - Albert here. Just wanted to mention really quick that the donation button you see to the right is not meant to be “nagware” or “guiltware”. PBooks is free and open source software, and you don’t have to contribute if you don’t want to.

We do welcome your contributions, and your contributions other that monetary donations would honestly be more helpful at this point in time. If you have a moment, please register and introduce yourself in the forums, download and test out the software, or help spread the word by linking to the blog or to the trac project.

The donate button is there only if you are feeling generous and are compelled to throw us a bone. Fear not, lack of donations will not slow down or halt pbooks development. As Kermit the frog always says, we’re “moving right along, dugga dunk dugga dunk”.

I also want to mention here that if you are interested in a new feature or integration with other systems, commercial support is available.

Thanks again for your interest!