Business logic is another concern. Currently I run reports against expense reports in another window next to my Emacs session to verify items like:
- Weekly spending limits are honored - Every txn has a receipt - There are no missing receipts - Expense reports aren't missing common consistent items - ie: Car & Hotel & Meals & Airfare & Mileage (note all the &'s) - All postings in a ER goto the right account - I didn't typo a category or other metadata tag In a UI, I could highlight txns that violate specific policies or have a "dashboard" on the current ER validating on the fly, comparing the ER to policies in the background instead of in another window and manually interpreting the results myself. It is painful to have to go locate txns across files and edit them to make them conform to a business rule. I don't think Ledger's assert language is going to allow assertions across multiple txns that follow a specific criteria either, so I'm not sure the best way to approach this with Ledger other than "report, edit, repeat". ------------------------------------------------------------------ Russell Adams [email protected] PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
