1 / 11

Accounting Integration

Joe Murray. Accounting Integration. Taking CiviCRM to the Enterprise Level. Easy to set up and administer for simple use cases via sensible defaults Powerful, flexible and robust for larger organizations with more sophisticated needs

baris
Télécharger la présentation

Accounting Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Joe Murray Accounting Integration Taking CiviCRM to the Enterprise Level

  2. Easy to set up and administer for simple use cases via sensible defaults • Powerful, flexible and robust for larger organizations with more sophisticated needs • Not a separate component, visible only through specific enhancements Vision

  3. Allow CiviCRM to handle all or part of accounts receivables for non-profit organizations: • Donations • Memberships / Subscriptions • Events • Enable CiviCRM to export into accounting packages like QuickBooks Scope

  4. Support CiviGrants accounts payables • Data schema support for transfers between chapters and central organizations Scope Expansions

  5. Don’t make CiviCRM into an accounting system: • No payroll • No accounts payable (except grants) • No capital depreciation • Taxes to be handled by extensions for countries/provinces (though supported in data schema) Out of Scope

  6. Changes and reversals • E.g. changing options for event ticket, refunding a subscription • Record accounting information at detailed line item level Major Enhancements

  7. Follow existing UI patterns • Design DB and API for extensibility • Satisfy auditors by preventing deletion of financial info • Record changes to financial info as new ‘difference’ transactions • Satisfy accountants and Executive Directors by storing separate account codes for all line items Objectives

  8. Financial entries are not deletable, to make actions auditable • Cancelling/reversing or changing an entry is done the way bookkeepers and accountants like: via additional transactions that reverse or modify the effect of the original ones No Loss of Financial Info

  9. Every amount has a G/L (general ledger) accounting code associated with it: • Each line item, not the whole contribution page • Premiums • Grants Feature: Detailed Accounting

  10. Examples: • Buy $100 ticket with cheque: • Revenue: dinner event: $100 • Asset: bank account: $100 • Pay for $50 membership later: • Revenue: membership: $50 • Asset: accounts receivable:$50 • $50 membership check received: • Asset: accounts receivable: $50 reduction • Asset: bank account: $50 Feature: Double Entry Accounting

  11. Included in CiviCRM 4.3 • Help needed with testing and documentation • Email joe.murray@jmaconsulting.biz • 4.3.Beta sandbox: http://sandbox.drupal.civicrm.org • svn: http://svn.civicrm.org/civicrm/ • Report issues to Alpha and Beta Testing Forum Current Status

More Related