Dolla

Work with recurring items and the review inbox

Use the recurring workspace for pattern tracking and the Review section for transactions that still need decisions.

Recurring workspace

The recurring workspace lives in the shared Transactions hub at /transactions?tab=recurring. It helps you understand inflows and outflows that should repeat, such as salary, rent, subscriptions, or regular bills.

Use its local List, Audit, and Calendar views without leaving Transactions. List is for saved items, suggestions, and drift follow-up; Audit is for keep, cancel, or later decisions; and Calendar places recurring timing into a month view.

The list shows one table with filters for inflows and outflows. Sort by the next due date or largest monthly amount. Expand an item to see its matching details, review changes, edit it, or manage linked reimbursements. Table columns stay the same width when details open. On a phone, each row stacks its labelled values.

The summary shows monthly equivalents across all tracked items. Weekly and fortnightly payments are spread across the year; quarterly and yearly payments are divided into months. Each linked reimbursement uses its own frequency before it is deducted from its outflow. Net recurring cash flow is an estimate, not your available balance.

Open Review possible recurring payments below the list to inspect payment dates and amounts. Yes, track it adds an item, Not recurring saves a dismissal for your profile, and Review later hides that pattern for 30 days. Saved decisions also prevent that pattern from being auto-created for your profile while the decision applies. Patterns are checked within one account, with each payment fitting the schedule. Older patterns and future-dated transactions are not treated as current suggestions. Variable bills can appear for manual review.

Housing and loan meaning is optional. Open a saved outflow's details and choose Set housing or loan payment meaning when it applies. Dolla asks about that selected item; it does not assign a meaning from the merchant name or category.

The backend and some internal helpers still use the older subscriptions naming in places, but the user-facing workspace is now consistently called recurring.

If you opt into recurring auto-create in notification settings, high-confidence suggestions can be promoted into active recurring items automatically after successful imports or syncs. This requires at least four payments with consistent amounts and timing. Variable bills stay in manual review. Auto-created items identify their source in their expanded details.

If active recurring items, suggestions, or drift checks cannot load, the workspace shows a retryable error for the affected section instead of presenting an empty-state message. Failed create, update, delete, add, or dismiss actions stay visible so you can retry after the connection or server issue is resolved.

Review inbox

The Review row in Track opens /transactions?tab=review in the same hub. It is for things that need a human decision, such as transactions that need categorisation, confirmation, reconciliation, or follow-up.

The overview now starts with queue cards so you can see which kind of work is building up, then focus a single queue without leaving the shared Transactions hub.

When you open a queue directly, the URL keeps that focus so you can deep-link a specific review backlog to yourself or another household member. Use the queue controls to categorise, verify, assign an account, review a merchant suggestion, or open reconciliation work, depending on what that queue needs.

Focused queues with more than one page of items now show paging controls and an item-range summary, so larger cleanup batches do not get silently truncated.

Reconciliation mismatches open a side-panel workflow where you can compare statement periods, review likely cross-account transfer matches, and save reconciliation records for the affected account.

When to use rules instead

If the same merchant or description keeps appearing in review, create a smart rule. The review inbox is for exceptions and edge cases, not for permanent manual cleanup.