On Wed, Feb 3, 2016 at 11:48 AM, Erik Hetzner <[email protected]> wrote:
> On Tue, 02 Feb 2016 19:48:06 -0800, > John Hendy <[email protected]> wrote: > > > > > > > > On Monday, February 1, 2016 at 10:41:26 PM UTC-6, Martin Blais wrote: > > > > > > - Merging new transactions with previous transactions imported from the > > > other side (e.g. a payment from a bank account to pay off on'es credit > card > > > will typically be imported from both the bank AND credit card > accounts; you > > > must merge the corresponding transactions together) > > > > > > > Definitely. Moneydance allowed me to input an account, which would "link" > > the transaction. Then I'd have to delete or merge the other account's > > record of the same transaction. > > One needn’t actually merge these. Here is what I do: > > 2015/12/31 Credit card payment > Assets:Checking -$100 > Transfer:AC->LCC $100 > > 2016/01/01 Payment received > Liabilities:CreditCard $100 > Transfer:AC->LCC -$100 > > Some kind person on the list pointed out this technique a while ago. > > This makes import easier and allows for a difference in transit time. All > Transfer:* accounts should balance to $0, so you have an additional check > that > everything is balancing out. > I think it would be possible to process the stream of transactions and identify close matches based on common accounts and nearby dates, and automatically merge matching transactions into a single one, removing zero balances. The dual operation is assigning individual dates on postings of a single transaction and having the software split them up to obtain the result you describe. In either case, matching transactions should be linked automatically and it should be possible to report on a set of matching transactions (a-la "bean-doctor linked"). -- --- 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.
