Dues sounds like a pretty good fit for tuition to me if they pay it in large
lumps instead of monthly or some such. For most organizations, dues are what
cover the base costs. Tuition is sort of like that although it probably
covers less of the base costs than dues do for many not-for profits. If they
pay monthly then maybe pledges would work but I have never looked at that
part of ebase at all since we don't do that.
> -----Original Message-----
> From: Nellie Pennington [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 20, 2001 9:10 PM
> To: TechRocks Support
> Subject: [support] "Payment For" options
>
>
> Hi,
>
> I'm working with a small independent school to get our records set up in
> ebase. I've been playing around with ebase: entering some data by hand
> and importing some names, setting up Affiliations, Issues, and Action
> Prefs to fit our activities, trying out queries based on these, etc. I
> think I'm getting a pretty good idea of how to set things up so that we
> can get back out the information we want.
>
> I'm having some trouble with the "Payments" area, however; it doesn't
> seem to fit our organization very well:
>
> 1) Our income comes from Tuition, Grants, and Contributions, primarily,
> with some income from Events and Sales. "Dues" doesn't apply at all.
>
> 2) While I can add an accounting code for Tuition, if I set "Payment
> For" to Tuition, I won't see the payment on the payments screen (unless
> I modify the layout).
>
> 3) Tuition payments are really different from "Giving" -- in general, if
> I'm reporting on giving, I'd like to exclude tuition payments. But it
> appears they get lumped in with the rest, even if they're marked as
> "nondeductible". Short of customization, is there any other way to
> handle this?
>
> 4) It might be nice to use "pledges" to record tuition agreements, which
> would help us find parents whose tuition payments are overdue. Any
> thoughts on whether this would be an appropriate use of pledges?
>
> 5) Finally, it would be nice to be able to base the "member level" on
> the contributions, not dues. But I understand that member level is
> coded within ebase to be calculated based on the Dues payments only, and
> I'm hesitant to muck with the logic here.
>
> It seems like it might be best simply to
>
> a) create our own summary field to accumulate contributions and assign a
> "donor level" based on this field, and
>
> b) separate the tuition into a custom table or custom fields, rather
> than including it with the other contributions we get.
>
> Any thoughts or comments from other schools, or suggestions from more
> experienced users?
>
>
>
> -- Nellie Pennington
> [EMAIL PROTECTED]
> for Open Fields School
>
> ------------------
> Reminder to each recipient: To change your list account preferences, go to
> http://email.sparklist.com/scripts/lyris.pl?enter=support and
> enter the email address you used to subscribe to the ebase
> support list:: [EMAIL PROTECTED]
>
> To unsubscribe send a blank email to [EMAIL PROTECTED]
> ---------------------------------------------------------------------
> ebase - Relationship Management for Nonprofits, http://www.ebase.org
> ---------------------------------------------------------------------
>
>
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address
you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
