Work on Project60 continues in the limelight. SEPA Direct Debit processing is alive and kicking, and we've just completed a first demo run of CiviBanking integrated with the Belgian bank format (CODA) importer. 261 files containing 1600+ transactions, running through an initial set of matching rules, good for an 80% hit rate ... not bad at all. Considering that the entire matching process takes about 2 minutes to complete, and only 320 transactions need a human intervention, this is promising news !
Imagine you're a non-profit employee or volunteer, responsible for managing donations. You get into the office, pick up the first coffee on the way to your desk, to find a HUGE bank statement for you to process today. Good news for your employer, not for you, because even at the rate of roughly two payments per minute, you'll be spending 19.5 hours processing them. Yay !
Wouldn't it be nice if CiviCRM would load the bank statement files and turn them into contributions, membership renewals, new contacts, people who have moved and so on ? Yes, of course.
If you are not fundraising in any of the Single European Payment Area countries, feel free to skip this blog -- unless you want to discover how the amazing CiviCRM community is building support for what is becoming Europe's most important recurring payment instrument.
We're fortunate to find Sir Civi in the midst of the Bug Smithing Weekend, and get a quick interview from him while his horse is being watered. So how's it going ?
Sir Civi: "Twenty two. So far, that is. Nasty creatures, them Bugs. Spoil the fun for everyone. Lurking in a piece of code that noone tested, popping up at the least opportune moment (like when you're doing a demo). Takes the fun out of moving to the next release."
-- Do you feel this release is getting more and more stable ?
When you think of it, it's quite amazing : open source communities bring out the best in people. Like all of you who participated in the first Bug Smithing Day, and ran 4.3 beta through a series of real-life tests, upgrades and API scripts. Even if you didn't find a bug, thou art truly thanked for thy effort.
Actually, that's not correct. Since testing the 4.3 release is ultimately good for you (the community), it's more appropriate to say you needs you ...
Don't go 'I don't have time', or 'I'm no developer so I can't help' or even 'that's why we have the core team' : I'm calling on each and every one of you to spend one hour of testing over the next few weeks. Have a large latte, put on that Celine Dion CD you say you don't like, close the door, take the phone off the hook and just do it.