BC NDP

JMA Consulting is working with the British Columbia New Democratic Party (BC NDP), a political party in one of Canada's provinces, to support their migration from a custom back-office system to CiviCRM. They require a few enhancements to CiviCRM core initially and perhaps more later.

Official Receipting

BC requires its political parties to follow the Canadian charitable receipting procedures. This functionality will be built to comply with Revenue Canada's charitable receipting requirements (see http://www.cra-arc.gc.ca/chrts-gvng/chrts/prtng/rcpts/whtnf-eng.html).

Amounts marked as political contributions, which may include only part of an event ticket price (eg the amount in excess of the cost of the dinner), are tallied for each contact for the year and a single receipt issued for all donations in the year. An optional not needed by the BC NDP is to issue a receipt as each donation is received, so long as only a single receipt is issued for each eligible donation.

The information about the person making the contribution, their address, the amount of the donation, and other information must not be able to be edited after the fact. The organization administering CiviCRM will be responsible for meeting Revenue Canada obligations with regard to making backups on media that cannot be changed (e.g. CDs), and for entering appropriate fair market values for events, and complying with Revenue Canada's de minimis rules (see http://www.cra-arc.gc.ca/chrts-gvng/chrts/prtng/rcpts/splt-eng.html#deminimis).

Official receipts must be issued with a unique sequential number. Re-issued receipts must include this number.

NB: Joe Murray notes January 24th that Revenue Canada requires signatures on electronically issued receipts (see http://www.cra-arc.gc.ca/chrts-gvng/chrts/prtng/rcpts/cmptr-eng.html), so we will need to build in support for signing pdf's. CiviCRM's pdf library supports digital signatures.

50 hrs - Covers year-end receipting and unique fixed sequence assuming we follow Gift-aid model. Assumes Multiple Accounts for Events (below). 15 hrs - Joe's estimate for a simple admin interface to tell CiviCRM the path where a single digital signature for a site is located, and using it when generating a pdf for an official receipt.

Multiple Accounts for Event Sales

Tickets for an event may have a deductible and a non-deductible portion. For example, the cost of a dinner is non-deductible, while the amount beyond that is considered a political contribution eligible for special tax treatment. Different accounts need to be specified for each of these portions, and they need to be tracked separately.

75-100 hrs - Extend Event Fee configuration interface to allow input of fee segmentation by income account. At registration, create multiple contribution records, one for each income account. Multiple contribution records are linked to a single financial transaction (payment record). NB: Superceded by CiviAccounts Data Schema and Infrastructure work.

Single page for event registration and membership purchase

Extend event registration configuration interface to allow configuration of a "membership block" for online event registration (similar to "Membership Settings" form in Configure Online Contribution pages). NOTE: Schema already supports linking membership_block to entities other than contribution_page.

At registration, create multiple contribution records linked to a single financial transaction (one or more for event registration depending on fee segmentation, one for membership fee).

30 hrs - If done at the same time as "Multiple Accounts for Event Sales"

Support for Refunds and Voids in Moneris Plug-in

Enhance the existing Moneris plugin to support refunds and voids once it is supported in core. This will require working with Moneris to determine compliance etc.

25 hrs