That works. Another approach is to just choose one of the two dates (and manually combine the two transactions into one); that's what I do so far. This can occasionally screw up balance assertions; when that happens I'll comment one out and trust that the next one will pass, or just fudge the date of the balance. It's not rigorous in that the posting history of one account doesn't always have all correct dates, but it works. I think that eventually one way to solve well this will be to provide an optional date on each posting and to automatically expand that one input/ into multiple transactions, to transfer accounts with names inferred automatically.
If you look carefully at your credit card transactions, it's likely you will also find a discrepancy between the date you used the card (the transaction date) and the date it posts on your statement (the settlement date). On Sun, Sep 11, 2016 at 7:29 AM, Matthias Ehret <matzelo...@gmail.com> wrote: > Hi Martin, > > tanks for the references, I think i'll try with the transfer account, > seems to be the most "correct" but verbose solution so far. Problem only > occurs if I transfer money within the scope of my own finances > Bank1:account1 -> Bank2:account2, not with the outside world so hopefully > there is not so much additional work neccessary. > > > Am Sonntag, 11. September 2016 01:49:31 UTC+2 schrieb Martin Blais: >> >> That problem has been discussed before on the list; look for "settlement >> date" in the archives, both in the context of Ledger and Beancount. >> >> There's no implicit solution, but you can explicitly move the funds >> "virtually" to a temporary account as you describe, that works, it's a bit >> verbose. The technical name for this is a "transfer account." >> >> You could also use Ledger's effective date feature, but the problem with >> that at the moment is that it could leave you with a balance that doesn't >> sum to zero. The right solution would be for the software to automatically >> generate transfer account transactions for you. There's some ongoing >> discussion in the context of developing an implicit solution to this >> problem (for Beancount) here: >> http://furius.ca/beancount/doc/proposal-dates >> >> >> >> >> On Sat, Sep 10, 2016 at 1:06 PM, Matthias Ehret <matze...@gmail.com> >> wrote: >> >>> Hi there, >>> >>> I just started with ledger and came across one problem i'm not sure how >>> to solve it. >>> >>> f.e. I transfer money from one bank to another bank and there is a >>> transfer delay of 3 days how do i handle this in ledger without having >>> inconsistent data in the register view? >>> >>> Create a dummy place were I park the money for 3 days or is there a >>> better solution? >>> >>> Matthias >>> >>> -- >>> >>> --- >>> 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 ledger-cli+...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > > --- > 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 ledger-cli+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
