Transactions

Transactions explain how money moves through your accounts. They are the foundation for spending, income, cash flow, category rules, dashboards, spreadsheet exports, and many AI workflows.

Where transactions live

Open Transactions from the main sidebar. The page shows transactions across accounts included in the transactions view.

The page includes:

• Search by transaction text.
• Quick filters for All, Spending, Income, and Ignored.
• Category filter.
• Date filters for 7 days, 30 days, this year, last year, or a custom range.
• Sorting by date, merchant, account, institution, or amount.
• Inline category editing.
• Bulk tag actions.
• Bulk ignore or restore actions.
• Row actions for editing, creating rules, managing tags, and deleting eligible manual transactions.

The URL stores filters and pagination, so a filtered view can be shared with another workspace member who has access.

Transaction fields to review

When new transactions arrive, check the fields that most often affect reporting:

• Date: the posted transaction date.
• Authorized date: the date the transaction was authorized, when the source provides it.
• Institution and account: where the transaction came from.
• Name: the transaction name used for display and matching.
• Merchant name: a cleaner merchant value when the source provides one.
• Original description: the raw statement description when available.
• Amount and currency.
• Pending status.
• Source primary and detailed category.
• Current Tablewealth category.
• Categorization source.
• Ignored state.
• Internal transfer state.
• Tags.

Small source differences can create large reporting differences, especially in cash flow, category totals, and transfer handling.

Pending transactions

Pending transactions are useful for awareness, but they can change before they settle. A pending card authorization may disappear, post with a different merchant, change amount, or move to a different posted date.

Use pending transactions for monitoring. Avoid treating them as final in reconciled reports, monthly exports, or decision-ready dashboards.

Spending and income

Use the Spending and Income quick filters when you are reviewing cash flow.

In Tablewealth's transaction data, provider amounts often follow the source convention where outflows and inflows may use different signs. The app normalizes views and rule helpers so you can work with Spending and Income as user-facing concepts instead of memorizing provider sign rules.

If a transaction appears in the wrong cash-flow group, check the amount, source type, transfer flag, and category before changing the report.

Transfers

Transfers move money between your own accounts. They should not usually count as income or spending.

Common examples include:

• Credit card payments.
• Brokerage cash movement.
• Bank-to-bank transfers.
• Savings transfers.
• Loan payments split across principal, interest, or account movement.

Open a transaction and turn on Internal transfer when the transaction represents movement between your own accounts. This helps spending analysis exclude it.

If both sides of a transfer appear as separate spending or income events, review both transactions. The goal is not always to delete one side. Usually you want the records to remain traceable while reports understand that the movement is internal.

Ignored records

Ignore a transaction when it should remain in the workspace but not appear in the default transactions view.

Good candidates include:

• Duplicates from overlapping sources.
• Provider noise.
• Test imports.
• Records outside the scope of a report.
• One side of a source issue you are preserving for auditability.

Use the Ignored quick filter to review ignored transactions. Restore a transaction if it should return to the active view.

Prefer ignoring over deleting when you may need to explain why a record was excluded later.

Manual transactions

Manual transactions can be added for manual accounts. Use them when a real cash movement is not coming from a provider or import.

Manual transactions are useful for:

• Cash activity.
• Private account activity.
• Adjustments to manual accounts.
• Offline transactions needed for a complete report.

Manual transactions can be edited and, when eligible, deleted. Provider-backed transactions should usually be corrected through category, transfer, ignored, or source cleanup actions instead of deletion.

Categories in the transactions table

The category cell shows the current category for a transaction. It may come from:

• Your workspace category.
• A manual category override.
• A categorization rule.
• The source or provider category.
• No category, shown as uncategorized.

Click the category cell to choose an existing workspace category, use the source category, create a new category, or select another available category. When you manually change a transaction category, Tablewealth may suggest creating a categorization rule for similar future transactions.

Tags

Tags are flexible labels that can cut across categories. Use categories for the main reporting bucket and tags for secondary review needs.

Good tag examples include:

• Reimbursable.
• Tax review.
• Vacation.
• Subscription.
• Business.
• Needs receipt.
• One-time.

Use bulk tag actions when several selected transactions need the same label.

Source mismatches

If a transaction looks wrong, compare it with the original source.

Common mismatch patterns:

• Amount sign is reversed.
• Authorized date differs from posted date.
• Merchant name is normalized differently.
• Original description contains useful matching text that the merchant field hides.
• An imported file overlaps with connected history.
• Currency conversion is missing or unexpected.
• Pending and posted versions both appear temporarily.
• A source category changed after the first sync.

Start cleanup with duplicates and amount signs, then review transfer state, then category. That order prevents one source issue from creating several reporting issues.

Review routine

Use this routine after adding a new source or before a monthly review:

1. Filter to the review date range.
2. Search for obvious duplicates.
3. Review large positive and negative amounts.
4. Mark internal transfers.
5. Review uncategorized transactions.
6. Edit repeated merchant categories.
7. Create rules only for repeated patterns.
8. Add tags for secondary workflows.
9. Check the Ignored filter before finalizing the report.
10. Reopen dashboards or spreadsheet syncs after cleanup.

Transactions are where a lot of financial truth gets cleaned up. A few minutes here makes every dashboard and spreadsheet downstream easier to trust.