androidlover5842/TrisolarisPMS
1
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Finance: Cashbook (cash in/out) with categories + approvals #12

New Issue
Open
opened 2026-02-09 17:29:16 +05:30 by androidlover5842 · 0 comments
androidlover5842 commented 2026-02-09 17:29:16 +05:30
Owner
Copy Link

Goal

  • Owner/manager can understand actual cash position even when cash is spent during the day.

Work

  • Cashbook entries:
    • IN: guest payments (already exists)
    • OUT: staff advance, groceries, maintenance, refunds, deposits to bank
  • Each OUT entry requires:
    • amount, category, notes, paidTo (vendor/employee), createdBy, createdAt
    • optional receipt image upload
  • Approvals:
    • staff can request
    • manager can approve up to limit
    • owner/admin approve above limit
  • Reports:
    • cash on hand (opening + in - out)
    • outflow by category/person
    • audit trail for edits/reversals (no hard delete)

Engineering requirements

  • Server is source of truth; follow Room DB sync rule.
  • Add explicit policy methods in core/auth/AuthzPolicy (do not reuse unrelated gates).

Acceptance

  • At any time, owner can see: cash collected, cash spent, cash deposited, expected cash on hand.
Goal - Owner/manager can understand actual cash position even when cash is spent during the day. Work - Cashbook entries: - IN: guest payments (already exists) - OUT: staff advance, groceries, maintenance, refunds, deposits to bank - Each OUT entry requires: - amount, category, notes, paidTo (vendor/employee), createdBy, createdAt - optional receipt image upload - Approvals: - staff can request - manager can approve up to limit - owner/admin approve above limit - Reports: - cash on hand (opening + in - out) - outflow by category/person - audit trail for edits/reversals (no hard delete) Engineering requirements - Server is source of truth; follow Room DB sync rule. - Add explicit policy methods in `core/auth/AuthzPolicy` (do not reuse unrelated gates). Acceptance - At any time, owner can see: cash collected, cash spent, cash deposited, expected cash on hand.
androidlover5842 added the featureroom-db-synccompliancesecurityfinance labels 2026-02-09 17:29:16 +05:30
androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:29:49 +05:30
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai-ocr
AI / OCR / parsing automation
 api
API / contract / retrofit
 availability
Availability / inventory / allocation
 bug
Bug / regression
 compliance
Compliance / audit / legal requirements
 feature
User-facing functionality
 finance
Cashbook / expenses / settlements
 guest
Guest profile & identity flows
 guest-docs
Guest documents (upload/view/delete)
 hr-payroll
Staff, attendance, payroll
 integration
3rd party integrations / automation
 privacy
Privacy, consent, sensitive data handling
 room-db-sync
Must follow Room DB sync rule
 room-stay
Room stay management
 security
Security / permissions / sensitive data
 telephony
Call-related UX/integrations
 ux
User experience / UI polish
 voice-ai
Speech-to-text / voice extraction
No Label compliance feature finance room-db-sync security
Milestone
No items
No Milestone
Projects
Clear projects
No project TrisolarisPMS Roadmap
Assignees
Clear assignees
androidlover5842
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: androidlover5842/TrisolarisPMS#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?