Transactions

The Transactions tab is where every ledger entry for a client lives, no matter how it got there. Hand-entered, OCR'd from a receipt, imported from CSV — they all surface in one list.

Open it from any client → Transactions.

The list

Each row shows:

• Date — sortable
• Vendor or payer as the primary label; an amber dot appears next to the name if the AI flagged the entry as non-deductible or partially deductible
• Account badge — the CoA code this row is booked to (e.g. 500-200)
• Reviewed ✓ — green check if a teammate signed off (see Month-end close)
• Amount on the right — green for income, neutral for expense, grey for transfer; sortable

The list is sorted newest first by date by default. Click any header to re-sort. Up to 1,000 rows per filter window — if the truncation banner appears, narrow the date range with the filter bar.

Filtering and searching

Above the list, two controls let you narrow the data:

• Search box — free-text across vendor, description, and account (case-insensitive). Results update as you type.
• Multi-filter chips — add one or more structured rules via + Add filter. Each chip shows the active condition; click it to edit or remove it.

Using the multi-filter

Click + Add filter to open the filter editor:

1. Column — pick what to filter on: Date, Vendor, Account, or Amount
2. Operation — changes based on the column type:
   • Text: contains / does not contain / is / is not
   • Number: equals / not equals / greater than / less than / between
   • Date: equals / not equals / after / before / between
3. Value — type a value or pick a date from the calendar. For between, set both start and end.
4. Apply — commits the rule and closes the editor.

Applied rules are shown as chips below the search box. Click any chip to reopen its editor and tweak the rule. Hit × on a chip to remove that rule.

Multiple rules work as AND — all active rules must match for a row to appear.

Adding a transaction manually

Hidden from Viewers; available to everyone else. Click Add transaction above the list. The form asks for:

Save creates a source = 'manual' transaction. Behind the scenes it also posts a balanced journal entry to the ledger — for a transfer, that's the money debited to the to account and credited from the from account — so the entry shows up in the trial balance and reports (see How Kiravy's general ledger works). A background AI deductibility check runs automatically and tags it for tax review.

Editing and deleting

Open any transaction → all fields except workspace, client, and created by are editable. Those three are write-once to protect the audit trail.

To delete: Delete button at the bottom → confirm. This is a soft delete — the row is hidden from every list, filter, and search, but it isn't physically removed from the database. Recovery requires support.

Hard delete from the UI doesn't exist by design. Deleting tax-relevant data has 7-year retention implications in Malaysia.

The "Reviewed" workflow

When a senior accountant signs off on a row, they set reviewed_at on it. The list shows a green checkmark, and by default unreviewed entries float to the top of your view (because Unreviewed is the default filter).

Where does the review actually happen? Not on this tab directly — instead through the Month-end close Review queue, which is the bulk-review UI. Open an engagement, batch-tick a hundred rows at a time.

This is intentional: reviewing one row at a time on the Transactions tab would be tedious; the engagement workflow is built for closing a period systematically.

Sources, explained

Each transaction has an internal source tag (not displayed in the list, but visible on the detail page):

CSV import

For when you've got transactions in a spreadsheet that aren't worth re-typing. Import CSV button (next to Add transaction) opens a 4-step wizard at /clients/[clientId]/transactions/import:

1. Upload — drag-drop the file. CSV or Excel. Kiravy AI suggests a column mapping based on header names.
2. Mapping — confirm or adjust the mapping. You pick how amounts are encoded:
   • Typed: separate Amount + Type columns
   • Signed: one Amount column where positive = income, negative = expense
   • Debit/Credit: separate Debit and Credit columns
3. Preview — Kiravy shows you the parsed rows, with any errors highlighted, before anything is saved
4. Done — confirmation with a count and a back-link to the list

Every imported row gets source = 'csv' and an internal import batch id so you can find them again if something goes wrong.

Bulk edit

There isn't one — yet. Edit transactions one at a time on the detail page. The CSV import wizard lets you bulk create but not bulk update. A bulk-edit affordance is on the roadmap.

What each role sees

Cross-firm access doesn't exist — RLS at the database level enforces tenant isolation.

What's next

• Receipts (OCR) — when transactions arrive as photos
• Month-end close — for the systematic review pass
• Chart of Accounts — how the account field actually works