4 ms·
Thank you! But i think having the option for them not to equal and do single entry bookkeeping is key. All the tools validate that the journals balance so it re
by darcys22 5y ago
Thank you! But i think having the option for them not to equal and do single entry bookkeeping is key. All the tools validate that the journals balance so it really takes effort for them not to balance. However ive been playing around with having accounts for things like ‘bank statements’ that are one sided and not shown as part of the GL. This allows for bank feeds to be built into the system and can reconcile against actual GL transactions.
I guess my strategy is delegating the enforcement of balancing journals onto higher levels of the system. The databases job is just to format the transactions nicely, building tools and scripts that can audit the GL and highlight bad transactions will definitely need to exist. Conceptually i think accounting systems need a CI system that runs after you push a transaction through to ensure that your journals are correct
- rwillians 5y agoI think this concept of a CI-like system for accounting is really interesting. You allow bad journal entries to go through but you show exactly which one put the GL out of balance. You know, that shouldn’t be too hard to build. I don’t really need that for my current project since all journal entries follows templates that were designed and well tested, but I’m fairly certain I have all the structure necessary for building it. Lemme know if you’d be interested in working on this CI, I could give you a hand ;)
- darcys22 5y agoYeah 100% because its not just journals being out of balance thats the risk. Checks for other things like asset registers becoming out of sync with your asset accounts could be included depending on the businesses needs. Would love to discuss this further
- rwillians 5y agoAwesome! I’ll ping you on telegram