Summary: | transaction date vs post date | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | jesse <jvapr27> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | mahueb55 |
Priority: | NOR | ||
Version: | 5.1.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
jesse
2021-09-05 19:22:11 UTC
Just having the transaction date in addition to the posting date may not even be enough for what you need - if I'm not mistaken, all splits currently share the same posting date (so a transfer between two accounts (e.g. checking <> credit card) would always show the same posting date on both accts). One way to deal with this is to run the transactions through a separate account. E.g. for the cc payment (scenario 2), you could create a "cash in transit" (CIT) account and use the following posting logic: on the day the payment posts to your checking, post a transfer from the checking to the CIT account (dr CIT, cr checking). on the day the payment clears on the cc, post another transfer from CIT to the CC (dr CC, cr CIT). Your CIT should now be zero; and both the checking and cc accounts should show the proper dates. You could do a similar thing for the expense transactions (scenario 1) as well - you'd probably want a separate account for that (I've seen this being called "outgoing checks" in the past, you may want to look for a better term, especially if you don't do check payments). on the day you make the purchase, post the expense and set up a liability (dr expense, cr outgoing checks) on the day the charge posts to the cc, reclass the liability into the actual cc account (dr outgoing checks, cr CC). Depending on the number of transactions you're dealing with, it may not be worth the effort to do all of this (I certainly don't do it for my personal finances) - but if having the dates 100% right is a must-have for you, this may be a workaround for now. |