Bug 241521

Summary:	Improve tax automatism in split transactions
Product:	[Applications] kmymoney	Reporter:	andreas.grupe
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	REOPENED ---
Severity:	wishlist	CC:	alexander.reimelt, mfcarpino, ralf.habacker
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on:	514180
Bug Blocks:

Description andreas.grupe 2010-06-12 10:07:05 UTC

Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

If I create a split transaction and one of the split parts has a category which should split the tax of this transaction, the tax split is not made.


Kind regards

Andreas



Reproducible: Always

Steps to Reproduce:
Create a split transaction
Enter only one transaction - or more but one is enough to show -
Assign a category to it which should split the tax 
Submit


Actual Results:  
The whole amount is booked to the category, tax is not calculated

Expected Results:  
The amount should be booked to the assigned category without taxes and the rest to the account which collects the tax

Comment 1 Thomas Baumgart 2010-06-12 11:19:24 UTC

Yes, but it currently works as designed. So I changed this into a wishlist item and rephrased the title

Comment 2 Alvaro Soliverez 2010-06-12 13:57:04 UTC

What's the difference to bug 241322?

Comment 3 andreas.grupe 2010-06-12 14:03:16 UTC

Bug 241322 appears when you import several or mass change transactions. This one here is definitively related to it but appears on every normal split transaction with tax categories you do.

Comment 4 Thomas Baumgart 2010-06-12 14:48:29 UTC

Bug 241521 only affects manual data entry whereas bug 241322 is related to import or online download.

Comment 5 Michael Carpino 2018-03-01 15:17:31 UTC

Requested over 5 years ago and it had been added to wish list. Bug closed

Comment 6 Alexander 2026-01-04 10:17:03 UTC

I did just run into this issue with version 5.2.1 and don't understand the intent behind not supporting this. Is this an oversight and no one had time to fix it, or is this really intentional?
Since taxes are supported and work with regular bookings, I see this as a bug and not a wishlist feature.

Comment 7 Thomas Baumgart 2026-01-05 12:39:34 UTC

I'm sorry, but I must strongly disagree here. A feature for which a requirement (wish) is present but has never been implemented can't be a bug by definition. It's a missing feature at most and thus remains a wish list item.

There are some corner cases which have not been specified so far. E.g. how should the application handle multiple entries that refer to the same tax category in the split editor? Sum them up in one split or keep multiple tax splits?

Comment 8 Ralf Habacker 2026-01-06 13:35:58 UTC

With https://bugsfiles.kde.org/attachment.cgi?id=188244 the actual VAT support can be inspected.

Comment 9 Alexander 2026-01-11 20:42:55 UTC

(In reply to Thomas Baumgart from comment #7)
> I'm sorry, but I must strongly disagree here. A feature for which a
> requirement (wish) is present but has never been implemented can't be a bug
> by definition. It's a missing feature at most and thus remains a wish list
> item.
> 
> There are some corner cases which have not been specified so far. E.g. how
> should the application handle multiple entries that refer to the same tax
> category in the split editor? Sum them up in one split or keep multiple tax
> splits?
I talked with another user about the expected outcome. Applying the tax split to the category as well would be best since it makes no difference mathematically and the user had some reason for splitting in the first place.