Sum of splits in transaction is not zero

Help
1

Hi there,

I have issues with the consistency check complaining about splits whenever saving. The problem does not exist in packaged Debian version (testing, v5.1.3), but only when using a newer version (currently latest master) compiled by my own.
Although it may be caused by some compile time setting configured wrongly, I very much suspect just the newer version being the “cause”.

It looks similar to this topic, but seems not to be caused by wrong signs.
Let me provide some example of transaction which is complained about:
```





```
Not knowing much about expected content (my knowledge is mostly based on aforementioned topic), it seems the corresponding split entry is lacking. This is supported by the fact that another transaction does not trigger this warning and indeed lists an additional split entry.
Anyway, KMyMoney complains about ”Sum of splits in transaction ‘T000000000000002014’ posted on 29.12.2025 is not zero.”.

Thinking about this now: Is this caused by the fact that I have not “classified” the transaction in question. Is that warning even expected?

Thanks for you support.

–
doak

2

Sorry, I’ve messed up the formatting. Since I can’t edit my original post (yet?), I just write it here as a reply:
<TRANSACTION id="T000000000000002014" postdate="2025-12-29" memo="xzy" entrydate="2025-12-29" commodity="EUR">
<SPLITS>
<SPLIT id="S0001" payee="P000030" reconciledate="" action="" reconcileflag="1" value="-1234/1" shares="-1234/1" price="0/1" memo="xzy" account="A000001" number="" bankid="A000001-2025-12-29-80cf650-1"/>
</SPLITS>
</TRANSACTION>

3

In fact, the warning is caused by the missing split (you should see an UNASSIGNED label in the ledger). Assign it a so called counter-account (category or account) and the the warning goes away. The warning is shown because your transaction violates double-entry accounting rules.

1 Like
4

Thanks for confirmation.
Just to clarify: This warning was introduced after v5.1.3, right?

5

Yes, that’s right. It was added in 2022 and appeared in version 5.2.0.

1 Like