[moneydance] Transaction matching rules

[Ben Walding]

Turns out it is an option to download MSMoney (OFC) files bank (the
Commonwealth Bank of Australia) doesn't make it clear that MSMoney ==
OFC though). I've tried that and it is a LOT simpler.  Thanks for the
info.

Thanks also for dealing with QIF import issue (even though it
hopefully no longer affects me). Much appreciated.


Cheers,

Ben

On Fri, Aug 1, 2008 at 4:15 AM, Sean Reilly <sreilly at seanreilly.com> wrote:
> Hi Ben,
>
> Is it not an option to download QFX or OFX files instead of QIF?  That
> would prevent this problem completely.
>
> Also, are you deleting the duplicate downloaded transactions or select
> the "new transaction" option from the popup?  If you are deleting then
> that is why Moneydance is attempting to repeatedly match downloaded
> transactions to the incorrect register transactions.
>
> Thanks,
> Sean
>
>
> On Jul 30, 2008, at 23:36 , Ben Walding wrote:
>
>> Is there anyway to tighten up the date criteria for transaction
>> matching
>> when importing .QIF (or any electronic transaction file?)
>>
>> I have the issue where I have transactions every fortnight for the
>> same
>> amount - say $100.
>>
>> MD foolishly tries to say these are all the same transaction which
>> causes
>> extreme frustration when I import my transaction file.  It would be
>> fairly
>> straightforward to tighten the rules so that a transaction match was
>> only
>> valid for 2 days either way; thus eliminating 90% of false-positives.
>>
>>
>> (This is even worse for credit card statements where I don't have a
>> running
>> balance to help with reconciliation (I would love to stab the genius
>> who
>> thought that was a good idea))
>>
>>
>> Thanks,
>>
>> Ben
> _______________________________________________
> moneydance-info mailing list
> moneydance-info at moneydance.com
> http://moneydance.com/mailman/listinfo/moneydance-info
>



-- 
Ben Walding :: ben at openxource.com
Web: http://openxource.com/