All Docs
FeaturesMaking Tax DigitalUpdated February 27, 2026

Known Issue: Manual Transactions Cannot Be Deleted

Known Issue: Manual Transactions Cannot Be Deleted

Status: Open — fix scheduled for a future release
Severity: Low
Introduced: v1.0.209 audit

What Is the Issue?

Transactions that are manually created through the app cannot currently be deleted. The transaction router (src/lib/routers/transactions.ts) provides mutations for creating and recategorising transactions, but does not expose a delete or exclude mutation.

This means if you accidentally add a duplicate transaction, the record will persist in your ledger even if it is no longer needed.

Who Is Affected?

This affects any user who:

  • Manually enters transactions through the app interface.
  • Accidentally creates a duplicate entry.
  • Wishes to clean up their transaction history.

Transactions imported automatically from the AgentOS API are not typically duplicated, so those users are less likely to encounter this in practice.

What Is the Impact?

AreaImpact
HMRC MTD Submissions✅ Not affected (use the workaround below)
Quarterly Summaries✅ Not affected (use the workaround below)
Transaction List / Ledger View⚠️ Duplicates will remain visible
Transaction Count Totals⚠️ Inflated by persisted duplicates

Workaround

You can prevent a duplicate transaction from affecting your HMRC submissions and quarterly summaries by marking it as unused:

  1. Go to the Transactions section for the relevant property.
  2. Find the duplicate transaction.
  3. Click Recategorise (or edit the transaction).
  4. Set the HMRC Category to unused.
  5. Save the change.

The transaction will now be excluded from:

  • All quarterly summary calculations.
  • HMRC Making Tax Digital submissions.
  • Property-level income and expense totals.

Note: The transaction record itself is not removed. It will still appear in the full transaction list with the unused label.

What We Are Doing About It

A delete mutation will be added to the transaction router in a future release. This will allow users to permanently remove manually created transactions from their ledger. A soft-delete (exclude) option may also be introduced to provide a recoverable alternative.

No action is required from users in the meantime — applying the unused category workaround fully protects your HMRC submission accuracy.