KMySync

Releases

• Oct 23, 2026 2.3
  ### New - **Bookings from push notifications.** For banks without FinTS, such as a credit card: KMySync reads the notifications of the banking apps you select in the profile settings. - When you enter a booking by hand, the app finds the matching notification and asks whether it should process future notifications for this account. - From then on, new transactions appear as a list of suggestions when you refresh – edit, delete or book them with OK; possible duplicates are marked. - The payee is found just like with voice input – via alias, earlier bookings and the location at the moment the notification arrived. If the payee was last booked as a transfer, the list suggests a transfer. - The note contains the exact wording of the notification. The raw texts stay on the device only briefly and are never part of a backup. - **KMyMoney database (SQLite).** Besides the `.kmy` file, KMySync can now read and write a KMyMoney database in SQLite format, with a cross-check after every write. - **Backups:** the number of backups is adjustable, plus permanent monthly backups. - **Receipt scanner:** in the variant with Google services it uses the Play services document scanner (automatic cropping and perspective correction).

  More…

  ### Even safer export - Self-check after every export: untouched parts must stay exactly as they were, character by character; new and changed transactions must be consistent; categories must sit in the right tree; the balance of each account must match the app's bookings. - Writing works the way KMyMoney itself does it – line by line, attributes in the file's order, amounts reduced. A line-by-line comparison shows what changed. - If the file is broken after an export, the app restores the previous version. - Export and import run in the background and wait instead of aborting when the connection drops briefly. ### Changed - Bookings reconciled in KMyMoney are read-only in the app; they can still be copied as a template. - Net worth is recalculated right after syncing with the KMyMoney file. - The watch app is much smaller (12 MB → 2 MB). - The alias question only appears when you corrected the payee by hand. ### Fixed - In some cases a category lost its side (income/expense). - The location of a booking was rewritten unnecessarily on save. - Line breaks in notes are written the way KMyMoney does it. ### F-Droid KMySync is now **on F-Droid**: https://f-droid.org/packages/de.spahr.ausgaben/ The F-Droid version is signed by F-Droid with its own key. That is why the F-Droid and GitHub versions **cannot update each other**. To switch, make a backup first, then uninstall and reinstall. **Downloads:** `app-full-release.apk` (with Google services, includes the Wear OS bridge) · `app-foss-release.apk` (no Google services) · `wear-release.apk` (smartwatch) ### Verifying this build This app is free software (GPL-3.0-only) and built from source — the F-Droid recipe builds the `foss` flavour straight from this tag. You can check that the file you downloaded is the file that was published: ``` sha256sum app-full-release.apk app-foss-release.apk wear-release.apk ``` ``` 0eb96a08a5cbd0a76fa7d81e18aaefa483b2a7dbfb9a0ccaaea3db263c251513 app-full-release.apk 1094002a220dfb8ec1314ff149eb7edd2c0f6a4358e38a6d26ec410378582dae app-foss-release.apk c467a88250e62f3692719ec93dc4bbbf999534a12e6fbef75ab018ab54d9469a wear-release.apk ``` All three are signed with the same key as every GitHub release since 1.0: ``` Signer certificate DN: CN=Michael Spahr, OU=Privat, O=Ausgaben, L=, ST=, C=DE Signer certificate SHA-256: 571fd757540602812eb32fc43882d4abff32b8d02614451304834485404afc3c ``` Check it yourself with `apksigner verify --print-certs <apk>` from the Android build tools. The `foss` build contains **no Google Play Services**; verified on the finished APK: ``` unzip -p app-foss-release.apk 'classes*.dex' | strings | grep -c com/google/android/gms # 0 ```