Bug 507864

Summary:	Consistency check results
Product:	[Applications] kmymoney	Reporter:	Herwig Janssen <herwig.janssen>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	5.2.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Herwig Janssen 2025-08-04 19:34:08 UTC

When I save my changes, I receive the following message. The consistency check has detected some problems in your data. The details are shown below. Problems that cannot be fixed automatically should be resolved manually.

Problems with entries
The sum of the allocations in the transaction “... ” is not zero.

This affects entries for the months 05-12/2016.

However, my current account book only starts on 02/01/2020.

Therefore, I have no way of correcting this.

I would like this message to no longer be displayed in the future.
What do I need to do?

Best regards,
Herwig Janssen

Translated with DeepL.com (free version)

Comment 1 Jack 2025-08-04 19:51:56 UTC

You get rid of the message by fixing the error in those transactions.  I suspect those old transaction are simply being hidden by some filter.
The first thing to do is copy one of the Transaction IDs from the consistency check and the enter it in the text field of the Find Transactions dialog, which you can display with Ctl-Shift-F.  If it doesn't display anything, go to Settings/Configure KMyMoney.  In the General section on the Filter tab,  at the bottom is a "Transactions" section which says "Do not show transaction prior to" with a date field.  See if that has been set to a too recent date.  Change it to 01-01-1900 and go back to the ledger and see if you now see the problem transactions.
I have no idea why you have transactions prior to what you think is the starting date for your data, but let's confirm whether that is really the case before other troubleshooting.

Comment 2 Bug Janitor Service 2025-08-19 03:46:31 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2025-09-03 03:48:25 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.