Skip to main content

Option to update pending status of duplicates in ActualBudget

Feature Request

Would be a nice QoL update to allow for existing pending transactions to be updated once they’re posted. Seems the duplicates logic in the import script currently prevents this. Only way around it at the moment is to prevent pending transactions in the first place, but would be nice to keep the pendings to ensure actual matches up with my accounts.

Thanks!

Posted by Jack Race ·
Status: On Provider3 comments

Log in to comment and vote

Comments3

  • Amr from Lunch Flow

    Team•

    Feb 10

    Hey @Jack 👋

    Thanks for the feedback! The reason behind the duplicates is that many pending transactions either don’t have IDs, or their IDs change once they’re confirmed. Sadly this is something controller by our upstream providers, and it’s one of the known limitations behind pending transactions, which is why I wasn’t too keen on implementing them in the first place 😅

    I can see how updating the pending status of duplicates can be useful, it might be a bit more involved though, but open to contributions if anyone wants to take a stab at it, so will keep this issue open 😄

    • Jack Race

      •

      Feb 10

      I see - no worries at all. In that case, I may switch back to ignoring pending transactions then. Trying to handle the edge cases could be painful 😬

      Thanks for the quick reply!

      • Amr from Lunch Flow

        Team•

        Feb 10

        Thanks for understanding, Jack! and keep the feedback coming 😄