Anthony,
> I just wanted to give everyone a heads up on the state of the treasury's
> financial accounting. This will probably precondition a cry for help :).
> Things have mostly been done on an ad hoc basis thus far. I think that this
> is normal for most young organizations.
>
> However, I have been running exhaustive searches on various accounting
> software out there over the past nine months. This is in an effort to both
> formalize how we work with projects (disbursing funds, accepting donations,
> etc) and to help keep records for our tax filings.
Yep, I think this makes sense.
> We are in a unique-ish position in that we are a non-profit that is a
> confederacy of projects. The overwhelming majority of accounting software
> out there does not come standard with critical features that we need. If
> you don't believe me that this is a problem, the software freedom
> conservancy has these same issues and they have put out a call to hire a
> developer to work on it.
Ouch - that smells wrong - I suppose it could be needed though.
> The two main features we must have is 1) a first-class notion of projects /
> accounts, and 2) a reliable mechanism for storing and associating documents
> (invoices, receipts, email, etc) with individual transactions. The
> permissioning for (1) has to be gotten right and the provenance for (2) has
> to be rock solid.
Some questions:
* Where are these feature requirements coming from? Legal counsel?
Tax/corp law?
* Is it strictly required that the *same* system handle both the
accounting and the associated documents?
* Does the solution have to be online/web based?
* Are there cost restrictions?
* How many people who end up needed to work with the software. Just a
treasurer/accountant? Each project?
> Inspired by a recent discussion with the board, I spent yesterday day
> re-researching all of the options I could think of and all of the advice
> that I have been given recently on this topic. Once again nothing really
> suits our needs -- or does so within our price range / off the shelf. Even
> tools open tools like GnuCash, Homebank, and Ledger which could
> theoretically be modified to fit our needs don't really work because the
> underlying model is so different.
What are the $ constraints? I have used Quickbooks before for a
multiproject small business and it worked very well. From some quick
Googling, it looks like there are add-ons to enable it to manage
associated documents. What were the problems identified with
Quickbooks. I was going to offer to talk to a friend of mine who is a
CPA, but I have a feeling I know exactly what she would say = use
quickbooks. For small/medium business, QuickBooks is also a format
that tax CPAs work with regularly.
> So even though I set out to avoid rolling our own solution because I think
> it might cause problems in the long term, we need to get to the long term
> first. After a lot of heartache I think we have to do this ourselves.
> Having looked at so many of these kinds of programs, I have come up with
> what I believe is a minimal solution for our use cases. I am going to try
> to hack out the model tonight. However, what I am going to write will not be
> Leah friendly...
In my mind, I would say that we should avoid rolling our own solution
at *all* costs. Because it is outside our own expertise the "cost" of
our doing this will exceed the cost of paying for even a horribly
expensive off-the-shelf solution.
Do you think it would be helpful if I talked to my CPA friend to see
what they advise?
> It also might not do all of the kinds of reporting, aggregation, and
> interfacing that people want right off the bat.
>
> That said, I would really appreciate any help I got on this front. I know
> that we are all busy and have our own projects. I do too. But it is
> becoming critical for us to get this done. So if you are interested in this
> kind of project OR if you have a vested interest in seeing NumFOCUS succeed
> please consider helping out and let me know.
>
> This is supposed to be a minimal viable product. I think a couple of days
> of sprinting on this will get the job done well enough.
I can't state my objection to this plan strongly enough. If
NumFocus's success means that our prized developers have to write
accounting software, then we need to go back to the drawing board and
redefine what success means. I think this is an example of the
hammer/nail effect - when you have a hammer (coding skills) every
problem looks like a nail.
At the same time, I feel compassion for you personally that you are
having to wade through all of this. I am not quite volunteering to
help out formally, but I have done accounting before and have CPAs I
can talk to if that would be helpful.
Cheers,
Brian
> Be Well
> Anthony
> NumFOCUS Treasurer
>
--
Brian E. Granger
Cal Poly State University, San Luis Obispo
bgra...@calpoly.edu and
elli...@gmail.com