plaid-recurring-detection

To detect recurring transactions from Plaid data, you need a Plaid access token with the transactions product enabled. The skill analyzes your synced transaction history to identify subscription patterns, categorize inflows and outflows, and return structured recurring streams.

You need at least 60 days of synced Plaid transactions to accurately identify recurring streams. This historical window allows the analysis to detect repeating patterns, predict next charge dates, and determine the frequency of ongoing subscriptions and bills.

Yes, recurring transaction detection supports filtering by specific accounts. When you query Plaid transaction data using your access token, you can narrow the analysis to individual accounts to isolate subscription tracking and budgeting streams.

Tracking recurring bills returns structured data fields including stream_id, frequency, status, predicted_next_date, and is_active. These fields categorize inflow and outflow streams for subscriptions, utilities, and payroll to build a comprehensive budgeting view.

Plaid recurring detection categorizes inflow and outflow streams by analyzing transaction patterns across your accounts. It identifies recurring deposits like paychecks and recurring withdrawals like subscriptions or utilities, predicting future charges based on historical data.