Hey Norman! Unfortunately this is an issue on how DAS receives transactions from banks. DAS will get 1 pending record and when it posts, we get another posted record. Our provider, Plaid tries to auto match pending to posted,but sometimes does to do so. DAS also takes a shot at matching if Plaid fails to do so base on the 2 transaction data. If DAS isn't confident enough on the match it won't combine the two. So what happens here is DAS reverts the original modifications (and puts money back in your bucket) and the new transaction takes its place. This only happens when assigning a bucket to a pending transaction. Posted transactions are final so DAS will 100% keep its changes. The same is true for auto spending from buckets. DAS will respend from the bucket just like the pending transaction. That being said, you should shoot me a message in the app of the transaction you're experiencing and I'll do my best to tweak the matching process to better understand and handle this specific case!
You can also check out this ticket for more info on the whole DAS spending process. It's actually closely related to this ticket https://dasbudget.canny.io/admin/feedback/bugs/p/pending-tra…