> I remember this coming up in the ML in the past, but can't find a > reference. I want to refactor some of my accounts & transactions, but > want to avoid breaking the resultant value for top level accounts > (since the data has already been reported to the government and I > don't want that to change by my refactoring :)).
Just wondering if anyone had ideas on how I can maintain consistency at the top level accounts for amount, whilst refactoring transactions amongst the lower level accounts in the hierarchy? Thanks, Chris -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
