use case: reconcile virtual accounts with real accounts

[ahdinosaur]

currently within Enspiral we're having a conversation about our internal accounting system: "my.enspiral". since i'm most keen to build a system that works for Enspiral, i'll be extracting some feedback on our current system into user stories and design requirements here.

the main requirement (and current pain point for our accountants) is to ensure a set of virtual internal bank accounts are reconciled with actual external bank accounts. missing transactions on either side means more manual work for accountants and chance for errors.

• virtual accounts must track respective actual accounts and vise versa
  • must include accounting of tax paid, tax yet to be paid, future refunds, etc
  • must include a mechanism for detecting missed or incorrect transactions
  • must be consistent with the "matching principle” - the concept that expenses are recognised in the period that the related income is earned

[almereyda]

We have moved the ValueFlows organization from GitHub to https://lab.allmende.io/valueflows.

This issue has been closed here, and all further discussion on this issue can be done at

https://lab.allmende.io/valueflows/exchange/-/issues/6.

If you have not done so, you are very welcome to register at https://lab.allmende.io and join the ValueFlows organization there.