Recurrence
Understanding recurrence in financial transactions is crucial for categorizing and predicting future cash flows. The Recurrence API allows you to identify and categorize recurring patterns found in the transactions of an account holder, such as periodic payments or subscriptions. These patterns are classified into a recurrence type and a recurrence group that encodes detailed information about its periodicity, transaction counterparty and amount metrics.
Understanding recurrence
We employ a machine learning model to identify recurring transactions and group them together. This model is designed to detect patterns of recurring transactions while filtering out noisy data, such as frequent transactions that may have similar periodicity by chance rather than being truly recurring. The model is able to categorize transactions into a recurrence type and group noncontiguous transactions, so even if there is a gap in a pattern - say missing a month on a monthly subscription over a year, it is still recognized.
Recurrence groups
A recurrence group is a grouping of transactions with the same recurring pattern. Every transaction in a recurring pattern shares the same counterparty, but not necessarily amounts. This means that:
- We might have transactions with different amounts in the same recurring group.
- There could be multiple recurrence groups per counterparty/general category.
- We could have non-recurrent transactions with a counterparty (e.g Amazon Web Services) even if thereβs already transactions with the same counterparty belonging to a group.