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

Finance: Cash handover logs (staff -> owner/manager) + per-person cash position #16

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

Goal

  • When owner/manager collects physical cash from staff (or transfers between staff), it must be logged so owner knows who has how much.

Work

  • Introduce Cash Handover transaction:
    • amount (cash)
    • fromUserId (who had the cash)
    • toUserId (owner/manager/cashier)
    • occurredAt
    • notes
    • optional evidence photo (receipt/ledger slip)
  • Cash position report:
    • for any date range (or "now"): cash collected by user - payouts by user - handovers out + handovers in - deposits
    • shows "cash currently with each person/counter"
  • Permissions:
    • staff can record handover they give
    • receiver confirms (2-step) OR allow receiver to create on behalf with audit trail
    • no delete; only reversal

Engineering requirements

  • Server is source of truth; follow Room DB sync rule.
  • Explicit policy methods in core/auth/AuthzPolicy (separate from payment permissions).

Acceptance

  • Owner can answer: "How much cash is with each person right now?" and reconcile mismatches.
Goal - When owner/manager collects physical cash from staff (or transfers between staff), it must be logged so owner knows who has how much. Work - Introduce Cash Handover transaction: - amount (cash) - fromUserId (who had the cash) - toUserId (owner/manager/cashier) - occurredAt - notes - optional evidence photo (receipt/ledger slip) - Cash position report: - for any date range (or "now"): cash collected by user - payouts by user - handovers out + handovers in - deposits - shows "cash currently with each person/counter" - Permissions: - staff can record handover they give - receiver confirms (2-step) OR allow receiver to create on behalf with audit trail - no delete; only reversal Engineering requirements - Server is source of truth; follow Room DB sync rule. - Explicit policy methods in `core/auth/AuthzPolicy` (separate from payment permissions). Acceptance - Owner can answer: "How much cash is with each person right now?" and reconcile mismatches.
androidlover5842 added the featureroom-db-synccompliancesecurityfinance labels 2026-02-09 17:32:04 +05:30
androidlover5842 added this to the TrisolarisPMS Roadmap project 2026-02-09 17:32:13 +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#16
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?