> ## Documentation Index
> Fetch the complete documentation index at: https://docs.criar.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Fees Module

> SKOLE-FEES — Fees Module

# SKOLE-FEES — Fees Module

**Module ID:** `SKOLE-FEES` | **Version:** 0.5 | **Status:** Placeholder / Planned\
**Products:** Parent App

***

## 1. Overview

| Field              | Value                                                                             |
| ------------------ | --------------------------------------------------------------------------------- |
| **Module Name**    | Fees                                                                              |
| **Module Code**    | FEES                                                                              |
| **Status**         | In development — UI screen exists, backend not yet wired                          |
| **Business Value** | Will allow parents to view fee statements, outstanding dues, and payment history. |

### Scope In (Planned)

* Fee statement display per student
* Due date visibility
* Payment history

### Scope Out (Current Phase)

* Online payment gateway integration (Razorpay/Stripe)

***

## 2. Requirements

### Functional Requirements (FR)

*What the module must DO — actions, behaviors, and outcomes.*

* **SKOLE-FEES-FR001:** The module shall allow parents to view comprehensive fee statements for each linked student.
* **SKOLE-FEES-FR002:** The module shall display clear visibility of upcoming and past due dates for various fee components.
* **SKOLE-FEES-FR003:** The module shall provide a full history of all payments made, including successful and failed attempts.

### Non-Functional Requirements (NFR)

*How well the module must do it — performance, security, and reliability.*

* **SKOLE-FEES-NFR001:** The module shall perform real-time calculation of outstanding dues based on the student's assigned fee structure.
* **SKOLE-FEES-NFR002:** The module shall behave securely by encrypting all payment-related transaction identifiers.

### Constraints

*Rules and boundaries — tech choices and platform restrictions.*

* **C001:** We must defer implementation of the payment gateway (Razorpay/Stripe) until the second phase of development.
* **C002:** We cannot store raw credit card or bank details locally due to PCI compliance restrictions.

## 3. UI Requirements

| ID                 | Screen     | Route   | Description                                                        |
| ------------------ | ---------- | ------- | ------------------------------------------------------------------ |
| `SKOLE-FEES-UI001` | FeesScreen | `/fees` | Static placeholder showing "Fee details coming soon" or dummy data |

**Note:** `FeesScreen.tsx` exists (9.7 KB) but has no live API connection.