Vereinsbuchhaltung - Releases

Fixed: - Duplicate accounts in the autocomplete: Frequently used accounts were also listed in their category group and showed up twice in a row when searching. Now listed once. - Search field in the "Pick receipt from folder" popup sometimes didn't react: A fast click could leave focus stuck on the modal backdrop, so clicks and typing went nowhere. Fixed – the same fix now applies to the account, bank account, and member dialogs. - Icon in the "Pick from folder" button was misaligned: The button was too narrow for icon and text together. - The getting-started card briefly flashed on load: It appeared for a moment even when everything was already set up. - Period selector stayed empty after a load error: A single failed request left it empty with no error and no retry. Now retries up to three times, then shows an error.

New: - Watch folder for receipts. Besides the internal storage and the user folder managed by the app there is a third storage type (cog → Receipts → "Storage type"): a folder in the Files app whose files, including all subfolders, can be picked when booking ("Pick from folder", with search and preview). The files stay where they are – renaming or reorganising them inside the watch folder does not break the link, the app remembers the Nextcloud file id. Receipts uploaded or photographed from the app are stored under <folder>/<year>/ and may be reorganised afterwards. The folder has to exist in the Files app beforehand and must not overlap with the watched folder for bank statements. It is chosen by clicking in the folder tree of the user's home ("Choose folder…" next to the path field) – a typo in the path is ruled out. The same tree is now available for the watched folder for bank statements. - The overview reports documents without an entry. If the watch folder holds a file that is not attached to any entry yet, the overview shows "x documents not yet assigned to an entry" – an invoice still to be paid, for instance. "View" opens the inbox with "Create entry" per file. A second tile warns about receipts whose file was deleted or moved out of the watch folder; the audit ZIP keeps listing such receipts in fehlende_dateien.txt. - The app never deletes a file in the watch folder. "Delete receipt" means "Unlink" there – the files also stay when an entry is deleted or all data is wiped. The same file may be attached to several entries, e.g. a split invoice. - When switching on, receipts the app stored under <folder>/<entry id>/ so far get their file id filled in – the existing receipt folder can become the watch folder directly. If a different folder is chosen, the old receipts count as missing until they are moved there.

Changed: - The Nextcloud viewer only opens a receipt when the file lives in the home of the signed-in user; everyone else gets the app's own view. Until now the viewer failed for anyone who did not own the storage folder. - Opening a receipt no longer creates folders, and receipts from the internal storage stay readable after switching the storage type.

New: - The fiscal year no longer has to match the calendar year. Under the gear icon → Fiscal year you can now choose when it starts: presets cover the calendar year, October–September, the school year August–July and half-year periods (semesters), plus a custom rule with any start day and a period length of 1 to 12 months (divisors of 12). Clubs with a deviating fiscal year previously had to add up their figures outside the app (issue #8). - The header's “Year" has become a “Period". Every period carries a freely editable name – suggested as “2026" for a calendar year, “2025/26" for a deviating one and “2025/26-1" for a winter semester. Entry numbers, reports, the budget, the receipt ZIP and the year-end lock all refer to the period rather than to a year number. - Periods can be maintained individually. The boundary between two open periods can be moved – the way to a short transitional fiscal year. An empty period at either end of the chain can be removed, and the next one created at the press of a button. - Switching shows what it will do first. Before a changed rule takes effect, a preview lists the resulting periods, how many bookings will change period, and which budget figures would be lost – because when two periods merge, an account can only keep one of the two figures. Locked periods block the switch: what the general meeting approved does not move afterwards. - The cash report names the actual key dates. The asset overview used fixed column headers “Balance Jan 1" and “Balance Dec 31"; it now shows the first and last day of the selected fiscal year. - The monthly chart on the dashboard follows the fiscal year. It always ran from January to December; with October–September it now starts in October, and a semester shows six months.

Changed: - The settings section Year-end closing is now called Fiscal year and holds the rule and the list of periods alongside the locking. - The xbuc import now derives a file's fiscal year from its date range instead of the calendar year. A file for a deviating fiscal year could not be assigned at all before. Bookings outside the range are dated to the first or last day of the period rather than to January 1 / December 31. - Existing installations are unaffected: the migration creates one period per previous calendar year, running Jan 1 to Dec 31 and named after the year. Entry numbers and existing locks are left untouched. If you change nothing, you notice nothing.

Fixed: - Opening the booking dialog before the account list had loaded left the cash account empty – and booking then only reported that it was a required field. The preselection is now filled in as soon as the accounts arrive. - Switching the period right after loading occasionally showed the journal and evaluation of the previous period: of several simultaneous requests the last to arrive won, not the last one made. A choice made before the periods had loaded did not stick either.

New: - Entries can be edited straight from the account statement. When you spot a mistake while going through an account in the Accounts tab, you can fix it on the spot: the pencil at the end of the row opens the same entry dialog as the Entries tab – for the description, both accounts, and turning the entry into a split entry. Until now you had to note the entry number, switch views and search for it there (issue #39). - Receipts are visible in the account statement. If an entry has a receipt attached, the row shows the paperclip and a click opens it. That includes the auditor role, which cannot change anything otherwise. - A tidier row: Reassign and Delete now live in the three-dot menu, exactly as in the Entries tab. Otherwise the row would have wrapped onto a second line in narrow windows.

Fixed: - The account statement refreshes after an entry is edited. Description, contra account and running balance used to sit there outdated until the next account switch whenever the entry had been changed elsewhere.

Fixed: - In Firefox the year in date fields is fully visible again. Since version 109 Firefox draws a calendar button inside the input, but does not account for it in the width Nextcloud gives to every input field – it therefore covered the last digits of the year, turning "07/09/2026" into a visible "07/09/202" (issue #43). Every date field in the app is now wide enough: entry date, next and first due date, mandate date, opening balance, open items, SEPA due date and the short report's period. - On phones the buttons inside dialogs are thumb-sized again. The 44px minimum for touch targets only applied outside dialogs – Nextcloud attaches dialog content to a different place in the page, so the rule never reached it. In the entry dialog Cancel and Book were only 34px tall and the Income/Expense toggles 40px; this now applies in every dialog. The round help button next to the spheres is properly round again – it was stretched into an oval on phones and on the desktop alike – and grows to full touch-target size under a finger. - The receipt ZIP export contains all receipts again. With the receipt storage set to app-internal, the archive came out empty and listed every receipt in fehlende_dateien.txt as not found – even though each one opened and downloaded perfectly on its own (issue #40). The files were never gone: while building the archive the app read them in a way that only exists for storage inside the Nextcloud file tree, not for the app-internal one. Only the ZIP export was affected, and only with app-internal storage. On top of that, fehlende_dateien.txt now states the reason for each entry instead of reporting every failure as "not found".

Fixed: - The report sub-tabs are fully reachable again on narrow screens. The bar holding Summary, Reporting groups, Spheres, Reserves, Budget and Log ran off the screen and could not be swiped – it ended after Spheres, and the More exports button was out of reach as well (issue #38). The bar can now be swiped sideways and indicates at its edges that there is more to come; jumping straight to one of the later tabs from the help or the bottom bar scrolls it into view automatically. The same applies to the sub-tabs under Entries and Contributions and – with the Nextcloud sidebar open or with longer labels – on the desktop too. - Amount fields now show the amount the way it appears next to them: "20.000,00 €" instead of "20000". In the budget, the Plan column was a bare number sitting next to the formatted Actual and Difference columns – with four- and five-digit figures it was hard to tell 5,000 from 50,000 (issue #34). The same applies to every other amount field: entry amount and split lines, opening balance, open items, membership fees and the default fee. While editing, the field still shows the bare value so that typing does not fight a live format; both notations are accepted – "20000", "20.000,00" or "20000.5". Anything unreadable restores the previous value instead of silently setting it to 0. - The treasurer's report and the short report moved into the More exports menu on phones. As separate buttons they no longer fitted into the row and pushed the menu off screen. The short report's date field is now part of that menu; nothing changes on the desktop.

New: - The header now shows the funds across all cash accounts, no longer just the first one. Until now the top right only ever showed the first cash account by account number – anyone running a cash box (1000) and a bank account (1200) therefore saw the cash box of all things, while the bank account stayed invisible (issue #31). The figure is now called Funds and adds up every cash account; the tooltip breaks it down by account and names the transactions not yet assigned. If the club runs only one cash account, its name still appears there – nothing changes for those clubs. - Individual cash accounts can be left out of that figure. For cash accounts the account dialog offers a new Counts towards the funds shown in the header flag (default: on). A fixed-term deposit account can thus stay out of the day-to-day figure without disappearing from the books: the cash report, the assets overview and the trial balance keep counting every cash account. The flag is display only and is therefore not locked by the finalization of a fiscal year either. - The cash-account table on the dashboard and in the evaluation has a total row – as soon as the club runs more than one cash account; with a single one it would merely repeat the row above it. If at least one account is excluded from the funds figure, an of which funds (header) row appears below it, and the accounts concerned are marked as such in the list – so it stays clear how the figure at the top comes about.

Changed: - Clicking an account that has sub-accounts now expands them. Previously this only worked through the small arrow in front of it, which was easy to miss. Collapsing still goes through the arrow – a second click on the row deliberately does not collapse it again, otherwise you could not select a parent account without closing it. - The posting text now grows with its content. Longer text wraps and is shown in full instead of running off the side of the field – when creating a posting as well as when editing one. The value itself stays single-line, so nothing changes for the journal, exports or the API. - Dialogs have a little more room to the edge. Content and buttons used to sit rather close to it.

Fixed: - The charts ignored dark mode. Axis labels and grid lines stayed black and were barely visible on a dark background – both on the overview and in the reports. The cause was a check for a theme--dark class that Nextcloud never sets, so the condition was always false. The charts now read their colours straight from Nextcloud's design variables and therefore follow any theme – light, dark, high contrast, and club colours set through the theming app. Changing the theme while the app is open redraws them. - Success and error messages (toasts) appeared at the bottom left. Nextcloud still shows its own messages at the top right, so one screen ended up with two kinds of toast in two different corners. @nextcloud/dialogs 7.5.0 moved them to the bottom left and dropped the position option; the app now puts them back where they belong. - The active button had a white border. Visible on the Income/Expense switch in the posting dialog, on active filter chips, on the underline of the active sub-tab and on the side selector when reassigning. Nextcloud claims button.active for its own pressed state and overrode the app's border colour. - The focus ring was clipped in the posting dialog. Tabbing through the dialog showed only a sliver of the ring around Income and Expense – the switch cut it off. - The posting dialog could be scrolled sideways. The hidden receipt file input claimed its full intrinsic width and pushed the dialog past its edge, producing a scrollbar. - Accounts with sub-accounts broke out of the account tree. They were bold and noticeably taller than their siblings, and their columns sat a few pixels further right. The cause was the expand arrow: on parent accounts it is a button, and Nextcloud gives every button a minimum height of 34px plus a margin – which grew the row to 46px while leaf rows stayed at 29px. All rows are now the same height and weight; the arrow alone marks an account as having children. The faint placeholder dot in front of accounts without sub-accounts is gone as well – it looked like a bullet point; the placeholder still keeps the column aligned. - Text hugged the edge in the "What's new" dialog. It now uses the same inner spacing as every other dialog.

New: - Receipts can now be attached while creating a posting on the desktop, too. On the desktop the New posting dialog shows the same Receipts section as the edit dialog: the selected files sit in a list (with a remove button) and are uploaded as soon as the posting is saved. Until now this only existed in the mobile view (windows up to 640 px) – on the desktop you had to save the posting first and then open it again (issue #29). File type and size are checked as soon as you pick a file: anything the server will not take (only PDF, JPG, PNG, GIF, WebP; 20 MB at most) is reported by name right away instead of after the posting has been saved. If an upload fails anyway – a dropped connection, say – the files concerned stay in the dialog and can be sent to the meanwhile created posting via Upload again, while the other receipts are already attached. While saving and uploading, the button is disabled so that a second click cannot turn into a second posting.

Fixed: - The Attach button could only be reached with the mouse. The file field behind it was hidden via hidden and therefore dropped out of the tab order – anyone operating the app from the keyboard could not get to the receipts at all. The field is now focusable and shows the focus on the button, on mobile as well as on the desktop.

Fixed: - Success and error messages (toasts) rendered as bare text in the top-left corner. Since 0.29.0, confirmations such as "Settings saved." sat unstyled across the header instead of appearing as a box at the bottom left. The cause was updating @nextcloud/dialogs to 7.5.0: the library's toasts now carry hashed CSS classes whose styling only its bundled stylesheet knows – up to 7.4.1, Nextcloud's server CSS had quietly styled the then-global Toastify class names, so the app's missing stylesheet import never showed. Both script entry points now load the stylesheet themselves; a static test and a sharpened e2e test guard this (the previous one only checked that the message text appears, not that it is styled).

Changed: - "Cost center" is now "reporting group". The report, the Manage reporting groups button, the field in the account dialog, all messages, the in-app help and the manual now use this term; in German Auswertungsgruppe. The trigger was a question from an accountant (issue #7): in cost accounting, a cost center is a second dimension on each posting line – an amount is allocated across cost centers independently of the account it is posted to. This app does something else: it groups accounts, and an account belongs to at most one group. The old name therefore promised a capability that does not exist – and strictly speaking there is no such thing as a result per cost center anyway, because a cost center carries costs, not income. Nothing about the functionality changes: the same three groupings, the same assignments, the same figures. Groups you created, their codes and names are kept unchanged; no conversion is needed. To split one amount across two groups, you still create two accounts for it (ideally as sub-accounts of a shared parent) and split the posting across them with Split…; manual chapter 5.4 now says so explicitly. Internally everything stays as it was – table vbh_costcenters, column cost_center_id, setting cost_center_mode and the /api/costcenters route are unchanged, and there is no migration. Older entries in the audit log keep their original wording.

Fixed: - A deleted collecting account blocked the entire settings page. If a collecting account had been selected under "Contributions & SEPA" and the data was then wiped via "Delete all data" (or an import with reset), the setting pointed at an account that no longer existed. From then on every save on the settings page failed with "The selected collecting account was not found." – including the club name or the receipt storage, because the page always sends the full set of fields. Resetting the data and deleting a single account now clear that setting as well, and it is only validated when it actually changes, so an account that became invalid later (after removing its IBAN, say) no longer paralyses the other sections.

• A deleted Nextcloud user blocked the entire settings page. If a Nextcloud user was configured under "Receipts" (receipt storage) or "Bank data" (watched folder) and that user was later deleted in Nextcloud, every save on the settings page failed with "The specified Nextcloud user for the … does not exist." – including the club name, because the page always sends the full set of fields. Deleting a Nextcloud user now clears both settings as well: the receipt storage falls back to the app-internal storage and the watched folder is switched off. The user is also only validated when it actually changes – for the deletions the app never learns about (a foreign user backend, a restored database dump, a deletion while the app was disabled).

• No Nextcloud user could be selected in the settings any more. This affected "Receipts" (receipt storage) and "Bank data" (watched folder): both dropdowns only offered "— internal (AppData) —" resp. "— off —", the list of Nextcloud users stayed empty. When the settings moved into the Nextcloud settings (0.25.0), the page lost its binding to the user list – the list was still being loaded, but no longer passed on to those two sections. As a result, receipts could no longer be stored in a user's folder and the watched folder could not be set up.

• Illegible labels and wrongly coloured buttons. The app used Nextcloud's light status background tones as text and accent colours: "Expense" in the posting dialog was white on pale pink, the remainder shown while splitting was barely readable, edge markers and warning stripes faded to pastels. The dark theme was also tied to the operating system setting instead of the choice in the Nextcloud profile – picking "Dark theme" there while the system was light produced light colours on a dark background. And several of the app's buttons (the income/expense toggle, the checklist links, "Skip", the suggestion chips) were painted blue by Nextcloud's generic button rule. An automated contrast sweep across twelve views in light and dark theme found nine WCAG AA violations before and none after; Nextcloud's high-contrast themes are now picked up correctly as well. Two superfluous separator lines in the header area are gone, too.

Fixed: - The interface stayed German even with Nextcloud set to English. Until now the app loaded its translation bundle straight from the app directory as a file (l10n/<language>.json). Nextcloud's shipped .htaccess only serves files with certain extensions from there – .json is not among them, so the request ends up in index.php and comes back as a 404. The attempt therefore failed silently in every normal installation and the app kept showing its German source strings (typical nginx configurations behave the same way). Translations now come from a dedicated endpoint (/api/l10n/<language>), which is not affected by that restriction. Server-side text – manual, audit guide, error messages – was never affected.

• The confirmation for posting a SEPA collection showed a red "Delete" button. Two dialogs were affected – "Mark collection as executed" and "Undo return" – both left the button label to the dialog's default, which is meant for deleting actions. They now read "Post" and "Undo" and are no longer red. The default label is translatable as well; until now it read "Löschen" even in the English interface.

• The buttons in the SEPA collection list were cut off. The action column is fixed at 160 pixels – a width meant for three icon buttons. The four text buttons ("Show rows", "Download XML", "Mark as collected", "Discard") wrapped onto separate lines there, the widest one stuck out of the column, and that made the table wider than its frame: the buttons sat half outside on the right, and the "Created" column was clipped on the left. From 900 pixels of window width they now sit side by side; below that they still stack, but inside the column. The same applied to "Undo return" in the expanded collection list.

• "The accounting was changed by another person" – after your own entry. The app compares its state with the server every 20 seconds, but a change detected that way only counted as your own for 15 seconds. Since the comparison runs less often than that window – and is deferred further while an import is running – the app regularly reported your own larger actions as someone else's change. The measure is no longer a fixed window but the moment your state last provably matched the server: anything you wrote after that explains the difference. Genuine changes by other people are still reported.

• Sphere, reserve and cost center names stayed German. They came from fixed strings in ReportService and never went through translation, so the English interface read "Ideeller Bereich" instead of "Non-profit purpose". This affected the sphere overview, the reserves overview and the built-in cost center names.

• 22 missing English translations added. Among them the default-fee hint in the member import, the labels on the SEPA collection cards ("Total", "Due", "created"), the "What's new" dialog and the first-run hints in the help – all of which showed up in German in the English interface. A sweep of all 850 strings in the code against l10n/en.json now comes back without a gap.

New: - Member lists with English column headings. The CSV import now recognises English column names alongside the German ones (Name, Email, IBAN, BIC, Mandate, Amount, Frequency, Start date plus common variants) as well as English frequency values (monthly, quarterly, semiannual, yearly, annually). The English manual already described these column names – now they actually work. Existing German lists keep working unchanged.

Fixed: - "What's new" popup from Nextcloud showed "[object Object]" instead of text. The 0.27.1 entry still had a ### Fixed sub-heading in its changelog entry; Nextcloud's popup renderer (marked v18) can no longer process Markdown headings correctly (see note above) and shows "[object Object]" in its place, while the rest of the text renders fine. From this version on, changelog entries avoid ### headings.

Fixed

• Broken "what's new" popup from Nextcloud itself. After updating to 0.27.0, Nextcloud's own app-update popup (independent of this app's in-app dialog) showed "What's new in {app} 0.27.0" followed by "[object Object]" instead of actual text. Cause: since 0.27.0, info.xml carried the app name in two <name> elements (German/English) for a localized App Store title – but Nextcloud's update notification reads the name at that point without a language code and can't handle multiple <name> elements (a Nextcloud core bug). <name> is single-language again; <summary>/<description> remain bilingual.

New

• README, manual and audit guide are now also available in English. README.md, CHANGELOG.md (from this version onward) and HANDBUCH.md are now also available as *.en.md, with a language switcher at the top of each file. info.xml now carries <name>/<summary>/<description> in both languages, so the App Store automatically shows the right one. The manual served in-app (/api/help/handbuch) and the printable audit guide for auditors (/api/help/pruefleitfaden) now detect the user's Nextcloud language setting and serve English instead of German once it's set to English. The chapter deep links from the in-app help (HelpModal) now point to language-independent anchors (section-<chapter>) instead of slugs derived from the (then translated) heading text.

Neu

• „Was ist neu"-Hinweis nach Updates. Nach einem Update zeigt die App jeder Person einmalig einen kurzen, auf ihre Rolle zugeschnittenen Hinweis, was sich geändert hat – statt dass Neuerungen nur zufällig auffallen oder gar nicht bemerkt werden. Der zuletzt gesehene Stand wird pro Nextcloud-Konto serverseitig gemerkt (nicht nur im Browser), damit er auf allen Geräten derselben Person konsistent erscheint. Über Hilfe → „Was ist neu in Version …" lässt er sich jederzeit erneut aufrufen. Nicht jede Version bekommt einen Eintrag – reine Fehlerbehebungen bleiben unerwähnt.

Geändert

• Beiträge → Mitglieder: Bearbeiten-Button zeigt jetzt das Stift-Symbol statt des Texts „Bearbeiten“ – konsistent mit den übrigen Bearbeiten-Buttons in Tabellenzeilen (Buchungen → Regeln, Journal).

Behoben

• Modal-Überschriften schwebten am Browserfensterrand statt im Popup: NcModals :name-Titel hängt CSS-seitig als Geschwister von .modal-container, nicht darin – bei zentrierten Dialogen (Einstellungen, Neue Buchung, neues Konto, Kostenstellen verwalten, Sphären zuordnen, Mitglied aufnehmen, Importe, Hilfe, Bankverbindung wechseln, Plan-Stand, Willkommens-Assistent) klaffte dadurch eine Lücke zwischen Titel und Box. Betroffene Dialoge rendern die Überschrift jetzt selbst im Inhalt; auf dem Handy (size="full") bleibt der eingebaute Titel-Balken, der dort korrekt über der Box sitzt.

Geändert

• Berichte → Kostenstellen/Sphären: Bericht bekommt die volle Höhe, Pflege wandert ins Modal: Seit 0.22.3 hing die Pflege (Kostenstellen anlegen/ zuordnen, Sphären zuweisen) als zweiter, oft sehr hoher Block unter der Split-Ansicht (Baum + Detail) im selben Scrollcontainer – der eigentliche Bericht war dadurch auf min-height: 360px gedeckelt, während die Pflege den Großteil der Seite einnahm. Die Pflege öffnet jetzt als NcModal über die Buttons „Kostenstellen verwalten" bzw. „Sphären zuordnen" oben rechts im Bericht (gleiches Muster wie „＋ Mitglied"/„Liste einlesen" im Reiter Beiträge) sowie zusätzlich über „Konten zuordnen" direkt bei der Baumzeile „– nicht zugeordnet". Der Kostenstellen-Modus (Gruppierung) bleibt sichtbar, da er den Bericht selbst steuert – er ist jetzt ein Auswahlfeld in der Kopfzeile statt einer Karte im Pflege-Modal. Damit entfallen auch die CSS-Sonderfälle aus 0.23.0/0.23.1 (.vbh-sectionbody.is-split hatte nur wegen des zweiten Blocks flex-direction: column und ein eigenes .vbh-section-divider-Padding gebraucht).

Behoben

• Berichte → Kostenstellen/Sphären: kein Rand, weder oben in der Split-Ansicht noch im Pflegepanel darunter: Nachbesserung zum 0.23.0-Fix, der die Split-Ansicht (.vbh-splitinner) wieder auf volle Breite brachte. Zwei getrennte Stellen hatten trotzdem noch keinen Rand, weil beide bislang nur implizit vom umgebenden .vbh-sectionbody profitierten, das für Kostenstellen/Sphären aber bewusst auf padding: 0 gesetzt ist (die Split-Ansicht managt Innenabstände sonst selbst) – bei der vorherigen ~1px-Quetschung war das nie sichtbar:
• .vbh-splitinner selbst (Baum + Detail: kein oberer/linker Rand) – jetzt eigenes padding-top/padding-left.
• das darunterliegende Pflegepanel (CostCenterPanel/SphereAssignPanel, umschlossen von .vbh-section-divider, das sonst nur als <h3>-Trenn- linie in schon gepolsterten Containern vorkommt) – jetzt eigenes horizontales Padding auf .vbh-sectionbody.is-split > .vbh-section-divider.

Fixed: - Duplicate accounts in the autocomplete: Frequently used accounts were also listed in their category group and showed up twice in a row when searching. Now listed once. - Search field in the "Pick receipt from folder" popup sometimes didn't react: A fast click could leave focus stuck on the modal backdrop, so clicks and typing went nowhere. Fixed – the same fix now applies to the account, bank account, and member dialogs. - Icon in the "Pick from folder" button was misaligned: The button was too narrow for icon and text together. - The getting-started card briefly flashed on load: It appeared for a moment even when everything was already set up. - Period selector stayed empty after a load error: A single failed request left it empty with no error and no retry. Now retries up to three times, then shows an error.

New: - Watch folder for receipts. Besides the internal storage and the user folder managed by the app there is a third storage type (cog → Receipts → "Storage type"): a folder in the Files app whose files, including all subfolders, can be picked when booking ("Pick from folder", with search and preview). The files stay where they are – renaming or reorganising them inside the watch folder does not break the link, the app remembers the Nextcloud file id. Receipts uploaded or photographed from the app are stored under <folder>/<year>/ and may be reorganised afterwards. The folder has to exist in the Files app beforehand and must not overlap with the watched folder for bank statements. It is chosen by clicking in the folder tree of the user's home ("Choose folder…" next to the path field) – a typo in the path is ruled out. The same tree is now available for the watched folder for bank statements. - The overview reports documents without an entry. If the watch folder holds a file that is not attached to any entry yet, the overview shows "x documents not yet assigned to an entry" – an invoice still to be paid, for instance. "View" opens the inbox with "Create entry" per file. A second tile warns about receipts whose file was deleted or moved out of the watch folder; the audit ZIP keeps listing such receipts in fehlende_dateien.txt. - The app never deletes a file in the watch folder. "Delete receipt" means "Unlink" there – the files also stay when an entry is deleted or all data is wiped. The same file may be attached to several entries, e.g. a split invoice. - When switching on, receipts the app stored under <folder>/<entry id>/ so far get their file id filled in – the existing receipt folder can become the watch folder directly. If a different folder is chosen, the old receipts count as missing until they are moved there.

Changed: - The Nextcloud viewer only opens a receipt when the file lives in the home of the signed-in user; everyone else gets the app's own view. Until now the viewer failed for anyone who did not own the storage folder. - Opening a receipt no longer creates folders, and receipts from the internal storage stay readable after switching the storage type.

New: - The fiscal year no longer has to match the calendar year. Under the gear icon → Fiscal year you can now choose when it starts: presets cover the calendar year, October–September, the school year August–July and half-year periods (semesters), plus a custom rule with any start day and a period length of 1 to 12 months (divisors of 12). Clubs with a deviating fiscal year previously had to add up their figures outside the app (issue #8). - The header's “Year" has become a “Period". Every period carries a freely editable name – suggested as “2026" for a calendar year, “2025/26" for a deviating one and “2025/26-1" for a winter semester. Entry numbers, reports, the budget, the receipt ZIP and the year-end lock all refer to the period rather than to a year number. - Periods can be maintained individually. The boundary between two open periods can be moved – the way to a short transitional fiscal year. An empty period at either end of the chain can be removed, and the next one created at the press of a button. - Switching shows what it will do first. Before a changed rule takes effect, a preview lists the resulting periods, how many bookings will change period, and which budget figures would be lost – because when two periods merge, an account can only keep one of the two figures. Locked periods block the switch: what the general meeting approved does not move afterwards. - The cash report names the actual key dates. The asset overview used fixed column headers “Balance Jan 1" and “Balance Dec 31"; it now shows the first and last day of the selected fiscal year. - The monthly chart on the dashboard follows the fiscal year. It always ran from January to December; with October–September it now starts in October, and a semester shows six months.

Changed: - The settings section Year-end closing is now called Fiscal year and holds the rule and the list of periods alongside the locking. - The xbuc import now derives a file's fiscal year from its date range instead of the calendar year. A file for a deviating fiscal year could not be assigned at all before. Bookings outside the range are dated to the first or last day of the period rather than to January 1 / December 31. - Existing installations are unaffected: the migration creates one period per previous calendar year, running Jan 1 to Dec 31 and named after the year. Entry numbers and existing locks are left untouched. If you change nothing, you notice nothing.

Fixed: - Opening the booking dialog before the account list had loaded left the cash account empty – and booking then only reported that it was a required field. The preselection is now filled in as soon as the accounts arrive. - Switching the period right after loading occasionally showed the journal and evaluation of the previous period: of several simultaneous requests the last to arrive won, not the last one made. A choice made before the periods had loaded did not stick either.

New: - Entries can be edited straight from the account statement. When you spot a mistake while going through an account in the Accounts tab, you can fix it on the spot: the pencil at the end of the row opens the same entry dialog as the Entries tab – for the description, both accounts, and turning the entry into a split entry. Until now you had to note the entry number, switch views and search for it there (issue #39). - Receipts are visible in the account statement. If an entry has a receipt attached, the row shows the paperclip and a click opens it. That includes the auditor role, which cannot change anything otherwise. - A tidier row: Reassign and Delete now live in the three-dot menu, exactly as in the Entries tab. Otherwise the row would have wrapped onto a second line in narrow windows.

Fixed: - The account statement refreshes after an entry is edited. Description, contra account and running balance used to sit there outdated until the next account switch whenever the entry had been changed elsewhere.

Fixed: - In Firefox the year in date fields is fully visible again. Since version 109 Firefox draws a calendar button inside the input, but does not account for it in the width Nextcloud gives to every input field – it therefore covered the last digits of the year, turning "07/09/2026" into a visible "07/09/202" (issue #43). Every date field in the app is now wide enough: entry date, next and first due date, mandate date, opening balance, open items, SEPA due date and the short report's period. - On phones the buttons inside dialogs are thumb-sized again. The 44px minimum for touch targets only applied outside dialogs – Nextcloud attaches dialog content to a different place in the page, so the rule never reached it. In the entry dialog Cancel and Book were only 34px tall and the Income/Expense toggles 40px; this now applies in every dialog. The round help button next to the spheres is properly round again – it was stretched into an oval on phones and on the desktop alike – and grows to full touch-target size under a finger. - The receipt ZIP export contains all receipts again. With the receipt storage set to app-internal, the archive came out empty and listed every receipt in fehlende_dateien.txt as not found – even though each one opened and downloaded perfectly on its own (issue #40). The files were never gone: while building the archive the app read them in a way that only exists for storage inside the Nextcloud file tree, not for the app-internal one. Only the ZIP export was affected, and only with app-internal storage. On top of that, fehlende_dateien.txt now states the reason for each entry instead of reporting every failure as "not found".

Fixed: - The report sub-tabs are fully reachable again on narrow screens. The bar holding Summary, Reporting groups, Spheres, Reserves, Budget and Log ran off the screen and could not be swiped – it ended after Spheres, and the More exports button was out of reach as well (issue #38). The bar can now be swiped sideways and indicates at its edges that there is more to come; jumping straight to one of the later tabs from the help or the bottom bar scrolls it into view automatically. The same applies to the sub-tabs under Entries and Contributions and – with the Nextcloud sidebar open or with longer labels – on the desktop too. - Amount fields now show the amount the way it appears next to them: "20.000,00 €" instead of "20000". In the budget, the Plan column was a bare number sitting next to the formatted Actual and Difference columns – with four- and five-digit figures it was hard to tell 5,000 from 50,000 (issue #34). The same applies to every other amount field: entry amount and split lines, opening balance, open items, membership fees and the default fee. While editing, the field still shows the bare value so that typing does not fight a live format; both notations are accepted – "20000", "20.000,00" or "20000.5". Anything unreadable restores the previous value instead of silently setting it to 0. - The treasurer's report and the short report moved into the More exports menu on phones. As separate buttons they no longer fitted into the row and pushed the menu off screen. The short report's date field is now part of that menu; nothing changes on the desktop.

New: - The header now shows the funds across all cash accounts, no longer just the first one. Until now the top right only ever showed the first cash account by account number – anyone running a cash box (1000) and a bank account (1200) therefore saw the cash box of all things, while the bank account stayed invisible (issue #31). The figure is now called Funds and adds up every cash account; the tooltip breaks it down by account and names the transactions not yet assigned. If the club runs only one cash account, its name still appears there – nothing changes for those clubs. - Individual cash accounts can be left out of that figure. For cash accounts the account dialog offers a new Counts towards the funds shown in the header flag (default: on). A fixed-term deposit account can thus stay out of the day-to-day figure without disappearing from the books: the cash report, the assets overview and the trial balance keep counting every cash account. The flag is display only and is therefore not locked by the finalization of a fiscal year either. - The cash-account table on the dashboard and in the evaluation has a total row – as soon as the club runs more than one cash account; with a single one it would merely repeat the row above it. If at least one account is excluded from the funds figure, an of which funds (header) row appears below it, and the accounts concerned are marked as such in the list – so it stays clear how the figure at the top comes about.

Changed: - Clicking an account that has sub-accounts now expands them. Previously this only worked through the small arrow in front of it, which was easy to miss. Collapsing still goes through the arrow – a second click on the row deliberately does not collapse it again, otherwise you could not select a parent account without closing it. - The posting text now grows with its content. Longer text wraps and is shown in full instead of running off the side of the field – when creating a posting as well as when editing one. The value itself stays single-line, so nothing changes for the journal, exports or the API. - Dialogs have a little more room to the edge. Content and buttons used to sit rather close to it.

Fixed: - The charts ignored dark mode. Axis labels and grid lines stayed black and were barely visible on a dark background – both on the overview and in the reports. The cause was a check for a theme--dark class that Nextcloud never sets, so the condition was always false. The charts now read their colours straight from Nextcloud's design variables and therefore follow any theme – light, dark, high contrast, and club colours set through the theming app. Changing the theme while the app is open redraws them. - Success and error messages (toasts) appeared at the bottom left. Nextcloud still shows its own messages at the top right, so one screen ended up with two kinds of toast in two different corners. @nextcloud/dialogs 7.5.0 moved them to the bottom left and dropped the position option; the app now puts them back where they belong. - The active button had a white border. Visible on the Income/Expense switch in the posting dialog, on active filter chips, on the underline of the active sub-tab and on the side selector when reassigning. Nextcloud claims button.active for its own pressed state and overrode the app's border colour. - The focus ring was clipped in the posting dialog. Tabbing through the dialog showed only a sliver of the ring around Income and Expense – the switch cut it off. - The posting dialog could be scrolled sideways. The hidden receipt file input claimed its full intrinsic width and pushed the dialog past its edge, producing a scrollbar. - Accounts with sub-accounts broke out of the account tree. They were bold and noticeably taller than their siblings, and their columns sat a few pixels further right. The cause was the expand arrow: on parent accounts it is a button, and Nextcloud gives every button a minimum height of 34px plus a margin – which grew the row to 46px while leaf rows stayed at 29px. All rows are now the same height and weight; the arrow alone marks an account as having children. The faint placeholder dot in front of accounts without sub-accounts is gone as well – it looked like a bullet point; the placeholder still keeps the column aligned. - Text hugged the edge in the "What's new" dialog. It now uses the same inner spacing as every other dialog.

New: - Receipts can now be attached while creating a posting on the desktop, too. On the desktop the New posting dialog shows the same Receipts section as the edit dialog: the selected files sit in a list (with a remove button) and are uploaded as soon as the posting is saved. Until now this only existed in the mobile view (windows up to 640 px) – on the desktop you had to save the posting first and then open it again (issue #29). File type and size are checked as soon as you pick a file: anything the server will not take (only PDF, JPG, PNG, GIF, WebP; 20 MB at most) is reported by name right away instead of after the posting has been saved. If an upload fails anyway – a dropped connection, say – the files concerned stay in the dialog and can be sent to the meanwhile created posting via Upload again, while the other receipts are already attached. While saving and uploading, the button is disabled so that a second click cannot turn into a second posting.

Fixed: - The Attach button could only be reached with the mouse. The file field behind it was hidden via hidden and therefore dropped out of the tab order – anyone operating the app from the keyboard could not get to the receipts at all. The field is now focusable and shows the focus on the button, on mobile as well as on the desktop.

Fixed: - Success and error messages (toasts) rendered as bare text in the top-left corner. Since 0.29.0, confirmations such as "Settings saved." sat unstyled across the header instead of appearing as a box at the bottom left. The cause was updating @nextcloud/dialogs to 7.5.0: the library's toasts now carry hashed CSS classes whose styling only its bundled stylesheet knows – up to 7.4.1, Nextcloud's server CSS had quietly styled the then-global Toastify class names, so the app's missing stylesheet import never showed. Both script entry points now load the stylesheet themselves; a static test and a sharpened e2e test guard this (the previous one only checked that the message text appears, not that it is styled).

Changed: - "Cost center" is now "reporting group". The report, the Manage reporting groups button, the field in the account dialog, all messages, the in-app help and the manual now use this term; in German Auswertungsgruppe. The trigger was a question from an accountant (issue #7): in cost accounting, a cost center is a second dimension on each posting line – an amount is allocated across cost centers independently of the account it is posted to. This app does something else: it groups accounts, and an account belongs to at most one group. The old name therefore promised a capability that does not exist – and strictly speaking there is no such thing as a result per cost center anyway, because a cost center carries costs, not income. Nothing about the functionality changes: the same three groupings, the same assignments, the same figures. Groups you created, their codes and names are kept unchanged; no conversion is needed. To split one amount across two groups, you still create two accounts for it (ideally as sub-accounts of a shared parent) and split the posting across them with Split…; manual chapter 5.4 now says so explicitly. Internally everything stays as it was – table vbh_costcenters, column cost_center_id, setting cost_center_mode and the /api/costcenters route are unchanged, and there is no migration. Older entries in the audit log keep their original wording.

Fixed: - A deleted collecting account blocked the entire settings page. If a collecting account had been selected under "Contributions & SEPA" and the data was then wiped via "Delete all data" (or an import with reset), the setting pointed at an account that no longer existed. From then on every save on the settings page failed with "The selected collecting account was not found." – including the club name or the receipt storage, because the page always sends the full set of fields. Resetting the data and deleting a single account now clear that setting as well, and it is only validated when it actually changes, so an account that became invalid later (after removing its IBAN, say) no longer paralyses the other sections.

• A deleted Nextcloud user blocked the entire settings page. If a Nextcloud user was configured under "Receipts" (receipt storage) or "Bank data" (watched folder) and that user was later deleted in Nextcloud, every save on the settings page failed with "The specified Nextcloud user for the … does not exist." – including the club name, because the page always sends the full set of fields. Deleting a Nextcloud user now clears both settings as well: the receipt storage falls back to the app-internal storage and the watched folder is switched off. The user is also only validated when it actually changes – for the deletions the app never learns about (a foreign user backend, a restored database dump, a deletion while the app was disabled).

• No Nextcloud user could be selected in the settings any more. This affected "Receipts" (receipt storage) and "Bank data" (watched folder): both dropdowns only offered "— internal (AppData) —" resp. "— off —", the list of Nextcloud users stayed empty. When the settings moved into the Nextcloud settings (0.25.0), the page lost its binding to the user list – the list was still being loaded, but no longer passed on to those two sections. As a result, receipts could no longer be stored in a user's folder and the watched folder could not be set up.

• Illegible labels and wrongly coloured buttons. The app used Nextcloud's light status background tones as text and accent colours: "Expense" in the posting dialog was white on pale pink, the remainder shown while splitting was barely readable, edge markers and warning stripes faded to pastels. The dark theme was also tied to the operating system setting instead of the choice in the Nextcloud profile – picking "Dark theme" there while the system was light produced light colours on a dark background. And several of the app's buttons (the income/expense toggle, the checklist links, "Skip", the suggestion chips) were painted blue by Nextcloud's generic button rule. An automated contrast sweep across twelve views in light and dark theme found nine WCAG AA violations before and none after; Nextcloud's high-contrast themes are now picked up correctly as well. Two superfluous separator lines in the header area are gone, too.

Fixed: - The interface stayed German even with Nextcloud set to English. Until now the app loaded its translation bundle straight from the app directory as a file (l10n/<language>.json). Nextcloud's shipped .htaccess only serves files with certain extensions from there – .json is not among them, so the request ends up in index.php and comes back as a 404. The attempt therefore failed silently in every normal installation and the app kept showing its German source strings (typical nginx configurations behave the same way). Translations now come from a dedicated endpoint (/api/l10n/<language>), which is not affected by that restriction. Server-side text – manual, audit guide, error messages – was never affected.

• The confirmation for posting a SEPA collection showed a red "Delete" button. Two dialogs were affected – "Mark collection as executed" and "Undo return" – both left the button label to the dialog's default, which is meant for deleting actions. They now read "Post" and "Undo" and are no longer red. The default label is translatable as well; until now it read "Löschen" even in the English interface.

• The buttons in the SEPA collection list were cut off. The action column is fixed at 160 pixels – a width meant for three icon buttons. The four text buttons ("Show rows", "Download XML", "Mark as collected", "Discard") wrapped onto separate lines there, the widest one stuck out of the column, and that made the table wider than its frame: the buttons sat half outside on the right, and the "Created" column was clipped on the left. From 900 pixels of window width they now sit side by side; below that they still stack, but inside the column. The same applied to "Undo return" in the expanded collection list.

• "The accounting was changed by another person" – after your own entry. The app compares its state with the server every 20 seconds, but a change detected that way only counted as your own for 15 seconds. Since the comparison runs less often than that window – and is deferred further while an import is running – the app regularly reported your own larger actions as someone else's change. The measure is no longer a fixed window but the moment your state last provably matched the server: anything you wrote after that explains the difference. Genuine changes by other people are still reported.

• Sphere, reserve and cost center names stayed German. They came from fixed strings in ReportService and never went through translation, so the English interface read "Ideeller Bereich" instead of "Non-profit purpose". This affected the sphere overview, the reserves overview and the built-in cost center names.

• 22 missing English translations added. Among them the default-fee hint in the member import, the labels on the SEPA collection cards ("Total", "Due", "created"), the "What's new" dialog and the first-run hints in the help – all of which showed up in German in the English interface. A sweep of all 850 strings in the code against l10n/en.json now comes back without a gap.

New: - Member lists with English column headings. The CSV import now recognises English column names alongside the German ones (Name, Email, IBAN, BIC, Mandate, Amount, Frequency, Start date plus common variants) as well as English frequency values (monthly, quarterly, semiannual, yearly, annually). The English manual already described these column names – now they actually work. Existing German lists keep working unchanged.

Fixed: - "What's new" popup from Nextcloud showed "[object Object]" instead of text. The 0.27.1 entry still had a ### Fixed sub-heading in its changelog entry; Nextcloud's popup renderer (marked v18) can no longer process Markdown headings correctly (see note above) and shows "[object Object]" in its place, while the rest of the text renders fine. From this version on, changelog entries avoid ### headings.

Fixed

• Broken "what's new" popup from Nextcloud itself. After updating to 0.27.0, Nextcloud's own app-update popup (independent of this app's in-app dialog) showed "What's new in {app} 0.27.0" followed by "[object Object]" instead of actual text. Cause: since 0.27.0, info.xml carried the app name in two <name> elements (German/English) for a localized App Store title – but Nextcloud's update notification reads the name at that point without a language code and can't handle multiple <name> elements (a Nextcloud core bug). <name> is single-language again; <summary>/<description> remain bilingual.

New

• README, manual and audit guide are now also available in English. README.md, CHANGELOG.md (from this version onward) and HANDBUCH.md are now also available as *.en.md, with a language switcher at the top of each file. info.xml now carries <name>/<summary>/<description> in both languages, so the App Store automatically shows the right one. The manual served in-app (/api/help/handbuch) and the printable audit guide for auditors (/api/help/pruefleitfaden) now detect the user's Nextcloud language setting and serve English instead of German once it's set to English. The chapter deep links from the in-app help (HelpModal) now point to language-independent anchors (section-<chapter>) instead of slugs derived from the (then translated) heading text.

Neu

• „Was ist neu"-Hinweis nach Updates. Nach einem Update zeigt die App jeder Person einmalig einen kurzen, auf ihre Rolle zugeschnittenen Hinweis, was sich geändert hat – statt dass Neuerungen nur zufällig auffallen oder gar nicht bemerkt werden. Der zuletzt gesehene Stand wird pro Nextcloud-Konto serverseitig gemerkt (nicht nur im Browser), damit er auf allen Geräten derselben Person konsistent erscheint. Über Hilfe → „Was ist neu in Version …" lässt er sich jederzeit erneut aufrufen. Nicht jede Version bekommt einen Eintrag – reine Fehlerbehebungen bleiben unerwähnt.

Geändert

• Beiträge → Mitglieder: Bearbeiten-Button zeigt jetzt das Stift-Symbol statt des Texts „Bearbeiten“ – konsistent mit den übrigen Bearbeiten-Buttons in Tabellenzeilen (Buchungen → Regeln, Journal).

Behoben

• Modal-Überschriften schwebten am Browserfensterrand statt im Popup: NcModals :name-Titel hängt CSS-seitig als Geschwister von .modal-container, nicht darin – bei zentrierten Dialogen (Einstellungen, Neue Buchung, neues Konto, Kostenstellen verwalten, Sphären zuordnen, Mitglied aufnehmen, Importe, Hilfe, Bankverbindung wechseln, Plan-Stand, Willkommens-Assistent) klaffte dadurch eine Lücke zwischen Titel und Box. Betroffene Dialoge rendern die Überschrift jetzt selbst im Inhalt; auf dem Handy (size="full") bleibt der eingebaute Titel-Balken, der dort korrekt über der Box sitzt.

Geändert

• Berichte → Kostenstellen/Sphären: Bericht bekommt die volle Höhe, Pflege wandert ins Modal: Seit 0.22.3 hing die Pflege (Kostenstellen anlegen/ zuordnen, Sphären zuweisen) als zweiter, oft sehr hoher Block unter der Split-Ansicht (Baum + Detail) im selben Scrollcontainer – der eigentliche Bericht war dadurch auf min-height: 360px gedeckelt, während die Pflege den Großteil der Seite einnahm. Die Pflege öffnet jetzt als NcModal über die Buttons „Kostenstellen verwalten" bzw. „Sphären zuordnen" oben rechts im Bericht (gleiches Muster wie „＋ Mitglied"/„Liste einlesen" im Reiter Beiträge) sowie zusätzlich über „Konten zuordnen" direkt bei der Baumzeile „– nicht zugeordnet". Der Kostenstellen-Modus (Gruppierung) bleibt sichtbar, da er den Bericht selbst steuert – er ist jetzt ein Auswahlfeld in der Kopfzeile statt einer Karte im Pflege-Modal. Damit entfallen auch die CSS-Sonderfälle aus 0.23.0/0.23.1 (.vbh-sectionbody.is-split hatte nur wegen des zweiten Blocks flex-direction: column und ein eigenes .vbh-section-divider-Padding gebraucht).

Behoben

• Berichte → Kostenstellen/Sphären: kein Rand, weder oben in der Split-Ansicht noch im Pflegepanel darunter: Nachbesserung zum 0.23.0-Fix, der die Split-Ansicht (.vbh-splitinner) wieder auf volle Breite brachte. Zwei getrennte Stellen hatten trotzdem noch keinen Rand, weil beide bislang nur implizit vom umgebenden .vbh-sectionbody profitierten, das für Kostenstellen/Sphären aber bewusst auf padding: 0 gesetzt ist (die Split-Ansicht managt Innenabstände sonst selbst) – bei der vorherigen ~1px-Quetschung war das nie sichtbar:
• .vbh-splitinner selbst (Baum + Detail: kein oberer/linker Rand) – jetzt eigenes padding-top/padding-left.
• das darunterliegende Pflegepanel (CostCenterPanel/SphereAssignPanel, umschlossen von .vbh-section-divider, das sonst nur als <h3>-Trenn- linie in schon gepolsterten Containern vorkommt) – jetzt eigenes horizontales Padding auf .vbh-sectionbody.is-split > .vbh-section-divider.

Geändert

• App-Store-Beschreibung aktualisiert: Das seit 0.20.0 bestehende Beiträge-&-SEPA-Modul (Mitgliederverwaltung, Lastschriftmandate, Sammeleinzug, eigener Reiter) fehlte dort drei Releases lang komplett. Ergänzt, außerdem CAMT.053/MT940 und der Wachordner beim Kontoauszug-Import – bisher war dort nur CSV-CAMT genannt.

Behoben

• Konto-/Kategorie-Auswahl auf dem Handy war unbedienbar: Das Bottom-Sheet zur Kontoauswahl (AccountPickerSheet.vue) rendete zwar in den DOM, blieb aber unsichtbar und unklickbar hinter dem Buchungsdialog – Nextclouds eigenes Core-CSS (#content { position: fixed }) erzeugt einen Stacking-Context, in dem das Sheet trotz hohem z-index gefangen war, während NcModal (der Buchungsdialog) dem entkommt, weil @nextcloud/vue seine Modals an document.body teleportiert. Das Sheet tut das jetzt auch (<teleport to="body">). Gefunden im Gesamt-App-Review, siehe APP-REVIEW.md.

In appinfo/info.xml direkt von 0.21.0 auf 0.22.1 gesprungen und dann auf 0.22.2 weitergezählt, ohne dass 0.22.0/0.22.1 je getaggt oder veröffentlicht wurden – dieser Abschnitt fasst beide Zwischenstände zu einem einzigen, tatsächlich veröffentlichten Release zusammen.

Neu

• Standard-Beitrag (Zahnrad → Beiträge & SEPA): ein einmal hinterlegter Betrag/Frequenz füllt „Mitglied aufnehmen" vor und greift auch im CSV-Import, wenn eine Zeile ein Start-Datum, aber keinen eigenen Betrag hat – bei 80–100 Mitgliedern mit demselben Satz sonst 80–100 Mal derselbe Wert von Hand.

Geändert

• Navigation aufgeräumt. Das Zahnrad-Menü „Einstellungen & Import" hatte über die Entwicklungszeit 16 Abschnitte angesammelt – Einrichtung und laufende Arbeit ungetrennt nebeneinander. Neu:
• Reiter „Beiträge" (Hauptnavigation, erscheint automatisch sobald das Modul genutzt wird): Mitgliederliste und SEPA-Sammeleinzug, vorher zwei Abschnitte im Einstellungen-Modal. Kennzahl im Reiter zeigt Beiträge im Rückstand.
• Unterreiter „Regeln" (Tab Buchungen): Auto-Zuordnungsregeln, dort wo sie auch entstehen (Blitz-Button beim Zuordnen).
• Kostenstellen- und Sphären-Pflege jetzt direkt in den gleichnamigen Berichten statt im Zahnrad – inklusive des Kostenstellen-Modus.
• Das Zahnrad selbst fasst jetzt nur noch sieben statt 16 Abschnitte (Verein, Belege, Bankdaten, Beiträge & SEPA, Berechtigungen, Jahresabschluss, Daten). Der Wegweiser-Hinweis „Kontoumsätze importieren" darin entfällt ersatzlos – der Import steht seit 0.19 im Tab „Buchungen".
• Keine Datenbank-Migration nötig; bestehende Installationen mit Mandaten/Beiträgen sehen den neuen Reiter sofort.
• Import-Verlauf konsolidiert. Die Liste „Bisherige CSV-Importe" unter Einstellungen → Daten zeigte dieselben Angaben (Dateiname, neu, Dubletten) wie das Änderungsprotokoll ein zweites Mal – beide wurden bei jedem Import parallel beschrieben. Die Liste entfällt; im Protokoll (Berichte → Protokoll) blendet der neue Schnellfilter „nur Importe" alles andere aus. Die dafür genutzte Tabelle vbh_imports wird per Migration entfernt.
• Buchhalter darf Mitglieder, SEPA-Mandate und den Einzug jetzt vollständig verwalten (vorher Verwalter-only) – die naheliegende Rollenzuweisung für eine Kassiererin ohne Rechtevergabe-Befugnis war sonst vom ganzen Reiter „Beiträge" ausgesperrt.
• Mitgliederliste und Einzug zeigen auf dem Handy Karten statt einer siebenspaltigen Tabelle, die dort zeilenweise Buchstabe für Buchstabe umbrach.
• Aktionsspalte der Mitgliederliste verdichtet. Seltene Aktionen (Bankverbindung wechseln, Mandat widerrufen, Löschen) stecken jetzt in einem Menü, „Bearbeiten" bleibt sichtbar – auch am Desktop ragte die Spalte vorher über den sichtbaren Bereich hinaus.

Behoben

• E-Mail-Adressen mit Umlaut im lokalen Teil („m.müller@gmx.de") galten beim Anlegen eines Mandats und beim CSV-Import als ungültig – betraf reale, bei gmx.de/web.de/t-online.de zustellbare Adressen.
• Bestätigungsdialoge für „Mitglieder übernehmen" und „Rückstand nachholen" zeigten einen roten „Löschen"-Button statt einer zum Anlegen passenden Beschriftung.
• Der Reiter „Beiträge" blitzte beim Laden der App kurz auf, bevor er endgültig erschien.

Details und die zugrundeliegenden Personas/Testfälle siehe BEITRAEGE-REVIEW.md.

Geändert

• Berichte-Seite: Reiter und Buttons wirkten überladen. Im Auswertung-Tab brachen bis zu 7 Export-Buttons (Kassenbericht, Kurzbericht, Beleg-ZIP, Prüfleitfaden, Saldenliste, E/A-Übersicht, Mehrjahresübersicht) neben den 6 Reitern mehrzeilig um und nahmen viel Platz ein. Kassenbericht und Kurzbericht – laut Handbuch die beiden meistgenutzten Berichte – bleiben direkt anklickbar, die übrigen fünf stecken jetzt in einem Menü „Weitere Exporte".

Behoben

• Kassenbericht und Kurzbericht erschienen auf Englisch, obwohl die Nextcloud-Oberfläche auf Deutsch stand. Nextclouds L10NFactory hält eine Sprache nur dann für „verfügbar", wenn im l10n/-Ordner der App eine Datei dazu liegt – für Deutsch gab es bisher keine, weil es ja die Quellsprache des Codes ist und l10n/de.json daher als überflüssig galt. Ohne diese Datei überspringt findLanguage() die deutsche Spracheinstellung des Nutzers und landet beim harten Fallback Englisch. Betroffen waren nur die serverseitig gerenderten Berichte (IL10N::t() direkt im PHP); die Vue-Oberfläche hat ihr eigenes, clientseitiges Übersetzungssystem und war nicht betroffen. Eine leere l10n/de.json reicht als Fix: sie macht Deutsch für Nextcloud „bekannt", ohne dass echte Übersetzungen nötig wären.

Geändert

• Buchungsjournal: Zeilen brachen durch bis zu 4 Aktions-Icons zweizeilig um. „Regel anlegen" und „Löschen" stecken jetzt in einem Menü-Button; Beleg (falls vorhanden) und „Bearbeiten" bleiben direkt anklickbar. Damit passt jede Zeile wieder auf eine Zeile.

Behoben

• Vorgemerkte Umsätze im CSV-Import konnten zu Dubletten führen. Die CSV-CAMT-Kontoauszüge führen anders als CAMT.053 keinen eigenen Statuscode, sondern schreiben den Buchungsstand als Klartext in die Spalte „Info" – „Umsatz vorgemerkt" wurde bislang nicht ausgewertet. Ändert sich ein solcher Umsatz beim endgültigen Buchen (typischerweise das Datum), erkannte ihn ein späterer, sich überschneidender Import nicht mehr als bereits vorhanden. CamtCsvParser überspringt vorgemerkte Zeilen jetzt wie schon Camt053Parser es für „PDNG" tut.

Hinzugefügt

• Nicht zugeordnete Bankumsätze lassen sich jetzt löschen. Bisher gab es dafür keinen Weg – ein Umsatz, den die Dublettenerkennung bei einem sich überschneidenden Kontoauszugs-Import nicht als bereits vorhanden erkannt hat, ließ sich weder zuordnen (dann läge er doppelt im Journal) noch wieder loswerden. Der Papierkorb-Knopf in „Zuzuordnen" löscht einen einzelnen, noch nicht verbuchten Umsatz; bereits zugeordnete bleiben wie gehabt nur über den zugehörigen Buchungssatz löschbar.

Hinzugefügt

• Weitere Mehrsprachigkeit im Backend. Kassenbericht und Kurzbericht (beide als druckfertige HTML-Seite) sowie das Änderungsprotokoll (Berichte → Protokoll) erscheinen jetzt in der Sprache des Nextcloud-Profils statt fest auf Deutsch.
• Alle bisher noch deutschen Fehler- und Bestätigungsmeldungen der Controller sind übersetzt, ebenso die Prüfmeldungen beim Anlegen und Ändern von Buchungen (Soll-Haben-Kontrolle) und die Fehlermeldungen der CAMT-/MT940-/CSV-Kontoauszugs-Parser.

Technisch

• Statische Prüfmethoden (JournalService::validateLines(), JournalService::reassignPlan(), BookingService::validateParts()), die auch direkt aus PHPUnit-Tests ohne laufende Nextcloud-Instanz aufgerufen werden, liefern jetzt stabile Fehlercodes statt fertigem Text; die Übersetzung passiert in einer begleitenden Instanzmethode mit Zugriff auf IL10N. Die Parser (CamtCsvParser, Camt053Parser, Mt940Parser, XbucParser) erhalten IL10N als optionalen, in Tests weglassbaren Konstruktorparameter mit deutschem Fallback-Text.

Bekannte Lücken

• Der CSV-Export der Auswertungen ist noch vollständig Deutsch.

Der erste sichtbare Schritt zur Mehrsprachigkeit: wer Nextcloud auf Englisch eingestellt hat, sieht jetzt eine englische Oberfläche statt einer deutschen mit englischen Brocken drumherum.

Hinzugefügt

• Englische Übersetzung. Alle Vue-Komponenten der Oberfläche – jeder Tab, jeder Dialog, jede Fehler- und Bestätigungsmeldung – sowie die häufigsten Fehlermeldungen des Backends sind jetzt ins Englische übersetzt (l10n/en.json). Einen eigenen Sprachschalter braucht die App dafür nicht: wer sein Nextcloud-Profil auf Englisch stellt, bekommt automatisch die englische Fassung. Die Quelltexte im Code bleiben bewusst Deutsch – der Herkunftssprache der App –, Deutsch ist also unverändert die Fallback-Sprache.
• Video in der App-Store-Beschreibung verlinkt.

Technisch

• Eigener Lademechanismus für Übersetzungen im Frontend (src/lib/l10n.js): die Bibliothek @nextcloud/l10n geht davon aus, dass Englisch die Quellsprache ist, und lädt dafür gar kein Übersetzungsbundle – bei einer deutschen Quellsprache wäre das genau die falsche Sprache.
• IL10N ist jetzt per Konstruktor in die Controller und Services injiziert, die nutzerseitige Fehlermeldungen werfen.

Bekannte Lücken

• Kassenbericht, Kurzbericht, Prüfleitfaden und die CSV-Exporte sind noch vollständig Deutsch.
• Ein paar Backend-Prüfungen (u. a. die Soll-Haben-Kontrolle beim Buchen, die CAMT-/MT940-Parser) bleiben vorerst Deutsch – sie sind bewusst ohne Nextcloud-Abhängigkeit gehalten, damit sie sich ohne laufende Instanz testen lassen.
• Das Änderungsprotokoll (Berichte → Protokoll) zeigt seine Einträge weiterhin auf Deutsch.

Diese Version bringt kaum sichtbare Neuerungen: sie räumt den Programmcode auf und sichert ihn gegen Fehler ab, die bisher niemand bemerkt hätte. Ein solcher Fehler kam dabei ans Licht – und er betraf ausgerechnet die Kassenprüfung.

Behoben

• Der Beleg-Export als ZIP brach ab, sobald ein Beleg im Zeitraum lag. Die Funktion rief eine Methode auf, die es in PHP gar nicht gibt (ZipArchive::addStream); der Download endete mit einem Serverfehler statt mit einem Archiv. Betroffen war genau die Funktion, die eine Kassenprüfung braucht, um alle Belege eines Jahres auf einmal zu bekommen. Die Belege werden jetzt blockweise ins Archiv geschrieben – der Speicherbedarf bleibt wie vorgesehen niedrig, auch bei einem Jahr voller PDFs.
• Der Kassenbericht ignorierte die dunkle Darstellung. Wer ihn bei dunklem Systemdesign öffnete, bekam schwarze Schrift auf weißem Grund in einem sonst dunklen Fenster – der Kurzbericht konnte es längst. Beide Berichte teilen sich jetzt dieselbe Gestaltung. Am Ausdruck ändert sich nichts.
• Beispieldaten konnten halb angelegt liegenbleiben. Fehlte ein Konto des Standard-Kontenrahmens, brach das Anlegen mitten in den Buchungen ab. Jetzt meldet die App vorher, welches Konto fehlt.

Geändert

• Die Rechenregeln aller Auswertungen liegen jetzt an einer Stelle. Die Frage, welches Konto mit welchem Vorzeichen ins Ergebnis eingeht, war an acht Stellen einzeln ausgeschrieben – in den Exporten, in der Saldenliste und in den Berichten. Eine Änderung daran musste bisher überall nachgezogen werden. An den Zahlen ändert sich nichts; sie sind jetzt nur an einer Stelle festgelegt und erstmals automatisiert geprüft.
• Der Sortier-Vergleich der Tabellen war dreifach vorhanden und ist es nun einmal. Sortierung und Sicherheitsabfragen sind damit in allen Ansichten garantiert gleich.

Technisch

• Statische Analyse (PHPStan, Stufe 5) läuft jetzt bei jeder Änderung mit und fand die drei oben genannten Fehler.
• Der 1149 Zeilen lange ExportController ist in Dienste aufgeteilt: CSV, Beleg-Archiv und die druckfertigen Berichte je für sich, der Controller behält nur die Auslieferung (158 Zeilen).
• Frontend-Unit-Tests (Vitest) für die Rechen- und Anzeigehelfer; der Testbestand wächst von 118 auf 210 Tests.

Behoben

• Gelöschte Buchung gab ihren Bankumsatz nicht wieder frei. Wurde ein Buchungssatz gelöscht, der durch das Zuordnen eines Bankumsatzes entstanden war, blieb der Umsatz auf „zugeordnet" stehen – mit einem Verweis auf einen Buchungssatz, den es nicht mehr gab. Er tauchte danach nirgends mehr auf: nicht unter Zuzuordnen (dort stehen nur offene Umsätze) und nicht in den Salden (die kennen nur Buchungen). Auch die Bank-Abstimmung führte ihn weder als gebucht noch als offen, sodass der Kontostand still vom Bankauszug abwich. Der Umsatz steht jetzt nach dem Löschen wieder unter Zuzuordnen und lässt sich neu zuordnen – derselbe Stand wie beim Aufheben einer Zuordnung.
• Belege eines Jahres konnten beim xbuc-Import verloren gehen. Die Dublettenprüfung des Zusammenführ-Imports beschrieb eine Splittbuchung nur über eine ihrer Zeilen. Eine eingehende Buchung, die zufällig auf diesen Teilbetrag passte, galt dadurch als bereits vorhanden und wurde stillschweigend übersprungen. Der Vergleich betrachtet jetzt die ganze Buchung, und beide Seiten des Vergleichs bilden ihren Schlüssel an derselben Stelle.
• Beleg löschen konnte einen Datensatz ohne Datei hinterlassen. Die Datei wurde vor dem Datensatz entfernt; schlug das Löschen des Datensatzes fehl, blieb ein Beleg zurück, der sich nicht mehr öffnen ließ. Jetzt gilt auch hier die Reihenfolge, die beim Löschen einer ganzen Buchung längst galt: erst der Datensatz, dann – nach erfolgreichem Abschluss – die Datei.

Geändert

• Der Jahresabschluss schützt jetzt auch die Konten-Stammdaten. Bisher war ein festgeschriebenes Geschäftsjahr nur gegen Änderungen an den Buchungen gesichert. Über das Konto ließ sich sein Bericht trotzdem nachträglich verschieben: Ein Wechsel der Kontoart dreht das Vorzeichen, ein Wechsel des Geldkonto-Kennzeichens verschiebt das Konto zwischen Vermögensübersicht und Einnahmen-/Ausgaben-Rechnung – das archivierte Jahresergebnis änderte sich, ohne dass eine einzige Buchung angefasst wurde. Kontoart, Geldkonto- Kennzeichen, Sphäre, Rücklagen-Art und Kostenstelle lassen sich deshalb nicht mehr ändern, solange das Konto in einem abgeschlossenen Jahr bebucht ist; wer die Änderung braucht, eröffnet das Jahr wieder und schließt es danach erneut ab. Nummer, Name, Kategorie, Aktiv-Schalter und Überkonto bleiben frei änderbar – sie ändern nur Beschriftungen, keine Beträge.
• Konten stehen jetzt im Änderungsprotokoll. Anlegen, Ändern und Löschen eines Kontos wurden bisher nicht protokolliert – ausgerechnet die Stammdaten, aus denen jede Auswertung gerechnet wird, waren für die Kassenprüfung unsichtbar. Bei einer Änderung vermerkt das Protokoll zusätzlich, ob ein auswertungsrelevantes Feld betroffen war.

Hinzugefügt

• Frei definierbare Kostenstellen. Bisher leitete die App die Kostenstelle aus dem Kontenrahmen ab – entweder aus der zweiten Zahlengruppe der Kontonummer oder „ein Konto = eine Kostenstelle". Beides setzt einen bestimmten Kontenaufbau voraus. Jetzt lassen sich Kostenstellen unter Einstellungen → Kostenstellen frei anlegen und Konten ihnen ausdrücklich zuordnen; beliebige Konten können so zu einem Projekt zusammengefasst werden. Der neue Modus heißt „Frei definierte Kostenstellen" (Einstellungen → Kostenstellen-Modus, nur Verwalter). Die beiden bisherigen Modi bleiben unverändert Standard – bestehende Auswertungen ändern sich nicht. Die Zuordnung geht einzeln im Konto-Dialog oder für viele Konten auf einmal. Angelegte Kostenstellen erscheinen im Bericht auch ohne zugeordnetes Konto, damit eine fehlende Zuordnung sichtbar ist.
• Umbuchen direkt im Kontoauszug. Wer beim Durchblättern eines Kontos (Tab Konten) eine falsch zugeordnete Buchung findet, bucht sie an Ort und Stelle auf ein anderes Konto um – der Umweg über das Journal entfällt. Umbuchen lässt sich jede Seite der Buchung, also auch das Gegenkonto. Geändert wird ausschließlich die Kontozuordnung; Betrag, Datum, Beschreibung und die Gegenseite bleiben, sodass Soll und Haben nicht auseinanderlaufen können. Abgeschlossene Geschäftsjahre bleiben gesperrt, jede Umbuchung steht im Änderungsprotokoll, und eine zwischenzeitliche Änderung durch jemand anderen wird erkannt.

Hinzugefügt

• Kontoauszüge in zwei weiteren Formaten: neben der bisherigen CSV liest die App jetzt auch CAMT.053 (XML) und MT940. Welches Format vorliegt, erkennt sie am Inhalt der Datei – die Endung spielt keine Rolle. CAMT.053 ist die bessere Wahl, wo die Bank es anbietet: Vorzeichen, Datum und Zahlungsbeteiligte stehen dort eindeutig drin, statt aus Spaltenüberschriften erraten zu werden.
• Wachordner: Auf Wunsch liest die App Kontoauszüge selbstständig aus einem Nextcloud-Ordner ein (Einstellungen → Kontoauszüge automatisch einlesen). Den heruntergeladenen Auszug dort ablegen genügt; stündlich sieht ein Hintergrundjob nach. Verarbeitete Dateien wandern nach verarbeitet/, nicht lesbare mit Begründung nach fehler/ – gelöscht wird nichts. Setzt System-Cron voraus. Das ersetzt das Hochladen von Hand, nicht das Herunterladen bei der Bank.
• Vorgemerkte Umsätze aus CAMT.053 werden übersprungen. Sie ändern sich beim endgültigen Buchen häufig noch und kämen sonst ein zweites Mal herein.
• Mehrere Bankkonten werden unterschieden. Am Geldkonto lässt sich die IBAN hinterlegen (Tab Konten → Konto bearbeiten, nur bei Geldkonten); beim Zuordnen einer Bankbuchung wählt die App daraufhin das Geldkonto, auf dem der Umsatz tatsächlich gebucht wurde. Bisher landete alles auf dem ersten Bankkonto des Kontenrahmens. Ohne hinterlegte IBAN – oder wenn der Auszug keine mitbringt – bleibt es beim bisherigen Verhalten. Wer mehrere Konten führt, sollte CAMT.053 oder MT940 exportieren: dort steht die IBAN verlässlich, in der CSV mancher Bank nur eine Kontonummer.

Behoben

• Derselbe Umsatz landet nicht mehr doppelt, wenn das Exportformat wechselt. Die Dublettenerkennung hing am eigenen Konto, und das schreiben die Formate verschieden: die CSV mancher Bank führt dort nur eine Kontonummer, CAMT.053 immer die volle IBAN. Zusätzlich zum bisherigen Vergleich prüft die App Umsätze jetzt über Datum, Betrag und Text gegen die bereits vorhandenen Bankbuchungen.

Sonstiges

• Die Umsatzquellen liegen hinter einer gemeinsamen Schnittstelle (lib/Service/Statement/); Dublettenerkennung, Regeln und Import-Protokoll sind für alle Formate dieselben. Der MT940-Parser ist zugleich die Vorarbeit für einen späteren FinTS-Abruf, der genau dieses Format liefert.
• Das Import-Protokoll hält fest, aus welchem Format ein Import stammt; Geldkonten können ihre IBAN tragen (Migration 122).
• Unit-Tests für beide neuen Parser sowie ein Kreuztest, der denselben Kontoauszug in allen drei Formaten vergleicht (61 Tests).

Behoben

• Beträge werden nicht mehr abgeschnitten. In Tabellen hatte die Betragsspalte eine feste Breite von 100 px; längere Werte wie „28.798,68 €" wurden mit „…" gekürzt und ließen sich falsch lesen. Die Spalte wächst jetzt mit.
• Mobil: „Buchungen" in der unteren Leiste war gekürzt („Buchun…"). Die Einträge teilen sich die Breite jetzt nach Inhalt statt zu gleichen Teilen.
• Mobil: zu kleine Tippziele. Schaltflächen, Auswahlfelder und Eingabefelder waren teils nur 24–36 px hoch. Sie sind jetzt mindestens 44 px – auch auf Tablets, die per Finger bedient werden, aber das Desktop-Layout bekommen.
• Mobil: lange Kontonamen im Kontenbaum wurden gekürzt und waren damit nicht mehr unterscheidbar; sie brechen jetzt um.
• Mobil: das Ende langer Listen lag unter dem schwebenden Buchungs-Knopf und war nicht lesbar.

Sonstiges

• Ausführliche Beschreibung und Screenshots für den Nextcloud App Store.

Erste im Nextcloud App Store veröffentlichte Fassung. Am Programm selbst ändert sich gegenüber 0.11.0 nichts.

Sonstiges

• Die App wird jetzt mit dem von Nextcloud ausgestellten Zertifikat signiert (appinfo/signature.json) und im App Store veröffentlicht. Das Paket zu 0.11.0 war noch unsigniert und ist deshalb nur über ein direktes Deployment aus dem GitHub-Release installierbar.