As 3.3. goes live it’s great to see a couple of Make-it-Happen initiatives included in it. The Make-it-Happen initiative was born out of my frustration at the difficulties of getting things into CiviCRM that were useful for everyone but not funded by any ONE organisation.
Since launching it we've managed to get a couple of long-wanted de-dupe improvements in - now in 3.3 you can make CiviCRM REMEMBER that John Smith from Widgimootha and John Smith from Aalberg are different people. For those of us who have been round the loop of running a de-dupe search, choosing two contacts to merge, merging them, and suddenly discovering than you can't navigate back to the duplicate listing page there's still quite a bit of scope for improvement so consider making a contribution to the 'prev-next' initiative
But, the Xmas present...Read more
There have been a number of blog posts discussing the needs for improved accounting features in CiviCRM. The results and current specification is at the wiki at: http://wiki.civicrm.org/confluence/display/CRM/Finance+and+Accounting
Its time to help to make-it-happen for CiviAccounts once the specifications on the wiki are streamlined and prioritized. Dave has requested that all interested parties join this new CiviAccounts team.
My priorities are:
1) Get many-to-many transactions to obligations working, both in the database as well as the UI. Many-to-many includes the following use cases:
- One check/credit card transaction that needs to be allocated to many obligations ( such as event fees, member dues, donations, etc )
- One obligation that will be fufilled by many transactions. Also known as partial payments. So...Read more
Creative Commons has been using CiviCRM for several years. A number of months ago we decided that for our annual fundraising campaign we wanted to streamline the donation process, possibly reducing it to a single click on the CC site.. About a month ago we launched our annual campaign along with a one-click donation process.
The process required a bit of custom coding, but fortunately very few changes to core CiviCRM code. Some of the main benefits of this method are:
- The contributor (potentially) makes only a single click to donate on your site. The less clicks/keystrokes the better chance someone will complete a contribution.
- You are no longer limited to designing your contribution pages within the confines/scope of Drupal and CiviCRM. You can create pages the way you want, wherever you want. This is especially nice for widgets, or anyone else wanting to help your campaign. Potentially, people can create their own donate links on their own sites...
About 8 weeks ago we began looking into a CiviCRM / QuickBooks integration framework. Our goal is to write a module that allows CiviCRM contributions and contact information to be written to QuickBooks. Our target version is QuickBooks 2009 Premier Non-Profit edition, since that's what we use.
At the very least, the module should be able to:
- Map sources of income in CiviCRM with accounts in QuickBooks.
- Insert Donations, Deposits and Payments from CivCRM to QuickBooks.
- A seamless process that requires little management from the staff.
We found the QuickBooks PHP framework by Keith Palmer to be the best fit for our needs:
It's being actively developed and supported by a handful of programmers who are also using the framework in production environments. It makes SOAP calls using...Read more
- generate a listing of the individual cheque and cash "receipts" processed since the last "deposit" was generated, add selected receipts to a deposit and print it as a deposit listing, using a template that would enable you to submit the listing to your bank with a deposit slip;
- enable a bank reconciliation to confirm that each deposit was successful and highlight any discrepancies such as bounced cheques or typo's when entering cash or cheque amounts. Ideally you would be able to tick off each receipt within a deposit as reconciled (or just tick the deposit as a whole and have the system mark each receipt within that deposit as reconciled). If a...
We are finding that CiviCRM/accounts issues are becoming increasingly important for our clients, and Eileen's recent blogs and the discussion they are generating are a fantastic step towards helping find the best way for Civi to deal with financial transactions.
For example, I think it could be useful for Civi to ultimately develop functionality for maintaining simple bank accounts within CiviCRM, so that small organisations can maintain basic accounts without the headaches of integration with an external package.
Currently we have clients who are willing to rely on CiviCRM as being the central repository for the detail of all contributions, with a lump sum figure hitting their GL at the end of each month which can be reconciled against CiviCRM's records. This is largely reliant on the organisation having very good procedures in place to attend to banking on the same day as transactions are entered into CiviCRM, to make it easier for payments to be reconciled. It...Read more
- Decide what basic information you want to collect from your fundraisers - a "Supporter Profile". We recommend collecting first and last name and email address.
- CiviCase - case management component with configurable workflows (learn more...).
- Personal Campaign Pages - Allow constituents to create and promote their own personal fundraising pages in order to drive traffic to your organization's online contribution pages (learn more...).
- Simplified CiviMail Requirements - PHP-based option to handle return channel (bounces, replies ...) - replaces AMAVIS and simplifies installation and...