- Joined
- May 7, 2018
- Messages
- 4
- Reaction score
- 1
- Country
We are the authors of a bookkeeping and fund accounting program for churches and charities (ACCOUNTS from Software4Nonprofits.com - not an ad, just telling you who's asking this!). Currently ACCOUNTS does not include importing of transactions from online banking, but we would like to include that at some point.
Our problem is that it's really hard to see what the right rules might be for matching downloaded transactions against manually entered ones. None of the other venders (like Quicken or Intuit) seem to publish comprehensive rules for how they do that, and it's clearly complex.
It would make sense to me to match on cheque numbers first, but what if other details (like the amount) don't match?
And if there's no cheque number, you could try to match on date and amount, but (a) there might be duplicates, and (b) there might be inaccuracies - like transactions that the bank doesn't think happened on the same date you thought it happened when you entered it manually into the accounting program. (That's probably even worse for credit card downloads.)
I would be very hesitant to include any matching on the Payee field because it's entirely likely that the spelling would differ between the manually-entered transaction and how the bank sees it.
Does anyone have either any exact knowledge of algorithms (detailed rules) used by other software for such matching, or well thought-out suggestions for how to do so?
Many thanks.
Our problem is that it's really hard to see what the right rules might be for matching downloaded transactions against manually entered ones. None of the other venders (like Quicken or Intuit) seem to publish comprehensive rules for how they do that, and it's clearly complex.
It would make sense to me to match on cheque numbers first, but what if other details (like the amount) don't match?
And if there's no cheque number, you could try to match on date and amount, but (a) there might be duplicates, and (b) there might be inaccuracies - like transactions that the bank doesn't think happened on the same date you thought it happened when you entered it manually into the accounting program. (That's probably even worse for credit card downloads.)
I would be very hesitant to include any matching on the Payee field because it's entirely likely that the spelling would differ between the manually-entered transaction and how the bank sees it.
Does anyone have either any exact knowledge of algorithms (detailed rules) used by other software for such matching, or well thought-out suggestions for how to do so?
Many thanks.