This is the top level page for all work associated with the Accounting Integration Data Schema project as well as related follow-on enhancements. At a high level, the scope of this project is the first point in http://civicrm.org/civicrm/contribute/transact?reset=1&id=11: 'Enhance the CiviCRM schema to enable better integration of accounting concepts and systems with CiviCRM. This includes clear separation of "obligations" from "payments", and the ability to specify revenue and asset accounts.' These changes will enable the data schema to support the following sorts of enhancements:
- Batching of Contributions
- Changes, Reversals, Refunds
- Detailed Account Codes
- Flexible Order Form
- Flexible User Payments
- Official Receipting
- Partial Payments - backoffice staff only
Attachments to this page provide diagrams of the schema, as well as MySQL Workbench and MySQL schema dump files.
![]() | As of July 4th the attached diagrams do not reflect a name change from invoice to order, though that is now reflected in the authoritative version in the subversion repository for the project at http://svn.civicrm.org/civicrm/branches/v4.1.civiaccounts/ |
While a wiki isn't necessarily the best tool for project collaboration and management, we'll use this page as a focal point for the project for now.
- 4.3 CiviAccounts To Do
- Accounting Improvements and Integration Data Schema Project Structure
- Apply Credit Notes to Amounts Owing
- Canadian Sales Tax Extension
- CiviAccounts - Data Flow Examples
- CiviAccounts Data Schema Acceptance Tests
- CiviAccounts Data Schema - Affected pages, forms, reports
- CiviAccounts Data Schema - BAO interfaces
- CiviAccounts Data Schema - Data migration and new schema
- CiviAccounts Data Schema - files
- CiviAccounts Data Schema - Project Plan
- CiviAccounts Data Schema - Sample Before and After Transactions
- CiviAccounts Data Schema - Schema Diff
- CiviAccounts - Event Registration with Price Set example
- CiviAccounts Project Overview
- CiviAccounts Specifications - Batches
- CiviAccounts Specifications-Changes, Reversals, Refunds
- CiviAccounts Specifications - Code changes
- CiviAccounts Specifications-Detailed Account Codes
- CiviAccounts Specifications - Financial Items
- CiviAccounts Specifications - Flexible Order Form
- CiviAccounts Specifications-Flexible User Payments
- CiviAccounts Specifications-Official Receipting
- CiviAccounts Specifications-Partial Payments - backoffice staff only
- CiviAccounts Specifications - references to contribution_id
- CiviAccounts - Support Agreement
- CiviAccounts - Value Added Tax / Sales Tax
- Draft of use-cases to verify
- Existing Code references for 'contribution_id'
- Invoice Format and Batch Entries Scenarios
- Minutes of Accounting Integration Steering Committee meetings
- QuickBooks Online Integration extension
- Sales Taxes and Invoicing - Phase 1
- Separating Contributions and Payments
- Some minor changes to the way Civi deals with finance...
- Use Case: Alter event pricing options
- Use Case Partial Refund For Event
- Use Case - Payment Processing (partial payments)
- VAT Electronic Services Extension