v1.3.0 — Monthly timesheets, and renames that stick

Two fixes, no schema change — the database is untouched at v10, so this update carries no migration at all.

Renaming a client now updates everywhere

Editing a client saved correctly, but only the clients list showed it: the client's own detail screen and any invoice kept displaying the name they had when you opened them.

The cause was a single line. clientProvider was the only FutureProvider among otherwise-streamed entities — a one-shot read that cached the row and never looked again, so every screen built on it rendered whatever was true at load. It now watches the row like invoiceProvider and the rest.

Your data was never wrong; only the reads were stale. Nothing needs re-saving — open the app and the correct names are simply there.

Timesheets: monthly or quarterly

The timesheet card now has a Quarter / Month switch, with a month picker when you choose monthly. Hours are commonly reported to a client per month, which previously meant exporting a quarter and cutting it up by hand.

The switch lives in the timesheet card rather than next to the shared year/quarter picker, because it governs that report alone — a BTW-aangifte is filed per quarter, so the VAT return stays quarterly by design.

Exports are also named for their period now — timesheet_2026-08.pdf, timesheet_2026-Q3.pdf — instead of every export landing as timesheet.pdf and overwriting the last one.

Downloads

File	For
SoleLedger-1.3.0-arm64-v8a.apk	Android phones and tablets (almost certainly this one)
SoleLedger-1.3.0-armeabi-v7a.apk	Older 32-bit Android devices
SoleLedger-1.3.0-x86_64.apk	Android emulators / x86 devices
SoleLedger-1.3.0-macos.zip	macOS (Apple silicon + Intel)

APKs are split per ABI. Debug-signed personal builds; the macOS .app isn't notarised (right-click → Open the first time).