actualbudget/actual

[Bug]: Custom Reports with 'Tag' filters do not calculate values of tagged top level split transactions

Open

#5,640 opened on Aug 28, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (603 forks)batch import
bughelp wantedreports

Repository metrics

Stars
 (7,129 stars)
PR merge metrics
 (Avg merge 4d 13h) (170 merged PRs in 30d)

Description

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I created a custom Pie Chart report to break down the amount spent with a Tag filter. The numbers were definitely wrong, when I realized I had tagged the Top Level of a split transaction instead of tagging each individual line item under the transactions

How can we reproduce the issue?

Create a split transaction in an account and tag the top level of the split with a tag:

  • Test transaction #test-tag = $50
  • Plane Ticket #test-tag = $1000 --- Ticket = $750 --- Seat Upgrade = $250

Create a custom report with the filter Has Tag #test-tag

See that the value will be equal to $50 instead of $1050

Now, if you tag each subtransaction of the split transaction with #test-tag, then you will see that the chart is properly calculated

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Contributor guide

Research direction
Investigate the report filtering logic for tags. Trace how split transactions are handled when the tag is applied at the top level versus individual subtransactions. Look in the codebase for functions related to report filtering, specifically tag based filtering. Check if the top level tag is being propagated to subtransactions or if only subtransaction tags are considered.
Tech stack
javascript
Domain
backendfrontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70