Project

General

Profile

Actions

Feature #704

open
NP

Canteen: monthly employee subsidy report (sub-project A of HR settlement)

Feature #704: Canteen: monthly employee subsidy report (sub-project A of HR settlement)

Added by Navya P. 11 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
11/01/2026
Due date:
% Done:

0%

Estimated time:
Resolved By:

Description

A large request came in for a full "Canteen <-> HR monthly subsidy settlement" feature -- Canteen reviews/approves a monthly report, generates a PDF, sends it to HR, HR reviews/approves/rejects, HR/Finance tracks payment. This directly overlaps with the payroll-deduction feature cancelled earlier (Feature #671) -- different mechanism, same underlying thing: a formal monthly reconciliation of what employees owe/are owed between Canteen and HR.

Researched first: nuvita-admin has an approval-workflows system, but it is a static config lookup with no submission/document/status tracking -- confirmed a false lead, nothing in the platform actually consumes it. HR LeaveRequest is the right template to copy the shape of (staged reviewer fields + attached document). A real server-side PDF renderer (ILetterRenderer) already exists in the shared kernel, used by EMR/OPD/Billing, not yet by HR or Canteen.

Split into 3 sub-projects since the full thing is too large for one spec: A) Canteen generates/reviews/approves its own monthly report (useful standalone), B) HR receives and approves it, C) payment tracking. B and C need A to exist first.

Spec for A written and committed to clinq-docs: modules/canteen-management/specs/2026-11-01-monthly-subsidy-report-design.md. Scopes out subsidy rule management (confirmed still HR-owned, unchanged), PDF generation (deferred to B, reuse ILetterRenderer), and any HR-facing submission. New MonthlySubsidyReport/Line entities (snapshot, not live-computed -- an approved report must not drift if underlying data could theoretically change), Draft->UnderReview->ChangesRequired->Approved workflow, Canteen-only.

Next: user reviews the spec, then writing-plans for an implementation plan.

No data to display

Actions

Also available in: PDF Atom