Transactions

Transactions is the Eigenn ledger for money that moves into and out of the business. It combines synced and manual transactions with receipt matches, 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 need a decision before you can trust the books or the finance reports?

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. You can also create a manual account from an account selector.

Useful preparation includes:

• the date range or account that you intend to examine
• receipts or invoice files for unreconciled expenses
• the categories and tags that 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 covers the current transaction set. It 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 Eigenn loaded and how many rows you selected. When a view contains many currencies, use account filters and the per-currency footer breakdown. Do not add values from different currencies into one total.

All, Review, and Subscriptions

• All is the main ledger. It respects the active search, filters, and sort.
• Review loads transactions that still need attention. It deliberately ignores the filters that you set on All. This keeps the full review backlog visible.
• 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. A transaction also enters that queue when it has no attachment and no completed mark. The unfulfilled branch of that queue does not include excluded or archived transactions.

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. You can sort the date, description, amount, category, counterparty, tags, account, method, assignee, and status-related columns 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 the same category for similar transactions. You can also create a category from the non-headless category selector. Then add current or new tags. Then assign a team member.

For a repeatable policy, create a deterministic rule. Do not accept 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 attachment that already exists
• select an invoice file
• confirm or decline a suggested match

When you select an invoice as the attachment, Eigenn marks that invoice paid with the transaction date. Confirm that the invoice and the payment truly belong together.

Eigenn shows an attached file or a manually completed transaction as Matched. Eigenn shows an unfulfilled row as No receipt. A pending suggestion still needs a confirm or decline decision, even when the other fields look complete.

Split across categories

Open Split to divide one transaction across many categories. You can give a category to each part or leave a part uncategorized. The parts must add up exactly to the transaction amount before Save splits becomes available.

Control reporting treatment

The Exclude from analytics switch in the detail sheet marks the transaction as internal. Use it for movements such as transfers between accounts. Without it, these movements 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 to find matches.

A manual transaction needs a description, amount, currency, account, and date. It can also include a category, owner, attachment, internal/reporting treatment, and note. Only manual transactions show 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 keep source traceability. To remove a bank-fed row, you must delete its account or connection. That deletion destroys every associated transaction.

Export works on selected rows. It can produce CSV, Excel, or both. It can also email the result to an accountant. It keeps 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 All view with active filters also loads up to 10,000 rows that match, for analysis and export.
• Receipt uploads accept PDF and supported image formats. Each file has a limit of 3 MB.
• CSV import accepts one CSV file up to 5 MB. The file needs at least two data rows.
• You can edit and delete a manual transaction directly. You cannot directly edit the source fields of a bank-fed transaction.
• The default ledger hides excluded and archived rows. Use the status filter to find them.
• On a bank-fed transaction, you can still change the category, owner, tag, note, split, attachment, or analytics treatment. This does not change the provider's source record.

Confirm the Result

Before you leave the page, confirm that:

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

Troubleshoot

The Review count does not decrease

Open the transaction. Then look for a pending suggested match. Mark as completed answers the no-receipt condition. A separate pending suggestion still needs a confirm or decline decision.

A transaction disappeared

Clear the filters. Return to All. Then check the archived, excluded, and exported status filters. Also confirm that nobody turned off or removed its bank account in Settings → Account → Bank Connections.

A bank transaction will not show Edit or Delete

Full edit and direct delete work only on manual rows. Categorize, tag, assign, attach, complete, or exclude a bank-fed row instead. If you remove its bank account or connection, Eigenn 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. Then try again.

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. Examine the connection state. Then 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