Bank sync education

Plaid recurring transactions: bills, subscriptions, and income

Learn what provider-detected recurring patterns can reveal, where detection can be incomplete, and what Expense Atlas currently supports through standard transaction history.

Why recurring transactions matter

Recurring detection is more than a list of bank transactions

A transaction feed by itself is just a list of charges and deposits. Recurring data products analyze that history for streams such as rent, payroll, subscriptions, utilities, insurance, and loan payments that appear on a predictable cadence.

Expense Atlas currently imports standard transaction history, but it does not provide Plaid Recurring Transactions or an automatic recurring-charge review list. You can still review imported merchants and categories while keeping known obligations accurate in your planning inputs.

If you want to review bills and subscriptions from the standard transaction history Expense Atlas already supports, use the recurring-expense use case. It describes manual merchant, date, and amount review. Expense Atlas does not currently include Plaid Recurring Transactions.

Track subscriptions and bills from transaction history

Signals recurring-data tools may evaluate

Same merchant appearing on a predictable cadence
Similar amount ranges month after month
Known payroll, utility, rent, insurance, or subscription merchants
Transfers and deposits that repeat on weekly, biweekly, monthly, or annual schedules

How Expense Atlas currently uses transaction history

Standard bank sync and supported imports bring activity together for review. They do not automatically create a complete or confirmed list of subscriptions and bills.

1

Sync or import transaction history

Expense Atlas can bring in standard bank transactions, statement uploads, CSV files, and supported receipts for you to review.

2

Review merchants and categories

Use the imported history to inspect repeated merchants and correct categories. Expense Atlas does not automatically turn those repeats into a confirmed subscription list.

3

Confirm planning inputs

Keep known expenses, debt minimums, income, and goals accurate so the Personalized Budget starts from obligations you have reviewed.

Common patterns recurring-data products may identify

Subscriptions

Streaming, software, memberships, and recurring card charges.

Income

Paychecks, deposits, freelance payments, and repeated transfers.

Bills

Rent, utilities, insurance, phone, internet, and loan payments.

Frequently asked questions

Separate provider capabilities from the transaction tools available in Expense Atlas today.

What are Plaid recurring transactions?

Plaid Recurring Transactions is a separate provider product that can identify streams of repeated income and spending from eligible transaction history. Coverage and confidence depend on the institution, account, and available history.

Why do recurring transactions matter for budgeting?

A reviewed recurring pattern can help distinguish known obligations from flexible spending. Detection can be incomplete or wrong, so a person still needs to verify the merchant, amount, timing, and whether the charge remains active.

Does Expense Atlas include Plaid Recurring Transactions?

No. Expense Atlas currently supports standard bank transaction sync and supported statement, CSV, and receipt imports. It does not currently provide Plaid Recurring Transactions or a dedicated workflow that automatically finds and confirms every recurring charge.

Bring reviewed transaction history into your budget

Compare plans for Plaid-powered bank sync, or review the full connection workflow and its account, institution, and refresh limits.