On Thu, Nov 10, 2011 at 11:52:40AM -0800, Rick F wrote: > This works at the cost of some complexity, external to Ledger I have > to keep track of ERids. For actual expense reports that's probably > not much of a price to pay since the ER will have an ID and the > reimbursement notice will probably reference that ID for you.
I do my expense reports in Ledger, exporting via report generator to Latex and PDF. > Seems entry is a little problematic. Typos could mean you have > multiple categories like Airefare and Airfare, or maybe a CATEGORY: > Airfare and a CATGORY: Airfare. You could probably have your entry > tool (Emacs?) help there, though. Does ledger catch this for you, say > by making you declare your meta variables up front? Validation and consistency can be an issue. I avoid some problems there with external validation scripts and my importer always uses the same categories. > If you assume every ER is associated with at most one project, is > there anything to be gained by using an ER: meta-value vs. just a sub > account or is it just six of one, half-dozen of another? As in: > ----------------------------------- > 2011/11/01 Airplane ride > Source:VISA -$1000.00 > Dest:Project:ER0001 > ; CATEGORY: Airfare > ; PROJECT: Test > > 2011/11/02 Hotel overnight > Source:VISA -$200.00 > Dest:Project:ER0001 > ; CATEGORY: Lodging > ; PROJECT: Test > -------------------------- > > Or heck, just going all out with sub accounts: > > --------------- > 2011/11/01 Airplane ride > Source:VISA -$1000.00 > Dest:Project:Test:ER0001:Airfare > > 2011/11/02 Hotel overnight > Source:VISA -$200.00 > Dest:Project:Test:ER0001:Lodging > --------------- > > Would you be able to do the same queries as you listed, albeit with > some regex work? I tried this and found it very bulky and unwieldy. I preferred the metadata and converted wholesale. That said, I have frequently found that I prefer my data be setup with a singular primary category or key and then multiple tags for flexibility. This persists across applications. Thanks. ------------------------------------------------------------------ Russell Adams [email protected] PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
