Skip to content
WealthMgr Docs

Insights

The Review page (sidebar label “Review”, with a count badge showing pending items) is your data-quality workbench. It surfaces four categories of issues: incomplete transactions, duplicate groups, subscription candidates, and projection rule matches that need disambiguation.

Incomplete transactions

An incomplete transaction lacks a source or destination account. This happens when a rule creates a transaction but cannot fill both sides — for example, after importing a bank export where the counterparty account is unknown.

Resolving an incomplete transaction

  1. Open Review in the sidebar.
  2. Find a transaction in the Incomplete section.
  3. Select the correct account for the missing field (from account or to account).
  4. Click Save.

The transaction is updated and removed from the list.

Creating a categorisation rule

After resolving an incomplete transaction, WealthMgr offers to create a categorisation rule. Click Create rule on any resolved transaction, confirm or edit the keyword, and save. The rule is added to Automations with keyword matching enabled.

Tip

Build up your categorisation rules over a few months and your transactions will mostly arrive already categorised.

Possible duplicates

Duplicate groups contain transactions the heuristic engine suspects are the same real-world event recorded more than once — common after importing data from a bank statement.

How duplicates are detected

The system compares transactions using two levels:

  • Hard match — same date, same amount, same currency, and either from or to account matches. Near-certain duplicates.
  • Soft match — same date and amount only. Potential duplicates flagged for manual review.

Resolving duplicates

  1. Find a group in the Possible Duplicates section.
  2. Review the transactions — check dates, amounts, and accounts.
  3. Click Merge to keep one transaction and delete the rest, or click Delete on specific duplicates.

Warning

Merging duplicates deletes all but one transaction in the group. This cannot be undone from the UI. Export a backup from Settings before doing bulk cleanup if you are unsure.

Possible subscriptions

When the heuristic engine finds recurring payments in your transaction history, it flags them here. Detection criteria:

  • At least 2 occurrences in different calendar months.
  • Same amount, description, source account, and destination account.
  • Not created by an existing rule.
  • Not marked as an installment payment (installments are handled separately).

Dismissed suggestions stay hidden and won’t reappear.

Create Bill vs Create Rule

Each detected subscription offers two actions, both prefilled from the transaction data:

Create Bill opens the bill setup wizard. A bill is a scheduled transfer with category bill. It creates:

  • An expense account (if needed) for the destination
  • An optional budget pocket in the source account
  • A monthly scheduled rule anchored to the day-of-month of the original transaction

Use Create Bill for recurring expenses — rent, utilities, streaming services.

Create Rule opens the generic rule editor. This creates a transfer rule without bill-specific metadata. Use it for recurring transfers between your own accounts, such as standing transfers to savings.

Tip

Both actions use the same detection logic. The difference is what gets created: "Create Bill" sets up expense tracking, while "Create Rule" creates a plain transfer.

Projection rule issues

This section shows rule-match reviews — automation rules whose target accounts or conditions were ambiguous at execution time. You can resolve each one by confirming the correct match or dismissing the suggestion. These affect how future projections compute; unresolved ambiguity means the simulation may include or exclude rules incorrectly.

Tier limits

The number of items you can review per month is limited by your subscription tier. The limit displays in the sidebar badge area. Upgrade for higher limits.

When to use Review

Check Review:

  • After your first few months, while categorisation rules are still thin.
  • After importing a bank statement or bulk transaction file.
  • As part of a monthly review alongside Reports and Alerts.