If you are a medium or large organization and use a payment processor with CiviCRM, and especially if your reporting needs are complex (e.g. political parties that need to report income rather carefully), then you will have run into the challenge of reconciling payment processor income in CiviCRM against your bookkeeping system and/or your bank account.
It's a time of year when machines and people get stressed, particularly in countries where tax laws and custom favour end-of-year donations. And if you've ever managed a CiviCRM installation, the last thing you probably want is to interrupt your end-of-year festivities with an issue of someone being unable to make a donation.
During the past year, I've been working with a number of medium and larger organizations using CiviCRM, and have found a few gaps in CiviCRM's CiviContribute functionality, particularly around the management of recurring donors, which are often a really important part of a larger organizations' donor base.
To this end, I'm happy to share a couple of extensions that I've been developing to fill these holes, detailed below.
Feedback and patches welcome, as usual.
I've just posted a new release for the iATS payment processor extension, with improvements and bugfixes, mostly for the ACH/EFT (direct debit) function.
The details about the release are here: https://github.com/iATSPayments/com.iatspayments.civicrm/releases/tag/1.2.7
I've been recommending the services of iATS for most of my clients' payment processing since way back in 2007, when I wrote a CiviCRM payment plugin processor for it: http://homeofficekernel.blogspot.ca/2007/12/iats-and-civicrm.html
That was a long time ago (CiviCRM version 1.8), and I've been promising myself and others that it's high time to rewrite it, because: