pre-civi... were using an M$ Access database. In the move... more focus was put on making it match the old system... than identifyingy requirements and coming up with "proper" solutions.
Of course, the org and needs have evolved as well.
Double Entry and Spreadsheets... and in general "onerous" is still a theme in CA's processes.
Looking to understand better what is posible and how CiviCRM can work with QuickBooks.
Civi seems to be well set up for Accrual Accounting.
QBO is not contact aware.
Recognizing membership dues when they are received.. not using accrual accounting.
Two spreadsheets: one for Checks, one for each payment processor (iATS, Authorize) and hand-entered in the back-end.
Using Classes and Accounts......
Process is generally manageable... but gets pretty tedious around conference time.
e.g. CMI events.. need to get a class (currently) in QBO.
Anne says that sub-accounts could be used for some classes.
Anne to draft reconciling classes and accounts
Custom field... does not use Appeal Codes.
Enable Deferred Revenue config operation enables a new field on contributions for "Revenue Recognition Data". TODO: confirm what this looks like in exports.