Central administrator advances
This register uses the authenticated central database. Requests do not post money. Only the Chief Administrator may approve or reject a request; actual disbursement requires a separate confirmation and is recorded as a separate audited transaction. Recoveries are allocated against already-posted collections or borrower principal repayments, never double-counted as a second receipt.
Sign in to view central advance requests.
| Requested | Provider | Amount | Recovered | Outstanding | Reason | Requester | Approver | Status | Action |
|---|---|---|---|---|---|---|---|---|---|
| Sign in to load central requests. | |||||||||
Fund income & expense register
Record non-transaction income and genuine operating expenses. Member contributions, loan repayments, loan interest and penalties already arise from the transaction ledger and must not be entered again here.
Recorded income and expenses
| Date | Type | Category | Reference | Explanation | Recorded by | Amount |
|---|
Administrator / director advance register
An advance is tracked as a separate funding liability, not member contribution, donation, loan income or distributable profit. Repayments reduce the outstanding advance.
Advance balances
| Advance ID | Provider | Date | Original amount | Recovered | Outstanding | Reason |
|---|
Apr 2026 – Mar 2027
0
₹0
₹0
—
Local only
—
0
Local prototype only · Member and collection figures are from this device. Available Fund and dividend are not calculated. Central ledger is not connected.
Register annual membership
Central member register
This register reads and writes the authenticated central database only. It does not import local demo members.
| Numeric ID | Formal ID | Name | Weekly | Joined | Status | Action |
|---|---|---|---|---|---|---|
| Central member records not loaded. | ||||||
Current-year members
| ID | Name | Phone | Weekly | Joined | Status |
|---|
Central cloud counter · authenticated mode
This counter talks only to the configured Shree Ram Worker API. It does not read or write this browser's localStorage fund ledger. Leave the API address blank until the independent Worker and D1 database have been deployed and health-checked.
Pending UPI verification queue
UPI receipts appear here as pending and do not reduce dues until a different authorised operator verifies them.
Cash and bank entries post after operator confirmation. UPI entries remain pending until a different authorised operator verifies the UTR. A successful preview expires after 15 minutes and is tied to this operator and the current member-ledger version.
Local prototype (device-only)
The legacy form below is retained for demo/testing only. Its entries do not sync with the central ledger. Do not use it for real fund collections.
Record a member payment
Central loan applications
Requests and decisions are stored in the central database. Approval is not disbursement; no money moves and no loan account is created at this stage.
| Member | Requested | Purpose | Status | Requested | Decision / disbursement |
|---|---|---|---|---|---|
| Central loan applications not loaded. | |||||
Central loan account register
Balances are calculated from posted central transactions and loan allocations. Pending UPI repayments do not reduce balances until independent verification.
| Loan ID | Member | Original principal | Disbursed week | Disbursed date | Status | Ledger |
|---|---|---|---|---|---|---|
| Central loan accounts not loaded. | ||||||
Register loan disbursement (local prototype only)
Flexible loan repayment
Loan register
| Loan | Member | Original | Outstanding | Current weekly interest |
|---|
Transactions & audit trail
Corrections are recorded as reversals with a mandatory reason. Original entries remain visible; never silently edit a posted transaction.
| Date | Reference | Member | Type | Mode | Amount | Receipt / Correction |
|---|
Financial Reports · local prototype
This original report panel reads this browser’s local prototype records only. It is not the central financial ledger. Reversed local transactions are excluded from totals and remain visible in the local transaction audit trail.
| Choose a report and select Generate report. |
Central financial reports
Authenticated read-only reports generated from the central database. These reports never read the local prototype ledger. Pending and reversed transactions remain explicitly labelled where the report includes transaction status.
| No central report loaded. |
Central Weeks 48–52 settlement preview
Read-only central calculation from posted contributions and loan allocations. The borrower may repay voluntarily during Weeks 48–52. This preview never offsets money, settles an account or creates a recovery case.
Annual Settlement & Dividend
Calculations use actual posted contribution allocations and current loan balances. Set the proposed dividend rate; this is a projection, not a declared or guaranteed payout. Final settlement requires committee approval and verified fund availability.
| Member ID | Member | Eligible contributions | Principal due | Interest due | Penalty due | Proposed dividend | Indicative net settlement |
|---|---|---|---|---|---|---|---|
| Calculate to view member settlements. | |||||||
Dividend funding & reserve assessment
This is a funding assessment only. It does not declare or guarantee a dividend. It counts realised loan interest and penalty receipts from posted transactions plus separately recorded other income, less recorded expenses. Administrator advances are excluded because they are repayable funding, not income.
Year-end closure & renewal readiness
This review is non-posting. It checks recorded data and prepares an archive snapshot. It does not settle member accounts, forgive balances, declare dividends, reset the year or authorize a new cycle.
Role and permission policy
Target production permissions. These are policy definitions, not active login permissions in this local prototype.
| Activity | Committee member | Chief Administrator | Dual approval |
|---|---|---|---|
| Enter member and collection records | Allowed | Allowed | No |
| Enter loan application / repayment | Allowed | Allowed | No |
| Approve loan sanction / disbursement | Recommend | Final approval | Policy / risk based |
| Penalty waiver / negotiated reduction | Recommend | Final approval | For sensitive exceptions |
| Weekly cash closing | Prepare | Approve | Mismatch requires explanation |
| Reverse posted transaction | Request / document | Approve | Required for production |
| Final annual settlement / year closure | Review | Approve | Chief Admin + committee |
| Reopen locked financial period | Request | Approve | Chief Admin + one committee member |
| Change annual financial rules | Review / recommend | Approve before cycle | Documented member / committee approval |
Mandatory production security gates
Do not use approval-name fields as proof of approval. Do not enter live member financial data until these gates are implemented and independently tested.
Required audit event fields
Each production event must be written server-side and retain the original record. Required fields: event ID, fund year, actor user ID, actor role, action, record type and ID, timestamp, before/after values or immutable references, reason, approval request ID, approver identity, approval timestamp, device/session reference and reversal linkage. Audit events must not be editable or deletable by ordinary application users.
Safe implementation sequence
- Confirm zero-cost backend and hosting limits before provisioning or enabling paid features.
- Configure authentication and verify email / recovery paths.
- Complete server-side role and fund-year authorization in the Worker API (D1 does not provide PostgreSQL-style row-level security).
- Implement approval requests and server-side approval checks.
- Write immutable audit events for every financial mutation.
- Test unauthorized access, duplicate approvals, replay, rollback, backup restore and multi-device conflicts.
Independent project status: The Shree Ram Worker/D1 backend foundation is being developed separately. No cloud account, database, credentials or deployment have been configured or verified for this project.
Cycle settings
Sunday cash closing
Prepare a weekly cash and verified digital reconciliation. A closing with a mismatch requires an explanation and Chief Administrator approval. A closed week is locked against a second closing in this prototype.
Backup and restore
Export a complete JSON backup to keep your records safe. Restore only a backup created by this application.
Penalty waiver / adjustment
Record an authorised reduction with a reason. The original penalty calculation remains available in the adjustment history.
Approved holiday / extension
A recorded extension suspends penalty increments for the selected member during the approved week range. Record the approving authority and reason.
Calculation rules currently applied
- Penalty: 5% of full weekly commitment for each delay-week number (progressive).
- Loan interest: 0.5% weekly on the next ₹1,000 slab rounded upward; e.g. ₹4,001–₹5,000 → ₹25/week.
- Repayment is voluntary; no compulsory instalments or weekly overdue penalties.
- When both interest and principal are paid, allocate interest first.
- Cash and UPI receipts require explicit confirmation/verification.