Transactions

Transactions is Eigenn's working ledger for money moving into and out of the business. It combines synced and manual transactions with receipt matching, categories, tags, owners, recurring-charge context, tax details, and review state.

Use this page to answer three questions:

• What moved, through which account, and in which currency?
• Does the transaction have the category, receipt, owner, and reporting treatment it needs?
• Which transactions still require a decision before the books or finance reports can be trusted?

Where Transactions Fits

These product areas use the same financial data for different jobs.

If a bank feed is stale, start in Settings → Account → Bank Connections. If a single row needs explanation or correction, start in Transactions.

Before You Start

You need an Eigenn workspace and at least one account for manual creation or CSV import. The account can come from a connected institution or be created as a manual account from an account selector.

Useful preparation includes:

• the date range or account you intend to review
• receipts or invoice files for unreconciled expenses
• the categories and tags your reporting process uses
• a clear owner for transactions that need follow-up

See Bank Connections when the ledger does not have a source yet.

What the Transactions Page Includes

Summary and working set

The summary strip reflects the current transaction set and shows:

• money in
• money out
• net movement
• transaction count and pending count
• review-queue count
• recurring count
• a reviewed percentage and short owner-focus prompts

The table also shows how many rows are loaded and selected. When a view contains multiple currencies, use account filters and the per-currency footer breakdown rather than treating values from different currencies as one total.

All, Review, and Subscriptions

• All is the operating ledger and respects the active search, filters, and sort.
• Review loads transactions that still need attention. It deliberately ignores the filters configured on All so the full review backlog is not accidentally hidden.
• Subscriptions shows recurring transaction streams and repeat charges.

The Review count is live. A transaction enters that queue when it has a pending receipt-match suggestion, or when it has no attachment and has not been marked completed. Excluded and archived transactions are not included in the unfulfilled branch of that queue.

Search and filters

The search box accepts plain search text and natural-language requests such as “Software and taxes last month.” The filter menu supports:

• date range and amount range
• status: completed, uncompleted, pending, archived, excluded, or exported
• attachments: has attachments or no attachments
• source: manual or bank connection
• type: income or expense
• assignee, category, tag, and account
• recurring cadence: all, weekly, monthly, annually, or irregular

Active filters appear as removable filter chips. Clear filters restores the unfiltered ledger.

Ledger columns and inline changes

The table can show date, description, amount, tax amount, category, counterparty, tags, account, method, assignee, reconciliation status, receipts, and row actions. Use the column control to hide optional columns. Date, description, amount, category, counterparty, tags, account, method, assignee, and status-related columns support sorting where available.

You can change categories, tags, and owners directly in the table. A row also flags pending transactions, recurring activity, and possible duplicate charges with a similar merchant, amount, and nearby date.

Work a Transaction

Click a row or choose View details from its action menu. The detail sheet includes:

• source, status, method, counterparty, merchant, bank account, balance, base amount, and FX rate
• category, owner, and tags
• a suggested receipt or invoice match when one is available
• attachments, transaction splits, tax information, recurring settings, metadata, and notes
• the source's internal transaction identifier and processing state

Use the arrow keys while the detail sheet is open to move to the previous or next loaded transaction.

Categorize and organize

Choose a category in the row or detail sheet. The detail-sheet flow can suggest applying the same category to similar transactions. You can also create a category from the non-headless category selector, then add existing or new tags and assign a team member.

For a repeatable policy, create a deterministic rule instead of accepting the same similarity prompt every month. See Transaction Categories and Rules.

Reconcile with a receipt or invoice

Use Attach receipt from the row menu, or open Attachments in the detail sheet. You can:

• upload a PDF or supported image
• search for an existing attachment
• select an invoice file
• confirm or decline a suggested match

Selecting an invoice as the attachment marks that invoice paid using the transaction date, so confirm that the invoice and payment truly belong together.

An attached file or a manually completed transaction is shown as Matched. An unfulfilled row is shown as No receipt. A pending suggestion still needs a confirm or decline decision even if other fields look complete.

Split across categories

Open Split to divide one transaction across multiple categories. Every part can be categorized or left uncategorized, but the parts must add up exactly to the transaction amount before Save splits becomes available.

Control reporting treatment

The detail sheet's Exclude from analytics switch marks the transaction as internal. It is intended for movements such as transfers between accounts that would otherwise double-count profit, expense, or revenue.

This differs from the row or bulk Exclude action:

Add Transactions

Open the add menu on Transactions to choose one of four workflows:

• Connect account starts the bank-connection flow.
• Import/backfill uploads historical transactions from CSV.
• Create transaction adds one manual transaction.
• Upload receipts starts receipt ingestion for matching.

A manual transaction requires a description, amount, currency, account, and date. It can also include a category, owner, attachment, internal/reporting treatment, and note. Only manual transactions expose full edit and direct-delete actions in the ledger.

Bulk Actions and Export

Select rows to make one change across a working set. Bulk actions can:

• set a category
• add or remove shared tags
• exclude or include rows
• archive or unarchive rows
• assign an owner
• mark rows completed or uncompleted
• set weekly, monthly, or annual recurring cadence
• move archived, excluded, or exported rows back to review

Delete is available only when every selected row is manual. Bank-fed rows retain source traceability; remove them only by deleting the owning account or connection, which is destructive to all associated transactions.

Export works on selected rows. It can produce CSV, Excel, or both, optionally email the result to an accountant, and remembers the workspace's export settings. Exported rows remain visible in the ledger with exported state.

States and Limits

• Review ignores the filters from All and loads up to 10,000 rows in its working set.
• An actively filtered All view also loads up to 10,000 matching rows for analysis and export.
• Receipt uploads accept PDF and supported image formats and are limited to 3 MB per file.
• CSV import accepts one CSV file up to 5 MB and requires at least two data rows.
• Manual transactions can be edited and deleted directly. Bank-fed transaction source fields are not directly editable.
• The default ledger hides excluded and archived rows. Use the status filter to find them.
• A category, owner, tag, note, split, attachment, or analytics treatment can still be changed on a bank-fed transaction without changing the provider's source record.

Verify the Result

Before leaving the page, confirm that:

• the intended account, date, amount, and currency are visible
• the category and reporting treatment are correct
• a receipt is attached, the match suggestion is resolved, or completion without a receipt is intentional
• split amounts equal the original transaction amount
• the right owner and tags are present
• the transaction no longer appears in Review when no further action is required

Troubleshooting

The Review count does not decrease

Open the transaction and look for a pending suggested match. Mark as completed satisfies the no-receipt requirement, but a separate pending suggestion still needs to be confirmed or declined.

A transaction disappeared

Clear filters, return to All, and check the archived, excluded, and exported status filters. Also verify that its bank account has not been disabled or removed in Settings → Account → Bank Connections.

A bank transaction will not show Edit or Delete

Full edit and direct delete are limited to manual rows. Categorize, tag, assign, attach, complete, or exclude a bank-fed row instead. Removing its bank account or connection also deletes every associated transaction.

A receipt upload fails

Use a PDF or supported image smaller than 3 MB. If a file with the same name is already attached, rename it before retrying.

The totals look wrong in a multi-currency view

Filter to one account or one currency context and use the footer's per-currency breakdown. Do not add unlike currencies together without an explicit conversion basis.

Synced data is stale

Go to Settings → Account → Bank Connections, inspect the connection state, and run a manual sync or reconnect. See Connect Transaction Records.

Related Pages

• Transaction Categories and Rules
• Bank Connections
• Connect Transaction Records
• Reconcile and Categorize Transactions
• Maintain Transaction Rules
• Document Processing
• Invoices