Ah, that could work. Effectively a subaccount per invoice, right? And ten I wonder if aging could be achieved by simply encoding the due date in the invoice number. So your 2010304 would become 2010304_20100630 (i.e. due on June 30th). Then I could envisage an aging report being produced (maybe with some perl/python-ish post processing of a core ledger report) to find all invoice "subaccounts" with non-zero balances where an age is calculated simply by taking the difference of the date suffix with today's date (or some specified "effective" date).
Tommy On Jun 27, 8:33 am, Simon Michael <[email protected]> wrote: > No explicit aging, but here's how I identify client and specific invoice: > > 2010/03/04 client A invoice > assets:accounts receivable:client A:2010304 $900 > income:consulting:client A $-900 > > 2010/03/30 client A payment > assets:accounts receivable:client A:2010304 $-900 > assets:bank:wells fargo:checking $900
