Skip to main content
Source snapshot: 13 October 2026. These pages describe the current implementation, including unfinished controls. See coverage and review notes.

Finance settings

Host: admin.<ROOT_DOMAIN> · Route: /[tenant]/settings/finance

Purpose and access

Configure the operational funds, ledger mappings, numbering, bank accounts, categories, dynamic collection fields, and payment methods used by finance screens.You need an account session and a resolved membership context in the selected Mahallu (including the API’s current platform elevation path). The API independently checks the requested operation’s permissions and feature availability.

Screen layout

The screen provides operational funds and COA ledgers, general currency/receipt/voucher settings, bank accounts, collection/expense categories, and payment methods. Category dialogs expose target scope, economic category, amounts, recurrence, and custom fields where applicable.

Fields and displayed information

Displayed table columns: Fund Name, Code, Description, Linked Categories, Default / Status, Actions, Ledger Account Name, Account Type, Mapped Categories, Balance, Bank Name, Account Name, Account Number, IFSC Code, Branch, Status.

Fields and filters: Finance settings client

Fields and filters: Dynamic form builder

Actions

Interaction sequence

Create operational funds and ledger accounts → create a category and map its fund/COA account → configure targets and dynamic fields → save. Set bank accounts and payment methods → save numbering/currency settings → use Collections or Payments with these definitions.

States and rules

Operational funds and ledger accounts are distinct records. Category COA mapping determines posting; do not treat a saved collection as automatically posted. Each dialog saves independently. Bank editing can keep the existing number when left blank.The rendered action controls bind loading indicators to pending state. Failed API saves keep their documented error/notification path; a loading indicator alone does not establish persistence.

Implementation references

Paths below are relative to the application repository. This is source-reviewed behavior, not a recorded browser test.
  • apps/web/src/app/sites/admin/[tenant]/settings/finance/page.tsx
  • apps/web/src/app/sites/admin/[tenant]/settings/finance/finance-settings-client.tsx
  • apps/web/src/features/finance/dynamic-form-builder.tsx
Data and access helpers: apps/web/src/lib/session.ts, apps/web/src/lib/server-api.ts, apps/web/src/lib/tenants.ts, apps/web/src/lib/finance.ts, apps/web/src/lib/structure.ts, apps/web/src/lib/api-client.ts

API behavior references

  • apps/api/src/tenants/admins.controller.ts
  • apps/api/src/tenants/roles.controller.ts
  • apps/api/src/tenants/tenants.controller.ts
  • apps/api/src/structure/structure.controller.ts
  • apps/api/src/notifications/notifications.controller.ts
  • apps/api/src/finance/finance.controller.ts