[Calendula-devel] DiscipleMakers weigh-in
Matthew Patton
pattonm@dm.org
Tue, 23 Mar 2004 10:11:39 -0500 (EST)
Hi Darryl,
You asked that we view the REQ document in the CVS repository.
I've done that and compared it with the requirements document we have here
at DM for our receipting system. The following are things that you didn't
have that we will need:
Functionality
=============
-There will be remote users whose user account will be associated with a
certain fund (in our case, remote staff who each have a fund that their
supporters give to). These users will need to be able to view certain
reports:
a. View gifts for their respective funds
b. View a donor's contact information
c. View an account's giving history (for what an account is, see
"Data" below)
d. Eventually it will be necessary to have the data that these
remote users have about their donors (contact information, personal notes,
relationship history) sync'd up with this central DB that stores the gifts
that come in, but this is an advanced feature that can wait
-The main kind of user, however, will be the administrator. In addition
to the functionality you mention, the system will need to provide the
admin with the following functionality:
Deposits (see below under "Data" what for what a deposit is)
a. add/mod deposit:
i. add/mod Transactions
1. add/mod accounts
ii. del Transactions
iii. Print / Email receipts
1. Individual receipts
2. All in batch
iv. Email to owners of funds a list of contributions they
have received
b. Reports
i. Bank report
Transactions
a. Search for transactions
Funds
a. add/mod/del funds, owners
b. Reports
i. History
Data
====
1. Deposit - one batch of transactions (mainly checks) processed at a time
(usually to go to the bank)
a. Name
b. Creation date
c. Transactions in this deposit (see Transaction)
d. Note
2. Transaction - one monetary event where money goes from an account to a
fund
a. Which account is sending money (see Account)
b. Line items:
i. Which fund is receiving money (see Fund)
ii. Amount of money
iii. Whether tax deductible
c. Type
Check
i. Check number
ii. Name of institution on check
iii. Name on check
iv. Routing number
v. Account number for check
vi. Who actually cut the check (used when a gift is given
from a business)
Money Order
i. Who actually cut the money order
Cash
[No additional data]
Electronic Fund Transfer (EFT)
i. Name of institution
ii. Routing number
iii. Account number?
d. Note
3. Account (not sure if this is the right technical accounting term for
this) - a single money-sending entity. Examples would be:
1. An individual (e.g., "Joe Smith")
2. A couple (e.g., "Joe & Sue Smith")
3. A family (e.g., "The Smiths")
4. A company (e.g., "Smith's Grocery, Inc.")
5. A church/organization (e.g., "First Presbyterian Church")
The data for an account would be:
a. Which donor(s) own this account
For each donor:
i. Name
ii. Sortname
iii. Gender
iv. Contact Information
1. Address
2. Phone number
3. E-mail address
b. Note
4. Fund - a single money-receiving entity. Examples would be:
1. An individual staff (e.g., "Joe Staff")
2. A staff couple or family (e.g., "Joe & Sue Staff")
3. An organization-wide fund (e.g., "Conferences")
The data for a fund would be:
a. Name
b. id of fund in accounting software package (we use Peachtree,
and would need to export from this receipting system the total received
for each fund and import those totals into the accounting system)
c. Whether tax deductible
d. Owners of fund
e. Whether the fund is active
f. Note
===================
There may be some overlap in what I have shared with what you have in your
Requirements Doc, Darryl, but I tried to minimize that. Let me know your
thoughts!
Matt
______________________________________________________________
Matthew Patton pattonm@dm.org
DiscipleMakers Headquarters: (814)234-7975 x32
On Sun, 21 Mar 2004, Darryl Caldwell wrote:
> Thanks Jason and Tom,
>
> The use case you outlined is right in line with the REQ doc that I have
> written for Calendula. Many donors hang on to "thank-you" letters from
> charities and other NPOs for their tax records.
>
> You all can view the REQ in the CVS repository or send me a note and I
> will attach it to an email message to you.
>
> NOW would be a good time to read through the REQ to see if it is missing
> something obvious. It also contains good talking points for you
> consultants out there that deal with nonprofits on a regular basis, and
> especially all of you on your way to NTEN/Penguinday.
>
>
> -D
>
>
>
>
> > Hi Darryl,
> >
> > On Sat, 20 Mar 2004, Darryl Caldwell wrote:
> >
> >>Thanks for the overview, Matt. Could you by chance provide us with a
> >>simple use case for this receipting system. I am trying to visualize how
> >>this would fit into a CRM.
> >
> > I'll throw in a little more to try and clarify things. By "receipting"
> > what we mean is the software that our secretaries use to handle
> > contributions (donations) that come to our headquarters, usually in the
> > form of checks. They use the software to enter in who the gift was from,
> > who it's for, and then print a receipt to mail to the donor (hence
> > the name "receipting"). It would be great for this "receipting" system to
> > tie into our CRM software so all of our staff (most are remote) would
> > automatically see all the gifts a contact has given when they look up a
> > person's record in the CRM software.
> >
> > The basic idea we have is to have this big database of people that all of
> > our software ties into, instead of our current situation of separate
> > software for the donations, CRM, event/conference management, etc.
> >
> > I hope that makes sense.
> >
> > -Jason
> > _______________________________________________
> > Calendula-devel mailing list
> > Calendula-devel@fudosys.com
> > http://list.fudosys.com/mailman/listinfo/calendula-devel
> >
>
>
> --
> Darryl Caldwell
> darrylc@fudosys.com
> www.fudosys.com
> _______________________________________________
> Calendula-devel mailing list
> Calendula-devel@fudosys.com
> http://list.fudosys.com/mailman/listinfo/calendula-devel
>