Open jharris1993 opened 1 year ago
This is a great suggestion, and I have an idea for how to implement it. To be honest it won't be a high priority for development, but it will stay on the list for consideration. Thank you for contributing it and providing a nice write-up.
Additional suggestion: Allow the date span to be configurable perhaps with five or seven days as the default.
For example:
Therefore, a transaction initiated at institution "X" on the Tuesday before Thanksgiving may not be processed by institution "Y" until the following Tuesday.
Viz.:
Ergo: A seven day transaction delta.
Thanks!
Ref: https://infinitekind.tenderapp.com/discussions/suggestions/15673-can-differing-dates-link-between-accounts
Text of suggestion:
Note: I already know I am going to get a bunch of replies claiming that Moneydance uses strict double-entry accounting. Please don't flame me for this.
Issue: When attempting to reconcile transactions between differing accounts within Moneydance, the transaction dates can differ between accounts and BOTH dates can be, and often are, authoritative.
Viz:
Why both dates are authoritative: Assume:
At least in the United States, the banks that issue credit cards can, and do, enforce the provision that payments are not considered received until posted to the credit card's account, regardless of what the issuing bank may say. Note that the question of it being "correct" or "reasonable" is not material to this discussion.
The result is that when importing data into Moneydance, there are two sets of duplicate transactions:
This results in a lot of unnecessary clean-up which is easily resolvable if the transactions can link, even though on slightly different dates.
Suggested resolution:
This way, those who desire and expect strict double-entry accounting can have what they want and expect, and those who want double-entry accounting with a more relaxed date tolerance can have that too.
Thanks!