Author Topic: Accounting Batches  (Read 1031 times)

Offline Guy Iaccarino

  • I post occasionally
  • **
  • Posts: 92
  • Karma: 5
    • Greenleaf Advancement
  • CiviCRM version: 4.4.10, 4.5.4
  • CMS version: WordPress 4, Drupal 7, Drupal 6, Joomla 3
  • MySQL version: 5.5
  • PHP version: 5.3
Accounting Batches
« on: December 16, 2014, 01:49:53 pm »
The Accounting Batch feature is great. The accounting control enabled within it is fabulous, and I understand it was probably no small feat to get that working as well as it does. The fact that it's customized for QuickBooks really makes it shine.

The one glaring shortcoming is the lack of the Class field. So many QuickBooks users rely on that field, but the fact that Civi doesn't have it precludes them from using the accounting integration.

One solution would be to add the Class field to the Contribution record, and then add it to the accounting batch exports. But a more universally usable solution (and perhaps simpler) would be to make the fields that get exported in the accounting batch defined by a Profile. Then users could add whatever custom fields they needed for their accounting systems to the contribution records, and add them also to the accounting batch export profile so they get exported during the accounting batch export.

Does this approach make sense?
« Last Edit: December 16, 2014, 02:04:06 pm by Guy Iaccarino »

Offline Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Accounting Batches
« Reply #1 on: December 16, 2014, 02:36:26 pm »
Guy - might be worth expanding on this in a blog post and seeing if you can drum up financial support from a few organizations. From my point of view would help to explain quite a bit more how the 'Class' field is used (with some examples) - especially since my initial thought was to add it as a property of a financial account or financial type (but I don't have enough info to know if that's a good approach).
Protect your investment in CiviCRM by  becoming a Member!

Offline Guy Iaccarino

  • I post occasionally
  • **
  • Posts: 92
  • Karma: 5
    • Greenleaf Advancement
  • CiviCRM version: 4.4.10, 4.5.4
  • CMS version: WordPress 4, Drupal 7, Drupal 6, Joomla 3
  • MySQL version: 5.5
  • PHP version: 5.3
Re: Accounting Batches
« Reply #2 on: December 16, 2014, 03:22:34 pm »
I'll see if I can do that (after I get that extension checklist done).

My initial thought about adding it as a property of a financial account or type is that that would seem nullify the whole purpose of the class. The class further defines the contribution, so if the class was by definition the same for every contribution of a given account or type, how would it help further define the contribution? But I too would need to look at examples and walk the process all the way through to be absolutely sure.

I like the profile idea because a. it fits in to the existing Civi paradigm (e.g.like the way a Profile defines the batch entry fields) and b. it allows flexibility for other accounting systems.

I think we could get folks to support this. Any idea on a ballpark number of hours / cost?

Offline Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Accounting Batches
« Reply #3 on: December 18, 2014, 04:32:36 pm »
No idea on number of hours for this, but probably non-trivial since I think many of the data elements included in the batch export are not currently exposed to profile system.
Protect your investment in CiviCRM by  becoming a Member!


Offline Upperholme

  • Administrator
  • Ask me questions
  • *****
  • Posts: 568
  • Karma: 8
    • MC3
  • CiviCRM version: 4.x
  • CMS version: Drupal 6.x/7.x, Wordpress, Joomla
Re: Accounting Batches
« Reply #5 on: June 21, 2015, 05:56:18 pm »
I wonder if this idea got any further forward? I agree that the idea of using a profile to define what fields get included in the export is a good one as it puts the user in control. I'm working with a client who uses Xero for their accounts, and Xero has provision for a couple of tracking category fields, so it would be great to simply add these in to Civi as custom fields for contributions, and then ensure that they get exported in the batch data. But making this happen looks to be really complex.

If the fields already included in the export are not exposed to the profile system, then maybe just think about using a profile to add additional fields? Not ideal, but perhaps simpler to implement.
Graham Mitchell
http://mc3.coop