Project 60 integrating CiviCRM with bank information

1. Project 60integrating CiviCRM with bank information Project summary

2. Project 60 Scope In real applications of CiviCRM, there are many processes which involve handling information between CiviCRM and bank accounts, which are currently handled manually or by custom scripts Financial Transactions (Bank Accounts) Importing bank payment information CiviCRM Decoding bank payments into contributions Reconciling contributions and bank accounts Managing SEPA Direct Debit recurring payments Project 60 is an initiative of a number of European CiviCRM integrators who want to develop a number of extensions supporting these processes.

3. Project 60 Deliverables Extensions to support the processing of bank payment information Extensions to support the complete SEPA Direct Debit processing CiviBanking SEPA Direct Debit support • Import payment information from bank statements in different formats • Import payment information from accounting systems • Manage multiple bank accounts per contact • Facilitate automatic or assisted matching of payments to CiviCRM entities (contact, membership, contribution, …) saving hundreds of hours of manual labour • Support a closed loop analytical accounting process • Support the SEPA Direct Debit B2C Core model / rulebook • Manage multiple creditor identities • Provide a SEPA-compliant Direct Debit payment processor • Manage the SDD mandate lifecycle • Generate one-off and recurring payment requests • Generate the XML required for bank submission • Handle the exception and feedback processing (requires CiviBanking) • Integrator’s Guides : • Developing import plugins • Developing match plugins • Integrator’s Guides : • Implementing an SDD workflow

4. Project 60 Benefits Extensions to support the processing of bank payment information Extensions to support the complete SEPA Direct Debit processing CiviBanking SEPA Direct Debit support • Turn bank payments into contributions and memberships much faster • Define your own interpretation and matching rules • Increase data quality and consistency • Reduce the workload on your back-office team • Give your data management team more time to focus on the real issues • Save time and money you can spend on your mission ! • Become operational with SEPA Direct Debit without a significant investment in understanding SDD protocols • Tap into the fundraising potential offered by flexible and versatile bank account-based recurring payments • Standardize recurring payments or memberships and long-term supporters on the new European standard • Be ready to deploy the new European recurring payment model in time !

5. Key Project 60 components

6. Key Project 60 components Ensure consistency in bank information by processing bank statement sequences Import payment information from electronic bank files or from your accounting system Maintain a registry of bank account information to improve automated / assisted identification of contacts Close the accounting loop and help in allocating funds correctly (using CiviAccounts)

7. Key Project 60 components Support the SEPA Direct Debit mandate lifecycle and operational exceptions Handle mandates from different sources (street, online, call center, document) Generate the recurring payment requests for all your mandates Generate the XML files for the handling bank

8. Key Project 60 components Run a multitude of matching rules to interpret payments and convert them into contributions Support data managers with full automatic, manual or assisted (suggested) interpretation logic Extend the standard matchers with your own business logic Automate handling of SDD batch payments and R-messages

9. Project 60 active participants • Software für Engagierte – Germany • Detlev Sieber, Olaf Buddenhagen • Systopia– Germany • Björn Endres, Fabian Schuttenberg • Delius–Belgium • Paul Delbar, Chris Madou • Tech tothe People – France • Xavier Dutoit

10. Project 60 timeline • Finalize scope and data model • Define final implementation plan • Implement overall extension architecture • Make It Happen kickoff CiviCRM 4.3 April • Build basic application logic • Build initial UI • Build initial bank import plugins May • Finalize Guidebooks for national implementation standards • Start initial trial implementations • Tune UI based on user feedback • Gather requirements for v2 June • Process MIH funding/requirements feedback and prioritize September • Launch GA/stable version of extensions in CiviCRM 4.4 • Align future development with core release plan • Start development of v2 CiviCRM 4.4 Octobre

11. Project 60 Funding • All active participants have short-term pilot customers who will fund development • Workload will be shared between active participants and core team / external members as skills / capacity are needed • MIH funding will allow us to • Move faster (which will benefit you too) • Involve the core team in a structural way

12. Project 60 sizing – current estimates (manhours) • Common • Data model 60 • Extension framework 40 • CiviBanking • API and business logic 60 • User Interface 120 • Plugin achitecture and initial plugins 40 • Guidebooks 60 • CiviSDD • API and business logic 60 • User interface 80 • XML generation 40 • Guidebooks 80 • Total 640