Bank Updates: what could prevent a SINGLE ledger entry from not appearing at the Quicken end?

Question

Both my father and I use Quicken Classic, but he no longer has the ability to troubleshoot or even go online all that well anymore, so I am posting this for him. His content would be scattered and incoherent, so it’s gotta be me doing the info request.

Within the last three months, a very curious problem has arisen within Quicken.

My parents get CPP and OAS, so there are four such entries into my father’s chequing account every month.

He can see these entries both on the bank’s website, as well as on the PDF statements he downloads from the bank.

However, when we do a bank update through Quicken, only three of the four entries get downloaded. One OAS line item does not - and consistently so, for the last three months.

What could prevent this line item from successfully making it down into Quicken? Is there a setting that allows Quicken to ignore/dispose specific line entries month after month?

And yes, I have already reset that specific account as well as all accounts that download data from the bank. I have also gone so far as to unlink all accounts and re-link them fully due to other unrelated issues with the bank sync.

rekabis · Answer

All dates between those two columns agree perfectly. Your suggestion was, unfortunately, not the answer.

> if the preference to replace the transaction date with the Downloaded Posting Date is enabled

This is not the case. This option no longer exists for our current version of Quicken:

Strange pattern though: the bank recorded those entries as “Canada Old Age” right up to and including April. For May, it changed to “CANADA Old Age Security”, and both entries were there for May. But all subsequent months had one OAS missing in Quicken. Not sure if this pattern has any relevance, adding it just in case it does.

mshiggins · Answer

@rekabis assuming the CPP and OAS pension payments are the same amount each month, it is possible the transaction is downloading but being matched to a previous month's transaction. When a downloaded transaction is incorrectly matched to an older transaction, the downloaded transaction - in effect - disappears. And once you start manually adding the missing payment, the incorrect matching continues to occur.

The easiest way to see if this incorrect matching is occurring is to add the Downloaded Posting Date to the account register. If the transaction date and the Downloaded Posting Date are different, that indicates in incorrect match. You can add/remove columns from the account register using the small square icon at the upper right of the account register. One thing that would prevent using this troubleshooting step is if the preference to replace the transaction date with the Downloaded Posting Date is enabled, you would not be able to see any date differences.

If the incorrect matching is occurring, the best solution would be to turn off the preference to Automatically Add Transactions to Banking Registers, then carefully check the downloaded transaction matches to ensure the transaction is matched to the correct transaction before accepting the downloaded transaction.