FR: Rules: Mark as transfer between accounts

[6ixfalls]

Describe the feature

My inter-account transfers follow a pattern that the rules match. I want to categorize those transactions as a transfer between my accounts, and it should properly handle positive and negative debits as an in/out transfer respectively; the feature should be similar to the one in Firefly III.

Why is this feature important?

This is needed to have transfers easily categorized on imports rather than needing to do this for every transaction manually, which may add up due to automated transfers, etc.

Additional context, screenshots, and relevant links

No response

[zachgoll]

This "auto transfer matching" is already implemented at the system level. We automatically match any 2 transactions that have:

1. Opposite amounts
2. From different accounts
3. Within 3 days of each other
4. Same currency

#1852 is an open feature request for matching multi-currency transfers.

[6ixfalls]

I don't think that's a full solution to this issue. Ideally a matching transaction would be created as a result of this rule, because I have an account that syncs with Plaid but others that don't - being able to automatically create the matching transfers would save me a lot of time.

[zachgoll]

Is my understanding correct here? This is what you're looking for?

1. Plaid syncs an account and pulls in a transaction that represents the "inflow" of a transfer
2. An existing manual account in Maybe represents the "outflow" side of this, but since it's manual, there is no transaction created.
3. You want a rule that says, "when you see a Plaid transaction of XYZ nature, create the corresponding match transaction in account ABC"

[6ixfalls]

Exactly. I think it would be useful to not narrow the scope to Plaid inflows and support the opposite as well of course, and also not limit to Plaid transactions too because I could see this useful for people who have only manual accounts as well.

[zachgoll]

@6ixfalls yep, that makes sense. It would need to support all scenarios except for the Manual -> Plaid direction since we treat Plaid data as the "source of truth" and don't want outside sources creating Plaid transactions to overwrite that source of truth.