Update OpenSpec artifacts to reflect implementation reality
design.md — 6 new decisions: - D19: AccountTreeGrid with Σ crossfade animation - D20: Three-tab Inspect Ledgers (huvudbok/grundbok/search) - D21: Transaction detail dialog with balanced indicator - D22: [LOC] account name resolution (with future multi-language path via Accept-Language for Open Ledgers) - D23: No server-side PDF rasterization (browser renders natively) - D24: CI with local NuGet/npm cache mirrors (Nexus) design.md — 7 new resolved questions: - Document rasterization eliminated - Migration from mysqldump (not live DB) - OOD lookup table mapping by name (not hardcoded IDs) - Open Ledgers locale per-request via Accept-Language - VAT amount entry: manual inbound, pre-filled outbound - Frontend state management: simple hooks, no framework specs/frontend-app — major expansion: - AccountTreeGrid component spec with crossfade scenarios - Balance Sheet/P&L with quarterly columns spec - Inspect Ledgers three-tab spec with 7 detailed scenarios - [LOC] account name resolution spec - Chart of accounts tree spec specs/documents — new requirements: - No server-side PDF rasterization - Legacy rasterized document support - Meaningful download filenames from business objects specs/data-migration — additions: - OOD lookup table discovery detail - Verified production migration results with exact counts - Implementation notes (batched inserts, zero-datetime, triggers) tasks.md — honest reconciliation: - Section 9: 16 of 21 tasks marked done (was 0/17) - Section 10: 10.7 marked done with full description - New tasks: 9.18 (LOC resolver), 9.19 (RBAC), 9.20 (org-scoping), 9.21 (closing journal) - Total: 137 done, 13 remaining (was 119/146) Made-with: Cursor
This commit is contained in:
@@ -165,9 +165,9 @@ ExchangeRateService
|
||||
**Rationale:** No existing CI to preserve (CruiseControl.NET is dead). Gitea Actions is workflow-compatible with GitHub Actions. Docker provides reproducible builds and deployment.
|
||||
|
||||
**Pipeline stages:**
|
||||
1. `dotnet restore` + `dotnet build` + `dotnet test`
|
||||
2. `npm ci` + `npm run build` (frontend)
|
||||
3. `docker build` (multi-stage: build + runtime)
|
||||
1. `dotnet restore` (with optional NuGet cache mirror) + `dotnet build` + `dotnet test`
|
||||
2. `npm ci` (with optional npm registry mirror) + `npm run lint` + `npm run build` (frontend)
|
||||
3. `docker build` (multi-stage: build + runtime, cache mirrors passed as build args)
|
||||
4. Push image to registry
|
||||
|
||||
### D12: Continuation transactions for closed-period operations
|
||||
@@ -231,6 +231,55 @@ ExchangeRateService
|
||||
|
||||
**Decision:** v6 Bucket 1 ships with English (primary), Swedish (secondary), and German (should-have). Translation packs use standard .NET resource files (.resx) for the backend and a JSON-based i18n system (e.g., react-i18next) for the frontend. AI-assisted translation generates initial packs; human review for Swedish.
|
||||
|
||||
### D19: AccountTreeGrid — aggregating collapsible tree component
|
||||
|
||||
**Decision:** Build a reusable React tree grid component that displays hierarchical financial data with expand/collapse. Parent nodes show Σ-prefixed aggregated values when collapsed and their own direct values when expanded. Column totals remain invariant regardless of expand/collapse state.
|
||||
|
||||
**Implementation:** Each parent cell contains two absolutely-positioned overlapping elements (aggregate value and own value). `isCollapsed` toggles opacity between them via CSS transition — a pure crossfade with no JavaScript animation timing. Child rows animate height via a wrapper div with `overflow: hidden`. Fixed column widths via `tableLayout: fixed` + `<colgroup>` prevent layout shifts.
|
||||
|
||||
**Rationale:** This replicates the v5 EasyUI treegrid behavior that was central to the Open Ledgers interface. The column-total invariant is the key requirement — the tree is a drill-down into the same total, not a filter.
|
||||
|
||||
**Used by:** Balance Sheet (quarterly), Profit & Loss (quarterly), Chart of Accounts.
|
||||
|
||||
### D20: Three-tab Inspect Ledgers (huvudbok / grundbok / search)
|
||||
|
||||
**Decision:** The Inspect Ledgers page is structured as three tabs:
|
||||
1. **Account Ledger (huvudbok):** Per-account transaction view with group support (selecting a parent shows all descendants merged), prior/closing balance rows, "own transactions only" checkbox
|
||||
2. **General Journal (grundbok):** All transactions chronologically, grouped by transaction with header rows and indented account rows showing type badges, `Parent » Child` account paths, and per-row running balances
|
||||
3. **Search:** Cross-account search by description, Tx#, amount range, date range
|
||||
|
||||
**Rationale:** These three views cover the standard accounting inspection needs: per-account drill-down, chronological journal, and ad-hoc search. The v5 system had the first two as separate EasyUI grids; v6 unifies them under tabs with a shared transaction detail dialog.
|
||||
|
||||
**Running balance computation:** Balance accounts (Asset/Debt) use all-time cumulative prior balance. Result accounts (Income/Cost) use fiscal-year-start prior balance. This matches standard accounting practice where P&L resets annually.
|
||||
|
||||
### D21: Transaction detail dialog
|
||||
|
||||
**Decision:** Clicking any transaction (in any tab) opens a modal dialog showing: transaction number with balanced/unbalanced indicator, date, description, currency, all rows with account names and debit/credit, dependency link (expense claim, invoice, etc.), blockchain hash, and documentation indicator.
|
||||
|
||||
**Rationale:** Provides a single consistent drill-down from any view. The balanced/unbalanced chip gives instant confidence about transaction integrity.
|
||||
|
||||
### D22: [LOC] account name resolution
|
||||
|
||||
**Decision:** Account names prefixed with `[LOC]` are localization keys from v5's resource system. The API layer resolves these to human-readable display names before sending to the frontend. Currently uses a static English dictionary matching the v5 `.resx` file. Non-`[LOC]` names (user-created accounts) pass through unchanged.
|
||||
|
||||
**Future:** The resolver will become a service that accepts a culture parameter, loaded from the v5 `.resx` files (45 languages available). For Open Ledgers, the `Accept-Language` header from the browser determines the locale per-request (not per-user), so a German Steuerberater sees German account names while the owner sees English — without any configuration.
|
||||
|
||||
### D23: Document storage — no server-side rasterization
|
||||
|
||||
**Decision:** v6 stores uploaded documents (PDF, JPEG, PNG) as-is, one Document record per upload. The browser renders PDFs natively via `<embed>` or pdf.js. No Ghostscript rasterization pipeline.
|
||||
|
||||
**Rationale:** The v5 rasterization pipeline (PDF → Ghostscript → per-page PNGs) was necessary in 2006 when browsers couldn't render PDFs. Modern browsers handle this natively. Eliminating the pipeline removes a complex backend dependency and simplifies the upload flow.
|
||||
|
||||
**Legacy support:** Migrated v5 documents are rasterized PNGs with `{{LOCPAGE-N-M}}` markers in ClientFileName. The viewer detects these and displays them as an image gallery. Original PDFs are still on disk (extensionless GUID files) and can be served for download.
|
||||
|
||||
**Download naming:** Documents are served with a meaningful filename derived from the business object dependency (e.g., "Expense Claim 184.pdf") rather than the GUID server filename.
|
||||
|
||||
### D24: CI with local NuGet/npm cache mirrors
|
||||
|
||||
**Decision:** The Gitea Actions CI pipeline supports optional local NuGet and npm cache mirrors (Nexus) configured via repository action variables (`NUGET_CACHE_URL`, `NPM_REGISTRY_URL`). When set, packages are fetched from the cache with fallback to public registries. When not set, the pipeline works exactly as before.
|
||||
|
||||
**Rationale:** Build reliability and speed in environments where upstream registries may be unreliable or slow. The cache is transparent — no code or project file changes needed.
|
||||
|
||||
## Risks / Trade-offs
|
||||
|
||||
**[Risk] Migration data fidelity** — ETL could introduce rounding errors or miss edge cases in financial data, leading to legally incorrect ledger presentation.
|
||||
@@ -312,3 +361,15 @@ The v5 production database is never touched — not even read during migration.
|
||||
- **Intermediate currency calculation precision** — Keep `double`, matching v5. `decimal` causes hard-to-debug issues in practice. Rates are inherently fluctuating snapshots; sub-cent precision on conversions is not meaningful. Documented as deliberate.
|
||||
|
||||
- **Fiscal year start month** — Removed from v6 Bucket 1. v5 assumes calendar-year fiscal years. Configurable fiscal year start is a Bucket 2+ concern at best.
|
||||
|
||||
- **Document rasterization** — Eliminated. v5 used Ghostscript to convert PDFs to per-page PNGs for browser display. v6 stores originals and lets the browser render PDFs natively. Legacy rasterized PNGs from migration are still supported.
|
||||
|
||||
- **Migration source** — mysqldump file, not live database connection. The dump is the legal archival artifact (sha256 checksummed). Migration loads it into a temporary MySQL instance. v5 production is never touched.
|
||||
|
||||
- **OOD lookup table mapping** — v5 ObjectOptionalData uses database-assigned IDs (not matching the C# enum ordinals). The migration tool reads the `ObjectTypes` and `ObjectOptionalDataTypes` lookup tables to map by name, not hardcoded IDs.
|
||||
|
||||
- **Open Ledgers locale** — Per-request via `Accept-Language` header, not per-user setting. Multiple concurrent Open Ledgers sessions can have different locales. The Steuerberater sees German, the owner sees English, no configuration needed.
|
||||
|
||||
- **VAT amount entry** — Inbound (expenses, supplier invoices): manual entry in whole currency units matching the receipt exactly, converted to cents at the API boundary. Outbound (customer invoices): pre-filled from org's `DefaultVatRatePercent`, editable for cross-border/exempt cases.
|
||||
|
||||
- **Frontend state management** — Simple `useState`/`useEffect`/`useMemo` with direct API calls. No Redux, no React Query. The accounting domain's page-based navigation means each page fetches its own data on mount. This proved sufficient and avoids framework overhead.
|
||||
|
||||
@@ -35,7 +35,7 @@ The tool SHALL migrate: financial accounts (chart of accounts with OwnerUserId),
|
||||
- **THEN** the v6 organization's `ClosedThroughYear` is set to N and all transactions in years <= N are marked as belonging to a closed period
|
||||
|
||||
### Requirement: ObjectOptionalData denormalization
|
||||
The tool SHALL read the v5 `ObjectOptionalData` EAV table and denormalize kept keys into first-class v6 columns per the mapping in design decision D16. The tool SHALL report any EAV keys found in v5 data that are not in the explicit keep/drop mapping, so nothing is silently lost.
|
||||
The tool SHALL read the v5 `ObjectOptionalData` EAV table and denormalize kept keys into first-class v6 columns per the mapping in design decision D16. The tool SHALL report any EAV keys found in v5 data that are not in the explicit keep/drop mapping, so nothing is silently lost. The tool SHALL read the v5 `ObjectTypes` and `ObjectOptionalDataTypes` lookup tables to resolve EAV keys by name (not hardcoded IDs), since the database-assigned IDs do not match the C# enum ordinals — they are populated on first use.
|
||||
|
||||
#### Scenario: Org settings denormalized
|
||||
- **WHEN** v5 has `OrgEconomyEnabled`, `OrgCurrency`, `OrgFirstFiscalYear`, `OrgBooksClosedForYear`, `OrgValueAddedTaxEnabled`, `OrgGovtRegistrationId`, etc. in ObjectOptionalData
|
||||
@@ -107,3 +107,29 @@ The migration tool SHALL support re-running against a v6 database. Re-running dr
|
||||
#### Scenario: Re-run migration
|
||||
- **WHEN** the migration tool is run against a v6 database that already contains migrated data
|
||||
- **THEN** the existing data is replaced with a fresh migration from v5
|
||||
|
||||
### Implementation Notes (verified against production data)
|
||||
|
||||
The migration tool has been run against a real production mysqldump (sha256: `735ba82d601e0c73b52d9323e200fccd90e4757c240aa9d56e71080cce06850e`, 396MB) with the following verified results:
|
||||
|
||||
- 246 currencies, 2 organizations (with full OOD denormalization including OpenLedgersDomain, VanityDomain)
|
||||
- 4 users (from People), 147 financial accounts (with OOD: native currency, bitcoin fields)
|
||||
- 4,010 transactions (with OrganizationSequenceId, BlockchainHash), 8,590 rows (67 with foreign currency)
|
||||
- 1,227 dependencies (28 continuation chains preserved)
|
||||
- 292 expense claims, 283 inbound invoices (with OOD: description, native currency), 101 outbound invoices
|
||||
- 422 payouts, 98 payment groups, 98 payments
|
||||
- 2,863 documents, 3,570 exchange rate snapshots + 614,750 datapoints
|
||||
- 36 hot wallet addresses + 44 UTXOs, 12 dependency types, 21 system settings
|
||||
|
||||
Verification passed on all three levels:
|
||||
- Transaction row totals per org/year: exact match
|
||||
- Per-account balance totals (100 accounts): exact match
|
||||
- Record counts for all major tables: exact match
|
||||
|
||||
Key implementation details discovered during migration:
|
||||
- v5 `ObjectTypes` and `ObjectOptionalDataTypes` are lookup tables populated on first use; IDs don't match C# enum ordinals
|
||||
- `ClosedThroughYear` uses v5 OOD value when present, with configurable fallbacks per org
|
||||
- Exchange rate datapoints require batched INSERT (614K rows); individual stored procedure calls are too slow
|
||||
- MySQL zero-datetime values in outbound invoices require `AllowZeroDateTime=True;ConvertZeroDateTime=True`
|
||||
- Closed-period triggers must be disabled during migration (historical data loading), then re-enabled after
|
||||
- Only organizations 7 and 8 are migrated (configurable in the tool)
|
||||
|
||||
@@ -32,3 +32,32 @@ The system SHALL access document storage through an `IDocumentStorage` interface
|
||||
#### Scenario: Storage interface isolation
|
||||
- **WHEN** a document is stored or retrieved
|
||||
- **THEN** the operation goes through `IDocumentStorage` and does not directly reference filesystem APIs in the business logic
|
||||
|
||||
### Requirement: No server-side PDF rasterization
|
||||
v6 SHALL NOT rasterize PDFs to PNGs on the server. Uploaded documents (PDF, JPEG, PNG) are stored as-is with one Document record per upload. The browser renders PDFs natively. This replaces the v5 Ghostscript pipeline.
|
||||
|
||||
#### Scenario: Upload PDF
|
||||
- **WHEN** a user uploads a PDF receipt
|
||||
- **THEN** the PDF is stored as-is and one Document record is created (not one per page)
|
||||
|
||||
#### Scenario: View PDF in browser
|
||||
- **WHEN** a user views an attached PDF document
|
||||
- **THEN** the browser renders the PDF natively via embed or pdf.js
|
||||
|
||||
### Requirement: Legacy rasterized document support
|
||||
Migrated v5 documents (rasterized PNGs with `{{LOCPAGE-N-M}}` markers in ClientFileName) SHALL continue to be viewable as image galleries. The original PDFs (extensionless GUID files on disk) SHALL be available for download.
|
||||
|
||||
#### Scenario: View legacy document
|
||||
- **WHEN** a user views a document whose ClientFileName contains `{{LOCPAGE`
|
||||
- **THEN** the system displays it as part of a page gallery (multiple PNGs from the same original upload)
|
||||
|
||||
#### Scenario: Download original PDF
|
||||
- **WHEN** a user downloads a legacy document
|
||||
- **THEN** the system serves the original PDF (extensionless GUID file) with a meaningful filename derived from the business object (e.g., "Expense Claim 184.pdf")
|
||||
|
||||
### Requirement: Meaningful download filenames
|
||||
When downloading a document, the system SHALL set the `Content-Disposition` filename to a human-readable name derived from the linked business object, not the internal GUID server filename.
|
||||
|
||||
#### Scenario: Download expense receipt
|
||||
- **WHEN** a user downloads a receipt attached to Expense Claim #184
|
||||
- **THEN** the downloaded file is named "Expense Claim 184.pdf" (or similar)
|
||||
|
||||
@@ -25,16 +25,68 @@ The frontend SHALL provide a sidebar navigation matching the Bucket 1 functional
|
||||
- **WHEN** a user clicks "Balance Sheet" in the navigation
|
||||
- **THEN** the balance sheet page loads with data for the active organization
|
||||
|
||||
### Requirement: Ledger pages
|
||||
The frontend SHALL implement pages for: chart of accounts (tree view, create/edit/close accounts), inspect ledgers (account + date range → transaction rows), balance sheet (as-of date), P&L (fiscal year), and budget vs actual (year view with variance).
|
||||
### Requirement: AccountTreeGrid component
|
||||
The frontend SHALL provide a reusable tree grid component for hierarchical financial data. Parent nodes show Σ-prefixed aggregated values when collapsed and their own direct values when expanded. Column totals SHALL remain invariant regardless of expand/collapse state. The transition between aggregate and own values SHALL use a CSS opacity crossfade. Child rows SHALL animate height smoothly on expand/collapse. Column widths SHALL be fixed to prevent layout shifts.
|
||||
|
||||
#### Scenario: Inspect ledger with date range
|
||||
- **WHEN** a user selects an account and date range on the inspect ledgers page
|
||||
- **THEN** transaction rows for that account and period are displayed with running balance
|
||||
#### Scenario: Collapse parent node
|
||||
- **WHEN** a user collapses a parent account node
|
||||
- **THEN** the children slide closed, the parent's own value crossfades to the Σ aggregate value, and the column total remains unchanged
|
||||
|
||||
#### Scenario: Expand parent node
|
||||
- **WHEN** a user expands a parent account node
|
||||
- **THEN** the children slide open, the parent's Σ aggregate crossfades to its own value (or empty if zero), and the column total remains unchanged
|
||||
|
||||
### Requirement: Balance Sheet and P&L with quarterly columns
|
||||
The Balance Sheet and P&L pages SHALL use the AccountTreeGrid with quarterly period columns (Start/Q1/Q2/Q3/Q4/Current for balance sheet; Last Year/Q1/Q2/Q3/Q4/YTD for P&L). Each page SHALL have a year selector and a CSV download option.
|
||||
|
||||
#### Scenario: View quarterly balance sheet
|
||||
- **WHEN** a user views the balance sheet for a given year
|
||||
- **THEN** the tree grid shows Assets and Liabilities sections with quarterly movement columns
|
||||
|
||||
### Requirement: Inspect Ledgers — three tabs
|
||||
The Inspect Ledgers page SHALL be structured as three tabs: Account Ledger (huvudbok), General Journal (grundbok), and Search.
|
||||
|
||||
#### Scenario: Account Ledger tab
|
||||
- **WHEN** a user selects an account from the searchable dropdown (showing tree indentation), a year, and optionally a month
|
||||
- **THEN** the system displays transaction rows with Tx#, date, description, debit, credit, and running balance, with prior balance and closing balance rows
|
||||
|
||||
#### Scenario: Account Ledger group view
|
||||
- **WHEN** a user selects a parent account that has children
|
||||
- **THEN** transactions from all descendant accounts are merged chronologically with an Account column showing which sub-account each row belongs to
|
||||
|
||||
#### Scenario: Account Ledger own-only filter
|
||||
- **WHEN** a user checks "Show only this account's own transactions (exclude sub-accounts)"
|
||||
- **THEN** only transactions posted directly to the selected account are shown; the checkbox remains visible regardless of whether results are empty
|
||||
|
||||
#### Scenario: General Journal tab
|
||||
- **WHEN** a user selects a year and month on the General Journal tab
|
||||
- **THEN** all transactions are shown chronologically, each with a bold header row (Tx#, date, description) and indented account rows showing type badge, account path (Parent » Child), debit, credit, and per-account running balance
|
||||
|
||||
#### Scenario: General Journal running balance
|
||||
- **WHEN** the General Journal displays transaction rows
|
||||
- **THEN** each row shows the running balance for that specific account after this row's delta is applied; balance accounts use all-time cumulative, result accounts use fiscal-year-start
|
||||
|
||||
#### Scenario: Search tab
|
||||
- **WHEN** a user enters search criteria (description text, Tx#, amount range, date range) and presses Search or Enter
|
||||
- **THEN** matching transactions are displayed in General Journal format, clickable for detail
|
||||
|
||||
#### Scenario: Transaction detail dialog
|
||||
- **WHEN** a user clicks any transaction row or header in any tab
|
||||
- **THEN** a modal dialog opens showing the full transaction: number, balanced/unbalanced indicator, date, description, currency, all rows with account names and debit/credit, dependency link, blockchain hash, and documentation indicator
|
||||
|
||||
### Requirement: [LOC] account name resolution
|
||||
Account names prefixed with `[LOC]` SHALL be resolved to human-readable display names before rendering. The resolution uses the v5 localization resource mappings (e.g., `[LOC]Asset_BitcoinHot` → "Bitcoin Hot Wallet"). Non-`[LOC]` names pass through unchanged.
|
||||
|
||||
#### Scenario: Localized account name display
|
||||
- **WHEN** an account with name `[LOC]Debt_Equity` is displayed
|
||||
- **THEN** the user sees "Equity" (or the equivalent in their locale)
|
||||
|
||||
### Requirement: Chart of accounts tree
|
||||
The frontend SHALL display accounts in a hierarchical tree grouped by type (Asset, Debt, Income, Cost) using the AccountTreeGrid component.
|
||||
|
||||
#### Scenario: Chart of accounts tree
|
||||
- **WHEN** a user views the chart of accounts
|
||||
- **THEN** accounts are displayed in a hierarchical tree grouped by type (Asset, Debt, Income, Cost)
|
||||
- **THEN** accounts are displayed in a hierarchical tree grouped by type with expand/collapse
|
||||
|
||||
### Requirement: Financial workflow pages
|
||||
The frontend SHALL implement pages for: expense claim submission (with document upload), inbound invoice registration, outbound invoice creation, attestation queue (list of items pending the user's attestation), receipt validation, and payout management.
|
||||
|
||||
@@ -110,23 +110,27 @@
|
||||
|
||||
## 9. API Layer (UsingCash.Api)
|
||||
|
||||
- [ ] 9.1 Configure ASP.NET Core host: DI registration for repositories and logic services, session-cookie auth middleware, org-scoping middleware, error response middleware
|
||||
- [ ] 9.2 Implement auth endpoints: POST /api/auth/login, POST /api/auth/logout, POST /api/auth/reset-password, GET /api/auth/me
|
||||
- [ ] 9.3 Implement financial account endpoints: GET/POST /api/organizations/{orgId}/accounts, PUT /api/organizations/{orgId}/accounts/{id} (including budget owner assignment)
|
||||
- [ ] 9.4 Implement ledger endpoints: GET /api/organizations/{orgId}/ledger, GET .../balance-sheet, GET .../profit-loss, GET .../budget-vs-actual
|
||||
- [ ] 9.5 Implement transaction endpoints: GET/POST /api/organizations/{orgId}/transactions, GET .../transactions/{id} (showing continuation chains)
|
||||
- [ ] 9.6 Implement expense claim endpoints: GET/POST /api/organizations/{orgId}/expense-claims (with VAT), POST .../attest, POST .../validate
|
||||
- [ ] 9.7 Implement invoice endpoints: GET/POST for inbound-invoices (with VAT) and outbound-invoices (with VAT), attestation and payment actions
|
||||
- [ ] 9.8 Implement payout endpoints: GET/POST /api/organizations/{orgId}/payouts, POST .../execute, POST .../confirm
|
||||
- [ ] 9.9 Implement crypto endpoints: GET /api/organizations/{orgId}/crypto/treasury, GET .../addresses, POST .../payouts
|
||||
- [ ] 9.10 Implement document endpoints: POST /api/organizations/{orgId}/documents (upload), GET .../documents/{id} (download)
|
||||
- [ ] 9.11 Implement dashboard endpoints: GET /api/organizations/{orgId}/dashboard, GET .../tasks
|
||||
- [ ] 9.12 Implement end-of-month endpoints: GET /api/organizations/{orgId}/end-of-month/checklist, POST .../upload-statement, POST .../close-year
|
||||
- [ ] 9.13 Implement organization endpoints: GET/PUT /api/organizations/{orgId} (all denormalized settings), GET /api/organizations
|
||||
- [ ] 9.14 Implement user management endpoints: GET/POST/PUT /api/users, POST /api/users/{id}/roles
|
||||
- [x] 9.1 Configure ASP.NET Core host: DI registration for repositories and logic services, session-cookie auth middleware, error response middleware
|
||||
- [x] 9.2 Implement auth endpoints: POST /api/auth/login, POST /api/auth/logout, POST /api/auth/reset-password (stub), GET /api/auth/me (with dev-mode auto-auth)
|
||||
- [x] 9.3 Implement financial account endpoints: GET/POST /api/organizations/{orgId}/accounts, PUT /api/organizations/{orgId}/accounts/{id}
|
||||
- [x] 9.4 Implement ledger endpoints: inspect/ledger (with group view), inspect/general-journal, inspect/accounts-tree, reports/balance-sheet-tree, reports/profit-loss-tree, search/transactions
|
||||
- [x] 9.5 Implement transaction endpoints: GET /api/organizations/{orgId}/transactions/{id} (with dependency and row detail)
|
||||
- [x] 9.6 Implement expense claim endpoints: GET/POST /api/organizations/{orgId}/expense-claims, POST .../attest, POST .../validate
|
||||
- [x] 9.7 Implement invoice endpoints: GET/POST for inbound-invoices (with OOD), outbound-invoices, attestation
|
||||
- [x] 9.8 Implement payout endpoints: GET/POST /api/organizations/{orgId}/payouts (list is stub)
|
||||
- [x] 9.9 Implement crypto endpoints: GET /api/organizations/{orgId}/crypto/treasury, GET .../addresses, GET .../addresses/{id}/utxos
|
||||
- [x] 9.10 Implement document endpoints: POST /api/organizations/{orgId}/documents (upload), GET .../documents/{id} (download from configured docstore)
|
||||
- [x] 9.11 Implement dashboard endpoints: GET /api/organizations/{orgId}/dashboard, GET .../tasks
|
||||
- [x] 9.12 Implement end-of-month endpoints: GET .../end-of-month/checklist, POST .../close-year (closing journal is TODO)
|
||||
- [x] 9.13 Implement organization endpoints: GET/PUT /api/organizations/{orgId} (with currencyCode), GET /api/organizations (with currencyCode)
|
||||
- [x] 9.14 Implement user management endpoints: GET/POST/PUT /api/users, POST /api/users/{id}/roles, DELETE .../roles/{roleId}
|
||||
- [ ] 9.15 Implement WebSocket endpoint for real-time notifications (deposit alerts, task changes, heartbeat status) with session-cookie auth on upgrade
|
||||
- [ ] 9.16 Configure static file serving for React SPA with fallthrough to index.html
|
||||
- [ ] 9.17 Implement dev-mode impersonation endpoint (disabled in production via configuration)
|
||||
- [x] 9.16 Configure static file serving for React SPA with fallthrough to index.html
|
||||
- [x] 9.17 Implement dev-mode impersonation endpoint (disabled in production via configuration)
|
||||
- [x] 9.18 Implement [LOC] account name resolution via AccountNameResolver (applied to all account-returning endpoints)
|
||||
- [ ] 9.19 Add RBAC enforcement middleware (Permission checks on API endpoints)
|
||||
- [ ] 9.20 Add org-scoping middleware (validate user belongs to requested org)
|
||||
- [ ] 9.21 Implement year-end closing journal creation in close-year endpoint (Dec 31 P&L-to-equity transfer)
|
||||
|
||||
## 10. Frontend Application
|
||||
|
||||
@@ -136,9 +140,9 @@
|
||||
- [x] 10.4 Implement app shell: sidebar navigation, top bar with org switcher and language selector, responsive layout
|
||||
- [x] 10.5 Implement dashboard page: task summary, YTD P&L, quick links, end-of-month status
|
||||
- [x] 10.6 Implement chart of accounts page: tree view with account types, create/edit/close/assign-owner actions
|
||||
- [ ] 10.7 Implement inspect ledgers page: account selector, date range picker, transaction row table with running balance and continuation chain links
|
||||
- [x] 10.8 Implement balance sheet page: as-of date selector, asset/debt/equity breakdown
|
||||
- [x] 10.9 Implement profit & loss page: fiscal year selector, income/cost breakdown
|
||||
- [x] 10.7 Implement inspect ledgers page: three tabs (Account Ledger with group view + checkbox, General Journal with per-row running balance + account type badges, Search with description/Tx#/amount range/date range), transaction detail dialog with balanced indicator
|
||||
- [x] 10.8 Implement balance sheet page: AccountTreeGrid with quarterly columns (Start/Q1/Q2/Q3/Q4/Current), CSV download
|
||||
- [x] 10.9 Implement profit & loss page: AccountTreeGrid with quarterly columns (Last Year/Q1/Q2/Q3/Q4/YTD), net result chip, CSV download
|
||||
- [ ] 10.10 Implement budget vs actual page: year selector, account-level budget/actual/variance table
|
||||
- [x] 10.11 Implement expense claim pages: list view (submission form and attestation actions are TODO)
|
||||
- [ ] 10.12 Implement inbound invoice pages: registration form with smart monetary input for amount and VAT, smart date input for issue/due dates, list view, attestation action
|
||||
|
||||
Reference in New Issue
Block a user