CiviContribute

Supporting tax rules worldwide

Published
2012-05-12 07:26
Written by

I am starting a project that will allow CiviCRM to support the needs of an Australian non-profit. This non-profit is subject to the Australian Goods & Services Tax rules (GST) for some but not all transactions.

The GST requirements apply whenever the non-profit provides a tangible good or service in exchange for a payment. This is most common with their dinners, selling DVDs, and items from their gift shop. 

 I have written up the requirements and possible approaches on the CiviCRM wiki at:

Improving CiviCRM’s soft credit functionality

Published
2012-05-11 15:03
Written by

At the April sprint, several of us discussed improvements to CiviCRM’s soft credit functionality. For those of us who use CiviCRM for fundraising, soft credits are vital component of managing donor relationships, and there are several ways CiviCRM could be improved to make soft credits more robust and easier to use.

Thanks to Kellie Brownell and Jane Hanley for their contributions to this blog post.

Some background:

Batch Entry of Contributions and Membership Payments - Draft Specification

Published
2012-02-22 15:31
Written by

Batch entry of gifts (checks, cash, etc.) is a much requested "missing feature" in CiviCRM. Thanks to a generous sponsorship commitment from the Electronic Frontier Foundation, we are about to launch a Make-it-Happen campaign to implement this feature for the next release (4.2). We've spent some time discussing requirements with folks at EFF and several other organizations, and we've reviewed analogous functionality offered by several of the proprietary donor management products. The purpose of this post is to share the draft specifications for the feature and solicit feedback from others in the community.

Overview

The goal is to provide a streamlined interface for data entry of batches of contributions and membership payments. A simple batching concept will be introduced to provide verification of count and totals. The feature will use a grid-style input form with the columns controlled by a selected profile. This will allow sites to add or remove non-required fields in the grid (e.g. add custom contribution fields, add or exclude premium fields etc.). The current plan is to have a separate flow / input grid for batch entry of contributions vs. membership signup / renewal payments. This will help reduce the number of columns required for each type of input.

Using only jQuery and CiviCRM to create Members Only Pricing

Published
2012-02-13 19:44
Written by

There have been several hook() or Drupal module based solutions for "members only" pricing for events or for other 'discounts' related to memberships.

 

I take a different approach by using only jQuery and blocks in Drupal 6.  For those who use Drupal 7 you can adapt this code with Drupal 7's new javascript namespace and Joomla folks could even make use of this in custom TPL files.

 

Price Sets

Published
2012-01-18 12:26
Written by

Notice to non-developers: This post is about how some functionality in 4.2 will be implemented in code and in the database, with very minor changes to anything visible through a browser. If you're not a developer, it probably won't interest you.

Case Study: Implementing CiviCRM for a religious organization

Published
2011-10-28 14:55
Written by

Background
Pogstone's client had already been using a web-based membership database, however that system did not have any features related to households and other features needed when interacting with families and children. They also needed many features related to needs of a typical synagogue that were missing from the previous system.

Roll-out process

Enhancing the System Templates Messages: Default Header/Footer, and, Pay Later consistency

Published
2011-09-09 17:43
Written by

A couple of issues have begun to sting us repeatedly and I see others raising same issue.

 

#1

Getting a Default Header/Footer used in the SysTplMsgs

 

SysTplMsgs (System Template Messages) are found here /civicrm/admin/messageTemplates?reset=1)

 

To avoid repeated copying of the desired header/footer in to the upto 22 SysTplMsg, one option would be to add a checkbox to the CiviMail Footer/Headers (/civicrm/admin/component?reset=1)